You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sis.apache.org by Adam Estrada <Ad...@mdaus.com> on 2012/09/21 03:07:08 UTC
SIS TLP Migration
All,
https://issues.apache.org/jira/browse/INFRA-5304
If you experience any hiccups with SVN or the website...its probably because @infra is working on it.
Adam
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
+1 to 0.3-SNAPSHOT...
Cheers,
Chris
On Sep 24, 2012, at 5:56 AM, Martin Desruisseaux wrote:
> Hello again
>
> The SIS version number currently declared in pom.xml files is "0.3-incubating-SNAPSHOT". Should we change it to "0.3-SNAPSHOT"?
>
> Martin
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Hello again
The SIS version number currently declared in pom.xml files is
"0.3-incubating-SNAPSHOT". Should we change it to "0.3-SNAPSHOT"?
Martin
Re: SIS TLP Migration
Posted by Adam Estrada <es...@gmail.com>.
#1 and #2 sound good to me too!
a
On Tue, Sep 25, 2012 at 10:15 AM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> Hey Martin,
>
> +1 to options #1 or #2 for me too.
>
> If I don't hear any objections in the next few days I'll change
> the port to something obscure.
>
> Thanks!
>
> Cheers,
> Chris
>
> On Sep 25, 2012, at 1:59 AM, Martin Desruisseaux wrote:
>
> > Le 25/09/12 13:37, Mattmann, Chris A (388J) a écrit :
> >> Sure +1 to starting to deploy SNAPSHOTS to Nexus@repository.apache.orgI think that would be great....
> >
> > Done. Actually I didn't had to configure anything. Just adding "deploy"
> on Jenkins worked well, since the parent Apache pom.xml already declared
> all necessary configuration. The artifacts are now available there:
> >
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/sis/
> >
> > However we still have a random " java.net.BindException: Address already
> in use" build failure in sis-webapp. We are apparently not the only project
> to have switched from port 8080 to 8081. Possible actions are:
> >
> > 1. Do nothing and live with the fact that those random build failures
> > are reasonable rare (however if we suffer from build failures, we
> > may also be causing build failures to the other project using that
> > port, unless their build is sophisticated enough for searching an
> > unused port).
> > 2. Chose a slightly less common port number (8082?)
> > 3. Implement some mechanism for searching an unused port number (anyone
> > know how to do that?)
> > 4. Create a wiki page and ask all Apache projects to document the port
> > numbers they are using for their Jenkins build, so anyone can pickup
> > an unused port.
> >
> >
> > My preferred approach would be 4 (if someone had energy for that), but
> I'm not sure it is realistic. Otherwise I think we can live with options 1
> or 2.
> >
> > Martin
> >
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Martin,
I implemented this approach: http://s.apache.org/hsd in r1391834.
Let's see if this fixes the Jetty tests, once and for all :)
The build is currently running at:
https://builds.apache.org/job/sis-trunk/86/
Fingers crossed!
Cheers,
Chris
On Sep 28, 2012, at 10:37 PM, Martin Desruisseaux wrote:
> Le 28/09/12 12:14, Adam Estrada a écrit :
>> I added Jetty as a way to quickly deploy the web app without much
>> configuration. I think its fine to disable it to run tests on the server.
>> Anyone else disagree?
>
> If no one object, I would like to create a Maven profile in the new few days for disabling those tests on Jenkins. But they would still be enabled by default on the developer machines.
>
> Martin
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
+1 from me on the profile....
Cheers,
Chris
On Sep 28, 2012, at 10:37 PM, Martin Desruisseaux wrote:
> Le 28/09/12 12:14, Adam Estrada a écrit :
>> I added Jetty as a way to quickly deploy the web app without much
>> configuration. I think its fine to disable it to run tests on the server.
>> Anyone else disagree?
>
> If no one object, I would like to create a Maven profile in the new few days for disabling those tests on Jenkins. But they would still be enabled by default on the developer machines.
>
> Martin
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Le 28/09/12 12:14, Adam Estrada a écrit :
> I added Jetty as a way to quickly deploy the web app without much
> configuration. I think its fine to disable it to run tests on the server.
> Anyone else disagree?
If no one object, I would like to create a Maven profile in the new few
days for disabling those tests on Jenkins. But they would still be
enabled by default on the developer machines.
Martin
Re: SIS TLP Migration
Posted by Adam Estrada <es...@gmail.com>.
I added Jetty as a way to quickly deploy the web app without much
configuration. I think its fine to disable it to run tests on the server.
Anyone else disagree?
a
On Thu, Sep 27, 2012 at 11:09 PM, Martin Desruisseaux <
martin.desruisseaux@geomatys.fr> wrote:
> Hello Chris
>
> Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit :
>
> Ugh, OK, I've went ahead and picked an obscure port in r1391035.
>> Let's see if that fixes it.
>>
>
> Thanks! But unfortunately, we still got a "java.net.BindException: Address
> already in use" despite the new port number. I wonder if all ports have
> been closed?
>
> Should we create a Maven profile for disabling the Jetty tests on Jenkins?
> They would still be executed on the developers local machine.
>
> Martin
>
>
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Olivier,
OK I will take a look and thanks for the pointer.
Cheers,
Chris
On Oct 1, 2012, at 8:27 AM, Olivier Lamy wrote:
> Chris,
> If you can use tomcat maven plugin rather than jetty.
> It's possible to use port 0 (which means jvm will use the first available port).
> I don't know exactly what your build do so I cannot tell you if that's
> possible or not for your use case.
> But in Archiva project, we start an embeded tomcat running a war then
> run selenium tests.
> And we use port 0 so problem with reserved port !
>
> 2012/10/1 Brett Porter <br...@apache.org>:
>> Chris,
>>
>> This sounds like you've had some jobs hang that held on to the port, as it'd be unlikely another project is using the same port.
>>
>> If you need to make sure you get distinct ports, try:
>> http://mojo.codehaus.org/build-helper-maven-plugin/reserve-network-port-mojo.html
>>
>> Either way, if the builds are leaving processes around, that should be sorted out. Someone with access to the particular Jenkins node you're building on would have to answer that.
>>
>> - Brett
>>
>> On 28/09/2012, at 1:14 PM, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>>
>>> Hey Martin,
>>>
>>> I saw this. I'm CC'ing builds@ here. Guys, I keep changing the pom.xml
>>> in Apache SIS to do automatic Jetty testing. I found this code snippet:
>>>
>>> {code}
>>> <execution>
>>> <id>start-jetty</id>
>>> <phase>pre-integration-test</phase>
>>> <goals>
>>> <goal>run</goal>
>>> </goals>
>>> <configuration>
>>> <connectors>
>>> <connector implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
>>> <port>50234</port>
>>> </connector>
>>> </connectors>
>>> <stopPort>50500</stopPort>
>>> <scanIntervalSeconds>10</scanIntervalSeconds>
>>> <daemon>true</daemon>
>>> <systemProperties>
>>> <systemProperty>
>>> <name>org.apache.commons.logging.Log</name>
>>> <value>org.apache.commons.logging.impl.Jdk14Logger</value>
>>> </systemProperty>
>>> <systemProperty>
>>> <name>java.util.logging.config.file</name>
>>> <value>./src/test/resources/logging.properties</value>
>>> </systemProperty>
>>> </systemProperties>
>>> </configuration>
>>> </execution>
>>>
>>> {code}
>>>
>>> That I *thought* scans different ports and tries to find a free one on the machine.
>>> Do the Jenkins build slaves allow this? Did I set the Maven conf up wrong?
>>> Can someone help? :)
>>>
>>> Thanks!
>>>
>>> Cheers,
>>> Chris
>>>
>>> On Sep 27, 2012, at 8:09 PM, Martin Desruisseaux wrote:
>>>
>>>> Hello Chris
>>>>
>>>> Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit :
>>>>> Ugh, OK, I've went ahead and picked an obscure port in r1391035.
>>>>> Let's see if that fixes it.
>>>>
>>>> Thanks! But unfortunately, we still got a "java.net.BindException: Address already in use" despite the new port number. I wonder if all ports have been closed?
>>>>
>>>> Should we create a Maven profile for disabling the Jetty tests on Jenkins? They would still be executed on the developers local machine.
>>>>
>>>> Martin
>>>>
>>>
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Chris Mattmann, Ph.D.
>>> Senior Computer Scientist
>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>> Office: 171-266B, Mailstop: 171-246
>>> Email: chris.a.mattmann@nasa.gov
>>> WWW: http://sunset.usc.edu/~mattmann/
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Adjunct Assistant Professor, Computer Science Department
>>> University of Southern California, Los Angeles, CA 90089 USA
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://brettporter.wordpress.com/
>> http://au.linkedin.com/in/brettporter
>> http://twitter.com/brettporter
>>
>>
>>
>>
>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Olivier,
OK I will take a look and thanks for the pointer.
Cheers,
Chris
On Oct 1, 2012, at 8:27 AM, Olivier Lamy wrote:
> Chris,
> If you can use tomcat maven plugin rather than jetty.
> It's possible to use port 0 (which means jvm will use the first available port).
> I don't know exactly what your build do so I cannot tell you if that's
> possible or not for your use case.
> But in Archiva project, we start an embeded tomcat running a war then
> run selenium tests.
> And we use port 0 so problem with reserved port !
>
> 2012/10/1 Brett Porter <br...@apache.org>:
>> Chris,
>>
>> This sounds like you've had some jobs hang that held on to the port, as it'd be unlikely another project is using the same port.
>>
>> If you need to make sure you get distinct ports, try:
>> http://mojo.codehaus.org/build-helper-maven-plugin/reserve-network-port-mojo.html
>>
>> Either way, if the builds are leaving processes around, that should be sorted out. Someone with access to the particular Jenkins node you're building on would have to answer that.
>>
>> - Brett
>>
>> On 28/09/2012, at 1:14 PM, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>>
>>> Hey Martin,
>>>
>>> I saw this. I'm CC'ing builds@ here. Guys, I keep changing the pom.xml
>>> in Apache SIS to do automatic Jetty testing. I found this code snippet:
>>>
>>> {code}
>>> <execution>
>>> <id>start-jetty</id>
>>> <phase>pre-integration-test</phase>
>>> <goals>
>>> <goal>run</goal>
>>> </goals>
>>> <configuration>
>>> <connectors>
>>> <connector implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
>>> <port>50234</port>
>>> </connector>
>>> </connectors>
>>> <stopPort>50500</stopPort>
>>> <scanIntervalSeconds>10</scanIntervalSeconds>
>>> <daemon>true</daemon>
>>> <systemProperties>
>>> <systemProperty>
>>> <name>org.apache.commons.logging.Log</name>
>>> <value>org.apache.commons.logging.impl.Jdk14Logger</value>
>>> </systemProperty>
>>> <systemProperty>
>>> <name>java.util.logging.config.file</name>
>>> <value>./src/test/resources/logging.properties</value>
>>> </systemProperty>
>>> </systemProperties>
>>> </configuration>
>>> </execution>
>>>
>>> {code}
>>>
>>> That I *thought* scans different ports and tries to find a free one on the machine.
>>> Do the Jenkins build slaves allow this? Did I set the Maven conf up wrong?
>>> Can someone help? :)
>>>
>>> Thanks!
>>>
>>> Cheers,
>>> Chris
>>>
>>> On Sep 27, 2012, at 8:09 PM, Martin Desruisseaux wrote:
>>>
>>>> Hello Chris
>>>>
>>>> Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit :
>>>>> Ugh, OK, I've went ahead and picked an obscure port in r1391035.
>>>>> Let's see if that fixes it.
>>>>
>>>> Thanks! But unfortunately, we still got a "java.net.BindException: Address already in use" despite the new port number. I wonder if all ports have been closed?
>>>>
>>>> Should we create a Maven profile for disabling the Jetty tests on Jenkins? They would still be executed on the developers local machine.
>>>>
>>>> Martin
>>>>
>>>
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Chris Mattmann, Ph.D.
>>> Senior Computer Scientist
>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>> Office: 171-266B, Mailstop: 171-246
>>> Email: chris.a.mattmann@nasa.gov
>>> WWW: http://sunset.usc.edu/~mattmann/
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Adjunct Assistant Professor, Computer Science Department
>>> University of Southern California, Los Angeles, CA 90089 USA
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://brettporter.wordpress.com/
>> http://au.linkedin.com/in/brettporter
>> http://twitter.com/brettporter
>>
>>
>>
>>
>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by Olivier Lamy <ol...@apache.org>.
Chris,
If you can use tomcat maven plugin rather than jetty.
It's possible to use port 0 (which means jvm will use the first available port).
I don't know exactly what your build do so I cannot tell you if that's
possible or not for your use case.
But in Archiva project, we start an embeded tomcat running a war then
run selenium tests.
And we use port 0 so problem with reserved port !
2012/10/1 Brett Porter <br...@apache.org>:
> Chris,
>
> This sounds like you've had some jobs hang that held on to the port, as it'd be unlikely another project is using the same port.
>
> If you need to make sure you get distinct ports, try:
> http://mojo.codehaus.org/build-helper-maven-plugin/reserve-network-port-mojo.html
>
> Either way, if the builds are leaving processes around, that should be sorted out. Someone with access to the particular Jenkins node you're building on would have to answer that.
>
> - Brett
>
> On 28/09/2012, at 1:14 PM, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>
>> Hey Martin,
>>
>> I saw this. I'm CC'ing builds@ here. Guys, I keep changing the pom.xml
>> in Apache SIS to do automatic Jetty testing. I found this code snippet:
>>
>> {code}
>> <execution>
>> <id>start-jetty</id>
>> <phase>pre-integration-test</phase>
>> <goals>
>> <goal>run</goal>
>> </goals>
>> <configuration>
>> <connectors>
>> <connector implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
>> <port>50234</port>
>> </connector>
>> </connectors>
>> <stopPort>50500</stopPort>
>> <scanIntervalSeconds>10</scanIntervalSeconds>
>> <daemon>true</daemon>
>> <systemProperties>
>> <systemProperty>
>> <name>org.apache.commons.logging.Log</name>
>> <value>org.apache.commons.logging.impl.Jdk14Logger</value>
>> </systemProperty>
>> <systemProperty>
>> <name>java.util.logging.config.file</name>
>> <value>./src/test/resources/logging.properties</value>
>> </systemProperty>
>> </systemProperties>
>> </configuration>
>> </execution>
>>
>> {code}
>>
>> That I *thought* scans different ports and tries to find a free one on the machine.
>> Do the Jenkins build slaves allow this? Did I set the Maven conf up wrong?
>> Can someone help? :)
>>
>> Thanks!
>>
>> Cheers,
>> Chris
>>
>> On Sep 27, 2012, at 8:09 PM, Martin Desruisseaux wrote:
>>
>>> Hello Chris
>>>
>>> Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit :
>>>> Ugh, OK, I've went ahead and picked an obscure port in r1391035.
>>>> Let's see if that fixes it.
>>>
>>> Thanks! But unfortunately, we still got a "java.net.BindException: Address already in use" despite the new port number. I wonder if all ports have been closed?
>>>
>>> Should we create a Maven profile for disabling the Jetty tests on Jenkins? They would still be executed on the developers local machine.
>>>
>>> Martin
>>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW: http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Brett,
Thanks! I was able to resolve this by finding the same helper plugin independently via
a few Google searches. That fixed it!
Thanks man!
Cheers,
Chris
On Oct 1, 2012, at 6:38 AM, Brett Porter wrote:
> Chris,
>
> This sounds like you've had some jobs hang that held on to the port, as it'd be unlikely another project is using the same port.
>
> If you need to make sure you get distinct ports, try:
> http://mojo.codehaus.org/build-helper-maven-plugin/reserve-network-port-mojo.html
>
> Either way, if the builds are leaving processes around, that should be sorted out. Someone with access to the particular Jenkins node you're building on would have to answer that.
>
> - Brett
>
> On 28/09/2012, at 1:14 PM, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>
>> Hey Martin,
>>
>> I saw this. I'm CC'ing builds@ here. Guys, I keep changing the pom.xml
>> in Apache SIS to do automatic Jetty testing. I found this code snippet:
>>
>> {code}
>> <execution>
>> <id>start-jetty</id>
>> <phase>pre-integration-test</phase>
>> <goals>
>> <goal>run</goal>
>> </goals>
>> <configuration>
>> <connectors>
>> <connector implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
>> <port>50234</port>
>> </connector>
>> </connectors>
>> <stopPort>50500</stopPort>
>> <scanIntervalSeconds>10</scanIntervalSeconds>
>> <daemon>true</daemon>
>> <systemProperties>
>> <systemProperty>
>> <name>org.apache.commons.logging.Log</name>
>> <value>org.apache.commons.logging.impl.Jdk14Logger</value>
>> </systemProperty>
>> <systemProperty>
>> <name>java.util.logging.config.file</name>
>> <value>./src/test/resources/logging.properties</value>
>> </systemProperty>
>> </systemProperties>
>> </configuration>
>> </execution>
>>
>> {code}
>>
>> That I *thought* scans different ports and tries to find a free one on the machine.
>> Do the Jenkins build slaves allow this? Did I set the Maven conf up wrong?
>> Can someone help? :)
>>
>> Thanks!
>>
>> Cheers,
>> Chris
>>
>> On Sep 27, 2012, at 8:09 PM, Martin Desruisseaux wrote:
>>
>>> Hello Chris
>>>
>>> Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit :
>>>> Ugh, OK, I've went ahead and picked an obscure port in r1391035.
>>>> Let's see if that fixes it.
>>>
>>> Thanks! But unfortunately, we still got a "java.net.BindException: Address already in use" despite the new port number. I wonder if all ports have been closed?
>>>
>>> Should we create a Maven profile for disabling the Jetty tests on Jenkins? They would still be executed on the developers local machine.
>>>
>>> Martin
>>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW: http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Brett,
Thanks! I was able to resolve this by finding the same helper plugin independently via
a few Google searches. That fixed it!
Thanks man!
Cheers,
Chris
On Oct 1, 2012, at 6:38 AM, Brett Porter wrote:
> Chris,
>
> This sounds like you've had some jobs hang that held on to the port, as it'd be unlikely another project is using the same port.
>
> If you need to make sure you get distinct ports, try:
> http://mojo.codehaus.org/build-helper-maven-plugin/reserve-network-port-mojo.html
>
> Either way, if the builds are leaving processes around, that should be sorted out. Someone with access to the particular Jenkins node you're building on would have to answer that.
>
> - Brett
>
> On 28/09/2012, at 1:14 PM, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>
>> Hey Martin,
>>
>> I saw this. I'm CC'ing builds@ here. Guys, I keep changing the pom.xml
>> in Apache SIS to do automatic Jetty testing. I found this code snippet:
>>
>> {code}
>> <execution>
>> <id>start-jetty</id>
>> <phase>pre-integration-test</phase>
>> <goals>
>> <goal>run</goal>
>> </goals>
>> <configuration>
>> <connectors>
>> <connector implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
>> <port>50234</port>
>> </connector>
>> </connectors>
>> <stopPort>50500</stopPort>
>> <scanIntervalSeconds>10</scanIntervalSeconds>
>> <daemon>true</daemon>
>> <systemProperties>
>> <systemProperty>
>> <name>org.apache.commons.logging.Log</name>
>> <value>org.apache.commons.logging.impl.Jdk14Logger</value>
>> </systemProperty>
>> <systemProperty>
>> <name>java.util.logging.config.file</name>
>> <value>./src/test/resources/logging.properties</value>
>> </systemProperty>
>> </systemProperties>
>> </configuration>
>> </execution>
>>
>> {code}
>>
>> That I *thought* scans different ports and tries to find a free one on the machine.
>> Do the Jenkins build slaves allow this? Did I set the Maven conf up wrong?
>> Can someone help? :)
>>
>> Thanks!
>>
>> Cheers,
>> Chris
>>
>> On Sep 27, 2012, at 8:09 PM, Martin Desruisseaux wrote:
>>
>>> Hello Chris
>>>
>>> Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit :
>>>> Ugh, OK, I've went ahead and picked an obscure port in r1391035.
>>>> Let's see if that fixes it.
>>>
>>> Thanks! But unfortunately, we still got a "java.net.BindException: Address already in use" despite the new port number. I wonder if all ports have been closed?
>>>
>>> Should we create a Maven profile for disabling the Jetty tests on Jenkins? They would still be executed on the developers local machine.
>>>
>>> Martin
>>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW: http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by Olivier Lamy <ol...@apache.org>.
Chris,
If you can use tomcat maven plugin rather than jetty.
It's possible to use port 0 (which means jvm will use the first available port).
I don't know exactly what your build do so I cannot tell you if that's
possible or not for your use case.
But in Archiva project, we start an embeded tomcat running a war then
run selenium tests.
And we use port 0 so problem with reserved port !
2012/10/1 Brett Porter <br...@apache.org>:
> Chris,
>
> This sounds like you've had some jobs hang that held on to the port, as it'd be unlikely another project is using the same port.
>
> If you need to make sure you get distinct ports, try:
> http://mojo.codehaus.org/build-helper-maven-plugin/reserve-network-port-mojo.html
>
> Either way, if the builds are leaving processes around, that should be sorted out. Someone with access to the particular Jenkins node you're building on would have to answer that.
>
> - Brett
>
> On 28/09/2012, at 1:14 PM, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>
>> Hey Martin,
>>
>> I saw this. I'm CC'ing builds@ here. Guys, I keep changing the pom.xml
>> in Apache SIS to do automatic Jetty testing. I found this code snippet:
>>
>> {code}
>> <execution>
>> <id>start-jetty</id>
>> <phase>pre-integration-test</phase>
>> <goals>
>> <goal>run</goal>
>> </goals>
>> <configuration>
>> <connectors>
>> <connector implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
>> <port>50234</port>
>> </connector>
>> </connectors>
>> <stopPort>50500</stopPort>
>> <scanIntervalSeconds>10</scanIntervalSeconds>
>> <daemon>true</daemon>
>> <systemProperties>
>> <systemProperty>
>> <name>org.apache.commons.logging.Log</name>
>> <value>org.apache.commons.logging.impl.Jdk14Logger</value>
>> </systemProperty>
>> <systemProperty>
>> <name>java.util.logging.config.file</name>
>> <value>./src/test/resources/logging.properties</value>
>> </systemProperty>
>> </systemProperties>
>> </configuration>
>> </execution>
>>
>> {code}
>>
>> That I *thought* scans different ports and tries to find a free one on the machine.
>> Do the Jenkins build slaves allow this? Did I set the Maven conf up wrong?
>> Can someone help? :)
>>
>> Thanks!
>>
>> Cheers,
>> Chris
>>
>> On Sep 27, 2012, at 8:09 PM, Martin Desruisseaux wrote:
>>
>>> Hello Chris
>>>
>>> Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit :
>>>> Ugh, OK, I've went ahead and picked an obscure port in r1391035.
>>>> Let's see if that fixes it.
>>>
>>> Thanks! But unfortunately, we still got a "java.net.BindException: Address already in use" despite the new port number. I wonder if all ports have been closed?
>>>
>>> Should we create a Maven profile for disabling the Jetty tests on Jenkins? They would still be executed on the developers local machine.
>>>
>>> Martin
>>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW: http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: SIS TLP Migration
Posted by Brett Porter <br...@apache.org>.
Chris,
This sounds like you've had some jobs hang that held on to the port, as it'd be unlikely another project is using the same port.
If you need to make sure you get distinct ports, try:
http://mojo.codehaus.org/build-helper-maven-plugin/reserve-network-port-mojo.html
Either way, if the builds are leaving processes around, that should be sorted out. Someone with access to the particular Jenkins node you're building on would have to answer that.
- Brett
On 28/09/2012, at 1:14 PM, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
> Hey Martin,
>
> I saw this. I'm CC'ing builds@ here. Guys, I keep changing the pom.xml
> in Apache SIS to do automatic Jetty testing. I found this code snippet:
>
> {code}
> <execution>
> <id>start-jetty</id>
> <phase>pre-integration-test</phase>
> <goals>
> <goal>run</goal>
> </goals>
> <configuration>
> <connectors>
> <connector implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
> <port>50234</port>
> </connector>
> </connectors>
> <stopPort>50500</stopPort>
> <scanIntervalSeconds>10</scanIntervalSeconds>
> <daemon>true</daemon>
> <systemProperties>
> <systemProperty>
> <name>org.apache.commons.logging.Log</name>
> <value>org.apache.commons.logging.impl.Jdk14Logger</value>
> </systemProperty>
> <systemProperty>
> <name>java.util.logging.config.file</name>
> <value>./src/test/resources/logging.properties</value>
> </systemProperty>
> </systemProperties>
> </configuration>
> </execution>
>
> {code}
>
> That I *thought* scans different ports and tries to find a free one on the machine.
> Do the Jenkins build slaves allow this? Did I set the Maven conf up wrong?
> Can someone help? :)
>
> Thanks!
>
> Cheers,
> Chris
>
> On Sep 27, 2012, at 8:09 PM, Martin Desruisseaux wrote:
>
>> Hello Chris
>>
>> Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit :
>>> Ugh, OK, I've went ahead and picked an obscure port in r1391035.
>>> Let's see if that fixes it.
>>
>> Thanks! But unfortunately, we still got a "java.net.BindException: Address already in use" despite the new port number. I wonder if all ports have been closed?
>>
>> Should we create a Maven profile for disabling the Jetty tests on Jenkins? They would still be executed on the developers local machine.
>>
>> Martin
>>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
Re: SIS TLP Migration
Posted by Brett Porter <br...@apache.org>.
Chris,
This sounds like you've had some jobs hang that held on to the port, as it'd be unlikely another project is using the same port.
If you need to make sure you get distinct ports, try:
http://mojo.codehaus.org/build-helper-maven-plugin/reserve-network-port-mojo.html
Either way, if the builds are leaving processes around, that should be sorted out. Someone with access to the particular Jenkins node you're building on would have to answer that.
- Brett
On 28/09/2012, at 1:14 PM, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
> Hey Martin,
>
> I saw this. I'm CC'ing builds@ here. Guys, I keep changing the pom.xml
> in Apache SIS to do automatic Jetty testing. I found this code snippet:
>
> {code}
> <execution>
> <id>start-jetty</id>
> <phase>pre-integration-test</phase>
> <goals>
> <goal>run</goal>
> </goals>
> <configuration>
> <connectors>
> <connector implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
> <port>50234</port>
> </connector>
> </connectors>
> <stopPort>50500</stopPort>
> <scanIntervalSeconds>10</scanIntervalSeconds>
> <daemon>true</daemon>
> <systemProperties>
> <systemProperty>
> <name>org.apache.commons.logging.Log</name>
> <value>org.apache.commons.logging.impl.Jdk14Logger</value>
> </systemProperty>
> <systemProperty>
> <name>java.util.logging.config.file</name>
> <value>./src/test/resources/logging.properties</value>
> </systemProperty>
> </systemProperties>
> </configuration>
> </execution>
>
> {code}
>
> That I *thought* scans different ports and tries to find a free one on the machine.
> Do the Jenkins build slaves allow this? Did I set the Maven conf up wrong?
> Can someone help? :)
>
> Thanks!
>
> Cheers,
> Chris
>
> On Sep 27, 2012, at 8:09 PM, Martin Desruisseaux wrote:
>
>> Hello Chris
>>
>> Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit :
>>> Ugh, OK, I've went ahead and picked an obscure port in r1391035.
>>> Let's see if that fixes it.
>>
>> Thanks! But unfortunately, we still got a "java.net.BindException: Address already in use" despite the new port number. I wonder if all ports have been closed?
>>
>> Should we create a Maven profile for disabling the Jetty tests on Jenkins? They would still be executed on the developers local machine.
>>
>> Martin
>>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Martin,
I saw this. I'm CC'ing builds@ here. Guys, I keep changing the pom.xml
in Apache SIS to do automatic Jetty testing. I found this code snippet:
{code}
<execution>
<id>start-jetty</id>
<phase>pre-integration-test</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<connectors>
<connector implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
<port>50234</port>
</connector>
</connectors>
<stopPort>50500</stopPort>
<scanIntervalSeconds>10</scanIntervalSeconds>
<daemon>true</daemon>
<systemProperties>
<systemProperty>
<name>org.apache.commons.logging.Log</name>
<value>org.apache.commons.logging.impl.Jdk14Logger</value>
</systemProperty>
<systemProperty>
<name>java.util.logging.config.file</name>
<value>./src/test/resources/logging.properties</value>
</systemProperty>
</systemProperties>
</configuration>
</execution>
{code}
That I *thought* scans different ports and tries to find a free one on the machine.
Do the Jenkins build slaves allow this? Did I set the Maven conf up wrong?
Can someone help? :)
Thanks!
Cheers,
Chris
On Sep 27, 2012, at 8:09 PM, Martin Desruisseaux wrote:
> Hello Chris
>
> Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit :
>> Ugh, OK, I've went ahead and picked an obscure port in r1391035.
>> Let's see if that fixes it.
>
> Thanks! But unfortunately, we still got a "java.net.BindException: Address already in use" despite the new port number. I wonder if all ports have been closed?
>
> Should we create a Maven profile for disabling the Jetty tests on Jenkins? They would still be executed on the developers local machine.
>
> Martin
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Le 28/09/12 12:17, Greg Reddin a écrit :
> Hmm, forgive my ignorance, but is it possible that our build is
> leaving a port hanging open and we're having trouble hitting it again
> on subsequent builds?
Maybe, I don't know. But in such case, I would expect the first build
after the change of port number to pass, but it hasn't be the case...
Martin
Re: SIS TLP Migration
Posted by Greg Reddin <gr...@gmail.com>.
On Thu, Sep 27, 2012 at 10:09 PM, Martin Desruisseaux
<ma...@geomatys.fr> wrote:
> Thanks! But unfortunately, we still got a "java.net.BindException: Address
> already in use" despite the new port number. I wonder if all ports have been
> closed?
Hmm, forgive my ignorance, but is it possible that our build is
leaving a port hanging open and we're having trouble hitting it again
on subsequent builds?
Greg
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Martin,
I saw this. I'm CC'ing builds@ here. Guys, I keep changing the pom.xml
in Apache SIS to do automatic Jetty testing. I found this code snippet:
{code}
<execution>
<id>start-jetty</id>
<phase>pre-integration-test</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<connectors>
<connector implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
<port>50234</port>
</connector>
</connectors>
<stopPort>50500</stopPort>
<scanIntervalSeconds>10</scanIntervalSeconds>
<daemon>true</daemon>
<systemProperties>
<systemProperty>
<name>org.apache.commons.logging.Log</name>
<value>org.apache.commons.logging.impl.Jdk14Logger</value>
</systemProperty>
<systemProperty>
<name>java.util.logging.config.file</name>
<value>./src/test/resources/logging.properties</value>
</systemProperty>
</systemProperties>
</configuration>
</execution>
{code}
That I *thought* scans different ports and tries to find a free one on the machine.
Do the Jenkins build slaves allow this? Did I set the Maven conf up wrong?
Can someone help? :)
Thanks!
Cheers,
Chris
On Sep 27, 2012, at 8:09 PM, Martin Desruisseaux wrote:
> Hello Chris
>
> Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit :
>> Ugh, OK, I've went ahead and picked an obscure port in r1391035.
>> Let's see if that fixes it.
>
> Thanks! But unfortunately, we still got a "java.net.BindException: Address already in use" despite the new port number. I wonder if all ports have been closed?
>
> Should we create a Maven profile for disabling the Jetty tests on Jenkins? They would still be executed on the developers local machine.
>
> Martin
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Hello Chris
Le 27/09/12 23:44, Mattmann, Chris A (388J) a écrit :
> Ugh, OK, I've went ahead and picked an obscure port in r1391035.
> Let's see if that fixes it.
Thanks! But unfortunately, we still got a "java.net.BindException:
Address already in use" despite the new port number. I wonder if all
ports have been closed?
Should we create a Maven profile for disabling the Jetty tests on
Jenkins? They would still be executed on the developers local machine.
Martin
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Martin,
Ugh, OK, I've went ahead and picked an obscure port in r1391035.
Let's see if that fixes it.
Thanks for letting me know!
Cheers,
Chris
On Sep 27, 2012, at 12:26 AM, Martin Desruisseaux wrote:
> Hello Chris
>
> Le 25/09/12 23:15, Mattmann, Chris A (388J) a écrit :
>> +1 to options #1 or #2 for me too.
>>
>> If I don't hear any objections in the next few days I'll change
>> the port to something obscure.
>
> Actually the error became systematic for the last 3 days, I don't know why. Sound like we have no choice to change the port number, but I don't know which ones we are allowing to use...
>
> Martin
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Hello Chris
Le 25/09/12 23:15, Mattmann, Chris A (388J) a écrit :
> +1 to options #1 or #2 for me too.
>
> If I don't hear any objections in the next few days I'll change
> the port to something obscure.
Actually the error became systematic for the last 3 days, I don't know
why. Sound like we have no choice to change the port number, but I don't
know which ones we are allowing to use...
Martin
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Martin,
+1 to options #1 or #2 for me too.
If I don't hear any objections in the next few days I'll change
the port to something obscure.
Thanks!
Cheers,
Chris
On Sep 25, 2012, at 1:59 AM, Martin Desruisseaux wrote:
> Le 25/09/12 13:37, Mattmann, Chris A (388J) a écrit :
>> Sure +1 to starting to deploy SNAPSHOTS to Nexus@repository.apache.org I think that would be great....
>
> Done. Actually I didn't had to configure anything. Just adding "deploy" on Jenkins worked well, since the parent Apache pom.xml already declared all necessary configuration. The artifacts are now available there:
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/sis/
>
> However we still have a random " java.net.BindException: Address already in use" build failure in sis-webapp. We are apparently not the only project to have switched from port 8080 to 8081. Possible actions are:
>
> 1. Do nothing and live with the fact that those random build failures
> are reasonable rare (however if we suffer from build failures, we
> may also be causing build failures to the other project using that
> port, unless their build is sophisticated enough for searching an
> unused port).
> 2. Chose a slightly less common port number (8082?)
> 3. Implement some mechanism for searching an unused port number (anyone
> know how to do that?)
> 4. Create a wiki page and ask all Apache projects to document the port
> numbers they are using for their Jenkins build, so anyone can pickup
> an unused port.
>
>
> My preferred approach would be 4 (if someone had energy for that), but I'm not sure it is realistic. Otherwise I think we can live with options 1 or 2.
>
> Martin
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Le 25/09/12 13:37, Mattmann, Chris A (388J) a écrit :
> Sure +1 to starting to deploy SNAPSHOTS to Nexus@repository.apache.org I think that would be great....
Done. Actually I didn't had to configure anything. Just adding "deploy"
on Jenkins worked well, since the parent Apache pom.xml already declared
all necessary configuration. The artifacts are now available there:
https://repository.apache.org/content/repositories/snapshots/org/apache/sis/
However we still have a random " java.net.BindException: Address already
in use" build failure in sis-webapp. We are apparently not the only
project to have switched from port 8080 to 8081. Possible actions are:
1. Do nothing and live with the fact that those random build failures
are reasonable rare (however if we suffer from build failures, we
may also be causing build failures to the other project using that
port, unless their build is sophisticated enough for searching an
unused port).
2. Chose a slightly less common port number (8082?)
3. Implement some mechanism for searching an unused port number (anyone
know how to do that?)
4. Create a wiki page and ask all Apache projects to document the port
numbers they are using for their Jenkins build, so anyone can pickup
an unused port.
My preferred approach would be 4 (if someone had energy for that), but
I'm not sure it is realistic. Otherwise I think we can live with options
1 or 2.
Martin
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Martin,
Sure +1 to starting to deploy SNAPSHOTS to Nexus@repository.apache.org I think that would be great....
Cheers,
Chris
On Sep 24, 2012, at 8:58 PM, Martin Desruisseaux wrote:
> Done (removed the paragraph about incubation from the README file, and removed the "incubating" part of version number).
>
> Do we start deploying the snapshots to https://repository.apache.org/content/repositories/snapshots/ ?
>
> For the next few days, I plan to work again a bit on the Maven configuration and the generated reports (including javadoc) before to continue on the code itself. Hopefully I will stop breaking the Jenkins build after that...
>
> Martin
>
>
> Le 25/09/12 00:06, Mattmann, Chris A (388J) a écrit :
>> Thanks! Yep +1 you can remove that Incubating part. See:
>>
>> http://svn.apache.org/repos/asf/tika/trunk/README.txt
>>
>> For a good example of the contents of README.txt
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Done (removed the paragraph about incubation from the README file, and
removed the "incubating" part of version number).
Do we start deploying the snapshots to
https://repository.apache.org/content/repositories/snapshots/ ?
For the next few days, I plan to work again a bit on the Maven
configuration and the generated reports (including javadoc) before to
continue on the code itself. Hopefully I will stop breaking the Jenkins
build after that...
Martin
Le 25/09/12 00:06, Mattmann, Chris A (388J) a écrit :
> Thanks! Yep +1 you can remove that Incubating part. See:
>
> http://svn.apache.org/repos/asf/tika/trunk/README.txt
>
> For a good example of the contents of README.txt
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Martin,
Thanks! Yep +1 you can remove that Incubating part. See:
http://svn.apache.org/repos/asf/tika/trunk/README.txt
For a good example of the contents of README.txt
Thanks!
Cheers,
Chris
On Sep 24, 2012, at 4:12 AM, Martin Desruisseaux wrote:
> I confirm that commits are now enabled. Thanks!
>
> I updated the SVN URL and the email address in the README and root pom.xml files:
>
> Old: http://svn.apache.org/repos/asf/incubator/sis/trunk
> New: http://svn.apache.org/repos/asf/sis/trunk
>
> Old: sis-dev@incubator.apache.org
> New: dev@sis.apache.org
>
> Same for "user" and "commit" mailing lists. However I did not yet updated the web page URL, since this is pending INFRA-5307.
>
> Note that the README file contains the following paragraph, which I presume is now obsolete. Should we just remove this paragraph, or does it needs to be replaced by something else?
>
> Apache SIS is an effort undergoing incubation at The Apache Software
> Foundation (ASF),
> sponsored by the Apache Incubator PMC. Incubation is required of all
> newly accepted
> projects until a further review indicates that the infrastructure,
> communications,
> and decision making process have stabilized in a manner consistent
> with other successful
> ASF projects. While incubation status is not necessarily a
> reflection of the completeness
> or stability of the code, it does indicate that the project has yet
> to be fully endorsed
> by the ASF.
>
>
> Martin
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
I confirm that commits are now enabled. Thanks!
I updated the SVN URL and the email address in the README and root
pom.xml files:
Old: http://svn.apache.org/repos/asf/incubator/sis/trunk
New: http://svn.apache.org/repos/asf/sis/trunk
Old: sis-dev@incubator.apache.org
New: dev@sis.apache.org
Same for "user" and "commit" mailing lists. However I did not yet
updated the web page URL, since this is pending INFRA-5307.
Note that the README file contains the following paragraph, which I
presume is now obsolete. Should we just remove this paragraph, or does
it needs to be replaced by something else?
Apache SIS is an effort undergoing incubation at The Apache Software
Foundation (ASF),
sponsored by the Apache Incubator PMC. Incubation is required of all
newly accepted
projects until a further review indicates that the infrastructure,
communications,
and decision making process have stabilized in a manner consistent
with other successful
ASF projects. While incubation status is not necessarily a
reflection of the completeness
or stability of the code, it does indicate that the project has yet
to be fully endorsed
by the ASF.
Martin
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Wait a sec -- I'm lame. I just read the issue. In fact, Adam can populate the group
all he has to do as the chair is:
1. ssh people.apache.org
2. for uid in set of Apache SIS PMC members
modify_unix_group.pl --add=uid sis
modify_committee.pl --add=uid sis
That's it! :)
Cheers,
Chris
On Sep 23, 2012, at 9:05 AM, Mattmann, Chris A (388J) wrote:
> Hey Guys,
>
> This is an infra@ task -- someone from infra@ needs to do it. Adam I would just
> check with them in a few days if it's not already done yet.
>
> Cheers,
> Chris
>
> On Sep 23, 2012, at 7:32 AM, Adam Estrada wrote:
>
>> I am not sure how to update LDAP. Anyone else know how to take care of that?
>>
>> a
>>
>> On Sun, Sep 23, 2012 at 9:06 AM, Martin Desruisseaux <
>> martin.desruisseaux@geomatys.fr> wrote:
>>
>>> Hello all
>>>
>>> I updated the SVN URL in Jenkins and re-enabled the build.
>>>
>>> I can not commit to the SVN since the graduation. According INFRA-5306
>>> [1], someone needs to populate the LDAP group for SIS. Does someone know
>>> how to proceed?
>>>
>>> Thanks,
>>>
>>> Martin
>>>
>>>
>>> [1] https://issues.apache.org/**jira/browse/INFRA-5306<https://issues.apache.org/jira/browse/INFRA-5306>
>>>
>>>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Guys,
This is an infra@ task -- someone from infra@ needs to do it. Adam I would just
check with them in a few days if it's not already done yet.
Cheers,
Chris
On Sep 23, 2012, at 7:32 AM, Adam Estrada wrote:
> I am not sure how to update LDAP. Anyone else know how to take care of that?
>
> a
>
> On Sun, Sep 23, 2012 at 9:06 AM, Martin Desruisseaux <
> martin.desruisseaux@geomatys.fr> wrote:
>
>> Hello all
>>
>> I updated the SVN URL in Jenkins and re-enabled the build.
>>
>> I can not commit to the SVN since the graduation. According INFRA-5306
>> [1], someone needs to populate the LDAP group for SIS. Does someone know
>> how to proceed?
>>
>> Thanks,
>>
>> Martin
>>
>>
>> [1] https://issues.apache.org/**jira/browse/INFRA-5306<https://issues.apache.org/jira/browse/INFRA-5306>
>>
>>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: SIS TLP Migration
Posted by Adam Estrada <es...@gmail.com>.
I am not sure how to update LDAP. Anyone else know how to take care of that?
a
On Sun, Sep 23, 2012 at 9:06 AM, Martin Desruisseaux <
martin.desruisseaux@geomatys.fr> wrote:
> Hello all
>
> I updated the SVN URL in Jenkins and re-enabled the build.
>
> I can not commit to the SVN since the graduation. According INFRA-5306
> [1], someone needs to populate the LDAP group for SIS. Does someone know
> how to proceed?
>
> Thanks,
>
> Martin
>
>
> [1] https://issues.apache.org/**jira/browse/INFRA-5306<https://issues.apache.org/jira/browse/INFRA-5306>
>
>
Re: SIS TLP Migration
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Hello all
I updated the SVN URL in Jenkins and re-enabled the build.
I can not commit to the SVN since the graduation. According INFRA-5306
[1], someone needs to populate the LDAP group for SIS. Does someone know
how to proceed?
Thanks,
Martin
[1] https://issues.apache.org/jira/browse/INFRA-5306
Re: SIS TLP Migration
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
It seems that the SVN has been moved, thanks! But according
https://issues.apache.org/jira/browse/INFRA-5306 some actions are still
needed for allowing write access?
No rush - this email is just in case it was unnoticed.
Regards,
Martin
Le 21/09/12 10:17, Adam Estrada a écrit :
>> All,
>>
>> https://issues.apache.org/jira/browse/INFRA-5304
>>
>> If you experience any hiccups with SVN or the website...its probably because @infra is working on it.
>>
>> Adam
SIS TLP Migration
Posted by Adam Estrada <es...@gmail.com>.
> All,
>
> https://issues.apache.org/jira/browse/INFRA-5304
>
> If you experience any hiccups with SVN or the website...its probably because @infra is working on it.
>
> Adam
Re: SIS TLP Migration
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Thanks Adam, you rock!
Cheers,
Chris
On Sep 20, 2012, at 6:07 PM, Adam Estrada wrote:
> All,
>
> https://issues.apache.org/jira/browse/INFRA-5304
>
> If you experience any hiccups with SVN or the website...its probably because @infra is working on it.
>
> Adam
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++