Opened 5 years ago

Last modified 3 years ago

#2953 new defect

GitPoller Not Triggering Builds on New Branches

Reported by: Jeremy.Cornett Owned by:
Priority: major Milestone: 0.9.+
Version: 0.8.9 Keywords: gitpoller, git

Description (last modified by sa2ajj)

I'm not sure if this was covered by the original purpose of the pollers, but it'd be really helpful it was.

My company implements a process where we create and commit to branches in a very small time frame. This has become problematic with automatic builds through Buildbot because the GitPoller will not trigger an automatic build of a new branch. It is only when a branch that's already been polled gets a new change that the scheduler will consider that commit.

For example, let's say a user creates a local only branch from master called master+POC44, makes a commit to the master+POC44 branch, and then pushes the POC44 branch to the remote. Buildbot will not pick up that commit and trigger a build through a scheduler configured to look for branches starting with master+POC.

The only way around this problem that I know is for a user to create the branch locally AND on the remote, wait till Buildbot has polled the branch, and THEN make and push a commit. In that case, once Buildbot picks up the commit, a build would be triggered.

This is a rare problem for users at my company because the GitPoller is set to run every two minutes, meaning they'd have to create the branch locally AND on the remote, and make and push a commit in under two minutes for the scheduler to ignore their change.

Change History (4)

comment:1 Changed 5 years ago by dustin

  • Keywords gitpoller git added
  • Milestone changed from undecided to 0.9.+
  • Type changed from undecided to defect

comment:2 Changed 5 years ago by sa2ajj

  • Description modified (diff)

comment:3 Changed 5 years ago by sa2ajj

  • Description modified (diff)
Note: See TracTickets for help on using tickets.