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.

Sign up for GitHub

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

Jump to bottom

Automate releasing a version of Bastion #80

Open
KPull opened this issue Jan 15, 2017 · 0 comments
Open

Automate releasing a version of Bastion #80

KPull opened this issue Jan 15, 2017 · 0 comments
Labels
enhancement
Milestone
1.0

Comments

@KPull
Copy link
Member

KPull commented Jan 15, 2017

We currently do the following when releasing a new version of Bastion:

  • Merge the develop branch into master branch.
  • Set the POM file's version to the next release version number.
  • Run mvn deploy -Prelease.
  • Commit.
  • Tag the current commit on master for the version we're releasing.
  • Merge master into develop.
  • Set the POM file's version to the next SNAPSHOT version.
  • Commit.
  • Push master, develop and the new tag.

We need to automate/script this so that we can configure Travis to run the whole process by itself.
@KPull KPull added this to the 0.6-BETA milestone Jan 15, 2017
@KPull KPull modified the milestones: 0.6-BETA, 1.0 Mar 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
1 participant
@KPull