-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Comments
#2681 likely identifies a length limitation in GitHub repo names, which usually correspond with artifact ID. |
Can this be closed as well @daniel-beck ? or is it related to another API. |
Given that #2681 was a new discovery when I commented, it's unrelated. |
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? |
If there's no other reason to limit lengths. I don't know. Yoloing would not be a good idea. |
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) |
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
repository-permissions-updater/src/main/groovy/io/jenkins/infra/repository_permissions_updater/ArtifactoryAPI.groovy
Lines 138 to 140 in 4ae7713
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
The text was updated successfully, but these errors were encountered: