Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
MIME-Version: 1.0
In-Reply-To: <1F2EC79C-5165-4BE2-A72E-E3E179F4766E@effectivemachines.com>
References: <1F2EC79C-5165-4BE2-A72E-E3E179F4766E@effectivemachines.com>
From: Sean Busbey <sean.busbey@gmail.com>
Date: Thu, 3 Aug 2017 14:21:33 -0500
Message-ID: <CAN5cbe4K1vMLfdsmV=JePzSkPx0Y2Dsjzyra34mWtf3-3doy6Q@mail.gmail.com>
Subject: Re: Precommit-Admin no longer running on Jenkins
To: builds@apache.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 03 Aug 2017 19:21:58 -0000

What are the associated node labels for it running? That's the most
common cause of no runs I know of.

On Thu, Aug 3, 2017 at 11:52 AM, Allen Wittenauer
<aw@effectivemachines.com> wrote:
> (BCC: dev@yetus.apache.org, since many Apache Yetus users are dependent u=
pon precommit-admin too)
>
>
>         I=E2=80=99m=E2=80=A6 very confused.
>
>         The precommit-admin (which kicks off patch testing for a large, l=
arge number of projects) is no longer automatically running. The job code a=
nd the job configuration hasn=E2=80=99t changed in a very long time. Howeve=
r it no longer appears to be getting fired off automatically by Jenkins.  I=
f one does a build now, it works just fine.
>
>         Could something have changed elsewhere to cause it stop getting s=
cheduled to run?
>
>         I haven=E2=80=99t looked really hard yet, but I=E2=80=99m thinkin=
g other scheduled jobs aren=E2=80=99t running either.  But thought I=E2=80=
=99d ask here before I started digging into those since this job is *defini=
tely* broken.
>
>         Thanks.


--=20
Sean