Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Pipelines not working

Eduard Fumas
Eduard Fumas
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
February 13, 2017

Pipelines failed all the times. 

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

Could you help us, please?

Answer
Watch
Like Matt Ryall likes this
1407 views

1 answer

0 votes
Matt Ryall
Matt Ryall
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 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.

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

    See all events