Philip Hodder Atlassian Team

Hi Patrick, The repo status shown there is based off the latest build on the "main branch" of your repo (in this case, likely your master branch). You can update the status shown by running a pipeline that finishes successfully. You can also change your "main branch" in the Repository settings -> Repository details -> Main…

Hello, Right now there isn't an option in the YAML to skip steps. You could try marking the step as 'manual' if it's always going to be the last step, and just require it to be manually triggered. Or you'll need to add your conditions to the start of the step. You can then just use 'exit 0' to finish the step early with a…

Hi Daniel, Can you give me an example of the tag that you're trying to match against? Thanks, Phil

Hello, Pipelines does not currently expose the previous git revision built. You can get some of this information manually via the Pipelines REST API: https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/pipelines/#get It'll need a little bit of fiddling to get the…

Hi Michael, Currently, Pipelines does not support exclude patterns. You'll need to use inclusive rules, or do an additional check at the start of the pipeline execution. You can open a feature request to add exclusion path support here: https://jira.atlassian.com/secure/CreateIssue!default.jspa Thanks, Phil

Hello Dan, Yes it does! You can use the Deployments feature to visualise and track your deployments. It also enables you to use a few other features, such as Deployment Permissions. Thanks, Phil

Hello Oliver, You can trigger a pipeline via the REST API here: https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/pipelines/ You can also configure scheduled pipelines in the UI directly, if you…

Hi Olof, Is this still happening to you? I just tested this out and it seems to work fine for me: https://api.bitbucket.org/2.0/repositories/phodder/prod-test/environments/ { category: { name: "Production" }, restrictions: { admin_only: false, type: "deployment_restrictions_configuration" }, uuid:…

Hi Solomon, At the moment there is no built-in support for having these types of conditions on steps being triggered. We an open feature request for triggering pipelines after certain files change. Which you can follow. You can also open a new feature request here: https://jira.atlassian.com/secure/CreateIssue!default.jspa…

No I don't have permission to see private pipelines. Can you open a support ticket here with details of your issue. They'll have permission to view private pipelines: https://support.atlassian.com/contact

Hello, This Pipeline should only run under the following two conditions * There is a new commit pushed to either the 'master' or 'stage' branch. * The 'master' or 'stage' has the bitbucket-pipelines.yml file on it. Thanks, Phil

Hello, You only have one step in your pipeline, so the option to "Rerun failed steps" doesn't show. As it's effectively the same as rerunning the pipeline. Is there a reason you'd like to rerun the step specifically, rather than just rerunning the pipeline? This should have the same effect. Thanks, Phil

Hello, You will need to create your own custom Docker image which extends nginx and includes your desired nginx.conf file to use as a service container. As Pipelines currently does not have a feature to mount files into service containers. If you'd like, you can open a feature request for that…

Hello, There is already caching occurring with pulled Docker images. We have a Docker registry proxying Dockerhub which speeds up download times of images. However, the Docker client will still need to pull images from that Docker registry. Are you finding the download times to be excessively long? Thanks, Phil

Hello, This is correct. The bitbucket-pipelines.yml file must be in the specified branch in order for it to be run. The expectation is that branches remain (roughly) in sync. Such as with a feature branching workflow. What is your branch workflow out of curiosity? Is there a reason you can't keep your branches in sync…

Hello, Is this problem still occurring? It's possible there may have been a temporary issue with the Docker image itself. Thanks, Philip

Hi Ming, This looks like it could be a bug. Can you open a ticket with the following information: * The XML you have pasted here. * The full directory path to the XML file. * The name of the XML file. Thanks, Philip

Hi Jonas, It's currently only possible to create a scheduled pipeline via the web UI. If you're interested in this as a feature, feel free to open a feature request here: https://jira.atlassian.com/projects/BCLOUD/issues/ Thanks, Phil

Hi, A Pipeline is marked as success or failed based on the exit code of all the commands set. So if your command has the exit code 0, we will still mark that as successful. Most tools will return a non-zero exit code when a test fails. Perhaps you can configure your tool to have a different exit code. The test output shown…

@Rafael Chebel we've released these to the public API now: https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/deployments_config/environments/%7Benvironment_uuid%7D/variables Our internal endpoints do not have a deprecation policy. So please move to the official…

Hello, We've added endpoints for interacting with deployment variables to our public API. You can find the documentation for them here: https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/deployments_config/environments/%7Benvironment_uuid%7D/variables Thanks, Phil

These endpoints have been added to the V2 API: https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/deployments_config/environments/%7Benvironment_uuid%7D/variables As our internal APIs do not have a deprecation policy. I suggest you migrate to the 2.0 API as soon…

Hello, With Docker, you have two options for adding these environment variables. * Build and deploy the separate Docker images with the different environment variables. * Or create a single Dockerfile without the variable defined (or an empty value). And then pass in the environment specific variable at container startup…

Hello, This looks like it's not a permission issue, but a parsing issue. Can you try running the same code, with the same configuration, locally? Thanks, Phil

Hi Mark, Currently Pipeline has no native way to populate environment variables from external key management solutions. You can open a feature request for those types of integrations here: https://bitbucket.org/site/master/issues/new For now, you would have to start your build script by retrieving the variables from the…

Hello, My initial suspicion is that the database is still starting up in the builds that fail. You can look at the logs in mysql tab of the build logs to see if it finished starting up. The quickest way to work around this issue is to add a sleep to the build. However, there may be more effective ways to work around this…

Hello, The folder size of an artifact is 1GB. Which seems to be a lot larger than the output of your local folder. My initial suspicion is that the 'dist' folder is not being created in Pipelines. Can you add a `ls -aRl .nuxt` command to the end of your script and see if the folder is being created. Thanks, Phil

Hello Prashant, Currently, Bitbucket Pipelines does not have an option to run builds on a GPU. You can open a feature request to add support for that here: https://bitbucket.org/site/master/issues/new The closest workaround I can think of would be to have your Pipelines trigger GPU-related tests to run on a cloud provider…

Hello Oleksandr, Currently you cannot disable the test reporting feature. The closest workaround would be to remove the files before the build finishes, which will make the parser not find any files to parse. Can you open a feature request with some more details about the size of your stack trave…

Hi Tanju, I'm glad that you enjoyed my article! So this is a bit awkward... 🤭 I went through the documentation to try find information and also couldn't find any details. So I asked some team mates, and it turns out it was a 20% project that one of the engineers (who has now left Atlassian) had worked on. This feature was…