Kubernetes slaves in parallel

2017-02-01 Thread Lionel Orellana
Hi

I have a pipeline with a podTemaplate definition from the Kubernetes plugin 
to create slaves on Openshift. 

Something like this.

podTemplate(name: 'jenkins-slave', label: 'kube-node',  instanceCap: 4,
containers: [
containerTemplate(
name: 'maven', 
image: "${registry}:5000/jenkins/slave-maven",
command: '/bin/bash',
args: '',
alwaysPullImage: true,
ttyEnabled: true,
envVars: [containerEnvVar(key: 'no_proxy', value: "${noProxy}")]),
containerTemplate(
name: 'oc', 
image: "${registry}:5000/jenkins/slave-oc",
args: 'cat',
alwaysPullImage: true,
ttyEnabled: true,
envVars: [containerEnvVar(key: 'KUBE_TOKEN', value: "${token}")])
])
{
node('kube-node') {
   stage ('Compile') {
   container ('maven') {
}
   }
}
node('kube-node') {
stage ('Unit Tests') {
container('maven') {
}
}
}
node('kube-node') {
stage ('Container Build') {
container('oc') {
}
}
}
}

That works fine and 3 kube-node pods get created one after the other.  But 
I want to parallelise the Unit Tests and the Container Build stages. When I 
move those two nodes into a parallel step they still get created in 
sequence. 

 parallel (
   "Tests": {
   node('kube-node') {
   stage ('Unit Tests') {
   container('maven') {
   }
   }
   }
   },
   "Container": {
   node('kube-node') {
   stage ('Container Build') {
   container('oc') {
   }
   }
   }
   }
)

The console shows both branches waiting for a new pod to be created.


[Pipeline] parallel[Pipeline] [Tests] { (Branch: Tests)[Pipeline] [Container] { 
(Branch: Container)[Pipeline] [Tests] node[Pipeline] [Container] node

[Tests] Still waiting to schedule task
[Tests] All nodes of label ‘kube-node’ are offline
[Container] Still waiting to schedule task
[Container] All nodes of label ‘kube-node’ are offline


At this point one pod is created and one of the branches runs. The branch 
finishes, the pod is terminated, a new pod created and the other branch 
runs. 

I have set -Dhudson.slaves.NodeProvisioner.MARGIN=50 
-Dhudson.slaves.NodeProvisioner.MARGIN0=0.85 in my jenkins startup options 
but made no difference. 

Any ideas how I can parallise these pods? 

Thanks

Lionel



-- 
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/9854d0c9-5a7d-4d1c-be5d-1a6166ae7cb7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Maven configuration in pipeline job

2017-02-01 Thread Irfan Sayed
Hi,
Can you please bit elaborate , what exactly you are looking for ?
may be some example ?


On Wed, Feb 1, 2017 at 11:51 PM, Tejinder Kaur Gill <
tejinder.gill1...@gmail.com> wrote:

> Hi,
>
> I am creating a pipeline job with some maven configurations in it. I want
> module view in it ,the same as we get in maven project job . Is it possible
> to get the same ?
>
> --
> 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/809943fc-bb6d-4ad7-8d5d-e524c0be09ed%40googlegroups.
> 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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CACGLCJYZk34KZtQqWRFKV3x5w%2BEus63RHKnZC9%3DSRvd%3DHV9Gig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Maven configuration in pipeline job

2017-02-01 Thread Tejinder Kaur Gill
Hi,

I am creating a pipeline job with some maven configurations in it. I want 
module view in it ,the same as we get in maven project job . Is it possible 
to get the same ?

-- 
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/809943fc-bb6d-4ad7-8d5d-e524c0be09ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


How to update URL of theme CSS in jenkins via groovy?

2017-02-01 Thread user_dev


down votefavorite 


I am trying to use custom css to change jenkins ui and have added the css 
file in userContent folder and installed 
https://wiki.jenkins-ci.org/display/JENKINS/Simple+Theme+Plugin. I can 
update the URL of theme css by going to configuration page inside jenkins. 
I am trying to automate this via groovy but not getting the right API. Is 
it even possible to do 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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/79afd83c-9d4e-49ad-a455-0584de473c43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: slave 2.52, IBM JVM 1.8, Out of memory at end of build

2017-02-01 Thread Mark Waite
I'd recommend that you use the Oracle JVM instead of the IBM JVM to run the
agent ("slave").  It is deeply tested with Jenkins, and runs very well.

If you need to run individual jobs with the IBM JVM on that agent, you can
configure it as a JVM installation (or with a JVM automatic installer).
That gives you the most tested environment (Oracle JVM) to run your agent,
and still allows you to run jobs using either the Oracle JVM or the IBM JVM.

Mark Waite

On Wed, Feb 1, 2017 at 4:25 PM Mikhail Ramendik  wrote:

> Hello,
>
> I am getting an out of memory error at the end of a build. I have changed
> the build itself to "echo hello world" and I still get the out of memory
> error.
>
> This seems to be connected with the slave host using IBM JVM 1.8 (64-bit),
> as when the Oracle JVM was used this did not happen.
>
> The slave is started using the command: javaws
> http://jenkins.host:8080/computer/node_name/slave-agent.jnlp
>
> The version of the slave is 2.52, according to the manifest file in
> slave.jar. The version of Jenkins is 1.632.
>
> I would appreciate advice about fixing this. The details of the error
> (fromthe console output as visible in Jenkins) follow.
>
> Yours, MIkhail Ramendik
>
> C:\Users\Administrator\SVT_UI_Auto>echo hello world
> hello world
>
> C:\Users\Administrator\SVT_UI_Auto>exit 0
> FATAL: Remote call on SVT_9_42_34_29_Windows_Node failedjava.io.IOException 
> : Remote 
> call on SVT_9_42_34_29_Windows_Node failed
>   at hudson.remoting.Channel.call(Channel.java:786) 
> 
>   at hudson.Launcher$RemoteLauncher.kill(Launcher.java:954) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:543) 
> 
>   at hudson.model.Run.execute(Run.java:1741) 
> 
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
> 
>   at hudson.model.ResourceController.execute(ResourceController.java:98) 
> 
>   at hudson.model.Executor.run(Executor.java:408) 
> 
> Caused by: java.lang.OutOfMemoryError 
> : 
> Java heap space
>   at java.lang.String.(String.java:388) 
> 
>   at java.lang.String.substring(String.java:1372) 
> 
>   at 
> org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:144) 
> 
>   at 
> org.jvnet.winp.WinProcess.getEnvironmentVariables(WinProcess.java:121) 
> 
>   at 
> hudson.util.ProcessTree$Windows$1.getEnvironmentVariables(ProcessTree.java:452)
>  
> 
>   at 
> hudson.util.ProcessTree$OSProcess.hasMatchingEnvVars(ProcessTree.java:276) 
> 
>   at hudson.util.ProcessTree$Windows.killAll(ProcessTree.java:478) 
> 
>   at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:966) 
> 
>   at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:957) 
> 
>   at hudson.remoting.UserRequest.perform(UserRequest.java:121) 
> 
>   at hudson.remoting.UserRequest.perform(UserRequest.java:49) 
> 
>   at hudson.remoting.Request$2.run(Request.java:326) 
> 
>   at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
>  

slave 2.52, IBM JVM 1.8, Out of memory at end of build

2017-02-01 Thread Mikhail Ramendik
Hello,

I am getting an out of memory error at the end of a build. I have changed 
the build itself to "echo hello world" and I still get the out of memory 
error.

