Hi, Hartmut:
>
> I might have found a solution to this.
>
> set PYINSTALLER_CONFIG_DIR=%WORKSPACE%
>
> inside each the Jenkins job gives each pyinstaller process its own
> bincache dir.
>
> Hartmut, would that be a valid solution, or are there implications I
> am not aware of?
>
This should work since the error seems to be caused by concurrent access
to the cached files and this changes the location of the cache.

It also seems to be the best solution, as it works the same for all
platforms. (PYINSTALLER_CONFIG_DIR overwrite any platform specific paths).

Thanks for pointing to this - I was not aware of this option anymore :-)

-- 
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer
Information Security Management, Security Governance, Secure Software
Development

Goebel Consult, Landshut
http://www.goebel-consult.de

Blog: https://www.goe-con.de/blog/deshalb-tr-069-ausschalten
Kolumne:
https://www.goe-con.de/hartmut-goebel/cissp-gefluester/2011-10-aus-der-schublade-in-die-koepf
<https://www.goe-con.de/hartmut-goebel/cissp-gefluester/2011-10-aus-der-schublade-in-die-koepfe>


-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pyinstaller/6b99c5b0-7fb1-a55b-5311-2b4723771ad0%40goebel-consult.de.

Attachment: 0x7B752811BF773B65.asc
Description: application/pgp-keys

Reply via email to