I'm using bitbucket pipelines to trigger my automated test run in AWS device farm, the problem here is bitbucket pipelines has a timeout of 120 minutes, and sometimes my test suite takes longer than 120 minutes to finish and the pipeline fails. So in this case, I want to update the pipeline status through API (if any available).
Honestly, per the *pipeline* itself 120 minutes is the hard limit, don't waste your build minutes per a pipeline just to wait for longer than 2 hours (or relatively below) - actually don't waste build minutes just for *waiting* - srsly?
As an alternative: Why not have the pipeline just trigger the otherwise truly remote build on AWS device farm and then let the AWS device farm update the build status via the REST API?
The build will be yellow until updated and there are no Atlassian Bitbucket Cloud Pipelines Plugin build minutes be counted for running your own infrastructure.
Principle here is to confirm a true commit as this is the anchor to verify to, if you really insist to temporary builds, e.g. a pull-request pipeline (which does not satisfy any quality gate at all by design), commit and (force) push a temporary commit (indirection) and build on that commit. Just saying in case you're running into an x/y problem here.
Hello friends! From the community that brought you Welcome Wednesday, Throwback Thursday and Friday Fun, welcome to Taco Tuesday, a weekly discussion about all things Trello. The best part? One Tac...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events