Hi, Usually, it's done the other way round. One possible configuration is : one Jenkins jobs for each library, one Jenkins jobs for each product. Then, for each library : - Poll SCM to check if changes happened - Build the library - Trigger the builds of the product that relie on this library.
For each product : - Retrieve the libraries artifacts from the libraries jobs - Compile the product You can configure the products to prevent a job to run while a library it depends upon is building (advanced project option - do not build when upstream project is building) 2012/12/7 Bharathi Ramalingam <ramalingam.bhara...@gmail.com> > > You should take a look at SCM poll and build trigger when scm changes. > > On Friday, December 7, 2012 11:06:08 AM UTC+5:30, Ivan Kharin wrote: >> >> I'm new to Jenkins. >> I have 20 libraries as separate jobs. >> And 15 products, each of which depends on a subset of these libraries. >> I can not understand how I obtain needed result: >> Before building the product, automatically start building only those >> libraries that have been changed. >> Is it possible to specify a condition for the Build Step "repository >> changed"? >> >> --- >> Regards, >> Ivan Kharin >> >
