You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
This commit isn't pointing to an actual release. It's simply saying "things have changed and the next release will have a more significant version number."
Releasing does the following things: build master -> tag -> push to forge -> bump version -> push to github. As you can see the version number that sits in master will always be the next, yet to be released version.
That said, as soon as I get a chance to run the acceptance tests for all the targeted Operating systems, I'll release it.
The reason will be displayed to describe this comment to others. Learn more.
Can you run the acceptance tests in travis-ci?
I have seen a few blog posts about running beaker tests in travis.
This is a bit old but it seems that it's possible: https://www.camptocamp.com/en/actualite/puppet-acceptance-testing-travis-ci/
From memory they switched to using docker after that article was written so you will probably have to turn off docker so you can run the tests in docker containers.
I am pretty sure I have seen other run their beaker tests in travis so it should be possible.
The reason will be displayed to describe this comment to others. Learn more.
@mbrodala No problem. The reason I like to bump the version immediately after release is so that one can differentiate between the latest release and upstream.
@rendhalver I didn't know travis could run beaker tests, I'd never really looked into it. That would be ideal. I'll create an issue for it.
ac64bc8
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 you add a tag for this commit? :-)
ac64bc8
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 commit isn't pointing to an actual release. It's simply saying "things have changed and the next release will have a more significant version number."
Releasing does the following things: build master -> tag -> push to forge -> bump version -> push to github. As you can see the version number that sits in master will always be the next, yet to be released version.
That said, as soon as I get a chance to run the acceptance tests for all the targeted Operating systems, I'll release it.
ac64bc8
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 for explaining. I'm just too used to bumping versions only on release. ;-)
ac64bc8
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 you run the acceptance tests in travis-ci?
I have seen a few blog posts about running beaker tests in travis.
This is a bit old but it seems that it's possible: https://www.camptocamp.com/en/actualite/puppet-acceptance-testing-travis-ci/
From memory they switched to using docker after that article was written so you will probably have to turn off docker so you can run the tests in docker containers.
I am pretty sure I have seen other run their beaker tests in travis so it should be possible.
ac64bc8
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.
@mbrodala No problem. The reason I like to bump the version immediately after release is so that one can differentiate between the latest release and upstream.
@rendhalver I didn't know travis could run beaker tests, I'd never really looked into it. That would be ideal. I'll create an issue for it.
ac64bc8
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.
I will see if I can help get that working.