I tried with Opera and Chrome, both browsers are constantly updated.
I go into the repository, click the "Pipelines" section, but the "content panel" is blank.
Screen Shot 2017-03-02 at 18.51.48.png
I tried from a colleague's account, gave him admin settings, but from his account the "Pipelines" button is not even visible.
As mentioned below, there is an issue where your clock being out of sync can cause Pipelines not to appear. I'm not 100% sure if that issue has been resolved, so please report back if that proves to be the problem.
If that isn't the problem, please raise a support ticket and one of our engineers can look into it for you.
My clock is not out of sync as I have NTP enabled.
The problem was also happening for several other people in remote locations.
What we did find is if we removed (or renamed) the bitbucket-pipelines.yml file then it fixed the problem. So here is the scenario:
1) Create a new repo and add a bitbucket-pipelines.yml file that references an environment variable that hasn't been defined.
2) Go to the pipeline tab to find it doesn't load.
3) Rename or delete the pipeline file and push.
4) Now you can access the pipeline tab.
Thanks for the reply, @Kevin Hale Boyes. I tried these steps in a new repo and couldn't reproduce it here.
Environment variables (defined or undefined) in the YAML file should have no impact on whether or not Pipelines loads, so we'll need some more information to investigate this (e.g. browser console output, account+repo names). The existing YAML file could hit some unexpected edge cases, but it does seem to be working for me.
If you have some time to help us get to the bottom of it, it would really help if you could raise a brief support ticket mentioning this post, then we can identify your specific repo and browser, get the necessary diagnostics, and work out what exactly is going on. Thanks!
If I go to this public page:
I can see the pipeline section. The iframe loads after some seconds. However this does not happen on my account's repositories.
Same happening to me. Tried with Chrome, Firefox and IE. Cleared cache, cookies and everything. Synchronized clock.
Apparently, the bug comes from file connect-host.js
The contentPromise callback is expecting the returned data to be a JSON, however it is getting a HTML document indicating the addon Pipelines has failed:
I see this question as resolved, should I create a new one?
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs