Re: [cross-project-issues-dev] Hudson Jetty conversion

2012-03-05 Thread Markus Knauer 
It's still broken. I've added *Bug
373325*-
/shared/technology
read-only for EPP Hudson build jobs in order to track this.

Thanks,
Markus

On Mon, Mar 5, 2012 at 22:29, Denis Roy  wrote:

>  /shared isn't explicitly read-only.  I think Matt was referring to the
> fact that the hudsonbuild user does not have write access to
> /shared/technology.  I'm re-running some ACL scripts -- please let me know
> if this is still broken for you in a few hours from now.
>
> Denis
>
>
>
>
>
>
> On 03/05/2012 10:20 AM, Markus Knauer wrote:
>
> Thanks for that info... is the read-only access to /shared permanent, or
> will it be changed in the (near) future to its old state? My understanding
> was that this is the place where we could store and work with possibly
> large build artifacts.
>
> Sorry if this has been asked somewhere else, but there are so many
> discussions around Hudson that I may have missed one.
>
> Thanks,
> Markus
>
>
> On Mon, Mar 5, 2012 at 16:05, Webmaster(Matt Ward) 
> wrote:
>
>>
>>  One is the web interface. It's painful slow today and/or I am getting
>>> our 'Bad Gateway' error. The same problems are shown when I try to update
>>> any of my job configurations. Maybe it's a bandwidth problem, maybe a
>>> problem with Hudson. Are others having the same problem?
>>>
>>  The interface seems responsive from here.  In the past the gateway error
>> has implied that Winstone(no longer used) was running out of resources to
>> serve content.  But I also see a 'flood' of requests today from:
>>
>> Commissariat a l'Energie Atomique 904
>> SAP AG, Walldorf   842
>>
>> So it may just be bandwidth/load.
>>
>>  The next problem is the file system access. Is /shared/technology
>>> available or what's the status there? I thought it should be accessible but
>>> every attempt to create/add/modify anything there ends up with error
>>> messages like this
>>>
>>  It's mounted, but the Hudson user/group has no access(ownership) on that
>> dir so it can only read.
>>
>>
>> -Matt.
>> --
>>
>> Eclipse WebMaster - webmas...@eclipse.org
>>
>> Questions? Consult the WebMaster FAQ at
>> http://wiki.eclipse.org/index.php/Webmaster_FAQ
>> View my status at http://wiki.eclipse.org/index.php/WebMaster
>>
>> EclipseCon 2012 
>>   ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
>
>
> ___
> cross-project-issues-dev mailing 
> listcross-project-issues-dev@eclipse.orghttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Juno M6 is not far away ... are you still greedy?

2012-03-05 Thread Eike Stepper 

Am 06.03.2012 07:27, schrieb Thomas Hallgren:

It's just been assembled and published to 
http://download.eclipse.org/tools/buckminster/headless-4.2.


That gives me this error:

 [echo] Installing director
  [get] Getting: 
http://download.eclipse.org/tools/buckminster/products/director_latest.zip
  [get] To: /tmp/director-1603735546.zip
[unzip] Expanding: /tmp/director-1603735546.zip into 
/opt/users/hudsonbuild/.hudson/jobs/emf-cdo-integration/workspace/tools

   [delete] Deleting: /tmp/director-1603735546.zip
 [echo]
 [echo] Installing buckminster
 [java] Installing org.eclipse.buckminster.cmdline.product 
1.5.0.v20120304-2134.
 [java] Installing 
org.eclipse.buckminster.core.headless.feature.feature.group 
1.5.0.v20120304-2134.
 [java] Installing 
org.eclipse.buckminster.pde.headless.feature.feature.group 1.5.0.v20120304-2134.
 [java] Installing 
org.eclipse.buckminster.git.headless.feature.feature.group 1.5.0.v20120304-2144.
 [java] Cannot complete the install because one or more required items 
could not be found.
 [java]  Software being installed: Buckminster - Headless PDE support 1.5.0.v20120304-2134 
(org.eclipse.buckminster.pde.headless.feature.feature.group 1.5.0.v20120304-2134)
 [java]  Missing requirement: PDE Core 3.8.0.v20120118-1658 (org.eclipse.pde.core 3.8.0.v20120118-1658) requires 
'bundle org.eclipse.equinox.p2.repository.tools [2.0.100,3.0.0)' but it could not be found

 [java]  Cannot satisfy dependency:
 [java]   From: Buckminster - Headless PDE support 1.5.0.v20120304-2134 
(org.eclipse.buckminster.pde.headless.feature.feature.group 1.5.0.v20120304-2134)

 [java]   To: org.eclipse.pde.core 0.0.0
 [java] Application failed, log file location: 
/opt/public/jobs/emf-cdo-integration/workspace/tools/director/configuration/1331019316932.log

 [java] Installation failed.

Do I need to use a different director or use it differently?

And:

Is http://download.eclipse.org/tools/buckminster/updates-4.2 supposed to be 
functional? I'm getting this error in my IDE:

Cannot complete the install because one or more required items could not be 
found.
  Software being installed: Buckminster - Core 1.5.0.v20120304-2134 (org.eclipse.buckminster.core.feature.feature.group 
1.5.0.v20120304-2134)
  Missing requirement: Buckminster Core 1.3.0.v20120304-2134 (org.eclipse.buckminster.core 1.3.0.v20120304-2134) 
requires 'bundle org.eclipse.equinox.p2.core [2.2.0,3.0.0)' but it could not be found

  Cannot satisfy dependency:
From: Buckminster - Core 1.5.0.v20120304-2134 
(org.eclipse.buckminster.core.feature.feature.group 1.5.0.v20120304-2134)
To: org.eclipse.buckminster.core [1.3.0.v20120304-2134]

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] p2 repositories ... we can do better

2012-03-05 Thread Matthias Sohn 
2012/3/6 Jesse McConnell 

> please don't let my 'silly' comment derail the conversation here...it
> was perhaps a careless word I threw out
>
> anything that improves peoples experience with p2 would be a good
> thing because right now for me it is still this black box that is a
> bit hit or miss in terms of what is in it, what comes out of it, and
> how its all organized
>
> I am sure people can say the same about maven central, but 5 minutes,
> a web browser and a bit of investigative spirit and clicking around
> can sort that out...
>
> by about the 5th jar file I have cracked open and sorting through
> MANIFEST.MF files...that is where the eye glazing comes in from my
> previous statement :)
>
> so by all means please continue improving p2 repositories!  and if the
> eclipse-signing-maven-plugin is supposed to be doing anything from
> this conversation please bring that to my attention directly!


could the eclipse-signing-maven-plugin provide a parameter to
inject the p2.mirrorsURL property into artifact repositories and
parameters to generate the p2.index file ?

-- 
Matthias
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Juno M6 is not far away ... are you still greedy?

2012-03-05 Thread Thomas Hallgren 

Hi Eike,


On 2012-03-06 07:20, Eike Stepper wrote:

Hi David,

Thank you for pointing our all these issues. Unfortunately this 
confuses me a lot. Some questions:


1) Do I have to understand all this? Or
2) Is it just a matter of using a 3.8 Buckminster? And if so

With respect to the optional dependencies, yes. That's all there's to it.


2.1) Where is it?

It's just been assembled and published to 
http://download.eclipse.org/tools/buckminster/headless-4.2.


- thomas


Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper



Am 06.03.2012 04:39, schrieb David M Williams:



I've added a new report to the common repository reports [1].

It is called "Optional Runtime Requirements and Greediness" [2]

I doubt it is too useful at the moment, except to reflect the 
magnitude of
the problem ... that many projects still have to move up to a more 
recent
publisher. Ideally, by M6 or M7, the first 2 or 3 lists in that 
report will
all be "0" (indicating we all are using the new p2 publisher) but 
they are
currently in the hundreds. The reports do not currently track back to 
"who
is responsible" for using the old publisher, but I might add that 
when the
list gets smaller. As it is, the reporting code is simply looking at 
only
the "which

IU required it.

As I mentioned in another note on this topic[3], the p2 publisher as of
Juno M1 began to publish "greedy=false" for those requirements which are
optional at runtime. The previous, implied default was 
"greedy=true".  This

better meets users and adopters expectations.

According to Thomas Hallgren[1], the Buckminster builder will use the 
new

publisher "by M6" so, not sure if that will be in time for you
Buckminster-builders to take advantage of for your own M6 
contribution to
Juno M6, but you might keep a close eye on it, and plan on changing 
shortly

after M6 if not before.

According to Igor Fedorenko [5] Tycho uses 3.8-based publisher and
generates non-greedy optional dependencies since version 0.13. So, I 
hope
everyone who uses Tycho has or can soon move up to that version (or, 
what

ever is their latest recommended version).

So, if you haven't yet, please do try and move up to a Juno based p2
publisher as soon as possible so we can do more testing on what we will
release and find problems or surprises early. I suspect some of the
anomalies in the report (such as com.ibm.icu sometimes required greedily
and sometime not) is a side effect of people using "old" Orbit builds 
for
their deliverables.? Orbit is planning to provide a Juno M6 usable 
S-build

this Friday 3/9, so everyone should be able to move up to latest Orbit S
build next week.

While the reports may not be too useful to your individual project at 
the
moment (since, it is just a big list, without saying who's to 
"blame") you
might find it interesting. I thought it would make a good excuse to 
give a

timely reminder to upgrade your p2 publisher.

Remember, M6+0 is 03/16 and M6 complete and available on Friday, 
03/23 [6]
which is significant because that is immediately before EclipseCon! 
It is a

challenge every year to make sure we get it done before people have to
start traveling!

Much thanks,


[1] http://build.eclipse.org/juno/simrel/
[2]
http://build.eclipse.org/juno/simrel/reporeports/reports/greedyReport.html 


[3]
http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg07098.html 


[4] http://dev.eclipse.org/mhonarc/lists/buckminster-dev/msg01320.html
[5]
http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg07100.html 


[6] http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Juno M6 is not far away ... are you still greedy?

2012-03-05 Thread Eike Stepper 

Hi David,

Thank you for pointing our all these issues. Unfortunately this confuses me a 
lot. Some questions:

1) Do I have to understand all this? Or
2) Is it just a matter of using a 3.8 Buckminster? And if so
2.1) Where is it?

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper



Am 06.03.2012 04:39, schrieb David M Williams:



I've added a new report to the common repository reports [1].

It is called "Optional Runtime Requirements and Greediness" [2]

I doubt it is too useful at the moment, except to reflect the magnitude of
the problem ... that many projects still have to move up to a more recent
publisher. Ideally, by M6 or M7, the first 2 or 3 lists in that report will
all be "0" (indicating we all are using the new p2 publisher) but they are
currently in the hundreds. The reports do not currently track back to "who
is responsible" for using the old publisher, but I might add that when the
list gets smaller. As it is, the reporting code is simply looking at only
the "http://build.eclipse.org/juno/simrel/
[2]
http://build.eclipse.org/juno/simrel/reporeports/reports/greedyReport.html
[3]
http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg07098.html
[4] http://dev.eclipse.org/mhonarc/lists/buckminster-dev/msg01320.html
[5]
http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg07100.html
[6] http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] p2 repositories ... we can do better

2012-03-05 Thread Ian Bull 
Here is a link to the bug report:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=361628

cheers,
ian

On Mon, Mar 5, 2012 at 9:59 PM, Ian Bull  wrote:

> Sorry, a little late to this game, but another small thing.  While David
> mentioned the use of packed jars, please keep the unpacked jars around too.
>  We have found that the Java 7 pack/un-packer has changed (compared to
> previous versions), and we are having trouble processing pack.gz files on
> Java 7 Runtimes.  If the un-packed jars are still around, p2 can fall back
> to these.
>
> Cheers,
> Ian
>
> On Mon, Mar 5, 2012 at 5:36 PM, Jesse McConnell  > wrote:
>
>> please don't let my 'silly' comment derail the conversation here...it
>> was perhaps a careless word I threw out
>>
>> anything that improves peoples experience with p2 would be a good
>> thing because right now for me it is still this black box that is a
>> bit hit or miss in terms of what is in it, what comes out of it, and
>> how its all organized
>>
>> I am sure people can say the same about maven central, but 5 minutes,
>> a web browser and a bit of investigative spirit and clicking around
>> can sort that out...
>>
>> by about the 5th jar file I have cracked open and sorting through
>> MANIFEST.MF files...that is where the eye glazing comes in from my
>> previous statement :)
>>
>> so by all means please continue improving p2 repositories!  and if the
>> eclipse-signing-maven-plugin is supposed to be doing anything from
>> this conversation please bring that to my attention directly!
>>
>> cheers,
>> jesse
>>
>> --
>> jesse mcconnell
>> jesse.mcconn...@gmail.com
>>
>>
>>
>> On Sat, Mar 3, 2012 at 07:02, Jesse McConnell 
>> wrote:
>> > the eclipse-signing-maven-plugin takes care of some of it but reading
>> > over the original mail I sort of glazed over and didn't really pick up
>> > on where else it ought to have helped address things...
>> >
>> > so from my view the index and mirror files goop is stuff in tycho land
>> >
>> > if anyone picks up on a shortcoming of the signing plugin do chirp up
>> > and let us know...past that igor will likely know more on the p2
>> > details, I still find it a bit silly. :)
>> >
>> > cheers,
>> > jesse
>> >
>> > --
>> > jesse mcconnell
>> > jesse.mcconn...@gmail.com
>> >
>> >
>> >
>> > On Sat, Mar 3, 2012 at 03:08, Marcel Bruch 
>> wrote:
>> >> I'm evaluating how to make our repositories comply to these needs with
>> our tycho build. Maybe some successful tycho user or tycho committer can
>> comment on how to support pack200, p2.index files, and p2.mirrorsURL?
>> >>
>> >> To me it sounds like these configuration options should be part of the
>> repository packaging but at least I haven't found them. Are there any
>> options to "switch on" these things? Or is there a set of plug-ins to use
>> that will do the trick?
>> >>
>> >> Thanks,
>> >> Marcel
>> >>
>> >>
>> >> ___
>> >> cross-project-issues-dev mailing list
>> >> cross-project-issues-dev@eclipse.org
>> >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
>
> --
> R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
> http://eclipsesource.com | http://twitter.com/eclipsesource
>



-- 
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] p2 repositories ... we can do better

2012-03-05 Thread Ian Bull 
Sorry, a little late to this game, but another small thing.  While David
mentioned the use of packed jars, please keep the unpacked jars around too.
 We have found that the Java 7 pack/un-packer has changed (compared to
previous versions), and we are having trouble processing pack.gz files on
Java 7 Runtimes.  If the un-packed jars are still around, p2 can fall back
to these.

Cheers,
Ian

On Mon, Mar 5, 2012 at 5:36 PM, Jesse McConnell
wrote:

> please don't let my 'silly' comment derail the conversation here...it
> was perhaps a careless word I threw out
>
> anything that improves peoples experience with p2 would be a good
> thing because right now for me it is still this black box that is a
> bit hit or miss in terms of what is in it, what comes out of it, and
> how its all organized
>
> I am sure people can say the same about maven central, but 5 minutes,
> a web browser and a bit of investigative spirit and clicking around
> can sort that out...
>
> by about the 5th jar file I have cracked open and sorting through
> MANIFEST.MF files...that is where the eye glazing comes in from my
> previous statement :)
>
> so by all means please continue improving p2 repositories!  and if the
> eclipse-signing-maven-plugin is supposed to be doing anything from
> this conversation please bring that to my attention directly!
>
> cheers,
> jesse
>
> --
> jesse mcconnell
> jesse.mcconn...@gmail.com
>
>
>
> On Sat, Mar 3, 2012 at 07:02, Jesse McConnell 
> wrote:
> > the eclipse-signing-maven-plugin takes care of some of it but reading
> > over the original mail I sort of glazed over and didn't really pick up
> > on where else it ought to have helped address things...
> >
> > so from my view the index and mirror files goop is stuff in tycho land
> >
> > if anyone picks up on a shortcoming of the signing plugin do chirp up
> > and let us know...past that igor will likely know more on the p2
> > details, I still find it a bit silly. :)
> >
> > cheers,
> > jesse
> >
> > --
> > jesse mcconnell
> > jesse.mcconn...@gmail.com
> >
> >
> >
> > On Sat, Mar 3, 2012 at 03:08, Marcel Bruch 
> wrote:
> >> I'm evaluating how to make our repositories comply to these needs with
> our tycho build. Maybe some successful tycho user or tycho committer can
> comment on how to support pack200, p2.index files, and p2.mirrorsURL?
> >>
> >> To me it sounds like these configuration options should be part of the
> repository packaging but at least I haven't found them. Are there any
> options to "switch on" these things? Or is there a set of plug-ins to use
> that will do the trick?
> >>
> >> Thanks,
> >> Marcel
> >>
> >>
> >> ___
> >> cross-project-issues-dev mailing list
> >> cross-project-issues-dev@eclipse.org
> >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>



-- 
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Juno M6 is not far away ... are you still greedy?

2012-03-05 Thread David M Williams 


I've added a new report to the common repository reports [1].

It is called "Optional Runtime Requirements and Greediness" [2]

I doubt it is too useful at the moment, except to reflect the magnitude of
the problem ... that many projects still have to move up to a more recent
publisher. Ideally, by M6 or M7, the first 2 or 3 lists in that report will
all be "0" (indicating we all are using the new p2 publisher) but they are
currently in the hundreds. The reports do not currently track back to "who
is responsible" for using the old publisher, but I might add that when the
list gets smaller. As it is, the reporting code is simply looking at only
the "http://build.eclipse.org/juno/simrel/
[2]
http://build.eclipse.org/juno/simrel/reporeports/reports/greedyReport.html
[3]
http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg07098.html
[4] http://dev.eclipse.org/mhonarc/lists/buckminster-dev/msg01320.html
[5]
http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg07100.html
[6] http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] p2 repositories ... we can do better

2012-03-05 Thread Jesse McConnell 
please don't let my 'silly' comment derail the conversation here...it
was perhaps a careless word I threw out

anything that improves peoples experience with p2 would be a good
thing because right now for me it is still this black box that is a
bit hit or miss in terms of what is in it, what comes out of it, and
how its all organized

I am sure people can say the same about maven central, but 5 minutes,
a web browser and a bit of investigative spirit and clicking around
can sort that out...

by about the 5th jar file I have cracked open and sorting through
MANIFEST.MF files...that is where the eye glazing comes in from my
previous statement :)

so by all means please continue improving p2 repositories!  and if the
eclipse-signing-maven-plugin is supposed to be doing anything from
this conversation please bring that to my attention directly!

cheers,
jesse

--
jesse mcconnell
jesse.mcconn...@gmail.com



On Sat, Mar 3, 2012 at 07:02, Jesse McConnell  wrote:
> the eclipse-signing-maven-plugin takes care of some of it but reading
> over the original mail I sort of glazed over and didn't really pick up
> on where else it ought to have helped address things...
>
> so from my view the index and mirror files goop is stuff in tycho land
>
> if anyone picks up on a shortcoming of the signing plugin do chirp up
> and let us know...past that igor will likely know more on the p2
> details, I still find it a bit silly. :)
>
> cheers,
> jesse
>
> --
> jesse mcconnell
> jesse.mcconn...@gmail.com
>
>
>
> On Sat, Mar 3, 2012 at 03:08, Marcel Bruch  wrote:
>> I'm evaluating how to make our repositories comply to these needs with our 
>> tycho build. Maybe some successful tycho user or tycho committer can comment 
>> on how to support pack200, p2.index files, and p2.mirrorsURL?
>>
>> To me it sounds like these configuration options should be part of the 
>> repository packaging but at least I haven't found them. Are there any 
>> options to "switch on" these things? Or is there a set of plug-ins to use 
>> that will do the trick?
>>
>> Thanks,
>> Marcel
>>
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Hudson Jetty conversion

2012-03-05 Thread Denis Roy 
/shared isn't explicitly read-only.  I think Matt was referring to the 
fact that the hudsonbuild user does not have write access to 
/shared/technology.  I'm re-running some ACL scripts -- please let me 
know if this is still broken for you in a few hours from now.


Denis





On 03/05/2012 10:20 AM, Markus Knauer wrote:
Thanks for that info... is the read-only access to /shared permanent, 
or will it be changed in the (near) future to its old state? My 
understanding was that this is the place where we could store and work 
with possibly large build artifacts.


Sorry if this has been asked somewhere else, but there are so many 
discussions around Hudson that I may have missed one.


Thanks,
Markus


On Mon, Mar 5, 2012 at 16:05, Webmaster(Matt Ward) 
mailto:webmas...@eclipse.org>> wrote:



One is the web interface. It's painful slow today and/or I am
getting our 'Bad Gateway' error. The same problems are shown
when I try to update any of my job configurations. Maybe it's
a bandwidth problem, maybe a problem with Hudson. Are others
having the same problem?

The interface seems responsive from here.  In the past the gateway
error has implied that Winstone(no longer used) was running out of
resources to serve content.  But I also see a 'flood' of requests
today from:

Commissariat a l'Energie Atomique 904
SAP AG, Walldorf   842

So it may just be bandwidth/load.

The next problem is the file system access. Is
/shared/technology available or what's the status there? I
thought it should be accessible but every attempt to
create/add/modify anything there ends up with error messages
like this

It's mounted, but the Hudson user/group has no access(ownership)
on that dir so it can only read.


-Matt.
-- 


Eclipse WebMaster - webmas...@eclipse.org


Questions? Consult the WebMaster FAQ at
http://wiki.eclipse.org/index.php/Webmaster_FAQ
View my status at http://wiki.eclipse.org/index.php/WebMaster

EclipseCon 2012 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev





___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Hudson Jetty conversion

2012-03-05 Thread Markus Knauer 
Thanks for that info... is the read-only access to /shared permanent, or
will it be changed in the (near) future to its old state? My understanding
was that this is the place where we could store and work with possibly
large build artifacts.

Sorry if this has been asked somewhere else, but there are so many
discussions around Hudson that I may have missed one.

Thanks,
Markus


On Mon, Mar 5, 2012 at 16:05, Webmaster(Matt Ward) wrote:

>
>  One is the web interface. It's painful slow today and/or I am getting our
>> 'Bad Gateway' error. The same problems are shown when I try to update any
>> of my job configurations. Maybe it's a bandwidth problem, maybe a problem
>> with Hudson. Are others having the same problem?
>>
> The interface seems responsive from here.  In the past the gateway error
> has implied that Winstone(no longer used) was running out of resources to
> serve content.  But I also see a 'flood' of requests today from:
>
> Commissariat a l'Energie Atomique 904
> SAP AG, Walldorf   842
>
> So it may just be bandwidth/load.
>
>  The next problem is the file system access. Is /shared/technology
>> available or what's the status there? I thought it should be accessible but
>> every attempt to create/add/modify anything there ends up with error
>> messages like this
>>
> It's mounted, but the Hudson user/group has no access(ownership) on that
> dir so it can only read.
>
>
> -Matt.
> --
>
> Eclipse WebMaster - webmas...@eclipse.org
>
> Questions? Consult the WebMaster FAQ at http://wiki.eclipse.org/index.**
> php/Webmaster_FAQ 
> View my status at 
> http://wiki.eclipse.org/index.**php/WebMaster
>
> EclipseCon 2012 
> 
> >
> __**_
> cross-project-issues-dev mailing list
> cross-project-issues-dev@**eclipse.org
> https://dev.eclipse.org/**mailman/listinfo/cross-**project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] p2 repositories ... we can do better

2012-03-05 Thread Denis Roy 

On 03/03/2012 08:02 AM, Jesse McConnell wrote:

if anyone picks up on a shortcoming of the signing plugin do chirp up
and let us know...past that igor will likely know more on the p2
details, I still find it a bit silly. :)


Jesse, I'm a bit intrigued by that last part -- could you elaborate?

Denis




cheers,
jesse

--
jesse mcconnell
jesse.mcconn...@gmail.com



On Sat, Mar 3, 2012 at 03:08, Marcel Bruch  wrote:

I'm evaluating how to make our repositories comply to these needs with our 
tycho build. Maybe some successful tycho user or tycho committer can comment on 
how to support pack200, p2.index files, and p2.mirrorsURL?

To me it sounds like these configuration options should be part of the repository 
packaging but at least I haven't found them. Are there any options to "switch 
on" these things? Or is there a set of plug-ins to use that will do the trick?

Thanks,
Marcel





___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Hudson Jetty conversion

2012-03-05 Thread Webmaster(Matt Ward) 


One is the web interface. It's painful slow today and/or I am getting 
our 'Bad Gateway' error. The same problems are shown when I try to 
update any of my job configurations. Maybe it's a bandwidth problem, 
maybe a problem with Hudson. Are others having the same problem?
The interface seems responsive from here.  In the past the gateway error 
has implied that Winstone(no longer used) was running out of resources 
to serve content.  But I also see a 'flood' of requests today from:


Commissariat a l'Energie Atomique 904
SAP AG, Walldorf   842

So it may just be bandwidth/load.
The next problem is the file system access. Is /shared/technology 
available or what's the status there? I thought it should be 
accessible but every attempt to create/add/modify anything there ends 
up with error messages like this
It's mounted, but the Hudson user/group has no access(ownership) on that 
dir so it can only read.


-Matt.
--

Eclipse WebMaster - webmas...@eclipse.org

Questions? Consult the WebMaster FAQ at 
http://wiki.eclipse.org/index.php/Webmaster_FAQ

View my status at http://wiki.eclipse.org/index.php/WebMaster

EclipseCon 2012 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Hudson Jetty conversion

2012-03-05 Thread Doug Schaefer 
I tried to save a configuration change and it did take forever. But
it's been that for a long time, just worse today.

On Mon, Mar 5, 2012 at 9:10 AM, Jesse McConnell
 wrote:
