Leonardo Marzo,

We actually had a similar issue and we sort of came up with a workable solution for it.

Our situation was that our Jenkins workspaces are owned by a common builder user, but as you said, whenever changes have to be made to the workspace, if the person, or persons, who have the credentials to login as that builder user are gone, then it takes a JazzAdmin to switch the owner (in our environment, only IT has JazzAdmin capabilities.)

So we used the command-line to help get around it a bit, mind you this is RTC 5.0 so you may need to look up the 4.x way of using the CLI if these commands don't exist in your environment:

1. On the build machine where Jenkins runs you create cached login credentials for the builder user so that you can run CLI calls with their permissions: 'scm.exe login --cache --nickname BUILDER_CREDS --username <builder> --repository-uri <RTC_server_url>'. This will create encrypted, locally-cached credentials for the builder user on the machine with a nickname of 'BUILDER_CREDS' so that you can easily use it in other CLI calls. By the way, this data is stored on disk at: C:\Users\<builder>AppData\Local\jazz-scm (or %APPDATA%\Local if you use another OS, this is Win7) so it survives reboots.

2. You can check the owner of a repository via the command line (be aware that the builder user must belong to the RTC Project to have scope to project-scoped workspaces): 'scm.exe --non-interactive --show-uuid y show attributes -r BUILDER_CREDS --workspace <workspace_name/uuid> ' (this is 'workspace propertylist' in the 4.x CLI I believe.)

3. You can re-assign ownership of the workspace by using: 'scm.exe --non-interactive --show-uuid y set attributes -r BUILDER_CREDS --workspace <worksace_name/uuid> --ownedby <user>' to reassign to a specific user.

The way we have this working is we have a parameterized Jenkins build you can start manually, it pings you for a RTC-compliant username, then it will use the above commands to re-assign ownership of a workspace, or range of workspaces by pattern, to the passed-in user in bulk. That way you can assign to you, modify the workspaces, then re-assign back to the builder user.