Script

Can a script be a python code?

How do I reference my Bamboo variables in bash? It doesn't like the dot in bamboo.variable

How can I let a script (exit code?) tell bamboo to fail the build?

I can't seem to get any of the bamboo run-time variables to work with my shell script. I'm specifically trying to use bamboo.build.working.directory. Trying to just echo the value from the script (bash script on centos linux):

echo ${bamboo_build_working_directory}
echo ${BAMBOO_BUILD_WORKING_DIRECTORY}
echo $BAMBOO_BUILD_WORKING_DIRECTORY

all of these return blank lines. 

I also tried setting up a plan variable that points to ${bamboo.build.working.directory} and then using that plan variable in the shell script. It returns the string ${bamboo.build.working.directory}.

> How can I let a script tell bamboo to fail the build? 

return a none-zero

> then how could i set a custom build failure info?

This is weird. For a Windows agent I defined CScript as a custom executable so that I can run a VBScript using Windows Scripting Host. I have a few named arguments that I quoted to pass to CScript, e.g., /sign /dryrun.

Bamboo insists on changing the forward slashes to backslashes. How is that useful? My script won't run because it doesn't understand the arguments being fed to it.

Is there anyway to force a TTY on the script? I'm trying to use sudo to install a couple of packages (e.g. "sudo apt-get install foo").

Is my impression that this page states that Bamboo will run inline-scripts with bash on Unix and with cmd.exe on Windows and there is no way to change this for inline-scripts? Jenkins allows you to specify the interpreter using the shebang line, allowing you to run the scripts with almost anything.

What's the advantage of using a script file as described here than using a .bat file registered as executable?

Well, inline scripts are handy because you can expose the build them to users (and thus let them control some of the build/deployment process) without giving them write access to your source code repository (if you are storing your build scripts in source control) or the build server itself (if you're relying on scripts/batch files in the system path). 

Conversely, if you control access to the inline script in Bamboo, you can hide the server-level stuff (like hard-coded credentials) from source control where many people perhaps have at least read access, and keep source control for source, not for deployment batch files used by DevOps/et al. 

-Kelly

Hi,

Can the script be a PERL script?

Thanks,

It can be anything you want, as long as you recognize it will be executed by /bin/sh. (on a linux box, for instance). Adjust your bits accordingly; for instance, as an inline script you could do this (I assume):

python path/to/the/script.py

Or if you have #!/usr/bin/python at the top of your script, and it's executable, you could just do an inline script like:

./path/to/the/script.py

If you're wondering if you can paste a python script into the inline script editor and get Bamboo to use python to run it - I don't think their custom builder (such as specifying /bin/bash, or /usr/bin/python) allows inline scripting yet, so that's a no. That would be a nice feature to have though. 

This shouldn't be a "Bamboo vs Jenkins" thread - they are different products, with different audiences. Bamboo is a build & deployment orchestrator & integrator. Jenkins is a development tool. While they share many features and uses on a venn diagram, they aren't the same circle. 

If you're struggling with Bamboo vs Jenkins, then maybe you need to understand your needs a little better; it shouldn't be a fight and you should use the product that fits your needs best, not spend your time & energy forcing a round peg into a square hole. 

-Kelly

Hi,

using the inline scripts - users are able to rename the files in bamboo_home?  how can we prevent this from happening

How can I get Bamboo to run a script on Win2k8r2 in 32 bit mode? I need it to remap the paths to Program files, etc just as a script run by the 32 bit version of cmd.exe on a 64 bit OS would.

Add an executable task instead of the script task. pass in your powershell that way. Set it up in admin using 32 bit.

I'm confused, from a script task that calls the OS's shell, be it cmd.exe on Windows or bash on Linux, just get that to call you Python, Groovy, Ruby, whatever the heck you want.  I think you can get what you need with just that. Parameters can be based to the shell script via the command line and/or environment variables.  Yeah, inline Python scripts might be nice, but you can just have the shell call that in a script.  I guess with Windows, you can call a PowerShell script directly.  I am new to Bamboo, what I would like to learn is how to have a shell script return values back to Bamboo for conditional logic.  With Jenkins, the script can write out to a Java properties file and the values read by in via the EnvInject plugin.

I have a simple in-line script:

rm -rf /scratch/target-dir
cp -rv src/target-dir /scratch
chmod -R 777 /scratch/target-dir
rm -rf /scratch/some-app
cp -rv src/some-app /scratch

It gets to the last line, executes the command, and causes the agent to crash.  I don't believe there is anything wrong with the script, is there ?

Why does Bamboo have to prefix all environment variables with "bamboo_" ?   If I have a plan variable called FOO_BAR, I want it passed to the shell as an environment variable called FOO_BAR not bamboo_FOO_BAR.  I now have to go through and edit about 117 files and change them to use bamboo_*.  No other build system does that.

I can understand converting to upper case and replacing "." with "_", but actually adding a prefix that was not specified does not seem right at all.  It causes vendor lock-in.  If I at some later point want to switch to something else, I have to make changes to scripts that I should never have had to change in the first place.

Hi,

We have a deployment script we run on our server that does the following:

1. Checks out the repo in a separate folder
2. Runs rsync --dry-run with live site files and shows files that will be changed
3. Requires a deploy y/n response

Is it at all possible to implement this command with Bamboo so that we could see what the deployment will do exactly from the Bamboo interface and then give the go ahead?

Bamboo runs its tasks in a non-interactive window, so on the face of it, no. 

You could make some kludge where it could write the results to a DB and twiddle its electronic thumbs while you decide yay or nay, periodically checking for a yay (or nay). 

Or, break this up into multiple stages and put an approval process in between the stages. 

Can my script leave behind environment variables for the next tasks?

Each script task will run in its own process space, so when the task ends, that process space is destroyed as are its child processes.   When that happens, the environment of the process, and the script, is destroyed as well.

What you could do, is probably write out the environment, as one of the last things you do before the end of the task, to a file in some common location, that subsequent tasks can access, modify, etc.  as needed.

Hope that helps.

I'm trying to use script to generate a variable which contains a git log, which i can acces as a variable in a subsequent task, the log contains multiple lines,

git log --no-merges --pretty=format:"* %s" ${bamboo.repository.previous.revision.number}..${bamboo.repository.revision.number}>changelog.txt

I'm successfully able to write this out to a file but am having issues trying to access it in the inject variables plugin, is there a simpler way to do this by using the script to set a variable?

Please help.  I am running a .bat file using the onDemand version on Bamboo against a windows EC2 machine.  The batch file is clearly being executed by the "bamboo" user.  To run this batch file requires admin privileges.  How can I run my batch file as an admin user automatically? 

Am I being blocked by this bug?  BAM-14097 - Getting issue details... STATUS

This REALLY needs to talk about exit values/return codes.  I came here looking for this, and there is not a single mention of this, which for a build system is pretty fundamental.

i get

command	16-Apr-2014 17:31:17	Beginning to execute external process for build 'Scanity - Build Scanity - Build ext #17 (SCAN-SCAN-BE-17)'\n ... running command line: \n/bin/sh /tmp/SCAN-SCAN-BE-17-ScriptBuildTask-7101257030486225774.sh\n ... in: /root/bamboo-agent-home/xml-data/build-dir/SCAN-SCAN-BE/ext\n
simple	16-Apr-2014 17:31:17	Failing task since return code of [/bin/sh /tmp/SCAN-SCAN-BE-17-ScriptBuildTask-7101257030486225774.sh] was -1 while expected 0

so i'm simply unable to execute a "Hello World" echo script contains: echo "Hello World"