I'm trying to use the Jenkins Amazon EC2 plugin to start and use AWS EC2
instances for slaves. Jenkins will start the slave, and the slave connects
to the master, but my builds are not able to connect to our Git
repositories over SSH. The slave is running on the Amazon Linux AMI.
I created a Gl
have to install.
The init script for the instance runs yum -y install git. Maybe it should
install something else.
On Saturday, November 2, 2013 2:22:19 PM UTC-5, David V wrote:
>
> I'm trying to use the Jenkins Amazon EC2 plugin to start and use AWS EC2
> instances for slaves
his value is? Or perhaps
> what dependencies it might have. Maybe the AMI is missing something that I
> have to install.
>
> The init script for the instance runs yum -y install git. Maybe it should
> install something else.
>
> On Saturday, November 2, 2013 2:22:19 PM UTC-5, David
We are setting up an EC2 cloud of Maven build slaves. Our projects have a
number of parent POMs in our Maven repository (not Maven Central). The
builds for projects fail during the Parsing POMs phase.
Parsing POMs
Failed to transfer Could not find artifact com.company:root-maven-pom:pom:7.2
in
Our Jenkins master server runs on an EC2 instance and we stop it twice a
day to switch between a small and medium instance to reduce our bills
during off hours. Our build slaves are EC2 instances using the Jenkins EC2
plugin. To keep the builds fast we have it configured to only stop the
slaves
I would like to stop them, not terminate them. Is there a proper way to
stop the instance from a Groovy script?
On Tuesday, January 21, 2014 11:51:00 AM UTC-6, Kevin Fleming wrote:
>
> Yes, a Groovy script could iterate over the current list of Jenkins nodes,
> determine which ones are EC2 slave
Presently, they have been idle when the shutdown occurs. I'm working on
updating the shutdown process to try to ensure that it waits until all jobs
are complete to enforce this.
On Tuesday, January 21, 2014 12:13:31 PM UTC-6, Kevin Fleming wrote:
>
> Are these slaves running active jobs, or are
Hey Kevin. Thanks for your help. The following script prints out the EC2
slaves and computers (it does not provide an actual description)
jenkins = Jenkins.instance;
for (slave in jenkins.slaves.findAll({s -> s instanceof
hudson.plugins.ec2.EC2OndemandSlave})) {
println slave
computer = sla
What do you think about exposing the stop() method? I found it in the
source on GitHub, but I've only just begun to take a look at the source
code for this project.
void stop() {
try {
AmazonEC2 ec2 = getCloud().connect();
StopInstancesRequest request = new StopIn
Hey Kevin. Thanks for your help. What I actually do now is terminate all my
EC2 slaves when we shut down. Now, if an uncontrolled shutdown occurs, we
might lose our slaves again.
For anybody you comes along with a similar problem, here is the script we
run:
import jenkins.model.*
jenkins = Jen
Hi Stephen. Thanks for responding with the suggestion. I would like to
incorporate it, but I'm not familiar with the Node Iterator API Plugin. I
see that you are the creator of the project. How do I use it?
>From looking at the source code, it looks like I would just change the loop
in my scrip
Is there a way to have Jenkins host a Maven site, much like the way that
the Javadoc plugin works? With the Javadoc plugin, I can view the latest
Javadoc of a job directly from its main page. I am interested in a similar
feature for Maven sites.
Thanks,
David
--
You received this message beca
am using a Maven job type. Here is my "goals and options" line:
clean deploy javadoc:javadoc site
Thanks.
David
On Saturday, February 23, 2013 9:13:49 AM UTC-6, Jesse Farinacci wrote:
>
> Greetings,
>
> On Sat, Feb 23, 2013 at 3:07 AM, Stephen Connolly
> > wrote:
&g
We configure our Maven installations in Jenkins using the system-wide
Jenkins installer. (Manage Jenkins -> Configuration -> Maven). This works
well when building Maven projects. We have two Maven installations which
are used on our slaves.
We need to script some Maven build steps in some Jenki
-maven (s3://company-maven):
Cannot access s3://company-maven with type default using the available
connector factories: WagonRepositoryConnectorFactory and 'parent.relativePath'
points at wrong local POM @ line 4, column 13
On Thursday, January 16, 2014 9:00:40 PM UTC-6, David V wrote
15 matches
Mail list logo
