Difference between revisions of "Template:Menu content continuous integration"
| (13 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Category: | + | [[Category:Menu]] |
| − | [[ | + | |
| + | |||
| + | [[File:icon_continous integration.png|64px|caption|Continuous integration]] 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 | ||
| + | * '''Artifact control''': Artifactory, 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 | ||
| + | |||
=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]] | + | * [[SVN server installation (Linux)]] |
| + | * [[SVN server installation (Windows)]] | ||
* [[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]] | ||
| + | |||
| + | |||
| Line 23: | Line 54: | ||
* [[Step-up artefact version on each build]] | * [[Step-up artefact version on each build]] | ||
| − | |||
| − | |||
| − | =Software quality= | + | |
| + | =Software quality metrics= | ||
| + | |||
| + | [[File:Improvement.png|64px|Caption|Quality principles]] Quality principles | ||
| + | |||
| + | [[Quality policies and enforcement]] | ||
| + | |||
| + | |||
| + | |||
[[File:Icon sonar.png|64px|caption|Sonar]] Sonatype sonarqube | [[File:Icon sonar.png|64px|caption|Sonar]] Sonatype sonarqube | ||
| − | [[Sonar]] | + | [[Sonar|Sonar setup]] |
| + | [[Sonar + maven principle]] | ||
| − | + | [[Sonar + maven configuration + Jenkins]] | |
| + | [[Maven site reports]] | ||
| + | |||
| + | =Artifacts hosting= | ||
[[File:Icon nexus.png|64px|caption|Nexus]] Sonatype Nexus Open-Source Edition | [[File:Icon nexus.png|64px|caption|Nexus]] Sonatype Nexus Open-Source Edition | ||
[[Nexus]] | [[Nexus]] | ||
| + | |||
| + | [[Nexus Maven configuration]] | ||
Latest revision as of 16:18, 21 May 2019
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
- Artifact control: Artifactory, 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
Quality principles
Quality policies and enforcement
Sonatype sonarqube
Sonar + maven configuration + Jenkins
Artifacts hosting
Sonatype Nexus Open-Source Edition
