I think this is a great idea, Julien looks to have done a lot of work, and
that sort of time commitment will be very helpful.
Julien, feel free to contact me if you have questions and I will try and be
responsive. And welcome!
On Wed, 19 Sep 2018 at 19:04, Baptiste Mathus wrote:
> +1.
>
>
And to confirm, I support this.
On Fri, 17 Aug 2018 at 10:31, Fabrizio Manfredi
wrote:
> Hi,
> I'd like to adopt the ec2-plugin. I discussed briefly with the maintainer and
> he doesn't have objection.
> My credential are :
> GitHub Login: thoulen
> Jenkins Login: thoulen
>
> I will send a pull
For a slave, is the remoteFs (like /var/jenkins) supposed to be created by
the user or by Jenkins? I can't find any code where Jenkins creates it, and
the description in the ec2 plugin is not clear. Should the ec2-plugin
create this if it's not present (this seems wrong to me)? If the user is
I would appreciate that. I don't have time to test many things these days,
so mainly I just look at the PRs to see if they make sense. If you can do
some actual testing, then maybe we can accept more of them. If you would
like to be a maintainer, I can put you on the list for that and you can
have
Perfect, thanks so much!
On Mon, Aug 21, 2017 at 2:40 AM, Daniel Beck <m...@beckweb.net> wrote:
>
> > On 21. Aug 2017, at 06:29, Francis UPTON IV <franc...@gmail.com> wrote:
> >
> > I have subsequently fixed master, which builds fine, but I can't figure
> out
I took a pull request that had a compile error in a Javadoc comment, and
then I added the Jenkinsfile to cause the ec2-plugin to be part of the new
build environment.
It built all of the existing PRs, but they call failed because of the
compile error in the master branch.
I have subsequently
Alicia,
I'm still around, but I have not been able to spend much time on this. I
have (finally) reacted to your PR, and I think I can spend at least a
little time reviewing PRs.
If you would like commit rights to the plugin though, I would not have any
problem with that. More people helping
grant you those permissions.
>
> Cheers
>
> Le 7 mai 2016 7:07 PM, <johnny.shie...@gmail.com> a écrit :
> Hi Jenkins team,
>
> Francis Upton who maintains the ec2-plugin has invited me to be a maintainer.
> Please grant me access to JIRA, Github, the Jenkins d
I would to have a look at and potentially change the settings on the
ec2-plugin repo (I want to make sure both merge and squash commits are
allowed).
It seems I don't have permissions to do so.
Can someone either grant me permissions or check this?
Thanks,
Francis
--
Cell +1 510 432 1589
Let me elaborate in my reply just a bit, see my embedded comments.
tl;dr - I don't support giving Mateusz commit rights.
On Thu, Mar 31, 2016 at 2:26 PM, Francis Upton <franc...@gmail.com> wrote:
> I have just reviewed the pull request and found some minor issues. I will
> m
I have just reviewed the pull request and found some minor issues. I will merge
it when they are corrected. Sorry for my delay in reviewing it. I'm very part
time with this however I have been consistently working one it for some years
now.
Sent from my iPhone
> On Mar 31, 2016, at 01:06,
I have a question about this
PR: https://github.com/jenkinsci/ec2-plugin/pull/179
It will have a sleep loop when launching an ec2 spot instance, which can
take some time (minutes).
Is this implemented in the right place so that it won't entirely lock up
Jenkins while the instance is being
Hi,
Cloudbees support told me I need to have someone on the Jenkins team hook
me up so I can launch a plugin build on the Jenkins build service. I'm the
maintainer of the ec2 plugin. My Id is francisu.
Can someone help me?
Thanks,
Francis
--
You received this message because you are
Yes, but in this case, a build failed because it timed out (due to network
problems apparently), and I could not restart it. I would like to have a
little flexibility.
On Mon, Jan 25, 2016 at 12:14 PM, Daniel Beck <m...@beckweb.net> wrote:
>
> On 25.01.2016, at 20:57, Francis UPT
Hi all,
I'm the maintainer of the EC2 plugin and I had a look at the ECS plugin to
see if there is anything in common and it appears after looking a few
minutes that there really is not much. I would certainly be happy to
entertain extending the EC2 plugin to support the ECS service if it makes
Hi Martin,
Here are the instructions with a bunch of hints:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
The way it has worked for me is to use version 2.5 of the mvn release
plugin (using the prepare and release on the same line).
To get going again, you need to delete the tag
[ERROR] Failed to execute goal on project ec2: Could not resolve
dependencies for project org.jenkins-ci.plugins:ec2:hpi:1.22: The
following artifacts could not be resolved:
org.jenkins-ci.main:jenkins-war:war:1.447,
org.jenkins-ci.main:jenkins-war:jar:war-for-test:1.447: Could not
transfer
The console output from this job:
https://jenkins.ci.cloudbees.com/job/plugins/job/ec2-plugin/104/
On Fri, Jun 27, 2014 at 8:37 PM, Mark Waite mark.earl.wa...@gmail.com
wrote:
Your disc is full?
On Fri, Jun 27, 2014 at 9:36 PM, Francis Upton franc...@gmail.com wrote:
[ERROR] Failed
Hi David, you are now a committer. Enjoy!
On Fri, Aug 9, 2013 at 5:37 AM, David Beer david.m.b...@gmail.com wrote:
Hi Guys
I am trying to find out how to update the s3-plugin. I have submitted a
pull request #17 on github for an update to support Region selection which
solves JENKINS-18839
This is great work Hugh, thanks for the contribution!
Can you make a pull request for your EC2 plugin tweaks so we can get them
in?
I think I see why putting this into src/test won't really work, you need to
have these available in the main code, so making a separate plugin make
sense.
I have
Hugh, this is excellent, would it be too much trouble for you to update the
Wiki? There are instructions there.
https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-Eclipse
If you do this, then people will really be able to find it.
Thanks,
Francis
On Fri, Jul 26, 2013
Since Google has announced their cloud offering and it appears to be
similar to EC2 in principle, we should have a corresponding Jenkins plugin
to address it.
In an ideal world, we should probably start with the EC2 plugin and find
all of the common bits and move them into Jenkins core. There has
Perhaps one thing to consider might just be a Cloud plugin that supports
EC2, Google and others. Or perhaps there could be a general cloud plugin
that provides the common infrastructure that the other plugins depend on.
I would be interested in the thoughts on this by the more senior Jenkins
This is from a recent build at the Ant plugin (and the same thing happens
in the EC2 plugin).
Can someone have a look?
Thanks!
[ERROR] Unresolveable build extension: Plugin
org.jenkins-ci.tools:maven-hpi-plugin:1.74 or one of its dependencies
could not be resolved: Could not find artifact
This is the work of many contributors over the last few months to increase
the reliability of the plugin.
The next release of the plugin will have additional fixes that require a
very recent version of Jenkins, and will also likely have contributed
functionality to handle spot pricing.
Many
For EC2 nodes, they can be quite long lived and have some extra
configuration that can be different for different instances which is why we
want to keep their state across Jenkins restarts.
On Tue, Mar 26, 2013 at 12:55 PM, Jesse Glick jgl...@cloudbees.com wrote:
On 03/26/2013 03:05 PM, Kevin
On Sat, Sep 15, 2012 at 7:32 AM, Francis Upton franc...@gmail.com wrote:
This describes how to do it, a group admin needs to do it:
http://support.google.com/groups/bin/answer.py?hl=enanswer=46319
This will make it a lot easier to manage the emails.
Thanks!
--
Cell 510 432
Hi,
I have been doing most of the committer work on the EC2 plugin the last few
months, but I don't get notified of any bug reports because Kohsuke is
listed as the lead for the plugin in JIRA, he gets automatically assigned
to the EC2 bugs.
Can the lead be changed to me (francisu,
This describes how to do it, a group admin needs to do it:
http://support.google.com/groups/bin/answer.py?hl=enanswer=46319
This will make it a lot easier to manage the emails.
Thanks!
--
Cell 510 432 1589
or is this a bug?
Also, is there any way, using a WGET or other scriptable interface, to
manually tell Jenkins to provision one an EC2 slave for a given build label?
Thanks
-Eric S.
On Wed, Jun 6, 2012 at 12:24 PM, Francis Upton franc...@gmail.com wrote:
Hey Eric,
I think
Hey Eric,
I think there is an outstanding enhancement request (or maybe it's even
been implemented) to exploit the fact that you pay for the node by the hour
in EC2, so if the node it idle, it is killed shortly before it's hour has
expired. Of course this might want to be optional/configurable
Version 1.15 (May 22, 2012)
- Stopped (as opposed to terminated) slaves are counted against the
active instance count for the purpose of launching; can prevent launching
of instance (issue #7883http://issues.jenkins-ci.org/browse/JENKINS-7883
)
- Clarification and updating of help
I'm using the Jelly Forms to provide a combo box to add the availability
zone support to the EC2 plugin.
In the SlaveTemplate.DescriptorImpl class, I have the following code:
public ListBoxModel doFillZoneItems(@QueryParameter String accessId,
@QueryParameter String secretKey,
33 matches
Mail list logo
