Saturday 6 November 2010

Where does Hudson store its last synchronized Perforce changelist number?

One of our Hudson build systems is not automatically starting its jobs since we switched it over to a different Perforce server. The polling log reports:

Last sync'd change was nnnnnn

Where nnnnnn is a changelist number from the old server. The new server has lower CL numbers, which causes the problem.

How do I adjust the CL number that Hudson compares against?


View the original article here

No comments:

Post a Comment