Bamboo Documentation

   Bamboo 5.0.x
   Bamboo 4.4.x
   Bamboo 4.3.x
   Bamboo 4.2.x  
   More...   

 

Bamboo Knowledge Base Resources

Know a good Support Engineer?
Atlassian is hiring! Refer-a-Mate to earn $2000.

Skip to end of metadata
Go to start of metadata

Builds in Bamboo are exactly the same as how they would be executed via command line.

Bamboo Build Process

Bamboo forks off a new process for each build, and tries to reproduce the user's environment by passing down all the System and PATH variables to the build.

The new process is created using the Apache Ant Execute Task as below:

 For the more curious, Bamboo uses Apache Ant Execute Task to fork the build process.
AbstractBuilder.java

Debugging Failing Builds

If you haven't done so already, please run your build outside of Bamboo via command line as the user running the Bamboo process and confirm that build is successful.

Navigate to your local working directory BAMBOO_HOME/xml-data/build-dir/PLAN_KEY and try executing your build manually.

For E.g, if this is a Maven build then please supply the appropriate goal: mvn clean install

Please ensure that the following criteria have been met:

  • Ensure that Bamboo is running as the local user and the user executing the build via commandline owns the Bamboo process.

    Bamboo Service on Windows

    Icon

    Bamboo will install itself as the SYSTEM user on Windows, ensure that you have configured Bamboo to run as the local Windows user

  • If the failing build is being executed on a remote agent, ensure that it can be executed successfully on the remote agent as the Bamboo user.
  • If your build has specific dependencies or requires you to set Environment Variables, ensure that the variables/dependencies are available to your build.
  • If your JAVA build is failing due to memory errors, then please try increasing memory allocated to your build.
Page: Bamboo Fails to Run a Build as the Build Number Already Exists Page: Build expiry fails when excluding builds with labels Page: Bamboo 2.7 Stages are not passing artifacts to next Stage Page: Error 'Can't connect to X11 window server' is reported during Server Startup Page: Grails builder always append "-non-interactive" to commands Page: Script task unable to run file in Windows Page: Build expiry fails Page: Build fails in Windows - The system cannot find the path specified Page: Visual Studio task fails when running Bamboo as a Windows service Page: Grails build fails - StackOverflowError Page: TestNG parser problem Page: Unsupported JDK`s can cause builds to stay put in an incomplete state due to problem with log parsing Page: Script task body is empty due to corrupted file system Page: Bamboo does not pick up the Path environment variable correctly Page: Maven build fails due to NullPointerException Page: java.lang.IllegalArgumentException : mstest.exe cannot be found Page: JUnit Parser: Test results are not found Page: Windows build artifacts are not copied Page: SCP Task fails to copy all artifacts Page: Bamboo Builds are randomly failing - it was marked as queued but was not present in the queue Page: Bamboo Build Fails to Run - duplicate key value violates unique constraint Page: ASPNETCOMPILER : error ASPRUNTIME: The specified path, file name, or both are too long Page: Grails task fails in Bamboo build - OutOfMemoryError Page: Deploying artifacts to tomcat will sometimes fail on due to file locking Page: Build fails with repository exception: svn: E175002: No space left on device Page: JUnit Parser - Too many levels of symbolic links Page: Build expiry is not working correctly for artifacts Page: Wrong settings of the user language and locale causes build logs to be shown with a default time 01-Jan-1970 01:00:00 Page: Bamboo hangs when uploading artifacts from elastic agents Page: Bad Substitution in nested variables