The developers I work with don't want to go the Web GUI every time they need deploy to an environment. They want to do it from the command line/terminal on their machine.
I see no documented way of doing this.
Is there a way to do this yet? Can this be added as a feature?
If not, would also be nice to have a way for us to add deployment auditing via the API...
Thank you so much @davina!! Didn't know if I'd ever get a reply to this one. Any help on my other unanswered questions would greatly appreciated!
https://community.atlassian.com/t5/user/viewprofilepage/user-id/1141533
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @davina when I try requests as specified in the link you provided I receive the cryptic response:
{
"type": "error",
"error": {
"message": "workspace"
}
}
Can you provide any insight? I can't find any information on this error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've seen this error before when there are typos in your account or repo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@davina turns out is was text case in our repo and pipeline names. Pipeline api behavior with case is different then rest of the API.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would also be interested in ways to trigger pipelines from an API call.
It would also be great to install a webhook that would be notified when the pipeline completes and then have access to artifacts from the build.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I made a Node.js package that has a cli helper to trigger pipelines (ie: downstream).
How I use it is by putting a JSON file in the my common utils repo which contains the repo name of each project that wants to have their pipeline triggered when this project's pipeline is complete. I then call the cli helper in the last step of the common utils repo pipeline and it kicks off a pipeline build for all listed repos in the JSON file.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is cool! Any plans to extend it to also be able to run a specific pipeline in a repo?
We have a separate repo that is only infra stuff, so there are separate pipelines for running various ansible scripts. One for setting up infrastructure, one for deploying lambdas, one for deploying out backend...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@rcole That would be a great idea! That actually is new to me, I wasn't aware a repo could have separate "pipelines" besides a pipeline per branch. The docs are a little lacking for pieplines stuff but I'd be really curious to know if you have any additional info that I haven't seen on the topic.
What I'm currently doing is triggering pipelines per branch with a config file ie:
const pipelineTriggers = [
{ "branch": "master", "workspace": "teamOrUser", "repo_slug": "repoName" },
{ "branch": "staging", "workspace": "teamOrUser", "repo_slug": "repoName" }
]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Cory Robinson it would be useful if you extended your tool for custom pipelines indeed. You can find examples here (Trigger a custom pipeline with variables):
https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/pipelines/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.