-
-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make more use of "set build name" plugin to identify which builds are which #434
Comments
You ok with me adding this one @karianna ? |
Yes, was about to do it and then got side tracked by upgrading existing ones for security. |
For some reason I'm not seeing this in the web UI. More investigation required. Bumping to ensure that happens. |
(Perhaps https://plugins.jenkins.io/description-setter/ is a better choice as that doesn't require it to be set via a pipeline) |
Bumping this since I want to see if we can make properly use of this for things like VPC to identify which run is which without using pipelines. |
Will aim to do this as part of the restarts required by #2961 |
https://plugins.jenkins.io/build-name-setter/ has been installed as part of last week's maintenance. It was disabled immediately after install but I've enabled it now. May still need a restart to take effect or something. Bouncing to April on the basis it's had progress but not yet in a usable state for the purpose. |
e.g. showing version numbers on build/test jobs
https://wiki.jenkins.io/display/JENKINS/Build+Name+Setter+Plugin is the plugin and we currently have it on the JCK jenkins, but it's not being used on the main one.
The text was updated successfully, but these errors were encountered: