I wrote a jenkins plugin while I was idle between Oath and my current gig. This plugin is a simplification of Oath’s (AOL’s) CICD Discover plugin. Re-written from scratch. Instead of crafting java code in the plugin, I walked it back to its origins, where it sends execution to an external executable. The impetus to…
Continue ReadingI 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 ReadingI 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 ReadingI 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 ReadingThe problem with hacking into the git-plugin and calling a separate script is that the git-plugin for Jenkins is core to a lot of the Pipeline plugins we also want to move forward with. We have to maintain the altered git-plugin through updates as that plugin is under active development. And the external script has…
Continue ReadingJenkins has survived Hudson and is a go-to UI for what used to be called Release Engineering. It can become a key element in Continuous Integration Continuous Delivery. I’ve been setting it up as a packer-ansible integration tool to build code then package it as AMI’s (Amazon Machine Images) to drop into AWS (Amazon Web…
Continue Reading