Open arm4b opened 8 years ago
^^ @enykeev @dennybaa @lakshmi-kannan please review the logic and provide your ideas if you have.
That'll be better automated after merging:
https://github.com/StackStorm/st2-packages/pull/227
https://github.com/StackStorm/st2-packages/pull/229
https://github.com/StackStorm/st2/pull/2569
https://github.com/StackStorm/st2/pull/2570
opening PR against any other branch of st2-packages repo will use st2 master code (fallback)
Not really. As of https://github.com/StackStorm/st2-packages/commit/86a4a43dec0db8d8815ab1cfdd226dab26bdb6dc, it depends on the point you're branching from. Any commit that branches after 86a4a43dec0db8d8815ab1cfdd226dab26bdb6dc will use 1.3 branch of st2.
@enykeev see: https://github.com/StackStorm/st2-packages/pull/227 PR.
As discussed with @enykeev, closing #227 branch autodetection as error-prone way.
ST2_GITREV
hardcoding in each branch of st2-packages
will work.
I guess we'll end up with hardcoding in st2
repo as well later, once we enable PR statuses there, if Circle won't add builds on Opened PRs
st2-packages
repo now followsst2
branching strategy. What it means.The Logic:
st2-packages
repo:master
ofst2-packages
repo will generate packages based onmaster
ofst2
v1.3
ofst2-packages
repo will generate packages based onv1.3
ofst2
master
branch ofst2-packages
repo will usest2
master
codev1.3
branch ofst2-packages
repo will usest2
v1.3
codest2-packages
repo will useST2_GITREV
hardcoded version incircle.yml
st2
repo:master
ofst2
repo will generate packages based onmaster
ofst2-packages
v1.3
ofst2
repo will generate packages based onv1.3
ofst2-packages
st2
repo yetRebuild the Package Manually:
Normally pushing to
v1.3
branch for anyst2
orst2-packages
repos will generate and deployv1.3
staging packages. Usually that's enough, but if you want to do that manually without pushing changes, just use CircleCI rebuild:v1.3
branch builds https://circleci.com/gh/StackStorm/st2-packages/tree/v1.3Rebuild