You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: