RE: Unable to schedule paralell builds using build flow dsl (java.util.ArrayList in place of set of closures)

2015-10-26 Thread Rob Mandeville
I think your problem is no bigger than a typo.  It’s “parallel”, not 
“paralell”.  The double-L is at the middle, not the end.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jakub Gladykowski
Sent: Monday, October 26, 2015 10:23 AM
To: Jenkins Users
Subject: Unable to schedule paralell builds using build flow dsl 
(java.util.ArrayList in place of set of closures)


Hi all,

Coming from Python world, I'm trying to schedule paralell execution of builds 
using build flow plugin. However I fail everytime, using simplest 
implementation from internet:


build_number = '1234'
//Get all jobs from folder '1234'
jobs = 
jenkins.model.Jenkins.instance.getItemByFullName(build_number).getAllJobs()

def jobs_to_run = []

jobs.each {
  def closure = {
build('/' + build_number + '/' + it.getDisplayName())
  }
  jobs_to_run.add(closure)
}

paralell(jobs_to_run)


Everytime I get error:

No signature of method: com.cloudbees.plugins.flow.FlowDelegate.paralell() is 
applicable for argument types: (java.util.ArrayList) values:
[[Script1$_run_closure1_closure2@4545b0b4, ...]]
Possible solutions: parallel([Lgroovy.lang.Closure;), 
parallel(java.util.Collection), parallel(java.util.Map)


Output of println(jobs_to_run):

[Script1$_run_closure1_closure2@4545b0b4, 
Script1$_run_closure1_closure2@245a2f77, 
Script1$_run_closure1_closure2@72e83ff6]

Where do I make mistake?
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e6814091-2687-4afd-97cb-e1b9e4e70054%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
here
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36DAB918C10%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


RE: Initiate script/email BEFORE SCM polling

2015-09-29 Thread Rob Mandeville
An alternate way of handling this is to stop polling.  Or rather, poll 
explicitly.

Have a job which runs every n minutes/hours and does the following:

1: Pull the latest version
2: Check it against a version file in the workspace (never clean the workspace)
3: If the latest version is the same as what’s in the version file, you 
succeeded.
4: If the latest version is different, or if there is no version file:
  A: Use an API call or the Scriptler plugin or something to run a second job 
that does the actual build.  Don’t wait for it to finish.
  B: Put the new version into the version file
  C: You succeeded.


The job described above can send email on every poll, and the job it calls can 
send email on every build.

--Rob


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jeff
Sent: Tuesday, September 22, 2015 4:49 PM
To: Jenkins Users
Subject: Initiate script/email BEFORE SCM polling


I have someone in our development group, who insists on receiving an email, no 
matter whether there are SCM changes initiating a build, or not (polling at 
scheduled times throughout the day).  They want evidence that the process is 
running at the scheduled times, whether a build is occurring or not .

The Editable Email Notification plug-in triggers seems to all require that a 
build has occurred in some fashion.  It sounds like there's been discussion on 
adding options to tie in to the SCM polling itself, but no movement to date.

I tried a 'Prepare an environment for run' script, but again, it apparently 
isn't called unless there are SCM changes.

Does anyone know of a trick, to run a script prior to SCM polling?

Thanks.

--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5ad68688-3825-4060-ab18-868726f739fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
here
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36DAB2DD344%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


Bash and hard-bracket tests

2015-08-25 Thread Rob Mandeville
Take the following script:


if [ foo == foo ]; then
   echo foo is foo
fi

if [ foo == bar ]; then
  echo foo is bar
fi

When I run this from the Linux command line, I get:

foo is foo

When I add #!/bin/bash -ex as a shebang, I get the expected line dump plus 
the foo is foo line.


When I make this an execute shell build step, and run that step on a linux 
slave, I get:

[bash hard bracket test] $ /bin/sh -xe /tmp/hudson942109571990858458.sh
+ [ foo == foo ]
/tmp/hudson942109571990858458.sh: 2: [: foo: unexpected operator
+ [ foo == bar ]
/tmp/hudson942109571990858458.sh: 6: [: foo: unexpected operator

When I add a #!/bin/bash to the step as a shebang, I just get the expected 
foo is foo line.  And if I add a #!/bin/bash -ex shebang to the step, I get 
the same thing that I get when running the script with the shebang from the 
command line.

In any case, whenever I run this as a build, the SHELL environment variable is 
/bin/bash


Why does running a shell step without a shebang behave differently than it does 
with a #!/bin/bash -ex shebang?  Exactly what is being run without  a shebang?

Thanks in advance,

--Rob Mandeville
Deka Research and Development


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9CB15FFE%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


RE: Bash and hard-bracket tests

2015-08-25 Thread Rob Mandeville
I’m using Ubuntu, and have never heard of dash (though I just checked and 
verified that /bin/sh is a symlink to it).  Are you saying that, if no shebang 
is given, the build step ignores the SHELL variable and runs /bin/sh –ex?  This 
would explain much.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Dirk Heinrichs
Sent: Tuesday, August 25, 2015 9:59 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Bash and hard-bracket tests

Am 25.08.2015 um 15:51 schrieb Rob Mandeville:
Why does running a shell step without a shebang behave differently than it does 
with a “#!/bin/bash –ex” shebang?  Exactly what is being run without  a shebang?

What sh is, depends on your OS. It may be bash, or something else.

CentOS:
# ll =sh
lrwxrwxrwx. 1 root root 4 Nov 18  2014 /bin/sh - bash

Ubuntu:
# ll =sh
lrwxrwxrwx 1 root root 4 Dec  2  2014 /bin/sh - dash

HTH...

Dirk
--
[cid:image001.gif@01D0DF1E.676E7710]
Dirk Heinrichs, Senior Systems Engineer, Engineering Solutions
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Tel: +49 2226 159 (Ansage) 1149
Email: d...@recommind.commailto:d...@recommind.com
Skype: dirk.heinrichs.recommind
www.recommind.comhttp://www.recommind.com


Click 
herehttps://www.mailcontrol.com/sr/biBNBiBbVJ!GX2PQPOmvUgfUspOYWKRbyY1g7HGtKqWXpGK2UrSzxZEh7iGY4duAOhgx6W5ulfPX405xsHCs!A==
 to report this email as spam.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/55DC7498.70609%40recommind.comhttps://groups.google.com/d/msgid/jenkinsci-users/55DC7498.70609%40recommind.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9CB16096%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


Better Logging for Jenkins Shutdown

2015-05-27 Thread Rob Mandeville
My Jenkins server went down last night, and the log showed no signs of trouble. 
 I am running:

Jenkins 1.565.1.LTS on
its own Winstone server on
Java HotSpot 64 bit 1.8.0_25-b17 on
Ubuntu 13.03 Saucy Salamander (yes, I know it's out of date) on a vSphere VM.

The log entries ended at 5:20 yesterday afternoon and started again when I ran 
'service jenkins start' at 8:20 this morning.  The relevant log segment is 
listed below the fold.

I see no 'JVM is terminating.  Shutting down winstone' message, so it doesn't 
look like a user did an orderly shutdown.

This instance is a memory hog; it takes about 15 minutes to bring up and has 
over 1,000 projects.  It is possible that the JVM ran out of memory or 
something, but I can't tell.

The worst case scenario (though very unlikely) is that someone ran 'kill -9' 
against the server.  In that case, there can't be a log entry.  But barring 
that, how can I increase the logging for typical shutdown conditions so that I 
have a better chance to know what happened next time?

--Rob



INFO: Branch development Project HSM DAL Manager Quick Static Code Analysis 
#129 main build action completed: SUCCESS
May 26, 2015 5:20:10 PM hudson.plugins.logparser.LogParserParser parseLogBody
INFO: LogParserParser: Start parsing : Branch development Project HSM DAL 
Manager Quick Static Code Analysis_build_129
May 26, 2015 5:20:13 PM hudson.plugins.logparser.LogParserParser parseLogBody
INFO: LogParserParser: Parsing took 0 minutes (3) seconds.
May 26, 2015 5:20:17 PM hudson.model.Run execute
INFO: Branch development Run SoapUI Smoke Tests #213 main build action 
completed: SUCCESS
May 26, 2015 5:20:18 PM hudson.model.Run execute
INFO: Branch development Smoke Tests #230 main build action completed: UNSTABLE
Running from: /usr/share/jenkins/jenkins.war.1.565.1.LTS
May 27, 2015 8:22:14 AM winstone.Logger logInternal
INFO: Beginning extraction from war file
May 27, 2015 8:22:14 AM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-8.y.z-SNAPSHOT
May 27, 2015 8:22:18 AM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: NO JSP Support for , did not find org.apache.jasper.servlet.JspServlet
Jenkins home directory: /var/lib/jenkins found at: 
EnvVars.masterEnvVars.get(JENKINS_HOME)
May 27, 2015 8:22:19 AM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started SelectChannelConnector@0.0.0.0:8080
May 27, 2015 8:22:19 AM winstone.Logger logInternal
INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled
May 27, 2015 8:22:21 AM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
May 27, 2015 8:22:23 AM hudson.ClassicPluginStrategy createPluginWrapper
INFO: Plugin subversion.jpi is disabled
May 27, 2015 8:22:24 AM hudson.ClassicPluginStrategy createPluginWrapper
INFO: Plugin cvs.jpi is disabled
May 27, 2015 8:22:25 AM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins




This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9BCC181A%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


RE: Better Logging for Jenkins Shutdown

2015-05-27 Thread Rob Mandeville
Thanks!  It got hit by the OOM killer.  I should have thought of that first.

--Rob

-Original Message-
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel Beck
Sent: Wednesday, May 27, 2015 12:40 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Better Logging for Jenkins Shutdown

Check the system logs. Too large of an Xmx may have Linux kill off your process 
(oom-killer).

On 27.05.2015, at 15:09, Rob Mandeville rmandevi...@dekaresearch.com wrote:

 My Jenkins server went down last night, and the log showed no signs of 
 trouble.  I am running:

 Jenkins 1.565.1.LTS on
 its own Winstone server on
 Java HotSpot 64 bit 1.8.0_25-b17 on
 Ubuntu 13.03 Saucy Salamander (yes, I know it’s out of date) on a vSphere VM.

 The log entries ended at 5:20 yesterday afternoon and started again when I 
 ran ‘service jenkins start’ at 8:20 this morning.  The relevant log segment 
 is listed below the fold.

 I see no ‘JVM is terminating.  Shutting down winstone’ message, so it doesn’t 
 look like a user did an orderly shutdown.

 This instance is a memory hog; it takes about 15 minutes to bring up and has 
 over 1,000 projects.  It is possible that the JVM ran out of memory or 
 something, but I can’t tell.

 The worst case scenario (though very unlikely) is that someone ran ‘kill -9’ 
 against the server.  In that case, there can’t be a log entry.  But barring 
 that, how can I increase the logging for typical shutdown conditions so that 
 I have a better chance to know what happened next time?

 --Rob



 INFO: Branch development Project HSM DAL Manager Quick Static Code
 Analysis #129 main build action completed: SUCCESS May 26, 2015
 5:20:10 PM hudson.plugins.logparser.LogParserParser parseLogBody
 INFO: LogParserParser: Start parsing : Branch development Project HSM
 DAL Manager Quick Static Code Analysis_build_129 May 26, 2015 5:20:13
 PM hudson.plugins.logparser.LogParserParser parseLogBody
 INFO: LogParserParser: Parsing took 0 minutes (3) seconds.
 May 26, 2015 5:20:17 PM hudson.model.Run execute
 INFO: Branch development Run SoapUI Smoke Tests #213 main build action
 completed: SUCCESS May 26, 2015 5:20:18 PM hudson.model.Run execute
 INFO: Branch development Smoke Tests #230 main build action completed:
 UNSTABLE Running from: /usr/share/jenkins/jenkins.war.1.565.1.LTS
 May 27, 2015 8:22:14 AM winstone.Logger logInternal
 INFO: Beginning extraction from war file May 27, 2015 8:22:14 AM
 org.eclipse.jetty.util.log.JavaUtilLog info
 INFO: jetty-8.y.z-SNAPSHOT
 May 27, 2015 8:22:18 AM org.eclipse.jetty.util.log.JavaUtilLog info
 INFO: NO JSP Support for , did not find
 org.apache.jasper.servlet.JspServlet
 Jenkins home directory: /var/lib/jenkins found at:
 EnvVars.masterEnvVars.get(JENKINS_HOME)
 May 27, 2015 8:22:19 AM org.eclipse.jetty.util.log.JavaUtilLog info
 INFO: Started SelectChannelConnector@0.0.0.0:8080
 May 27, 2015 8:22:19 AM winstone.Logger logInternal
 INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled May
 27, 2015 8:22:21 AM jenkins.InitReactorRunner$1 onAttained
 INFO: Started initialization
 May 27, 2015 8:22:23 AM hudson.ClassicPluginStrategy
 createPluginWrapper
 INFO: Plugin subversion.jpi is disabled May 27, 2015 8:22:24 AM
 hudson.ClassicPluginStrategy createPluginWrapper
 INFO: Plugin cvs.jpi is disabled
 May 27, 2015 8:22:25 AM jenkins.InitReactorRunner$1 onAttained
 INFO: Listed all plugins



 This e-mail and the information, including any attachments it contains, are 
 intended to be a confidential communication only to the person or entity to 
 whom it is addressed and may contain information that is privileged. If the 
 reader of this message is not the intended recipient, you are hereby notified 
 that any dissemination, distribution or copying of this communication is 
 strictly prohibited. If you have received this communication in error, please 
 immediately notify the sender and destroy the original message.

 Thank you.

 Please consider the environment before printing this email.

 --
 You received this message because you are subscribed to the Google Groups 
 Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to jenkinsci-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9BCC181A%40dekaexchange07.deka.local.
 For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20B968A5-8400-40A7-8E24-2B82B47C4D41%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


 Click 
https://www.mailcontrol.com/sr

RE: old war file deploying

2015-02-12 Thread Rob Mandeville
Nope, nobody here can help you.  We’ve got nothing to go on :*)

What sort of a job are you running?  May we see some logs?  How does it choose 
which WAR file to deploy, and even where are they coming from?  Why are you 
expecting a newer WAR file than Jenkins is giving you?

With some more information, we may be able to help.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nagashree ck
Sent: Thursday, February 12, 2015 5:08 AM
To: jenkinsci-users@googlegroups.com
Subject: old war file deploying

Hi Friends,


old war files getting deploying through jenkins.

can anybody help me.

Thanks in Advance


--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAKO07kr9WLqR-7CEKx8xWBxoJ%3DksUduvNyY0NDF6oGcsqwhFjg%40mail.gmail.comhttps://groups.google.com/d/msgid/jenkinsci-users/CAKO07kr9WLqR-7CEKx8xWBxoJ%3DksUduvNyY0NDF6oGcsqwhFjg%40mail.gmail.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/KuGmbpSuEfTGX2PQPOmvUkyXKmclf+CPT+aOHUU1mWO9SV11Q8cZIzkhA8USUoRapfmunE2R0s4Ds2jC!2iYuQ==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9AEF6397%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


RE: Slave Node associate to IP or User

2015-02-09 Thread Rob Mandeville
I’m not sure what you mean.  Are you saying that you want user ‘fred’ to be 
confined to the Jenkins slave on his own personal system?  That wouldn’t be a 
Jenkins farm.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of uzqates...@gmail.com
Sent: Monday, February 09, 2015 12:11 PM
To: jenkinsci-users@googlegroups.com
Subject: Slave Node associate to IP or User

Hi!

I am creating a Jenkins Farm, i was looking the way to link an Slave Node to a 
User Credential or IP. What i need is that every developer execute the jobs in 
they virtual machine.

How can I do this?

Regards
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1a799406-6486-4e93-9bd5-2a64c971593b%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/1a799406-6486-4e93-9bd5-2a64c971593b%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/76rP5IdX1O3GX2PQPOmvUgfUspOYWKRbrz1v0O!BQKcZBijctWZWsdyekGabpg5qZGQNskQ9zi!3vm7b4Ic+!w==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9AE60BC5%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


Git Credentials on Workflow Plugin

2015-01-27 Thread Rob Mandeville
I am using:

* Jenkins 1.580.2

* GIT client plugin 1.15.0

* GIT plugin 2.3.4

* Workflow plugins 1.1

* Credentials plugin 1.22

We use GitLab for source control and do not allow anonymous access of any kind. 
 We use the Credentials plugin, have put in credentials allowing us access to 
Git, and on our normal projects, we simply give Git these pre-loaded 
credentials.  Now, I'm trying to create a Workflow job.

I can't find any doc which says how to feed credentials to Git, so I went to 
the credentials plugin and pulled the plugin ID from the URL.  I then wrote the 
following Groovy CPS DSL script (without the redactions, obviously):


steps.stage('Setup')
node('mock_builder') {
   String templateUrl = 'git@URL_REDACTED'
   steps.git(url: templateUrl, credentialsId: 'ID_REDACTED')
   sh 'echo hello world'
}

The job gets stuck in the SCM step and exits with the following output:


Running: Setup

Entering stage Setup

Proceeding

Running: Allocate node : Start

Running on mock_builder in 
C:\Windows\TEMP\hudson1572436821107746068tmp\workspace\Try a Workflow

Running: Allocate node : Body : Start

Running: Git

  git.exe rev-parse --is-inside-work-tree # timeout=10

Fetching changes from the remote Git repository

  git.exe config remote.origin.url git@URL_REDACTED # timeout=10

Fetching upstream changes from git@URL_REDACTED

  git.exe --version # timeout=10

  git.exe -c core.askpass=true fetch --tags --progress git@URL_REDACTED 
  +refs/heads/*:refs/remotes/origin/*

ERROR: Timeout after 10 minutes

ERRORhttp://stacktrace.jenkins-ci.org/search?query=ERROR: Error fetching 
remote repo 'origin'

Runninghttp://stacktrace.jenkins-ci.org/search?query=Running: Allocate node : 
Body : End

Running: Allocate node : End

Running: End of Workflow

ERROR: Error fetching remote repo 'origin'

Finishedhttp://stacktrace.jenkins-ci.org/search?query=Finished: FAILURE

I'm wondering where the -c core.askpass=true came from, and figuring that it 
was waiting to receive a password via standard input.
Is there any way, with or without the credentials plugin, to feed Git 
credentials to this project?

Thanks in advance,

--Rob


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9ACEDA91%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


RE: Schedule large numbers of building jobs - perfromance issue

2015-01-20 Thread Rob Mandeville
Are you talking about 200-1000 jobs configured, or running simultaneously?

Clients feed log data and artifacts to the Jenkins server in real time.  If 
you’re running hundreds of these simultaneously, you are using tons of threads, 
tons of RAM for buffers, and tons of disk revolutions.  At this point, you can 
start thinking of your Jenkins server as a database server and determine your 
hardware requirements accordingly.  It’s fairly easy to become I/O bound, and 
you might become network bound if you’re using older, slower networking.

Also, how is your polling?  If you have hundreds of jobs polling, think of 
those as hundreds of “mini-jobs” querying source control on a regular basis.  
They don’t show up in the regular build logs, but they have similar resource 
needs.  If there’s a way to avoid polling (we use GitLab and have a plugin 
which lets GitLab push updates to Jenkins rather than have Jenkins poll), 
consider it.

The guys at Cloudbees would be willing to sell you a way to do this using 
multiple Jenkins servers and have them all centrally managed; you may want to 
talk to them if this is that big of a project.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Tomasz Majchrowski
Sent: Friday, January 16, 2015 12:47 PM
To: jenkinsci-users@googlegroups.com
Subject: Schedule large numbers of building jobs - perfromance issue

Dear All
The way in which Jenkins manages tasks and machines is very powerful. We are 
thinking about moving our python written system to distribute builds across 
server farm in to the Jenkins.

The challenge that I recognize will be a number of parallel tasks that needs to 
be handle by Jenkins. Basically I create project which based on dependency 
triggers the downstream project with using of groovy system scripts and 
schedule2(Task, int, 
List)http://javadoc.jenkins-ci.org/hudson/model/Queue.html#schedule2%28hudson.model.Queue.Task,%20int,%20java.util.List%29.
 Since the number of downstream builds of the same project (with different 
parameter) may achieve range (200-1000) I recognize performance issue.

It's really hard to say if the bottle neck is coming from:
* the bad design of one of the plugin installed in the chain or
* basically the Jenkins is not the right tool for such a scale of parallel task 
due to its' overhead.

I debug a bit with visualvm to found a bottle neck, however couldn't found any 
interesting. Anyone is having experience with such a large build queue. Could 
you share hints/best practice?

Best regards, Tomasz Majchrowski.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/bb6d5973-f2e1-4326-843e-5a20af42443a%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/bb6d5973-f2e1-4326-843e-5a20af42443a%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/xS3HpdCMjQDGX2PQPOmvUqy!8K4P2+304Ad+ogp4iPfiWOMVFa61EOZGNMmAiCb41plses+MFQyTKOxjbsImtQ==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9ABFEF7E%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


RE: Upcoming Mastering continuous integration with Jenkins - 28-29th January

2015-01-20 Thread Rob Mandeville
On the one hand, this is the sort of commercial-ish message we want to see on 
these boards, as opposed to the storm of recruiting spam we’ve been weathering 
lately.

On the other hand, the page doesn’t load; it complains that it can’t connect to 
MySQL.  Marián, you may want to have someone look into that if you want people 
to attend.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Marián Knotek
Sent: Tuesday, January 20, 2015 2:23 PM
To: jenkinsci-users@googlegroups.com
Subject: Upcoming Mastering continuous integration with Jenkins - 28-29th 
January

http://www.forest-technologies.co.uk/events/mastering-continuous-integration-with-jenkins-jan
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/125ef8d8-fd33-4952-b274-cc1c7ecf5a5d%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/125ef8d8-fd33-4952-b274-cc1c7ecf5a5d%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/!OvXUrrwVUDGX2PQPOmvUkyXKmclf+CPdO05Q!bYyXRpZ8zGTVnDiJI1n6MP5Kj21plses+MFQwzGm2rSK1dVQ==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9AC37123%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


RE: Variable from shell script to Jenkins job

2015-01-16 Thread Rob Mandeville
In the technique below, the echo lines are run on the remote (slave node).  The 
“Inject environment variables” step works on the slave node and reads any files 
it needs from there, not the server.  Also, this technique was built to allow 
one shell step to calculate the values of environment variables and inject them 
into later steps.  Given your specific case, you don’t have to get this 
involved.

The environment variables in your case below don’t appear to depend on anything 
the job does.  These variables look like properties of the machine you’re 
running on.  While the envInject technique would still work, you could set the 
environment variables either at the build environment section of the job or in 
the node configuration.  In either case, you’ll have to specify ACE as 
“/opt/play/apps/default-ace/ACE”; “$APPS/default-ace/ACE” only makes sense 
within a shell.

There’s a good argument to be had for inserting these variables in the slave 
node itself, as they describe information specific to that host rather than 
specific to any job.  If you do set the environment variable at the slave 
level, make sure to reboot the slave by selecting Disconnect on it (slaves 
should restart themselves)—until the slave process reboots, it will have the 
old values for environment variables.

--Rob (Same Rob, different job)



From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Adrian Paraschiv
Sent: Friday, January 16, 2015 6:43 AM
To: jenkinsci-users@googlegroups.com
Cc: rmandevi...@litle.com
Subject: Re: Variable from shell script to Jenkins job

Hello Rob,

I have a couple of questions:
1. The line echo “varID = $varID”  export_props.properties is run on the 
jenkins server or on the remote ?
2. If I need something like this on the remote server for a script that jenkins 
runs:
..
export APPS=/opt/play/apps
export ACE=$APPS/default-ace/ACE
..

What would be the best method to use:
1. Add build step (before Execute shell ) Inject enviromnet variables  and at 
the Properties Content I add the above...or
2. At Build Environment check Inject environment variables to the build 
process and add the above at Properties Content

Thanks

On Thursday, January 23, 2014 at 5:55:55 PM UTC+2, Mandeville, Rob wrote:
We’ve got a technique for this at our shop.  It requires the envInject plugin.

You write a line such as:

echo “varID = $varID”  export_props.properties

In the step after the shell step, create an “Inject environment variables” step 
that reads from export_props.properties.

Now, the contents of export_props.properties is injected into the job itself, 
and will be injected into shell steps as environment variables.

--Rob

From: jenkins...@googlegroups.comjavascript: 
[mailto:jenkins...@googlegroups.comjavascript:] On Behalf Of Naumenko, Roman
Sent: Thursday, January 23, 2014 10:50 AM
To: jenkins...@googlegroups.comjavascript:
Subject: Variable from shell script to Jenkins job

Jenkins experts,

Does anybody remember how to pass variable from shell execution inside the job 
to Jenkins itself?

Say there is pre-step:
varID=(grep something ${WORKSPACE}/pom.xml | cut something else)

Is it possible to use $varID in further non-shell steps in the job?

--Roman

___

This email is intended only for the use of the individual(s) to whom it is 
addressed and may be privileged and confidential.
Unauthorised use or disclosure is prohibited. If you receive This e-mail in 
error, please advise immediately and delete the original message.
This message may have been altered without your or our knowledge and the sender 
does not accept any liability for any errors or omissions in the message.

Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits 
et obligations qui s'y rapportent.
Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il 
contient par une personne autre que le (les) destinataire(s) désigné(s) est 
interdite.
Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par 
retour de courriel ou par un autre moyen.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-use...@googlegroups.comjavascript:.
For more options, visit https://groups.google.com/groups/opt_out.
The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle  Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle  Co. immediately 

RE: Jenkins - Baby steps

2015-01-16 Thread Rob Mandeville
The beauty of Jenkins is that a single installation can run on multiple hosts.  
That’s what slave nodes are for.  Rather than cross-compiling, just put 
together a Linux machine with GCC, and build your Linux binaries there.  Here’s 
what you do.

First off, I’m assuming that you have a job like “Build windows binary”.  
Configure that job, and check the “Restrict where this project can be run” box 
so that it runs on “master”.  This forces it to run on the Jenkins server 
itself; since your Jenkins server runs in Windows, this forces this job to run 
on a Windows machine.

In your Linux compiler box, create an account for Jenkins (maybe name it 
‘jenkins’).  In its home directory, make a directory called “linux1”.

Go to Jenkins-Manage Jenkins-Manage Nodes-New Node.  Create a new “dumb 
slave” node called “linux1”.


Set up “linux1” to use the launch method of “Launch slave agents on Unix 
machines via SSH”.  Give it the credentials to log in to your Linux compiler 
box.  as a non-root user with access to the compiler.  Set the Remote FS to the 
directory you set up (likely /home/jenkins/linux1).  Give it a label of 
“linux”.  After configuring it, make sure that it launches.

If you go to the main Jenkins page, you will now see “linux1” on the left, 
under the build queue.

Create a new job, called “Build Linux binary”, as a copy of the “Build windows 
binary” job.  Change the “Restrict where this project can be run” to run on 
label “linux”.  Replace all “Execute Windows batch command” steps with the 
appropriate “Execute shell” steps—while all new steps are created at the end of 
the list, you can drag steps into place by dragging the little 4x4 grid at the 
top left of a given step.  Make whatever other changes are necessary to make 
this job appropriate to your Linux machine.

With all this set up, your new job will run on the Linux host you set up, and 
you can still see everything from the Jenkins server.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kumara Raja S
Sent: Friday, January 16, 2015 5:26 AM
To: jenkinsci-users@googlegroups.com
Cc: david.aldr...@emea.nec.com
Subject: Re: Jenkins - Baby steps

Hi David,

Sorry for the delayed reply.

Here is my further analysis.

I want to integrate a simple c project. This project will be built using gcc. 
As you mentioned targetting Linux platform.

But the Jenkins will be running in windows machine, reason is that, Jenkins 
need to build the windows based application as well.

Further to this, I understood that, I need to have gcc compiler in windows 
machine to build the application.

So, I have installed MinGW. But, still am not able to link the project 
successfully.

On Wednesday, January 14, 2015 at 7:20:01 PM UTC+5:30, David Aldrich wrote:
Which environment are you targeting?  (I guess you are targeting Linux with the 
gcc compiler).
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/39ed8162-8990-42a5-8ef5-3fefa5f412ed%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/39ed8162-8990-42a5-8ef5-3fefa5f412ed%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/JwETsHLN6G3GX2PQPOmvUqy!8K4P2+30iYib4kdjg12Ivnq81oddVp5ysW9bRhUYmC+Xt1!OxeesCq9I+zBdpQ==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9ABBB0B7%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


RE: Very urgent:: data modeler

2015-01-12 Thread Rob Mandeville
If enough people hit the ‘report message as spam’ button at the bottom, will 
Googlegroups ban this bozo?

--Rob


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of hitesh sharma
Sent: Monday, January 12, 2015 4:22 PM
To: xrec...@googlegroups.com; recruiters_gu...@googlegroups.com; 
microsoft-sharepoint-development--us...@googlegroups.com; 
usaafricadialo...@googlegroups.com; 
direct-clientprime-vendor-requireme...@googlegroups.com; 
quick-respo...@googlegroups.com; asp-...@googlegroups.com; 
gta...@googlegroups.com; true-value-care...@googlegroups.com; 
recruiting-simplif...@googlegroups.com; 
narendras-it-recruitment-for-...@googlegroups.com; 
it_jobs_...@googlegroups.com; technical-recruiter-us-staff...@googlegroups.com; 
help4jobhunt...@googlegroups.com; itjobs-...@googlegroups.com; 
abap_sapgooglegroups...@googlegroups.com; us_jobsnconsulta...@googlegroups.com; 
us-it-staffing-and-consult...@googlegroups.com; 
oracle-develo...@googlegroups.com; itusaj...@googlegroups.com; 
corp2corp-...@googlegroups.com; financearti...@googlegroups.com; 
java-developer-usa-gr...@googlegroups.com; koda...@googlegroups.com; 
technical-recruit...@googlegroups.com; recruitersandresu...@googlegroups.com; 
qa-test...@googlegroups.com; technicalrecruiterscoun...@googlegroups.com; 
usa-hotlist-r...@googlegroups.com; 
helpful-network-us-it-recruit...@googlegroups.com; 
recruitingprow...@googlegroups.com; usaconsulta...@googlegroups.com; 
corp-to-corp-jo...@googlegroups.com; best-it-consulting-gr...@googlegroups.com; 
jp...@googlegroups.com; lookh...@googlegroups.com; 
us-it-consult...@googlegroups.com; vamsyst...@googlegroups.com; 
c2c-...@googlegroups.com; oracle...@googlegroups.com; 
recruits-...@googlegroups.com; sap-...@googlegroups.com; m...@googlegroups.com; 
ora...@googlegroups.com; 
hotlists_resume_consultants-4-recruit...@googlegroups.com; 
usa-c2c-j...@googlegroups.com; lucidj...@googlegroups.com; 
sap-care...@googlegroups.com; fisica_teor...@googlegroups.com; 
w2-j...@googlegroups.com; opt-...@googlegroups.com; 
losangelesj...@googlegroups.com; assen...@googlegroups.com; 
nebraska-j...@googlegroups.com; bostont...@googlegroups.com; 
us-it-recruiter-posti...@googlegroups.com; h1b...@googlegroups.com; 
bestmi...@googlegroups.com; monikakjadhav...@googlegroups.com; 
shilpa...@googlegroups.com; recruiterski...@googlegroups.com; 
oracle-financials-jobsgooglegroups...@googlegroups.com; 
us-it-j...@googlegroups.com; jobs-in-itgooglegroups...@googlegroups.com; 
dice...@googlegroups.com; rajesh_us_it_recrui...@googlegroups.com; 
us-...@googlegroups.com; it_technical_recruit...@googlegroups.com; 
abapc...@googlegroups.com; immediate...@googlegroups.com; 
chrisbr...@googlegroups.com; 1-usa-j...@googlegroups.com; 
davids-...@googlegroups.com; jobgr...@googlegroups.com; 
contract-job-ale...@googlegroups.com; chetna-jobs-recruite...@googlegroups.com; 
corptocorpcandida...@googlegroups.com; uscitizenfullt...@googlegroups.com; 
jobsbank...@googlegroups.com; c2c-j...@googlegroups.com; 
req-...@googlegroups.com; itresu...@googlegroups.com; 
immediate-hotl...@googlegroups.com; dice-j...@googlegroups.com; 
sapa...@googlegroups.com; novian-job-ale...@googlegroups.com; 
recruiter2...@googlegroups.com; jenkinsci-users@googlegroups.com; 
java-j...@googlegroups.com; mainfr...@googlegroups.com; 
us-recruitment-servi...@googlegroups.com; hot-resu...@googlegroups.com; 
venkat-ag...@googlegroups.com; hire-a-program...@googlegroups.com; 
corptoc...@googlegroups.com; only-direct-client-requireme...@googlegroups.com; 
immediate-interviews-direct-client-requireme...@googlegroups.com; 
c2c-requireme...@googlegroups.com; shekar_j...@googlegroups.com; 
javacare...@googlegroups.com; weech...@googlegroups.com; 
indians-who-love-mov...@googlegroups.com; 
websphere-admin-nee...@googlegroups.com; abdul_it_staff...@googlegroups.com; 
usaerpsu...@googlegroups.com; hotlist-vasa...@googlegroups.com; 
us-staffing-a...@googlegroups.com; sap-requireme...@googlegroups.com; 
ahmed_recrui...@googlegroups.com; business-anal...@googlegroups.com; 
directclien...@googlegroups.com; ccie-vo...@googlegroups.com; 
itconsulta...@googlegroups.com; blog...@googlegroups.com; 
firewa...@googlegroups.com; a...@googlegroups.com; 
optcandida...@googlegroups.com; delphi-j...@googlegroups.com; 
us-hotl...@googlegroups.com; dba-supp...@googlegroups.com; 
start-dot...@googlegroups.com; 
jobs-for-indians-abroad-wwwindianreunited...@googlegroups.com; 
oracle-train...@googlegroups.com; s...@googlegroups.com; 
fresherstr...@googlegroups.com; made-in-...@googlegroups.com; 
sacramento-jobs-resu...@googlegroups.com; 96_j...@googlegroups.com; 
usa-open-r...@googlegroups.com; h1b_j...@googlegroups.com; 
sureshotj...@googlegroups.com; websphere-por...@googlegroups.com; 
microsoft-sharepoint-servi...@googlegroups.com; noi-j...@googlegroups.com; 
sapbwathomekoreapub...@googlegroups.com; womencar...@googlegroups.com; 
it-datab...@googlegroups.com; 

RE: Git based builds; one commit at a time

2014-12-31 Thread Rob Mandeville
It can be (mostly) done, but you are intentionally defeating a Jenkins feature 
and you need to take that into account.

When a job is monitoring a Git repository, there are two problems.  First off, 
by default it polls.  If two commits get in within the same poll interval, 
you’re getting both.  Secondly, you can only have one job in the queue with a 
given name and a given set of parameters.  Duplicate jobs in the queue get 
silently discarded.  This is a feature, not a bug, so that five commits don’t 
cause five builds.  It sounds like you explicitly don’t want this behavior.

To do what you want, build two jobs, a “poller” and a runner.  The “polling” 
job starts by polling Git (it’s in quotes for reasons below).  Its only purpose 
is to launch the runner job with the ${GIT_REVISION} as its only argument.

The runner doesn’t poll at all, it just pulls from the Git repository, 
explicitly getting the version passed in by the poller.  By making the revision 
an argument, this allows five commits to trigger five different jobs, and 
allows all five jobs to remain in the queue (as they have different arguments).

The above still has the problem of handling multiple commits in one polling 
interval.  In theory, you could poll once a minute, but that’s expensive and 
still not going to get you what you want.  There is no way to poll quickly 
enough to insure one job per commit.  You’re going to have to do something 
other than polling.

In my shop, we use a local GitLab installation for our source control.  We 
installed the Gitlab Hook 
Pluginhttps://wiki.jenkins-ci.org/display/JENKINS/Gitlab+Hook+Plugin, and set 
our jobs to only poll once a day.  The plugin allows GitLab to use a Web hook, 
so that whenever it receives a commit, it tells Jenkins “Poll on this 
repository NOW”.  Jenkins will then launch a poll on every job which is polling 
that Git repository.  Polling once a day satisfies that requirement, and our 
jobs launch within seconds of getting a commit.

It may still be possible to get multiple commits to come in fast enough so that 
the forced poll catches multiple commits.  If someone merges in a branch with 
five commits on it, I suspect that all five commits are considered 
simultaneous, and you will only poll once and build once.

If you absolutely, positively need one job per commit, including the case above 
(or cases where multiple people commit faster than Jenkins can even run its 
poll), now you’re going to have to get tricky.  Now you need to work in the 
poller job.  It will have to behave like so:

1.   Determine what the last commit built was.  Maybe it can use Jenkins 
internals, or get the parameters from the last build of the runner via HTTP to 
the job’s /api/xml page.

2.   Get the history of the repository or branch

3.   Find all the commits done after the last commit built

4.   In order, launch the runner for each of those commits.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Steve K
Sent: Tuesday, December 30, 2014 3:21 PM
To: jenkinsci-users@googlegroups.com
Subject: Git based builds; one commit at a time

Let's say that, since my most recent build, there have been three (3) new 
commits.
Rather than having one build that includes all three commits, I would like to 
have three separate builds; one for each of the three in sequence.

Is anyone doing something like that?  If so, how are you doing it?

Thanks in advance.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/60bb2099-c4c1-4630-874c-339fc27c82b0%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/60bb2099-c4c1-4630-874c-339fc27c82b0%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/kDHW7Nj!uqrGX2PQPOmvUvmldA89nuwl+4q7Z7PYepNtJmQIFgNOaagMtbaIYtrvfRb1JLBUB+kJwVIOzJj0SQ==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 

RE: Run number of parameterized jobs based on property files

2014-12-15 Thread Rob Mandeville
Look at the  Job DSL Plugin.

If all these jobs can be started at the same time (even if they have to queue 
up for lack of executors), I would have a job connected to that git repository 
and set on a schedule.  The job would read all the files into some data 
structure, then use Build Flow or Job DSL to loop through all the files and 
kick off a job for each one.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Maneesh M P
Sent: Friday, December 12, 2014 11:16 PM
To: jenkinsci-users@googlegroups.com
Subject: Run number of parameterized jobs based on property files

Hello,

   I have git repository which contains just property files, around 30, I would 
like to kick start same parametrized jobs for 30 times passing each of these 
different  property files.
  Is there an easy way other than adding the triggers manually ?

Thanks,
Manesh
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5ba8c3e7-fb23-4904-82b4-ae9582afae66%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/5ba8c3e7-fb23-4904-82b4-ae9582afae66%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/q8t9fMK9OcDGX2PQPOmvUml+xXZX6IbqWOwaK22Xgz7YEdRMUQX3BcU3c6hO7kE6Z1av+d2vtxbOTml8Ao4xWg==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9A843D95%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


Build Pipeline Plugin, Ball Color, and Unused Steps

2014-12-12 Thread Rob Mandeville
I auto-generate a bunch of build jobs and build pipeline views with the Job 
Generator plugin and the Job DSL plugin.   My jobs use the Conditional Build 
Step plugin and can launch sub-jobs depending on runtime conditions.  For 
instance, if we find a smoke test defined in the source at runtime, we deploy 
the system to a testbed and run the smoke tests against it.  If there are no 
smoke tests defined, we neither deploy the code nor run the tests.  Deploying 
the code and running smoke tests are each a Jenkins job in their own rights.

Thus, when I run a pipeline where there are no smoke tests, those two tasks are 
un-run, and the pipeline view shows them as blue (not successful-blue, just 
blue-at my site, success is green).  In the nested view holding the pipeline 
views, however, the ball for that pipeline shows red, presumably because not 
all the jobs succeeded (as not all of them ran).

Is there a good way to show my users the true outcome of these pipelines?  I 
specifically define the true outcome as the result of the first job in the 
pipeline, as it collects all test artifacts and results from all the downstream 
jobs.

Thanks in advance,

--Rob


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9A807CE7%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


RE: What steps should I take to diagnose why output does not appear in Jenkins's Console Output immediately?

2014-12-03 Thread Rob Mandeville
I’m guessing that, if you run your command from the command line, you get your 
output more quickly than you do when you run it in Jenkins.

One possibility is that the program writing the log can tell whether it’s 
writing to a TTY or not, and changes its behavior accordingly.  Often, this 
means that it flushes its output cache every line for TTY output, and every 
(say) 1024 bytes for non-TTY output.

If you’re using Unix, try running this (replacing foo with your command):

foo  file.out ; tail –f file.out

This makes the foo command write to a file rather than a TTY, and lets you see 
what gets written to that file in real time.

If this is indeed the problem, I don’t have a solution right off, except to 
google for “Jenkins slave tty” and go from there.

Hope this helps!

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Behrang Saeedzadeh
Sent: Tuesday, December 02, 2014 9:14 PM
To: jenkinsci-users@googlegroups.com
Subject: What steps should I take to diagnose why output does not appear in 
Jenkins's Console Output immediately?

Hi,

We have some Jenkins jobs that at some point during their executions output 
they produce during execution of their scripts, etc. does not appear in the 
Jenkins Console Output immediately.

What are some things that can cause this behavior and how do you suggest I 
should start diagnosing this?
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fb455d67-b0e6-4f4b-b491-3962851905cf%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/fb455d67-b0e6-4f4b-b491-3962851905cf%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/3hMzoHQh6h!GX2PQPOmvUtVTDJsKpCsg8hqP+rIAYoUqiRB+oN7Q1FoT4ILRgIFHY3TQOiZ2K0IgL4AI7al!HQ==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9A6B85A6%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


Auto-generating a complex view setup

2014-11-25 Thread Rob Mandeville
I have a matrix of n projects building on m branches, and I am putting together 
pipelines for each one.  That is, there are a set of jobs of the form 
regression tests for branch FOO of project BAR.  I have a JSON file showing 
the list of branches, projects, and their configurations.  With that, I've 
developed an intricate system to regenerate all the jobs with no problem.  Now, 
I just need to generate several dozen views.

The hierarchy which I have been building by hand is:


· (Nested View) Branch Builds

o   (Monitor View) All Builds for Branch FOO

o   (Monitor View) All Regression Tests for Branch FOO

o   (Nested View) Regression Pipelines for Branch FOO

§  (Build Pipeline View) Regression Pipeline for Branch FOO Project BAR

§  (Build Pipeline View) Regression Pipeline for Branch FOO Project QUX

§  ...

o   (Build Pipeline View) Builds for Branch FOO Project BAR

o   (Build Pipeline View) Builds for Branch FOO Project QUX

o   ...

This is no longer scalable, and I'm wearing out my mouse button.

I have been trying to use the Job DSL Plugin to handle this, to no avail.  It 
has no support for monitor views, and when I try to nest nested views inside 
each other, the views all end up at the top level, making the tab bar 
ridiculously long.

Is there a plugin I can use, a technique you know of, or even a way to insert 
views via XML without rebooting the Jenkins server?

Thanks in advance,

--Rob



This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9A5EE68E%40dekaexchange07.deka.local.
For more options, visit https://groups.google.com/d/optout.


RE: Last Success shows unexpected time

2014-11-20 Thread Rob Mandeville
Start time is more important, as it tells  you which version of the source code 
it built and tested.  It tells you that the code that was in SCM five minutes 
ago is good.  It has no clue if the code in SCM right now can even compile.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: Thursday, November 20, 2014 8:05 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Last Success shows unexpected time

I'm pretty sure Jenkins shows the build start time,rather than build end time.

On Thu, Nov 20, 2014 at 5:16 AM, James Green 
james.mk.gr...@gmail.commailto:james.mk.gr...@gmail.com wrote:
My build just completed. It took around five minutes. The Last Success time 
shows a time five minutes ago - presumably the time the build _began_.

Am I wrong in expecting the last success to be when the last successful build 
_completed_?

James

--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Thanks!
Mark Waite
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/KCXxwJHkYM3GX2PQPOmvUikZGg4PuPFTY+AiCxr1elLN3tqpkgWzyxX4QqN2EcusMfBPjk0ffGuoZTw26POg4w==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: multi-scm plugin and wanting only some repos to trigger builds

2014-11-14 Thread Rob Mandeville
I don't think that the SCM trigger has the functionality you seek, but I could 
be wrong.

Consider a trigger job.  Write a job that only polls the one SCM that you want 
to watch, and has one task: trigger the multi-SCM job.

--Rob

-Original Message-
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Chris Withers
Sent: Friday, November 14, 2014 5:04 AM
To: jenkinsci-users@googlegroups.com
Subject: multi-scm plugin and wanting only some repos to trigger builds

Hello,

So, we have a number of jobs that use the Multi-SCM plugin, we want the build 
to trigger only when one of the 2 repos configured has changes.

How can we achieve that?

Chris

--
Simplistix - Content Management, Batch Processing  Python Consulting
 - http://www.simplistix.co.uk

--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


 Click 
https://www.mailcontrol.com/sr/r0oibr8W6GHGX2PQPOmvUml+xXZX6IbqvrZlqBNh3aDBR3jUZxU1NYsDGAD0hjxQxXDcnlWWD4nDexT6npRA1w==
  to report this email as spam.

This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Master Slave - Jenkins

2014-11-12 Thread Rob Mandeville
There is one master “slave” node, but you can set the number of executors on it 
like any other.

I set up one slave node for each SUT, each node with one executor, and have 
that node run the tests.  Anything that is done to the SUT must be done through 
the node, so Jenkins naturally prevents multiple jobs from interacting with the 
SUT simultaneously.  These nodes are on dedicated Jenkins machines, not the 
SUTs themselves (this way, you don’t need to install test software on the SUT), 
but they each have environment variables (such as the DNS name of the SUT) set 
so that the tests know which SUT to run against.  Actual builds and unit tests 
(which don’t need an SUT) are run on a different set of nodes.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of sandeep s
Sent: Wednesday, November 12, 2014 7:55 AM
To: jenkinsci-users@googlegroups.com
Subject: Master Slave - Jenkins

HI All,
Currently for our Build , automation test execution , we use Jenkins.
The current architecture doesn't scales well with respect to distributing test 
suites equally to the nodes and SUT's.

So to get started with new architecture the first question is:
1. Can we have multiple masters in Single Instance of Jenkins?
   Scenario we are thinking off is : 1 Master Jenkins , 'n slave BSD 
machines for test executions and 'n SUT;s to the Master Jenkins . Similarly we 
can have multiple masters and same infrastructure for multiple release 
executions.

IF the above question is doable , then i will have set of preceding questions 
will add up.


Thanks and Looking for a positive feedback

Sandeep






--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/G9Cd25!tqWLGX2PQPOmvUmkxeMeR4!Fm8ic!LfLuQHNmKcTtnGPHwAcHAjuCZGDyDZBLv8O0BTQNCU1!U1Tbvw==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Specs for new Master server

2014-11-12 Thread Rob Mandeville
If you move most/all of the actual jobs off to slave nodes on other machines, 
then the Jenkins server host needs to:


· Interact with the user (minimal hardware requirements if your users 
don’t use auto-refresh; auto-refresh could greatly increase CPU needs)

· Retrieve data, artifacts, and logs from the slave machines (needs 
good network connectivity and large, fast storage capacity)

· Hold data for every build (but not artifacts and logs) in core 
(requires great gobs of memory)

You certainly don’t need one core per slave executor on the master, unless you 
expect all your jobs to be “chatty” all the time.  Generally, capturing the 
data, logs, and artifacts from a build requires one or two orders of magnitude 
less CPU time than actually running the build.  You’re likely to get bigger 
speed gains by increasing the speed of your disk than that of your CPU.

Every build that your Jenkins server “remembers” will have its data stored on 
disk and in memory, and its artifacts and logs will remain on disk until and 
unless requested by a user or another job.  If this was the whole story, then 
memory and disk needs would increase without bounds.  However, you can set jobs 
to only remember a certain number of builds and/or a certain number of days of 
builds.  You can separately limit how many logs and artifacts it will keep.  
Use this feature judiciously, preferably on every job you define.  If you have  
a need to store results “since the beginning of time”, you have a big problem.  
At a previous job, I had that and had to parse my build logs and write the data 
required to a database, only using Jenkins to run builds and not to analyze the 
results.

I currently run Jenkins servers and clients on VMs, and don’t have any problems 
with them.  This might make it easier to do whole-host backups of your Jenkins 
system (if you have the space for that) for disaster recovery.

Any combined master/slave machine can be converted to a slave-only machine 
without more hardware; you might even be able to increase the number of 
executors.  In terms of server CPU and network use, adding executors to an 
existing node is slightly less expensive than adding nodes.

Finally, you have said that you are running a small number of Jenkins 
standalone servers.  I would suspect that a master-only machine needs no more 
CPU or disk than a standalone host, and may just need more disk capacity.  You 
should be able to sacrifice one standalone system to serve as the master, and 
the rest of them can be converted to slave-only hosts.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Brooks
Sent: Wednesday, November 12, 2014 8:44 AM
To: jenkinsci-users@googlegroups.com
Subject: Specs for new Master server

I have searched the archives and don't see a direct answer to this question.  I 
apologize if  this has already been asked and answered.

My team currently runs a few Jenkins stand-alone build servers, lots of jobs 
each, some CI jobs, not a lot of concurrency in builds, but some.

I have been asked to migrate our environment to a master/slave setup so the job 
management can be run from one server.  My questions is this: what kind of 
hardware would a master-only machine need to be successful?  The current 
stand-alone servers will become the slaves.

So here are the questions I am starting with:

 *   It seems from what I have read in this and other forums that it is a good 
idea to have one CPU core per executor.  Is this true for the master as well as 
the server doing the builds?  Or can we scale back?
 *   I have also read that the master can become I/O bound while moving the 
logs and build results around.  (I think I have that right but some threads 
suggest that Jenkins can become CPU bound as a result of being I/O bound, an 
interaction that I don't fully understand.)  The network backbone isn't an 
issue but I can spec out a variety of different storage solutions.  I would 
obviously like to avoid spending money on storage we don't need but I need to 
build something that will function.
 *   How much RAM should this master-only machine have?
 *   All of our servers are virtual.  That helps in that they can be rescaled 
if needed, but are there any special considerations that a virtual master 
introduces that I should know about?
 *   Is there anything that I should be thinking about when converting the 
stand-alone servers to slaves?  I have already modeled the process of getting a 
Jenkins server to be both a stand-alone server and a slave so that I can do the 
migration without bringing the servers down.  That works fine.  But is there 
anything about being a slave server that would change the system requirements?
I know I haven't provided enough details to come up with a spec, and that is 
sort of intentional.  I hope to learn instead how to do the analysis, what the 
tradeoffs are, what the design considerations are, etc. so I can 

RE: Specs for new Master server

2014-11-12 Thread Rob Mandeville
There are some hairy reasons for running a job on the master, specifically if 
you need to mess with Jenkins internals.  If you don't need to do that (and if 
you have to ask, you don't), just reduce the number of executors on the master 
node to zero and see what breaks ;^.

Also (and you probably know this) you may have to explicitly set the memory 
settings on the JVM as well as the VM; Java won't take all your memory by 
default, and you might want to leave a GB or so free so that the OS can do its 
OS-y things.  Basically, if the JVM gives an out of memory complaint, think 
about the JVM settings first--adding 64GB to your host won't help if Java is 
only taking 4GB of it.

--Rob

-Original Message-
From: Les Mikesell [mailto:lesmikes...@gmail.com]
Sent: Wednesday, November 12, 2014 12:12 PM
To: jenkinsci-users
Cc: Rob Mandeville
Subject: Re: Specs for new Master server

On Wed, Nov 12, 2014 at 8:21 AM, David Brooks dkbro...@gmail.com wrote:
 Hi Rob, rginga -

 Excellent information, exactly what I was hoping to see.

 For the RAM requirements, would it be safe to estimate the required
 RAM on the master by looking at the combined utilization of the build
 servers?  For instance, I see that the Jenkins and Java processes
 combined are using about 8GB of ram on one of our build servers.
 Would this this translate directly to the master utilization?  So just
 add up the utilization for the build servers and that is the baseline for the 
 master?

 If so then this machine is going to need TONS of ram.  Or I am going
 to have to start pruning how much Jenkins 'remembers' about builds.
 That may not go over very well with the teams.

RAM use will have 'something' to do with the total number of jobs and the 
number of builds retained for each, but won't be equivalent to
adding the whole JVM usage across multiple machines.   But if you are
using VMs you shouldn't have to be that precise in your initial setup as long 
as you don't overcommit the physical host.  I'd just pick one of the existing 
servers as the master, move the jobs there and connect the others as slaves.  
You can do that piecemeal and adjust resources
if you see a problem.   And I'd recommend not running any jobs on the
master itself, just on general principles.

--
   Les Mikesell
  lesmikes...@gmail.com


 Click 
https://www.mailcontrol.com/sr/o!P5to5kZQnGX2PQPOmvUjg7ce8j6mWJPVy6vlyKvt9qEDX2TVKozQAM3OsLei9cDZBLv8O0BTTBcfXS4znW5Q==
  to report this email as spam.

-Original Message-
From: Les Mikesell [mailto:lesmikes...@gmail.com]
Sent: Wednesday, November 12, 2014 12:12 PM
To: jenkinsci-users
Cc: Rob Mandeville
Subject: Re: Specs for new Master server

On Wed, Nov 12, 2014 at 8:21 AM, David Brooks dkbro...@gmail.com wrote:
 Hi Rob, rginga -

 Excellent information, exactly what I was hoping to see.

 For the RAM requirements, would it be safe to estimate the required
 RAM on the master by looking at the combined utilization of the build
 servers?  For instance, I see that the Jenkins and Java processes
 combined are using about 8GB of ram on one of our build servers.
 Would this this translate directly to the master utilization?  So just
 add up the utilization for the build servers and that is the baseline for the 
 master?

 If so then this machine is going to need TONS of ram.  Or I am going
 to have to start pruning how much Jenkins 'remembers' about builds.
 That may not go over very well with the teams.

RAM use will have 'something' to do with the total number of jobs and the 
number of builds retained for each, but won't be equivalent to
adding the whole JVM usage across multiple machines.   But if you are
using VMs you shouldn't have to be that precise in your initial setup as long 
as you don't overcommit the physical host.  I'd just pick one of the existing 
servers as the master, move the jobs there and connect the others as slaves.  
You can do that piecemeal and adjust resources
if you see a problem.   And I'd recommend not running any jobs on the
master itself, just on general principles.

--
   Les Mikesell
  lesmikes...@gmail.com


 Click 
https://www.mailcontrol.com/sr/o!P5to5kZQnGX2PQPOmvUjg7ce8j6mWJPVy6vlyKvt9qEDX2TVKozQAM3OsLei9cDZBLv8O0BTTBcfXS4znW5Q==
  to report this email as spam.

This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from

RE: how to run all jobs in parallel using build flow plugin which are stored in string array

2014-11-11 Thread Rob Mandeville
I’ve dealt with this problem.  You generate a list of closures, and then run 
the list through parallel.  I’ve changed the constants to protect my employer, 
but the code goes like this:

Jobs_to_build = [ ‘foo’, ‘bar’, ‘baz’, ‘xyzzy’]
  jobs_to_build.each { String job_name -
  a_closure = { -
build(job_name,
PARAMETER_1: ‘You can add all the parameters you want here as key-value 
pairs’,
PARAMETER_2: ‘Or just use build(job_name) if they don’t take parameters’
)
  }
  build_closures.add(a_closure)
}
// Run all build jobs for this project/branch tuple in parallel
parallel(build_closures)
  }
}

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of niraj nandane
Sent: Tuesday, November 11, 2014 5:24 AM
To: jenkinsci-users@googlegroups.com
Subject: how to run all jobs in parallel using build flow plugin which are 
stored in string array

Hi,
I want to run the jobs in parallel which are stored in string array using 
build-flow plugin's parallel method.
Any help would be greatly appreciated.
Thanks,
Niraj
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/tyvBwV!0D0bGX2PQPOmvUihCLhWP7Wj9hNznH0s0xN+HlCIE6hbY3M4YnGFX!boy+pKcdHXFkglAlVq5uz6AOA==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Groovy script to do jenkins configuration

2014-11-10 Thread Rob Mandeville
If you want to configure your Jenkins service via Groovy, you need the Groovy 
plugin.  This allows you to run a “System Groovy Script”.  This runs in the 
same JVM as the server.

This gives you the raw capabilities.  I don’t know of one particular reference 
to tell you how to do what you’re trying to do.  You may need to get the 
javadoc for your server and for the plugins you wish to configure.  I don’t 
have the code here, but at a previous position I was able to use this 
capability to enable and disable slave nodes as part of a Jenkins job.

You may also want to look at the Scriptler plugin.  This will allow easier 
storage of your Groovy configuration scripts, and easier execution of them 
within a Jenkins job.

Hope this helps!

--Rob Mandeville


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ankush Aggarwal
Sent: Monday, November 10, 2014 7:30 AM
To: jenkinsci-users@googlegroups.com
Subject: Groovy script to do jenkins configuration

Hi All,

I have installed sonar and artifactory plugin in jenkins. I want to do both 
sonar and artifactory configurations via groovy script.

I am able to do using GUI Manage Jenkins - configure system but need to do 
similar activity via groovy script.

Anyone please help me on this.

Thanks,
Ankush
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/xlCCm2w16k!GX2PQPOmvUtVTDJsKpCsgkXmJl7Mxg1r+EDfsm14EugAM3OsLei9chu5YqLyvUFSzR1Lppn2zgQ==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Groovy script to do jenkins configuration

2014-11-10 Thread Rob Mandeville
Sorry, I don’t know how to help you more there.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ankush Aggarwal
Sent: Monday, November 10, 2014 9:05 AM
To: jenkinsci-users@googlegroups.com
Cc: Rob Mandeville
Subject: Re: Groovy script to do jenkins configuration

Hi Rob,

I have script to add Maven configuration through groovy script and it is 
working fine. i need similar kind of script for sonar and artifactory.

maven3.groovy


import jenkins.*
import jenkins.model.*
import hudson.*
import hudson.model.*
a=Jenkins.instance.getExtensionList(hudson.tasks.Maven.DescriptorImpl.class)[0];
b=(a.installations as List);
b.add(new hudson.tasks.Maven.MavenInstallation(MAVEN3, 
/home/jenkins/apache-maven/apache-maven-3.2.3, []));
a.installations=b
a.save()

command line to execute.
java -jar jenkins-cli.jar -s  http://localhost:8080/ groovy maven3.groovy

-Ankush

On Monday, 10 November 2014 19:03:44 UTC+5:30, Rob Mandeville wrote:
If you want to configure your Jenkins service via Groovy, you need the Groovy 
plugin.  This allows you to run a “System Groovy Script”.  This runs in the 
same JVM as the server.

This gives you the raw capabilities.  I don’t know of one particular reference 
to tell you how to do what you’re trying to do.  You may need to get the 
javadoc for your server and for the plugins you wish to configure.  I don’t 
have the code here, but at a previous position I was able to use this 
capability to enable and disable slave nodes as part of a Jenkins job.

You may also want to look at the Scriptler plugin.  This will allow easier 
storage of your Groovy configuration scripts, and easier execution of them 
within a Jenkins job.

Hope this helps!

--Rob Mandeville


From: jenkins...@googlegroups.comjavascript: 
[mailto:jenkins...@googlegroups.comjavascript:] On Behalf Of Ankush Aggarwal
Sent: Monday, November 10, 2014 7:30 AM
To: jenkins...@googlegroups.comjavascript:
Subject: Groovy script to do jenkins configuration

Hi All,

I have installed sonar and artifactory plugin in jenkins. I want to do both 
sonar and artifactory configurations via groovy script.

I am able to do using GUI Manage Jenkins - configure system but need to do 
similar activity via groovy script.

Anyone please help me on this.

Thanks,
Ankush
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-use...@googlegroups.comjavascript:.
For more options, visit https://groups.google.com/d/optout.

Click herehttps://www.mailcontrol.com/sr/MZbqvYs5QwJvpeaetUwhCQ== to report 
this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: I am a jenkin user would like post few queries

2014-11-06 Thread Rob Mandeville
You posted to the group rather than to the subscriber.  The subscriber address 
is 
jenkinsci-users+subscr...@googlegroups.commailto:jenkinsci-users+subscr...@googlegroups.com.
  On the other hand, as you did post to the group, it looks like you’re already 
a member.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Prem Subudhi
Sent: Thursday, November 06, 2014 9:24 AM
To: jenkinsci-users@googlegroups.com
Subject: I am a jenkin user would like post few queries

Please allow me to join in this group.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/ey6BmB5xbXrGX2PQPOmvUtVTDJsKpCsgOVoMdwkKhUB!ltIo1UttCpfM1iyAeuy4XkrYMy68DJOsCq9I+zBdpQ==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Unable to successfully start a JBOSS service using Publish over SSH

2014-11-04 Thread Rob Mandeville
I’m not sure if this is relevant, but it may be worth looking at.  The slave 
considers the job complete when the process exits _and_ STDOUT and STDERR have 
been closed off.  Since the “service” program is launching JBoss, it may do 
something stupid like leave stderr open, so that if the server ran into a 
problem, you’d see it on the prompt that you ran “service” on.

Here’s an experiment.  Make the command:

service jboss start  /tmp/jboss_start.out 21  cat /tmp/jboss_start.out

One of three things might happen:

1: Everything just works, which is great.
2: The job still hangs, and cat is left running, not getting EOF from 
jboss_start.out because the server is still connected to it.  If you can get 
away with it, ditch the ‘cat’ command and only look at jboss_start.out by hand 
if you need to.
3: The job still hangs after cat exits out, which means that my theory is wrong.

--Rob


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Eric Wood
Sent: Tuesday, November 04, 2014 3:51 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Unable to successfully start a JBOSS service using Publish over SSH

An additional note.  I see that they recommend using the provided service 
script called $JBOSS_HOME/bin/init.d/jboss-as-standalone.sh. We are using some 
older version developed in-house.  I can't see significant differences, but 
not sure if the way the service is invoked is a factor.
do you use the recommended version of the init.d script mentioned above?

Thanks, Eric

On Tuesday, November 4, 2014 3:37 PM, Eric Wood 
eric.w...@rocketmail.commailto:eric.w...@rocketmail.com wrote:

Richard:

When I run the service from the command line on the actual server, it takes 
about 30 secs to run and does return to the command line prompt.  If I run the 
same service from the publish over ssh, it does not seem to return and times 
out.  I have the time out set to five minutes.  It i stop the process once it 
is started via the ssh command and then go to the server and kill the process 
by running a service jboss7.1 stop, the ssh command will terminate and return 
normally to the jenkins job and indicate success.  What is teh run line you are 
using to start your service?

Thanks, Eric

On Tuesday, November 4, 2014 3:13 PM, Richard Bywater 
rich...@byh2o.commailto:rich...@byh2o.com wrote:

Hi Eric

We do this with JBoss EAP and it works fine. We found we had to up the Exec 
Timeout property (under Advanced) as the JBoss start script that we use 
doesn't return until the app server has started and all the apps deployed have 
started too (i.e. its open for business)
Not sure if thats what you are seeing or not but might be worth looking at. I 
assume that service jboss7.1 start, if run from a normal command line, will 
eventually return back to the shell prompt? If not, then that's probably the 
bigger issue as service commands should really return eventually :)
HTH
Richard.

On Wed, Nov 5, 2014 at 7:18 AM, Eric Wood 
eric.w...@rocketmail.commailto:eric.w...@rocketmail.com wrote:
The appearance is that as long as the process is running, the ssh session will 
not terminate. It will eventually timeout, but not terminate on it own even 
when the service command exits with a 0.  If I run the command:

 service jbossas7.1 stop

while the Jenkins job is still connected and after the service has successfully 
started, it will terminate the connection and the job will return with a 
success status.  How do I get the service started and the ssh session to 
terminate when the service starts.

On Tuesday, November 4, 2014 12:11 PM, Eric Wood 
eric.w...@rocketmail.commailto:eric.w...@rocketmail.com wrote:

I am attempting to stop and start a JBOSS service on a remote server and I am 
using the Publish over SSH plugin for this purpose.  I am running the service 
command

service jbossas7.1 start

I can see it starting up, but the plugin does not seem to disconnect after a 
successful startup. Eventually the ssh connect timeouts and the build 
terminates in an UNSTABLE state.  Any idea how I can resolve this issue? The 
run line in the service script looks like this:

su -s /bin/sh $JBOSS_USER -c sh $JBOSS_HOME/bin/standalone.sh -c 
appConfig.xml -b 0.0.0.0 21  /tmp/jboss7.log 

Thanks, Eric


--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You 

RE: batch file is not an internal or external is not recognized as internal or external command

2014-10-09 Thread Rob Mandeville
How do you set the Windows path?  If you’re not setting it in the job itself, 
consider it suspect.  The PATH you get if you’re using the master node is the 
PATH that Jenkins launches with (is it set up as a service?).  If you’re using 
a slave node, you get the PATH that the slave launches with.

Either set the PATH in the Batch step that you are running the files in, or 
call them explicitly by path.  Remember that the batch step will run in the 
workspace directory, so you should be able to use a relative path.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Menos II
Sent: Thursday, October 09, 2014 11:00 AM
To: jenkinsci-users@googlegroups.com
Subject: batch file is not an internal or external is not recognized as 
internal or external command


Hello,

I am trying to build a Delphi XE6 project. The source code is being pulled from 
two subversion folders. Inside one of these folders are a few .bat files that 
need to be run. I assigned these .bat files to be run on a build task. When 
trying to build the project everything goes fine until the build needs the 
execute the .bat files. I get the following error: [bat file] is not recognized 
as an internal or external command, operable program or batch file. I already 
tried adding the subversion and the Jenkins workspace directory to the Windows 
Path, but this has not fixed the problem. I also disabled UAC.
Hopefully someone can help me.

System information:
Windows 8.1
Jenkins 1.583
Google Chrome.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/lY!cibUq2L!GX2PQPOmvUlHUcPnZ!qyDFruFDv!cpa7lEZVLFhpbq7YkKSbFUrl7ZzI00M6Pw3ug1M3YVHc55g==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Parametrically creating Build Flow jobs

2014-08-25 Thread Rob Mandeville
I'm working on a system with n projects and m branches on each, so I want nXm 
build chains of jobs.  I've already grabbed the Job Generator plugin and used 
that and a Build Flow job to generate sets of free-style jobs, and that works 
fine.  But now I want to wrap each build chain in its own separate Build Flow 
job.  I know that I could just parameterize it and let people call it that way, 
but I really want nXm build flow jobs that just differ in a couple of settings. 
 Is there a good way to do this?  I think there's an Enterprise plugin that 
lets us do this, but we're not ready to pony up money to CloudBees at this 
point.  I am, however, not averse to diving into the server a little bit with 
Scriptler.

Thanks in advance,

--Rob



This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Large scale Jenkins installation : Help!

2014-08-19 Thread Rob Mandeville
I used to run a system with about as many executors, but all in one server room.

First off, is there a good reason to run the slaves on a WAN?  I understand 
that your users are spread throughout Europe, but why should your builds be?  
Users generally only need to talk to the Jenkins server, not every piece of the 
build farm.  Would it be possible to simply ship all of your racks to one 
building?

If you need a geographically distributed build farm, you should see how much 
you can localize resources to a single farm.  Of your three SCM systems, Git is 
distributed, so it’s preferable.  I suspect you don’t get to choose, however.  
When using ClearCase, especially with a distributed build farm, make sure to 
use snapshot views.  You do not want every single file read to be a 
transcontinental event.

Jenkins requires a permanent connection to the slave nodes.  If your WAN is 
even a little bit flaky, you could lose slaves easily.  Consider putting a 
separate Jenkins server at each site, and then having a master one for user 
interface (where the configuration for “build project Foo” is “Tell Jenkins in 
Frankfurt to build project Foo”).  This will be easier if you can isolate 
various projects to a single site each.

Per the memory leak on the server: do as little as possible on the server’s 
address space.  See if you can reduce the number of master nodes to zero, so 
everything is done on the slaves.  If you aren’t already, consider using Java 7 
or Java 8, each of which has its own strategy to GC PermGenSpace.

Your Jenkins server(s) should be well-connected and have plenty of fast disk.  
Logs and artifacts end up being sent to the server in real time.  Also, all of 
the data (except for the logs and artifacts) from the build runs it is aware of 
goes into memory on the server.  To reduce this, set jobs to erase old 
builds—do something like keep the last 100 runs, or the last 30 days of runs.

If you’ve got a farm this big, you may want to go pro.  While Cloudbees’ bread 
and butter is serving you build farms on the cloud, they also sell CloudBees 
Enterprise.  This is a support contract plus some extra plugins not available 
for general release.  Said plugins are designed for controlling large 
deployments like yours.  My previous employer used it, and liked it.  It is a 
bit expensive, and the license fee is per server and per executor.  What we 
didn’t try is a new product called Jenkins Ops Center.  This appears to be able 
to tie multiple Jenkins servers together.  They are worth investigating.

Finally, if you’re considering upgrades, you don’t want the Latest and 
Greatest.  Get the LTS (Long Term Support) release; currently, that’s 1.565.1.

Hope this helps!

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Frederic Meyrou
Sent: Tuesday, August 19, 2014 8:09 AM
To: jenkinsci-users@googlegroups.com
Subject: Large scale Jenkins installation : Help!

Dear mates,

I'm recently in charge of quite big Jenkins configuration based on a central 
master (no build on master) with :

7000 Jobs
136 active Slaves mostly tied build
150-200 Total Slaves
~450 potential executors

Users are on many RD sites in Europe, slaves are spread over the WAN each site 
has a Nexus proxy next to the slaves.
SCM servers (SVN/ClearCase/Git) are not on the same LAN...

At the moment the console is quite slow and we had recently memory trouble that 
end-up adding 4 more Gb of RAM to the server and review the JVM setup
below. At the moment it looks better, but I can't be sure because most builds 
are schedule at night... I installed the monitoring plugin.
The strange thing is that Jenkins is using more memory on the Windows server 
then just the total of XMX + MaxPermSize (7+1 Gb), and ends-up using more
then 10 Gb... any idea why?
I found a memory leak affecting the PermGen memory, the number of loaded 
classes rise continuously and fills-up PermGem memory at the same time. I have 
to restart Jenkins weekly.
It saw also slave build making surefire reports over 200Mb going back to the 
server.
I'm also convinced that I should migrate to a more recent version of Jenkins, 
but with such a big config and so much users, it's not so easy!

What do you think of such a configuration? Do you think the server is well 
sized or under-sized, should I use several master? Any TIPs for large scale
administration is welcome!

My configuration :

VMWare VM
Win 2K8R2 64bits
12 Gb VRAM
4 VCPU Xeon X5660 2,8 Ghz
JENKINS : 1.424.1
TOMCAT : 6.0.29
JDK : 1.7.0_03

Tomcat JVM Setup as a NT Service :
-Xms7g -Xmx7g -Xss128kb
-XX:+UseLargePages
-XX:PermSize=1g
-XX:MaxPermSize=1g
-XX:+UseConcMarkSweepGC
-XX:+UseParNewGC
-XX:+CMSIncrementalMode
-XX:+CMSIncrementalPacing
-XX:CMSInitiatingOccupancyFraction=33
-XX:CMSIncrementalDutyCycleMin=10
-XX:CMSIncrementalDutyCycle=50
-XX:ParallelGCThreads=8
-XX:MaxGCPauseMillis=2000
-XX:GCTimeRatio=10
-XX:+DisableExplicitGC

Fighting the Screensaver

2014-08-18 Thread Rob Mandeville
Our QA team is using the TestComplete GUI testing software to test our web 
applications.  TestComplete drives a Windows console session, effectively 
emulating mouse and keyboard, to test how a given browser responds to our code.

The problem that we've been having is that there is a password-protected 
screensaver installed on the Windows machine for security purposes.  As a 
result, the test launches on a locked Windows VM, then hangs until timeout and 
fails.

While we are working with the admins to get an exception there so that we don't 
have the screensaver, this may be difficult-this company has had decades of 
experience building medical devices with embedded software, but as a company 
we're still learning how to do web applications.

I have also advised the QA team to start their test suites by using 
TestComplete to log into the VM console, then end them by logging out of it.  
It's unclear whether that will be possible.

The Jenkins slave node is running on the Windows VM.  Is there a Jenkins way, 
given the proper credentials, to log into the console or authenticate past the 
screensaver before launching a build?

Thanks in advance,

--Rob



This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Top 5 mistakes RD managers make when managing open source usage

2014-08-14 Thread Rob Mandeville
I think that it’s both off-topic and marketing a service.  Neither are 
appropriate for this mailing list.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of 
patricia.john...@whitesourcesoftware.com
Sent: Thursday, August 14, 2014 6:25 AM
To: jenkinsci-users@googlegroups.com
Subject: Top 5 mistakes RD managers make when managing open source usage

Hi,

Here's our latest blog post - we ranked the top mistakes people make when 
managing open 
sourcehttp://www.whitesourcesoftware.com/top-5-mistakes-rd-managers-make-managing-open-source-usage/.
What do you think?


--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/BDKnD5It+CTGX2PQPOmvUjg7ce8j6mWJuMP+4vXtOQISjD!sSzFZ6M6TcmujaHJVURR7CItTLEgmMzVbnZsAVw==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: False positive on Jenkins builds. How to address.

2014-08-08 Thread Rob Mandeville
Ugh, intermittent test failures.  I lived in that jungle for years.  In a 
previous life, my company used Jenkins to drive a complete homebrew solution.  
We wrote a tool to parse the log and write to database, wrote a webapp to read 
the database and let you know what failed, even wrote a tool to produce a 
subset of jobs so that you could auto-rerun all the failures.  Jenkins was 
reduced to simply running the jobs, and nobody looked at the site to see what 
passed and what failed.

Trust me: you do not want to go there unless it’s absolutely necessary.

First thought should be to keeping these tests from being intermittent.  
Perhaps the test code could account for strange OS or resource factors.  
Perhaps you can limit slave nodes or something to control resource contention.  
Perhaps not.

If fixing the intermittency is not an option, your next defense is to break up 
the build.  If you have an hour of tests, but only five minutes of them are 
intermittent, isolate the intermittents into their own job so that you can do a 
rerun in five minutes rather than an hour.

Now, for plugins.

First, there is a Naginator plugin.  This can be configured to rerun failed 
builds, so it can keep trying those intermittent tests.

Secondly, there is a Build Flow plugin, which is more complicated and more 
versatile.  You use it to tie a bunch of build jobs together (compile as one 
job, unit tests over on another one, Selenium jobs on a third…).  The DSL that 
you use has the ‘retry’ keyword, so you can say to run a certain job some 
number of times until it succeeds.  This would allow you to have one master 
build that is red, yellow, or (blue|green), and that could retry your 
intermittent tests until they pass or just fail one too many times.

Of course, all of this retrying-until-it-works is based on the assumption that 
if you run a test three times and it fails on two of those tries, the test 
should be considered passing.  This is not a good assumption: it could mean 
that the code is just plain flaky.  I prefer to get the test to recognize the 
conditions that make it flaky and thus respond to them.  If the test can fail 
because the database is unresponsive, have the test start by trying to contact 
the database, and retrying every minute or two until it succeeds or a 
test-determined timeout occurs.  Handling intermittency at the test level 
rather than the Jenkins level requires you to define the things that can break 
your test, rather than just assuming that passing once in a while is okay.  If 
you can name me some factors that cause your tests to go intermittent, I may 
have some ideas as to how to make the tests non-intermittent.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Albert Tresens
Sent: Friday, August 08, 2014 11:05 AM
To: jenkinsci-users@googlegroups.com
Subject: False positive on Jenkins builds. How to address.

Hi,

I am trying to optimize the triaging time on jenkins failues caused by false 
positives. There is a percentage of failures that are always self healed after 
subsequent builds.  Mostly dependent on the underlying OS or some resource 
factors.

Does someone followed any specific approach to address such a situations?. I 
guess is a common problem.

I thought about spawning the Jenkins jobs so I get duplicated results and 
discard if its not a double failure or adding plugins for filtering specific 
exceptions.

Any suggestion or alternatives?

Thanks!
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/T2QE9Uq1co7GX2PQPOmvUtVTDJsKpCsgUcP!5TmclhuaW9pNFZEyQhCHjGJhJAM35b6TXk5rwVH1VsBVsOva5A==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Could not load program curl

2014-08-04 Thread Rob Mandeville
If you’ve checked on the server, are you sure that the job is running on the 
server?  If the job ran on a slave node running on another machine,  you have 
to check the machine that the slave node is running on.

--Rob


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Max B
Sent: Monday, August 04, 2014 1:29 PM
To: jenkinsci-users@googlegroups.com
Subject: Could not load program curl


Hi,



I am invoking the jenkins job and I am seeing these errors in my log.

can someone please advise me ? how do I fix it ?



i've already checked on my server i've those listed files in corresponding 
directories.





Could not load module /usr/lib/libidn.a(libidn.so.11).

 Dependent module /usr/lib/libiconv.a(libiconv.so.2) could not be 
loaded.

 Member libiconv.so.2 is not found in archive

Could not load module curl.

 Dependent module /usr/lib/libidn.a(libidn.so.11) could not be loaded.

Could not load module .
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/Wi9yr9YQTcHGX2PQPOmvUgfUspOYWKRb7LoQTIN2PxBWw+QCsiIu1IHtNluRcx4ZalPjxinsAkDBcfXS4znW5Q==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Any upper limit on slaves?

2014-07-29 Thread Rob Mandeville
I have personally run about 350 one-executor slaves (each slave represented a 
unique resource).  The hardware was reasonably beefy, at least 128 GB RAM and 
1TB storage, and the Jenkins server ran a bunch of other services as well.  The 
limiting factor appeared to be disk I/O; remember that all logs and artifacts 
have to be saved to disk on the server end.  Judicious use of “discard old 
builds” might be needed to keep disk usage in check.

My system was running builds 24/7.  It can be difficult if you are doing the 
same, as there is no safe time to bounce the service.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly
Sent: Tuesday, July 29, 2014 4:21 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Any upper limit on slaves?

With appropriate tuning of various parameters, we have seen customers get over 
1000 executors on-line (with an average of 2-3 per slave)

With a large number of slaves, you are usually better using one of the 
on-demand retention strategies.

Getting all 1000 executors running builds can be problematic though.

I am currently working on a scalability framework for testing how Jenkins 
scales. It will be here https://github.com/jenkinsci/scalability-test-framework 
once I finish some refactoring that I identified as required - I want people to 
have a mostly stable API when I publish this framework.

Some other tooling I have built:

* https://github.com/jenkinsci/mock-load-builder-plugin which will create build 
jobs that should load up the remoting channel with load representative of a 
chatty build

* https://github.com/jenkinsci/random-job-builder-plugin which will build jobs 
selected at random at a specified rate.

With that tooling you can set up a Jenkins instance with a load of jobs and 
have those jobs queue up in a semi-realistic - if stressed - way.

Using all the above I can report that:

A 1.553 Jenkins master on an m3.large can support:

* Connecting 60 JNLP slaves and having them idle (but the system will be 
unresponsive for 2-3 minutes after startup); OR
* Connecting 60 SSH slaves and having them idle (but the system will be 
unresponsive for 5-6 minutes after startup); OR
* Connecting 60 CloudBees NIO SSH slaves and having them idle

All with 2 executors per slave

For both of the SSH slave options above, you need to tell the JVM to use 
/dev/./urandom as the entropy source. I suspect the newer NIO JNLP mode will 
have removed / reduced the unresponsivity of the JNLP master after startup... 
also that is a side-effect of me starting all the JNLP slaves at the same time. 
Real systems will likely have JNLP slaves connect in a more staggered way and 
not suffer the thread contention that locks up the Web UI.

On each of those test systems I created 3000 mock jobs organized in folders. I 
then upped the rate of builds until the Web UI became unresponsive.

* JNLP hits system load  5 and web UI is unusable at somewhere between 50 and 
55 concurrent builds on an m3.large
* Traditional SSH hits system load  5 and web UI is unusable at between 10 and 
12 concurrent builds on an m3.large
* CloudBees NIO SSH hits system load of 4 at 15 concurrent builds, but Web UI 
remains usable all the way up to 120 concurrent build. The build duration - 
however - is increased once you go past 15 concurrent builds. So the cause and 
effect here is that back-pressure is being forced on the build in order to 
allow the master to remain usable...

I picked a m3.large as being a reasonably cost-effective machine type that 
would let me scale up to a size where you should start seeing problems of 
scalability but not so large that I need a massive army of machines to saturate 
it.

HTH

On 28 July 2014 23:51, Maureen Barger 
mobar...@gmail.commailto:mobar...@gmail.com wrote:
Hi - I am wondering if there is a limit to how many slaves can connect to one 
master.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/!oag5VG71g!GX2PQPOmvUgfUspOYWKRbGsXAOJ84oQ4x7JVx4eYAnf8VFAIdfjuAZ!IcHOUH37CzR1Lppn2zgQ==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain 

RE: Can i revert back the commit in git if the build fails in jenkins or bamboo?

2014-07-21 Thread Rob Mandeville
Maybe you can go about it the other way around.  If you haves branch called 
“r1.0” that you want to protect, don’t let users merge to “r1.0”.  Instead, 
have them merge to “r1.0_candidate”.  Put a build job on that, and let it 
promote from “r1.0_candiate” to “r1.0” if the tests pass.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Sumit Kumar
Sent: Monday, July 21, 2014 2:29 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Can i revert back the commit in git if the build fails in jenkins 
or bamboo?

Is there any other option available?? Writing hooks/scripts for checking if 
Build Fails or not in jenkins??

On Friday, July 18, 2014 5:25:07 PM UTC+5:30, Mark Waite wrote:

I am not aware of any Jenkins plugin that will revert changes on a failed build.
On Jul 18, 2014 5:48 AM, Sumit Kumar 
sumi...@gmail.commailto:sumi...@gmail.com wrote:
Can we write checks or script to do the revert in GIT, pre commit hooks or do 
we have any plugin available in jenkins or Bamboo for this?
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-use...@googlegroups.commailto:jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/7fHdpJqeGWTGX2PQPOmvUmkxeMeR4!FmLShixMFkpqDJ12uG!oUC4RkNRpVuV2sX2PF171VK7gusCq9I+zBdpQ==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: How do I stay logged into multiple Jenkins servers

2014-07-18 Thread Rob Mandeville
I’ve been using http://hostname:8080 for one and http://hostname:9090 for the 
other.  I took another’s suggestion and am using an alternate browser for my 
second instance.  It works, though if there is a simple solution that allows me 
to use the same browser, I’d be all ears.  If it’s going to take some real 
effort, I’ll just go by the two-browser method.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Richard Bywater
Sent: Thursday, July 17, 2014 2:55 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: How do I stay logged into multiple Jenkins servers

I'm guessing you are using the same host name for both instances and switching 
based on context? If so, changing it to switch by (virtual) host names would 
solve what sounds like a cookie issue although not sure if Winstone supports 
virtual host concept?

Richard.

On Friday, July 18, 2014, Rob Mandeville 
rmandevi...@dekaresearch.commailto:rmandevi...@dekaresearch.com wrote:
I have two Jenkins servers: one for prime time use (my production environment; 
my customers’ development environment) and another for my own mad science 
development.  Both are currently on the same Linux machine and running out of 
Winstone, but both aspects of that are negotiable.  The fact that it’s using 
Active Directory for authentication is less negotiable.

The problem is that I have to work on both of them.  I do some work on one, 
then I go to the other one and I have to log in again.  Once I flip back to the 
first one, I have to log in _again_.  Is there any way for me to remain logged 
into both instances simultaneously?

Thanks in advance,

--Rob



This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/NZlKHZR9bcvGX2PQPOmvUj!GOBh06pKKgw0jkqkEgFINLgTwhjo5E9SzFHfi2FTWs7l1mTlXsv9AlVq5uz6AOA==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


How do I stay logged into multiple Jenkins servers

2014-07-17 Thread Rob Mandeville
I have two Jenkins servers: one for prime time use (my production environment; 
my customers' development environment) and another for my own mad science 
development.  Both are currently on the same Linux machine and running out of 
Winstone, but both aspects of that are negotiable.  The fact that it's using 
Active Directory for authentication is less negotiable.

The problem is that I have to work on both of them.  I do some work on one, 
then I go to the other one and I have to log in again.  Once I flip back to the 
first one, I have to log in _again_.  Is there any way for me to remain logged 
into both instances simultaneously?

Thanks in advance,

--Rob



This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Java API to get the view name

2014-07-16 Thread Rob Mandeville
Not likely, as there is no view name for a job.  It’s an N:M relationship 
between jobs and views: a view can have any number of jobs, and a job can have 
any number of views.  I suspect that jobs don’t “know” what view they’re in.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Subashini Unny
Sent: Wednesday, July 16, 2014 2:38 PM
To: jenkinsci-users@googlegroups.com
Subject: Java API to get the view name

Is there a Java API in Jenkins to get the view name for a job? I did see that 
there is a way to get the list of all views and then the list of items in each 
view and can check if my job is present in that list but this is not very 
efficient and also might have performance implications.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/r0Mp98k3cyjGX2PQPOmvUihCLhWP7Wj9lqZ5e3i0gKQuDn23SbCOpXbbFirEORjv72UkG9eV!fqqE4naC2k80A==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Jenkins setup question

2014-07-14 Thread Rob Mandeville
Obligatory link to Jenkins doc: 
https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds.

This sounds fairly straightforward for Jenkins.  A Jenkins server can have any 
number of slave agents attached to it (I’ve personally run a server with 300+ 
agents and there are bigger ones out there), so you just put one slave agent on 
each host.  Give each slave node the same label (like “remote”) and set up your 
jobs to require that label, and the jobs will only launch there (rather than on 
the master Jenkins server).  If it only makes sense to run one thing on a box 
at a time, set the number of executors on the  node to one; if not, set it to 
the maximum number of jobs you would feel comfortable running on that machine 
at a time.

Each agent will reside on one machine, and they don’t talk to each other; all 
Jenkins communication goes through the server.

If you have other questions, feel free to ask.  If you need to know how to get 
the slave agents up and running on these machines, not what platform the slave 
machines are running.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of ctime800
Sent: Friday, July 11, 2014 11:52 PM
To: jenkinsci-users@googlegroups.com
Subject: Jenkins setup question


I need a Jenkins setup advise:

What I want to achieve is like this:
* Jenkins master 1 has:
* Jenkins slave 1
* Jenkins slave 2
* Jenkins slave n

Each slave will have identical software so that I can run the build/deploy job 
on each and load balancing them. All good with this setup so far?

Then for deployment with an Agent (i.e. setting up Jenkins Agent in each slave 
to the runtime server for deployment), how do I achieve this goal with the 
above architecture? I think of the follow issue (not sure if they are):

1. The Jenkins slave cannot connect to another slave (the runtime server)?
2. How do slave 1  slave 2 have the same Agent pointing to the same runtime 
server?

If this is not the right approach, what will the new approach be? Again, what I 
want is to be able to add more slaves easily to support more loads when needed.

I think the 'agentless' deployment model work, but agent deployment model will 
not work with this setup.  Thanks for your help in advance!
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/jyKGat8RsOrGX2PQPOmvUqW!RI4xIDLr3j4LpY8DWDH4o24xPTWXmjvQ9CVHIG9Rz5IJDRCUVEZPpv0P1Tfw+Q==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Jenkins, BitBucket and MatLab on Ubuntu

2014-07-08 Thread Rob Mandeville
You’ll want to go through the documentation at http://jenkins-ci.org/, clearly.

I’m assuming that you have BitBucket and MatLab (two technologies that I am 
unfamiliar with) on a Ubuntu box.  I’m also assuming that you know BitBucket, 
MatLab, and Ubuntu.  Frankly, I’m not sure what TAP is, so I can’t help you 
there.

You can read how to install Jenkins at 
https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins, in the section 
“Installation”.  Basically, you download jenkins.war (there’s a link on that 
page) and run “java –jar jenkins.war”.  You’ll have a simple Jenkins server on 
port 8080.  If you don’t know how to have that come up every time the machine 
boots, your local sysadmin will know how to make an “init.d script” to make 
that happen.

Via the Web, go to Manage Jenkins-Manage Plugins.  If you only reach the 
internet through a proxy, select the ‘Advanced’ tag and set the HTTP Proxy 
configuration; see your admin as needed.

Select the ‘Available’ tab.  Search for the plugin called ‘Bitbucket 
pullrequest builder plugin’  Click the box to put a checkmark on it, then get 
to the bottom of the page and click ‘Install without restart’.  This should 
install the BitBucket plugin.

Now you’re ready to create a build job.

Get back to the main screen by clicking the word ‘Jenkins’ in the top left hand 
corner (to my knowledge, this always works).  Click ‘New Item’ to create a new 
job.  Give it a name, and select ‘Build a free-style software project’ and you 
will go to the configuration page.

Your first goal here is to just get the matlab job to run.

Go to the ‘Source Code Management’ section and select BitBucket.  I don’t know 
what options it will have, but whatever they are, they should make sense to an 
expert in BitBucket.  Select the options needed.

In the ‘Build’ section, add a build step called ‘Execute Shell’.  When this job 
runs, it will create a new (and temporary) directory, drop everything you’re 
pulling out of BitBucket into that directory and the appropriate 
subdirectories, and then run whatever you put in the execute shell step as if 
it was a Bash script.

Once you have the configuration the way that you want it, click ‘save’ at the 
bottom and you’ll get a page for the job itself.  Click the ‘build’ button (it 
looks like a clock with a ‘Play’ triangle, as you are actually scheduling a 
build).

On the left, there will be a ‘Build history’ section.  The ‘ball’ to the left 
will be blue if it succeeds (there’s a plugin to make that green if you prefer) 
or red if it fails.  There is yellow for ‘unstable’, but you won’t be using 
that at this point.

Very likely, the first run will hand you a red ball back.  Like anything else 
in software, you’re gonna have to debug.  Click on the build you just ran, then 
on ‘Console output’, to see what happened.  Once you know what happened, go 
back two pages to the page for the job itself, and select ‘Configure’ to go 
back to the configuration page.  You’ll cycle between running a job, checking 
the console output, and editing the configuration to get it right.

You may have to take several tries to get this script to work.  It will have 
mostly the same environment of whoever or whatever ran the ‘java –jar 
Jenkins.war’ command, so the environment will be different if you start it from 
your command line versus it being started from an init.d script.  If, for 
example, it complains that it can’t find MatLab, go into the shell step and add 
the directory MatLab is in to the path before running the command.  If you have 
trouble here, work with your local shell script expert; that’s all this step is 
doing.

Once you have that all set and are getting blue results back, check the output 
again to make sure that it’s actually doing what you want it to do.  Once 
you’re assured of that, you’re probably going to want to automate running this. 
 Back in the configuration, go to ‘Build Triggers’.  You probably want to use 
‘Build periodically’ (build it every day or every two hours, for instance), or 
‘Poll SCM’ (build every time somebody checks new stuff into BitBucket.  Rely on 
the little blue help icons on the right to walk yourself through this.

I’ll leave the ‘tutorial’ at this point, as the next steps (if any) depend on 
what you want to do.  There are a set of ‘Post-Build Actions’ that can read the 
output to determine if tests passed, publish output from certain files or 
directories, or send email to various people when the job finishes (or even 
just when it fails).  What you’re going to do here depends on what your needs 
are, and I can’t possibly cover every possibility.

--Rob


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Martin Bergene Johansen
Sent: Tuesday, July 08, 2014 4:32 AM
To: jenkinsci-users@googlegroups.com
Subject: Jenkins, BitBucket and MatLab on Ubuntu


Hello

I’m new to Jenkins, BitBucket, MatLab and Ubuntu, and I’m in a project group 
that needs to run 

RE: Jenkins, BitBucket and MatLab on Ubuntu

2014-07-08 Thread Rob Mandeville
You’re getting a permission denied failure trying to write to 
/home/gevj/MatLabScripts/MyTAPOutput.tap.  Odds are, the user Jenkins is 
running as doesn’t have write permissions there.

Generally, Jenkins doesn’t write to other users’ home directories.  If you 
really want it to, you would have to give the Jenkins user write permissions 
there.  More likely, you want to tell Matlab (or maybe the Matlab script?) to 
write to a different place.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Martin Bergene Johansen
Sent: Tuesday, July 08, 2014 10:45 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Jenkins, BitBucket and MatLab on Ubuntu


Hello Eric

By a lucky chance i got a picture of the failure, I have attached it to this 
post.

From what I could figure out it seems like you’re right, but I will not be 
able to try what you suggested right now since I’m out of the office. I will 
try it first thing tomorrow.
​

kl. 08:09:40 UTC-6 tirsdag 8. juli 2014 skrev Eric Pyle følgende:
You don't say what the failure is, but I suspect the matlab command may not 
be found. Jenkins is probably running as a different user than you (likely as 
user jenkins), and this user does not have matlab on its path. You could 
address this by either adding the necessary elements to the Jenkins user's 
path, or giving the full path to matlab.

Eric
On 7/8/2014 10:03 AM, Martin Bergene Johansen wrote:
In the ‘Build’ section, add a build step called ‘Execute Shell’.  When this job 
runs, it will create a new (and temporary) directory, drop everything you’re 
pulling out of BitBucket into that directory and the appropriate 
subdirectories, and then run whatever you put in the execute shell step as if 
it was a Bash script.

This part is something I’m struggling with. I don’t know how this script should 
look like.
I have been running

matlab -nodesktop -nosplash -r cd /home/username/matlabScriptLocation; 
someMatlabScript; exit

in the Ubuntu terminal, and I managed to run the script specified in the 
command.
I tried to run the same line in Jenkins but it didn’t work. So it seems that 
I’m doing something wrong.
Also, I will now be running a script from BitBucket rather than a location on 
the machine, so I guess it will require some additional alterations.

I know you said you weren’t familiar with MatLab and BitBucket, but would you 
by any chance have any educated guesses on how this script should look like?
​


kl. 14:34:08 UTC+2 tirsdag 8. juli 2014 skrev Rob Mandeville følgende:
You’ll want to go through the documentation at http://jenkins-ci.org/, clearly.

I’m assuming that you have BitBucket and MatLab (two technologies that I am 
unfamiliar with) on a Ubuntu box.  I’m also assuming that you know BitBucket, 
MatLab, and Ubuntu.  Frankly, I’m not sure what TAP is, so I can’t help you 
there.

You can read how to install Jenkins at 
https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins, in the section 
“Installation”.  Basically, you download jenkins.war (there’s a link on that 
page) and run “java –jar jenkins.war”.  You’ll have a simple Jenkins server on 
port 8080.  If you don’t know how to have that come up every time the machine 
boots, your local sysadmin will know how to make an “init.d script” to make 
that happen.

Via the Web, go to Manage Jenkins-Manage Plugins.  If you only reach the 
internet through a proxy, select the ‘Advanced’ tag and set the HTTP Proxy 
configuration; see your admin as needed.

Select the ‘Available’ tab.  Search for the plugin called ‘Bitbucket 
pullrequest builder plugin’  Click the box to put a checkmark on it, then get 
to the bottom of the page and click ‘Install without restart’.  This should 
install the BitBucket plugin.

Now you’re ready to create a build job.

Get back to the main screen by clicking the word ‘Jenkins’ in the top left hand 
corner (to my knowledge, this always works).  Click ‘New Item’ to create a new 
job.  Give it a name, and select ‘Build a free-style software project’ and you 
will go to the configuration page.

Your first goal here is to just get the matlab job to run.

Go to the ‘Source Code Management’ section and select BitBucket.  I don’t know 
what options it will have, but whatever they are, they should make sense to an 
expert in BitBucket.  Select the options needed.

In the ‘Build’ section, add a build step called ‘Execute Shell’.  When this job 
runs, it will create a new (and temporary) directory, drop everything you’re 
pulling out of BitBucket into that directory and the appropriate 
subdirectories, and then run whatever you put in the execute shell step as if 
it was a Bash script.

Once you have the configuration the way that you want it, click ‘save’ at the 
bottom and you’ll get a page for the job itself.  Click the ‘build’ button (it 
looks like a clock with a ‘Play’ triangle, as you are actually scheduling a 
build).

On the left, there will be a ‘Build history’ section

RE: Want to build Jenkins job every after 15 seconds

2014-07-02 Thread Rob Mandeville
Right, so you have a good reason to launch every 15 seconds from Jenkins.  
Presumably, you want to use the Performance 
Pluginhttps://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin, and 
want it to run every 15 seconds.

So build your Jmeter job, adding a “Trigger builds remotely (e.g., from 
scripts)” trigger.  That will give you a URL to use to call it.

Install a command-line HTTP client, such as curl or wget, where one of your 
build nodes can reach it.

Make a second job that runs on said build node(s), launches every minute, and 
use a shell or windows batch step.

Write a shell script or batch file that:
1: Hits the JMeter job URL via the HTTP client you installed.
2: Sleeps for 15 seconds.
3: hits the JMeter job
4: sleeps
5: hits the JMeter job
6: sleeps
7: hits the JMeter job

This way, even if the job dies somewhere along the way, Jenkins will bring it 
back.  If you truly want to shut it down, disable this job to keep it from 
running.

--Rob



From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Swapnil Pawar
Sent: Wednesday, July 02, 2014 8:23 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Want to build Jenkins job every after 15 seconds

Hi Rob,
1: Do you want each job to launch 15 seconds after the previous one launched, 
or after the previous one finished? - yes..have to laucnh the after previous 
one finished

Context : I am executing the Jmeter scripts after every 15 seconds through the 
Jenkins to check the health of API.


- Swapnil


On Wednesday, 2 July 2014 14:12:27 UTC+5:30, Swapnil Pawar wrote:
Hi,

Can you please tell me How I can schedule Jenkins Job which will execute every 
after 15 seconds.

Regards,
Swapnil
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Click 
herehttps://www.mailcontrol.com/sr/1yf5JAz0DKLGX2PQPOmvUikZGg4PuPFTgg6u5vXcugAP3KUMDva2X7Oahn8PXCwyoyxjTtESlxhMob8Srs06FQ==
 to report this email as spam.


This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: Get build duration using post-build Groovy script

2014-07-02 Thread Rob Mandeville
Install the EnvInject plugin 
(https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin).

In your job, make your first step get the current time in the format you prefer 
and write that out to a file called times.properties.  Here is how in Linux:

touch times.properties # create the file
TIME=date +%s # seconds since epoch
echo START_TIME = ${TIME}  times.properties

After you finish the main job, have your next step write another timestamp to 
times.properties

TIME=date +%s # seconds since epoch
echo END_TIME = ${TIME}  times.properties

Then create an Inject environment variables step (which requires the plugin) 
and load them from times.properties.

Finally, open up another shell step and you will have START_TIME and END_TIME 
as environment variables.  Do the math, et voila!

--Rob

-Original Message-
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of heinst
Sent: Wednesday, July 02, 2014 12:55 PM
To: jenkinsci-users@googlegroups.com
Subject: Get build duration using post-build Groovy script

I have a post build script and am trying to get the build duration. I am trying 
to get it like so:

def build = manager.build
build.duration.toString()

but that just yields 0. Is there a way I can get the build duration using a 
post build groovy script?



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Get-build-duration-using-post-build-Groovy-script-tp4709134.html
Sent from the Jenkins users mailing list archive at Nabble.com.

--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


 Click 
https://www.mailcontrol.com/sr/AeynyPUxbszGX2PQPOmvUikZGg4PuPFTdX0L8fzvSFvPzOIV2M9nacuAsLSybwr0oyxjTtESlxiZDddCOqP2wA==
  to report this email as spam.

This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Can Jenkins forget passwords?

2014-07-01 Thread Rob Mandeville
I'm trying to implement a job that requires each user to enter their own 
credentials.  There is a password parameter, which is all well and good.  But 
if I remember correctly, the Rebuild Plugin allows you to rerun builds with 
password parameters.  This means that Jenkins remembers the password you 
entered in such a way that it can retrieve it later (that is, even if it's 
stored encrypted, it can decrypt it).  More practically, it means that if Joe 
runs a build, I can later run a build as Joe by rebuilding his build, changing 
everything but Joe's username and password.

Is there a way to get Jenkins to completely forget the password you entered 
after it runs the job?

--Rob



This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


OWASP Dependency Check plugin DOA?

2014-06-26 Thread Rob Mandeville
When I am configuring a project and attempt to add a build step, one of the 
choices is Invoke OWASP Dependency-Check analysis.  When I select it, I do 
not get a new build step; nothing happens.

My stack is:
OWASP Dependency-check plugin 1.2.2
Jenkins 1.554 running as Windows service with no separate Web container
Windows 7 Pro SP1

I have not installed any OWASP software for the plugin to connect to; as it 
doesn't refer to one, I am guessing that the logic is in the plugin itself.  If 
I need to install other software, that information would be useful.

Any ideas?

Thanks in advance,

--Rob



This e-mail and the information, including any attachments it contains, are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[xmlsec] Build issues: xmlsec 1.2.8 on mingw32 (xmlsec-ltdl.c)

2006-05-12 Thread Rob Mandeville
I cannot seem to build XMLSec 1.2.8 on my XP Pro box.  The file 
xmlsec-ltdl.c fails to compile, and that stops everything.  I have both 
cygwin and mingw32 installed.  My build script is as follows (run in 
bash, not cmd):


---begin---
make distclean

export CFLAGS=-I/cygdrive/c/MingWStudio/MinGW/include 
-I/cygdrive/c/MingWStudio/MinGW/include/c++/3.4.2
export CCFLAGS=-I/cygdrive/c/MingWStudio/MinGW/include 
-I/cygdrive/c/MingWStudio/MinGW/include/c++/3.4.2
export CPPFLAGS=-I/cygdrive/c/MingWStudio/MinGW/include 
-I/cygdrive/c/MingWStudio/MinGW/include/c++/3.4.2

export LDFLAGS=-L/cygdrive/MingWStudio/MinGW/lib

./configure --prefix=$SR_ROOT --enable-static --disable-shared 
--with-openssl --without-xslt --build=i686-pc-mingw32 
--disable-ltdl-install --disable-ltdl-convenience


make
---end---

SR_ROOT is the name of an environment variable pointing to my system's 
equivalent of /usr/local.


Here is the error part of the log.  Note that if I use make -k, the 
other sources compile; errors are limited to xmlsec-ltdl.c.


---begin---
/bin/sh ../libtool --mode=compile --tag=CC gcc -DHAVE_CONFIG_H -I. -I. 
-I.. -DPACKAGE=\xmlsec1\ -I.. -I../include 
-D__XMLSEC_FUNCTION__=__FUNCTION__ -DXMLSEC_NO_XKMS=1 
-I/usr/include/libxml2 -I/usr/include/libxml2   
-I/cygdrive/c/MingWStudio/MinGW/include 
-I/cygdrive/c/MingWStudio/MinGW/include/c++/3.4.2  
-I/cygdrive/c/MingWStudio/MinGW/include 
-I/cygdrive/c/MingWStudio/MinGW/include/c++/3.4.2 -c -o xmlsec-ltdl.lo 
xmlsec-ltdl.c
gcc -DHAVE_CONFIG_H -I. -I. -I.. -DPACKAGE=\xmlsec1\ -I.. 
-I../include -D__XMLSEC_FUNCTION__=__FUNCTION__ -DXMLSEC_NO_XKMS=1 
-I/usr/include/libxml2 -I/usr/include/libxml2 
-I/cygdrive/c/MingWStudio/MinGW/include 
-I/cygdrive/c/MingWStudio/MinGW/include/c++/3.4.2 
-I/cygdrive/c/MingWStudio/MinGW/include 
-I/cygdrive/c/MingWStudio/MinGW/include/c++/3.4.2 -c xmlsec-ltdl.c -o 
xmlsec-ltdl.o

xmlsec-ltdl.c:168: error: `LTDL_OBJDIR' undeclared here (not in a function)
xmlsec-ltdl.c:254: error: `malloc' undeclared here (not in a function)
xmlsec-ltdl.c:256: error: `free' undeclared here (not in a function)
xmlsec-ltdl.c: In function `find_file':
xmlsec-ltdl.c:1680: warning: assignment discards qualifiers from pointer 
target type

xmlsec-ltdl.c:1730: error: `FILE' undeclared (first use in this function)
xmlsec-ltdl.c:1730: error: (Each undeclared identifier is reported only once
xmlsec-ltdl.c:1730: error: for each function it appears in.)
xmlsec-ltdl.c:1730: error: `file' undeclared (first use in this function)
xmlsec-ltdl.c: In function `xmlsec_lt_dlopen':
xmlsec-ltdl.c:2053: warning: assignment discards qualifiers from pointer 
target type

xmlsec-ltdl.c:2078: error: `FILE' undeclared (first use in this function)
xmlsec-ltdl.c:2078: error: `file' undeclared (first use in this function)
xmlsec-ltdl.c:2121: error: parse error before ')' token
xmlsec-ltdl.c:2124: error: parse error before ')' token
xmlsec-ltdl.c:2238: warning: assignment discards qualifiers from pointer 
target type

xmlsec-ltdl.c:2238: error: `NULL' undeclared (first use in this function)
make[3]: *** [xmlsec-ltdl.lo] Error 1
---end---

All I'm looking for is a static lib.  I explicitly do _not_ want shared 
libraries.  As far as I can tell, xmlsec-ltdl is all about dynamic 
linking, which I don't want in the first place.  But it seems impossible 
to get the static lib without compiling this.


Any ideas, people?  Thanks in advance!

--Rob Mandeville ([EMAIL PROTECTED])

ENTIRE BUILD LOG FOLLOWS


cd c:/devel/surround/xmlsec_1.2.8/
SR_build_cygwin

c:\devel\surround\xmlsec_1.2.8bash SR_build_cygwin.sh
Making distclean in docs
make[1]: Entering directory `/cygdrive/c/devel/surround/xmlsec_1.2.8/docs'
Making distclean in api
File not found - *.c
File not found - *.h
make[2]: Entering directory 
`/cygdrive/c/devel/surround/xmlsec_1.2.8/docs/api'

rm -rf .libs _libs
rm -f *.lo
test -z  || rm -f
rm -f libtool
rm -f Makefile
make[2]: Leaving directory 
`/cygdrive/c/devel/surround/xmlsec_1.2.8/docs/api'

Making distclean in .
make[2]: Entering directory `/cygdrive/c/devel/surround/xmlsec_1.2.8/docs'
rm -rf .libs _libs
rm -f *.lo
test -z  || rm -f
rm -f libtool
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
make[2]: Leaving directory `/cygdrive/c/devel/surround/xmlsec_1.2.8/docs'
rm -f Makefile
make[1]: Leaving directory `/cygdrive/c/devel/surround/xmlsec_1.2.8/docs'
Making distclean in man
make[1]: Entering directory `/cygdrive/c/devel/surround/xmlsec_1.2.8/man'
rm -rf .libs _libs
rm -f *.lo
test -z  || rm -f
rm -f libtool
rm -f Makefile
make[1]: Leaving directory `/cygdrive/c/devel/surround/xmlsec_1.2.8/man'
Making distclean in apps
make[1]: Entering directory `/cygdrive/c/devel/surround/xmlsec_1.2.8/apps'
rm -f xmlsec1.exe xmlsec1
rm -rf .libs _libs
rm -f *.o
rm -f *.lo
rm -f *.tab.c
test -z  || rm -f
rm -f libtool
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
rm -rf ./.deps
rm -f Makefile
make[1]: Leaving directory `/cygdrive/c/devel/surround/xmlsec_1.2.8/apps'
Making distclean in src

[xmlsec] Build errors with xmlsec-openssl.a under SPARC-Solaris

2005-09-30 Thread Rob Mandeville
I've been building xmlsec against openssl, and the library I get always 
comes out unusable.  When I build a program with it later, the linker 
complains about the library and I'm stuck with unfilled references.


Here's the setup:

uname -a = SunOS {machinename} 5.9 Generic_7171-07 sun4u sparc 
SUNW,Ultra-250

gcc version 3.3.6
xmlsec1 version 1.2.8
libxml2 version 2.6.19
openssl version 0.9.7g

options placed to ./configure on xmlsec1: --prefix={dir} 
--with-openssl={dir} --with-libxml={dir} --without-gnutls 
--without-libxslt --enable-static-linking=yes --enable-static=yes 
--enable-shared=no


I've specifically been statically linking everything I can, so I can 
assume as little as possible about the machine I'm deploying this to.


Here's the relevant portion of the gmake -d output:

---BEGIN OUTPUT---
   Must remake target `libxmlsec1-openssl.la'.
/bin/bash ../../libtool --mode=link --tag=CC gcc  -g -O2   -o 
libxmlsec1-openssl.la -rpath /home/robm/devel/local/lib -version-info 
3:8:2  app.lo bn.lo ciphers.lo crypto.lo digests.lo evp.lo hmac.lo 
kw_aes.lo kw_des.lo kt_rsa.lo signatures.lo symkeys.lo x509.lo 
x509vfy.lo  ../libxmlsec1.la /home/robm/devel/local/lib/libcrypto.a  
-L/home/robm/devel/local/lib -R/home/robm/devel/local/lib -lxml2 -lz 
-lpthread -lm -lsocket -lnsl 
Putting child 0x00067498 (libxmlsec1-openssl.la) PID 8349 on the chain.

Live child 0x00067498 (libxmlsec1-openssl.la) PID 8349
mkdir .libs

*** Warning: Linking the shared library libxmlsec1-openssl.la against the
*** static library /home/robm/devel/local/lib/libcrypto.a is not portable!
ar cru .libs/libxmlsec1-openssl.a 
/home/robm/devel/local/lib/libcrypto.a  app.o bn.o ciphers.o crypto.o 
digests.o evp.o hmac.o kw_aes.o kw_des.o kt_rsa.o signatures.o symkeys.o 
x509.o x509vfy.o /home/robm/devel/local/lib/libcrypto.a
ar: /home/robm/devel/local/lib/libcrypto.a is in archive format - 
embedded archives are not allowed
ar: /home/robm/devel/local/lib/libcrypto.a is in archive format - 
embedded archives are not allowed

ranlib .libs/libxmlsec1-openssl.a
creating libxmlsec1-openssl.la
(cd .libs  rm -f libxmlsec1-openssl.la  ln -s 
../libxmlsec1-openssl.la libxmlsec1-openssl.la)

Got a SIGCHLD; 1 unreaped children.
Reaping winning child 0x00067498 PID 8349
Removing child 0x00067498 PID 8349 from chain.


---END OUTPUT---

So why is it tryng to link the entire libcrypto library to the 
libxml-openssl library?  Obviously, Sun's ar can't put archives into 
archives, which is causing the errors and the scrambled library.


I can fix this by removing all references to libxmlsec1-openssl.a from 
the Makefile, but is there a better way than hand-hacking?


Thanks in advance,

--Rob

___
xmlsec mailing list
xmlsec@aleksey.com
http://www.aleksey.com/mailman/listinfo/xmlsec