I have one site, two engineers, playground, a half QA engineer (me) slash PM and the need to coordinate tasks between all of us.
Right now JIRA's kanban looks something like this:
need to do | in progress | in testing | accepted
We want: when some of tasks are done, a new version of site is creating and uploading automatically.
Problem is I haven't worked with pipelines yet.
I wonder what is the best condition when new version are sending to pipe.
1) When ALL tested tasks goes to "accepted"?
But what if some tasks is super important and needed to upload immediatly, and some are still testing?
2) When created new column, something like "to upload" with checkbox. I choose which tasks and when will go to new version.
I don't like it, because manual sucks.
How you guys manage your projects with such questions? Couldn't find any advices :(
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs