Skip to content

Commit

Permalink
feat: add extra comment for gitlab bot post instruction
Browse files Browse the repository at this point in the history
Signed-off-by: sebastien.heurtematte <sebastien.heurtematte@eclipse-foundation.org>
  • Loading branch information
heurtematte authored and fredg02 committed Jul 29, 2024
1 parent 9be3bf4 commit c6b614f
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions gitlab/setup_jenkins_gitlab_integration.sh
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,10 @@ Post the following on the corresponding HelpDesk issue:
A GitLab bot user for ${PROJECT_NAME} has been created, along with credentials that have been added to the CI instance (SSH credentials ID: \`gitlab-bot-ssh\`).
A webhook that will trigger CI jobs has been added as well.
As part of our [jenkins pipeline best practice](https://github.com/eclipse-cbi/jiro/wiki/Jenkins#jenkins-pipeline-best-practices), we encourage following recommendations:
* Utilize \`Jenkinsfile\`: it allows to define an entire pipeline as code by managing build process declaratively or with scripted syntax, making pipeline configuration version-controlled and therefore reproducible. Learn more about Jenkinsfile [here](https://www.jenkins.io/doc/book/pipeline/jenkinsfile/).
* In addition \`Multibranch Pipeline\`: automatically creates a pipeline for each branch/merge request of a repository. This approach simplifies branch management and enables automated branch-based builds and testing. More about Multibranch Pipeline [here](https://www.jenkins.io/doc/book/pipeline/multibranch/).
The recommended way of creating a GitLab triggered job and handle merge request is as follows:
* create a Multi-branch pipeline job
* in your job config under "Branch Sources > Add source" select "GitLab project"
Expand Down

0 comments on commit c6b614f

Please sign in to comment.