I was looking for the variable settings in our bitbucket-pipelines.yml file and some how it all went wrong and configuration disappeared. It appears I some how over wrote the bitbucket-pipelines.yml file in the master branch. The production configuration is gone. How do I do a revert or get the configuration back with the variables? Please help, I am having a heart attack over this.
Hi @Florian Lungu ,
Was the previous version of the bitbucket-pipelines.yml file committed in the repo?
Based on your description, I assume that the issue occurred while editing the file online? So, you didn't force push any changes?
Assuming that the previous version was already committed in the repo, and no one force pushed any changes that would make previous commits get lost, you should be able to find the previous version in the history of the file.
If you select the commit 036ddff right above the file in your screenshot, can you see a list with previous commits? Selecting one of the those commits should give you previously committed versions of the file.
@Theodora Boudale thank you. We were able to sort it out by doing a copy paste from the previous file, commiting the change to master, and running a pull request. Fortunately all the variables named in the bitbucket-pipelines.yml are stored as Repository Variables so they were not deleted.
I still have no idea how this happened. The situation prevented the organization from pushing code to any environment. Our Deployments webpage still does not look like it used to but the organization can do code pushes again so we are all set.
Hi everyone, We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events