Difference between revisions of "Template:Menu content continuous integration"
| Line 24: | Line 24: | ||
=Source code control= | =Source code control= | ||
| − | [[File:Icon svn.png|64px|caption|SVN]] Subversion | + | ==Subversion== |
| + | |||
| + | [[File:Icon svn.png|64px|caption|SVN]] Subversion (SVN) | ||
* [[SVN server installation (Linux)]] | * [[SVN server installation (Linux)]] | ||
| Line 30: | Line 32: | ||
* [[SVN server behind Apache2 proxy]] | * [[SVN server behind Apache2 proxy]] | ||
* [[SVN client]] | * [[SVN client]] | ||
| + | |||
| + | |||
| + | ==GIT== | ||
| + | |||
| + | [[File:Icon git.png|64px|caption|GIT SCM]] GIT | ||
| + | |||
| + | * [[GIT client]] | ||
| + | |||
| + | |||
Revision as of 17:45, 19 October 2014
Continuous Integration
To achieve "Continuous Integration" you need a set of tools + organizational changes.
This page only describes the tooling aspect.
You need:
- Source control: SVN, GIT, ...
- Build system: Jenkins
- Artefact control: Artefactory, Nexus, ...
- Project tool: for Scrum dashboard + Bug tracking. You can use software like JIRA, Redmine, ...
Sometimes you might use also:
- Software quality metrics - this will only check HOW you've done your work ; not if the feature is correct! - Sonar
- Documentation tools
Contents
Source code control
Subversion
Subversion (SVN)
- SVN server installation (Linux)
- SVN server installation (Windows)
- SVN server behind Apache2 proxy
- SVN client
GIT
GIT
Build server
Jenkins
Advanced stuff:
Software quality metrics
Sonatype sonarqube
Artefacts hosting
Sonatype Nexus Open-Source Edition
