Difference between revisions of "CI Minimalistic Developer's Guide"

From Gcube Wiki
Jump to: navigation, search
Line 12: Line 12:
 
# At release time, perform the expected [[Continuous_Integration:_Developer| release activities]]
 
# At release time, perform the expected [[Continuous_Integration:_Developer| release activities]]
  
''Back to the [[Continuous_Integration_procedure_(2019) | CI guide]].''
+
 
 +
''To have a complete overview of the Continuous Integration P to [[Continuous_Integration_procedure_(2019) | CI guide]].''

Revision as of 07:45, 7 June 2019

This section collects the steps for gCube Developers to get started with the CI pipeline.

  1. Configure the development machine
  2. Create a new Git Repository in Gitea
  3. Import the SVN project into Git
  4. Enable Eclipse to work with Git
  5. Create the related Jenkins job
  6. Setting up the webhook on the Gitea Repository
  7. Clone the Git Repository on the development machine
  8. Switch the POM to inherit from maven-parent 1.1.0-SNAPSHOT (the Jenkins project will not build until this step).
  9. Work on the project following the branching strategy
  10. At release time, perform the expected release activities


To have a complete overview of the Continuous Integration P to CI guide.