Jenkins › Jenkins dev

bundled prototype.js library

Classic

List

Threaded

11 messages Options

Jesse Farinacci

bundled prototype.js library

Greetings,

OHTAKE Tomohiro has isolated a javascript problem[0] with a plugin[1]
(but this applies to another[2]). The core is that we use a pretty old
version of prototype.js, and I'd like to explore what people think as
to updating that library. Since this potentially has a lot of impact,
and not just in core, I don't want to just do it..

Put in perspective, prototype-1.5.1.js was released in mid-2007[3],
and prototype-1.7 was released in end-2011[4].

-Jesse

[0] https://issues.jenkins-ci.org/browse/JENKINS-11618
[1] https://wiki.jenkins-ci.org/display/JENKINS/HTML5+Notifier+Plugin
[2] https://wiki.jenkins-ci.org/display/JENKINS/Keyboard+Shortcuts+Plugin
[3] http://www.prototypejs.org/2007/5/1/prototype-1-5-1-released
[4] http://www.prototypejs.org/2010/11/22/prototype-1-7

--
There are 10 types of people in this world, those
that can read binary and those that can not.

Remove Ads

Lars Hvile

Re: bundled prototype.js library

My slightly peripheral plugin =), the html audio notifier, depends on the current prototype version.
At least it was designed for 1.5 since that what was Jenkins already provided.
How would you implement/coordinate this kind of update without breaking any plugins?

--
Lars Hvile

On Thu, 2012-02-02 at 16:46 +0100, Jesse Farinacci wrote:

> Greetings,
>
> OHTAKE Tomohiro has isolated a javascript problem[0] with a plugin[1]
> (but this applies to another[2]). The core is that we use a pretty old
> version of prototype.js, and I'd like to explore what people think as
> to updating that library. Since this potentially has a lot of impact,
> and not just in core, I don't want to just do it..
>
> Put in perspective, prototype-1.5.1.js was released in mid-2007[3],
> and prototype-1.7 was released in end-2011[4].
>
> -Jesse
>
> [0] https://issues.jenkins-ci.org/browse/JENKINS-11618
> [1] https://wiki.jenkins-ci.org/display/JENKINS/HTML5+Notifier+Plugin
> [2] https://wiki.jenkins-ci.org/display/JENKINS/Keyboard+Shortcuts+Plugin
> [3] http://www.prototypejs.org/2007/5/1/prototype-1-5-1-released
> [4] http://www.prototypejs.org/2010/11/22/prototype-1-7
>

Jesse Farinacci

Re: bundled prototype.js library

Greetings,

On Thu, Feb 2, 2012 at 2:03 PM, Lars Hvile <[hidden email]> wrote:
> My slightly peripheral plugin =), the html audio notifier, depends on the current prototype version.
> At least it was designed for 1.5 since that what was Jenkins already provided.

Are you sure that it depends on that specific version? I expect
prototype to be mostly backwards compatible. There was JENKINS-11618
which I think is probably an oddball case, but I was able to fix it by
adding the breaking function to my prototype-1.7.js.

> How would you implement/coordinate this kind of update without breaking any plugins?

By doing exactly this, mailing the jenkinsci-dev list and requesting
comments. I don't think there is any way to guarantee protection for
plugins, which is yet another reason why statically typed languages
are superior to dynamic/weakly typed languages. ;-)

Anyhow, I don't want a flame war, so I'll close with: I think we can
try to test the ones we know require prototype and see if they can
work with the 1.7 version. Validate and/or fix them, then update core,
and see what breaks... I don't think there is anything more we can do
than that, but again, I am requesting comments.

-Jesse

--
There are 10 types of people in this world, those
that can read binary and those that can not.

Lars Hvile

Re: bundled prototype.js library

I haven't checked it, it may work with out of the box with 1.7, and I
would certainly fix it quickly if it broke anyway. I just got the
feeling that something may be 'wrong' with the way prototype is shared.

>> I don't think there is any way to guarantee protection for plugins

If the plugins had some way of expressing which shared libs they
expected/required you could at least get some idea about the scope of
the update.

Guaranteed protection would probably mean no sharing of external libs at
all, but that doesn't seem very practical, if at all possible.

--
Lars Hvile

On Thu, 2012-02-02 at 20:44 +0100, Jesse Farinacci wrote:

> Greetings,
>
> On Thu, Feb 2, 2012 at 2:03 PM, Lars Hvile <[hidden email]> wrote:
> > My slightly peripheral plugin =), the html audio notifier, depends on the current prototype version.
> > At least it was designed for 1.5 since that what was Jenkins already provided.
>
> Are you sure that it depends on that specific version? I expect
> prototype to be mostly backwards compatible. There was JENKINS-11618
> which I think is probably an oddball case, but I was able to fix it by
> adding the breaking function to my prototype-1.7.js.
>
> > How would you implement/coordinate this kind of update without breaking any plugins?
>
> By doing exactly this, mailing the jenkinsci-dev list and requesting
> comments. I don't think there is any way to guarantee protection for
> plugins, which is yet another reason why statically typed languages
> are superior to dynamic/weakly typed languages. ;-)
>
> Anyhow, I don't want a flame war, so I'll close with: I think we can
> try to test the ones we know require prototype and see if they can
> work with the 1.7 version. Validate and/or fix them, then update core,
> and see what breaks... I don't think there is anything more we can do
> than that, but again, I am requesting comments.
>
> -Jesse
>

Emanuele Zattin

Re: bundled prototype.js library

In reply to this post by Jesse Farinacci

I'd surely welcome an update of the library.

On Feb 2, 4:46 pm, Jesse Farinacci <[hidden email]> wrote:

> Greetings,
>
> OHTAKE Tomohiro has isolated a javascript problem[0] with a plugin[1]
> (but this applies to another[2]). The core is that we use a pretty old
> version ofprototype.js, and I'd like to explore what people think as
> to updating that library. Since this potentially has a lot of impact,
> and not just in core, I don't want to just do it..
>
> Put in perspective,prototype-1.5.1.js was released in mid-2007[3],
> andprototype-1.7 was released in end-2011[4].
>
> -Jesse
>
> [0]https://issues.jenkins-ci.org/browse/JENKINS-11618
> [1]https://wiki.jenkins-ci.org/display/JENKINS/HTML5+Notifier+Plugin
> [2]https://wiki.jenkins-ci.org/display/JENKINS/Keyboard+Shortcuts+Plugin
> [3]http://www.prototypejs.org/2007/5/1/prototype-1-5-1-released
> [4]http://www.prototypejs.org/2010/11/22/prototype-1-7
>
> --
> There are 10 types of people in this world, those
> that can read binary and those that can not.

kohsuke Kawaguchi (CB)

Re: bundled prototype.js library

In reply to this post by Jesse Farinacci

Coming late to the party.

I've integrated Prototype 1.7 toward 1.454.

I've created 'prototype-incoming' branch to track the inbound pristine
prototype.js copy.

There are several patches made to prototype.js, for example to
transparently support Crumb. This change incorporates those local
changes, and I've created prototype-patched branch to keep track of
those changes, which would simplify future upgrade of prototype.js, if
it ever happens.

I encourage keyboard shortcuts plugin and html5-notifier plugin to rely
on 1.454.4 to avoid bundling its own version of prototype.js for two
reasons --- first, those copies do not have the patches needed, and
second, if in the future core updates to newer version of prototype.js,
those plugins will again break.

On 02/02/2012 07:46 AM, Jesse Farinacci wrote:

--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

Emanuele Zattin

Re: bundled prototype.js library

I know it's a more complicated change but is there any chance to have
YUI3 as well?

BR,

Emanuele Zattin
---------------------------------------------------
-I don't have to know an answer. I don't feel frightened by not
knowing things; by being lost in a mysterious universe without any
purpose — which is the way it really is, as far as I can tell,
possibly. It doesn't frighten me.- Richard Feynman

On Fri, Mar 2, 2012 at 7:42 AM, Kohsuke Kawaguchi
<[hidden email]> wrote:

>
> Coming late to the party.
>
> I've integrated Prototype 1.7 toward 1.454.
>
> I've created 'prototype-incoming' branch to track the inbound pristine
> prototype.js copy.
>
> There are several patches made to prototype.js, for example to transparently
> support Crumb. This change incorporates those local changes, and I've
> created prototype-patched branch to keep track of those changes, which would
> simplify future upgrade of prototype.js, if it ever happens.
>
> I encourage keyboard shortcuts plugin and html5-notifier plugin to rely on
> 1.454.4 to avoid bundling its own version of prototype.js for two reasons
> --- first, those copies do not have the patches needed, and second, if in
> the future core updates to newer version of prototype.js, those plugins will
> again break.
>
>
>
> On 02/02/2012 07:46 AM, Jesse Farinacci wrote:
>>
>> Greetings,
>>
>> OHTAKE Tomohiro has isolated a javascript problem[0] with a plugin[1]
>> (but this applies to another[2]). The core is that we use a pretty old
>> version of prototype.js, and I'd like to explore what people think as
>> to updating that library. Since this potentially has a lot of impact,
>> and not just in core, I don't want to just do it..
>>
>> Put in perspective, prototype-1.5.1.js was released in mid-2007[3],
>> and prototype-1.7 was released in end-2011[4].
>>
>> -Jesse
>>
>> [0] https://issues.jenkins-ci.org/browse/JENKINS-11618
>> [1] https://wiki.jenkins-ci.org/display/JENKINS/HTML5+Notifier+Plugin
>> [2] https://wiki.jenkins-ci.org/display/JENKINS/Keyboard+Shortcuts+Plugin
>> [3] http://www.prototypejs.org/2007/5/1/prototype-1-5-1-released
>> [4] http://www.prototypejs.org/2010/11/22/prototype-1-7
>>
>
>
> --
> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
> Try Nectar, our professional version of Jenkins

kohsuke Kawaguchi (CB)

Re: bundled prototype.js library

On 03/02/2012 12:30 AM, Emanuele Zattin wrote:
> I know it's a more complicated change but is there any chance to have
> YUI3 as well?

My understanding is that YUI3 is drastically different from YUI2 to the
point that there's no hope of fixing up backward compatibility.

But maybe it is possible for YUI2 and YUI3 to live side by side, in
which case perhaps we can have YUI3 plugin that bundles them, and have
interested plugins depend on it.

--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

Emanuele Zattin

Re: bundled prototype.js library

I did some reading and it looks like YUI 3 has a compatibility mode
for 2.9... here's an interesting read:

http://andrewwooldridge.com/blog/2010/03/27/yui3-and-a-quiet-revolution/

I wonder how much of that is applicable to our beloved Jenkins.

BR,

Emanuele Zattin
---------------------------------------------------
-I don't have to know an answer. I don't feel frightened by not
knowing things; by being lost in a mysterious universe without any
purpose — which is the way it really is, as far as I can tell,
possibly. It doesn't frighten me.- Richard Feynman

On Fri, Mar 2, 2012 at 5:19 PM, Kohsuke Kawaguchi
<[hidden email]> wrote:

> On 03/02/2012 12:30 AM, Emanuele Zattin wrote:
>>
>> I know it's a more complicated change but is there any chance to have
>> YUI3 as well?
>
>
> My understanding is that YUI3 is drastically different from YUI2 to the
> point that there's no hope of fixing up backward compatibility.
>
> But maybe it is possible for YUI2 and YUI3 to live side by side, in which
> case perhaps we can have YUI3 plugin that bundles them, and have interested
> plugins depend on it.
>
>
>
>>
>> BR,
>>
>> Emanuele Zattin
>> ---------------------------------------------------
>> -I don't have to know an answer. I don't feel frightened by not
>> knowing things; by being lost in a mysterious universe without any
>> purpose — which is the way it really is, as far as I can tell,
>> possibly. It doesn't frighten me.- Richard Feynman
>>
>>
>>
>> On Fri, Mar 2, 2012 at 7:42 AM, Kohsuke Kawaguchi
>> <[hidden email]> wrote:
>>>
>>>
>>> Coming late to the party.
>>>
>>> I've integrated Prototype 1.7 toward 1.454.
>>>
>>> I've created 'prototype-incoming' branch to track the inbound pristine
>>> prototype.js copy.
>>>
>>> There are several patches made to prototype.js, for example to
>>> transparently
>>> support Crumb. This change incorporates those local changes, and I've
>>> created prototype-patched branch to keep track of those changes, which
>>> would
>>> simplify future upgrade of prototype.js, if it ever happens.
>>>
>>> I encourage keyboard shortcuts plugin and html5-notifier plugin to rely
>>> on
>>> 1.454.4 to avoid bundling its own version of prototype.js for two
>>> reasons
>>> --- first, those copies do not have the patches needed, and second, if
>>> in
>>> the future core updates to newer version of prototype.js, those plugins
>>> will
>>> again break.
>>>
>>>
>>>
>>> On 02/02/2012 07:46 AM, Jesse Farinacci wrote:
>>>>
>>>>
>>>> Greetings,
>>>>
>>>> OHTAKE Tomohiro has isolated a javascript problem[0] with a plugin[1]
>>>> (but this applies to another[2]). The core is that we use a pretty old
>>>> version of prototype.js, and I'd like to explore what people think as
>>>> to updating that library. Since this potentially has a lot of impact,
>>>> and not just in core, I don't want to just do it..
>>>>
>>>> Put in perspective, prototype-1.5.1.js was released in mid-2007[3],
>>>> and prototype-1.7 was released in end-2011[4].
>>>>
>>>> -Jesse
>>>>
>>>> [0] https://issues.jenkins-ci.org/browse/JENKINS-11618
>>>> [1] https://wiki.jenkins-ci.org/display/JENKINS/HTML5+Notifier+Plugin
>>>> [2]
>>>> https://wiki.jenkins-ci.org/display/JENKINS/Keyboard+Shortcuts+Plugin
>>>> [3] http://www.prototypejs.org/2007/5/1/prototype-1-5-1-released
>>>> [4] http://www.prototypejs.org/2010/11/22/prototype-1-7
>>>>
>>>
>>>
>>> --
>>> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
>>> Try Nectar, our professional version of Jenkins
>>
>>
>
>
> --
> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
> Try Nectar, our professional version of Jenkins

kohsuke Kawaguchi (CB)

Re: bundled prototype.js library

On 03/02/2012 08:22 AM, Emanuele Zattin wrote:
> I did some reading and it looks like YUI 3 has a compatibility mode
> for 2.9... here's an interesting read:
>
> http://andrewwooldridge.com/blog/2010/03/27/yui3-and-a-quiet-revolution/
>
> I wonder how much of that is applicable to our beloved Jenkins.

I've used that module to integrate YUI3 into Jenkins and pushed the yui3
branch. It passes all the tests, but this is a fairly big change.

Anyone willing to try out their favorite plugins that use YUI with this
for backward compatibility?

