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; } } }

Using Bamboo variables on Windows,

Peter Hitchmoug1

I am trying to run the PHPUnit command in the code my Bamboo job has checked out.

Using advice in another post I set a custom capability: build_dir=D:\bamboo\xml-data\build-dir.

Then in my task I set an environment variable:
BUILDROOT="${bamboo.capability.build-dir}/${bamboo.buildKey}"

I get the error on running the task:
Unable to find executable at ${BUILDROOT}/vendor/bin/phpunit.bat

Any help would be appreciated.

Accepted answers

Jason Monsorno2

You can't use the bamboo variable in the executable path but there are work arounds.

1. Use a script task

Long way to illustrate a point other might need. Inline script: ${bamboo.build.working.directory}\vendor\bin\phpunit.bat
Short way and more proper, script file vendor\bin\phpunit.bat

2. Make a custom executable for your purpose at an absolute location ex. C:\RunPhpUnit.bat

Allows control and audit of server capabilities
Add ${bamboo.build.working.directory} to the arguments each time it is used and use it inside your script to execute what you really what.

All comments

Peter Hitchmoug1

I defined the executable as

${BUILDROOT}/vendor/bin/phpunit.bat

I also tried

%BUILDROOT%/vendor/bin/phpunit.bat

to no avail.

Jason Monsorno2

Can you just use ${bamboo.build.working.directory}?

Peter Hitchmoug1

When I substitute ${bamboo.build.working.directory} in my executable, I see the following in the build log -

Unable to find executable at ${bamboo.build.working.directory}\vendor\bin\phpunit.bat.

Ron Chan2

Peter,

Are you trying to define the PHPUnit executable path for the task as ${bamboo.build.working.directory}\vendor\bin\phpunit.bat ?

If that's the case then that's probably not going to work. The executable path needs to be an absolute path. So in our case, we define MSBuild task path to be "C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\msbuild.exe".

Jason Monsorno2

You can't use the bamboo variable in the executable path but there are work arounds.

1. Use a script task

Long way to illustrate a point other might need. Inline script: ${bamboo.build.working.directory}\vendor\bin\phpunit.bat
Short way and more proper, script file vendor\bin\phpunit.bat

2. Make a custom executable for your purpose at an absolute location ex. C:\RunPhpUnit.bat

Allows control and audit of server capabilities
Add ${bamboo.build.working.directory} to the arguments each time it is used and use it inside your script to execute what you really what.

Peter Hitchmoug1

Thanks. That clarifies things. It's a learning curve.

I want to use the PHPUnit installation that is kept alongside the project, managed by composer. I will probably have similar requirements. I will make a small collection of build command scripts at a fixed path which my projects can use.

Also, I will install some more standard build tools e.g. a default PHPUnit and Composer.

I'll try to summarise things in an answer later, but for now things look good.

Peter Hitchmoug1

Agreed - for all the reasons you state.

Jeff Chen7

I just come cross this issue as well. I think it should be very handy to allow using bamboo variable in executable path.