Monday, 13 August 2018

Setting JUCE global paths for Jenkins (Windows)



My problem: Jenkins build jobs were failing due to being unable to generate projects form jucer files. JUCE complained that the global paths were incorrect. ROLI user and license details didn't appear to be being saved either.

Solution: Okay the projucer settings on the PC don't get passed over to Jenkins builds, this is because the projucer settings are saved in your user details and Jenkins runs runs jobs as a special kind of user.

To solve this open up Projucer and log in, set up all the global paths you’ll need and save. 
Then copy the following file:
C:\Users\<Username>\AppData\Roaming\Projucer\Projucer.settings

to the location where Jenkins can find and use it:
C:\Windows\System32\config\systemprofile\AppData\Roaming\Projucer\Projucer.settings

AppData is a hidden folder so be sure to turn those on if you cannot see it by going to the View tab in windows explorer and checking the 'Hidden items' checkbox.

If your Jenkins is only using JUCE 5 you're probably good to go, but my Jenkins is building other projects using JUCE 4 and my settings get overwritten and lost every time a JUCE 4 project is built. So I have copied my good settings file to a safe folder in my Documents and copy it over before every JUCE 5 build using this batch command

copy /Y "C:\Users\<Username>\Documents\Projucer5\Projucer.settings" C:\Windows\System32\config\systemprofile\AppData\Roaming\Projucer\Projucer.settings

Now when you use JUCE from Jenkins everything should be fine.

No comments:

Post a Comment

  Azure Trusted Signing Signtool Error SignTool Error: An unexpected internal error has occurred. Error information: "Error: SignerSign...