Skip to content

Commit

Permalink
fix: comment gitlab bot recommendation
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 23d7f36 commit 4d330e9
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion gitlab/setup_jenkins_gitlab_integration.sh
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@ 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.
[jenkins pipeline best practice](https://github.com/eclipse-cbi/jiro/wiki/Jenkins#jenkins-pipeline-best-practices) and we encourage the following:
As part of our [Jenkins pipeline best practices](https://github.com/eclipse-cbi/jiro/wiki/Jenkins#jenkins-pipeline-best-practices), we encourage the 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/).
Expand Down

0 comments on commit 4d330e9

Please sign in to comment.