Skip to content

Conversation

asifdxtreme
Copy link
Member

No description provided.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 86.467% when pulling 98213fc on asifdxtreme:master into bbf3f8f on ServiceComb:master.

<id>release</id>
<build>
<plugins>
<plugin>
Copy link
Member

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?

Copy link
Member Author

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

<password>${env.SONATYPE_PASSWORD}</password>
</server>
</servers>
<profiles>
Copy link
Contributor

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

Copy link
Member Author

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

@coveralls
Copy link

Coverage Status

Coverage remained the same at 86.467% when pulling c804648 on asifdxtreme:master into bbf3f8f on ServiceComb:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 86.467% when pulling c804648 on asifdxtreme:master into bbf3f8f on ServiceComb:master.

.travis.yml Outdated
- mvn deploy -DskipTests -Prelease -Ppassphrase --settings .travis.settings.xml
on:
tags: true
all_branches: true
Copy link
Member

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?

Copy link
Member Author

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
Copy link
Member

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

Copy link
Member

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?

Copy link
Member Author

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.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.006%) to 86.473% when pulling 169b8e0 on asifdxtreme:master into bbf3f8f on ServiceComb:master.

So the current behavior will retain and on tagged build the deploy will be performed by signed jars
@coveralls
Copy link

Coverage Status

Coverage increased (+0.006%) to 86.473% when pulling a701e0f on asifdxtreme:master into bbf3f8f on ServiceComb:master.

.travis.yml Outdated
- mvn deploy -DskipTests -Prelease -Ppassphrase --settings .travis.settings.xml
on:
tags: true
all_branches: true
Copy link
Member

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?

Copy link
Member Author

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

@coveralls
Copy link

Coverage Status

Coverage increased (+0.006%) to 86.473% when pulling 57a0928 on asifdxtreme:master into bbf3f8f on ServiceComb:master.

@seanyinx seanyinx merged commit c22128f into apache:master Oct 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants