Difference between revisions of "Development"
Line 1: | Line 1: | ||
[[Category:Development]] | [[Category:Development]] | ||
Installation, configuration and usage. | Installation, configuration and usage. | ||
+ | |||
+ | |||
+ | =Nouveau menu= | ||
+ | |||
+ | {{Template:Menu content continuous integration}} | ||
+ | |||
+ | |||
+ | |||
+ | =Ancien menu= | ||
+ | |||
==Developer tools== | ==Developer tools== | ||
+ | |||
* [[JDK setup|Java JDK setup]] | * [[JDK setup|Java JDK setup]] | ||
* [[Maven]] | * [[Maven]] |
Revision as of 21:10, 18 October 2014
Installation, configuration and usage.
Contents
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
Subversion
- SVN server installation (Linux)
- SVN server installation (Windows)
- SVN server behind Apache2 proxy
- SVN client
GIT
Build server
Advanced stuff:
Software quality metrics
Quality policies and enforcement
Sonar + maven configuration + Jenkins
Artifacts hosting
Sonatype Nexus Open-Source Edition
Developer tools
- Java JDK setup
- Maven
- SVN client
- GIT client
- IDE configuration
- Java / JEE server
- Database
- Squirel client
- MySQL workbench
- MySQL server
- SOAPui
- Messaging servers
Programming
- Code
- Java
- JEE
- Spring
- JMS
- Maven tricks
- SQL
- Other
- Tests
- Units tests
- Integration tests
- Spring tests
- DB Unit
- Arquillian
- Load tests
- Architecture
- Design patterns
- SOA / ESB
- Clean code
- Performances check
- VisualVM (JMX monitoring of JDK)
- Methods
- Scrum
- Kanban
Continuous integration
TODO: GIT server
Hints
Java
Javascript