This seems to be connected with the slave host using IBM JVM 1.8 (64-bit), 
as when the Oracle JVM was used this did not happen.

The slave is started using the command: javaws 
http://jenkins.host:8080/computer/node_name/slave-agent.jnlp

The version of the slave is 2.52, according to the manifest file in 
slave.jar. The version of Jenkins is 1.632.

I would appreciate advice about fixing this. The details of the error 
(fromthe console output as visible in Jenkins) follow.

Yours, MIkhail Ramendik

C:\Users\Administrator\SVT_UI_Auto>echo hello world 
hello world

C:\Users\Administrator\SVT_UI_Auto>exit 0 
FATAL: Remote call on SVT_9_42_34_29_Windows_Node failedjava.io.IOException 
: Remote 
call on SVT_9_42_34_29_Windows_Node failed
at hudson.remoting.Channel.call(Channel.java:786) 

at hudson.Launcher$RemoteLauncher.kill(Launcher.java:954) 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:543) 

at hudson.model.Run.execute(Run.java:1741) 

at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 

at hudson.model.ResourceController.execute(ResourceController.java:98) 

at hudson.model.Executor.run(Executor.java:408) 

Caused by: java.lang.OutOfMemoryError 
: 
Java heap space
at java.lang.String.(String.java:388) 

at java.lang.String.substring(String.java:1372) 

at 
org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:144) 

at 
org.jvnet.winp.WinProcess.getEnvironmentVariables(WinProcess.java:121) 

at 
hudson.util.ProcessTree$Windows$1.getEnvironmentVariables(ProcessTree.java:452) 

at 
hudson.util.ProcessTree$OSProcess.hasMatchingEnvVars(ProcessTree.java:276) 

at hudson.util.ProcessTree$Windows.killAll(ProcessTree.java:478) 

at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:966) 

at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:957) 

at hudson.remoting.UserRequest.perform(UserRequest.java:121) 

at hudson.remoting.UserRequest.perform(UserRequest.java:49) 

at hudson.remoting.Request$2.run(Request.java:326) 

at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
 

at java.util.concurrent.FutureTask.run(FutureTask.java:277) 

at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) 

at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 

Re: Jenkins Email notification when build fails and include failed scenarios in the email body

2017-02-01 Thread Slide
Please don't double post.

On Wed, Feb 1, 2017 at 3:20 PM siva varma Datla 
wrote:

