Does bamboo stores copy of scripts? Script History?

[Alberto Pineda]

I made multiple improvements and changes to the deployment power-shell script.

If I wanted to see what changes I made, or if I break the script I would like to have a place to see the history of the scripts created/updated in bamboo for a deployment?

[Alexey Chystoprudov · Accepted solution]

There's another way to keep script code in repo and don't use Bamboo Specs.

Just checkout repo with script as part of your build/deployment and then script task call it from file. This way your team don't forget to modify script code as it will be stored at single place

[Alberto Pineda]

I ended up using this approach, it was a bit annoying that had to pass all the bamboo variables that I needed via Environment Variables

[Milos Zikmund (MoroSystems)]

Hi Alberto,

this isn't exact answer for your question but take a look to Bamboo specs here https://confluence.atlassian.com/bamboo/bamboo-specs-894743906.html. It's a way how to configure your Bamboo builds as a code so you can have it as part of your app in source control.

Greetings,

M.

[Alberto Pineda]

Thanks for the quick responses (To everyone), I created a ticket to review this alternative in a few weeks.

[Alberto Pineda]

I didn't see a way, so I'm storing a copy of the scripts in source control. But I fear that me or other team members will forget to update the source control files.

[Jimmy Seddon]

Hi @Alberto Pineda,

As @Milos Zikmund (MoroSystems) has mentioned if you enable repository scanned Bamboo Specs.  More information here: https://confluence.atlassian.com/bamboo/enabling-repository-stored-bamboo-specs-938641941.html

That will force you to use the version stored in source control to make changes so you will never have to worry about forgetting to update source control, it also gives you a 100% versioned copy of your configuration so you know what has been changed.

I hope that helps!

-Jimmy