> I am able click around quickly right now..
>
> jesse
>
> --
> jesse mcconnell
> jesse.mcconn...@gmail.com
>
>
>
> On Mon, Mar 5, 2012 at 08:08, Markus Knauer  wrote:
>> I've got two new problems today... :(
>>
>> One is the web interface. It's painful slow today and/or I am getting our
>> 'Bad Gateway' error. The same problems are shown when I try to update any of
>> my job configurations. Maybe it's a bandwidth problem, maybe a problem with
>> Hudson. Are others having the same problem?
>>
>> The next problem is the file system access. Is /shared/technology available
>> or what's the status there? I thought it should be accessible but every
>> attempt to create/add/modify anything there ends up with error messages like
>> this
>>
>> Cleaning the workspace because project is configured to clean the workspace
>> before each build.
>> java.io.IOException: Failed to mkdirs: /shared/technology/epp/epp_repo/juno
>>
>>
>> Regards,
>> Markus
>>
>>
>>
>>
>> On Thu, Mar 1, 2012 at 08:52, Laurent Goubet  wrote:
>>>
>>> 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 builds we launched went back to a rough 13 minutes each.
>>>
>>> So yeah, seen from our side, we have a winner :p. Thanks for all the work
>>> you've done on this!
>>>
>>> Laurent Goubet
>>> Obeo
>>>
>>>
>>> On 29/02/2012 22:33, Denis Roy wrote:

 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 soo slw for the last
> 6 minutes?
>
> :-D

 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

>>>
>>>
>>> ___
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@eclipse.org
>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>
>>
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Hudson Jetty conversion

2012-03-05 Thread Jesse McConnell 
I am able click around quickly right now..

jesse

--
jesse mcconnell
jesse.mcconn...@gmail.com



On Mon, Mar 5, 2012 at 08:08, Markus Knauer  wrote:
> I've got two new problems today... :(
>
> One is the web interface. It's painful slow today and/or I am getting our
> 'Bad Gateway' error. The same problems are shown when I try to update any of
> my job configurations. Maybe it's a bandwidth problem, maybe a problem with
> Hudson. Are others having the same problem?
>
> The next problem is the file system access. Is /shared/technology available
> or what's the status there? I thought it should be accessible but every
> attempt to create/add/modify anything there ends up with error messages like
> this
>
> Cleaning the workspace because project is configured to clean the workspace
> before each build.
> java.io.IOException: Failed to mkdirs: /shared/technology/epp/epp_repo/juno
>
>
> Regards,
> Markus
>
>
>
>
> On Thu, Mar 1, 2012 at 08:52, Laurent Goubet  wrote:
>>
>> 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 builds we launched went back to a rough 13 minutes each.
>>
>> So yeah, seen from our side, we have a winner :p. Thanks for all the work
>> you've done on this!
>>
>> Laurent Goubet
>> Obeo
>>
>>
>> On 29/02/2012 22:33, Denis Roy wrote:
>>>
>>> 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 soo slw for the last
 6 minutes?

 :-D
>>>
>>> ___
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@eclipse.org
>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>
>>
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Hudson Jetty conversion

2012-03-05 Thread Markus Knauer 
I've got two new problems today... :(

One is the web interface. It's painful slow today and/or I am getting our
'Bad Gateway' error. The same problems are shown when I try to update any
of my job configurations. Maybe it's a bandwidth problem, maybe a problem
with Hudson. Are others having the same problem?

The next problem is the file system access. Is /shared/technology available
or what's the status there? I thought it should be accessible but every
attempt to create/add/modify anything there ends up with error messages
like this

Cleaning the workspace because project is configured to clean the
workspace before each build.
java.io.IOException: Failed to mkdirs: /shared/technology/epp/epp_repo/juno


Regards,
Markus



On Thu, Mar 1, 2012 at 08:52, Laurent Goubet  wrote:

> 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 builds we launched went back to a rough 13 minutes each.
>
> So yeah, seen from our side, we have a winner :p. Thanks for all the work
> you've done on this!
>
> Laurent Goubet
> Obeo
>
>
> On 29/02/2012 22:33, Denis Roy wrote:
>
>> 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 soo slw for the last
>>> 6 minutes?
>>>
>>> :-D
>>>
>> __**_
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@**eclipse.org
>> https://dev.eclipse.org/**mailman/listinfo/cross-**project-issues-dev
>>
>>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev