How to disable automatic scheduling of the Git Plugin

[bl0ck3r]

The Git Plugin tells me that it is "Scheduling another build to catch up with project-integration"
I do not use polling, I do not use any triggers, I have a plain job triggered by hand.
How do I turn off any and all of the automatic scheduling performed by the Git Plugin?

Thanks,
Martin

[Mark Waite]

I don't think you can disable all scheduling of jobs performed by the git plugin.  It assumes the tip of each "branch to build" should be built if not built previously.

You might try leaving the "branches to build" field completely empty, or give it the name of a branch which is known to not exist.  Both would be quite unusual use models based on what I've seen with the plugin, but they might work.

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 jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/10864b38-38cf-40bb-8f63-b0f5e9196072%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Jason Pyeron]

I am looking for a way to track the builds of each branch. It does not make sense for a developer's branch to be reflected in the main branch's reports such as stability, code coverage, etc.

Any ideas?

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.

f-40bb-8f63-b0f5e9196072%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/10864b38-38
cf-40bb-8f63-b0f5e9196072%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 jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFbiGH
OzqB_9Vpw5%3DqSkNFGW4qpPD%3DE2U0c0H5BWCD-jw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFbiG
HOzqB_9Vpw5%3DqSkNFGW4qpPD%3DE2U0c0H5BWCD-jw%40mail.gmail.com?> utm_medium=email&utm_source=footer> .

[Jason Pyeron]

> -----Original Message-----
> From: Mark Waite
> Sent: Tuesday, January 27, 2015 21:49
>

> I don't think you can disable all scheduling of jobs
> performed by the git plugin. It assumes the tip of each
> "branch to build" should be built if not built previously.
>
> You might try leaving the "branches to build" field

You need to put the specific branch in the box, that causes it to ignore all other branches.

> completely empty, or give it the name of a branch which is
> known to not exist. Both would be quite unusual use models
> based on what I've seen with the plugin, but they might work.
>
> Mark Waite
>
> On Tue, Jan 27, 2015 at 5:44 PM, bl0ck3r
> <martin....@gmail.com> wrote:
>
>
> The Git Plugin tells me that it is "Scheduling another
> build to catch up with project-integration"
> I do not use polling, I do not use any triggers, I have
> a plain job triggered by hand.
> How do I turn off any and all of the automatic
> scheduling performed by the Git Plugin?

It is because you have multiple branches matching the:

Branches to build: Branch Specifier (blank for 'any'):

>
> Thanks,
> Martin

[Mark Waite]

I really like the multi-branch plugin for that use case.  It automatically creates and destroys jobs based on the branches which match a pattern defined in the job definition.

That avoids the mixing of build results of different branches in the history of a single job.

Mark Waite

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/90C6917954124F27828F08BAEE07177C%40black.

For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Dunnigan, Terrence J]

We have plenty of parameterized builds that we invoke on-demand, by clicking ‘Build with Parameters’. They use git and build a specific branch. They do not poll and we don’t use any external triggers.

 

I’ve never seen a message like the one you describe. Where do you get this message? On the job configuration page?

 

Terry

--

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 jenkinsci-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/10864b38-38cf-40bb-8f63-b0f5e9196072%40googlegroups.com.

[bl0ck3r]

I see that message ("Scheduling another build to catch up with project-integration") in the console. My use case is the same as yours: all my builds are on-demand. We definitely do not want any self-triggered builds.

[bl0ck3r]

Yes, Mark was also suggesting that that as a probable cause, however, I think the problem is different. I decided to open a feature request, where I show that the Branch Specifier is set by a build parameter variable:
https://issues.jenkins-ci.org/browse/JENKINS-26664

Martin

> You might try leaving the "branches to build" field

You need to put the specific branch in the box, that causes it to ignore all other branches.

[mi...@scene53.com]

We, too, would like the option to prevent the GIT plugin from triggering new builds on its own.

We have a number of management jobs which we manually run; These jobs use the GIT SCM plugin to pull the latest version of our management script repository. As I understand it, if I push changes to my scripts and then (perhaps weeks later) run the job, Jenkins will trigger an _additional_ run using default(?) parameters.

I understand that Jenkins is primarily a CI tool, and in that case, you would _expect_ jobs to be triggered on SCM changes, but there should be an option for disabling this behavior, especially when "Poll SCM is disabled"...

-Mike

[Björn Pedersen]

Hi,

The problem are the default build strategies. They try to be clever. As I am using  gerrit here I only use the gerrit-trigger stragety that ensure only the specified REF (The refspec field in the advanced settings) is built.  YOu could probably factor the  strategy into its own plugin or just install the gerrit trigger plugin and use its strategy.

Björn