Part 2 improving your software development v1.0
•Als PPT, PDF herunterladen•
1 gefällt mir•895 views
Improving your software development process
![Outline ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Ähnlich wie Part 2 improving your software development v1.0
Ähnlich wie Part 2 improving your software development v1.0 (20)
Mehr von Jasmine Conseil
Mehr von Jasmine Conseil (19)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Part 2 improving your software development v1.0
- 1. Part 2: Improving your software development process March 2011 Santa Clara Karim DJAAFAR CO of Jasmine Conseil
- 3. TOWARDS A BETTER BUILD PROCESS USING AGILE TOOLS
- 4. Build is often a hard process
- 6. The Integrate button Source : Continuous Integration by Paul M. DUVALL
- 8. Build Tools Automation in a agile scenario CI Build Server Automated testing Automated code quality Build Tool
- 13. What is the primary build tool and release management you typically use ? Source: Eclipse community Survey
- 17. Common way to build applications MOJO – Maven 2 Plugins Project http://mojo.codehaus.org/ plugins user e.g. mvn install M2 generate- sources compile test install deploy package integration- test Well-known phases mojo mojo mojo mojo mojo bindings
- 18. CONTINUOUS INTEGRATION PRINCIPLES AND TOOLS
- 20. Continuous Integration (CI) scenario
- 23. The components of a CI system Commit changes Compile Source Code, Integrate Database, Run Tests, Run Inspections, Deploy Software Feedback Mechanism Generate feedback SCM Server (Svn, Git, …) CI Server
- 29. JASFORGE © PROJECT AND HUDSON CI TOOL
- 34. List of projects
- 39. JASFORGE © HUDSON TOOLS
- 42. Thank you for your Attention Jasforge: A Jasmine Conseil concept http://www.jasmineconseil.com Need More information ? [email_address]
Hinweis der Redaktion
- 1. First, a developer commits code to the version control repository. Meanwhile, the CI server on the integration build machine is polling this repository for changes (e.g., every few minutes). 2. Soon after a commit occurs, the CI server detects that changes have occurred in the version control repository, so the CI server retrieves the latest copy of the code from the repository and then executes a build script, which integrates the software. 3. The CI server generates feedback by e-mailing build results to specified project members. 4. The CI server continues to poll for changes in the version control repository.
- An agile Platform to manage Continuous Integration Process Help development team to better collaborate and be efficient in their daily task (project creation, development, tests, integration, deployment ...) A central platform for the creation and managing of middle to complex projects, from the inception to the deployment Available in two edition: Community Edition (Eclipse Public License) Enterprise Edition
- Démo video CreateProject ImportProject