-
Notifications
You must be signed in to change notification settings - Fork 182
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
print_rel_notes
should support customizing tarball_name
#435
Labels
P3
An issue that we are not working on but will review quarterly
Comments
guw
added a commit
to guw/rules_pkg
that referenced
this issue
Oct 15, 2021
guw
added a commit
to guw/rules_pkg
that referenced
this issue
Oct 15, 2021
guw
added a commit
to guw/rules_pkg
that referenced
this issue
Oct 15, 2021
@aiuto I'd like to give it another try. Do you have an idea for implementation? |
aiuto
added a commit
to aiuto/rules_pkg
that referenced
this issue
Feb 14, 2022
This allows you to use artifact names that do not follow the standard convention. Fixes bazelbuild#435
aiuto
added a commit
that referenced
this issue
Feb 15, 2022
This allows you to use artifact names that do not follow the standard convention. Fixes #435
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
tarball_name
is currently hard coded inprint_rel_notes
to follow a strict pattern ofrepo
name andversion
. This does not support the case where different name is used for the tar file. The call/build then fails with missing input file.The text was updated successfully, but these errors were encountered: