EC2 plugin development

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

EC2 plugin development

adphillips
Hi,

I'd like to contribute a fix or two and maybe some features to the EC2 plugin.  What approach is preferred in GitHub, i.e. should I fork and issue pull requests or work off a branch of the main repository?  Don't know if this matters, but back in the java.net days I had core committer access.  Jenkins-ci.org account: adphillips (GitHub account also adphillips)

Also, I'm curious what is the relationship between the EC2 plugin and the GitHub project named "extras-ec2-launcher".  Can someone shed some light on that project.. what's it for/where does it fit in to the EC2 story?

Thanks,
Aaron


Reply | Threaded
Open this post in threaded view
|

Re: EC2 plugin development

riftware-2
It looks like EC2 was merged to fix an issue with a URL endpoint (not
sure if that was your fix or not).    I'm actually in need of that fix
for our Hudson 1.391 installation.   I don't have a compilation
environment setup anymore - would you happen to have a privately built
version of the plugin or know when 1.11 is scheduled to be released?
I can be reached at
riftware
---------- at gmail.com


On Feb 20, 7:18 pm, Aaron Phillips <[hidden email]> wrote:

> Hi,
>
> I'd like to contribute a fix or two and maybe some features to the EC2
> plugin.  What approach is preferred in GitHub, i.e. should I fork and issue
> pull requests or work off a branch of the main repository?  Don't know if
> this matters, but back in the java.net days I had core committer access.
>  Jenkins-ci.org account: adphillips (GitHub account also adphillips)
>
> Also, I'm curious what is the relationship between the EC2 plugin and the
> GitHub project named "extras-ec2-launcher".  Can someone shed some light on
> that project.. what's it for/where does it fit in to the EC2 story?
>
> Thanks,
> Aaron
Reply | Threaded
Open this post in threaded view
|

Re: EC2 plugin development

kohsuke Kawaguchi (CB)
In reply to this post by adphillips
On 02/20/2011 05:18 PM, Aaron Phillips wrote:
> Hi,
>
> I'd like to contribute a fix or two and maybe some features to the EC2
> plugin.  What approach is preferred in GitHub, i.e. should I fork and
> issue pull requests or work off a branch of the main repository?  Don't
> know if this matters, but back in the java.net <http://java.net> days I
> had core committer access.  Jenkins-ci.org account: adphillips (GitHub
> account also adphillips)

The general policy is still the same --- to encourage participation, we
liberally give away the commit access. If you feel that your change
should be checked by someone else (e.g., you are new to that particular
plugin), send in a pull request. If you are pretty sure your changes are
OK, feel free to push directly.

I've given you the full access to all our repositories. I've been
meaning to improve the IRC bot so that this process is streamlined.


> Also, I'm curious what is the relationship between the EC2 plugin and
> the GitHub project named "extras-ec2-launcher".  Can someone shed some
> light on that project.. what's it for/where does it fit in to the EC2 story?

That's a little GUI tool that launches Jenkins on EC2. But I suspect it
needs to be updated. I haven't touched it for a while.


--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/