From 24e6f1397347cff742a676c8e974a2f08fa127fe Mon Sep 17 00:00:00 2001 From: Inaki Date: Wed, 8 Jan 2020 17:47:26 +0100 Subject: [PATCH] Update jenkins.md --- docs/jenkins.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/jenkins.md b/docs/jenkins.md index d853bd91..df0ab95c 100644 --- a/docs/jenkins.md +++ b/docs/jenkins.md @@ -93,3 +93,18 @@ ## Jenkins X * [itnext.io/tagged/jenkins-x](https://itnext.io/tagged/jenkins-x) * [itnext.io: Jenkins X — Managing Jenkins](https://itnext.io/jenkins-x-managing-jenkins-926f0e0f8bcf) + +## CI/CD BOTs +''' +Use bots to accomplish tasks like merging PR's that have been approved and automatically updating dependencies. Usage of one of these bots might allow us to trigger certain builds based off of specific GitHub tags, it would allow us to only selectively run certain test suites and increase the throughput of the build by only testing changes made in a branch / PR. + +Investigate options that are available and see if we can integrate them with CI. + +We should be able to configure this bot to automatically apply labels to PR's based off of what is changed in a PR. For instance, if a PR contains any documentation changes, the area/Documentation label can be applied. +''' +* [Jenkins-X UpdateBOT](https://github.com/jenkins-x/updatebot) +* [PlasticSCM MergeBot Jenkins Plugin](https://wiki.jenkins.io/display/JENKINS/PlasticSCM+MergeBot+plugin) +* [support.cloudbees.com: how to configure jenkins for git merge](https://support.cloudbees.com/hc/en-us/articles/227246387-How-to-Configure-Jenkins-for-Git-Merge-) +* [Jenkins ghprb plugin](https://github.com/jenkinsci/ghprb-plugin) +* [Bors-ng: A merge bot for GitHub Pull Requests](https://github.com/bors-ng/bors-ng) +