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

We may no longer need length limitations for groupId, artifactId #2619

Open
daniel-beck opened this issue Jun 28, 2022 · 6 comments
Open

We may no longer need length limitations for groupId, artifactId #2619

daniel-beck opened this issue Jun 28, 2022 · 6 comments

Comments

@daniel-beck
Copy link
Contributor

What feature do you want to see added?

After jenkins-infra/update-center2#605, we may no longer have a need for length limitations for groupId, artifactId.

RPU itself can handle names based on overly long artifact IDs in

// Artifactory has an undocumented max length for permission target names of 64 chars (and possibly other types)
// If length is exceeded, use 55 chars of the prefix+name, separator, and 8 hopefully unique chars (prefix of name's SHA-256)
name = name.substring(0, 54) + '_' + sha256(name).substring(0, 7)
.

Otherwise I'm not sure we need to limit lengths for infra reasons. We can probably relax the current lengths and allow longer values, but perhaps not fully unrestricted?

Upstream changes

No response

@daniel-beck
Copy link
Contributor Author

#2681 likely identifies a length limitation in GitHub repo names, which usually correspond with artifact ID.

@jetersen
Copy link
Contributor

jetersen commented Aug 12, 2022

Can this be closed as well @daniel-beck ? or is it related to another API.

@daniel-beck
Copy link
Contributor Author

Given that #2681 was a new discovery when I commented, it's unrelated.

@timja
Copy link
Member

timja commented Aug 12, 2022

It's related as it was a reason to not lift the limitation isn't it?

Now that it's resolved we can possibly go ahead and remove the limitation?

@daniel-beck
Copy link
Contributor Author

Now that it's resolved we can possibly go ahead and remove the limitation?

If there's no other reason to limit lengths. I don't know. Yoloing would not be a good idea.

@timja
Copy link
Member

timja commented Aug 12, 2022

There's no known issues but I haven't rushed to remove this as I don't think it's harmful to have reasonable length names (i.e. not too long)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants