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

From Gcube Wiki
Jump to: navigation, search
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
This section collects the basic steps for gCube Developers to get started with the CI pipeline.
+
This section collects the steps for gCube Developers to get started with the CI pipeline.
  
# Configure the developer's machine
+
# Configure the [[Development_Machine| development machine]]
# Create a Git Repository in Gitea
+
# Create a new [[Git_Repositories#Create%20a%20New%20Repository| Git Repository]] in Gitea
# Import the SVN project into git
+
# [[Import_from_SVN| Import the SVN]] project into Git
# Enable Eclipse to work with Git
+
# Enable [[Git_Eclipse|Eclipse]] to work with Git
# Create the related Jenkins job
+
# Create the related [[Jenkins_Projects_(aka_Jobs)| Jenkins job]]
# Setting up the webhook
+
# Setting up the [[Gitea/Jenkins:_Setting_up_Webhooks#Webhook_on_the_Gitea_repository| webhook on the Gitea Repository]]
# Follow the branching strategy
+
# [[Git_Eclipse#Clone_the_Git_Repository| Clone the Git Repository]] on the development machine
# Release activities
+
# Switch the POM to inherit from maven-parent 1.1.0(the Jenkins project will not build until this step).
 +
# Work on the project following the [[Git_Branching_Strategy| branching strategy]]
 +
# At release time, perform the expected [[Continuous_Integration:_Developer| release activities]]
 +
 
 +
 
 +
''To have a complete overview of the Continuous Integration Procedure to [[Continuous_Integration_procedure_(2019)#Complete_Guide | CI guide]].''
 +
 
 +
[[Category:Continuous_Integration]]

Latest revision as of 15:56, 23 September 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(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 Procedure to CI guide.