I followed Darin Pope’s video on YouTube (link here) and successfully set up a GitHub Organization in Jenkins. Everything is working great — all branches are discovered and builds are automatically triggered as expected.
However, I’m running into an issue with tags. I’ve already enabled “Discover Tags” in the configuration, and I can see the tags listed under the “Tags” tab in Jenkins. But for some reason, when I push new tags to the repository, they don’t trigger any builds.
Does anyone know what might be missing or how I can get tag builds to trigger properly?
Thanks in advance for any help!
TL;DR; By default, builds are not triggered by git tag even when discovered. It is to avoid build storms if you reload your configuration or migrate your controller (otherwise your tags could be rebuilt accidentally and overriding artifacts or even failing).
However, by adding the Basic Branch Build Strategies plugin, you can set up your jobs to be triggered by tags which are less than 3 days olds (by default: can be tuned in the plugin). The configuration can be done at GitHub Organization Folder once for all, and then a “Scan Organization” will apply the setting to all children (and kick builds).
Be aware that git tag should be annotated to be sure their timestamps are set to when the tag is created (and not the commit’s timestamp).
In any case (with or without the plugin), you can trigger tags builds manually if they are discovered.