-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REQUEST] Support for Bitbucket Commit Statuses #187
Comments
Hi! This looks like it would be a useful addition to the cloud build notifiers repository. It would be great if you could send over a PR once you have something workable! With regards to your question as to where the built-in notifiers are stored, once the PR is merged, we build the code and store the image internally in Artifact Registry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a proof of concept, I was able to use the bitbucket status API to push build statuses to my team's repository.
I'm curious whether this is replicable or useful enough to branch it out into it's own reusable notifier, like the HTTP or Slack notifiers in this repo. I've read the code enough to feel comfortable taking a first crack at it if it seems useful, though I'm not sure how / where the docker images are stored for the built-in notifiers.
The text was updated successfully, but these errors were encountered: