I am clicking to pipelines button and try to setup a new one. it says
Looks like you already have a bitbucket-pipelines.yml file in this repository
When I click review pipeline, I got an error:
Resource not found.
Actually resource is not there. I dont have bitbucket-pipelines.yml file in repository. I cannot create a new one from templates because I dont know howto setup one.
Please help
Hi Alp and welcome to the community!
I was able to reproduce this behavior in a repo where Pipelines had never been enabled. This looks like a bug and I created a bug report in our issue tracker:
I have posted steps to enable Pipelines and configure a bitbucket-pipelines.yml file in the Workaround section of the bug report, I am quoting also here:
Currently there is no workaround for showing the templates.
The following steps can be used to enable Pipelines and create a bitbucket-pipelines.yml file:
- On Bitbucket's website, open the repository
- Select Repository settings from the left sidebar
- Select Settings under the section titled Pipelines from the new left sidebar
- On the new page, select the toggle to enable Pipelines
Afterwards, the bitbucket-pipelines.yml can be created either locally or via the website.
Locally, a user can create it in a clone of the repo, commit it, and then push the commit to Bitbucket.
From the website, a user can create it from the Source page of the repo > select the 3 dots menu (near the top right corner) > select Add file.
The following documentation page can be used as a reference for the content of the bitbucket-pipelines.yml file:
The page I shared in the Workaround has links to other pages with more details on several Pipelines options.
If you plan to use Pipelines on Atlassian's infrastructure, the builds run in Docker containers based on the image specified in the bitbucket-pipelines.yml. I suggest paying attention to the page Docker image option, as the image you choose will determine your build environment and what command line tools will be available during the build.
The page Pipelines start conditions has more info on setting the triggers for your builds, while the page Step options has details on configuration options for your pipeline steps.
The commands added to each step's script are Linux commands or commands from CLI tools that are pre-installed in the Docker image. It is always possible to install additional tools during the build, by adding the necessary commands in the yml file's script.
Please feel free to reach out if you have any questions!
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.