Hi,

Eventually I ended up building periodically and checking for SCM changee 
manually in each repository manually. It took some work, but I didn't want 
to define multiple jobs just for polling.

Taro

On Tuesday, October 18, 2016 at 2:44:22 PM UTC-7, Rachel Moreno wrote:
>
> Hi,
>
> Sorry, it's possible with Pipeline:
>
> *Polling is supported across multiple SCMs (changes in one or more will 
> trigger a new build), and again is done according to the SCMs used in the 
> last build of the pipeline.*
>
> You'll have to run it once manually for listening to SCM changes.
>
> More information: 
> https://github.com/jenkinsci/workflow-scm-step-plugin/blob/master/README.md
>
> Best regards,
> Rachel
>
> El jueves, 13 de octubre de 2016, 22:56:16 (UTC+2), Rachel escribió:
>>
>> Hi,
>>
>> In your case, I would have two separated Jenkins jobs, but sharing the 
>> same workspace:
>>
>>    - Advanced Project Options > Use custom workspace 
>>
>> I hope be useful.
>>
>> Best regards,
>> Rachel
>>
>> El miércoles, 12 de octubre de 2016, 2:47:08 (UTC+2), [email protected] 
>> escribió:
>>>
>>> Is it possible to poll for changes from both svn and git repositories 
>>> from within a pipeline job? In Jenkins, pipeline scm configuration is tied 
>>> to a particular scm type (due to a radio button), but I would like to poll 
>>> both svn and git at the same time. As a result of the poll detecting an scm 
>>> change, I want to invoke only one build.
>>>
>>> As a workaround, maybe I need to have two separate Jenkins jobs? 
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3f0b0a8d-afdd-44f3-9d5e-71d117f392e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to