We need to force a deploy from our bitbucket repository to our server. We have two branches in BitBucket, a development branch and a master branch. Usually, we push to the develop branch first, which triggers shippable to do a build and deploy to our test website. We then check the test website to make sure everything is OK, and if it is, then we do a merge in BitBucket. We merge the develop branch to the master branch. This merge also triggers shippable to do a build and deploy to our production website.
This time, for some reason, shippable didn't deploy. We merged from develop to master, but the results of the merge on the master branch did not get pushed to the production website. We have verified that both the develop branch and master branch are synchronized and that they both have the latest code. Since we rely on the merge from develop to master to automatically trigger shippable, we don't have any way of deploying our website to production now (BitBucket won't do another merge if it detects the two branches are in sync).
How do we force shippable to do a build and deploy of the master branch?
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