Hi,
could someone please change back the number of "build processors" for the
"lucene" Jenkins node to 1? Currently it executes always 2 Jobs in parallel.
The underlying server only has 4 cpu cores and the Lucene Job configuration is
done in a way that it uses all available CPU nodes, so runnin
> On 20 Aug 2015, at 9:17 am, Uwe Schindler wrote:
>
> Hi,
>
> could someone please change back the number of "build processors" for the
> "lucene" Jenkins node to 1? Currently it executes always 2 Jobs in parallel.
> The underlying server only has 4 cpu cores and the Lucene Job configuration
Hi,
The backlog of Lucene is generally large. That's wanted, because we don't
trigger builds based on commits; just to always have one build of everything in
the queue we do it time-based. Because of our pseudorandomized test
infrastructure, the build slave should never be out of work because e
> On 20 Aug 2015, at 10:28 am, Uwe Schindler wrote:
>
> Hi,
>
> The backlog of Lucene is generally large. That's wanted,
No problem, thanks for letting me know, I’ll take that into account in the
future.
> because we don't trigger builds based on commits; just to always have one
> build of
> On 20 Aug 2015, at 7:55 am, Daan Hoogland wrote:
>
> cloudstack...! we started making more intensive use of pull-builders. the
> old pull-request build job is replaced by a rat and an analysis job. Maybe
> others have done so as well but I am sure we (ACS) are a culprit in this.
From what I c
> On 20 Aug 2015, at 4:03 am, David Nalley wrote:
>
> Whatever we are using for DNS on those build slaves is redirecting any
> NXDOMAIN to a Level3 search domain.
>
> Is this happening on the ubuntu-* slaves or on the dynamic build slaves?
It was mentioned earlier :
> I am certainly seeing t
> On 20 Aug 2015, at 3:28 am, David Nalley wrote:
>
> So, just spot checking some of the dynamic build slaves - historically
> those have spun up a few hours at a time, to give us additional
> capacity when our queue spiked - but it looks like the slaves are
> staying online pretty much all of t
> On 20 Aug 2015, at 2:18 am, David Nalley wrote:
>
>
> ...how many additional
> build nodes/executors will satiate our current demand for capacity?
I know this was not aimed at me but I’ll give my opinion.
From what I’ve seen of the current growth over the last year; and to allow for
future
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704738#comment-14704738
]
Gavin commented on BUILDS-106:
--
maven-archetype: maven 3.0.3 -> maven 3.2.2 :: jdk 1.6.0_24 -
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704745#comment-14704745
]
Gavin edited comment on BUILDS-106 at 8/20/15 12:15 PM:
maven-doxi
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704745#comment-14704745
]
Gavin commented on BUILDS-106:
--
maven-doxia: maven 3.0.4 -> maven 3.2.2 :: jdk 1.1.0_45 -> no
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704751#comment-14704751
]
Gavin commented on BUILDS-106:
--
maven-parent-pom: maven 3.0.3 -> maven 3.2.2 :: jdk 1.6.0_24
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704759#comment-14704759
]
Gavin commented on BUILDS-106:
--
maven-plugin-tools: maven 3.0.4 -> maven 3.2.2 :: jdk 1.6.0_2
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704768#comment-14704768
]
Gavin commented on BUILDS-106:
--
maven-release: maven 3.0.4 -> maven 3.2.2 :: jdk 1.7.0_65 ->
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704789#comment-14704789
]
Gavin commented on BUILDS-106:
--
maven-shared: maven 3.0.5 -> maven 3.2.2 :: jdk 1.7.0_51 -> n
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704807#comment-14704807
]
Gavin commented on BUILDS-106:
--
maven-surefire: maven 3.0.4 -> maven 3.2.2 :: jdk 1.6.0_24 ->
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704817#comment-14704817
]
Gavin commented on BUILDS-106:
--
maven-wagon: maven 3.0.4 -> maven 3.2.2 :: jdk 1.6.0_24 - no
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704825#comment-14704825
]
Gavin commented on BUILDS-106:
--
tomcat-maven-plugin: maven 3.1.1 -> maven 3.2.2 :: jdk 1.6.0_
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704841#comment-14704841
]
Gavin commented on BUILDS-106:
--
asf-paren-pom: maven 3.0.3 -> maven 3.2.2 :: jdk 1.6.0_24 ->
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704842#comment-14704842
]
Gavin commented on BUILDS-106:
--
let me know if I need to do anything this side for the failur
[
https://issues.apache.org/jira/browse/BUILDS-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin closed BUILDS-89.
---
Resolution: Fixed
ok so I installed a toolchains.xml into ubuntu3 and tied your build to it.
ran fine and passed.
htt
So the Yahoo! provided slaves (H*, ubuntu-*) do have Level3's DNS servers
in /etc/resolv.conf - we don't actually control that directly, it's part of
the system setup Y! uses, I think. I'll ping our contact at Y! about
changing them to use more standard DNS.
A.
On Thu, Aug 20, 2015 at 6:15 AM, Ga
On Thu, Aug 20, 2015 at 6:32 AM, Gavin McDonald wrote:
>
>> On 20 Aug 2015, at 2:18 am, David Nalley wrote:
>>
>>
>
>> ...how many additional
>> build nodes/executors will satiate our current demand for capacity?
>
> I know this was not aimed at me but I’ll give my opinion.
>
> From what I’ve se
On Thu, Aug 20, 2015 at 2:55 AM, Daan Hoogland wrote:
> cloudstack...! we started making more intensive use of pull-builders. the
> old pull-request build job is replaced by a rat and an analysis job. Maybe
> others have done so as well but I am sure we (ACS) are a culprit in this.
>
I thought a
Yeah, I don't think we need physical nodes - leasing hosts somewhere would
be perfectly fine. If we did go with physical nodes, I'd guess that five
would probably be fine for the next year, split into multiple
VMs/containers.
I'm working on getting stats/graphs - should hopefully have that ready i
On Thu, Aug 20, 2015 at 5:02 PM, David Nalley wrote:
> On Thu, Aug 20, 2015 at 2:55 AM, Daan Hoogland
> wrote:
> > cloudstack...!
>
> I thought all of the ACS PR builds were happening on Travis?
>
only smoke tests, no code analysis
.
> --David
>
--
Daan
Andrew Bayer created BUILDS-110:
---
Summary: Set up Jenkins job linter/rules enforcer
Key: BUILDS-110
URL: https://issues.apache.org/jira/browse/BUILDS-110
Project: Infra Build Platform
Issue Typ
Andrew Bayer created BUILDS-111:
---
Summary: Auto-cleanup job for orphaned Java processes on builds.a.o
Key: BUILDS-111
URL: https://issues.apache.org/jira/browse/BUILDS-111
Project: Infra Build Platform
[
https://issues.apache.org/jira/browse/BUILDS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705228#comment-14705228
]
Gavin commented on BUILDS-85:
-
[~mgrigorov] and everyone else here - I've deployed a toolchains
[
https://issues.apache.org/jira/browse/BUILDS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705269#comment-14705269
]
Andrew Bayer commented on BUILDS-111:
-
Gonna need to restart Jenkins to install the gr
[
https://issues.apache.org/jira/browse/BUILDS-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705313#comment-14705313
]
Krzysztof Sobkowiak commented on BUILDS-108:
It seems to work correctly now
>
[
https://issues.apache.org/jira/browse/BUILDS-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer reassigned BUILDS-108:
---
Assignee: Andrew Bayer
> Problem with ServiceMix-Bundles Jenkins job
> --
Yup,
http://drewgraybeal.blogspot.com/2015/05/level-3-dns-hijacking-4222-and-others.html
-
level3 is hijacking NXDOMAIN now. I think Y!'s DHCP is setting those DNS
servers? Rajiv, can you comment?
A.
On Thu, Aug 20, 2015 at 10:32 AM, Andrew Bayer
wrote:
> So the Yahoo! provided slaves (H*, ubun
[
https://issues.apache.org/jira/browse/BUILDS-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705326#comment-14705326
]
Andrew Bayer commented on BUILDS-108:
-
A whole lot of things were in messed up states
FYI, I've manually overwritten /etc/resolv.conf on all the H* and ubuntu-*
slaves with something more valid.
A.
On Thu, Aug 20, 2015 at 1:16 PM, Andrew Bayer
wrote:
> Yup,
> http://drewgraybeal.blogspot.com/2015/05/level-3-dns-hijacking-4222-and-others.html
> -
> level3 is hijacking NXDOMAIN n
[
https://issues.apache.org/jira/browse/BUILDS-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705351#comment-14705351
]
Krzysztof Sobkowiak commented on BUILDS-108:
[~abayer] thanks for your help
>
I noticed a lot of jobs that were running every day regardless of whether
anything changed and eating up a lot of executors, so I bulk-removed all of
them, changing those jobs to poll for changes hourly instead. If your
project has one or two jobs that you need to run daily whether there are
code c
[
https://issues.apache.org/jira/browse/BUILDS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705384#comment-14705384
]
Martin Grigorov commented on BUILDS-85:
---
[~ipv6guru] You rock, man!
> Could not gene
[
https://issues.apache.org/jira/browse/BUILDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705410#comment-14705410
]
Hervé Boutemy commented on BUILDS-106:
--
thank you Gavin
here are next steps, please:
So it looks like part of the problem is that HBase builds have been
hanging/causing slaves to barf out due to orphaned java processes eating up
resources. They're looking into this over at
https://issues.apache.org/jira/browse/INFRA-10150.
On Thu, Aug 20, 2015 at 11:44 AM, Daan Hoogland
wrote:
>
[
https://issues.apache.org/jira/browse/BUILDS-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin reassigned BUILDS-14:
---
Assignee: Gavin
> Install RVM on ubuntu-* slaves
> --
>
> Key: BUI
[
https://issues.apache.org/jira/browse/BUILDS-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin closed BUILDS-14.
---
Resolution: Fixed
yeah done a while ago.
> Install RVM on ubuntu-* slaves
> --
>
>
[
https://issues.apache.org/jira/browse/BUILDS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705777#comment-14705777
]
Martin Grigorov commented on BUILDS-85:
---
[~ipv6guru] Just tried it and the build at B
[
https://issues.apache.org/jira/browse/BUILDS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705806#comment-14705806
]
Gavin commented on BUILDS-85:
-
check it out for yourself:
https://github.com/apache/infrastruc
[
https://issues.apache.org/jira/browse/BUILDS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705811#comment-14705811
]
Gavin commented on BUILDS-85:
-
Oh I see whats happening.
Most people in this ticket have been
Hi Andrew,
see my mail thread about the Lucene builds this morning with Gav:
> From: Uwe Schindler [mailto:u...@thetaphi.de]
> Sent: Thursday, August 20, 2015 11:28 AM
> To: builds@apache.org
> Subject: Re: Number of build prozessors on Lucene node
>
> Hi,
>
> The backlog of Lucene is generally
[
https://issues.apache.org/jira/browse/BUILDS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705829#comment-14705829
]
Gavin commented on BUILDS-85:
-
Just added toolchains.xml to buildbot slave 18 so you can try th
Yeah, that's fine - the only viable way to do this was across the board, so
I'm sorry for messing with your jobs. =)
On Aug 20, 2015 17:41, "Uwe Schindler" wrote:
> Hi Andrew,
>
> see my mail thread about the Lucene builds this morning with Gav:
>
> > From: Uwe Schindler [mailto:u...@thetaphi.de]
Using google public dns should be fine.
Removed yahoo in colo resolver, 67.195.2.197 which is accessible from hosted
apache nodes. DHCPD configs is also updated to issue revolvers as
8.8.8.8/8.8.4.4 .
-rajive
From: Andrew Bayer
To: "builds@apache.org"
Cc: Keith W ; Rajiv Chittajall
49 matches
Mail list logo
