Slide, thanks for the quick response as well.
Is this the setting you're referring to?
https://imgur.com/f2dDD2v





On Thu, Mar 28, 2019 at 4:28 PM Tom Duerr <[email protected]> wrote:

> Mark, thanks for the quick response.
> My settings are here.
> https://imgur.com/eDfxW45
>
> I guess Im a little confused by the options.
>
> Tom
>
>
> On Thu, Mar 28, 2019 at 4:19 PM Mark Waite <[email protected]>
> wrote:
>
>> I thought that was an indication that the GitHub branch source is defined
>> to both create a job for each branch and for each pull request.  I think
>> you need to reconfigure the job to not build a branch if it has a matching
>> pull request.
>>
>> On Thu, Mar 28, 2019 at 5:17 PM Tom Duerr <[email protected]> wrote:
>>
>>> Jenkin 2.138
>>> Branch-Source plugin 2.4.2
>>> SCM=Github Enterprise
>>> Amazon Linux
>>>
>>> Hi,
>>>
>>> We've recently started converting from freestyle jobs to
>>> Jenkinsfile/pipelines.
>>>
>>> We're seeing odd behaviors when pull requests(PR) are created directly
>>> from our
>>> main repo and not from a fork of the repo. Specifically around
>>> the git status checks. PRs that are NOT created from a fork result in two
>>> git checks and 2 full builds being kicked off.
>>> We see these 2 checks:
>>>
>>> continuous-integration/jenkins/branch
>>> continuous-integration/jenkins/pr-merge
>>>
>>> The PRs from the developers fork, cause only 1 check and 1 build.
>>> continuous-integration/jenkins/pr-merge
>>>
>>> Does anyone know how the 2 checks get created?
>>> Whats the difference between continuous-integration/jenkins/branch and
>>> continuous-integration/jenkins/pr-merge?
>>>
>>> Thanks,
>>> Tom
>>>
>>> --
>>> 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/7c18652a-1938-487a-ab70-a1e652010e5a%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/7c18652a-1938-487a-ab70-a1e652010e5a%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
>> --
>> 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/CAO49JtHpRLxjHRhfyRRUWPKaS%2BBX%2BjfTaPNUrochM1kb95Z_EA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHpRLxjHRhfyRRUWPKaS%2BBX%2BjfTaPNUrochM1kb95Z_EA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/CAJuMdDMiAa1Zubs4fh8v3BExgGLN17okmkRZNhYvQfP87Rgxrg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to