Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Apr 2016 01:56:30 -0700
From:      Craig Rodrigues <rodrigc@FreeBSD.org>
To:        Li-Wen Hsu <lwhsu@freebsd.org>
Cc:        "jenkins-admin@freebsd.org" <jenkins-admin@freebsd.org>,  "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>
Subject:   Re: Why is FreeBSD-HEAD disabled in Jenkins?
Message-ID:  <CAG=rPVeCwnNEx1P_ojQT=thZxu=BeJVHrgAv5FedD62NLhGhUQ@mail.gmail.com>
In-Reply-To: <20160405195603.GA49583@FreeBSD.cs.nctu.edu.tw>
References:  <CAGHfRMB-n2buWxzUMco=dUkn-BX6RdVL%2BCaYYHuwh1txcYke9g@mail.gmail.com> <20160405195603.GA49583@FreeBSD.cs.nctu.edu.tw>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 5, 2016 at 12:56 PM, Li-Wen Hsu <lwhsu@freebsd.org> wrote:

>
> It is not disabled.  It looks the repository checking is set against to
> https://github.com/freebsd/freebsd-ci.git but not our svn src head:
>
> https://jenkins.freebsd.org/job/FreeBSD_HEAD/scmPollLog/
>
> I'll check if I can fix this this week.
>


Polling is working properly for this build.  However, because this is a
Pipeline job,
if there is no workspace from a previous build, then polling won't work.  I
complained about this:
https://groups.google.com/d/msg/jenkinsci-users/-TKlj8y4hrk/76iTTK8KEQAJ

but was told "that's how it works".

So, it is necessary to manually kick off a build, and then automatic
polling will work in
subsequent builds, and you don't have to touch it.

I'm not sure why this build was in this state, but I manually kicked off a
build,
and subsequent builds for FreeBSD_HEAD now seem to be polling the SCM
properly and working.

--
Craig



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVeCwnNEx1P_ojQT=thZxu=BeJVHrgAv5FedD62NLhGhUQ>