Pipelines failed all the times.
/opt/atlassian/pipelines/agent/tmp/bashScript5488901748017688290.sh: line 12: grails: command not found
Could you help us, please?
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.
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.