Difference between revisions of "Template:Menu content continuous integration"
(→Software quality metrics) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 58: | Line 58: | ||
=Software quality metrics= | =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 | ||
| Line 67: | Line 74: | ||
[[Sonar + maven configuration + Jenkins]] | [[Sonar + maven configuration + Jenkins]] | ||
| − | [[ | + | [[Maven site reports]] |
=Artifacts hosting= | =Artifacts hosting= | ||
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
