CODEWITHSUNDEEP
jenkinsclearcaseclearcase-ucm
Samselvaprabu
Samselvaprabu

Reputation: 18147

Why my clearcase views are often stopped?

We recently upgraded to Clearcase version 8.0.1.8 . In recent days our Clearcase dynamic views are often stopped. Since my views were used in Jenkins if they stopped , some user are calling me and say build is not working.

The root cause is Clearcase view is stopped. How to avoid this ? Or is there any way to start my view every time via Jenkins?

Upvotes: 1

Views: 83

Answers (3)

iclman
iclman

Reputation: 1436

What you can do is force Jenkins to start the view it needs to use. This can be done with the "cleartool startview" command. You just need to specify the view tag you want to start at the beginning of the job that needs to use the view, e.g.,

cleartool startview <view-tag>

Upvotes: 1

Brian Cowan
Brian Cowan

Reputation: 1073

If you upgraded to 8.x from a really old version, you may be dealing with the view idle timeout. If a view server process is idle for 2 hours, it shuts down. It's also possible that someone is shutting down the view. I had someone recently set up a job that 1) ran in parallel on multiple systems; 2) started and set a specific (shared) view; 3) ran a short job; and 4) ran a cleartext endview -server. This tended to do interesting things to the other hosts.

Generally, this just increases the amount of time the job takes as the MVFS will eventually restart the view.

If, OTOH, the I views are getting ended on the client so they drop off /view, that's a little different. I'd set up ClearCase command history and see who is stopping the views.

Upvotes: 1

VonC
VonC

Reputation: 1324557

I don't know of a Jenkins side-effect on dynamic view but:

  • you can check the logs (of the client and the view server) to see if there are any events explaining why the view stops
  • you can add a first build step in the job which ensures that the view is started.

Upvotes: 1

Related Questions