>
> BR,
>
> Emanuele Zattin
> ---------------------------------------------------
> -I don't have to know an answer. I don't feel frightened by not
> knowing things; by being lost in a mysterious universe without any
> purpose — which is the way it really is, as far as I can tell,
> possibly. It doesn't frighten me.- Richard Feynman
>
>
>
> On Fri, Mar 2, 2012 at 5:19 PM, Kohsuke Kawaguchi
> <[hidden email]> wrote:
>> On 03/02/2012 12:30 AM, Emanuele Zattin wrote:
>>>
>>> I know it's a more complicated change but is there any chance to have
>>> YUI3 as well?
>>
>>
>> My understanding is that YUI3 is drastically different from YUI2 to the
>> point that there's no hope of fixing up backward compatibility.
>>
>> But maybe it is possible for YUI2 and YUI3 to live side by side, in which
>> case perhaps we can have YUI3 plugin that bundles them, and have interested
>> plugins depend on it.
>>
>>
>>
>>>
>>> BR,
>>>
>>> Emanuele Zattin
>>> ---------------------------------------------------
>>> -I don't have to know an answer. I don't feel frightened by not
>>> knowing things; by being lost in a mysterious universe without any
>>> purpose — which is the way it really is, as far as I can tell,
>>> possibly. It doesn't frighten me.- Richard Feynman
>>>
>>>
>>>
>>> On Fri, Mar 2, 2012 at 7:42 AM, Kohsuke Kawaguchi
>>> <[hidden email]> wrote:
>>>>
>>>>
>>>> Coming late to the party.
>>>>
>>>> I've integrated Prototype 1.7 toward 1.454.
>>>>
>>>> I've created 'prototype-incoming' branch to track the inbound pristine
>>>> prototype.js copy.
>>>>
>>>> There are several patches made to prototype.js, for example to
>>>> transparently
>>>> support Crumb. This change incorporates those local changes, and I've
>>>> created prototype-patched branch to keep track of those changes, which
>>>> would
>>>> simplify future upgrade of prototype.js, if it ever happens.
>>>>
>>>> I encourage keyboard shortcuts plugin and html5-notifier plugin to rely
>>>> on
>>>> 1.454.4 to avoid bundling its own version of prototype.js for two
>>>> reasons
>>>> --- first, those copies do not have the patches needed, and second, if
>>>> in
>>>> the future core updates to newer version of prototype.js, those plugins
>>>> will
>>>> again break.
>>>>
>>>>
>>>>
>>>> On 02/02/2012 07:46 AM, Jesse Farinacci wrote:
>>>>>
>>>>>
>>>>> Greetings,
>>>>>
>>>>> OHTAKE Tomohiro has isolated a javascript problem[0] with a plugin[1]
>>>>> (but this applies to another[2]). The core is that we use a pretty old
>>>>> version of prototype.js, and I'd like to explore what people think as
>>>>> to updating that library. Since this potentially has a lot of impact,
>>>>> and not just in core, I don't want to just do it..
>>>>>
>>>>> Put in perspective, prototype-1.5.1.js was released in mid-2007[3],
>>>>> and prototype-1.7 was released in end-2011[4].
>>>>>
>>>>> -Jesse
>>>>>
>>>>> [0] https://issues.jenkins-ci.org/browse/JENKINS-11618
>>>>> [1] https://wiki.jenkins-ci.org/display/JENKINS/HTML5+Notifier+Plugin
>>>>> [2]
>>>>> https://wiki.jenkins-ci.org/display/JENKINS/Keyboard+Shortcuts+Plugin
>>>>> [3] http://www.prototypejs.org/2007/5/1/prototype-1-5-1-released
>>>>> [4] http://www.prototypejs.org/2010/11/22/prototype-1-7
>>>>>
>>>>
>>>>
>>>> --
>>>> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
>>>> Try Nectar, our professional version of Jenkins
>>>
>>>
>>
>>
>> --
>> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
>> Try Nectar, our professional version of Jenkins
>

--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

Emanuele Zattin

Re: bundled prototype.js library

I'm building it to give it a try with a new plugin I'm developing
which is pretty JS intensive.

Thank you Kohsuke

Emanuele Zattin
---------------------------------------------------
-I don't have to know an answer. I don't feel frightened by not
knowing things; by being lost in a mysterious universe without any
purpose — which is the way it really is, as far as I can tell,
possibly. It doesn't frighten me.- Richard Feynman

On Sat, Mar 3, 2012 at 4:18 AM, Kohsuke Kawaguchi
<[hidden email]> wrote:

> On 03/02/2012 08:22 AM, Emanuele Zattin wrote:
>>
>> I did some reading and it looks like YUI 3 has a compatibility mode
>> for 2.9... here's an interesting read:
>>
>> http://andrewwooldridge.com/blog/2010/03/27/yui3-and-a-quiet-revolution/
>>
>> I wonder how much of that is applicable to our beloved Jenkins.
>
>
> I've used that module to integrate YUI3 into Jenkins and pushed the yui3
> branch. It passes all the tests, but this is a fairly big change.
>
> Anyone willing to try out their favorite plugins that use YUI with this for
> backward compatibility?
>
>
>>
>> BR,
>>
>> Emanuele Zattin
>> ---------------------------------------------------
>> -I don't have to know an answer. I don't feel frightened by not
>> knowing things; by being lost in a mysterious universe without any
>> purpose — which is the way it really is, as far as I can tell,
>> possibly. It doesn't frighten me.- Richard Feynman
>>
>>
>>
>> On Fri, Mar 2, 2012 at 5:19 PM, Kohsuke Kawaguchi
>> <[hidden email]> wrote:
>>>
>>> On 03/02/2012 12:30 AM, Emanuele Zattin wrote:
>>>>
>>>>
>>>> I know it's a more complicated change but is there any chance to have
>>>> YUI3 as well?
>>>
>>>
>>>
>>> My understanding is that YUI3 is drastically different from YUI2 to the
>>> point that there's no hope of fixing up backward compatibility.
>>>
>>> But maybe it is possible for YUI2 and YUI3 to live side by side, in
>>> which
>>> case perhaps we can have YUI3 plugin that bundles them, and have
>>> interested
>>> plugins depend on it.
>>>
>>>
>>>
>>>>
>>>> BR,
>>>>
>>>> Emanuele Zattin
>>>> ---------------------------------------------------
>>>> -I don't have to know an answer. I don't feel frightened by not
>>>> knowing things; by being lost in a mysterious universe without any
>>>> purpose — which is the way it really is, as far as I can tell,
>>>> possibly. It doesn't frighten me.- Richard Feynman
>>>>
>>>>
>>>>
>>>> On Fri, Mar 2, 2012 at 7:42 AM, Kohsuke Kawaguchi
>>>> <[hidden email]> wrote:
>>>>>
>>>>>
>>>>>
>>>>> Coming late to the party.
>>>>>
>>>>> I've integrated Prototype 1.7 toward 1.454.
>>>>>
>>>>> I've created 'prototype-incoming' branch to track the inbound
>>>>> pristine
>>>>> prototype.js copy.
>>>>>
>>>>> There are several patches made to prototype.js, for example to
>>>>> transparently
>>>>> support Crumb. This change incorporates those local changes, and I've
>>>>> created prototype-patched branch to keep track of those changes,
>>>>> which
>>>>> would
>>>>> simplify future upgrade of prototype.js, if it ever happens.
>>>>>
>>>>> I encourage keyboard shortcuts plugin and html5-notifier plugin to
>>>>> rely
>>>>> on
>>>>> 1.454.4 to avoid bundling its own version of prototype.js for two
>>>>> reasons
>>>>> --- first, those copies do not have the patches needed, and second,
>>>>> if
>>>>> in
>>>>> the future core updates to newer version of prototype.js, those
>>>>> plugins
>>>>> will
>>>>> again break.
>>>>>
>>>>>
>>>>>
>>>>> On 02/02/2012 07:46 AM, Jesse Farinacci wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Greetings,
>>>>>>
>>>>>> OHTAKE Tomohiro has isolated a javascript problem[0] with a
>>>>>> plugin[1]
>>>>>> (but this applies to another[2]). The core is that we use a pretty
>>>>>> old
>>>>>> version of prototype.js, and I'd like to explore what people think
>>>>>> as
>>>>>> to updating that library. Since this potentially has a lot of
>>>>>> impact,
>>>>>> and not just in core, I don't want to just do it..
>>>>>>
>>>>>> Put in perspective, prototype-1.5.1.js was released in mid-2007[3],
>>>>>> and prototype-1.7 was released in end-2011[4].
>>>>>>
>>>>>> -Jesse
>>>>>>
>>>>>> [0] https://issues.jenkins-ci.org/browse/JENKINS-11618
>>>>>> [1]
>>>>>> https://wiki.jenkins-ci.org/display/JENKINS/HTML5+Notifier+Plugin
>>>>>> [2]
>>>>>> https://wiki.jenkins-ci.org/display/JENKINS/Keyboard+Shortcuts+Plugin
>>>>>> [3] http://www.prototypejs.org/2007/5/1/prototype-1-5-1-released
>>>>>> [4] http://www.prototypejs.org/2010/11/22/prototype-1-7
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
>>>>> Try Nectar, our professional version of Jenkins
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
>>> Try Nectar, our professional version of Jenkins
>>
>>
>
>
> --
> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
> Try Nectar, our professional version of Jenkins