I downgraded my git plugin to 1.5xx and Included Regions work.... Now I'm 
getting hanging SCM Polling threads though.  Found this jira ticket (which 
is kinda old but still has chatter): 
https://issues.jenkins-ci.org/browse/JENKINS-5413

I'm trying to clean up the threads with the script in the discussion but 
I'd rather have a cleaner solution.  Any help?

Thanks!

On Friday, November 22, 2013 11:59:27 AM UTC-5, Erik Cokeley wrote:
>
> Thanks I'm going to try the Force polling using workspace option.
>
> On Friday, November 22, 2013 11:51:33 AM UTC-5, Nicolas De loof wrote:
>>
>> yes, I'm looking into possible changes in jenkins-core that would allow 
>> such a remote-polling to be used to detect potential changes, then use 
>> workspace to "confirm" changes actually have to get handled by a build.
>>
>>
>> 2013/11/22 Mark Waite <[email protected]>
>>
>>> Nicolas DeLoof just posted a hint that the issue may be related to the 
>>> change in the default state of "fast remote polling".  Fast remote polling 
>>> allows the master Jenkins instance to check for changes on a git 
>>> repository, without cloning that git repository.  That technique makes 
>>> commit detection much lighter and faster.  However, that technique cannot 
>>> process inclusion and exclusion conditions.
>>>
>>> If you have not already downgraded your Git plugin, you might try adding 
>>> the Advanced Behavior, "Force polling using workspace".
>>>
>>> Mark Waite
>>>
>>>
>>> On Fri, Nov 22, 2013 at 8:06 AM, Erik Cokeley <[email protected]>wrote:
>>>
>>>> Thanks I'm going to downgrade my git plugin.  I think that is what I'm 
>>>> running into.
>>>>
>>>> On Thursday, November 21, 2013 6:12:33 PM UTC-5, Mark Waite wrote:
>>>>>
>>>>> You may be suffering from:
>>>>>
>>>>> https://issues.jenkins-ci.org/browse/JENKINS-20569<https://www.google.com/url?q=https%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-20569&sa=D&sntz=1&usg=AFQjCNEHM0UHu4NkxSUJiQgjBx8R5mEAPQ>
>>>>>  - 
>>>>> excluded regions not honored by Git plugin 2.0
>>>>>
>>>>> I believe there is also a bug report that include regions do not 
>>>>> behave as expected.  It is probably worth a search through Jira to see 
>>>>> what 
>>>>> it will tell you about include and exclude regions.
>>>>>
>>>>> Mark Waite
>>>>>
>>>>>
>>>>> On Thu, Nov 21, 2013 at 4:03 PM, Erik Cokeley <[email protected]>wrote:
>>>>>
>>>>>> My git is calling Jenkins in it's post-receive hook exactly how it 
>>>>>> says to here: https://wiki.jenkins-ci.org/display/JENKINS/Git+
>>>>>> Plugin#GitPlugin-Pushnotificationfromrepository<https://www.google.com/url?q=https%3A%2F%2Fwiki.jenkins-ci.org%2Fdisplay%2FJENKINS%2FGit%2BPlugin%23GitPlugin-Pushnotificationfromrepository&sa=D&sntz=1&usg=AFQjCNFAxqsAPNeJWeZKYX87tY81fnKzSA>
>>>>>>
>>>>>> It is kicking off builds and doing the Poll SCM (which I checked).
>>>>>>
>>>>>> My git is huge (I mean HUGE) and I need to leverage the Included 
>>>>>> Regions.
>>>>>>
>>>>>> It seems like I get mixed results for pushes.  I might push to 
>>>>>> folderA/folderB/project1 and folderA/folderC/project2 will be triggered 
>>>>>> along with project1's job.  And my Included Region will look like 
>>>>>> folderA/folderB/.*
>>>>>>
>>>>>> Is this a known bug or can anyone point me to why builds are being 
>>>>>> triggered wrong?
>>>>>>
>>>>>> I'm also making my branch */master is the * in that effecting 
>>>>>> anything (I only have 1 git setup for anything as of now)
>>>>>>  
>>>>>> -- 
>>>>>> 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].
>>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>>>
>>>>>
>>>>>  -- 
>>>> 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].
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>
>>>  -- 
>>> 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].
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>

-- 
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].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to