Pipelines not working

Pipelines failed all the times. 

/opt/atlassian/pipelines/agent/tmp/bashScript5488901748017688290.sh: line 12: grails: command not found

Could you help us, please?

1 answer

0 votes
Matt Ryall Atlassian Team Feb 13, 2017

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Thursday in Bitbucket Pipelines

Building a Bitbucket Pipe as a casual coder

...ipe.sh :  #!/bin/bash source "$(dirname "$0")/common.sh" enable_debug extra_args="" if [[ "${DEBUG}" == "true" ]]; then extra_args="--verbose" fi # mandatory variables R...

228 views 0 12
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you