ClearCase identities used by the clearcase-jenkins plugin

When using automatic or web views, the ClearCase identity is provided by the administrator configuring a Jenkins build job. The administrator stores credentials in the Jenkins-protected credentials store. When a job runs, it retrieves credentials from the Jenkins store and uses them to access the CCRC WAN server. This works for operations on the Jenkins controller node and also on any agent nodes.

When using dynamic or snapshot views, the ClearCase identity is provided by the operating system. The account running the Jenkins process on the controller node must have appropriate access to the ClearCase VOBs that can be used during job execution. The controller node performs several ClearCase operations locally while starting a job.

During the job's execution, Jenkins might distribute operations to one or more Jenkins agents. Each of those agents also performs ClearCase operations in dynamic or snapshot views, so the operating system account used for the agent(s) must have the appropriate access to the requisite ClearCase VOBs.

Also, when using dynamic or snapshot views with remote agents: the hosts for each agent need to be in an appropriate registry region to have access to the same views and VOBs. If you are using the same operating system type (Windows or Linux) on an agent host as on the controller node host, then both hosts should have the same registry server and region.

If you are using a Windows or Linux interoperation environment, then each host should use the same ClearCase registry host. You should configure a pair of regions on the registry host for the interoperation of VOBs and assign each host to the appropriate region for its operating system. Your build jobs (scripts and pipelines) must be defined to be compatible with whatever OS is used by the Jenkins agent that will execute the job step(s).

With the remote view types, the views are registered under the OS account running the Jenkins controller and agent processes, and they are only visible to the creating user. With the local view types, the views are created or owned by the Jenkins and or agent OS identities and centrally registered with the ClearCase registry.