You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@any23.apache.org by Lewis John Mcgibbney <le...@gmail.com> on 2011/11/13 21:15:49 UTC
Jenkins build online
Hi everyone,
Just a quick note to say that I've set us up a Jenkins build which can be
found here [1]. Currently as you know, the code is being pulled from google
code so I will ensure that the build is updated when the code is moved into
the apache SVN repo.
There are some underlying issues with the build. I haven't had time to look
closely but will get round to it at some stage. For ther record, is anyone
aware of failing tests?
Finally, on a slightly different topic, can someone advise if Any23 is
available within Maven repo? I would like to think about a Any23 Nutch
plugin.
Thanks for now
Lewis
[1] https://builds.apache.org/job/Any23%20trunk/
--
*Lewis*
Re: Jenkins build online
Posted by Lewis John Mcgibbney <le...@gmail.com>.
This is a +1 from me. It's nice to see that we have a healthy build online,
once code is over @ Apache SVN I suppose it's time to get stuck into some
issues!
Thank you
Lewis
On Fri, Nov 18, 2011 at 9:06 AM, Michele Mostarda <
michele.mostarda@gmail.com> wrote:
> On 18 November 2011 06:49, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
> > On Nov 16, 2011, at 3:20 AM, Michele Mostarda wrote:
> >
> > > On 16 November 2011 12:11, Michele Mostarda <
> michele.mostarda@gmail.com
> > >wrote:
> > >
> > > I can login in Jenkins but I have no permissions to change the project
> > > configuration.
> > > Who should I ask to have admin access ?
> > >
> >
> > Me. :-) PMC chairs can take of this for you, and I happen to have a few
> of
> > those hats.
> >
> > Here ya go!
> >
>
> Well guys, I just renamed the Any23 project name from 'Any23 trunk' to
> 'Any23-trunk'[1]
> and the plugin manager returned working. Now we have 0 test failures.
>
> Reported an issue [2].
>
> About the startup plan:
>
>
> > 1. SVN dump Google code right now to Apache
> > 2. Finish up whatever is going on at Google code
> > 3. Merge into SVN at Apache
> > 4. Make 0.7.0 release at Apache
>
> Tomorrow I would spend some time tomorrow on points (1) and (2).
> If anybody is online and wants to contact me in realtime
> my Skype contact is 'michele.mostarda' .
>
> Everybody agree?
>
> The best.
>
> Mic
>
> [1] https://builds.apache.org/view/A-F/view/Any23/job/Any23-trunk/
> [2] https://issues.apache.org/jira/browse/ANY23-20
>
>
> > Per: http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson
> >
> > [mattmann@minotaur]/home/mattmann(24):
> modify_appgroups.plhudson-jobadmin --add=mostarda
> > LDAP Password (^D aborts):
> > Done!
> > Notification sent to <ro...@apache.org>.
> > [mattmann@minotaur]/home/mattmann(25):
> >
> > Cheers,
> > Chris
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 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
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >
>
>
> --
> Michele Mostarda
> Senior Software Engineer
> skype: michele.mostarda
> twitter: micmos
> mail: me@michelemostarda.com
> site : http://www.michelemostarda.com
>
--
*Lewis*
Re: Jenkins build online
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Please ignore my last comment.
OK (hopefully) soon to be resolved in INFRA-4146
Thanks for logging and progressing.
Lewis
On Tue, Nov 22, 2011 at 4:57 PM, Lewis John Mcgibbney <
lewis.mcgibbney@gmail.com> wrote:
> Hmmm...
>
> Is it possible to do an import from a local copy of the code? If I'm
> honest I've never initiated a new repository but hoping this may be a work
> around!
> Try here for resources on this
>
> http://svnbook.red-bean.com/en/1.7/svn.tour.importing.html#svn.tour.importing.import
>
> hth
>
>
> On Tue, Nov 22, 2011 at 4:28 PM, Michele Mostarda <
> michele.mostarda@gmail.com> wrote:
>
>> Hi Chris, guys,
>>
>> does anybody know a good strategy for importing the SVN content of a
>> Google Code project (in this case Any23)
>> to the Apache SVN repository?
>>
>> I tried with svnsync with the procedure [1] but the svnsych init requires
>> that the destination path is the
>> SVN root (https://svn.apache.org/repos/asf) and not a sub path (
>> https://svn.apache.org/repos/asf/incubator/any23/) .
>>
>> The best.
>>
>> Mic
>>
>> [1] <<<<
>> $ svnsync init https://svn.apache.org/repos/asf/incubator/any23/
>> https://any23.googlecode.com/svn
>> $ svnsync sync https://svn.apache.org/repos/asf/incubator/any23
>> >>>>
>>
>> On 18 November 2011 19:22, Mattmann, Chris A (388J) <
>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>
>> > Hi Michele,
>> >
>> > You ROCK. Thanks for pushing this forward!
>> >
>> > Cheers,
>> > Chris
>> >
>> > On Nov 18, 2011, at 1:06 AM, Michele Mostarda wrote:
>> >
>> > > On 18 November 2011 06:49, Mattmann, Chris A (388J) <
>> > > chris.a.mattmann@jpl.nasa.gov> wrote:
>> > >
>> > >> On Nov 16, 2011, at 3:20 AM, Michele Mostarda wrote:
>> > >>
>> > >>> On 16 November 2011 12:11, Michele Mostarda <
>> > michele.mostarda@gmail.com
>> > >>> wrote:
>> > >>>
>> > >>> I can login in Jenkins but I have no permissions to change the
>> project
>> > >>> configuration.
>> > >>> Who should I ask to have admin access ?
>> > >>>
>> > >>
>> > >> Me. :-) PMC chairs can take of this for you, and I happen to have a
>> few
>> > of
>> > >> those hats.
>> > >>
>> > >> Here ya go!
>> > >>
>> > >
>> > > Well guys, I just renamed the Any23 project name from 'Any23 trunk'
>> to
>> > > 'Any23-trunk'[1]
>> > > and the plugin manager returned working. Now we have 0 test failures.
>> > >
>> > > Reported an issue [2].
>> > >
>> > > About the startup plan:
>> > >
>> > >
>> > >> 1. SVN dump Google code right now to Apache
>> > >> 2. Finish up whatever is going on at Google code
>> > >> 3. Merge into SVN at Apache
>> > >> 4. Make 0.7.0 release at Apache
>> > >
>> > > Tomorrow I would spend some time tomorrow on points (1) and (2).
>> > > If anybody is online and wants to contact me in realtime
>> > > my Skype contact is 'michele.mostarda' .
>> > >
>> > > Everybody agree?
>> > >
>> > > The best.
>> > >
>> > > Mic
>> > >
>> > > [1] https://builds.apache.org/view/A-F/view/Any23/job/Any23-trunk/
>> > > [2] https://issues.apache.org/jira/browse/ANY23-20
>> > >
>> > >
>> > >> Per:
>> http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson
>> > >>
>> > >> [mattmann@minotaur]/home/mattmann(24):
>> > modify_appgroups.plhudson-jobadmin --add=mostarda
>> > >> LDAP Password (^D aborts):
>> > >> Done!
>> > >> Notification sent to <ro...@apache.org>.
>> > >> [mattmann@minotaur]/home/mattmann(25):
>> > >>
>> > >> Cheers,
>> > >> Chris
>> > >>
>> > >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > >> 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
>> > >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > >>
>> > >>
>> > >
>> > >
>> > > --
>> > > Michele Mostarda
>> > > Senior Software Engineer
>> > > skype: michele.mostarda
>> > > twitter: micmos
>> > > mail: me@michelemostarda.com
>> > > site : http://www.michelemostarda.com
>> >
>> >
>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > 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
>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> >
>> >
>>
>>
>> --
>> Michele Mostarda
>> Senior Software Engineer
>> skype: michele.mostarda
>> twitter: micmos
>> mail: me@michelemostarda.com
>> site : http://www.michelemostarda.com
>>
>
>
>
> --
> *Lewis*
>
>
--
*Lewis*
Re: Jenkins build online
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hmmm...
Is it possible to do an import from a local copy of the code? If I'm honest
I've never initiated a new repository but hoping this may be a work around!
Try here for resources on this
http://svnbook.red-bean.com/en/1.7/svn.tour.importing.html#svn.tour.importing.import
hth
On Tue, Nov 22, 2011 at 4:28 PM, Michele Mostarda <
michele.mostarda@gmail.com> wrote:
> Hi Chris, guys,
>
> does anybody know a good strategy for importing the SVN content of a
> Google Code project (in this case Any23)
> to the Apache SVN repository?
>
> I tried with svnsync with the procedure [1] but the svnsych init requires
> that the destination path is the
> SVN root (https://svn.apache.org/repos/asf) and not a sub path (
> https://svn.apache.org/repos/asf/incubator/any23/) .
>
> The best.
>
> Mic
>
> [1] <<<<
> $ svnsync init https://svn.apache.org/repos/asf/incubator/any23/
> https://any23.googlecode.com/svn
> $ svnsync sync https://svn.apache.org/repos/asf/incubator/any23
> >>>>
>
> On 18 November 2011 19:22, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
> > Hi Michele,
> >
> > You ROCK. Thanks for pushing this forward!
> >
> > Cheers,
> > Chris
> >
> > On Nov 18, 2011, at 1:06 AM, Michele Mostarda wrote:
> >
> > > On 18 November 2011 06:49, Mattmann, Chris A (388J) <
> > > chris.a.mattmann@jpl.nasa.gov> wrote:
> > >
> > >> On Nov 16, 2011, at 3:20 AM, Michele Mostarda wrote:
> > >>
> > >>> On 16 November 2011 12:11, Michele Mostarda <
> > michele.mostarda@gmail.com
> > >>> wrote:
> > >>>
> > >>> I can login in Jenkins but I have no permissions to change the
> project
> > >>> configuration.
> > >>> Who should I ask to have admin access ?
> > >>>
> > >>
> > >> Me. :-) PMC chairs can take of this for you, and I happen to have a
> few
> > of
> > >> those hats.
> > >>
> > >> Here ya go!
> > >>
> > >
> > > Well guys, I just renamed the Any23 project name from 'Any23 trunk' to
> > > 'Any23-trunk'[1]
> > > and the plugin manager returned working. Now we have 0 test failures.
> > >
> > > Reported an issue [2].
> > >
> > > About the startup plan:
> > >
> > >
> > >> 1. SVN dump Google code right now to Apache
> > >> 2. Finish up whatever is going on at Google code
> > >> 3. Merge into SVN at Apache
> > >> 4. Make 0.7.0 release at Apache
> > >
> > > Tomorrow I would spend some time tomorrow on points (1) and (2).
> > > If anybody is online and wants to contact me in realtime
> > > my Skype contact is 'michele.mostarda' .
> > >
> > > Everybody agree?
> > >
> > > The best.
> > >
> > > Mic
> > >
> > > [1] https://builds.apache.org/view/A-F/view/Any23/job/Any23-trunk/
> > > [2] https://issues.apache.org/jira/browse/ANY23-20
> > >
> > >
> > >> Per:
> http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson
> > >>
> > >> [mattmann@minotaur]/home/mattmann(24):
> > modify_appgroups.plhudson-jobadmin --add=mostarda
> > >> LDAP Password (^D aborts):
> > >> Done!
> > >> Notification sent to <ro...@apache.org>.
> > >> [mattmann@minotaur]/home/mattmann(25):
> > >>
> > >> Cheers,
> > >> Chris
> > >>
> > >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > >> 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
> > >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > >>
> > >>
> > >
> > >
> > > --
> > > Michele Mostarda
> > > Senior Software Engineer
> > > skype: michele.mostarda
> > > twitter: micmos
> > > mail: me@michelemostarda.com
> > > site : http://www.michelemostarda.com
> >
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 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
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >
>
>
> --
> Michele Mostarda
> Senior Software Engineer
> skype: michele.mostarda
> twitter: micmos
> mail: me@michelemostarda.com
> site : http://www.michelemostarda.com
>
--
*Lewis*
Re: Jenkins build online
Posted by Michele Mostarda <mi...@gmail.com>.
Hi Chris, guys,
does anybody know a good strategy for importing the SVN content of a
Google Code project (in this case Any23)
to the Apache SVN repository?
I tried with svnsync with the procedure [1] but the svnsych init requires
that the destination path is the
SVN root (https://svn.apache.org/repos/asf) and not a sub path (
https://svn.apache.org/repos/asf/incubator/any23/) .
The best.
Mic
[1] <<<<
$ svnsync init https://svn.apache.org/repos/asf/incubator/any23/
https://any23.googlecode.com/svn
$ svnsync sync https://svn.apache.org/repos/asf/incubator/any23
>>>>
On 18 November 2011 19:22, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> Hi Michele,
>
> You ROCK. Thanks for pushing this forward!
>
> Cheers,
> Chris
>
> On Nov 18, 2011, at 1:06 AM, Michele Mostarda wrote:
>
> > On 18 November 2011 06:49, Mattmann, Chris A (388J) <
> > chris.a.mattmann@jpl.nasa.gov> wrote:
> >
> >> On Nov 16, 2011, at 3:20 AM, Michele Mostarda wrote:
> >>
> >>> On 16 November 2011 12:11, Michele Mostarda <
> michele.mostarda@gmail.com
> >>> wrote:
> >>>
> >>> I can login in Jenkins but I have no permissions to change the project
> >>> configuration.
> >>> Who should I ask to have admin access ?
> >>>
> >>
> >> Me. :-) PMC chairs can take of this for you, and I happen to have a few
> of
> >> those hats.
> >>
> >> Here ya go!
> >>
> >
> > Well guys, I just renamed the Any23 project name from 'Any23 trunk' to
> > 'Any23-trunk'[1]
> > and the plugin manager returned working. Now we have 0 test failures.
> >
> > Reported an issue [2].
> >
> > About the startup plan:
> >
> >
> >> 1. SVN dump Google code right now to Apache
> >> 2. Finish up whatever is going on at Google code
> >> 3. Merge into SVN at Apache
> >> 4. Make 0.7.0 release at Apache
> >
> > Tomorrow I would spend some time tomorrow on points (1) and (2).
> > If anybody is online and wants to contact me in realtime
> > my Skype contact is 'michele.mostarda' .
> >
> > Everybody agree?
> >
> > The best.
> >
> > Mic
> >
> > [1] https://builds.apache.org/view/A-F/view/Any23/job/Any23-trunk/
> > [2] https://issues.apache.org/jira/browse/ANY23-20
> >
> >
> >> Per: http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson
> >>
> >> [mattmann@minotaur]/home/mattmann(24):
> modify_appgroups.plhudson-jobadmin --add=mostarda
> >> LDAP Password (^D aborts):
> >> Done!
> >> Notification sent to <ro...@apache.org>.
> >> [mattmann@minotaur]/home/mattmann(25):
> >>
> >> Cheers,
> >> Chris
> >>
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> 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
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>
> >>
> >
> >
> > --
> > Michele Mostarda
> > Senior Software Engineer
> > skype: michele.mostarda
> > twitter: micmos
> > mail: me@michelemostarda.com
> > site : http://www.michelemostarda.com
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
--
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com
Re: Jenkins build online
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Michele,
You ROCK. Thanks for pushing this forward!
Cheers,
Chris
On Nov 18, 2011, at 1:06 AM, Michele Mostarda wrote:
> On 18 November 2011 06:49, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> On Nov 16, 2011, at 3:20 AM, Michele Mostarda wrote:
>>
>>> On 16 November 2011 12:11, Michele Mostarda <michele.mostarda@gmail.com
>>> wrote:
>>>
>>> I can login in Jenkins but I have no permissions to change the project
>>> configuration.
>>> Who should I ask to have admin access ?
>>>
>>
>> Me. :-) PMC chairs can take of this for you, and I happen to have a few of
>> those hats.
>>
>> Here ya go!
>>
>
> Well guys, I just renamed the Any23 project name from 'Any23 trunk' to
> 'Any23-trunk'[1]
> and the plugin manager returned working. Now we have 0 test failures.
>
> Reported an issue [2].
>
> About the startup plan:
>
>
>> 1. SVN dump Google code right now to Apache
>> 2. Finish up whatever is going on at Google code
>> 3. Merge into SVN at Apache
>> 4. Make 0.7.0 release at Apache
>
> Tomorrow I would spend some time tomorrow on points (1) and (2).
> If anybody is online and wants to contact me in realtime
> my Skype contact is 'michele.mostarda' .
>
> Everybody agree?
>
> The best.
>
> Mic
>
> [1] https://builds.apache.org/view/A-F/view/Any23/job/Any23-trunk/
> [2] https://issues.apache.org/jira/browse/ANY23-20
>
>
>> Per: http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson
>>
>> [mattmann@minotaur]/home/mattmann(24): modify_appgroups.plhudson-jobadmin --add=mostarda
>> LDAP Password (^D aborts):
>> Done!
>> Notification sent to <ro...@apache.org>.
>> [mattmann@minotaur]/home/mattmann(25):
>>
>> Cheers,
>> Chris
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>
>
> --
> Michele Mostarda
> Senior Software Engineer
> skype: michele.mostarda
> twitter: micmos
> mail: me@michelemostarda.com
> site : http://www.michelemostarda.com
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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: Jenkins build online
Posted by Michele Mostarda <mi...@gmail.com>.
On 18 November 2011 06:49, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> On Nov 16, 2011, at 3:20 AM, Michele Mostarda wrote:
>
> > On 16 November 2011 12:11, Michele Mostarda <michele.mostarda@gmail.com
> >wrote:
> >
> > I can login in Jenkins but I have no permissions to change the project
> > configuration.
> > Who should I ask to have admin access ?
> >
>
> Me. :-) PMC chairs can take of this for you, and I happen to have a few of
> those hats.
>
> Here ya go!
>
Well guys, I just renamed the Any23 project name from 'Any23 trunk' to
'Any23-trunk'[1]
and the plugin manager returned working. Now we have 0 test failures.
Reported an issue [2].
About the startup plan:
> 1. SVN dump Google code right now to Apache
> 2. Finish up whatever is going on at Google code
> 3. Merge into SVN at Apache
> 4. Make 0.7.0 release at Apache
Tomorrow I would spend some time tomorrow on points (1) and (2).
If anybody is online and wants to contact me in realtime
my Skype contact is 'michele.mostarda' .
Everybody agree?
The best.
Mic
[1] https://builds.apache.org/view/A-F/view/Any23/job/Any23-trunk/
[2] https://issues.apache.org/jira/browse/ANY23-20
> Per: http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson
>
> [mattmann@minotaur]/home/mattmann(24): modify_appgroups.plhudson-jobadmin --add=mostarda
> LDAP Password (^D aborts):
> Done!
> Notification sent to <ro...@apache.org>.
> [mattmann@minotaur]/home/mattmann(25):
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
--
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com
Re: Jenkins build online
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
On Nov 16, 2011, at 3:20 AM, Michele Mostarda wrote:
> On 16 November 2011 12:11, Michele Mostarda <mi...@gmail.com>wrote:
>
> I can login in Jenkins but I have no permissions to change the project
> configuration.
> Who should I ask to have admin access ?
>
Me. :-) PMC chairs can take of this for you, and I happen to have a few of those hats.
Here ya go!
Per: http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson
[mattmann@minotaur]/home/mattmann(24): modify_appgroups.pl hudson-jobadmin --add=mostarda
LDAP Password (^D aborts):
Done!
Notification sent to <ro...@apache.org>.
[mattmann@minotaur]/home/mattmann(25):
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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: Jenkins build online
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi,
Take a look here please
http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson#How_do_I_get_an_account
On Wed, Nov 16, 2011 at 11:20 AM, Michele Mostarda <
michele.mostarda@gmail.com> wrote:
> On 16 November 2011 12:11, Michele Mostarda <michele.mostarda@gmail.com
> >wrote:
>
Thank you
Re: Jenkins build online
Posted by Michele Mostarda <mi...@gmail.com>.
On 16 November 2011 12:11, Michele Mostarda <mi...@gmail.com>wrote:
>
>
> On 15 November 2011 20:52, Lewis John Mcgibbney <lewis.mcgibbney@gmail.com
> > wrote:
>
>> Hi,
>>
>
> Hi Guys,
>
>>
>> Just quickly, a new build page can be seen here [1].
>>
>> I must say that I agree with Chris in the respect that your concerns are
>> understood regarding migration of code and the subsequent effect that this
>> has on 0.7.0 release etc. But it also means that as an incubating
>> community
>> we are unable to begin working on the ASF Any23 codebase until this is
>> completed. Personally, the quicker the codecase can be dumped in SVN the
>> eariler I can begin working on it, addressing some of the Jira issues and
>> the better this will be for the project as an exciting incubating
>> component.
>>
>
> I agree that it is important to start ASAP.
> If we cannot keep the original package it is not a big deal. Let's start.
>
>
>> One last thing, thanks for logging the issue we discovered through the
>> Jenkins build, if the solution is trivial then as a committer you should
>> be
>> able to sign up to Jenkins and change the workspace name.
>
>
> Will have a look this evening. If the workaround will not work I will
> fix the PluginManager with high priority.
>
I can login in Jenkins but I have no permissions to change the project
configuration.
Who should I ask to have admin access ?
>
>> I will look at the issue in more detail shortly though and hopefully we
>> can be a stable
>> nightly build sorted out before any 0.7.0 release.
>>
>> Thank you
>>
>
> Thanks you too!
>
>
>>
>> Lewis
>>
>
> Mic
>
>
>>
>> [1] https://builds.apache.org/view/A-F/view/Any23/
>>
>> On Mon, Nov 14, 2011 at 3:20 PM, Mattmann, Chris A (388J) <
>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>
>> > Hi Michele,
>> >
>> > On Nov 14, 2011, at 2:11 AM, Michele Mostarda wrote:
>> >
>> > > On 13 November 2011 21:22, Mattmann, Chris A (388J) <
>> > > chris.a.mattmann@jpl.nasa.gov> wrote:
>> > >
>> > >> Guys, speaking of which:
>> > >>
>> > >> I think it's time for a code import, no? I see we're still
>> referencing
>> > the
>> > >> Google
>> > >> Code SVN here.
>> > >>
>> > >
>> > > I agree, let's go ahead.
>> > >
>> > > I'm pushing with the 0.7.0 release but the ETA is not completely
>> under my
>> > > control :)
>> >
>> > :-) No worries.
>> >
>> > Now that the project is at Apache, we need to make sure that any release
>> > that occurs follows the Incubator project release guidelines, here:
>> >
>> > http://incubator.apache.org/guides/releasemanagement.html
>> >
>> > Yes, this is a huge document :-) Yes, this is why I'm asking the
>> question
>> > now.
>> >
>> > I know in certain special cases, Apache has allowed a project coming
>> into
>> > Incubation to do any one of the following things:
>> >
>> > 1. preserve the namespace packaging (I think as you suggest below),
>> e.g.,
>> > com.foo.mypackage on the initial Apache release, to maintain some level
>> > of back compat and then move to org.apache.mypackage after that.
>> >
>> > 2. release at some other organization (e.g., Google Code) e.g., in the
>> > case of
>> > Subversion releasing at CollabNet. NOTE: this was highly *not*
>> encouraged
>> > but was allowed due to Subversion's close collaboration with the ASF and
>> > foundation-like status.
>> >
>> > 3. Some combination of the above.
>> >
>> > I know in all cases, 1-3 above are *not* preferred compared to simply:
>> >
>> > 1. Moving the code to the ASF SVN and hardware
>> > 2. Distributing all bits there
>> > 3. Moving all discussion from the external entity to all the ASF mailing
>> > lists.
>> >
>> > Since we're early in Incubation, it might make most sense to simply take
>> > care
>> > of 1-3 now.
>> >
>> >
>> > >
>> > > My only concern is that a code repackaging in the Apache repo would
>> make
>> > > really painful
>> > > a merge with the subsequent code developed for the 0.7.0 release in
>> the
>> > > Google code.
>> >
>> > I hear you. Can you elaborate on what would be required other than a
>> > namespace
>> > change, and moving the bits to SVN? One option might be to (in
>> parallel):
>> >
>> > 1. SVN dump Google code right now to Apache
>> > 2. Finish up whatever is going on at Google code
>> > 3. Merge into SVN at Apache
>> > 4. Make 0.7.0 release at Apache
>> >
>> > Would that work?
>> >
>> > >
>> > > A workaround would be to preserve the original source packaging until
>> the
>> > > final 0.7.0 merge,
>> > > (and the dismission of the Google Code repo).
>> >
>> > Yep, I think this is 1-4 above, right?
>> >
>> > >
>> > > Is that possible?
>> >
>> > It's definitely possible if we're talking about 1-4 :-)
>> >
>> > >
>> > >
>> > >>
>> > >> Can we make it a priority over the next week or two to get Any23 code
>> > into
>> > >> https://svn.apache.org/repos/asf/incubator/any23/? I'd be happy to
>> grab
>> > >> the latest trunk from Google code and do the import? Alternatively
>> > another
>> > >> approach would be to try and svnadmin dump the full history and then
>> > >> work with INFRA to import it. Any preferences?
>> > >>
>> > >
>> > > Adding you (Chris) as admin of the Any23 Google Code prj [1].
>> > > Let me know if you need any support.
>> >
>> > Thanks. I'll try and dump the SVN out of there over the next few days
>> > and do an import into the ASF SVN. I'll get in touch with infra@ and
>> > CC this list to keep folks up to date.
>> >
>> > >
>> > > The best.
>> >
>> > You too!
>> >
>> > Cheers,
>> > Chris
>> >
>> >
>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > 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
>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> >
>> >
>>
>>
>> --
>> *Lewis*
>>
>
>
>
> --
> Michele Mostarda
> Senior Software Engineer
> skype: michele.mostarda
> twitter: micmos
> mail: me@michelemostarda.com
> site : http://www.michelemostarda.com
>
>
--
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com
Re: Jenkins build online
Posted by Michele Mostarda <mi...@gmail.com>.
On 15 November 2011 20:52, Lewis John Mcgibbney
<le...@gmail.com>wrote:
> Hi,
>
Hi Guys,
>
> Just quickly, a new build page can be seen here [1].
>
> I must say that I agree with Chris in the respect that your concerns are
> understood regarding migration of code and the subsequent effect that this
> has on 0.7.0 release etc. But it also means that as an incubating community
> we are unable to begin working on the ASF Any23 codebase until this is
> completed. Personally, the quicker the codecase can be dumped in SVN the
> eariler I can begin working on it, addressing some of the Jira issues and
> the better this will be for the project as an exciting incubating
> component.
>
I agree that it is important to start ASAP.
If we cannot keep the original package it is not a big deal. Let's start.
> One last thing, thanks for logging the issue we discovered through the
> Jenkins build, if the solution is trivial then as a committer you should be
> able to sign up to Jenkins and change the workspace name.
Will have a look this evening. If the workaround will not work I will
fix the PluginManager with high priority.
> I will look at the issue in more detail shortly though and hopefully we
> can be a stable
> nightly build sorted out before any 0.7.0 release.
>
> Thank you
>
Thanks you too!
>
> Lewis
>
Mic
>
> [1] https://builds.apache.org/view/A-F/view/Any23/
>
> On Mon, Nov 14, 2011 at 3:20 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
> > Hi Michele,
> >
> > On Nov 14, 2011, at 2:11 AM, Michele Mostarda wrote:
> >
> > > On 13 November 2011 21:22, Mattmann, Chris A (388J) <
> > > chris.a.mattmann@jpl.nasa.gov> wrote:
> > >
> > >> Guys, speaking of which:
> > >>
> > >> I think it's time for a code import, no? I see we're still referencing
> > the
> > >> Google
> > >> Code SVN here.
> > >>
> > >
> > > I agree, let's go ahead.
> > >
> > > I'm pushing with the 0.7.0 release but the ETA is not completely under
> my
> > > control :)
> >
> > :-) No worries.
> >
> > Now that the project is at Apache, we need to make sure that any release
> > that occurs follows the Incubator project release guidelines, here:
> >
> > http://incubator.apache.org/guides/releasemanagement.html
> >
> > Yes, this is a huge document :-) Yes, this is why I'm asking the question
> > now.
> >
> > I know in certain special cases, Apache has allowed a project coming into
> > Incubation to do any one of the following things:
> >
> > 1. preserve the namespace packaging (I think as you suggest below), e.g.,
> > com.foo.mypackage on the initial Apache release, to maintain some level
> > of back compat and then move to org.apache.mypackage after that.
> >
> > 2. release at some other organization (e.g., Google Code) e.g., in the
> > case of
> > Subversion releasing at CollabNet. NOTE: this was highly *not* encouraged
> > but was allowed due to Subversion's close collaboration with the ASF and
> > foundation-like status.
> >
> > 3. Some combination of the above.
> >
> > I know in all cases, 1-3 above are *not* preferred compared to simply:
> >
> > 1. Moving the code to the ASF SVN and hardware
> > 2. Distributing all bits there
> > 3. Moving all discussion from the external entity to all the ASF mailing
> > lists.
> >
> > Since we're early in Incubation, it might make most sense to simply take
> > care
> > of 1-3 now.
> >
> >
> > >
> > > My only concern is that a code repackaging in the Apache repo would
> make
> > > really painful
> > > a merge with the subsequent code developed for the 0.7.0 release in
> the
> > > Google code.
> >
> > I hear you. Can you elaborate on what would be required other than a
> > namespace
> > change, and moving the bits to SVN? One option might be to (in parallel):
> >
> > 1. SVN dump Google code right now to Apache
> > 2. Finish up whatever is going on at Google code
> > 3. Merge into SVN at Apache
> > 4. Make 0.7.0 release at Apache
> >
> > Would that work?
> >
> > >
> > > A workaround would be to preserve the original source packaging until
> the
> > > final 0.7.0 merge,
> > > (and the dismission of the Google Code repo).
> >
> > Yep, I think this is 1-4 above, right?
> >
> > >
> > > Is that possible?
> >
> > It's definitely possible if we're talking about 1-4 :-)
> >
> > >
> > >
> > >>
> > >> Can we make it a priority over the next week or two to get Any23 code
> > into
> > >> https://svn.apache.org/repos/asf/incubator/any23/? I'd be happy to
> grab
> > >> the latest trunk from Google code and do the import? Alternatively
> > another
> > >> approach would be to try and svnadmin dump the full history and then
> > >> work with INFRA to import it. Any preferences?
> > >>
> > >
> > > Adding you (Chris) as admin of the Any23 Google Code prj [1].
> > > Let me know if you need any support.
> >
> > Thanks. I'll try and dump the SVN out of there over the next few days
> > and do an import into the ASF SVN. I'll get in touch with infra@ and
> > CC this list to keep folks up to date.
> >
> > >
> > > The best.
> >
> > You too!
> >
> > Cheers,
> > Chris
> >
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 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
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >
>
>
> --
> *Lewis*
>
--
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com
Re: Jenkins build online
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi,
Just quickly, a new build page can be seen here [1].
I must say that I agree with Chris in the respect that your concerns are
understood regarding migration of code and the subsequent effect that this
has on 0.7.0 release etc. But it also means that as an incubating community
we are unable to begin working on the ASF Any23 codebase until this is
completed. Personally, the quicker the codecase can be dumped in SVN the
eariler I can begin working on it, addressing some of the Jira issues and
the better this will be for the project as an exciting incubating component.
One last thing, thanks for logging the issue we discovered through the
Jenkins build, if the solution is trivial then as a committer you should be
able to sign up to Jenkins and change the workspace name. I will look at
the issue in more detail shortly though and hopefully we can be a stable
nightly build sorted out before any 0.7.0 release.
Thank you
Lewis
[1] https://builds.apache.org/view/A-F/view/Any23/
On Mon, Nov 14, 2011 at 3:20 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> Hi Michele,
>
> On Nov 14, 2011, at 2:11 AM, Michele Mostarda wrote:
>
> > On 13 November 2011 21:22, Mattmann, Chris A (388J) <
> > chris.a.mattmann@jpl.nasa.gov> wrote:
> >
> >> Guys, speaking of which:
> >>
> >> I think it's time for a code import, no? I see we're still referencing
> the
> >> Google
> >> Code SVN here.
> >>
> >
> > I agree, let's go ahead.
> >
> > I'm pushing with the 0.7.0 release but the ETA is not completely under my
> > control :)
>
> :-) No worries.
>
> Now that the project is at Apache, we need to make sure that any release
> that occurs follows the Incubator project release guidelines, here:
>
> http://incubator.apache.org/guides/releasemanagement.html
>
> Yes, this is a huge document :-) Yes, this is why I'm asking the question
> now.
>
> I know in certain special cases, Apache has allowed a project coming into
> Incubation to do any one of the following things:
>
> 1. preserve the namespace packaging (I think as you suggest below), e.g.,
> com.foo.mypackage on the initial Apache release, to maintain some level
> of back compat and then move to org.apache.mypackage after that.
>
> 2. release at some other organization (e.g., Google Code) e.g., in the
> case of
> Subversion releasing at CollabNet. NOTE: this was highly *not* encouraged
> but was allowed due to Subversion's close collaboration with the ASF and
> foundation-like status.
>
> 3. Some combination of the above.
>
> I know in all cases, 1-3 above are *not* preferred compared to simply:
>
> 1. Moving the code to the ASF SVN and hardware
> 2. Distributing all bits there
> 3. Moving all discussion from the external entity to all the ASF mailing
> lists.
>
> Since we're early in Incubation, it might make most sense to simply take
> care
> of 1-3 now.
>
>
> >
> > My only concern is that a code repackaging in the Apache repo would make
> > really painful
> > a merge with the subsequent code developed for the 0.7.0 release in the
> > Google code.
>
> I hear you. Can you elaborate on what would be required other than a
> namespace
> change, and moving the bits to SVN? One option might be to (in parallel):
>
> 1. SVN dump Google code right now to Apache
> 2. Finish up whatever is going on at Google code
> 3. Merge into SVN at Apache
> 4. Make 0.7.0 release at Apache
>
> Would that work?
>
> >
> > A workaround would be to preserve the original source packaging until the
> > final 0.7.0 merge,
> > (and the dismission of the Google Code repo).
>
> Yep, I think this is 1-4 above, right?
>
> >
> > Is that possible?
>
> It's definitely possible if we're talking about 1-4 :-)
>
> >
> >
> >>
> >> Can we make it a priority over the next week or two to get Any23 code
> into
> >> https://svn.apache.org/repos/asf/incubator/any23/? I'd be happy to grab
> >> the latest trunk from Google code and do the import? Alternatively
> another
> >> approach would be to try and svnadmin dump the full history and then
> >> work with INFRA to import it. Any preferences?
> >>
> >
> > Adding you (Chris) as admin of the Any23 Google Code prj [1].
> > Let me know if you need any support.
>
> Thanks. I'll try and dump the SVN out of there over the next few days
> and do an import into the ASF SVN. I'll get in touch with infra@ and
> CC this list to keep folks up to date.
>
> >
> > The best.
>
> You too!
>
> Cheers,
> Chris
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
--
*Lewis*
Re: Jenkins build online
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Michele,
On Nov 14, 2011, at 2:11 AM, Michele Mostarda wrote:
> On 13 November 2011 21:22, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> Guys, speaking of which:
>>
>> I think it's time for a code import, no? I see we're still referencing the
>> Google
>> Code SVN here.
>>
>
> I agree, let's go ahead.
>
> I'm pushing with the 0.7.0 release but the ETA is not completely under my
> control :)
:-) No worries.
Now that the project is at Apache, we need to make sure that any release
that occurs follows the Incubator project release guidelines, here:
http://incubator.apache.org/guides/releasemanagement.html
Yes, this is a huge document :-) Yes, this is why I'm asking the question now.
I know in certain special cases, Apache has allowed a project coming into
Incubation to do any one of the following things:
1. preserve the namespace packaging (I think as you suggest below), e.g.,
com.foo.mypackage on the initial Apache release, to maintain some level
of back compat and then move to org.apache.mypackage after that.
2. release at some other organization (e.g., Google Code) e.g., in the case of
Subversion releasing at CollabNet. NOTE: this was highly *not* encouraged
but was allowed due to Subversion's close collaboration with the ASF and
foundation-like status.
3. Some combination of the above.
I know in all cases, 1-3 above are *not* preferred compared to simply:
1. Moving the code to the ASF SVN and hardware
2. Distributing all bits there
3. Moving all discussion from the external entity to all the ASF mailing lists.
Since we're early in Incubation, it might make most sense to simply take care
of 1-3 now.
>
> My only concern is that a code repackaging in the Apache repo would make
> really painful
> a merge with the subsequent code developed for the 0.7.0 release in the
> Google code.
I hear you. Can you elaborate on what would be required other than a namespace
change, and moving the bits to SVN? One option might be to (in parallel):
1. SVN dump Google code right now to Apache
2. Finish up whatever is going on at Google code
3. Merge into SVN at Apache
4. Make 0.7.0 release at Apache
Would that work?
>
> A workaround would be to preserve the original source packaging until the
> final 0.7.0 merge,
> (and the dismission of the Google Code repo).
Yep, I think this is 1-4 above, right?
>
> Is that possible?
It's definitely possible if we're talking about 1-4 :-)
>
>
>>
>> Can we make it a priority over the next week or two to get Any23 code into
>> https://svn.apache.org/repos/asf/incubator/any23/? I'd be happy to grab
>> the latest trunk from Google code and do the import? Alternatively another
>> approach would be to try and svnadmin dump the full history and then
>> work with INFRA to import it. Any preferences?
>>
>
> Adding you (Chris) as admin of the Any23 Google Code prj [1].
> Let me know if you need any support.
Thanks. I'll try and dump the SVN out of there over the next few days
and do an import into the ASF SVN. I'll get in touch with infra@ and
CC this list to keep folks up to date.
>
> The best.
You too!
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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: Jenkins build online
Posted by Michele Mostarda <mi...@gmail.com>.
On 13 November 2011 21:22, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> Guys, speaking of which:
>
> I think it's time for a code import, no? I see we're still referencing the
> Google
> Code SVN here.
>
I agree, let's go ahead.
I'm pushing with the 0.7.0 release but the ETA is not completely under my
control :)
My only concern is that a code repackaging in the Apache repo would make
really painful
a merge with the subsequent code developed for the 0.7.0 release in the
Google code.
A workaround would be to preserve the original source packaging until the
final 0.7.0 merge,
(and the dismission of the Google Code repo).
Is that possible?
>
> Can we make it a priority over the next week or two to get Any23 code into
> https://svn.apache.org/repos/asf/incubator/any23/? I'd be happy to grab
> the latest trunk from Google code and do the import? Alternatively another
> approach would be to try and svnadmin dump the full history and then
> work with INFRA to import it. Any preferences?
>
Adding you (Chris) as admin of the Any23 Google Code prj [1].
Let me know if you need any support.
The best.
Mic
[1] http://code.google.com/p/any23
> Cheers,
> Chris
>
>
[1]
> On Nov 13, 2011, at 12:15 PM, Lewis John Mcgibbney wrote:
>
> > Hi everyone,
> >
> > Just a quick note to say that I've set us up a Jenkins build which can be
> > found here [1]. Currently as you know, the code is being pulled from
> google
> > code so I will ensure that the build is updated when the code is moved
> into
> > the apache SVN repo.
> >
> > There are some underlying issues with the build. I haven't had time to
> look
> > closely but will get round to it at some stage. For ther record, is
> anyone
> > aware of failing tests?
> >
> > Finally, on a slightly different topic, can someone advise if Any23 is
> > available within Maven repo? I would like to think about a Any23 Nutch
> > plugin.
> >
> > Thanks for now
> >
> > Lewis
> >
> > [1] https://builds.apache.org/job/Any23%20trunk/
> >
> > --
> > *Lewis*
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
--
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com
Re: Jenkins build online
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Guys, speaking of which:
I think it's time for a code import, no? I see we're still referencing the Google
Code SVN here.
Can we make it a priority over the next week or two to get Any23 code into
https://svn.apache.org/repos/asf/incubator/any23/? I'd be happy to grab
the latest trunk from Google code and do the import? Alternatively another
approach would be to try and svnadmin dump the full history and then
work with INFRA to import it. Any preferences?
Cheers,
Chris
On Nov 13, 2011, at 12:15 PM, Lewis John Mcgibbney wrote:
> Hi everyone,
>
> Just a quick note to say that I've set us up a Jenkins build which can be
> found here [1]. Currently as you know, the code is being pulled from google
> code so I will ensure that the build is updated when the code is moved into
> the apache SVN repo.
>
> There are some underlying issues with the build. I haven't had time to look
> closely but will get round to it at some stage. For ther record, is anyone
> aware of failing tests?
>
> Finally, on a slightly different topic, can someone advise if Any23 is
> available within Maven repo? I would like to think about a Any23 Nutch
> plugin.
>
> Thanks for now
>
> Lewis
>
> [1] https://builds.apache.org/job/Any23%20trunk/
>
> --
> *Lewis*
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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: Jenkins build online
Posted by Michele Mostarda <mi...@gmail.com>.
Hi Lewis,
On 13 November 2011 21:15, Lewis John Mcgibbney
<le...@gmail.com>wrote:
> Hi everyone,
>
> Just a quick note to say that I've set us up a Jenkins build which can be
> found here [1]. Currently as you know, the code is being pulled from google
> code so I will ensure that the build is updated when the code is moved into
> the apache SVN repo.
>
> There are some underlying issues with the build. I haven't had time to look
> closely but will get round to it at some stage. For ther record, is anyone
> aware of failing tests?
>
I just had a quick look, it seems the failures are raised by the Any23
plugin manager
which is performing auto detection on a path containing a whitespace.
[/home/jenkins/jenkins-slave/workspace/Any23%20trunk/any23-core/target/classes]
It seems a bug, I opened an issue [1].
A possible workaround would be to replace the workspace 'Any23 trunk' in
'Any23-trunk' or similar.
> Finally, on a slightly different topic, can someone advise if Any23 is
> available within Maven repo? I would like to think about a Any23 Nutch
> plugin.
>
Sure, there is a Maven repo build on the http+svn googlecode repo,
you can follow instructions in [2].
The Best.
Mic
[1] http://code.google.com/p/any23/issues/detail?id=205
[2] http://code.google.com/p/any23/wiki/MavenUsageGuide
> Thanks for now
>
> Lewis
>
> [1] https://builds.apache.org/job/Any23%20trunk/
>
> --
> *Lewis*
>
--
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com