On 31/10/12 00:23, Jesse Glick wrote:
> On 10/30/2012 05:48 AM, Edward Cullen wrote:
>> We've just hit this in our production environment:
>>
>> JENKINS-15369 - NPE from Jenkins.removeNode
>
> Do you have any idea how to reproduce? If so, do 300bfc4 & 87d9a6e help?
>
> CloudBees encountered this
Grr, my bad.
The new mainline release on Sunday flushed the queue and pushed
everything to the site properly.
2012/10/27 Vojtech Juranek :
> On Wednesday 24 October 2012 21:01:24 Kohsuke Kawaguchi wrote:
>> RC posted.
>
> unfortunately it's not propagated to the mirrors and cannot be downloaded.
On 10/30/2012 05:48 AM, Edward Cullen wrote:
We've just hit this in our production environment:
JENKINS-15369 - NPE from Jenkins.removeNode
Do you have any idea how to reproduce? If so, do 300bfc4 & 87d9a6e help?
CloudBees encountered this NPE in our hosted Jenkins instances, we are guessing
On 21/10/12 21:54, Vojtech Juranek wrote:
> Hi,
> as agreed on the last Jenkins meeting [1], next LTS will be based on 1.480.
> I identified and backported following bug fixes:
We've just hit this in our production environment:
JENKINS-15369 - NPE from Jenkins.removeNode [1]
Eddy
[1] https://is
On Wednesday 24 October 2012 21:01:24 Kohsuke Kawaguchi wrote:
> RC posted.
unfortunately it's not propagated to the mirrors and cannot be downloaded.
Could you (or someone with admin access - rtyler?) take a look and put it to
the mirrors?
Thanks
Vojta
> @Kohsuke would you mind re-spin RC to include this fix? It passed all tests
> [1].
or, taken into account that backported fix/workaround is just wrapping one line
into try-catch block, new RC is probably not needed at all. I'll start testing
today with original RC
Hi,
> Suggestion: backport f50316b which is pretty small and should be
> safe;
done
> Nickolay’s patch (if extended as mentioned above) would be about as
> good for a backport but has not been tested in trunk.
as this is not even in trunk yet, I don't include this patch
> I hope it is not to
I forgot to bring up JENKINS-13202 [1], relating to problems archiving due to advanced filesystem operations (esp. symlinks) on relatively unusual operating systems,
which is a little complicated:
1. 95c1728 made an improvement, but this was already in 1.467 (and an even
earlier e15b2e1 in 1.46
2012/10/25 Vojtech Juranek
> FYI: on JonJ there are some failed tests because of time out [1], on our
> instance it passed without any failure [2], so there shouldn't be any
> regressions caused by backporting
>
> [1]
> https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_lts_branch/75/
> [2
RC posted.
2012/10/24 Vojtech Juranek :
> FYI: on JonJ there are some failed tests because of time out [1], on our
> instance it passed without any failure [2], so there shouldn't be any
> regressions caused by backporting
>
> [1] https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_lts_branc
FYI: on JonJ there are some failed tests because of time out [1], on our
instance it passed without any failure [2], so there shouldn't be any
regressions caused by backporting
[1] https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_lts_branch/75/
[2] http://ci.jboss.org/hudson/job/HTS-Jen
On Tuesday 23 October 2012 15:40:16 Jesse Glick wrote:
> On 10/23/2012 03:33 PM, Vojtech Juranek wrote:
> > https://issues.jenkins-ci.org/browse/JENKINS-15206
>
> You merged the main commit but not the follow-up 06514d2.
it's already there (got a notification from failing test
hudson.model.ViewT
On 10/23/2012 03:33 PM, Vojtech Juranek wrote:
https://issues.jenkins-ci.org/browse/JENKINS-15206
You merged the main commit but not the follow-up 06514d2.
> JENKINS-15494 [4] is too new I guess, by a couple of days.
>
>
> [1] https://issues.jenkins-ci.org/browse/JENKINS-7214
> [2] https://issues.jenkins-ci.org/browse/JENKINS-15206
> [3] https://issues.jenkins-ci.org/browse/JENKINS-15226
> [4] https://issues.jenkins-ci.org/browse/JENKINS-15494
[1,
On 10/21/2012 04:54 PM, Vojtech Juranek wrote:
any other critical or blocker issues need to be backported to 1.480.1
JENKINS-7214 [1] should be considered; large installations can be slowed to a
crawl by this longstanding issue. Ditto JENKINS-15206 [2]. Neither are trivial
fixes, though.
JEN
I'm flying back to home today, and planning to take a sweep Tuesday afternoon.
2012/10/22 Vojtech Juranek :
> Hi,
> as agreed on the last Jenkins meeting [1], next LTS will be based on 1.480.
> I identified and backported following bug fixes:
>
> JENKINS-13336 Invalid JSON is produced during remot
Done
On Monday 22 October 2012 09:19:45 Nord, James wrote:
> I would like to nominate JENKINS-15382 [1]
>
> Not a critical or blocker, but it caused me some intermittent grief. (and
> I've been running this in production backported to 1.466.2 thanks to
> Cloudbees)
>
> /James
>
> [1] https://is
I would like to nominate JENKINS-15382 [1]
Not a critical or blocker, but it caused me some intermittent grief. (and I've
been running this in production backported to 1.466.2 thanks to Cloudbees)
/James
[1] https://issues.jenkins-ci.org/browse/JENKINS-15382.
> -Original Message-
> Fro
I guess this marker is that the issue is either "blocker" or "critical" (+ the
fix has to be in Jenkins for at least cca 2 weeks).
I'm asking because someone could forget to bump the issue to critical (default
is "major") or I can miss something (both happened in the past).
On Monday 22 Octob
Makes me wonder : can we have some way on Jira to tag issues as "*request
backport to LTS*", so that LTS management would not require you to do such
a reminder ?
2012/10/21 Vojtech Juranek
> Hi,
> as agreed on the last Jenkins meeting [1], next LTS will be based on 1.480.
> I identified and back
20 matches
Mail list logo
