Difference between revisions of "CI Minimalistic GitHub's Guide"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | This section collects the steps for Developers to enable the CI pipeline | + | This section collects the steps for Developers to enable the CI pipeline on a GitHub repository. |
# Configure the [[Development_Machine| development machine]]. | # Configure the [[Development_Machine| development machine]]. | ||
# Switch the POM to inherit from maven-parent 1.1.0 (the Jenkins project will not build until this step). | # Switch the POM to inherit from maven-parent 1.1.0 (the Jenkins project will not build until this step). | ||
| − | # Make sure the SCM Connection in your POM is properly | + | # Make sure the SCM Connection in your POM is properly configured to point to your GitHub repository. |
# Create a [[Jenkins_Projects_(aka_Jobs)_for_GitHub| Jenkins job]] that builds the GitHub repository. | # Create a [[Jenkins_Projects_(aka_Jobs)_for_GitHub| Jenkins job]] that builds the GitHub repository. | ||
# Set up a [[GitHub/Jenkins: Setting up Webhooks| Jenkins/GitHub webhook]] | # Set up a [[GitHub/Jenkins: Setting up Webhooks| Jenkins/GitHub webhook]] | ||
Latest revision as of 00:24, 1 December 2019
This section collects the steps for Developers to enable the CI pipeline on a GitHub repository.
- Configure the development machine.
- Switch the POM to inherit from maven-parent 1.1.0 (the Jenkins project will not build until this step).
- Make sure the SCM Connection in your POM is properly configured to point to your GitHub repository.
- Create a Jenkins job that builds the GitHub repository.
- Set up a Jenkins/GitHub webhook
- Work on the project following the branching strategy
- At release time, perform the expected release activities
To have a complete overview of the Continuous Integration Procedure see CI guide.
