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

Begin mini-migration from Plugin-GitHash to Implementation-Build #471

Merged
merged 1 commit into from
Apr 19, 2023

Conversation

basil
Copy link
Member

@basil basil commented Apr 18, 2023

For consistency with jenkinsci/pom#419, put the Git hash in Implementation-Build rather than Plugin-GitHash. For now I am keeping it in Plugin-GitHash since it was (very recently) added there for PCT, but I will update PCT to start consuming Implementation-Build instead and plan to rip out Plugin-GitHash shortly (in a month or so) once it's no longer used by anything (not much is using it today, just the AWS Java SDK plugin I think).

Copy link
Member

@jtnord jtnord left a comment

Choose a reason for hiding this comment

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

only minor NIT is that Implementation-Build implies it is build related rather than source related (e.g. a tag can be built multiple times - locally. or on CI if the deploy failed due to an artifactory issue etc), esp as we have Jenkins which also has builds.

@basil
Copy link
Member Author

basil commented Apr 19, 2023

I agree that the name isn't ideal, but it is what is recommended in https://www.mojohaus.org/buildnumber-maven-plugin/usage.html so more people are likely to be using that name than any other name.

@basil basil merged commit 68a46ee into jenkinsci:master Apr 19, 2023
@basil basil deleted the implementation-build branch April 19, 2023 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants