I have a remote agent running on Windows Server 2012 as a Window's Service. The remote agent specifies the following directories:
Temporary directory: C:\Windows\system32\config\systemprofile\AppData\Local\Temp\
User Home: C:\Windows\system32\config\systemprofile
All build step requirements are met by the remote agent (source checkout, npm install, bower install, grunt test)
When running the grunt test task which uses Karma to test against the phantomJS browser the build fails when the remote agent fails to open a file in the temporary directory.
build 26-Sep-2016 12:25:17 [32m26 09 2016 12:25:17.509:INFO [karma]: [39mKarma v1.3.0 server started at http://localhost:8080/ build 26-Sep-2016 12:25:17 [32m26 09 2016 12:25:17.525:INFO [launcher]: [39mLaunching browser PhantomJS with unlimited concurrency build 26-Sep-2016 12:25:17 [32m26 09 2016 12:25:17.556:INFO [launcher]: [39mStarting browser PhantomJS build 26-Sep-2016 12:25:19 [31m26 09 2016 12:25:19.762:ERROR [phantomjs.launcher]: [39mCan't open 'C:\Windows\system32\config\systemprofile\AppData\Local\Temp\karma-44978277/capture.js'
I have set directory permissions for Temp\ to 'all-access' for the System and admin uses.
Logging into the remote agent during a build allows me to see the temp\karma\ directory get created, but then it disappears during the failure.
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events