No don't I have a use case for it, other than potentially running two build systems on different forks (potentially one of the build systems would be under test). However, I think can be accomplished by having different keys in the POST. The only issue would be cluttering up a production repo with status updates from a non production build system. I don't think this is a real issue. Thanks again for your help.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot