Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
MIME-Version: 1.0
Reply-To: jfarrell@apache.org
In-Reply-To: 
 <CADXZZfsqXzC8edhrRq+X3TOF1YzT=wvPV=kd_vdyKWRqL4KOKw@mail.gmail.com>
References: 
 <CADXZZfsqXzC8edhrRq+X3TOF1YzT=wvPV=kd_vdyKWRqL4KOKw@mail.gmail.com>
Date: Wed, 12 Mar 2014 19:43:40 -0400
Message-ID: 
 <CANyrgvcOrNGttG-Vzzj2psSd-7pSR2wpMSkujU560-f8bGPsng@mail.gmail.com>
Subject: Re: Jenkins-CI API error with Git plugin v2.0.3
From: Jake Farrell <jfarrell@apache.org>
To: "builds@apache.org" <builds@apache.org>
Content-Type: multipart/alternative; boundary=001a11347e9e022daa04f47168ba

--001a11347e9e022daa04f47168ba
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Martin
The git-plugin version 2.0.4 is installed, Jenkins just requires a restart
for it to become active

-Jake


On Wed, Mar 12, 2014 at 1:35 PM, Martin Brandtner <brandtner@ifi.uzh.ch>wro=
te:

> Dear Build Admins,
>
> the version of the Jenkins-CI git-plugin, which is currently installed on
> your build servers causes an error during API calls. For example: [1]
> This issue is known and fixed in version 2.0.4 of the git-plugin: [2]
>
> We currently work on a research project [3], which highly depends on the
> Jenkins-CI data of various Apache projects.
> May we ask you to tell us when you plan the next update of your Jenkins-C=
I
> instance, especially of the git-plugin?
>
> [1] https://builds.apache.org/job/Camel.trunk.fulltest/1735/api/json
> [2] https://issues.jenkins-ci.org/browse/JENKINS-21954
> [3] https://seal-students.ifi.uzh.ch/sqa-timeline
>
> --
> Best Regards/Freundliche Gr=FCsse
> Martin Brandtner
>
> University of Zurich
> Software Evolution and Architecture Lab
> Binzm=FChlestrasse 14
> CH-8050 Z=FCrich
> Tel. +41 44 635 67 31
> http://seal.ifi.uzh.ch/brandtner
>

--001a11347e9e022daa04f47168ba--