Thanks for raising this, Eduard. Due to some recent infrastructure changes, Pipelines is now running your
~/.bashrc file (or similar) in non-interactive mode. For a small number of customers this prevents proper initialisation of the build container. In your case, it may have prevented
$PATH being set correctly and caused this error.
Here's the issue where we're tracking this problem: https://bitbucket.org/site/master/issues/13844/bitbucket-pipelines-command-not-found
We're in the process of rolling out a fix for this now, so you should see your pipelines going green again shortly. Apologies for the inconvenience.
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
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