-
Notifications
You must be signed in to change notification settings - Fork 826
[JAV-397] Add automatic signing of release on tagged builds #181
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
Conversation
<id>release</id> | ||
<build> | ||
<plugins> | ||
<plugin> |
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.
why do we need to add the config of maven-deploy-plugin?
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.
yes it is redundant as already while calling mvn deploy we are setting skiptest so this configuration is not required, I will update the changes
.travis.settings.xml
Outdated
<password>${env.SONATYPE_PASSWORD}</password> | ||
</server> | ||
</servers> | ||
<profiles> |
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.
This file is not properly indented
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.
Thanks @liubao68 , I have updated the file with proper indentedation
.travis.yml
Outdated
- mvn deploy -DskipTests -Prelease -Ppassphrase --settings .travis.settings.xml | ||
on: | ||
tags: true | ||
all_branches: true |
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.
does this mean deploying changes from all branches?
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.
if there is any tagged commit from any branch then it will deploy with auto-signing
|
||
- mvn clean install -Ddocker.showLogs -Pdocker -Pjacoco -Pit -Pcoverage coveralls:report | ||
after_success: | ||
- mvn deploy -DskipTests --settings .travis.settings.xml |
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.
we need snapshots deployed too on each build, in order to allow testing in demo projects to discover potential bugs before release
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.
Can we just keep deploying the snapshot there?
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.
Currently I have made the changes to retain old behaviour and on tagged commit the auto signing will be performed for deploy.
So the current behavior will retain and on tagged build the deploy will be performed by signed jars
.travis.yml
Outdated
- mvn deploy -DskipTests -Prelease -Ppassphrase --settings .travis.settings.xml | ||
on: | ||
tags: true | ||
all_branches: true |
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.
is it better to limit release to tag on master only?
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.
okay, I will update it
No description provided.