Skip to content
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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

jtnord
Copy link
Contributor

@jtnord jtnord commented Mar 10, 2020

do not allow a slave label

someone with access to all infra could find/replace this label with agent if they where so inclined.

do not allow a slave label
@oleg-nenashev oleg-nenashev added the on-hold This PR is on hold, typically because of a dependency to another change or event. label Mar 10, 2020
Copy link
Contributor

@oleg-nenashev oleg-nenashev left a 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

@oleg-nenashev
Copy link
Contributor

If we take agents or something similar as a new label, again I will do the GitHub legwork. Created https://issues.jenkins-ci.org/browse/INFRA-2513 as a placeholder

@oleg-nenashev oleg-nenashev changed the title Update allowed-labels.properties [INFRA-2513] - Update allowed-labels.properties Mar 10, 2020
@jtnord
Copy link
Contributor Author

jtnord commented Mar 10, 2020

changed all to agent in the properties file. looks a little strange as the prior label was pluralised (slaves) and now it is not (agent) but other things are singular (report vs reports / parameter vs parameters)

Copy link
Contributor

@daniel-beck daniel-beck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@daniel-beck
Copy link
Contributor

@jtnord Are you still interested in this change?

@daniel-beck daniel-beck added the metadata This PR changes metadata (suspensions, labels, etc.) label May 24, 2020
@jtnord
Copy link
Contributor Author

jtnord commented May 26, 2020

@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.

@jtnord jtnord closed this May 26, 2020
@oleg-nenashev oleg-nenashev reopened this May 26, 2020
@oleg-nenashev oleg-nenashev self-assigned this May 26, 2020
@oleg-nenashev
Copy link
Contributor

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

@daniel-beck daniel-beck added the needs-fix This PR needs to be fixed before it can be considered mergable. label May 26, 2020
@daniel-beck
Copy link
Contributor

Works for me.

@oleg-nenashev
Copy link
Contributor

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

@markjacksonfishing
Copy link

I can work on this. I will sync with you @oleg-nenashev

@daniel-beck
Copy link
Contributor

and Artifact IDs

That's quite some scope creep here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
metadata This PR changes metadata (suspensions, labels, etc.) needs-fix This PR needs to be fixed before it can be considered mergable. on-hold This PR is on hold, typically because of a dependency to another change or event.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants