Closed njchandu closed 3 years ago
Why do you need a second release branch? Why not to use the same branch? Or better yet same artifacts in staging and production?
Yes, that actually makes sense. Let me think about it. I will update this ticket in a day or two, thanks.
Hi @aleksandr-m, I agree with your thought process on not needing a second release branch. Would it be better to throw this error during a release:start instead of release:finish?
I am trying gitflow for the first time in our org. First pass was a super duper mess because of conflicts and not thinking the process through completely.
I'm trying to integrate it with CI. Could you please let me know if there are any fundamental issues with this approach.
There are 2 Jenkins jobs:
@njchandu
Would it be better to throw this error during a release:start instead of release:finish?
It is already there.
Hi,
I am trying to follow gitflow and ran into this issue. I'm trying to hold on to the release branches mainly because we mostly do canary deployment before deploying to all the instances and they are two different processes. First a canary deployment takes place, we monitor the metrics for 1 to 7 days depending on the feature and deploy to all the regions and hosts upon validation.
I got this error when I try
release-finish
What should I do in this case. Thanks in advance.