-
Notifications
You must be signed in to change notification settings - Fork 302
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
Azure DevOps - Git branch name #438
Comments
Thanks for creating an issue! That sounds reasonable. Just as a hint (if you not already know): |
Thanks @TheSnoozer I had a quick look around at the Azure Pipeline environment variables and the source code, I found exactly what you pointed out, thanks for that. Running some tests now and creating the pull request soon for you guys to review (Y) |
Thanks for making the changes and improving this project! |
…for Azure DevOps
Issue #438 Populate "git.branch" and "git.build.number" for Azure DevOps
Implemented via #439. Thanks for your contribution! |
@TheSnoozer Entirely my pleasure, thank you guys for writing the plugin in the first place! (Y) |
It's always great to know that this plugin is still in use :-) Anyhow, as far as i remember travis deploys snapshots of the master-branch to oss-sonatype. if you want to start to use this feature you could already do so, by specifying the Sonatype-Snapshot repo. e.g. <pluginRepositories>
<pluginRepository>
<id>sonatype-snapshots</id>
<name>Sonatype Snapshots</name>
<url>https://oss.sonatype.org/content/repositories/snapshots/</url>
</pluginRepository>
</pluginRepositories> If you'd prefer a more official release feel free to ping me in #432. Releases only happen randomly or when users (YOU) ask for it ;-) |
Thank you, didn't know about the Sonatype snapshot builds, I had deployed mine on our Artficatory to be able to test it. Thanks for the notes, whenever you feel it's worth releasing it it's fine, no pressure :-) |
Describe your idea
AzureDevops checks out Git branches in detached mode, resulting in
git.branch
being populated with the commit hash.Expected Behavior
The branch name can be populated from
BUILD_SOURCEBRANCHNAME
environment vaiable as per Azure Devops / Azure Pipelines - Build variablesAdditional context
Will provide a pull request soon with proposed changes for review.
The text was updated successfully, but these errors were encountered: