nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to input the Bamboo Build directory into script using Jenkins WORKSPACE variable?

Dale Binkley

We are migrating to Bamboo from Jenkins. We have ~10 projects using the same core scripts. I am creating a new build project using Bamboo rather than Jenkins as a proof of concept task. So as not to be too disruptive, I must use the scripts that were created for Jenkins.

In the pipeline one script calls another and uses the Jenkins $WORKSPACE variable- I need to translate the Jenkins variable to Bamboo build directory. I've created an artifact (WORKSPACE=${bamboo.build.working.directory}, export the variable (export WORKSPACE=${bamboo.build.working.directory} even added the argument and environment variable. But still unable to pass the variable.

Any suggestions?

Accepted answers

Dale Binkley

Thanks to Eduardo Alvarenga

Found the answer from an earlier post:

https://community.atlassian.com/t5/Bamboo-questions/How-to-use-Bamboo-variables-in-an-app-s-code/qaq-p/1690813

All comments

Alexey Chystoprudov

Variable export will not be available for tasks.

You can use Inject Variable task to make environment variable available for other tasks, but then again it will have "bamboo." prefix and you need to make changes to your scripts to override WORKSPACE variable if bamboo.inject.YOUR_VAR exists

Dale Binkley

I can't change the core scripts because we are still using Jenkins on other projects

Dale Binkley

Thanks to Eduardo Alvarenga

Found the answer from an earlier post:

https://community.atlassian.com/t5/Bamboo-questions/How-to-use-Bamboo-variables-in-an-app-s-code/qaq-p/1690813