We were seeing a steady increase in the time taken by our builds to
complete, eventually reaching the time out we had set at 30 minutes,
then reaching the time out we had raised to 40 minutes in order to have
a build... since Winston started working on this and switching to jetty,
all the build
I was kidding yesterday, but after 24 hours, I'll echo other people's
comments here ... Hudson on Jetty, seems like we have a winner.
Many thanks to Winston and Jesse for helping out.
On 02/28/2012 04:28 PM, Denis Roy wrote:
> Yeah, nice try, buddy.
>
> Man, is it just me, or has Hudson been s
Actually, for the record, it wasn't the IDE build, it was the kernel build that
had the 27GB usage. But it looks like someone else on Virgo team has taken care
of that.
On Feb 29, 2012, at 11:13 AM, Miles Parker wrote:
> I hadn't thought to look and had no idea we were using up so many resourc
I hadn't thought to look and had no idea we were using up so many resources :O,
thanks for the heads up. I've set us up to keep 30 builds (we need some back
history at the dependencies are evolving rapidly) but only the last five
artifacts. That should reduce things up nicely. :)
On Feb 29, 201
The Hudson UI had been very responsive since these changes were made. I
haven't seen any network timeouts either when trying to contact slaves.
Kudos to all those involved in making these improvements. Much
appreciated!
Kim
From: Winston Prakash
To: Cross project issues
Date: 02
(Please ignore this one -- it's the same as yesterday)
On 02/29/2012 01:06 PM, ge...@eclipse.org wrote:
> Compiled 2012-02-29T12:07
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo
Compiled 2012-02-29T12:07
build.eclipse.org
-> Usage exceeding 1GB for: Hudson master jobs and workspace (2012-02-29T10:00)
17.9G eclipse-equinox-test-N
3.8G cbi-scout-3.7
3.0G cbi-pdt-3.0-indigo
2.9G cbi-pdt-2.2-helios
2.1G emf-cdo-integration
2.1G Xtext-nightly-HEAD
Thanks Borislav. We'll update the CQs to add the keyword for you.
Regards,
Janet
From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Borislav
Kapukaranov
Sent: Wednesday, February 29, 2012 3:05 AM
To: Cross project issues
Does it have nested jars? And is Java 1.7 involved? If so, you might read
through
https://bugs.eclipse.org/bugs/show_bug.cgi?id=361628
But, other than that, I think many projects have occasionally found issues
where some jars simply can not be "packed200'd" correctly and for those
cases must be e
that is a new one to me...
if you find it an issue in the plugin open an issue on the dash
project and ping me
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Wed, Feb 29, 2012 at 09:07, Zeb Ford-Reitz wrote:
> We recently made the switch over to the eclipse-signing-maven-plugin for
>
We recently made the switch over to the eclipse-signing-maven-plugin for
repacking, signing, and packing the Jubula project, using
https://hudson.eclipse.org/hudson/job/linuxtools-Indigo as a reference
(for job and pom). After the switch, I noticed that the produced p2
repository contained at l
Hi Janet,
We went through the rt.virgo CQs and dropped a comment in them but they
still don't show up in the Juno search.
How can we add the Juno keyword to the CQs?
Thanks,
Borislav
On Tue, Feb 28, 2012 at 11:52 PM, Janet Campbell wrote:
> Hi Tom,
>
> I only need updates for CQs that are not
12 matches
Mail list logo
