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

From Gcube Wiki
Jump to: navigation, search
Line 8: Line 8:
 
# Setting up the [[Gitea/Jenkins:_Setting_up_Webhooks#Webhook_on_the_Gitea_repository| webhook on the Gitea Repository]]
 
# Setting up the [[Gitea/Jenkins:_Setting_up_Webhooks#Webhook_on_the_Gitea_repository| webhook on the Gitea Repository]]
 
# [[Git_Eclipse#Clone_the_Git_Repository| Clone the Git Repository]] on the development machine
 
# [[Git_Eclipse#Clone_the_Git_Repository| Clone the Git Repository]] on the development machine
# Switch the POM to inherit from the maven-parent 1.1.0-SNAPSHOT.
+
# Switch the POM to inherit from maven-parent 1.1.0-SNAPSHOT.
 
# Work on the project following the [[Git_Branching_Strategy| branching strategy]]
 
# Work on the project following the [[Git_Branching_Strategy| branching strategy]]
 
# 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]].''
 
''Back to the [[Continuous_Integration_procedure_(2019) | CI guide]].''

Revision as of 04:35, 31 May 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.
  9. Work on the project following the branching strategy
  10. At release time, perform the expected release activities

Back to the CI guide.