You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by Andreas Lehmkuehler <an...@lehmi.de> on 2014/04/18 20:16:11 UTC
PDFBox build job disappears
Hi,
one of our PDFBox build jobs [1] somehow disappears. Does anyone know why? Is it
just a jenkins hickup or did someone delete it accidentically? The other 2 are
still available [2], [3]
BR
Andreas Lehmkühler
[1] https://builds.apache.org/job/PDFBox-trunk/
[2] https://builds.apache.org/job/PDFBox%201.8.x/
[3] https://builds.apache.org/job/PDFBox-ant/
Re: PDFBox build job disappears
Posted by Olivier Lamy <ol...@apache.org>.
On 20 April 2014 04:01, Andreas Lehmkuehler <an...@lehmi.de> wrote:
> The missing job is back again.
>
> Whatever you've done, thanks for your help.
>
> Is there anything I can do to prevent such cases?
As it's due to a Jenkins bug not really :-)
>
>
> BR
> Andreas Lehmkühler
>
> Am 19.04.2014 04:16, schrieb Olivier Lamy:
>>
>> Yup there is an issue in Jenkins.
>>
>> I fixed that
>> https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cfca215b4eaec48613
>> I will try to release the jenkins plugin and update our instance.
>> (tonight or tomorrow)
>>
>>
>> On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
>>>
>>> Hi,
>>>
>>> one of our PDFBox build jobs [1] somehow disappears. Does anyone know
>>> why?
>>> Is it just a jenkins hickup or did someone delete it accidentically? The
>>> other 2 are still available [2], [3]
>>>
>>>
>>> BR
>>> Andreas Lehmkühler
>>>
>>> [1] https://builds.apache.org/job/PDFBox-trunk/
>>> [2] https://builds.apache.org/job/PDFBox%201.8.x/
>>> [3] https://builds.apache.org/job/PDFBox-ant/
>>
>>
>>
>>
>
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: PDFBox build job disappears
Posted by Andreas Lehmkuehler <an...@lehmi.de>.
The missing job is back again.
Whatever you've done, thanks for your help.
Is there anything I can do to prevent such cases?
BR
Andreas Lehmkühler
Am 19.04.2014 04:16, schrieb Olivier Lamy:
> Yup there is an issue in Jenkins.
> I fixed that https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cfca215b4eaec48613
> I will try to release the jenkins plugin and update our instance.
> (tonight or tomorrow)
>
>
> On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
>> Hi,
>>
>> one of our PDFBox build jobs [1] somehow disappears. Does anyone know why?
>> Is it just a jenkins hickup or did someone delete it accidentically? The
>> other 2 are still available [2], [3]
>>
>>
>> BR
>> Andreas Lehmkühler
>>
>> [1] https://builds.apache.org/job/PDFBox-trunk/
>> [2] https://builds.apache.org/job/PDFBox%201.8.x/
>> [3] https://builds.apache.org/job/PDFBox-ant/
>
>
>
Re: PDFBox build job disappears
Posted by Hervé BOUTEMY <he...@free.fr>.
thank you: this may give hints to Andreas for workarounds
BTW: is there a way for normal Jenkins users to see which version of which
plugin is installed actually?
Regards,
Hervé
Le samedi 19 avril 2014 18:08:12 Olivier Lamy a écrit :
> https://issues.jenkins-ci.org/browse/JENKINS-22647
>
> On 19 April 2014 15:42, Hervé BOUTEMY <he...@free.fr> wrote:
> > Hi,
> >
> > you mean this NPE causes job silently disappear?
> > ouch, it's more severe than expected
> >
> > I'm not a Jenkins master: there is not tracker issue associated?
> >
> > Regards,
> >
> > Hervé
> >
> > Le samedi 19 avril 2014 12:16:22 Olivier Lamy a écrit :
> >> Yup there is an issue in Jenkins.
> >> I fixed that
> >> https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cf
> >> ca
> >> 215b4eaec48613 I will try to release the jenkins plugin and update our
> >> instance.
> >> (tonight or tomorrow)
> >>
> >> On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
> >> > Hi,
> >> >
> >> > one of our PDFBox build jobs [1] somehow disappears. Does anyone know
> >> > why?
> >> > Is it just a jenkins hickup or did someone delete it accidentically?
> >> > The
> >> > other 2 are still available [2], [3]
> >> >
> >> >
> >> > BR
> >> > Andreas Lehmkühler
> >> >
> >> > [1] https://builds.apache.org/job/PDFBox-trunk/
> >> > [2] https://builds.apache.org/job/PDFBox%201.8.x/
> >> > [3] https://builds.apache.org/job/PDFBox-ant/
Re: PDFBox build job disappears
Posted by Olivier Lamy <ol...@apache.org>.
https://issues.jenkins-ci.org/browse/JENKINS-22647
On 19 April 2014 15:42, Hervé BOUTEMY <he...@free.fr> wrote:
> Hi,
>
> you mean this NPE causes job silently disappear?
> ouch, it's more severe than expected
>
> I'm not a Jenkins master: there is not tracker issue associated?
>
> Regards,
>
> Hervé
>
> Le samedi 19 avril 2014 12:16:22 Olivier Lamy a écrit :
>> Yup there is an issue in Jenkins.
>> I fixed that
>> https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cfca
>> 215b4eaec48613 I will try to release the jenkins plugin and update our
>> instance.
>> (tonight or tomorrow)
>>
>> On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
>> > Hi,
>> >
>> > one of our PDFBox build jobs [1] somehow disappears. Does anyone know why?
>> > Is it just a jenkins hickup or did someone delete it accidentically? The
>> > other 2 are still available [2], [3]
>> >
>> >
>> > BR
>> > Andreas Lehmkühler
>> >
>> > [1] https://builds.apache.org/job/PDFBox-trunk/
>> > [2] https://builds.apache.org/job/PDFBox%201.8.x/
>> > [3] https://builds.apache.org/job/PDFBox-ant/
>
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: PDFBox build job disappears
Posted by Hervé BOUTEMY <he...@free.fr>.
Hi,
you mean this NPE causes job silently disappear?
ouch, it's more severe than expected
I'm not a Jenkins master: there is not tracker issue associated?
Regards,
Hervé
Le samedi 19 avril 2014 12:16:22 Olivier Lamy a écrit :
> Yup there is an issue in Jenkins.
> I fixed that
> https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cfca
> 215b4eaec48613 I will try to release the jenkins plugin and update our
> instance.
> (tonight or tomorrow)
>
> On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
> > Hi,
> >
> > one of our PDFBox build jobs [1] somehow disappears. Does anyone know why?
> > Is it just a jenkins hickup or did someone delete it accidentically? The
> > other 2 are still available [2], [3]
> >
> >
> > BR
> > Andreas Lehmkühler
> >
> > [1] https://builds.apache.org/job/PDFBox-trunk/
> > [2] https://builds.apache.org/job/PDFBox%201.8.x/
> > [3] https://builds.apache.org/job/PDFBox-ant/
Re: PDFBox build job disappears
Posted by Hervé BOUTEMY <he...@free.fr>.
Le samedi 19 avril 2014 21:44:57 Olivier Lamy a écrit :
> On 19 April 2014 20:21, Hervé BOUTEMY <he...@free.fr> wrote:
> > Le samedi 19 avril 2014 11:27:47 Andreas Lehmkuehler a écrit :
> >> Hi,
> >>
> >> Am 19.04.2014 08:13, schrieb Hervé BOUTEMY:
> >> > IIUC, the display name of a PDFBox Maven module is causing harm because
> >> > it
> >> > is null: is it possible for Andreas just to change something in his
> >> > project poms to avoid this null display name? I suppose such null
> >> > display
> >> > name won't be a great thing in other parts of Jenkins, but couldn't
> >> > easily find how this value is calculated
> >>
> >> Hmmm, where can I see that null value? Which module are you referring to?
> >
> > I don't know, hence my question
> > My reasoning is just that if Olivier's commit fixes a problem encountered
> > by your PDFBox job, that means that your job causes a null value in a
> > module display name (I simply read the little commit)
> >
> > I just tested to create a PDFBox Jenkins job on my local machine, with
> > Jenkins 1.559 and Jenkins's maven-plugin 2.2 and got no failure, nor job
> > disappearing I don't know if my local test has something that makes it
> > not representative
> Did you restart Jenkins.
> BTW loading a job without history is different from loading one with
> some history
yes, I restarted Jenkins after doing one build: perhaps one is too short a
history
I don't know if you hope that the commit will change status for PDFBox because
you found something about it in logs
I see I can just wait and see: so be it
Regards,
Hervé
>
> > But for the moment, I'm not sure that the comit will fix your PDFBox job
> > disappear problem: we'll see when the new plugin version is deployed :)
> >
> > Regards,
> >
> > Hervé
> >
> >> > Regards,
> >> >
> >> > Hervé
> >>
> >> BR
> >> Andreas Lehmkühler
> >>
> >> > Le samedi 19 avril 2014 12:16:22 Olivier Lamy a écrit :
> >> >> Yup there is an issue in Jenkins.
> >> >> I fixed that
> >> >> https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a
> >> >> 2cf
> >> >> ca
> >> >> 215b4eaec48613 I will try to release the jenkins plugin and update our
> >> >> instance.
> >> >> (tonight or tomorrow)
> >> >>
> >> >> On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
> >> >>> Hi,
> >> >>>
> >> >>> one of our PDFBox build jobs [1] somehow disappears. Does anyone know
> >> >>> why?
> >> >>> Is it just a jenkins hickup or did someone delete it accidentically?
> >> >>> The
> >> >>> other 2 are still available [2], [3]
> >> >>>
> >> >>>
> >> >>> BR
> >> >>> Andreas Lehmkühler
> >> >>>
> >> >>> [1] https://builds.apache.org/job/PDFBox-trunk/
> >> >>> [2] https://builds.apache.org/job/PDFBox%201.8.x/
> >> >>> [3] https://builds.apache.org/job/PDFBox-ant/
Re: PDFBox build job disappears
Posted by Olivier Lamy <ol...@apache.org>.
On 19 April 2014 20:21, Hervé BOUTEMY <he...@free.fr> wrote:
> Le samedi 19 avril 2014 11:27:47 Andreas Lehmkuehler a écrit :
>> Hi,
>>
>> Am 19.04.2014 08:13, schrieb Hervé BOUTEMY:
>> > IIUC, the display name of a PDFBox Maven module is causing harm because it
>> > is null: is it possible for Andreas just to change something in his
>> > project poms to avoid this null display name? I suppose such null display
>> > name won't be a great thing in other parts of Jenkins, but couldn't
>> > easily find how this value is calculated
>>
>> Hmmm, where can I see that null value? Which module are you referring to?
> I don't know, hence my question
> My reasoning is just that if Olivier's commit fixes a problem encountered by
> your PDFBox job, that means that your job causes a null value in a module
> display name (I simply read the little commit)
>
> I just tested to create a PDFBox Jenkins job on my local machine, with Jenkins
> 1.559 and Jenkins's maven-plugin 2.2 and got no failure, nor job disappearing
> I don't know if my local test has something that makes it not representative
>
Did you restart Jenkins.
BTW loading a job without history is different from loading one with
some history
> But for the moment, I'm not sure that the comit will fix your PDFBox job
> disappear problem: we'll see when the new plugin version is deployed :)
>
> Regards,
>
> Hervé
>
>>
>> > Regards,
>> >
>> > Hervé
>>
>> BR
>> Andreas Lehmkühler
>>
>> > Le samedi 19 avril 2014 12:16:22 Olivier Lamy a écrit :
>> >> Yup there is an issue in Jenkins.
>> >> I fixed that
>> >> https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cf
>> >> ca
>> >> 215b4eaec48613 I will try to release the jenkins plugin and update our
>> >> instance.
>> >> (tonight or tomorrow)
>> >>
>> >> On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
>> >>> Hi,
>> >>>
>> >>> one of our PDFBox build jobs [1] somehow disappears. Does anyone know
>> >>> why?
>> >>> Is it just a jenkins hickup or did someone delete it accidentically? The
>> >>> other 2 are still available [2], [3]
>> >>>
>> >>>
>> >>> BR
>> >>> Andreas Lehmkühler
>> >>>
>> >>> [1] https://builds.apache.org/job/PDFBox-trunk/
>> >>> [2] https://builds.apache.org/job/PDFBox%201.8.x/
>> >>> [3] https://builds.apache.org/job/PDFBox-ant/
>
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: PDFBox build job disappears
Posted by Andreas Lehmkuehler <an...@lehmi.de>.
Hi,
Am 19.04.2014 12:21, schrieb Hervé BOUTEMY:
> Le samedi 19 avril 2014 11:27:47 Andreas Lehmkuehler a écrit :
>> Hi,
>>
>> Am 19.04.2014 08:13, schrieb Hervé BOUTEMY:
>>> IIUC, the display name of a PDFBox Maven module is causing harm because it
>>> is null: is it possible for Andreas just to change something in his
>>> project poms to avoid this null display name? I suppose such null display
>>> name won't be a great thing in other parts of Jenkins, but couldn't
>>> easily find how this value is calculated
>>
>> Hmmm, where can I see that null value? Which module are you referring to?
> I don't know, hence my question
> My reasoning is just that if Olivier's commit fixes a problem encountered by
> your PDFBox job, that means that your job causes a null value in a module
> display name (I simply read the little commit)
OK, I see.
> I just tested to create a PDFBox Jenkins job on my local machine, with Jenkins
> 1.559 and Jenkins's maven-plugin 2.2 and got no failure, nor job disappearing
> I don't know if my local test has something that makes it not representative
The job isn't new but quite old. There weren't any big changes over years (just
things like jdk/maven-update, changed module config etc.), it just disappears.
> But for the moment, I'm not sure that the comit will fix your PDFBox job
> disappear problem: we'll see when the new plugin version is deployed :)
So, the question is, will the job appear again after deploying the new plugin
version, or do we have to create a new job to replace the missing one?
> Regards,
>
> Hervé
Thanks for your help,
Andreas
>
>>
>>> Regards,
>>>
>>> Hervé
>>
>> BR
>> Andreas Lehmkühler
>>
>>> Le samedi 19 avril 2014 12:16:22 Olivier Lamy a écrit :
>>>> Yup there is an issue in Jenkins.
>>>> I fixed that
>>>> https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cf
>>>> ca
>>>> 215b4eaec48613 I will try to release the jenkins plugin and update our
>>>> instance.
>>>> (tonight or tomorrow)
>>>>
>>>> On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
>>>>> Hi,
>>>>>
>>>>> one of our PDFBox build jobs [1] somehow disappears. Does anyone know
>>>>> why?
>>>>> Is it just a jenkins hickup or did someone delete it accidentically? The
>>>>> other 2 are still available [2], [3]
>>>>>
>>>>>
>>>>> BR
>>>>> Andreas Lehmkühler
>>>>>
>>>>> [1] https://builds.apache.org/job/PDFBox-trunk/
>>>>> [2] https://builds.apache.org/job/PDFBox%201.8.x/
>>>>> [3] https://builds.apache.org/job/PDFBox-ant/
>
Re: PDFBox build job disappears
Posted by Hervé BOUTEMY <he...@free.fr>.
Le samedi 19 avril 2014 11:27:47 Andreas Lehmkuehler a écrit :
> Hi,
>
> Am 19.04.2014 08:13, schrieb Hervé BOUTEMY:
> > IIUC, the display name of a PDFBox Maven module is causing harm because it
> > is null: is it possible for Andreas just to change something in his
> > project poms to avoid this null display name? I suppose such null display
> > name won't be a great thing in other parts of Jenkins, but couldn't
> > easily find how this value is calculated
>
> Hmmm, where can I see that null value? Which module are you referring to?
I don't know, hence my question
My reasoning is just that if Olivier's commit fixes a problem encountered by
your PDFBox job, that means that your job causes a null value in a module
display name (I simply read the little commit)
I just tested to create a PDFBox Jenkins job on my local machine, with Jenkins
1.559 and Jenkins's maven-plugin 2.2 and got no failure, nor job disappearing
I don't know if my local test has something that makes it not representative
But for the moment, I'm not sure that the comit will fix your PDFBox job
disappear problem: we'll see when the new plugin version is deployed :)
Regards,
Hervé
>
> > Regards,
> >
> > Hervé
>
> BR
> Andreas Lehmkühler
>
> > Le samedi 19 avril 2014 12:16:22 Olivier Lamy a écrit :
> >> Yup there is an issue in Jenkins.
> >> I fixed that
> >> https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cf
> >> ca
> >> 215b4eaec48613 I will try to release the jenkins plugin and update our
> >> instance.
> >> (tonight or tomorrow)
> >>
> >> On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
> >>> Hi,
> >>>
> >>> one of our PDFBox build jobs [1] somehow disappears. Does anyone know
> >>> why?
> >>> Is it just a jenkins hickup or did someone delete it accidentically? The
> >>> other 2 are still available [2], [3]
> >>>
> >>>
> >>> BR
> >>> Andreas Lehmkühler
> >>>
> >>> [1] https://builds.apache.org/job/PDFBox-trunk/
> >>> [2] https://builds.apache.org/job/PDFBox%201.8.x/
> >>> [3] https://builds.apache.org/job/PDFBox-ant/
Re: PDFBox build job disappears
Posted by Andreas Lehmkuehler <an...@lehmi.de>.
Hi,
Am 19.04.2014 08:13, schrieb Hervé BOUTEMY:
> IIUC, the display name of a PDFBox Maven module is causing harm because it is
> null: is it possible for Andreas just to change something in his project poms
> to avoid this null display name? I suppose such null display name won't be a
> great thing in other parts of Jenkins, but couldn't easily find how this value
> is calculated
Hmmm, where can I see that null value? Which module are you referring to?
> Regards,
>
> Hervé
BR
Andreas Lehmkühler
>
> Le samedi 19 avril 2014 12:16:22 Olivier Lamy a écrit :
>> Yup there is an issue in Jenkins.
>> I fixed that
>> https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cfca
>> 215b4eaec48613 I will try to release the jenkins plugin and update our
>> instance.
>> (tonight or tomorrow)
>>
>> On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
>>> Hi,
>>>
>>> one of our PDFBox build jobs [1] somehow disappears. Does anyone know why?
>>> Is it just a jenkins hickup or did someone delete it accidentically? The
>>> other 2 are still available [2], [3]
>>>
>>>
>>> BR
>>> Andreas Lehmkühler
>>>
>>> [1] https://builds.apache.org/job/PDFBox-trunk/
>>> [2] https://builds.apache.org/job/PDFBox%201.8.x/
>>> [3] https://builds.apache.org/job/PDFBox-ant/
>
Re: PDFBox build job disappears
Posted by Hervé BOUTEMY <he...@free.fr>.
IIUC, the display name of a PDFBox Maven module is causing harm because it is
null: is it possible for Andreas just to change something in his project poms
to avoid this null display name? I suppose such null display name won't be a
great thing in other parts of Jenkins, but couldn't easily find how this value
is calculated
Regards,
Hervé
Le samedi 19 avril 2014 12:16:22 Olivier Lamy a écrit :
> Yup there is an issue in Jenkins.
> I fixed that
> https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cfca
> 215b4eaec48613 I will try to release the jenkins plugin and update our
> instance.
> (tonight or tomorrow)
>
> On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
> > Hi,
> >
> > one of our PDFBox build jobs [1] somehow disappears. Does anyone know why?
> > Is it just a jenkins hickup or did someone delete it accidentically? The
> > other 2 are still available [2], [3]
> >
> >
> > BR
> > Andreas Lehmkühler
> >
> > [1] https://builds.apache.org/job/PDFBox-trunk/
> > [2] https://builds.apache.org/job/PDFBox%201.8.x/
> > [3] https://builds.apache.org/job/PDFBox-ant/
Re: PDFBox build job disappears
Posted by Andreas Lehmkuehler <an...@lehmi.de>.
Hi,
thanks for looking into this so fast!!
BR
Andreas Lehmkühler
Am 19.04.2014 04:16, schrieb Olivier Lamy:
> Yup there is an issue in Jenkins.
> I fixed that https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cfca215b4eaec48613
> I will try to release the jenkins plugin and update our instance.
> (tonight or tomorrow)
>
>
> On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
>> Hi,
>>
>> one of our PDFBox build jobs [1] somehow disappears. Does anyone know why?
>> Is it just a jenkins hickup or did someone delete it accidentically? The
>> other 2 are still available [2], [3]
>>
>>
>> BR
>> Andreas Lehmkühler
>>
>> [1] https://builds.apache.org/job/PDFBox-trunk/
>> [2] https://builds.apache.org/job/PDFBox%201.8.x/
>> [3] https://builds.apache.org/job/PDFBox-ant/
>
>
>
Re: PDFBox build job disappears
Posted by Olivier Lamy <ol...@apache.org>.
Yup there is an issue in Jenkins.
I fixed that https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cfca215b4eaec48613
I will try to release the jenkins plugin and update our instance.
(tonight or tomorrow)
On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
> Hi,
>
> one of our PDFBox build jobs [1] somehow disappears. Does anyone know why?
> Is it just a jenkins hickup or did someone delete it accidentically? The
> other 2 are still available [2], [3]
>
>
> BR
> Andreas Lehmkühler
>
> [1] https://builds.apache.org/job/PDFBox-trunk/
> [2] https://builds.apache.org/job/PDFBox%201.8.x/
> [3] https://builds.apache.org/job/PDFBox-ant/
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: PDFBox build job disappears
Posted by Andreas Lehmkühler <an...@lehmi.de>.
Hi,
> Andreas Lehmkuehler <an...@lehmi.de> hat am 18. April 2014 um 20:16
> geschrieben:
>
>
> Hi,
>
> one of our PDFBox build jobs [1] somehow disappears. Does anyone know why? Is
> it
> just a jenkins hickup or did someone delete it accidentically? The other 2 are
> still available [2], [3]
Sorry for the late feedback, but I guess everybody already noticed that the
build
reappears some time ago. The issue was an issue with a jenkins plugin.
> BR
> Andreas Lehmkühler
>
> [1] https://builds.apache.org/job/PDFBox-trunk/
> [2] https://builds.apache.org/job/PDFBox%201.8.x/
> [3] https://builds.apache.org/job/PDFBox-ant/
BR
Andreas Lehmkühler
Re: PDFBox build job disappears
Posted by Olivier Lamy <ol...@apache.org>.
Yup there is an issue in Jenkins.
I fixed that https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cfca215b4eaec48613
I will try to release the jenkins plugin and update our instance.
(tonight or tomorrow)
On 19 April 2014 04:16, Andreas Lehmkuehler <an...@lehmi.de> wrote:
> Hi,
>
> one of our PDFBox build jobs [1] somehow disappears. Does anyone know why?
> Is it just a jenkins hickup or did someone delete it accidentically? The
> other 2 are still available [2], [3]
>
>
> BR
> Andreas Lehmkühler
>
> [1] https://builds.apache.org/job/PDFBox-trunk/
> [2] https://builds.apache.org/job/PDFBox%201.8.x/
> [3] https://builds.apache.org/job/PDFBox-ant/
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy