I use Jenkins for automated testing of various PHP applications, all of 
which contain a shared library that is included as a Mercurial sub repo. 
 The shared library is excluded from each applications tests and analysis, 
and so in Jenkins I have created a job specifically to run tests against 
the shared library.  The tests also include the shared library as a sub 
repo.

Can anyone suggest a technique or plugin that I can use so that whenever 
anyone pushes changes into the shared library, the testing application will 
update the library sub repo and then build the job as normal?

Reply via email to