> I am kind of new to jenkins can someone help me please
>
> my Groovy syntax is
> node {
> echo 'Hello World'
> }
> node {
>
> notifyFailure()
> /* ... existing build steps ... */
> }
>
> def notifyFailure() {
> emailext (
> subject: "FAILURE: Job '${JOB_NAME} [${BUILD_NUMBER}]'",
> body: '''FAILURE: Job '${JOB_NAME} [${BUILD_NUMBER}]':
> Check console output at  href='${BUILD_URL}consoleText'>${JOB_NAME} [${BUILD_NUMBER}]
> ${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished: FAILURE$"}''',
> to: '...@domain.com'
>   )
> }
>
>
> My console o/p is
> Started by user
> [Pipeline] node
> Running on in /ci-build/.jenkins/workspace/
> [Pipeline] {
> [Pipeline] echo
> Hello World
> [Pipeline] }
> [Pipeline] // node
> [Pipeline] node
> Running on /ci-build/.jenkins/workspace/
> [Pipeline] {
> [Pipeline] emailext
> Sending email to: ...@domain.com
> [Pipeline] }
> [Pipeline] // node
> [Pipeline] End of Pipeline
> Finished: SUCCESS
>
>
> *My email notification: *
> *STARTED: Job 'testemail [247]':*
>
> *[Pipeline] } [Pipeline] // node [Pipeline] node Running on SER26VVM323 in
> /ci-build/.jenkins/workspace/ncrtestemail [Pipeline] {*
>
>
> I want an email notification with status and some part of console o/p in
> my email body starting from Hello World to Finished: FAILURE.
>
> Could you please help me to make some changes in that script.
> I appreciate your help
>
> Thanks & 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.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/a5a2962b-bbae-4b87-a00d-fd648386%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVenVg5FCJZBOa%2Bs31VPjSB5sF%2BfRHM6d-4ZoG5f2aDiUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins email notificatiosn for failed build along with failed scenarios in the email body

2017-02-01 Thread Slide
Please don't double post.

On Wed, Feb 1, 2017 at 3:23 PM Indra Gunawan (ingunawa) 
wrote:

> Would you please post once and by the way your question has already been
> answered by the author of the plugin.
>
>
>
> *From: * on behalf of siva varma Datla <
> sivavarma...@gmail.com>
> *Reply-To: *"jenkinsci-users@googlegroups.com" <
> jenkinsci-users@googlegroups.com>
> *Date: *Wednesday, February 1, 2017 at 2:21 PM
> *To: *Jenkins Users 
> *Subject: *Jenkins email notificatiosn for failed build along with failed
> scenarios in the email body
>
>
>
> I am kind of new to jenkins can someone help me please
>
>
>
> my Groovy syntax is
>
> node {
>
> echo 'Hello World'
>
> }
>
> node {
>
>
>
> notifyFailure()
>
> /* ... existing build steps ... */
>
> }
>
>
>
> def notifyFailure() {
>
> emailext (
>
> subject: "FAILURE: Job '${JOB_NAME} [${BUILD_NUMBER}]'",
>
> body: '''FAILURE: Job '${JOB_NAME} [${BUILD_NUMBER}]':
>
> Check console output at  href='${BUILD_URL}consoleText'>${JOB_NAME} [${BUILD_NUMBER}]
>
> ${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished: FAILURE$"}''',
>
> to: '...@domain.com'
>
>   )
>
> }
>
>
>
>
>
> My console o/p is
>
> Started by user
>
> [Pipeline] node
>
> Running on in /ci-build/.jenkins/workspace/
>
> [Pipeline] {
>
> [Pipeline] echo
>
> Hello World
>
> [Pipeline] }
>
> [Pipeline] // node
>
> [Pipeline] node
>
> Running on /ci-build/.jenkins/workspace/
>
> [Pipeline] {
>
> [Pipeline] emailext
>
> Sending email to: ...@domain.com
>
> [Pipeline] }
>
> [Pipeline] // node
>
> [Pipeline] End of Pipeline
>
> Finished: FAILURE
>
>
>
>
>
> My email notification:
>
> STARTED: Job 'testemail [247]':
>
>
>
> [Pipeline] } [Pipeline] // node [Pipeline] node Running on SER26VVM323 in
> /ci-build/.jenkins/workspace/ncrtestemail [Pipeline] {
>
>
>
>
>
> I want an email notification with status and some part of console o/p in
> my email body starting from Hello World to Finished: FAILURE.
>
>
>
> Could you please help me to make some changes in that script.
>
> I appreciate your help
>
>
>
> Thanks & 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.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/cf219fce-0a71-4d35-95b6-71cd958a465e%40googlegroups.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.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/5B46119E-F004-4769-91B5-A38064E3A2DE%40cisco.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVfegb%2BMCCy7kPqEorTha0L6XnE3kkqWtZbFoX2BG2MZew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


M2 Release Plugin https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin

2017-02-01 Thread Jeff Gardner
Hi,
I am trying to use the release plugin and after configuring everything 
there should be a link perform maven release.  The link is not showing for 
my project.  All the configuration stuff is showing but the link is not 
there.  

-- 
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/9c363c89-9588-4072-a575-d7f7645c1900%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins email notificatiosn for failed build along with failed scenarios in the email body

2017-02-01 Thread Indra Gunawan (ingunawa)
Would you please post once and by the way your question has already been 
answered by the author of the plugin.

From:  on behalf of siva varma Datla 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Wednesday, February 1, 2017 at 2:21 PM
To: Jenkins Users 
Subject: Jenkins email notificatiosn for failed build along with failed 
scenarios in the email body

I am kind of new to jenkins can someone help me please

my Groovy syntax is
node {
echo 'Hello World'
}
node {

notifyFailure()
/* ... existing build steps ... */
}

def notifyFailure() {
emailext (
subject: "FAILURE: Job '${JOB_NAME} [${BUILD_NUMBER}]'",
body: '''FAILURE: Job '${JOB_NAME} [${BUILD_NUMBER}]':
Check console output at ${JOB_NAME} 
[${BUILD_NUMBER}]
${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished: FAILURE$"}''',
to: '...@domain.com'
  )
}


My console o/p is
Started by user
[Pipeline] node
Running on in /ci-build/.jenkins/workspace/
[Pipeline] {
[Pipeline] echo
Hello World
[Pipeline] }
[Pipeline] // node
[Pipeline] node
Running on /ci-build/.jenkins/workspace/
[Pipeline] {
[Pipeline] emailext
Sending email to: ...@domain.com
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: FAILURE


My email notification:
STARTED: Job 'testemail [247]':

[Pipeline] } [Pipeline] // node [Pipeline] node Running on SER26VVM323 in 
/ci-build/.jenkins/workspace/ncrtestemail [Pipeline] {


I want an email notification with status and some part of console o/p in my 
email body starting from Hello World to Finished: FAILURE.

Could you please help me to make some changes in that script.
I appreciate your help

Thanks & 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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cf219fce-0a71-4d35-95b6-71cd958a465e%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5B46119E-F004-4769-91B5-A38064E3A2DE%40cisco.com.
For more options, visit https://groups.google.com/d/optout.


Re: $JENKINS_HOME vs. $WORKSPACE on a slave (agent) node vs master node

2017-02-01 Thread Indra Gunawan (ingunawa)
Yes, that is the expected behavior.  JENKINS_HOME only matters on Jenkins 
master. JENKINS_HOME is the path where all metadata of Jenkins instance like 
plugins, jobs are stored.  It is not a variable for slave.
Are you the Jenkins admin such that you have administration permission on the 
Jenkins UI?

Why don’t you define an environment variable with different name in the Manage 
Jenkins -> Configure System.  This env variable is then available to all jobs 
regardless where the job is running.

From:  on behalf of Bruce Epstein 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Wednesday, February 1, 2017 at 1:48 PM
To: Jenkins Users 
Subject: $JENKINS_HOME vs. $WORKSPACE on a slave (agent) node vs master node

Hi Everyone -

I have one master and one slave node.

I am trying to move some Jenkins jobs that currently run on the master to 
instead run on the slave.

For various reasons, I need (or at least want) to use the $JENKINS_HOME env 
variable in my scripts, but it returns the value of the master jenkins 
localtion, even when running a job on the slave.

On the master node, $JENKINS_HOME  is /opt/apache-tomcat-7.0.54/webapps/jenkins

On the slave node, $JENKINS_HOME should be /opt/jenkins, but is being returned 
as the master's value ( /opt/apache-tomcat-7.0.54/webapps/jenkins)

For now, the best I have been able to do is climb up the directory hierarchy, 
using something like:

$WORKSPACE/../../../..

So $WORKSPACE is returning the workspace location correctly on the slave, but 
$JENKINS_HOME is returning the jenkins installation folder on the master.

Is this the expected behavior?

Is there another env variable I should be using?

Regardless, I have hundreds of Jenkins jobs, and tweaking them all will be 
painful if I can't simply modify $JENKINS_HOME on which they currently rely.

I think it is an IT configuration issue, because they say that when they echo 
$JENKINS_HOME it gives the expected value on the slave node, as follows:



[jenkins@builder01-slave01 ~]$ echo $JENKINS_HOME



/opt/jenkins



Maybe the Jenkins process was started as "root" and not as the "jenkins" user, 
and they've defined $JENKINS_HOME for the wrong user?

If it is an IT-related configuration and not a Jenkins thing, please give 
advice and I'll rely it onto the IT dept, who control the server config.


Thanks in advance
Cheers
Bruce
--
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/502de496-603d-4c3f-935a-a723c0821e6b%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4FD0804E-C393-4F0C-BA61-431687833367%40cisco.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins email notificatiosn for failed build along with failed scenarios in the email body

2017-02-01 Thread siva varma Datla
I am kind of new to jenkins can someone help me please

my Groovy syntax is 
node { 
echo 'Hello World' 
} 
node { 

notifyFailure() 
/* ... existing build steps ... */ 
} 

def notifyFailure() { 
emailext ( 
subject: "FAILURE: Job '${JOB_NAME} [${BUILD_NUMBER}]'", 
body: '''FAILURE: Job '${JOB_NAME} [${BUILD_NUMBER}]':
Check console output at ${JOB_NAME} [${BUILD_NUMBER}]
${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished: FAILURE$"}''',
to: '...@domain.com' 
  ) 
}


My console o/p is 
Started by user 
[Pipeline] node
Running on in /ci-build/.jenkins/workspace/
[Pipeline] {
[Pipeline] echo
Hello World
[Pipeline] }
[Pipeline] // node
[Pipeline] node
Running on /ci-build/.jenkins/workspace/
[Pipeline] {
[Pipeline] emailext
Sending email to: ...@domain.com
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: FAILURE


My email notification: 
STARTED: Job 'testemail [247]':

[Pipeline] } [Pipeline] // node [Pipeline] node Running on SER26VVM323 in 
/ci-build/.jenkins/workspace/ncrtestemail [Pipeline] {


I want an email notification with status and some part of console o/p in my 
email body starting from Hello World to Finished: FAILURE.

Could you please help me to make some changes in that script.
I appreciate your help 

Thanks & 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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cf219fce-0a71-4d35-95b6-71cd958a465e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins Email notification when build fails and include failed scenarios in the email body

2017-02-01 Thread siva varma Datla
I am kind of new to jenkins can someone help me please

my Groovy syntax is 
node { 
echo 'Hello World' 
} 
node { 

notifyFailure() 
/* ... existing build steps ... */ 
} 

def notifyFailure() { 
emailext ( 
subject: "FAILURE: Job '${JOB_NAME} [${BUILD_NUMBER}]'", 
body: '''FAILURE: Job '${JOB_NAME} [${BUILD_NUMBER}]':
Check console output at ${JOB_NAME} [${BUILD_NUMBER}]
${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished: FAILURE$"}''',
to: '...@domain.com' 
  ) 
}


My console o/p is 
Started by user 
[Pipeline] node
Running on in /ci-build/.jenkins/workspace/
[Pipeline] {
[Pipeline] echo
Hello World
[Pipeline] }
[Pipeline] // node
[Pipeline] node
Running on /ci-build/.jenkins/workspace/
[Pipeline] {
[Pipeline] emailext
Sending email to: ...@domain.com
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS


*My email notification: *
*STARTED: Job 'testemail [247]':*

*[Pipeline] } [Pipeline] // node [Pipeline] node Running on SER26VVM323 in 
/ci-build/.jenkins/workspace/ncrtestemail [Pipeline] {*


I want an email notification with status and some part of console o/p in my 
email body starting from Hello World to Finished: FAILURE.

Could you please help me to make some changes in that script.
I appreciate your help 

Thanks & 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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a5a2962b-bbae-4b87-a00d-fd648386%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Any pointers on docs for using Jenkins to control remote jobs on various machines, non-java.

2017-02-01 Thread tarocaravan
Pipelines really help in coordinating multiple tasks to be run on multiple 
hosts, sequentially and even concurrently. Have you considered this? The 
old Jenkins way of define multijobs would be cumbersome so I suggest 
looking into pipelines. Another option is something like ansible, though in 
practice Jenkins fits the model of CI better.

T

On Tuesday, January 31, 2017 at 4:07:07 PM UTC-8, Rusty Carruth wrote:
>
> So, I'm just looking at Jenkins as a 'controller' for our test scripts.  
> I've tried to find some kind of pointers to how to do this, and I do have a 
> few ideas, but was hoping I could find some documentation on setting up 
> things as below, (yes, I know that I can use ssh or the server on the test 
> host (defined below) to start jobs - indeed I've done that, but the more 
> important thing is 
>
> First, the environment/current process:
>
> We have a Windows-based build machine, 15 linux/FreeDOS-based test hosts, 
> a linux-only test host, a linux/Windows test host, and a linux-only OakGate 
> test host.
>
> Every day (or more often) a build is run on the windows-based build 
> machine.
>
> When the build is finished, the 'products' of the build are placed in a 
> new directory on a Linux machine (for now, we'll call it 'client').
>
> Cron jobs are running which detect this and initiate an arbitrary number 
> of tests on up to 17 (more or less) of the above 'test hosts'.  This is 
> done via a (bash) shell script, using a configuration file that can specify 
> the configuration file for each test host (the configuration file for each 
> test host could be different per host, or all the same, or whatever).  This 
> startup script does many things, including commanding the serial port 
> programs (a modified minicom) running on any one of a number of machines to 
> begin saving serial port data to a log file (among other things that the 
> bash script can and does do).
>
> This startup bash shell script will initiate (via ssh) a command on each 
> test host (as configured above) to begin the test.  The host(s) will then 
> proceed with the test, as configured, until the test ends.
>
> At the time the test ends, a script will be run on the Linux-booted test 
> host to upload results back to the initial linux machine ('client', above) 
> and create a report (and mail it, and lots of other stuff, including 
> database updates, etc).
>
> When booting into Linux, the test host detects that a test was in process 
> and checks to see if any 'post-DOS' tests need to be run, and if so runs 
> them.
>
> Once all that is done, the test host will then run a script which copies 
> the results over to 'client', creates reports, including an email report, 
> emails it, updates databases, etc.
>
> Right now, it all works fine.  However, as is often the case, we want to 
> 'improve' it.
>
> Here's what we want to change to:
>
> The test host must be running Linux before a test is initiated on it 
> (trying to use FreeDOS to copy files via the network was a total disaster, 
> so we have to do all network operations in Linux)
>
> We plan to allow the test designer to group arbitrary tests together into 
> a 'supertest' (the requirement is that they all have to be under the same 
> OS) to be run as one.
>
> The test overseer program can then be configured to run any number of 
> sequentially-executed invocations of these sets of tests ('supertests' 
> above)  as the user wants, so that you could run a bunch of Linux tests 
> (together in one batch), followed by a bunch of FreeDOS tests (again, as a 
> single batch), followed by a bunch of Linux tests, etc.
>
> IF the test host is to run the test under an OS other than Linux, the 
> configuration file specified to the initial bash shell script mentioned 
> above is used to configure the test.  The test host will complete the test 
> as specified and then reboot to Linux.
>
> One other 'minor' variation - we can also do a 'manual' run, which 
> basically means that the user must cause the Linux host to reboot (at which 
> point it will boot into FreeDOS - allowing the user to (using an IPKVM) 
> control the test manually if desired). When booting out of FreeDOS it will 
> return to Linux, but NOT 'detect that a test was in process' and run 
> 'finish').
>
> What we would like to do is remove the 'flowchart' of 
> linux/dos/linux/done.  We may wish to boot linux/dos/linux/dos/linux/done, 
> or perhaps even boot various versions of linux (yeah, not likely, but I had 
> to come up with something besides toggling between linux and dos!)
>
> We also want to be able to abort a test group at the first possible moment 
> (under FreeDOS the only possible moment is when the tests are finished, of 
> course).
>
> Also, we'd like to set some test hosts to repeatedly run tests over and 
> over again, regardless of the build machine's finishing.  Possibly with 
> changes in the test configuration.
>
> Note that there are 18-ish test hosts, with up to 4 or 5 people wanting 

Jenkins Email notification when build fails and include failed scenarios in the email body

2017-02-01 Thread siva varma Datla
I am kind of new to jenkins can someone help me please

my Groovy syntax is 
node { 
echo 'Hello World' 
} 
node { 

notifyFailure() 
/* ... existing build steps ... */ 
} 

def notifyFailure() { 
emailext ( 
subject: "FAILURE: Job '${JOB_NAME} [${BUILD_NUMBER}]'", 
body: '''FAILURE: Job '${JOB_NAME} [${BUILD_NUMBER}]':
Check console output at ${JOB_NAME} [${BUILD_NUMBER}]
${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished: FAILURE$"}''',
to: 'xx...@gmail.com ' 
  ) 
}


My console o/p is 

Started by user [Pipeline] nodeRunning on in 
/ci-build/.jenkins/workspace/[Pipeline] {[Pipeline] echoHello World[Pipeline] 
}[Pipeline] // node[Pipeline] nodeRunning on 
/ci-build/.jenkins/workspace/[Pipeline] {[Pipeline] emailextSending email to: 
xx...@gmail.com [Pipeline] }[Pipeline] // 
node[Pipeline] End of PipelineFinished: SUCCESS



*My email notification: *

*STARTED: Job 'testemail [247]':*

*[Pipeline] } [Pipeline] // node [Pipeline] node Running on SER26VVM323 in 
/ci-build/.jenkins/workspace/ncrtestemail [Pipeline] {*


I want an email notification with status and some part of console o/p in my 
email body starting from Hello World to Finished: FAILURE.


Could you please help me to make some changes in that script.

I appreciate your help 


Thanks & 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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/51771770-aff6-4f01-b88b-ba246c59e2c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Deploying a file on a remote location

2017-02-01 Thread Victor Martinez
Besides of that, there are some other threads about some permissions issues 
when using the same plugin:
- 
https://groups.google.com/forum/#!searchin/jenkinsci-users/ArtifactDeployer%7Csort:relevance

I hope it helps

On Wednesday, 1 February 2017 21:51:39 UTC, Victor Martinez wrote:
>
> Can you confirm whether the Jenkins user got write privileges where those 
> files should be copied to? There are some limitations according to the wiki 
> page:
> - https://wiki.jenkins-ci.org/display/JENKINS/ArtifactDeployer+Plugin
>
> On Wednesday, 1 February 2017 12:03:45 UTC, gaurav lele wrote:
>>
>> I am using the ArtifactDeployer plugin to deploy files onto a remote 
>> location. But I am getting these errors.
>>  [ArtifactDeployer] - [ERROR] -  Failed to deploy. Can't create the 
>> directory '53'
>>  [ArtifactDeployer] - [ERROR] - Failed to mkdirs
>>
>> And also how do I create permissions in Jenkins to write files?
>> I have checked the global security but coulndt find any option
>> Please let me know a solution.
>>
>

-- 
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/fc94096e-5677-4572-89d1-253382a09509%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Deploying a file on a remote location

2017-02-01 Thread Victor Martinez
Can you confirm whether the Jenkins user got write privileges where those 
files should be copied to? There are some limitations according to the wiki 
page:
- https://wiki.jenkins-ci.org/display/JENKINS/ArtifactDeployer+Plugin

On Wednesday, 1 February 2017 12:03:45 UTC, gaurav lele wrote:
>
> I am using the ArtifactDeployer plugin to deploy files onto a remote 
> location. But I am getting these errors.
>  [ArtifactDeployer] - [ERROR] -  Failed to deploy. Can't create the 
> directory '53'
>  [ArtifactDeployer] - [ERROR] - Failed to mkdirs
>
> And also how do I create permissions in Jenkins to write files?
> I have checked the global security but coulndt find any option
> Please let me know a solution.
>

-- 
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/a7414a4e-43b6-423f-9a7f-377e69a16f1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


$JENKINS_HOME vs. $WORKSPACE on a slave (agent) node vs master node

2017-02-01 Thread Bruce Epstein
Hi Everyone -

I have one master and one slave node.

I am trying to move some Jenkins jobs that currently run on the master to 
instead run on the slave.

For various reasons, I need (or at least want) to use the $JENKINS_HOME env 
variable in my scripts, but it returns the value of the master jenkins 
localtion, even when running a job on the slave.

On the master node, $JENKINS_HOME  is 
/opt/apache-tomcat-7.0.54/webapps/jenkins

On the slave node, $JENKINS_HOME should be /opt/jenkins, but is being 
returned as the master's value ( /opt/apache-tomcat-7.0.54/webapps/jenkins)

For now, the best I have been able to do is climb up the directory 
hierarchy, using something like:

$WORKSPACE/../../../..

So $WORKSPACE is returning the workspace location correctly on the slave, 
but $JENKINS_HOME is returning the jenkins installation folder on the 
master.

Is this the expected behavior?

Is there another env variable I should be using?

Regardless, I have hundreds of Jenkins jobs, and tweaking them all will be 
painful if I can't simply modify $JENKINS_HOME on which they currently rely.

I think it is an IT configuration issue, because they say that when they 
echo $JENKINS_HOME it gives the expected value on the slave node, as 
follows:

[jenkins@builder01-slave01 ~]$ echo $JENKINS_HOME


/opt/jenkins

 

Maybe the Jenkins process was started as "root" and not as the "jenkins" 
user, and they've defined $JENKINS_HOME for the wrong user?

If it is an IT-related configuration and not a Jenkins thing, please give 
advice and I'll rely it onto the IT dept, who control the server config.


Thanks in advance 
Cheers
Bruce

-- 
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/502de496-603d-4c3f-935a-a723c0821e6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Email notifications attach part of build log in email body

2017-02-01 Thread Slide
You could echo out something that isn't valuable, just a marker at the
beginning and end and use those as the start/end parameter.

On Wed, Feb 1, 2017 at 2:21 PM siva varma Datla 
wrote:

> Is there any option that I can include that particular part of the build
> in the email body??
>
>
> On Wednesday, February 1, 2017 at 4:04:15 PM UTC-5, slide wrote:
>
> That's how BUILD_LOG_EXCERPT works. It will include only what is between
> the start and end.
>
> On Wed, Feb 1, 2017 at 1:50 PM siva varma Datla 
> wrote:
>
> I am running a jenkins build where I need an email notification whenever
> the build fails I am using Groovy syntax to run my jenkins build I want an
> email with the status of the build along with the some part of log in the
> body of the build.
> *Please find the syntax below and suggest me if have to make any changes
> to make it work.*
> *using this all I can get is the part in between Hello and Finished but I
> want it  starting from Hello and End at Finish.*
>
> *Groovy Syntax*
>
> node {
> echo 'Hello World'
> }
> node {
>
> notifyFailed()
> /* ... existing build steps ... */
> }
>
> def notifyFailed() {
> emailext (
> subject: "FAILED: Job '${JOB_NAME} [${BUILD_NUMBER}]'",
> body: '''FAILED: Job '${JOB_NAME} [${BUILD_NUMBER}]':
> Check console output at  href='${BUILD_URL}consoleText'>${JOB_NAME} [${BUILD_NUMBER}]
> ${BUILD_LOG_EXCERPT, start="^Hello", end="^Finished"}''',
>
> to: 'xx...@domain.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-use...@googlegroups.com.
>
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/dcff97cf-47d3-4caf-9745-11985be0a757%40googlegroups.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.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/8f67af8f-fea7-494a-bebc-8f3bfc650df0%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVdCg-ZnKXL9BqMTtvoJMgVgdxSqX6Y7s1jEeGS1Ds5xGA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Email notifications attach part of build log in email body

2017-02-01 Thread siva varma Datla
Is there any option that I can include that particular part of the build in 
the email body??

On Wednesday, February 1, 2017 at 4:04:15 PM UTC-5, slide wrote:
>
> That's how BUILD_LOG_EXCERPT works. It will include only what is between 
> the start and end.
>
> On Wed, Feb 1, 2017 at 1:50 PM siva varma Datla  > wrote:
>
>> I am running a jenkins build where I need an email notification whenever 
>> the build fails I am using Groovy syntax to run my jenkins build I want an 
>> email with the status of the build along with the some part of log in the 
>> body of the build.
>> *Please find the syntax below and suggest me if have to make any changes 
>> to make it work.*
>> *using this all I can get is the part in between Hello and Finished but I 
>> want it  starting from Hello and End at Finish.*
>>
>> *Groovy Syntax*
>>
>> node { 
>> echo 'Hello World' 
>> } 
>> node { 
>>
>> notifyFailed() 
>> /* ... existing build steps ... */ 
>> } 
>>
>> def notifyFailed() { 
>> emailext ( 
>> subject: "FAILED: Job '${JOB_NAME} [${BUILD_NUMBER}]'", 
>> body: '''FAILED: Job '${JOB_NAME} [${BUILD_NUMBER}]':
>> Check console output at > href='${BUILD_URL}consoleText'>${JOB_NAME} [${BUILD_NUMBER}]
>> ${BUILD_LOG_EXCERPT, start="^Hello", end="^Finished"}''',
>> to: 'xx...@domain.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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/dcff97cf-47d3-4caf-9745-11985be0a757%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8f67af8f-fea7-494a-bebc-8f3bfc650df0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Email notifications attach part of build log in email body

2017-02-01 Thread Slide
That's how BUILD_LOG_EXCERPT works. It will include only what is between
the start and end.

On Wed, Feb 1, 2017 at 1:50 PM siva varma Datla 
wrote:

> I am running a jenkins build where I need an email notification whenever
> the build fails I am using Groovy syntax to run my jenkins build I want an
> email with the status of the build along with the some part of log in the
> body of the build.
> *Please find the syntax below and suggest me if have to make any changes
> to make it work.*
> *using this all I can get is the part in between Hello and Finished but I
> want it  starting from Hello and End at Finish.*
>
> *Groovy Syntax*
>
> node {
> echo 'Hello World'
> }
> node {
>
> notifyFailed()
> /* ... existing build steps ... */
> }
>
> def notifyFailed() {
> emailext (
> subject: "FAILED: Job '${JOB_NAME} [${BUILD_NUMBER}]'",
> body: '''FAILED: Job '${JOB_NAME} [${BUILD_NUMBER}]':
> Check console output at  href='${BUILD_URL}consoleText'>${JOB_NAME} [${BUILD_NUMBER}]
> ${BUILD_LOG_EXCERPT, start="^Hello", end="^Finished"}''',
> to: 'xx...@domain.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/dcff97cf-47d3-4caf-9745-11985be0a757%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVcp9a_q7MGy%2BZYLMw9JiSR7T4UV8jGptq5ZRbGDQww5bA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Email notifications attach part of build log in email body

2017-02-01 Thread siva varma Datla
I am running a jenkins build where I need an email notification whenever 
the build fails I am using Groovy syntax to run my jenkins build I want an 
email with the status of the build along with the some part of log in the 
body of the build.
*Please find the syntax below and suggest me if have to make any changes to 
make it work.*
*using this all I can get is the part in between Hello and Finished but I 
want it  starting from Hello and End at Finish.*

*Groovy Syntax*

node { 
echo 'Hello World' 
} 
node { 

notifyFailed() 
/* ... existing build steps ... */ 
} 

def notifyFailed() { 
emailext ( 
subject: "FAILED: Job '${JOB_NAME} [${BUILD_NUMBER}]'", 
body: '''FAILED: Job '${JOB_NAME} [${BUILD_NUMBER}]':
Check console output at ${JOB_NAME} [${BUILD_NUMBER}]
${BUILD_LOG_EXCERPT, start="^Hello", end="^Finished"}''',
to: 'xx...@domain.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/dcff97cf-47d3-4caf-9745-11985be0a757%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How do I configure redis server in jenkins?

2017-02-01 Thread Indra Gunawan (ingunawa)
Your question is too vague.  If you are using pipeline, you use “sh” step to 
run the bash Shell script file to start and stop redis service or simply run 
the redis docker container.


From:  on behalf of Lavanya pujari 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Wednesday, February 1, 2017 at 9:36 AM
To: Jenkins Users 
Subject: How do I configure redis server in jenkins?

I am trying to integrate Jenkins with node.js application where I need to add 
redis server in the job.

Any help would be thankful..
--
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/d2f832c4-3175-44ba-8096-77d1faf9a0bc%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/B7269E94-8C0D-4649-9EB7-3B8E5B83C8D0%40cisco.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins Email-ext help - accessing build log in email

2017-02-01 Thread Slide
body : """..."""

You are using double quotes...use single quotes

body : '''...'''

On Wed, Feb 1, 2017 at 11:03 AM siva varma Datla 
wrote:

> I am attaching the whole groovy Syntax I am using to get an email
> notification when build is started I also want to include some part of
> console log starting from Hello World to Finished Success.
>
> When I try with single quotes I end up this
> ERROR:
>
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup 
> failed:
> WorkflowScript: 17: unexpected token: BUILD_LOG_EXCERPT @ line 17, column 12.
> '${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished: 
> SUCCESS"}'""",
>
>
>
>
> GROOVY SYNTAX
>
>
> node {
>echo 'Hello World'
> }
> node {
>
>   notifyStarted()
>
>   /* ... existing build steps ... */
> }
>
> properties = ([data])
> def notifyStarted() {
>emailext (
>   subject: "STARTED: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]'",
>   body: """STARTED: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]':
>  Check console output at  href='${env.BUILD_URL}consoleText'>${env.JOB_NAME}
> [${env.BUILD_NUMBER}]""",
>  '${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished:
> SUCCESS"}'
>  to: 'sivaverma.da...@ncr.com'
> )
> }
>
>
>
>
> On Wednesday, February 1, 2017 at 12:48:47 PM UTC-5, slide wrote:
>
> Use single quotes instead of double quotes, I don't know how else to say
> it.
>
> On Wed, Feb 1, 2017 at 10:32 AM siva varma Datla 
> wrote:
>
> Can you provide me with an example please!!
> I would appreciate it if you do so
>
>
> On Wednesday, February 1, 2017 at 11:40:04 AM UTC-5, slide wrote:
>
> If you are including this in a pipeline script, you need to make sure and
> use single quotes or escape the $. Groovy will try and evaluate that if you
> use double quotes.
>
> On Wed, Feb 1, 2017 at 9:20 AM Ghazi TRIKI  wrote:
>
> Hello,
>
> I am helping Siva on a Jenkins build task. We wrote a pipeline email
> function that get log and puts it to email. The issue we have is that we
> tried using BUILD_LOG_EXCERPT and BUILD_LOG variables but get the following
> exception. Can you help us please?
>
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
> failed:
> WorkflowScript: 17: unexpected token: BUILD_LOG_EXCERPT @ line 17, column
> 11.
>  ${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished:
> SUCCESS"}""",
>
> --
> 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.com.
>
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/aa987e90-2a58-4909-88fc-2773f666d0a2%40googlegroups.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-use...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1246470b-2b92-455f-ba62-e3996aed8825%40googlegroups.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.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/07479b01-44b0-44c3-ae0c-f430857c3999%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVeOGjBJxOBRHzKn60_RzEhgMyBsW5%3Ds5xTixC7P3Km1rw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins Email-ext help - accessing build log in email

2017-02-01 Thread siva varma Datla
I am attaching the whole groovy Syntax I am using to get an email 
notification when build is started I also want to include some part of 
console log starting from Hello World to Finished Success.

When I try with single quotes I end up this 
ERROR:

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 17: unexpected token: BUILD_LOG_EXCERPT @ line 17, column 12.
  '${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished: 
SUCCESS"}'""",




GROOVY SYNTAX


node {
   echo 'Hello World'
}
node {

  notifyStarted()

  /* ... existing build steps ... */
}

properties = ([data])
def notifyStarted() {
   emailext (
  subject: "STARTED: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]'",
  body: """STARTED: Job '${env.JOB_NAME} [${env.BUILD_NUMBER}]':
 Check console output at ${env.JOB_NAME} 
[${env.BUILD_NUMBER}]""",
 '${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished: 
SUCCESS"}'
 to: 'sivaverma.da...@ncr.com'
)
}




On Wednesday, February 1, 2017 at 12:48:47 PM UTC-5, slide wrote:
>
> Use single quotes instead of double quotes, I don't know how else to say 
> it.
>
> On Wed, Feb 1, 2017 at 10:32 AM siva varma Datla  > wrote:
>
>> Can you provide me with an example please!!
>> I would appreciate it if you do so
>>
>>
>> On Wednesday, February 1, 2017 at 11:40:04 AM UTC-5, slide wrote:
>>
>>> If you are including this in a pipeline script, you need to make sure 
>>> and use single quotes or escape the $. Groovy will try and evaluate that if 
>>> you use double quotes.
>>>
>>> On Wed, Feb 1, 2017 at 9:20 AM Ghazi TRIKI  wrote:
>>>
>> Hello,

 I am helping Siva on a Jenkins build task. We wrote a pipeline email 
 function that get log and puts it to email. The issue we have is that we 
 tried using BUILD_LOG_EXCERPT and BUILD_LOG variables but get the 
 following 
 exception. Can you help us please?

 org.codehaus.groovy.control.MultipleCompilationErrorsException: startup 
 failed:
 WorkflowScript: 17: unexpected token: BUILD_LOG_EXCERPT @ line 17, 
 column 11.
  ${BUILD_LOG_EXCERPT, start="^Hello World", 
 end="^Finished: SUCCESS"}""",

 -- 
 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.com.
>>>
>>>
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/aa987e90-2a58-4909-88fc-2773f666d0a2%40googlegroups.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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/1246470b-2b92-455f-ba62-e3996aed8825%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/07479b01-44b0-44c3-ae0c-f430857c3999%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins Email-ext help - accessing build log in email

2017-02-01 Thread Slide
Use single quotes instead of double quotes, I don't know how else to say it.

On Wed, Feb 1, 2017 at 10:32 AM siva varma Datla 
wrote:

> Can you provide me with an example please!!
> I would appreciate it if you do so
>
>
> On Wednesday, February 1, 2017 at 11:40:04 AM UTC-5, slide wrote:
>
> If you are including this in a pipeline script, you need to make sure and
> use single quotes or escape the $. Groovy will try and evaluate that if you
> use double quotes.
>
> On Wed, Feb 1, 2017 at 9:20 AM Ghazi TRIKI  wrote:
>
> Hello,
>
> I am helping Siva on a Jenkins build task. We wrote a pipeline email
> function that get log and puts it to email. The issue we have is that we
> tried using BUILD_LOG_EXCERPT and BUILD_LOG variables but get the following
> exception. Can you help us please?
>
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
> failed:
> WorkflowScript: 17: unexpected token: BUILD_LOG_EXCERPT @ line 17, column
> 11.
>  ${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished:
> SUCCESS"}""",
>
> --
> 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.com.
>
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/aa987e90-2a58-4909-88fc-2773f666d0a2%40googlegroups.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.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1246470b-2b92-455f-ba62-e3996aed8825%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVd_kPb7v1j_uVQEo0_nYyo12YW5ef1va-bSRv6XEBDBWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


How do I configure redis server in jenkins?

2017-02-01 Thread Lavanya pujari
I am trying to integrate Jenkins with node.js application where I need to 
add redis server in the job. 

Any help would be thankful..

-- 
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/d2f832c4-3175-44ba-8096-77d1faf9a0bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins Email-ext help - accessing build log in email

2017-02-01 Thread siva varma Datla
Can you provide me with an example please!!
I would appreciate it if you do so

On Wednesday, February 1, 2017 at 11:40:04 AM UTC-5, slide wrote:
>
> If you are including this in a pipeline script, you need to make sure and 
> use single quotes or escape the $. Groovy will try and evaluate that if you 
> use double quotes.
>
> On Wed, Feb 1, 2017 at 9:20 AM Ghazi TRIKI  > wrote:
>
>> Hello,
>>
>> I am helping Siva on a Jenkins build task. We wrote a pipeline email 
>> function that get log and puts it to email. The issue we have is that we 
>> tried using BUILD_LOG_EXCERPT and BUILD_LOG variables but get the following 
>> exception. Can you help us please?
>>
>> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup 
>> failed:
>> WorkflowScript: 17: unexpected token: BUILD_LOG_EXCERPT @ line 17, column 
>> 11.
>>  ${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished: 
>> SUCCESS"}""",
>>
>> -- 
>> 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.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/aa987e90-2a58-4909-88fc-2773f666d0a2%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1246470b-2b92-455f-ba62-e3996aed8825%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins Email-ext help - accessing build log in email

2017-02-01 Thread Ghazi TRIKI
Can you please give an example of what we need to use?

Le mercredi 1 février 2017 17:40:04 UTC+1, slide a écrit :
>
> If you are including this in a pipeline script, you need to make sure and 
> use single quotes or escape the $. Groovy will try and evaluate that if you 
> use double quotes.
>
> On Wed, Feb 1, 2017 at 9:20 AM Ghazi TRIKI  > wrote:
>
>> Hello,
>>
>> I am helping Siva on a Jenkins build task. We wrote a pipeline email 
>> function that get log and puts it to email. The issue we have is that we 
>> tried using BUILD_LOG_EXCERPT and BUILD_LOG variables but get the following 
>> exception. Can you help us please?
>>
>> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup 
>> failed:
>> WorkflowScript: 17: unexpected token: BUILD_LOG_EXCERPT @ line 17, column 
>> 11.
>>  ${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished: 
>> SUCCESS"}""",
>>
>> -- 
>> 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.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/aa987e90-2a58-4909-88fc-2773f666d0a2%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5e53371f-e4d2-415f-aa7d-14b2de2d6071%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: What is the proper name for "ghost" jobs and how are they controlled?

2017-02-01 Thread John Bobinyec
The apparent interference might have been due to other things.

But does no one else have ghosts?

jb

On Thursday, January 26, 2017 at 3:27:12 PM UTC-5, John Bobinyec wrote:
>
>
> We have a pool of slaves.  When a job is dispatched to one of them it is 
> assigned to an executor on that machine.  Oftentimes there is a very 
> similar job running on another machine but it's not assigned to an 
> executor.  I call these ghosts.  What do they do?  How are they 
> dispatched?  It seems like they interfere with the jobs which are supposed 
> to be running on that machine, because real jobs which are destined for 
> that machine get queued up.
>
> Thanks,
> jb
>

-- 
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/335ed9c7-ea23-4eec-9ceb-0b75cfcc4fe2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Email complete build report when build fails

2017-02-01 Thread jerome
You can set a variable global and set it during various step/stage. Then 
when you throw you could known what was the last thing done and append it 
to the email info with the error info too

def my_last_seen_step = "start"
try
{
stage('Checkout') 
  {
  my_last_seen_step = 'checkout begin'
   ...
my_last_seen_step = 'checkout end'
 }
  stage('Build') 
 {
  my_last_seen_step = 'build begin'
  ...
my_last_seen_step = 'build end'
}
}
catch(any)
{
  notifyFailed(my_last_seen_step, any);
}

This is not the best approche, just an easy one, a scope object would be 
better suited for this like the stage() {}. WOuld be nice to have the last 
seen stage or the seen stages list somehow.

-- 
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/723d1b08-92e4-46d2-80c0-1d2b331a6d06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Post build plugin's to run on slave

2017-02-01 Thread Richard Ginga
check out this plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Any+Build+Step+Plugin

On Wed, Feb 1, 2017 at 1:53 AM, Vikram Varma 
wrote:

>
>
> I have a packer installed on my Slave machine. But I am having issue that
> Packer Jenkins plugin is a post build action. But I need this to run on my
> slave machine after my build is completed. Is there any way I could get my
> Packer Jenkins Plugin can run on my slave machine? I don’t want this to run
> on my Master
>
>
>
> 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.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/a2926f8a-1c97-45f0-bb41-a7f31d0f8098%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Dick Ginga
Build Engineer
rgi...@disruptorbeam.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAL3PpaX_gG_7KgXaG4j2Z2zbknGuZX_thkRopKj3ws%3DwHfnHUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins Email-ext help - accessing build log in email

2017-02-01 Thread Slide
If you are including this in a pipeline script, you need to make sure and
use single quotes or escape the $. Groovy will try and evaluate that if you
use double quotes.

On Wed, Feb 1, 2017 at 9:20 AM Ghazi TRIKI  wrote:

> Hello,
>
> I am helping Siva on a Jenkins build task. We wrote a pipeline email
> function that get log and puts it to email. The issue we have is that we
> tried using BUILD_LOG_EXCERPT and BUILD_LOG variables but get the following
> exception. Can you help us please?
>
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
> failed:
> WorkflowScript: 17: unexpected token: BUILD_LOG_EXCERPT @ line 17, column
> 11.
>  ${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished:
> SUCCESS"}""",
>
> --
> 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/aa987e90-2a58-4909-88fc-2773f666d0a2%40googlegroups.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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVdDS2kNudwYnCQZivO03V1hc15qYfD88VxtpHcRZZLx4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


docker plugins

2017-02-01 Thread john
I have been using the docker-build-step plugin for creating an image and 
running various docker commands in a build. Unfortunately since docker has 
moved on, it has stopped working and is not being updated.
Is there a preferred docker plugin? Or am I better off using shell commands?
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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/dbf9d056-fc33-4903-bc00-fd024146364b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins Email-ext help - accessing build log in email

2017-02-01 Thread Ghazi TRIKI


Hello,

I am helping Siva on a Jenkins build task. We wrote a pipeline email 
function that get log and puts it to email. The issue we have is that we 
tried using BUILD_LOG_EXCERPT and BUILD_LOG variables but get the following 
exception. Can you help us please?

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup 
failed:
WorkflowScript: 17: unexpected token: BUILD_LOG_EXCERPT @ line 17, column 
11.
 ${BUILD_LOG_EXCERPT, start="^Hello World", end="^Finished: 
SUCCESS"}""",

-- 
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/aa987e90-2a58-4909-88fc-2773f666d0a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Build pipeline plugin can't find downstream job for manual trigger

2017-02-01 Thread Peter Nelissen
What do you mean with the folder? The project name? Pipeline name?

Thanks!
Peter

On Monday, 18 July 2016 21:38:58 UTC+2, Guy Knights wrote:
>
> For anyone else dealing with this issue, I found the solution. I recently 
> moved to using folders in Jenkins 2.x, and it's necessary to specify the 
> folder name in the downstream job text field for the post-build action, but 
> only for the manual trigger. I found this info here: 
> https://issues.jenkins-ci.org/browse/JENKINS-34099.
>
> On Thursday, July 14, 2016 at 4:04:30 PM UTC-7, Guy Knights wrote:
>>
>> In Jenkins 2.7.1 with build-pipeline plugin 1.5.3.1 I'm trying to set a 
>> manual downstream trigger for a job using the "Build other projects (manual 
>> step)" post-build action, but it can't seem to find any projects in the 
>> same folder, and if I type the name in manually it gives me a "No such 
>> project" error like so:
>>
>> *No such project ‘CLIENT - Deploy to production’. Did you mean ‘CLIENT - 
>> Deploy to production?*
>>
>> As you can see, the name it suggests is the same as the name it says it 
>> can't find, which is perplexing. I try copying the name it suggests into 
>> the downstream project names box, but it still gives me the same error.
>>
>> If I use the "Trigger parameterized build on other projects" post-build 
>> action instead, it finds all the projects fine and I can use this method, 
>> but of course it executes without manual intervention, which is not what 
>> I'm after. I used to run Jenkins 1.65 and this worked fine, so I'm 
>> wondering if it's a bug related to this new Jenkins version. Does anyone 
>> know how to fix this?
>>
>> Thanks,
>> Guy
>>
>>

-- 
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/15f2207c-bf43-46b9-86dd-9f0d80144687%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Immediate need Sr. Database Developer (MySQL/SQL Server) -Direct Client

2017-02-01 Thread Ranadheer
Hello,



Hope you are doing great.



*Position ID – 7181 *

*Position Title – Sr. Database Developer (MySQL/SQL Server)*

*Worksite Address – Columbia, SC*



*Required Skills (Rank In Order of Importance):*

·  Accounting & Financial knowledge & experience in connection with DB and
application development.

·  Database experience (5 years min.) of at least two (2) databases.

  oMySQL

  oMS SQL Server

  oOther

·  Database tools, at least one of the following (1-year min.)

  oMySQL Workbench

  oTOAD or equivalent

·  Experience implementing up-to-date industry standard procedures and
schemas for the majority of the following:

  oNaming conventions

  oRevising DB schemas for consistent use of terminology, naming,
etc.\

   oUpdate history

   oLogging

   oHIPAA compliance
   oSecurity and access control

   oData exchange protocols

   oCross platform integration

·  Strong knowledge and use of SQL; multi table JOINS, functions,
procedures, triggers, etc.

·  Experience creating SQL views for the foundation of reports and forms

·  Excellent listening and communication (written & verbal) skills; ability
to discuss and present information logically and concisely

·  Ability to work individually and as part of a team. Willing to share
knowledge & experience with others

·  Flexible problem solver; use of previous knowledge & experience, yet
open to alternative methods when made available



*Preferred Skills:*



·  Additional Database tools experience; e.g.

oDatanamic tool Suite

oErWin, etc.

oSurvey application DB schema with update history capacity

  oOpen Source development experience; e.g., PHP and/or JavaScript
coding

oExperience with disconnected (store & forward) database
applications

oDatabase experience

§  Sybase

§  MS Access

Experience with Platforms as a Service (PaaS) and Software as a Service
(SaaS)

§  Data transfers

§  Data integration across systems


  o  Experience with Data Governance and related documentation



*Required Education/Certifications:*

·  Bachelor of Science; BA may be considered



*Preferred Education/Certifications:*

·  Master of Science or PhD

-- 
Thanks,
Ranadheer
Swift Solutions Inc
*732.218.7803*  (Desk)
*r...@s3staff.com * (Email)
*www.swiftsol.com * (Website)
Certified Minority Business Enterprise (MBE)

-- 
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/CAEAA5hL7YgpiZzGv9O_MQecm%3D5Mss9EVGh%2B8J2bkQ%3D%3DcQrKruQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Slow updates from the repository

2017-02-01 Thread Eliezer Croitoru
I am updating Jenkins regularly on both CentOS, Debian and Ubuntu and most
of the time it's in the middle of the night(TimeZone +2) and I have used the
instructions from:
http://pkg.jenkins-ci.org/redhat/

But most of the time the download is lower the 1Mbit per second and some
other times it's 20+(my dsl connection is 30+).
I wanted to know if others have the same issue and if so what can be done to
resolve this issue?
I have a local self hosted server which I can rsync at the spare time the
repository once in a while(a week or less).
Where should I start in order to mirror locally the repositories to speed
the local updates?

Thanks,
Eliezer


Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il



-- 
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/068001d27c86%247d65c850%24783158f0%24%40ngtech.co.il.
For more options, visit https://groups.google.com/d/optout.


Deploying a file on a remote location

2017-02-01 Thread gaurav lele
I am using the ArtifactDeployer plugin to deploy files onto a remote 
location. But I am getting these errors.
 [ArtifactDeployer] - [ERROR] -  Failed to deploy. Can't create the 
directory '53'
 [ArtifactDeployer] - [ERROR] - Failed to mkdirs

And also how do I create permissions in Jenkins to write files?
I have checked the global security but coulndt find any option
Please let me know a solution.

-- 
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/954ca79a-26ea-4d34-9d35-932f61dcbf51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Attaching to QueueTaskDispatcher extension point without a plugin

2017-02-01 Thread Stephen Connolly
Writing a plugin would be easier than your suggested approach.

Writing a plugin is not that hard. You'll just start with an empty plugin
and add your extension class.

On Wed 1 Feb 2017 at 03:55, Alexander Yustus  wrote:

> Hi all,
>
> I want to implement the feature to prevent a Pipeline job from even
> starting when there is no available executors with certain label.
> I didn't found any plugins that do the exact thing, and I'm no java
> developer, so writing my own plugin is what I really want to avoid ;)
>
> That said, is there a way to add an extension for QueueTaskDispatcher via
> Groovy script,
> for example, using Groovy Events Listener Plugin
> ?
>
> thank you in advance,
> Alexander.
>
> --
> 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/50d9ea71-2acd-4bb6-96c5-a6d8554fe949%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Sent from my phone

-- 
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/CA%2BnPnMzB1t7UUXVsL7HLD7K3WP53auNPyq_OzvYC5eXGsM1vkg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.