PlasticSCM / Unity Version Control Token Expiring Too Fast on Jenkins Build Machine

Unity Services
,
1

Hi everyone,

I’m using Jenkins for build automation on a Windows VM, where PlasticSCM / Unity Version Control is installed and logged in using my Unity ID. However, I keep running into an issue where the authentication token expires way too fast.

Issue:

• Every time the token expires, Jenkins fails to access PlasticSCM / Unity Version Control.

• The build output shows a message asking me to log in, and the process hangs.

• The only way to fix it is to RDP into the machine, manually start Plastic, log in again, and acquire a new token .

• Once I do that, the build works fine—until the token expires again, requiring me to repeat the process.

Question:

• Is there a way to extend the token expiration time ?

• Can I automate the authentication renewal so I don’t have to manually log in via RDP every time?

• Is there a recommended approach to handling PlasticSCM authentication in a headless Jenkins environment?

Any help or best practices would be greatly appreciated!

Thanks!

2

Hi @maximiliananzinger ,

You can generate Token at Plasticscm.com → Plastic SCM Dashboard -->Edit Account → API Keys -->Add New API Token.

Reveal Token button instructs how to use your token.

Please let us know if you have any questions.

1 Like