On Mon, Oct 8, 2012 at 10:58 AM, Benson Margulies wrote:
> On Mon, Oct 8, 2012 at 10:51 AM, Jason van Zyl wrote:
>> It's continuous delivery. Builds happen via CI, they get deployed to Nexus
>> and you pick the one you deem release worthy to go into the catalog by
>> making a pull request to chan
On Mon, Oct 8, 2012 at 10:51 AM, Jason van Zyl wrote:
> It's continuous delivery. Builds happen via CI, they get deployed to Nexus
> and you pick the one you deem release worthy to go into the catalog by
> making a pull request to change the catalog. It will get more sophisticated
> but this is wh
On Mon, Oct 8, 2012 at 10:51 AM, Jason van Zyl wrote:
> It's continuous delivery. Builds happen via CI, they get deployed to Nexus
> and you pick the one you deem release worthy to go into the catalog by
> making a pull request to change the catalog. It will get more sophisticated
> but this is wh
It's continuous delivery. Builds happen via CI, they get deployed to Nexus and
you pick the one you deem release worthy to go into the catalog by making a
pull request to change the catalog. It will get more sophisticated but this is
what it is for now. I will change the triggers so that a build
Jason,
What's your model of 'releases' for plugins connected to your
structure? How does someone who works on the plugin trigger the
process on your end?
--benson
___
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/
I will take a look at your build and I may need to adjust it. I use your build
and Benson's as a starting point for trying to document how the build should be
structured. I deploy whole p2 sites to Nexus which I don't believe many do
because it's a feature set in Nexus Pro that I'm open sourcing
Hi,
> Sure, I'll create a job and deploy it. I'll let you know if there
> are any problems.
What about my Axistools connector?
https://github.com/theit/m2e-lifecycle-axistools
I followed all the discussions recently, but I'm not sure if there's I
need to do...?
Apart from that, thanks for all
Benson,
I need to refactor your build slightly to add the capability to deploy the
update site so I'll do that tomorrow and get it setup.
On Oct 7, 2012, at 5:02 PM, Benson Margulies wrote:
> On Sun, Oct 7, 2012 at 1:30 PM, Jason van Zyl wrote:
>> Simply a directory structure of self-containe
Sure, I'll create a job and deploy it. I'll let you know if there are any
problems.
jvz
On 2012-10-07, at 5:02 PM, Benson Margulies wrote:
> On Sun, Oct 7, 2012 at 1:30 PM, Jason van Zyl wrote:
>> Simply a directory structure of self-contained p2 update sites. I want
>> something distributed
On Sun, Oct 7, 2012 at 1:30 PM, Jason van Zyl wrote:
> Simply a directory structure of self-contained p2 update sites. I want
> something distributed and reliable and while I've never had any problems
> with hosting at Contegix, the EdgeCast setup on Central provides what I'm
> looking for and is
As a big user of m2e I just wanted to say thanks to the sonatype folks
and plugin authors for making it better and easier to use.
-Eric
On 10/7/12 12:30 PM, Jason van Zyl wrote:
Simply a directory structure of self-contained p2 update sites. I want
something distributed and reliable and while
Simply a directory structure of self-contained p2 update sites. I want
something distributed and reliable and while I've never had any problems with
hosting at Contegix, the EdgeCast setup on Central provides what I'm looking
for and is a better long term solution that my Tesla Nexus instance. I
I'm intrigued by Jason's recent off-hand references to plugins
available on Central. I wasn't aware that it was possible to publish
Eclipse plugins on Central, due to the lack of OSGI support on OSSRH
and Central itself? Can someone please point me to a guide? I'll move
the code quality plugins fro
13 matches
Mail list logo
