Does SCM_ALLOW_INSECURE work in RTC 3.0.1.2?
Could not secure .jazz-scm:
Failed to set permissions on directory /home/myhome/.jazz-scm
Does anybody know whether it also work for RTC 3.0.1.2?
I also found references that suggested to remove .jazz-scm and have scm recreate it and I did that and have started a bunch of builds again.
Accepted answer
Comments
It can do the lock when only one scm command is running. The issue is when 2 or more are running at the same time and only one of them can get the lock.
I remember that there was a race condition that could occur when running multiple commands from different consoles. I haven't seen any error related to that with respect to setting the permissions.
this is nothing to do with a sandbox.
We are running the builds form Build Forge.
That means that all builds run from the same service account.
We use the -r nickname, so the pw doesn't get exposed.
The BF project is generic and used from literally thousands of build definitions.
Builds run in parallel, each has its own workspace, sandbox etc. They do commands like
scm list components, scm compare, scm list baselines, scm deliver
In fact scm list components is run as the very first command and the output is parsed to determine the stream name.
As probability will have it, if 2 or more builds are started in succession, the list components commands run at the same time and often 1 has that error.
I tried setting SCM_ALLOW_INSECURE=true and it looks like it works in 3.0.1.2 as well, its just undocumented.
I'll set it in the BF env and watch whether the error goes away.
SCM_ALLOW_INSECURE=true has no effect in RTC 3.0.1.2.
All our shares are NFS. Its a VM.
I have put in code that checks the error message for "Could not secure .jazz-scm" and retries in that case.
I just found this article that mentions the issue with NFS... https://jazz.net/library/article/533