Hi Community,
Hope you guys are doing well :).
I have created a bitbucket-pipelines.yml file and merged it to the main branch of our repository, however the pipeline setting can not detect my yml pipeline and keep require create a new pipeline from the template sample.
Is there any body also counter this problem and figured out the solution for this?
I would be grateful for any tips or helps over here.
Hi @thanhle97 and welcome to the community!
If I understand correctly, the bitbucket-pipelines.yml file was initially created in a branch other than the main one?
Can you please try the following steps:
Please feel free to let me know how it goes and if you have any questions!
Kind regards,
Theodora
Hi @Theodora Boudale ,
Thank you very much for the details in solution. I have following and resolve the issue. Also, the pipeline not triggered due to I was missing indent in my YAML file.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This isnt working for me.
I've toggled the setting multiple times to no avail.
If i go to a specific commit and click run pipeline there, a popup appears with nothing in the drowdown, so i click "see configurations" which links to:
https://bitbucket.org/REDACTED/src/COMMIT_REF/bitbucket-pipelines.yml
but this shows an error. The file is definitely present at the linked commit ref.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Stephen Breakey ,
I would like to ask if you could please create a new question via https://community.atlassian.com/t5/forums/postpage/board-id/bitbucket-questions and we will look into your issue.
It's best to have a separate question for an issue you would like us to troubleshoot, especially when the root cause seems to be different, as a question can become convoluted and difficult to follow if we try to troubleshoot multiple users' issues.
When you create a new question, please provide screenshots of any errors and also the content of your bitbucket-pipelines.yml file. If you don't feel comfortable sharing this here, you can also create a ticket with the support team, which will be visible only to you and Atlassian staff. You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product.
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.
If someone's arrives here and is still blocked:
Check there is no space at the beginning of the bitbucket-pipelines.yml filename.
Easy to check in the url:
https://bitbucket.org/org/repo/src/master/%20bitbucket-pipelines.yml
Just in case...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If someone's arrives here and is still blocked:
Check there is no space at the beginning of the bitbucket-pipelines.yml filename.
Easy to check in the url:
https://bitbucket.org/org/repo/src/master/%20bitbucket-pipelines.yml
Just in case...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How difficult would it be for Atlassian to provide a more useful message in the bitbucket pipeline? Right now, a user:
Here's an alternative logic:
IF branch contains a bitbucket-pipelines.yml, and Enable Pipelines is FALSE, show message "It looks like you haven't enabled pipelines in your repository. To enable, go to repository settings, PIPELINES section, Settings, and Enable Pipelines"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark,
Thank you for the feedback. I understand that this behavior can be confusing to users.
I went ahead and created a request to improve it here:
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.
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.