-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat: create an annotated tag instead of a ligthweight tag to ensure the correct timestamp #26
Conversation
your repo: doesn't exist. you need to fork that and point it to your other repo / branch. or just push an origin branch |
I went for jenkinsci/jenkins-infra-test-plugin#47 for testing. It's hackish but it should do. @timja https://github.com/dduportal/github-reusable-workflows exists (plural form as per https://github.com/jenkinsci/jenkins-infra-test-plugin/pull/45/files#diff-ea3ea8c9932adc7ba8161ceda844fedd43b006848ef1140c050cbd7ea0788a18R14) |
test: try annotated tags with jenkins-infra/jenkins-maven-cd-action#26
Current testing says: I guess I have to rework it a bit :) |
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.
Looks OK, assuming it in fact works in the test plugin.
This PR fixes #25.
It ensures that an annotated tag is created before publishing the release.
It follows the official Git API documentation about creating tags in https://docs.github.com/en/rest/git/tags#create-a-tag-object:
Note: I have no idea how to properly test this in "real life" scenario. I tried in jenkinsci/jenkins-infra-test-plugin#45 but it seems that we use 2 levels of actions and there are "local" actions (e.g. restricted to the organization).
I'll try to publish my modified action to gh action and work with it but it's not really easy: any tip is welcome