Triggering a CI process as a pre condition to a check-in - implications.

[EdDev]

Hello,

 

I was thinking of integrating PlasticSCM with Jenkins in two modes:

1. Polling: The Jenkins agent will frequently check changes on the branch and build project on change.

2. Triggering: On check-in, issue a command to the agent to perform a build on the latest change.

 

The second can be used as a pre condition for the completion of the check-in in a release branch, which can help avoid "contaminating" a release branch.

 

What I am not clear about is the behavior on waiting for this build to complete (assuming it takes ~5min).

Is the user stuck on the client side? Will it timeout and send him an error?

Is this option even applicable with PlasticSCM?

 

Thanks,

Ed.

 

[manu]

Hi Ed,

 

I'm not sure is this is the answer you are looking for but here I go

 

You can use an after-checkin trigger to issue your own tool that triggers the Jenkins build. In this scenario the local client will be free, no lock.

 

You can build an specific changeset by using the update command plus the --changeset parameter:

 

cm update . --changeset=XYZ