Well, quite simple.
As 1.485 was the last version, 1.486 is gonna be in the beginning of next
week (previous sunday, actually): see http://jenkins-ci.org/changelog.
About migrating onto LTS, this subject has already be debated here. The
most conservative solution is to keep your current Jenkins ve
On Wed, Oct 10, 2012 at 7:54 AM, Dirk Kuypers wrote:
> Hi,
>
> this bug: https://issues.jenkins-ci.org/browse/JENKINS-15335
>
> is fixed with 1.486.
Is there an ETA on when this will hit the autoupdate servers? 1.485
blew up all the APIs I was using, which causes our scripts to spam
tickets to GH
Hi,
this bug: https://issues.jenkins-ci.org/browse/JENKINS-15335
is fixed with 1.486.
BR
Dirk
2012/10/10 Michaël Pailloncy :
> Hi,
>
> I've faced with the same issue with 1.484.
>
> Michaël
>
>
> 2012/10/10 Pawel
>>
>> Hello,
>>
>> After upgrading from 478 to 485 I have the following issue:
>>
Hi,
I've faced with the same issue with 1.484.
Michaël
2012/10/10 Pawel
> Hello,
>
> After upgrading from 478 to 485 I have the following issue:
>
> If there are some jobs in the job queue after a while they will disappear
> and I will get "No builds in the queue.". It is purely a GUI issue, a
Hello,
After upgrading from 478 to 485 I have the following issue:
If there are some jobs in the job queue after a while they will disappear
and I will get "No builds in the queue.". It is purely a GUI issue, as
refreshing the page shows the jobs again. Rather frustrating though.
