I created an automagically configured Jenkins controller. It spun up in Amazon Web Services, it grabbed and installed its private keys for access, and it was stateless. But… But the Jenkins AMI came with a Jenkins config.xml configured with agent AMI ids when it was built. As development moved forward (CICD, after all), the config.xml…
Continue ReadingJenkins
Jenkins | Seems Like You Really Need SCM Polling
I tested notifyCommit messages sent to the git plugin in Jenkins – what happens when you commit several different branches in the same repo and rely on the git plugin to catch and schedule. The results were – odd. Some branches committed never made it. The limit for certainty seems to be the first commit,…
Continue ReadingnotifyCommit messages to Same Repo
I started off from scratch with our CicdDiscover Jenkins plugin. I created and kicked off a job in Jenkins by committing to branch “test-cicddiscover-branch”. This as expected created the job. It then started building – not the test-cicddiscover-branch change, but an earlier change to origin/rc. I went ahead and committed another two changes, to branch…
Continue ReadingJenkins CicdDiscover plugin
I worked through how to add in the trigger for building the new job in Jenkins after the CicdDiscover plugin created it – and realized… All it has to do is re-send the original /git/notifyCommit?url=Url hook. The second time the CicdDiscover plugin will ignore it and the original Git plugin will catch and handle. This…
Continue ReadingMore on Jenkins and CICD
The original Jenkins git plugin drops the case where the repo string it’s parsing for doesn’t exist in a Jenkins job. To use this all by itself we would have to by hand configure and maintain jobs in Jenkins and in a large CICD environment that’s not workable. It’s possible that in the Jenkins architecture…
Continue Reading- 1
- 2