You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by Les Hazlewood <le...@hazlewood.com> on 2008/07/24 23:49:28 UTC
Fwd: CI and deployment
The folks at Sonatype have set up Continuous Integration for JSecurity for
their own purposes because they're integrating it with Plexus.
Naturally this isn't a substitute for our own CI setup, but I thought you
guys would find it interesting :)
Cheers,
Les
---------- Forwarded message ----------
Hi Les,
just wanted to inform you that because of our plexus-jsecurity integration,
and your note to follow current code, we added JSecurity to our CI:
http://ci.sonatype.org/job/Apache%20JSecurity/
And the result is deployed to our Nexus:
http://repository.sonatype.org/content/repositories/snapshots/org/jsecurity/jsecurity/0.9.0-RC1-SNAPSHOT/
Builds are triggered by SVN change polling.
Have fun,
~t~
Re: CI and deployment
Posted by Jeremy Haile <jh...@fastmail.fm>.
Thanks for sharing - very cool!
On Jul 24, 2008, at 5:49 PM, Les Hazlewood wrote:
> The folks at Sonatype have set up Continuous Integration for
> JSecurity for
> their own purposes because they're integrating it with Plexus.
>
> Naturally this isn't a substitute for our own CI setup, but I
> thought you
> guys would find it interesting :)
>
> Cheers,
>
> Les
>
> ---------- Forwarded message ----------
>
> Hi Les,
>
> just wanted to inform you that because of our plexus-jsecurity
> integration,
> and your note to follow current code, we added JSecurity to our CI:
>
> http://ci.sonatype.org/job/Apache%20JSecurity/
>
> And the result is deployed to our Nexus:
> http://repository.sonatype.org/content/repositories/snapshots/org/jsecurity/jsecurity/0.9.0-RC1-SNAPSHOT/
>
> Builds are triggered by SVN change polling.
>
> Have fun,
> ~t~
Re: Fwd: CI and deployment
Posted by Emmanuel Lécharny <el...@gmail.com>.
Not sure that I didn't replied to Les only, so I forward his answer to
the list.
Les Hazlewood wrote:
> They said that they were running the 'ant jar' task only - not running the
> test suite. I need to ensure they (and we) can do that too.
>
> Although the project team has discussed maven vs. ant+ivy in the past, and I
> don't know if we want to do that again, if there is anyone willing to look
> at making maven builds work as well (without screwing with the existing
> directory structure too much), I'd love to see that happen. Best both
> worlds and all...
>
Well, as much as I hated Maven in the past, I have to admit that it is
now orders of magnitude better now. Would I start a new project, I think
I would use Maven.
Compared to the Log convo we had, I think that the Maven vs Ant case
will be way more easy to set...
Les Hazlewood wrote:
>
> >> Oh, I know :) I was just saying that even though CI has been set up for
> >> our
> >> project by a 3rd party (and it happens to be Hudson), it isn't the Hudson
> >> one that we're going to use in the ASF infrastructure. But it was cool
> >> for
> >> us to see :)
> >>
> >>
>
> FYI, Sonatype is full of Apache peeps... Not really Third party to me :)
>
> The interesting part of the message is that if Sonatype successfully
> integrated JSecurity into their build system, it will be a piece of cake to
> do it on the apache servers !
>
--
--
cordialement, regards,
Emmanuel Lécharny
www.nextury.com
directory.apache.org
Re: Fwd: CI and deployment
Posted by Les Hazlewood <le...@hazlewood.com>.
Oh, I know :) I was just saying that even though CI has been set up for our
project by a 3rd party (and it happens to be Hudson), it isn't the Hudson
one that we're going to use in the ASF infrastructure. But it was cool for
us to see :)
On Thu, Jul 24, 2008 at 7:55 PM, Emmanuel Lecharny <el...@gmail.com>
wrote:
> Les Hazlewood wrote:
>
>> The folks at Sonatype have set up Continuous Integration for JSecurity for
>> their own purposes because they're integrating it with Plexus.
>>
>> Naturally this isn't a substitute for our own CI setup, but I thought you
>> guys would find it interesting :)
>>
>>
> Well, AFAIK, they are using Hudson.
>
> We also have Hudson on ASF servers, we are just waiting for the sources to
> be injected on ASF subversion to have CI running on our own servers :)
>
> --
> --
> cordialement, regards,
> Emmanuel Lécharny
> www.iktek.com
> directory.apache.org
>
>
>
Re: Fwd: CI and deployment
Posted by Emmanuel Lecharny <el...@gmail.com>.
Les Hazlewood wrote:
> The folks at Sonatype have set up Continuous Integration for JSecurity for
> their own purposes because they're integrating it with Plexus.
>
> Naturally this isn't a substitute for our own CI setup, but I thought you
> guys would find it interesting :)
>
Well, AFAIK, they are using Hudson.
We also have Hudson on ASF servers, we are just waiting for the sources
to be injected on ASF subversion to have CI running on our own servers :)
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
Re: CI and deployment
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
That's pretty neat.
Regards,
Alan
On Jul 24, 2008, at 2:49 PM, Les Hazlewood wrote:
> The folks at Sonatype have set up Continuous Integration for
> JSecurity for
> their own purposes because they're integrating it with Plexus.
>
> Naturally this isn't a substitute for our own CI setup, but I
> thought you
> guys would find it interesting :)
>
> Cheers,
>
> Les
>
> ---------- Forwarded message ----------
>
> Hi Les,
>
> just wanted to inform you that because of our plexus-jsecurity
> integration,
> and your note to follow current code, we added JSecurity to our CI:
>
> http://ci.sonatype.org/job/Apache%20JSecurity/
>
> And the result is deployed to our Nexus:
> http://repository.sonatype.org/content/repositories/snapshots/org/jsecurity/jsecurity/0.9.0-RC1-SNAPSHOT/
>
> Builds are triggered by SVN change polling.
>
> Have fun,
> ~t~