-
-
Notifications
You must be signed in to change notification settings - Fork 267
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
[INFRA-2513] - Update allowed-labels.properties #353
base: master
Are you sure you want to change the base?
Conversation
do not allow a slave label
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jtnord Although it is technically correct, we need to do some cleanup and in https://github.com/jenkins-infra/update-center2/blob/master/src/main/resources/label-definitions.properties first. I'd guess replacing all labels by agent
is a best step.
If you update the Label definitions file, I will get GitHub repos fixed
If we take |
changed all to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should amend https://github.com/jenkinsci/jenkins/blob/9ead76e210a52cda65befe89e70355127ad3ff31/core/src/main/resources/hudson/model/Messages.properties#L325 first to support the replacement, and backport the change into LTS, otherwise the display of this label in Jenkins will suffer quite a bit, especially since jenkinsci/jenkins#4534
Likewise, https://github.com/jenkins-infra/plugin-site-api/blob/bd2a5fe337ddf9526666ef5a7ad6a3f5bb388c6f/src/main/resources/categories.json#L34 and https://github.com/jenkins-infra/plugin-site-api/blob/bd2a5fe337ddf9526666ef5a7ad6a3f5bb388c6f/src/main/resources/labels.json#L35-L36
@jtnord Are you still interested in this change? |
I do not know enough about the UC to know what needs changing and where to move this forward. This was an attempt to keep aligning things better given the project decided to move to agents. |
If you are fine @daniel-beck @jtnord , I would like to keep it open. I want to deliver an engine for label aliases, and I will do it on the top of this PR |
Works for me. |
I will be unable to work on a new engine anytime soon. It would be needed for removing "slave" terms from labels and Artifact IDs. Maybe @MarkEWaite or @markyjackson-taulia would be interested to facilitate this change in the community |
I can work on this. I will sync with you @oleg-nenashev |
That's quite some scope creep here. |
do not allow a slave label
someone with access to all infra could find/replace this label with agent if they where so inclined.