If you're anything like any company in the world, you release to QA, then that build, when approved, can move to Stage. From there, another approval, and it moves to Prod. There is now a UI to Approve/Deny builds. What I really want from the deployment stuff is to only allow approved builds to advance to the next environment. So only builds marked as approved are an option in the version dropdown for Stage. Right now, however, you can create a whole new release and push it directly to Stage.
Is there some usage pattern I'm missing here? I would expect all the enterprise folks to throw a fit over this, but maybe this is why most people still suggest using regular plans for deployments?
Dustin - join the club https://jira.atlassian.com/browse/BAM-13266
Feel free to voice your displeasure to stimulate some activity on this front.
Yeah... This one seems to wrap up the actual workflow we all want: https://jira.atlassian.com/browse/BAM-13356
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Right you are, that is the over arching one for deployments workflow.
So anxiously waiting for these changes!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.