Intro to learn GitHub

Very interesting references for GitHub:

– http://git-scm.com/docs

– https://help.github.com/categories/54/articles

– https://guides.github.com/activities/hello-world/

– http://git-scm.com/book/en/Getting-Started-About-Version-Control

– http://semver.org/

– https://guides.github.com/features/mastering-markdown/

Anuncios

Maven and continous integration

Good references:

http://mikiorbe.wordpress.com/2008/12/04/presentando-maven-explicacion-basica/

http://mikiorbe.wordpress.com/2009/01/20/repositorios-maven-nexus/

https://www.ibmdw.net/urbancode/docs/continuous-delivery-maturity-model/

http://docs.codehaus.org/display/MAVENUSER/Maven+Repository+Manager+Feature+Matrix

http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/hudsonADF/hudsonADF.html

How I believe the build and deploy pipeline works is:

1. A programmer checks code in SVN (Subversion)
2. Hudson detects it (using the plug-in with subversion that comes initially with Hudson)
3. Hudson launch Maven to do the build, for that, it is necessary to have previously made the pom for the project. The pom is an xml doc that defines how to build the project (sequence of steps, relations with other modules,,…). It is Maven who uses the pom.
4. Maven leaves the built module in a repository of built modules which can be Nexus. Maven also goes to Nexus to capture other modules that he can need to do the builds.
5. Hudson can continue after Maven is finished, for example doing tests or deploying the modules
6. If something goes wrong it can be set up in a way that certain roles will know it (mail, …)

Look as well to…….

http://rterp.wordpress.com/2012/02/28/creating-a-build-pipeline-using-maven-jenkins-subversion-and-nexus/