Ok, I am just dropping some creativity to the thread. Don't expect this to be thought to rock bottom. Considering 2 repositories are in use.
First thought - I have to admit it is somewhat coarse - 2 jobs each polling its own repository. The jobs have a parametrized build trigger with a predeifined build parameter (e.g. the repository name). If changes found will the polling job trigger the build job with the parameter needed to know where the change happened. That build job has 2 conditional build steps (plugin) and no SCM module active. One of conditional build step get active depending on the passed build parameter, switches to the modules belonging the respective repository and fire off a "svn update ." You will initially have to either activate the SCM module to create and load the workspace with content, do this manually or compose a condition (if not exist) that checks out the repository if not existent. That's a first shot which not necessarily takes changes in both repositories into account so the build job may run twice. There are also solutions for this issue but I'm not fit enough atm. Maybe there is already a solution or plugin available or of better help but my idea should at least push you into the right direction. Depending on your own creativity I'm content that you will figure out more and more nifty approaches when you start to crunch your head on the issue ;) HTH Jan Am Dienstag, 17. Juli 2012 15:02:52 UTC+2 schrieb Varghese Renny: > > > How can i write using shell script like checking whether any updates on > repository every time..(polling repository everytime) do update if any > changes..replacing existing poll scm..? > > > Thanks in advance >
