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

Initial CI Build Refactor #962

Merged
merged 1 commit into from
May 11, 2019
Merged

Initial CI Build Refactor #962

merged 1 commit into from
May 11, 2019

Conversation

kdavisk6
Copy link
Member

@kdavisk6 kdavisk6 commented May 9, 2019

Fixes: #963

Simplified the travis configuration back to it's minimal form to create
a new starting point.

  • Adding Explicit Deploy stage
  • Updating documentation and adding tagging to the release script
  • Adding tag configuration to pom
  • Configured Travis to Skip the commits created when preparing the release
  • Adding Git Credentials
  • Added Sync Stage during releases

Simplified the `travis` configuration back to it's minimal form to create
a new starting point.

* Adding Explicit Deploy stage
* Updating documentation and adding tagging to the release script
* Adding tag configuration to pom
* Configured Travis to Skip the commits created when preparing the release
* Adding Git Credentials
* Added Sync Stage during releases
@kdavisk6 kdavisk6 requested a review from velo May 9, 2019 14:27
@kdavisk6 kdavisk6 added the chore For issues related to technical debt and other non-functional tasks label May 9, 2019
@kdavisk6 kdavisk6 added this to the 10.2.1 milestone May 9, 2019
Copy link
Member

@velo velo left a comment

Choose a reason for hiding this comment

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

I like it, FWIW, later we can clone the feign-forms approach that uses some travis deployment support

@@ -129,6 +131,11 @@
<email>velo br at gmail dot com</email>
<url>about.me/velo</url>
</developer>
<developer>
Copy link
Member

Choose a reason for hiding this comment

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

🥇

@kdavisk6
Copy link
Member Author

@velo

I think that makes a lot of sense. I was thinking about doing the same thing, adding a GitHub release stage. I'll create a new issue for that.

@kdavisk6 kdavisk6 merged commit aa57f59 into master May 11, 2019
@kdavisk6 kdavisk6 deleted the travis-ci-build-updates branch May 31, 2019 14:39
velo pushed a commit to velo/feign that referenced this pull request Jun 30, 2019
Simplified the `travis` configuration back to it's minimal form to create
a new starting point.

* Adding Explicit Deploy stage
* Updating documentation and adding tagging to the release script
* Adding tag configuration to pom
* Configured Travis to Skip the commits created when preparing the release
* Adding Git Credentials
* Added Sync Stage during releases
velo pushed a commit that referenced this pull request Oct 7, 2024
Simplified the `travis` configuration back to it's minimal form to create
a new starting point.

* Adding Explicit Deploy stage
* Updating documentation and adding tagging to the release script
* Adding tag configuration to pom
* Configured Travis to Skip the commits created when preparing the release
* Adding Git Credentials
* Added Sync Stage during releases
velo pushed a commit that referenced this pull request Oct 8, 2024
Simplified the `travis` configuration back to it's minimal form to create
a new starting point.

* Adding Explicit Deploy stage
* Updating documentation and adding tagging to the release script
* Adding tag configuration to pom
* Configured Travis to Skip the commits created when preparing the release
* Adding Git Credentials
* Added Sync Stage during releases
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore For issues related to technical debt and other non-functional tasks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improve Release Process with Travis
2 participants