date:20170221

Thanks for suggestions Indra. It finally works!

I just missed the Saltstack plugin version. I used the 1.7.1. Pipeline 
support is on 2.0.0.

I just installed the Saltstack plugin 2.0.0 manually and the pipeline 
support finally works.

- Rustan

On Wednesday, February 22, 2017 at 9:50:32 AM UTC+8, Rustan Capal wrote:
>
> Thanks Indra. We'll look with your suggested solution.
>
>
> On Wednesday, February 22, 2017 at 2:22:47 AM UTC+8, Indra Gunawan 
> (ingunawa) wrote:
>>
>> Check first if you have installed the saltstack-plugin version that 
>> supports pipeline.  Please verify that the plugin with pipeline support 
>> dependencies are met.
>>
>> Observe anything that might be printed out in Jenkins log file related to 
>> saltstack-plugin.
>>
>>  
>>
>> -Indra
>>
>>  
>>
>>  
>>
>> *From: * on behalf of Rustan Capal <
>> rusta...@gmail.com>
>> *Reply-To: *"jenkins...@googlegroups.com" 
>> *Date: *Tuesday, February 21, 2017 at 10:01 AM
>> *To: *Jenkins Users 
>> *Subject: *Re: java.lang.NoSuchMethodError: No such DSL method 'salt' 
>> found among steps
>>
>>  
>>
>> Saltstack Plugin Installed: 
>> https://wiki.jenkins-ci.org/display/JENKINS/saltstack-plugin
>>
>>
>> On Wednesday, February 22, 2017 at 1:54:17 AM UTC+8, Rustan Capal wrote: 
>>
>> Hi Everyone,
>>
>> Can anyone tell me what I'm missing here? Salt API already installed. 
>> Jenkins version: 2.32.2
>>
>>
>>
>> *[PIPELINE SCRIPT] *import groovy.json.*
>>
>> node() {
>>   saltresult = salt authtype: 'pam', clientInterface: local(arguments: 
>> '"uname -r"', blockbuild: true, 
>> function: 'cmd.run', jobPollTime: 16, target: '*', targetType: 
>> 'glob'), 
>> credentialsId: 'c58c819b-89f2-4400-bb94-1ec79920adb4', servername: '
>> http://10.10.214.233:8181'
>>   def prettyJson = JsonOutput.prettyPrint(saltresult)
>>   println(prettyJson)
>> }
>>
>>
>> *[BUILD OUTPUT]*
>>
>> [Pipeline] node
>>
>> Running on master in 
>> /var/lib/jenkins/workspace/hello-world-pipeline-saltstack
>>
>> [Pipeline] {
>>
>> [Pipeline] }
>>
>> [Pipeline] // node
>>
>> [Pipeline] End of Pipeline
>>
>> java.lang.NoSuchMethodError: No such DSL method 'salt' found among steps 
>> [ansiColor, archive, bat, build, catchError, checkout, deleteDir, dir, 
>> dockerFingerprintFrom, dockerFingerprintRun, echo, emailext, 
>> emailextrecipients, error, exws, exwsAllocate, fileExists, findFiles, 
>> getContext, git, input, isUnix, libraryResource, load, mail, milestone, 
>> node, parallel, properties, pwd, readFile, readManifest, readMavenPom, 
>> readProperties, readTrusted, readYaml, retry, sh, sleep, stage, stash, step, 
>> svn, timeout, timestamps, tool, touch, unarchive, unstash, unzip, waitUntil, 
>> withContext, withCredentials, withDockerContainer, withDockerRegistry, 
>> withDockerServer, withEnv, wrap, writeFile, writeMavenPom, ws, zip] or 
>> symbols [all, always, ant, antFromApache, antOutcome, antTarget, apiToken, 
>> architecture, archiveArtifacts, artifactManager, batchFile, booleanParam, 
>> buildButton, buildDiscarder, caseInsensitive, caseSensitive, choice, 
>> choiceParam, clock, cloud, command, configFile, configFileProvider, cron, 
>> crumb, defaultView, demand, disableConcurrentBuilds, downloadSettings, 
>> downstream, dumb, envVars, fastestReadSpeed, fastestWriteSpeed, file, 
>> fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, 
>> git, hyperlink, hyperlinkToModels, installSource, jdk, jdkInstaller, jgit, 
>> jgitapache, jnlp, jobName, junit, lastDuration, lastFailure, 
>> lastGrantedAuthorities, lastStable, lastSuccess, legacy, list, local, 
>> location, logRotator, loggedInUsersCanDoAnything, masterBuild, maven, 
>> maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, mostUsableSpace, 
>> myView, nodeProperties, nonStoredPasswordParam, none, overrideIndexTriggers, 
>> paneStatus, parameters, password, pattern, pipelineTriggers, plainText, 
>> plugin, pollSCM, projectNamingStrategy, proxy, queueItemAuthenticator, 
>> quietPeriod, run, runParam, schedule, scmRetryCount, search, security, 
>> shell, slave, stackTrace, standard, status, string, stringParam, swapSpace, 
>> text, textParam, tmpSpace, toolLocation, unsecured, upstream, 
>> usernameColonPassword, usernamePassword, viewsTabBar, weather, zfs, zip] or 
>> globals [currentBuild, docker, env, params, scm, simpleBuild]
>>
>>   at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:149)
>>
>>   at 
>> org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108)
>>
>>   at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source)
>>
>>   at 
>> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
>>
>>   at 
>> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
>>
>>   at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151)
>>
>>   at 
>>

Separating build failure from test failures

2017-02-21 Thread Cody Konior

I'd like to somehow separate on the Jenkins page the difference between 
jobs which failed due to a build/script error versus jobs which had failing 
tests.

I use the PowerShell plugin and can set the overall pass/fail based on that 
- sure. But then I lose visibility on the front page that a job had failing 
tests within it.

Does anyone have a workaround?

I saw a plugin a while ago that could add Pass/Fail counts (but not 
indicators) to the front view. But I don't remember the plugin name and it 
didn't function with Folders (and it was a view, so, it was nigh impossible 
to replace the All view, as you know how difficult it can be for folders).

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/3f08873e-838a-4669-be74-3d46f1cc8388%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Workspace root directory (Jenkinsfile)

I have my local environment setup to debug.  I have no experience, so it 
might take some time, but so far I have noticed it works fine for Pipeline 
jobs, but an issue with multibranch pipelines and ultimately github orgs 
(uses multibranch pipelines).

I'll post my findings when I'm done.

On Tuesday, February 21, 2017 at 8:03:23 PM UTC-5, Ryan Hutchison wrote:
>
> This is all very new to me, but it looks like I need to start here.
>
>
> https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java#L541-L548
>

-- 
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/a338fe23-fb29-4028-b060-537fe69ed7e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: CloudBees Docker Build and Publish plugin - Auto deploy to EC2

2017-02-21 Thread Paul Mateos

Did you get any answers regarding this issue. I too cannot select 
credentials from the dropdown

On Saturday, 25 July 2015 01:27:22 UTC+10, Prasad Bond wrote:
>
> We are trying to do the auto deployment of docker image to EC2 container. 
>  We thought of doing the following.
>
> 1.   Created the Jenkins Jobs – to get the code from git hub, prepare 
> the image  and push the image to private docker hub (which is created on 
> docker.com ) using CloudBees Docker Build and Publish plugin 
> 
>
> 2.   Than thought of deploy the docker image from docker hub to EC2 
> instance. 
>
>  
>
> Can you please guide me with the proper steps to make auto deployment of 
> docker images to EC2 instance. I added the following post build step for 
> the docker build and publish.
>
>
> 
>
>
>  
>
> But here my doubt is what will the docker host URI, server credentials 
> (not able to see any details in the drop down even after adding from add 
> button). For testing I gave the values for Repository name, tag, docker 
> host url left blank, server credentials left blank. *Given the values for 
> docker registry as **https://registry.hub.docker.com/u/ABCD/javatest/* 
> * and by clicking on 
> Add button given the registry credentials*.
>
>  
>
> 1.   When I trigger the build from Jenkins getting the following 
> error.
>
> ERROR: Build step failed with exception
>
> net.sf.json.JSONException: null object
>
> at net.sf.json.JSONObject.verifyIsNull(JSONObject.java:2688)
>
> at net.sf.json.JSONObject.element(JSONObject.java:1733)
>
> at net.sf.json.JSONObject.element(JSONObject.java:1716)
>
> at net.sf.json.JSONObject.put(JSONObject.java:2328)
>
> at 
> org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryToken$1.call(DockerRegistryToken.java:100)
>
> at 
> org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryToken$1.call(DockerRegistryToken.java:71)
>
> at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
>
> at 
> org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryToken.newKeyMaterialFactory(DockerRegistryToken.java:71)
>
> at 
> org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:204)
>
> at 
> org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:193)
>
> at 
> com.cloudbees.dockerpublish.DockerBuilder$Perform.executeCmd(DockerBuilder.java:381)
>
> at 
> com.cloudbees.dockerpublish.DockerBuilder$Perform.executeCmd(DockerBuilder.java:359)
>
> at 
> com.cloudbees.dockerpublish.DockerBuilder$Perform.buildAndTag(DockerBuilder.java:305)
>
> at 
> com.cloudbees.dockerpublish.DockerBuilder$Perform.exec(DockerBuilder.java:252)
>
> at 
> com.cloudbees.dockerpublish.DockerBuilder$Perform.access$100(DockerBuilder.java:233)
>
> at 
> com.cloudbees.dockerpublish.DockerBuilder.perform(DockerBuilder.java:208)
>
> at 
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
>
> at 
> hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:906)
>
> at 
> hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:857)
>
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)
>
> at hudson.model.Run.execute(Run.java:1741)
>
> at 
> hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
>
> at 
> hudson.model.ResourceController.execute(ResourceController.java:98)
>
> at hudson.model.Executor.run(Executor.java:381)
>
> Build step 'Docker Build and Publish' marked build as failure
>
>  
>
> 2.   When I give the value as none for ‘*the registry credentials’ 
> *getting 
> the following error*.*
>
>  
>
> Image push failed
>
> Please login prior to push:
>
> Username: EOF
>
> Build step 'Docker Build and Publish' marked build as failure
>
>  
>
> *Following is the docker file:*   
>
> FROM java:7
>
> MAINTAINER tester
>
> ADD sample.jar /test/sample.jar
>
> RUN chmod +x /test/sample.jar
>
>  
>
> Following are the configuration/environment:
>
> Java version "1.8.0_40"
>
> Linux -  x86_64 -  GNU/Linux
>
> Docker version 1.7.1, build 786b29d
>
> Jenkins version - 1.620
>
> CloudBees Docker Build and Publish plugin 
> 
>  
> – 1.0
>
> Docker Commons Plugin – 1.1
>
>  
>
> *sudo docker version >>*
>
> Client version: 1.7.1
>
> Client API

RejectedAccessException: unclassified method java.lang.String call java.lang.String org.jenkinsci.plugins.workflow.cps.CpsClosure2

2017-02-21 Thread Thomas Fjellstrom

When using the scripted pipeline, I'm seemingly unable to pass closures 
into methods, that then call those closures? Maybe my grasp of groovy and 
jenkins is weak.

Full error:

org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: 
unclassified method java.lang.String call java.lang.String 
org.jenkinsci.plugins.workflow.cps.CpsClosure2 at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:113)
 at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at 
org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at 
com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16)
 at WorkflowScript.dockerStage(WorkflowScript:43) at ___cps.transform___(Native 
Method) at 
com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)
 at 
com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)
 at 
com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82)
 at sun.reflect.GeneratedMethodAccessor210.invoke(Unknown Source) at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606) at 
com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
 at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46) at 
com.cloudbees.groovy.cps.Next.step(Next.java:74) at 
com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
 at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33)
 at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30)
 at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
 at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30)
 at 
org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) 
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) 
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80)
 at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240)
 at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228)
 at 
org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262) at 
hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
 at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at 
java.util.concurrent.FutureTask.run(FutureTask.java:262) at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
at java.lang.Thread.run(Thread.java:745) Finished: FAILURE

Example code:


def dockerStage(title, dir, def body) {
 stage(title) {
 node('docker') {
 checkout scm
 
 dir(dir) {
 withCredentials([[$class: 'UsernamePasswordMultiBinding', credentialsId: 
REGISTRY_AUTH_KEY, usernameVariable: 'USERNAME', passwordVariable: 
'PASSWORD']]) {
 sh "$DOCKER_CMD login -u $USERNAME -p $PASSWORD $DOCKER_REGISTRY"
 body()
 }
 }
 }
 }
}


Called like:

dockerStage('Do a thing', 'somedir') {
   sh './do_something'
}

-- 
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/f59aeb22-7ee6-4a9e-9cbf-ba5428910476%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoSuchMethodError: No such DSL method 'salt' found among steps

Thanks Indra. We'll look with your suggested solution.


On Wednesday, February 22, 2017 at 2:22:47 AM UTC+8, Indra Gunawan 
(ingunawa) wrote:
>
> Check first if you have installed the saltstack-plugin version that 
> supports pipeline.  Please verify that the plugin with pipeline support 
> dependencies are met.
>
> Observe anything that might be printed out in Jenkins log file related to 
> saltstack-plugin.
>
>  
>
> -Indra
>
>  
>
>  
>
> *From: * on behalf of Rustan 
> Capal 
> *Reply-To: *"jenkins...@googlegroups.com " <
> jenkins...@googlegroups.com >
> *Date: *Tuesday, February 21, 2017 at 10:01 AM
> *To: *Jenkins Users 
> *Subject: *Re: java.lang.NoSuchMethodError: No such DSL method 'salt' 
> found among steps
>
>  
>
> Saltstack Plugin Installed: 
> https://wiki.jenkins-ci.org/display/JENKINS/saltstack-plugin
>
>
> On Wednesday, February 22, 2017 at 1:54:17 AM UTC+8, Rustan Capal wrote: 
>
> Hi Everyone,
>
> Can anyone tell me what I'm missing here? Salt API already installed. 
> Jenkins version: 2.32.2
>
>
>
> *[PIPELINE SCRIPT] *import groovy.json.*
>
> node() {
>   saltresult = salt authtype: 'pam', clientInterface: local(arguments: 
> '"uname -r"', blockbuild: true, 
> function: 'cmd.run', jobPollTime: 16, target: '*', targetType: 
> 'glob'), 
> credentialsId: 'c58c819b-89f2-4400-bb94-1ec79920adb4', servername: '
> http://10.10.214.233:8181'
>   def prettyJson = JsonOutput.prettyPrint(saltresult)
>   println(prettyJson)
> }
>
>
> *[BUILD OUTPUT]*
>
> [Pipeline] node
>
> Running on master in /var/lib/jenkins/workspace/hello-world-pipeline-saltstack
>
> [Pipeline] {
>
> [Pipeline] }
>
> [Pipeline] // node
>
> [Pipeline] End of Pipeline
>
> java.lang.NoSuchMethodError: No such DSL method 'salt' found among steps 
> [ansiColor, archive, bat, build, catchError, checkout, deleteDir, dir, 
> dockerFingerprintFrom, dockerFingerprintRun, echo, emailext, 
> emailextrecipients, error, exws, exwsAllocate, fileExists, findFiles, 
> getContext, git, input, isUnix, libraryResource, load, mail, milestone, node, 
> parallel, properties, pwd, readFile, readManifest, readMavenPom, 
> readProperties, readTrusted, readYaml, retry, sh, sleep, stage, stash, step, 
> svn, timeout, timestamps, tool, touch, unarchive, unstash, unzip, waitUntil, 
> withContext, withCredentials, withDockerContainer, withDockerRegistry, 
> withDockerServer, withEnv, wrap, writeFile, writeMavenPom, ws, zip] or 
> symbols [all, always, ant, antFromApache, antOutcome, antTarget, apiToken, 
> architecture, archiveArtifacts, artifactManager, batchFile, booleanParam, 
> buildButton, buildDiscarder, caseInsensitive, caseSensitive, choice, 
> choiceParam, clock, cloud, command, configFile, configFileProvider, cron, 
> crumb, defaultView, demand, disableConcurrentBuilds, downloadSettings, 
> downstream, dumb, envVars, fastestReadSpeed, fastestWriteSpeed, file, 
> fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, git, 
> hyperlink, hyperlinkToModels, installSource, jdk, jdkInstaller, jgit, 
> jgitapache, jnlp, jobName, junit, lastDuration, lastFailure, 
> lastGrantedAuthorities, lastStable, lastSuccess, legacy, list, local, 
> location, logRotator, loggedInUsersCanDoAnything, masterBuild, maven, 
> maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, mostUsableSpace, myView, 
> nodeProperties, nonStoredPasswordParam, none, overrideIndexTriggers, 
> paneStatus, parameters, password, pattern, pipelineTriggers, plainText, 
> plugin, pollSCM, projectNamingStrategy, proxy, queueItemAuthenticator, 
> quietPeriod, run, runParam, schedule, scmRetryCount, search, security, shell, 
> slave, stackTrace, standard, status, string, stringParam, swapSpace, text, 
> textParam, tmpSpace, toolLocation, unsecured, upstream, 
> usernameColonPassword, usernamePassword, viewsTabBar, weather, zfs, zip] or 
> globals [currentBuild, docker, env, params, scm, simpleBuild]
>
>   at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:149)
>
>   at 
> org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108)
>
>   at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source)
>
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
>
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
>
>   at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151)
>
>   at 
> org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21)
>
>   at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115)
>
>   at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149)
>
>   at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146)
>
>   at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123)
>
>

RE: Updated Hotlist please share your daily requirements..

2017-02-21 Thread John Mellor

Can someone please cancel the posting credentials for this user that allows 
them to post this inappropriate garbage?


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of mahi v
Sent: February-21-17 17:06
Subject: Updated Hotlist please share your daily requirements..

Dear Recruiter,
Please find the Below Hotlist and send me your Requirements to 
mah...@samuraiinfotech.com / 
r...@samuraiinfotech.com
Name

Skill Set

Experience (In Years)

Location

Relocation











Aarthi G

QA Engineer

8

TX

Open

Koneru

SQL DBA

7

NY

Open

Dheeraj

Citrix Admin

7

DC

Open

Phanesh

AWS Developer

7

CA

Open

Charan

Citrix Admin

7

DC

Open

Sruthi

UI Developer

5

PA

Open

Hema

.net Developer

5

VA

Open

Vijitha (Citizen)

QA Tester

5

GA

Only GA

Tushma

QA Tester

7

GA

Open

Venakta (Citizen)

QA Tester

5

TX

Only TX

Anjana

WMB Admin

7

WI

Open

Ravi Kumar

Devops /AWS

7

GA

Open

Rekha

.net Developer

5

GA

Only GA

Gokul

CognosT1

7

CA

Open

Krishna

Oracle Apps Fin Functional

10

CA

Open

Ram

Project Manager

15

NY

 Open

Naveen

CognosT1

5

CA

Open

Srini

Devops/AWS

6

PA

Open

Balaji

Quality Analyst

7

NY

Open

Raj

Devops /AWS

7

GA

Open

Ravi

Devops /AWS

7

NY

Open

Avinash

Performance Tester

7

AZ

Open

 Jayaram

Programme Manager

16

IN

Open

Rakesh

Salesforce Developer

8

IN

Open

  Annapurna (Citizen)

QA Analyst

7

GA

Only GA


Thanks & Regards
Mahesh
Samurai Infotech LLC
Consulting - Development – Staffing
Voice: 678-799-8055
E-mail : 
mah...@samuraiinfotech.com/r...@samuraiinfotech.com
Website : www.samuraiinfotech.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/CAAko6%3D8nxe22x6ga-riDURyxaW%2BBQWYArDShQXU2%2B1jRAiP_Ag%40mail.gmail.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/acb00ab342da4faa8b834db0b312483b%40mbx02cmb01p.esentire.local.
For more options, visit https://groups.google.com/d/optout.

Updated Hotlist please share your daily requirements..

2017-02-21 Thread mahi v

Dear Recruiter,

Please find the Below Hotlist and send me your Requirements to
mah...@samuraiinfotech.com  /
r...@samuraiinfotech.com

*Name *

*Skill Set *

*Experience (In Years) *

*Location*

*Relocation *











*Aarthi G*

*QA Engineer*

*8*

*TX*

*Open*

*Koneru*

*SQL DBA*

*7*

*NY*

*Open*

*Dheeraj *

*Citrix Admin*

*7*

*DC*

*Open*

*Phanesh*

*AWS Developer*

*7*

*CA*

*Open*

*Charan*

*Citrix Admin*

*7*

*DC*

*Open*

*Sruthi *

*UI Developer*

*5*

*PA*

*Open*

*Hema *

*.net Developer*

*5*

*VA*

*Open*

*Vijitha (Citizen)*

*QA Tester*

*5*

*GA*

*Only GA*

*Tushma *

*QA Tester*

*7*

*GA*

*Open*

*Venakta (Citizen)*

*QA Tester*

*5*

*TX*

*Only TX*

*Anjana *

*WMB Admin *

*7*

*WI*

*Open*

*Ravi Kumar*

*Devops /AWS*

*7*

*GA*

*Open*

*Rekha *

*.net Developer*

*5*

*GA*

*Only GA*

*Gokul*

*CognosT1*

*7*

*CA*

*Open*

*Krishna*

*Oracle Apps Fin Functional*

*10 *

*CA*

*Open *

*Ram*

*Project Manager*

*15*

*NY*

* Open*

*Naveen*

*CognosT1*

*5*

*CA*

*Open*

*Srini*

*Devops/AWS*

*6*

*PA*

*Open*

*Balaji*

*Quality Analyst *

*7*

*NY*

*Open*

*Raj*

*Devops /AWS*

*7*

*GA*

*Open*

*Ravi*

*Devops /AWS*

*7*

*NY*

*Open*

*Avinash  *

*Performance Tester*

*7*

*AZ*

*Open*

* Jayaram*

*Programme Manager*

*16*

*IN*

*Open*

*Rakesh *

*Salesforce Developer*

*8*

*IN*

*Open*

*  Annapurna (Citizen)*

*QA Analyst*

*7*

*GA*

*Only GA*



*Thanks & Regards*

*Mahesh*

*Samurai Infotech LLC *

*Consulting - Development – Staffing*

*Voice: *678-799-8055

*E-mail : *mah...@samuraiinfotech.com/r...@samuraiinfotech.com

Website : www.samuraiinfotech.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/CAAko6%3D8nxe22x6ga-riDURyxaW%2BBQWYArDShQXU2%2B1jRAiP_Ag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: QUESTION: Jenkins initialization has not reached the COMPLETED

2017-02-21 Thread Inna Ginzburg

Thank You Danial. It fixed for me too

On Monday, January 30, 2017 at 8:24:33 AM UTC-6, Daniel Beck wrote:
>
>
> > On 30.01.2017, at 09:39, Victor Martinez  > wrote: 
> > 
> > Current state is "Loaded all jobs" and I don't see much exceptions or 
> errors in the jenkins.log file, so I wonder, whether the above message is a 
> genuine issue and if so, how I can debug further. 
> > 
>
> Well, 'Loaded all jobs' is not the last init stage, 'Completed' is. So 
> there appears to be a problem 
>
> Do you have the extremenotification plugin installed? It's the one 
> referenced in JENKINS-37759. 
>
>

-- 
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/a8dd1077-82e8-41b5-b4c6-010b62c5d6af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins PR triggers a build of PR

2017-02-21 Thread Indra Gunawan (ingunawa)

The working solution we have implemented is to use Jenkins Github Pull Request 
Builder plugin with webhook.  We let the plugin to control the webhook, ie.  
the Jenkins user account used by the plugin to check the github REST API would 
need write permission to the Github repository.

That’s the most stable solution.  We hate polling.


From:  on behalf of Michael Tidwell 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Tuesday, February 21, 2017 at 12:08 PM
To: Jenkins Users 
Subject: Re: Jenkins PR triggers a build of PR

Also like to note, I'm not using a webhook.  I'm attempting to do this through 
a "* * * * *" polling method (even though that seems to be frowned upon)

On Tuesday, February 21, 2017 at 3:05:43 PM UTC-5, Michael Tidwell wrote:
Hey Everyone,

Messing around with Jenkins.  Trying to make Jenkins automatically build on a 
PR, pull request, trigger. I want it to build the new PR code before it gets 
merged in.
I can actually make Jenkins build when I start a Pull Request, but it builds 
the old code base not the new PR code.

Any ideas?

Thanks,

Michael Tidwell
--
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/7c68b756-4b57-4192-8238-57fe34613d40%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/8301172D-73B0-4C09-AC97-0AD160064C7E%40cisco.com.
For more options, visit https://groups.google.com/d/optout.

Re: Workspace root directory (Jenkinsfile)

To simplify things, I stripped down my Jenkinsfile

node {
checkout scm
}

Still: Running on master in C:\Program Files
(x86)\Jenkins\workspace\ers.asicentral.com_pipeline-KZZ2FMCWP4OQDL4O6QTDBOBKZZPIXSJL4UPRWYIRJN3RJMX2S5IA

On Tue, Feb 21, 2017 at 3:35 PM, Jérôme Godbout  wrote:

> humm, I had a different workspace under Windows with pipeline working.
>
> Just to make sure you don't do any cd.. or dir(){} change into your
> pipeline script?
> Do you use the exws or exwsAllocate call?
>
> Probably not to all the above, just in case... sorry I can't help more,
> good luck
>
> [image: bodycad] 
> Jerome Godbout
> Software Developer
> 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
> T:  +1 418 527-1388 <(418)%20527-1388>
> E: jer...@bodycad.com
> www.bodycad.com
>
> The contents of this email message and any attachments are intended solely
> for the addressee(s) and may contain confidential and/or privileged
> information and may be legally protected from disclosure. If you are not
> the intended recipient of this message or their agent, or if this message
> has been addressed to you in error, please immediately alert the sender by
> reply email and then delete this message and any attachments. If you are
> not the intended recipient, you are hereby notified that any use,
> dissemination, copying, or storage of this message or its attachments is
> strictly prohibited.
>
> Le contenu de ce message et les pièces jointes sont destinés uniquement
> pour le(s) destinataire(s) et peuvent contenir des informations
> confidentielles et / ou privilégiées qui peuvent être protégées légalement
> contre toute divulgation. Si vous n'êtes pas le destinataire de ce message
> ou son agent, ou si ce message vous a été adressé par erreur, s’il vous
> plaît avertir immédiatement l'expéditeur par courriel de réponse, puis
> supprimer ce message et les pièces jointes. Si vous n'êtes pas le
> destinataire prévu, vous êtes par la présente informé que toute
> utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces
> jointes est strictement interdit.
>
> On Tue, Feb 21, 2017 at 2:57 PM, Ryan Hutchison 
> wrote:
>
>> I do not believe it's an issue with permissions.
>>
>> When I have worked with generic jobs, I did not have this issue.  It
>> seems to be related to pipeline/workflow.
>>
>> Hopefully someone that is familiar with the internals of pipeline can
>> provide some assistance.
>>
>> On Tuesday, February 21, 2017 at 2:53:44 PM UTC-5, Jérôme Godbout wrote:
>>>
>>> Humm, maybe someone from Jenkins can step in on this I'm out of idea.
>>> Else the only think I could see is permission problems for the service to
>>> write at that location and compare with the default path.
>>>
>>> [image: bodycad] 
>>> Jerome Godbout
>>> Software Developer
>>> 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
>>> T:  +1 418 527-1388 <(418)%20527-1388>
>>> E: jer...@bodycad.com
>>> www.bodycad.com
>>>
>>> The contents of this email message and any attachments are intended
>>> solely for the addressee(s) and may contain confidential and/or privileged
>>> information and may be legally protected from disclosure. If you are not
>>> the intended recipient of this message or their agent, or if this message
>>> has been addressed to you in error, please immediately alert the sender by
>>> reply email and then delete this message and any attachments. If you are
>>> not the intended recipient, you are hereby notified that any use,
>>> dissemination, copying, or storage of this message or its attachments is
>>> strictly prohibited.
>>>
>>> Le contenu de ce message et les pièces jointes sont destinés uniquement
>>> pour le(s) destinataire(s) et peuvent contenir des informations
>>> confidentielles et / ou privilégiées qui peuvent être protégées légalement
>>> contre toute divulgation. Si vous n'êtes pas le destinataire de ce message
>>> ou son agent, ou si ce message vous a été adressé par erreur, s’il vous
>>> plaît avertir immédiatement l'expéditeur par courriel de réponse, puis
>>> supprimer ce message et les pièces jointes. Si vous n'êtes pas le
>>> destinataire prévu, vous êtes par la présente informé que toute
>>> utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces
>>> jointes est strictement interdit.
>>>
>>> On Tue, Feb 21, 2017 at 2:21 PM, Ryan Hutchison 
>>> wrote:
>>>
 I have tried d:/${ITEM_FULLNAME} - no luck

 I also just tried ${JENKINS_HOME}/TEST/${ITEM_FULLNAME}

 note default is: ${JENKINS_HOME}/workspace/${ITEM_FULLNAME}

 I created TEST directory under jenkins home same root that workspace
 exists - still ignored.

 Running on master in C:\Program Files (x86)\Jenkins\workspace\i_api.
 asicentral.com_master-BLRHPIOJSBVARDRRLSJX5OHVKMDV5UTXULFID5
 BU57E37BSQ

 On Tuesday, February 21, 2017 at 2:13:47 PM UTC-5, Jérôme

Re: Workspace root directory (Jenkinsfile)

humm, I had a different workspace under Windows with pipeline working.

Just to make sure you don't do any cd.. or dir(){} change into your
pipeline script?
Do you use the exws or exwsAllocate call?

Probably not to all the above, just in case... sorry I can't help more,
good luck

[image: bodycad] 
Jerome Godbout
Software Developer
2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
T:  +1 418 527-1388
E: jer...@bodycad.com
www.bodycad.com

The contents of this email message and any attachments are intended solely
for the addressee(s) and may contain confidential and/or privileged
information and may be legally protected from disclosure. If you are not
the intended recipient of this message or their agent, or if this message
has been addressed to you in error, please immediately alert the sender by
reply email and then delete this message and any attachments. If you are
not the intended recipient, you are hereby notified that any use,
dissemination, copying, or storage of this message or its attachments is
strictly prohibited.

Le contenu de ce message et les pièces jointes sont destinés uniquement
pour le(s) destinataire(s) et peuvent contenir des informations
confidentielles et / ou privilégiées qui peuvent être protégées légalement
contre toute divulgation. Si vous n'êtes pas le destinataire de ce message
ou son agent, ou si ce message vous a été adressé par erreur, s’il vous
plaît avertir immédiatement l'expéditeur par courriel de réponse, puis
supprimer ce message et les pièces jointes. Si vous n'êtes pas le
destinataire prévu, vous êtes par la présente informé que toute
utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces
jointes est strictement interdit.

On Tue, Feb 21, 2017 at 2:57 PM, Ryan Hutchison 
wrote:

> I do not believe it's an issue with permissions.
>
> When I have worked with generic jobs, I did not have this issue.  It seems
> to be related to pipeline/workflow.
>
> Hopefully someone that is familiar with the internals of pipeline can
> provide some assistance.
>
> On Tuesday, February 21, 2017 at 2:53:44 PM UTC-5, Jérôme Godbout wrote:
>>
>> Humm, maybe someone from Jenkins can step in on this I'm out of idea.
>> Else the only think I could see is permission problems for the service to
>> write at that location and compare with the default path.
>>
>> [image: bodycad] 
>> Jerome Godbout
>> Software Developer
>> 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
>> T:  +1 418 527-1388 <(418)%20527-1388>
>> E: jer...@bodycad.com
>> www.bodycad.com
>>
>> The contents of this email message and any attachments are intended
>> solely for the addressee(s) and may contain confidential and/or privileged
>> information and may be legally protected from disclosure. If you are not
>> the intended recipient of this message or their agent, or if this message
>> has been addressed to you in error, please immediately alert the sender by
>> reply email and then delete this message and any attachments. If you are
>> not the intended recipient, you are hereby notified that any use,
>> dissemination, copying, or storage of this message or its attachments is
>> strictly prohibited.
>>
>> Le contenu de ce message et les pièces jointes sont destinés uniquement
>> pour le(s) destinataire(s) et peuvent contenir des informations
>> confidentielles et / ou privilégiées qui peuvent être protégées légalement
>> contre toute divulgation. Si vous n'êtes pas le destinataire de ce message
>> ou son agent, ou si ce message vous a été adressé par erreur, s’il vous
>> plaît avertir immédiatement l'expéditeur par courriel de réponse, puis
>> supprimer ce message et les pièces jointes. Si vous n'êtes pas le
>> destinataire prévu, vous êtes par la présente informé que toute
>> utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces
>> jointes est strictement interdit.
>>
>> On Tue, Feb 21, 2017 at 2:21 PM, Ryan Hutchison 
>> wrote:
>>
>>> I have tried d:/${ITEM_FULLNAME} - no luck
>>>
>>> I also just tried ${JENKINS_HOME}/TEST/${ITEM_FULLNAME}
>>>
>>> note default is: ${JENKINS_HOME}/workspace/${ITEM_FULLNAME}
>>>
>>> I created TEST directory under jenkins home same root that workspace
>>> exists - still ignored.
>>>
>>> Running on master in C:\Program Files (x86)\Jenkins\workspace\i_api.
>>> asicentral.com_master-BLRHPIOJSBVARDRRLSJX5OHVKMDV5UTXULFID5
>>> BU57E37BSQ
>>>
>>> On Tuesday, February 21, 2017 at 2:13:47 PM UTC-5, Jérôme Godbout wrote:

 can you try d:/${ITEM_FULLNAME}

 reverse the backslash just in case...

 [image: bodycad] 
 Jerome Godbout
 Software Developer
 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
 T:  +1 418 527-1388
 E: jer...@bodycad.com
 www.bodycad.com

 The contents of this email message and any attachments are intended
 solely for the addressee(s) and may contain

Re: Jenkins PR triggers a build of PR

2017-02-21 Thread Michael Tidwell

Also like to note, I'm not using a webhook.  I'm attempting to do this 
through a "* * * * *" polling method (even though that seems to be frowned 
upon)

On Tuesday, February 21, 2017 at 3:05:43 PM UTC-5, Michael Tidwell wrote:
>
> Hey Everyone,
>
> Messing around with Jenkins.  Trying to make Jenkins automatically build 
> on a PR, pull request, trigger. I want it to build the new PR code before 
> it gets merged in.
> I can actually make Jenkins build when I start a Pull Request, but it 
> builds the old code base not the new PR code.
>
> Any ideas?
>
> Thanks,
>
> Michael Tidwell
>

-- 
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/7c68b756-4b57-4192-8238-57fe34613d40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins PR triggers a build of PR

2017-02-21 Thread Michael Tidwell

Hey Everyone,

Messing around with Jenkins.  Trying to make Jenkins automatically build on 
a PR, pull request, trigger. I want it to build the new PR code before it 
gets merged in.
I can actually make Jenkins build when I start a Pull Request, but it 
builds the old code base not the new PR code.

Any ideas?

Thanks,

Michael Tidwell

-- 
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/e6cf9818-36b5-493c-9caf-48764b44ffe4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Workspace root directory (Jenkinsfile)

I do not believe it's an issue with permissions.

When I have worked with generic jobs, I did not have this issue.  It seems 
to be related to pipeline/workflow.

Hopefully someone that is familiar with the internals of pipeline can 
provide some assistance.

On Tuesday, February 21, 2017 at 2:53:44 PM UTC-5, Jérôme Godbout wrote:
>
> Humm, maybe someone from Jenkins can step in on this I'm out of idea. Else 
> the only think I could see is permission problems for the service to write 
> at that location and compare with the default path.
>
> [image: bodycad]  
> Jerome Godbout
> Software Developer
> 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
> T:  +1 418 527-1388
> E: jer...@bodycad.com 
> www.bodycad.com
>
> The contents of this email message and any attachments are intended solely 
> for the addressee(s) and may contain confidential and/or privileged 
> information and may be legally protected from disclosure. If you are not 
> the intended recipient of this message or their agent, or if this message 
> has been addressed to you in error, please immediately alert the sender by 
> reply email and then delete this message and any attachments. If you are 
> not the intended recipient, you are hereby notified that any use, 
> dissemination, copying, or storage of this message or its attachments is 
> strictly prohibited. 
>
> Le contenu de ce message et les pièces jointes sont destinés uniquement 
> pour le(s) destinataire(s) et peuvent contenir des informations 
> confidentielles et / ou privilégiées qui peuvent être protégées légalement 
> contre toute divulgation. Si vous n'êtes pas le destinataire de ce message 
> ou son agent, ou si ce message vous a été adressé par erreur, s’il vous 
> plaît avertir immédiatement l'expéditeur par courriel de réponse, puis 
> supprimer ce message et les pièces jointes. Si vous n'êtes pas le 
> destinataire prévu, vous êtes par la présente informé que toute 
> utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces 
> jointes est strictement interdit.
>
> On Tue, Feb 21, 2017 at 2:21 PM, Ryan Hutchison  > wrote:
>
>> I have tried d:/${ITEM_FULLNAME} - no luck
>>
>> I also just tried ${JENKINS_HOME}/TEST/${ITEM_FULLNAME}
>>
>> note default is: ${JENKINS_HOME}/workspace/${ITEM_FULLNAME}
>>
>> I created TEST directory under jenkins home same root that workspace 
>> exists - still ignored.
>>
>> Running on master in C:\Program Files 
>> (x86)\Jenkins\workspace\i_api.asicentral.com_master-BLRHPIOJSBVARDRRLSJX5OHVKMDV5UTXULFID5BU57E37BSQ
>>
>> On Tuesday, February 21, 2017 at 2:13:47 PM UTC-5, Jérôme Godbout wrote:
>>>
>>> can you try d:/${ITEM_FULLNAME}
>>>
>>> reverse the backslash just in case...
>>>
>>> [image: bodycad]  
>>> Jerome Godbout
>>> Software Developer
>>> 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
>>> T:  +1 418 527-1388
>>> E: jer...@bodycad.com
>>> www.bodycad.com
>>>
>>> The contents of this email message and any attachments are intended 
>>> solely for the addressee(s) and may contain confidential and/or privileged 
>>> information and may be legally protected from disclosure. If you are not 
>>> the intended recipient of this message or their agent, or if this message 
>>> has been addressed to you in error, please immediately alert the sender by 
>>> reply email and then delete this message and any attachments. If you are 
>>> not the intended recipient, you are hereby notified that any use, 
>>> dissemination, copying, or storage of this message or its attachments is 
>>> strictly prohibited. 
>>>
>>> Le contenu de ce message et les pièces jointes sont destinés uniquement 
>>> pour le(s) destinataire(s) et peuvent contenir des informations 
>>> confidentielles et / ou privilégiées qui peuvent être protégées légalement 
>>> contre toute divulgation. Si vous n'êtes pas le destinataire de ce message 
>>> ou son agent, ou si ce message vous a été adressé par erreur, s’il vous 
>>> plaît avertir immédiatement l'expéditeur par courriel de réponse, puis 
>>> supprimer ce message et les pièces jointes. Si vous n'êtes pas le 
>>> destinataire prévu, vous êtes par la présente informé que toute 
>>> utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces 
>>> jointes est strictement interdit.
>>>
>>> On Tue, Feb 21, 2017 at 2:12 PM, Ryan Hutchison  
>>> wrote:
>>>
 Global configuration workspace root directory is set to 
 D:\${ITEM_FULLNAME}

 D: is a physical disk.

 Service recycled.

 LOG:
 Running on asi-bldcn02-01 in C:\Program Files 
 (x86)\Jenkins\workspace\i_api.asicentral.com_master-BLRHPIOJSBVARDRRLSJX5OHVKMDV5UTXULFID5BU57E37BSQ

 Versions:
 Jenkins 2.47
 Pipeline 2.5

 Setup using Github Organization/Multibranch pipeline


 On Tuesday, February 21, 2017 at 1:50:40 PM UTC-5, Ryan Hutchison wrote:
>
> Thanks - I

Re: Workspace root directory (Jenkinsfile)

Humm, maybe someone from Jenkins can step in on this I'm out of idea. Else
the only think I could see is permission problems for the service to write
at that location and compare with the default path.

[image: bodycad] 
Jerome Godbout
Software Developer
2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
T:  +1 418 527-1388
E: jer...@bodycad.com
www.bodycad.com

The contents of this email message and any attachments are intended solely
for the addressee(s) and may contain confidential and/or privileged
information and may be legally protected from disclosure. If you are not
the intended recipient of this message or their agent, or if this message
has been addressed to you in error, please immediately alert the sender by
reply email and then delete this message and any attachments. If you are
not the intended recipient, you are hereby notified that any use,
dissemination, copying, or storage of this message or its attachments is
strictly prohibited.

Le contenu de ce message et les pièces jointes sont destinés uniquement
pour le(s) destinataire(s) et peuvent contenir des informations
confidentielles et / ou privilégiées qui peuvent être protégées légalement
contre toute divulgation. Si vous n'êtes pas le destinataire de ce message
ou son agent, ou si ce message vous a été adressé par erreur, s’il vous
plaît avertir immédiatement l'expéditeur par courriel de réponse, puis
supprimer ce message et les pièces jointes. Si vous n'êtes pas le
destinataire prévu, vous êtes par la présente informé que toute
utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces
jointes est strictement interdit.

On Tue, Feb 21, 2017 at 2:21 PM, Ryan Hutchison 
wrote:

> I have tried d:/${ITEM_FULLNAME} - no luck
>
> I also just tried ${JENKINS_HOME}/TEST/${ITEM_FULLNAME}
>
> note default is: ${JENKINS_HOME}/workspace/${ITEM_FULLNAME}
>
> I created TEST directory under jenkins home same root that workspace
> exists - still ignored.
>
> Running on master in C:\Program Files (x86)\Jenkins\workspace\i_api.
> asicentral.com_master-BLRHPIOJSBVARDRRLSJX5OHVKMDV5UTXULFID5BU57E37BSQ
>
> On Tuesday, February 21, 2017 at 2:13:47 PM UTC-5, Jérôme Godbout wrote:
>>
>> can you try d:/${ITEM_FULLNAME}
>>
>> reverse the backslash just in case...
>>
>> [image: bodycad] 
>> Jerome Godbout
>> Software Developer
>> 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
>> T:  +1 418 527-1388 <(418)%20527-1388>
>> E: jer...@bodycad.com
>> www.bodycad.com
>>
>> The contents of this email message and any attachments are intended
>> solely for the addressee(s) and may contain confidential and/or privileged
>> information and may be legally protected from disclosure. If you are not
>> the intended recipient of this message or their agent, or if this message
>> has been addressed to you in error, please immediately alert the sender by
>> reply email and then delete this message and any attachments. If you are
>> not the intended recipient, you are hereby notified that any use,
>> dissemination, copying, or storage of this message or its attachments is
>> strictly prohibited.
>>
>> Le contenu de ce message et les pièces jointes sont destinés uniquement
>> pour le(s) destinataire(s) et peuvent contenir des informations
>> confidentielles et / ou privilégiées qui peuvent être protégées légalement
>> contre toute divulgation. Si vous n'êtes pas le destinataire de ce message
>> ou son agent, ou si ce message vous a été adressé par erreur, s’il vous
>> plaît avertir immédiatement l'expéditeur par courriel de réponse, puis
>> supprimer ce message et les pièces jointes. Si vous n'êtes pas le
>> destinataire prévu, vous êtes par la présente informé que toute
>> utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces
>> jointes est strictement interdit.
>>
>> On Tue, Feb 21, 2017 at 2:12 PM, Ryan Hutchison 
>> wrote:
>>
>>> Global configuration workspace root directory is set to
>>> D:\${ITEM_FULLNAME}
>>>
>>> D: is a physical disk.
>>>
>>> Service recycled.
>>>
>>> LOG:
>>> Running on asi-bldcn02-01 in C:\Program Files
>>> (x86)\Jenkins\workspace\i_api.asicentral.com_master-BLRHPIOJ
>>> SBVARDRRLSJX5OHVKMDV5UTXULFID5BU57E37BSQ
>>>
>>> Versions:
>>> Jenkins 2.47
>>> Pipeline 2.5
>>>
>>> Setup using Github Organization/Multibranch pipeline
>>>
>>>
>>> On Tuesday, February 21, 2017 at 1:50:40 PM UTC-5, Ryan Hutchison wrote:

 Thanks - I will check everything again and try to recycle the service.

 I am simply mapping to D:\${ITEM_FULLNAME} - where D: is a physical
 disk.

 On Tuesday, February 21, 2017 at 1:45:38 PM UTC-5, Jérôme Godbout wrote:
>
> Have you try to restart the Jenkins server so it can take into account
> this new path? If so, which version, cause if the path is truly valid, it
> should work?
>
> I have a Window server which was working fine with another drive.

Re: credential plugin disappears after Jenkins upgrade to 1.658

2017-02-21 Thread Indra Gunawan (ingunawa)

You set the Jenkins to shut-down mode.  In plugin directory, Then you rename 
the credential directory to credential.bak or whatever.   Delete the existing 
credential.jpi and credentials.hpi.
Copy the backup credentials.hpi to plugin directory and restart Jenkins.  Tail 
the Jenkins.log as Jenkins restarts.


From:  on behalf of Prasu S 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Tuesday, February 21, 2017 at 11:24 AM
To: Jenkins Users 
Subject: Re: credential plugin disappears after Jenkins upgrade to 1.658

I have plugins directory back up , Can I copy the plugin from the backup or do 
I have to install different plugin version like 1.22. Please help. Appreciate 
any help.


I see these errors in the log:
***
SEVERE: Failed Inspecting plugin 
D:\Build\Jenkins\apps\jenkins\jenkins_home\plugins\credentials.jpi
java.io.IOException: Failed to expand 
D:\Build\Jenkins\apps\jenkins\jenkins_home\plugins\credentials.jpi
at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:532)
at 
hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:167)
at hudson.PluginManager$1$3$1.run(PluginManager.java:288)
at 
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$8.runTask(Jenkins.java:958)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: Problem creating zip: null
at org.apache.tools.ant.taskdefs.Zip.executeMain(Zip.java:741)
at org.apache.tools.ant.taskdefs.Zip.execute(Zip.java:568)
at 
hudson.ClassicPluginStrategy.createClassJarFromWebInfClasses(ClassicPluginStrategy.java:589)
at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:530)
... 10 more
Caused by: java.io.EOFException
at java.io.RandomAccessFile.readFully(RandomAccessFile.java:446)
at java.io.RandomAccessFile.readFully(RandomAccessFile.java:424)
at org.apache.tools.zip.ZipFile.resolveLocalFileHeaderData(ZipFile.java:522)
at org.apache.tools.zip.ZipFile.(ZipFile.java:187)
at org.apache.tools.zip.ZipFile.(ZipFile.java:163)
at 
org.apache.tools.ant.types.resources.ZipResource.getInputStream(ZipResource.java:133)
at 
org.apache.tools.ant.types.resources.ResourceDecorator.getInputStream(ResourceDecorator.java:125)
at org.apache.tools.ant.taskdefs.Zip.addResource(Zip.java:1041)
at org.apache.tools.ant.taskdefs.Zip.addResources(Zip.java:1098)
at org.apache.tools.ant.taskdefs.Zip.executeMain(Zip.java:665)
- show quoted text -

On Tuesday, February 21, 2017 at 9:22:35 AM UTC-5, Prasu S wrote:
I upgraded Jenkins from 1.607 to 1.658 , after the upgrade credentials plugin 
1.18 is missing. Due to this, we are  not able to get code from Github. When I 
tried to re-install the same version(1.18) , it is still not showing under 
installed plugin list.  How can I recover credential plugin. Any help is 
greatly appreciated. Thank you
--
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/cfc2ee75-6bd1-46de-a3c8-d1664958d822%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/E21B7494-7343-4856-B181-542DE8993A9D%40cisco.com.
For more options, visit https://groups.google.com/d/optout.

Re: credential plugin disappears after Jenkins upgrade to 1.658

2017-02-21 Thread Prasu S

I have plugins directory back up , Can I copy the plugin from the backup or 
do I have to install different plugin version like 1.22. Please help. 
Appreciate any help.


I see these errors in the log:
***
SEVERE: Failed Inspecting plugin 
D:\Build\Jenkins\apps\jenkins\jenkins_home\plugins\credentials.jpi
java.io.IOException: Failed to expand 
D:\Build\Jenkins\apps\jenkins\jenkins_home\plugins\credentials.jpi
at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:532)
at 
hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:167)
at hudson.PluginManager$1$3$1.run(PluginManager.java:288)
at 
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$8.runTask(Jenkins.java:958)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: Problem creating zip: null
at org.apache.tools.ant.taskdefs.Zip.executeMain(Zip.java:741)
at org.apache.tools.ant.taskdefs.Zip.execute(Zip.java:568)
at 
hudson.ClassicPluginStrategy.createClassJarFromWebInfClasses(ClassicPluginStrategy.java:589)
at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:530)
... 10 more
Caused by: java.io.EOFException
at java.io.RandomAccessFile.readFully(RandomAccessFile.java:446)
at java.io.RandomAccessFile.readFully(RandomAccessFile.java:424)
at org.apache.tools.zip.ZipFile.resolveLocalFileHeaderData(ZipFile.java:522)
at org.apache.tools.zip.ZipFile.(ZipFile.java:187)
at org.apache.tools.zip.ZipFile.(ZipFile.java:163)
at 
org.apache.tools.ant.types.resources.ZipResource.getInputStream(ZipResource.java:133)
at 
org.apache.tools.ant.types.resources.ResourceDecorator.getInputStream(ResourceDecorator.java:125)
at org.apache.tools.ant.taskdefs.Zip.addResource(Zip.java:1041)
at org.apache.tools.ant.taskdefs.Zip.addResources(Zip.java:1098)
at org.apache.tools.ant.taskdefs.Zip.executeMain(Zip.java:665)
- show quoted text -

On Tuesday, February 21, 2017 at 9:22:35 AM UTC-5, Prasu S wrote:
>
> I upgraded Jenkins from 1.607 to 1.658 , after the upgrade credentials 
> plugin 1.18 is missing. Due to this, we are  not able to get code from 
> Github. When I tried to re-install the same version(1.18) , it is still not 
> showing under installed plugin list.  How can I recover credential plugin. 
> Any help is greatly appreciated. Thank you
>

-- 
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/cfc2ee75-6bd1-46de-a3c8-d1664958d822%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Workspace root directory (Jenkinsfile)

I have tried d:/${ITEM_FULLNAME} - no luck

I also just tried ${JENKINS_HOME}/TEST/${ITEM_FULLNAME}

note default is: ${JENKINS_HOME}/workspace/${ITEM_FULLNAME}

I created TEST directory under jenkins home same root that workspace exists 
- still ignored.

Running on master in C:\Program Files 
(x86)\Jenkins\workspace\i_api.asicentral.com_master-BLRHPIOJSBVARDRRLSJX5OHVKMDV5UTXULFID5BU57E37BSQ

On Tuesday, February 21, 2017 at 2:13:47 PM UTC-5, Jérôme Godbout wrote:
>
> can you try d:/${ITEM_FULLNAME}
>
> reverse the backslash just in case...
>
> [image: bodycad]  
> Jerome Godbout
> Software Developer
> 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
> T:  +1 418 527-1388
> E: jer...@bodycad.com 
> www.bodycad.com
>
> The contents of this email message and any attachments are intended solely 
> for the addressee(s) and may contain confidential and/or privileged 
> information and may be legally protected from disclosure. If you are not 
> the intended recipient of this message or their agent, or if this message 
> has been addressed to you in error, please immediately alert the sender by 
> reply email and then delete this message and any attachments. If you are 
> not the intended recipient, you are hereby notified that any use, 
> dissemination, copying, or storage of this message or its attachments is 
> strictly prohibited. 
>
> Le contenu de ce message et les pièces jointes sont destinés uniquement 
> pour le(s) destinataire(s) et peuvent contenir des informations 
> confidentielles et / ou privilégiées qui peuvent être protégées légalement 
> contre toute divulgation. Si vous n'êtes pas le destinataire de ce message 
> ou son agent, ou si ce message vous a été adressé par erreur, s’il vous 
> plaît avertir immédiatement l'expéditeur par courriel de réponse, puis 
> supprimer ce message et les pièces jointes. Si vous n'êtes pas le 
> destinataire prévu, vous êtes par la présente informé que toute 
> utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces 
> jointes est strictement interdit.
>
> On Tue, Feb 21, 2017 at 2:12 PM, Ryan Hutchison  > wrote:
>
>> Global configuration workspace root directory is set to 
>> D:\${ITEM_FULLNAME}
>>
>> D: is a physical disk.
>>
>> Service recycled.
>>
>> LOG:
>> Running on asi-bldcn02-01 in C:\Program Files 
>> (x86)\Jenkins\workspace\i_api.asicentral.com_master-BLRHPIOJSBVARDRRLSJX5OHVKMDV5UTXULFID5BU57E37BSQ
>>
>> Versions:
>> Jenkins 2.47
>> Pipeline 2.5
>>
>> Setup using Github Organization/Multibranch pipeline
>>
>>
>> On Tuesday, February 21, 2017 at 1:50:40 PM UTC-5, Ryan Hutchison wrote:
>>>
>>> Thanks - I will check everything again and try to recycle the service.
>>>
>>> I am simply mapping to D:\${ITEM_FULLNAME} - where D: is a physical disk.
>>>
>>> On Tuesday, February 21, 2017 at 1:45:38 PM UTC-5, Jérôme Godbout wrote:

 Have you try to restart the Jenkins server so it can take into account 
 this new path? If so, which version, cause if the path is truly valid, it 
 should work?

 I have a Window server which was working fine with another drive. Just 
 a note, if the other drive is a network drive, make sure your Jenkins 
 services can access it (I strongly recommend avoiding this, this is a 
 pain).

 I think (if I remember well) if the path is invalid Jenkins default 
 back to the default value for the workspace, but I might be wrong on this.

 Make sure the folder exist with proper (case sensitive???)

 [image: bodycad]  
 Jerome Godbout
 Software Developer
 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
 T:  +1 418 527-1388
 E: jer...@bodycad.com
 www.bodycad.com

 The contents of this email message and any attachments are intended 
 solely for the addressee(s) and may contain confidential and/or privileged 
 information and may be legally protected from disclosure. If you are not 
 the intended recipient of this message or their agent, or if this message 
 has been addressed to you in error, please immediately alert the sender by 
 reply email and then delete this message and any attachments. If you are 
 not the intended recipient, you are hereby notified that any use, 
 dissemination, copying, or storage of this message or its attachments is 
 strictly prohibited. 

 Le contenu de ce message et les pièces jointes sont destinés uniquement 
 pour le(s) destinataire(s) et peuvent contenir des informations 
 confidentielles et / ou privilégiées qui peuvent être protégées légalement 
 contre toute divulgation. Si vous n'êtes pas le destinataire de ce message 
 ou son agent, ou si ce message vous a été adressé par erreur, s’il vous 
 plaît avertir immédiatement l'expéditeur par courriel de réponse, puis 
 supprimer ce message et les pièces jointes. Si vous n'êtes pas le

Re: Workspace root directory (Jenkinsfile)

can you try d:/${ITEM_FULLNAME}

reverse the backslash just in case...

[image: bodycad] 
Jerome Godbout
Software Developer
2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
T:  +1 418 527-1388
E: jer...@bodycad.com
www.bodycad.com

The contents of this email message and any attachments are intended solely
for the addressee(s) and may contain confidential and/or privileged
information and may be legally protected from disclosure. If you are not
the intended recipient of this message or their agent, or if this message
has been addressed to you in error, please immediately alert the sender by
reply email and then delete this message and any attachments. If you are
not the intended recipient, you are hereby notified that any use,
dissemination, copying, or storage of this message or its attachments is
strictly prohibited.

Le contenu de ce message et les pièces jointes sont destinés uniquement
pour le(s) destinataire(s) et peuvent contenir des informations
confidentielles et / ou privilégiées qui peuvent être protégées légalement
contre toute divulgation. Si vous n'êtes pas le destinataire de ce message
ou son agent, ou si ce message vous a été adressé par erreur, s’il vous
plaît avertir immédiatement l'expéditeur par courriel de réponse, puis
supprimer ce message et les pièces jointes. Si vous n'êtes pas le
destinataire prévu, vous êtes par la présente informé que toute
utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces
jointes est strictement interdit.

On Tue, Feb 21, 2017 at 2:12 PM, Ryan Hutchison 
wrote:

> Global configuration workspace root directory is set to D:\${ITEM_FULLNAME}
>
> D: is a physical disk.
>
> Service recycled.
>
> LOG:
> Running on asi-bldcn02-01 in C:\Program Files
> (x86)\Jenkins\workspace\i_api.asicentral.com_master-
> BLRHPIOJSBVARDRRLSJX5OHVKMDV5UTXULFID5BU57E37BSQ
>
> Versions:
> Jenkins 2.47
> Pipeline 2.5
>
> Setup using Github Organization/Multibranch pipeline
>
>
> On Tuesday, February 21, 2017 at 1:50:40 PM UTC-5, Ryan Hutchison wrote:
>>
>> Thanks - I will check everything again and try to recycle the service.
>>
>> I am simply mapping to D:\${ITEM_FULLNAME} - where D: is a physical disk.
>>
>> On Tuesday, February 21, 2017 at 1:45:38 PM UTC-5, Jérôme Godbout wrote:
>>>
>>> Have you try to restart the Jenkins server so it can take into account
>>> this new path? If so, which version, cause if the path is truly valid, it
>>> should work?
>>>
>>> I have a Window server which was working fine with another drive. Just a
>>> note, if the other drive is a network drive, make sure your Jenkins
>>> services can access it (I strongly recommend avoiding this, this is a pain).
>>>
>>> I think (if I remember well) if the path is invalid Jenkins default back
>>> to the default value for the workspace, but I might be wrong on this.
>>>
>>> Make sure the folder exist with proper (case sensitive???)
>>>
>>> [image: bodycad] 
>>> Jerome Godbout
>>> Software Developer
>>> 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
>>> T:  +1 418 527-1388 <(418)%20527-1388>
>>> E: jer...@bodycad.com
>>> www.bodycad.com
>>>
>>> The contents of this email message and any attachments are intended
>>> solely for the addressee(s) and may contain confidential and/or privileged
>>> information and may be legally protected from disclosure. If you are not
>>> the intended recipient of this message or their agent, or if this message
>>> has been addressed to you in error, please immediately alert the sender by
>>> reply email and then delete this message and any attachments. If you are
>>> not the intended recipient, you are hereby notified that any use,
>>> dissemination, copying, or storage of this message or its attachments is
>>> strictly prohibited.
>>>
>>> Le contenu de ce message et les pièces jointes sont destinés uniquement
>>> pour le(s) destinataire(s) et peuvent contenir des informations
>>> confidentielles et / ou privilégiées qui peuvent être protégées légalement
>>> contre toute divulgation. Si vous n'êtes pas le destinataire de ce message
>>> ou son agent, ou si ce message vous a été adressé par erreur, s’il vous
>>> plaît avertir immédiatement l'expéditeur par courriel de réponse, puis
>>> supprimer ce message et les pièces jointes. Si vous n'êtes pas le
>>> destinataire prévu, vous êtes par la présente informé que toute
>>> utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces
>>> jointes est strictement interdit.
>>>
>>> On Tue, Feb 21, 2017 at 1:39 PM, Ryan Hutchison 
>>> wrote:
>>>
 I have changed the Workspace Root Directory, but it seems like if
 you're using Pipeline As Code / Jenkinsfile, it ignores this variable.

 On Tuesday, February 21, 2017 at 12:13:53 PM UTC-5, jer...@bodycad.com
 wrote:
>
> What I have found so far:
>
> Inside the Jenkins management you can change the Workspace directory.
>

Re: Workspace root directory (Jenkinsfile)

Global configuration workspace root directory is set to D:\${ITEM_FULLNAME}

D: is a physical disk.

Service recycled.

LOG:
Running on asi-bldcn02-01 in C:\Program Files 
(x86)\Jenkins\workspace\i_api.asicentral.com_master-BLRHPIOJSBVARDRRLSJX5OHVKMDV5UTXULFID5BU57E37BSQ

Versions:
Jenkins 2.47
Pipeline 2.5

Setup using Github Organization/Multibranch pipeline


On Tuesday, February 21, 2017 at 1:50:40 PM UTC-5, Ryan Hutchison wrote:
>
> Thanks - I will check everything again and try to recycle the service.
>
> I am simply mapping to D:\${ITEM_FULLNAME} - where D: is a physical disk.
>
> On Tuesday, February 21, 2017 at 1:45:38 PM UTC-5, Jérôme Godbout wrote:
>>
>> Have you try to restart the Jenkins server so it can take into account 
>> this new path? If so, which version, cause if the path is truly valid, it 
>> should work?
>>
>> I have a Window server which was working fine with another drive. Just a 
>> note, if the other drive is a network drive, make sure your Jenkins 
>> services can access it (I strongly recommend avoiding this, this is a pain).
>>
>> I think (if I remember well) if the path is invalid Jenkins default back 
>> to the default value for the workspace, but I might be wrong on this.
>>
>> Make sure the folder exist with proper (case sensitive???)
>>
>> [image: bodycad]  
>> Jerome Godbout
>> Software Developer
>> 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
>> T:  +1 418 527-1388
>> E: jer...@bodycad.com
>> www.bodycad.com
>>
>> The contents of this email message and any attachments are intended 
>> solely for the addressee(s) and may contain confidential and/or privileged 
>> information and may be legally protected from disclosure. If you are not 
>> the intended recipient of this message or their agent, or if this message 
>> has been addressed to you in error, please immediately alert the sender by 
>> reply email and then delete this message and any attachments. If you are 
>> not the intended recipient, you are hereby notified that any use, 
>> dissemination, copying, or storage of this message or its attachments is 
>> strictly prohibited. 
>>
>> Le contenu de ce message et les pièces jointes sont destinés uniquement 
>> pour le(s) destinataire(s) et peuvent contenir des informations 
>> confidentielles et / ou privilégiées qui peuvent être protégées légalement 
>> contre toute divulgation. Si vous n'êtes pas le destinataire de ce message 
>> ou son agent, ou si ce message vous a été adressé par erreur, s’il vous 
>> plaît avertir immédiatement l'expéditeur par courriel de réponse, puis 
>> supprimer ce message et les pièces jointes. Si vous n'êtes pas le 
>> destinataire prévu, vous êtes par la présente informé que toute 
>> utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces 
>> jointes est strictement interdit.
>>
>> On Tue, Feb 21, 2017 at 1:39 PM, Ryan Hutchison  
>> wrote:
>>
>>> I have changed the Workspace Root Directory, but it seems like if you're 
>>> using Pipeline As Code / Jenkinsfile, it ignores this variable.
>>>
>>> On Tuesday, February 21, 2017 at 12:13:53 PM UTC-5, jer...@bodycad.com 
>>> wrote:

 What I have found so far:

 Inside the Jenkins management you can change the Workspace directory. 


1. http://MY_HOST/Jenkins/configure
2. Right under the home directory into advanced button.
3. Workspace Root Directory 
  ${JENKINS_HOME}/workspace/${ITEM_FULLNAME}

 you could change it for something short indeed like  D:/work
 I had the same problems with the zip archiving under Windows. The 256 
 char path limits is a pain. Keep your job project short, use description 
 for more info. Try to avoid too many job folder under Windows since it 
 does 
 create 2 folder deep /job/name every time.

 -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Jenkins Users" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-users/Us_sfZTgJgk/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/6e769449-4b67-4b36-8a7f-3c60f5c73fdd%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

Re: Workspace root directory (Jenkinsfile)

The drive you see into the user account and the one a services can access
are 2 different thing under Windows, try with another path on a local drive
after that you will pinpoint the drive usage with the service if this work
properly.

If so here some information that can be useful

net use \\10.1.1.10\mypath /savecred /user:MyUserName MyPassword

According to http://support.microsoft.com/kb/287536 try using the following
instead, seem like giving the password may prevent the credential creation
even if /savecred switch is given. Use * for password so the password get a
prompt, it should always create the credential with that.

net use * \\10.1.1.10\mypath /savecred /user:MyUserName

Mount Drive for deamon or services

   1. download the
   http://technet.microsoft.com/en-us/sysinternals/bb842062.aspx
   2. install the tools
   3. open a cmd.exe
   4. type psexec -i -s cmd.exe
   1. into new shell type whoami
  2. should see: nt authority\system
  3. mount the drive with net use see above
  4. if you ever need to unmount the drive into the same psexec
  5. net use z: /delete

[image: bodycad] 
Jerome Godbout
Software Developer
2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
T:  +1 418 527-1388
E: jer...@bodycad.com
www.bodycad.com

The contents of this email message and any attachments are intended solely
for the addressee(s) and may contain confidential and/or privileged
information and may be legally protected from disclosure. If you are not
the intended recipient of this message or their agent, or if this message
has been addressed to you in error, please immediately alert the sender by
reply email and then delete this message and any attachments. If you are
not the intended recipient, you are hereby notified that any use,
dissemination, copying, or storage of this message or its attachments is
strictly prohibited.

Le contenu de ce message et les pièces jointes sont destinés uniquement
pour le(s) destinataire(s) et peuvent contenir des informations
confidentielles et / ou privilégiées qui peuvent être protégées légalement
contre toute divulgation. Si vous n'êtes pas le destinataire de ce message
ou son agent, ou si ce message vous a été adressé par erreur, s’il vous
plaît avertir immédiatement l'expéditeur par courriel de réponse, puis
supprimer ce message et les pièces jointes. Si vous n'êtes pas le
destinataire prévu, vous êtes par la présente informé que toute
utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces
jointes est strictement interdit.

On Tue, Feb 21, 2017 at 1:47 PM, Ryan Hutchison 
wrote:

> I can map the path with SUBST, but I still end up with
> :\workspace -- ideally this could still be shorter.
>
> I also then have to map a drive X:\ -> C:\Program Files (x86)\Jenkins and
> then C:\Program Files (x86)\Jenkins\workspace -> D:\ (ugh)
>
> RE: OS, I wish I was able to share the same luxury
>
> On Tuesday, February 21, 2017 at 11:04:49 AM UTC-5, j.spriggs wrote:
>>
>> Hi Ryan,
>>
>>
>>
>> Been there.
>>
>>
>>
>> How about setting your JENKINS_HOME to something shorter before you start
>> the jenkins server?
>>
>>
>>
>> For instance, this works for me:
>>
>>
>>
>> JENKINS_HOME=”/jk”  java  -jar  jenkins.war
>>
>>
>>
>> [ Obviously, I enjoy the luxury of a sensible OS. ;-) ]
>>
>>
>>
>> See the notes at the top of the “Manage Jenkins|Configure System” page
>> for more info.
>>
>>
>>
>> Good Luck!
>>
>> --
>>
>> jim
>>
>>
>>
>> *Von:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *Im
>> Auftrag von *Ryan Hutchison
>> *Gesendet:* Dienstag, 21. Februar 2017 16:38
>> *An:* jenkins...@googlegroups.com
>> *Betreff:* Workspace root directory (Jenkinsfile)
>>
>>
>>
>> My JENKINS_HOME is C:\Program Files (x86)\Jenkins
>>
>>
>>
>> I have allocated a separate drive for my workspace `D:\` and modified the
>> global workspace property to reflect this new location.
>>
>>
>>
>> When my build job runs (Jenkinsfile), it always goes to
>> ${JENKINS_HOME}\workspace.
>>
>>
>>
>> My issue is that msbuild ends up failing due to long file names/paths.
>> It does not help that the randomly generated ${ITEM_FULLNAME} is quite long
>> by itself.
>>
>>
>>
>> Any thoughts or pointers would be appreciated.
>>
>>
>>
>> --
>> 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/ms
>> gid/jenkinsci-users/CAFFG4vjXshWaTHe7hzuqDw890Q20DU2zS01pf3D
>> VeQGSubvPbg%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>>
>> RAYLASE AG
>>

Re: Workspace root directory (Jenkinsfile)

Thanks - I will check everything again and try to recycle the service.

I am simply mapping to D:\${ITEM_FULLNAME} - where D: is a physical disk.

On Tuesday, February 21, 2017 at 1:45:38 PM UTC-5, Jérôme Godbout wrote:
>
> Have you try to restart the Jenkins server so it can take into account 
> this new path? If so, which version, cause if the path is truly valid, it 
> should work?
>
> I have a Window server which was working fine with another drive. Just a 
> note, if the other drive is a network drive, make sure your Jenkins 
> services can access it (I strongly recommend avoiding this, this is a pain).
>
> I think (if I remember well) if the path is invalid Jenkins default back 
> to the default value for the workspace, but I might be wrong on this.
>
> Make sure the folder exist with proper (case sensitive???)
>
> [image: bodycad]  
> Jerome Godbout
> Software Developer
> 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
> T:  +1 418 527-1388
> E: jer...@bodycad.com 
> www.bodycad.com
>
> The contents of this email message and any attachments are intended solely 
> for the addressee(s) and may contain confidential and/or privileged 
> information and may be legally protected from disclosure. If you are not 
> the intended recipient of this message or their agent, or if this message 
> has been addressed to you in error, please immediately alert the sender by 
> reply email and then delete this message and any attachments. If you are 
> not the intended recipient, you are hereby notified that any use, 
> dissemination, copying, or storage of this message or its attachments is 
> strictly prohibited. 
>
> Le contenu de ce message et les pièces jointes sont destinés uniquement 
> pour le(s) destinataire(s) et peuvent contenir des informations 
> confidentielles et / ou privilégiées qui peuvent être protégées légalement 
> contre toute divulgation. Si vous n'êtes pas le destinataire de ce message 
> ou son agent, ou si ce message vous a été adressé par erreur, s’il vous 
> plaît avertir immédiatement l'expéditeur par courriel de réponse, puis 
> supprimer ce message et les pièces jointes. Si vous n'êtes pas le 
> destinataire prévu, vous êtes par la présente informé que toute 
> utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces 
> jointes est strictement interdit.
>
> On Tue, Feb 21, 2017 at 1:39 PM, Ryan Hutchison  > wrote:
>
>> I have changed the Workspace Root Directory, but it seems like if you're 
>> using Pipeline As Code / Jenkinsfile, it ignores this variable.
>>
>> On Tuesday, February 21, 2017 at 12:13:53 PM UTC-5, jer...@bodycad.com 
>> wrote:
>>>
>>> What I have found so far:
>>>
>>> Inside the Jenkins management you can change the Workspace directory. 
>>>
>>>
>>>1. http://MY_HOST/Jenkins/configure
>>>2. Right under the home directory into advanced button.
>>>3. Workspace Root Directory 
>>>  ${JENKINS_HOME}/workspace/${ITEM_FULLNAME}
>>>
>>> you could change it for something short indeed like  D:/work
>>> I had the same problems with the zip archiving under Windows. The 256 
>>> char path limits is a pain. Keep your job project short, use description 
>>> for more info. Try to avoid too many job folder under Windows since it does 
>>> create 2 folder deep /job/name every time.
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Users" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-users/Us_sfZTgJgk/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/6e769449-4b67-4b36-8a7f-3c60f5c73fdd%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/d35b4e2f-c606-429e-9c25-db15cab020a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Slave Container accessing GitHub private repository via SSH keys

2017-02-21 Thread Matthew Ceroni

Running into issues checking out a private repository within a slave 
container. 

To start, I created a SSH username + private key credential. The private 
key has been verified to work against the GitHub organization I am 
attempting to clone repositories from.

My pipeline looks like such:

import groovy.json.JsonSlurper

@NonCPS
def parseResponse(response) {
def list = new JsonSlurper().parseText( response )

def repositories = []
for (Map item : list) {
repositories.push(item.ssh_url)
//println "${item.ssh_url}"
}
return repositories
}

podTemplate(label: 'mypod', containers: [
containerTemplate(name: 'golang', image: 'golang:1.6.3', ttyEnabled: 
true, command: 'cat')
  ]) {

node ('mypod') {
stage 'Find Repositories'

// make call to GitHub API to list all repositories for project
def response = httpRequest 
"https://api.github.com/teams//repos?access_token=x;

// parse the response and write out a file containing the list of 
repositories
def repositories = parseResponse(response.content)

container('golang') {
stage 'Checkout Repositories'

for (String item : repositories) {
git branch: 'master', credentialsId: 
'7f66557f-8ee3-4d69-b271-f8b1bbfa02b0', url: item
println item
}

sh """
sleep 600
"""

}

}
}

Basically, I query all the repositories that are part of a team and then 
want to loop over those and perform some action. But the git call fails 
with the following:

[Pipeline] gitCloning the remote Git repository
Cloning repository g...@github.com:X/activeMqMessageQueueing.git
 > git init /home/jenkins/workspace/DevOps/git-hooks # timeout=10
Fetching upstream changes from 
g...@github.com:XX/activeMqMessageQueueing.git
 > git --version # timeout=10
using GIT_SSH to set credentials s-automation GitHub SSH key
 > git fetch --tags --progress 
 > g...@github.com:X/activeMqMessageQueueing.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException 
:
 Command "git fetch --tags --progress 
g...@github.com:/activeMqMessageQueueing.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: /tmp/ssh7121108186801417889.sh: line 6: ssh: not found
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.



So it appears to set the credentials correctly (using GIT_SSH to set 
credentials to s-automation GitHub SSH key) but then complains SSH not 
found. The container that this part of the pipeline runs in has SSH so not 
sure why it would complain about that. I would love to be able to see what 
is in  /tmp/ssh7121108186801417889.sh but the job fails and the container 
dies at that point. 

Kind of stuck where to go from here. Any assistance would be appreciated.

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/d911f54f-149b-42d2-94ed-d1f4a94e2d37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Workspace root directory (Jenkinsfile)

I can map the path with SUBST, but I still end up with 
:\workspace -- ideally this could still be shorter.

I also then have to map a drive X:\ -> C:\Program Files (x86)\Jenkins and 
then C:\Program Files (x86)\Jenkins\workspace -> D:\ (ugh)

RE: OS, I wish I was able to share the same luxury

On Tuesday, February 21, 2017 at 11:04:49 AM UTC-5, j.spriggs wrote:
>
> Hi Ryan,
>
>  
>
> Been there.
>
>  
>
> How about setting your JENKINS_HOME to something shorter before you start 
> the jenkins server?
>
>  
>
> For instance, this works for me:
>
>  
>
> JENKINS_HOME=”/jk”  java  -jar  jenkins.war
>
>  
>
> [ Obviously, I enjoy the luxury of a sensible OS. ;-) ]
>
>  
>
> See the notes at the top of the “Manage Jenkins|Configure System” page for 
> more info.
>
>  
>
> Good Luck!
>
> --
>
> jim
>
>  
>
> *Von:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *Im Auftrag von *Ryan Hutchison
> *Gesendet:* Dienstag, 21. Februar 2017 16:38
> *An:* jenkins...@googlegroups.com 
> *Betreff:* Workspace root directory (Jenkinsfile)
>
>  
>
> My JENKINS_HOME is C:\Program Files (x86)\Jenkins
>
>  
>
> I have allocated a separate drive for my workspace `D:\` and modified the 
> global workspace property to reflect this new location.
>
>  
>
> When my build job runs (Jenkinsfile), it always goes to 
> ${JENKINS_HOME}\workspace.
>
>  
>
> My issue is that msbuild ends up failing due to long file names/paths.  It 
> does not help that the randomly generated ${ITEM_FULLNAME} is quite long by 
> itself.
>
>  
>
> Any thoughts or pointers would be appreciated.
>
>  
>
> -- 
> 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/CAFFG4vjXshWaTHe7hzuqDw890Q20DU2zS01pf3DVeQGSubvPbg%40mail.gmail.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
>
> RAYLASE AG
> Argelsrieder Feld 2+4
> 82234 Wessling
> Germany
> Tel.: +49-(0)8153/88 98-0
> Fax: +49-(0)8153/88 98-10
> http://www.raylase.de
>
> District Court Munich, HRB 131450
>
> Board: Dr. Philipp Schön (Chairman), Berthold Dambacher, Christoph von Jan
>
> Supervisory Board: Dr. Ulrich Lohmann (Chairman)
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und 
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
> Weitergabe dieser Mail ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error) 
> please notify the sender immediately and destroy this e-mail. Any 
> unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden.
>

-- 
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/c33792b9-2540-49e9-8b95-610e6efa5ae4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Workspace root directory (Jenkinsfile)

Have you try to restart the Jenkins server so it can take into account this
new path? If so, which version, cause if the path is truly valid, it should
work?

I have a Window server which was working fine with another drive. Just a
note, if the other drive is a network drive, make sure your Jenkins
services can access it (I strongly recommend avoiding this, this is a pain).

I think (if I remember well) if the path is invalid Jenkins default back to
the default value for the workspace, but I might be wrong on this.

Make sure the folder exist with proper (case sensitive???)

[image: bodycad] 
Jerome Godbout
Software Developer
2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
T:  +1 418 527-1388
E: jer...@bodycad.com
www.bodycad.com

The contents of this email message and any attachments are intended solely
for the addressee(s) and may contain confidential and/or privileged
information and may be legally protected from disclosure. If you are not
the intended recipient of this message or their agent, or if this message
has been addressed to you in error, please immediately alert the sender by
reply email and then delete this message and any attachments. If you are
not the intended recipient, you are hereby notified that any use,
dissemination, copying, or storage of this message or its attachments is
strictly prohibited.

Le contenu de ce message et les pièces jointes sont destinés uniquement
pour le(s) destinataire(s) et peuvent contenir des informations
confidentielles et / ou privilégiées qui peuvent être protégées légalement
contre toute divulgation. Si vous n'êtes pas le destinataire de ce message
ou son agent, ou si ce message vous a été adressé par erreur, s’il vous
plaît avertir immédiatement l'expéditeur par courriel de réponse, puis
supprimer ce message et les pièces jointes. Si vous n'êtes pas le
destinataire prévu, vous êtes par la présente informé que toute
utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces
jointes est strictement interdit.

On Tue, Feb 21, 2017 at 1:39 PM, Ryan Hutchison 
wrote:

> I have changed the Workspace Root Directory, but it seems like if you're
> using Pipeline As Code / Jenkinsfile, it ignores this variable.
>
> On Tuesday, February 21, 2017 at 12:13:53 PM UTC-5, jer...@bodycad.com
> wrote:
>>
>> What I have found so far:
>>
>> Inside the Jenkins management you can change the Workspace directory.
>>
>>
>>1. http://MY_HOST/Jenkins/configure
>>2. Right under the home directory into advanced button.
>>3. Workspace Root Directory   ${JENKINS_HOME}/workspace/${
>>ITEM_FULLNAME}
>>
>> you could change it for something short indeed like  D:/work
>> I had the same problems with the zip archiving under Windows. The 256
>> char path limits is a pain. Keep your job project short, use description
>> for more info. Try to avoid too many job folder under Windows since it does
>> create 2 folder deep /job/name every time.
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-users/Us_sfZTgJgk/unsubscribe.
> To unsubscribe from this group and all its topics, 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/6e769449-4b67-4b36-8a7f-3c60f5c73fdd%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/CAKmu%2Be3-KidSUZ3iMbSVZsM6LA6s06MFZ24BfCDrQjZ%2B3e9paw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Workspace root directory (Jenkinsfile)

I have changed the Workspace Root Directory, but it seems like if you're 
using Pipeline As Code / Jenkinsfile, it ignores this variable.

On Tuesday, February 21, 2017 at 12:13:53 PM UTC-5, jer...@bodycad.com 
wrote:
>
> What I have found so far:
>
> Inside the Jenkins management you can change the Workspace directory. 
>
>
>1. http://MY_HOST/Jenkins/configure
>2. Right under the home directory into advanced button.
>3. Workspace Root Directory 
>  ${JENKINS_HOME}/workspace/${ITEM_FULLNAME}
>
> you could change it for something short indeed like  D:/work
> I had the same problems with the zip archiving under Windows. The 256 char 
> path limits is a pain. Keep your job project short, use description for 
> more info. Try to avoid too many job folder under Windows since it does 
> create 2 folder deep /job/name every time.
>
>

-- 
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/6e769449-4b67-4b36-8a7f-3c60f5c73fdd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoSuchMethodError: No such DSL method 'salt' found among steps

2017-02-21 Thread Indra Gunawan (ingunawa)

Check first if you have installed the saltstack-plugin version that supports 
pipeline.  Please verify that the plugin with pipeline support dependencies are 
met.
Observe anything that might be printed out in Jenkins log file related to 
saltstack-plugin.

-Indra


From:  on behalf of Rustan Capal 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Tuesday, February 21, 2017 at 10:01 AM
To: Jenkins Users 
Subject: Re: java.lang.NoSuchMethodError: No such DSL method 'salt' found among 
steps

Saltstack Plugin Installed: 
https://wiki.jenkins-ci.org/display/JENKINS/saltstack-plugin


On Wednesday, February 22, 2017 at 1:54:17 AM UTC+8, Rustan Capal wrote:
Hi Everyone,

Can anyone tell me what I'm missing here? Salt API already installed. Jenkins 
version: 2.32.2

[PIPELINE SCRIPT]

import groovy.json.*

node() {
  saltresult = salt authtype: 'pam', clientInterface: local(arguments: '"uname 
-r"', blockbuild: true,
function: 'cmd.run', jobPollTime: 16, target: '*', targetType: 'glob'),
credentialsId: 'c58c819b-89f2-4400-bb94-1ec79920adb4', servername: 
'http://10.10.214.233:8181'
  def prettyJson = JsonOutput.prettyPrint(saltresult)
  println(prettyJson)
}


[BUILD OUTPUT]

[Pipeline] node

Running on master in /var/lib/jenkins/workspace/hello-world-pipeline-saltstack

[Pipeline] {

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline

java.lang.NoSuchMethodError: No such DSL method 'salt' found among steps 
[ansiColor, archive, bat, build, catchError, checkout, deleteDir, dir, 
dockerFingerprintFrom, dockerFingerprintRun, echo, emailext, 
emailextrecipients, error, exws, exwsAllocate, fileExists, findFiles, 
getContext, git, input, isUnix, libraryResource, load, mail, milestone, node, 
parallel, properties, pwd, readFile, readManifest, readMavenPom, 
readProperties, readTrusted, readYaml, retry, sh, sleep, stage, stash, step, 
svn, timeout, timestamps, tool, touch, unarchive, unstash, unzip, waitUntil, 
withContext, withCredentials, withDockerContainer, withDockerRegistry, 
withDockerServer, withEnv, wrap, writeFile, writeMavenPom, ws, zip] or symbols 
[all, always, ant, antFromApache, antOutcome, antTarget, apiToken, 
architecture, archiveArtifacts, artifactManager, batchFile, booleanParam, 
buildButton, buildDiscarder, caseInsensitive, caseSensitive, choice, 
choiceParam, clock, cloud, command, configFile, configFileProvider, cron, 
crumb, defaultView, demand, disableConcurrentBuilds, downloadSettings, 
downstream, dumb, envVars, fastestReadSpeed, fastestWriteSpeed, file, 
fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, git, 
hyperlink, hyperlinkToModels, installSource, jdk, jdkInstaller, jgit, 
jgitapache, jnlp, jobName, junit, lastDuration, lastFailure, 
lastGrantedAuthorities, lastStable, lastSuccess, legacy, list, local, location, 
logRotator, loggedInUsersCanDoAnything, masterBuild, maven, maven3Mojos, 
mavenErrors, mavenMojos, mavenWarnings, mostUsableSpace, myView, 
nodeProperties, nonStoredPasswordParam, none, overrideIndexTriggers, 
paneStatus, parameters, password, pattern, pipelineTriggers, plainText, plugin, 
pollSCM, projectNamingStrategy, proxy, queueItemAuthenticator, quietPeriod, 
run, runParam, schedule, scmRetryCount, search, security, shell, slave, 
stackTrace, standard, status, string, stringParam, swapSpace, text, textParam, 
tmpSpace, toolLocation, unsecured, upstream, usernameColonPassword, 
usernamePassword, viewsTabBar, weather, zfs, zip] or globals [currentBuild, 
docker, env, params, scm, simpleBuild]

  at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:149)

  at 
org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108)

  at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source)

  at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)

  at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)

  at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151)

  at 
org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21)

  at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115)

  at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149)

  at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146)

  at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123)

  at 
com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16)

  at WorkflowScript.run(WorkflowScript:4)

  at ___cps.transform___(Native Method)

  at 
com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)

  at

Jenkins build says successful but no output is seen

2017-02-21 Thread Sharan Basappa



My Jenkins build job indicates success but none of the scripts I am 
executing seem to do anything. I put a simple "pwd" command to echo current 
working directory but nothing happens. All Jenkins reports is "Running 
shell script" and then nothing is seen.

Snippet of Jenkins log:

First time build. Skipping changelog. [Pipeline] sh [an_example_test3-
26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A] Running shell script [
Pipeline] sh [an_example_test3-
26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A] Running shell script [
Pipeline] sh [an_example_test3-
26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A] Running shell script [
Pipeline] sh [an_example_test3-
26UQSYQ445FSBP4QRKEWLPQCJH545MLQVD6B552CIGPOXLZO4G5A] Running shell script [
Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS


Jenkinsfile that is used to define the builds:

node { stage 'build' sh "echo ${env.BRANCH_NAME}" git url: 'git@hd1:testing'
, branch: "${env.BRANCH_NAME}" sh "ls -rtl" sh "pwd" sh "csh 
${workspace}/simple.csh" sh "csh ${workspace}/source.csh" }



-- 
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/264cf466-6de8-4afe-8d16-b5b40713955d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoSuchMethodError: No such DSL method 'salt' found among steps

Saltstack Plugin Installed: 
https://wiki.jenkins-ci.org/display/JENKINS/saltstack-plugin


On Wednesday, February 22, 2017 at 1:54:17 AM UTC+8, Rustan Capal wrote:
>
> Hi Everyone,
>
> Can anyone tell me what I'm missing here? Salt API already installed. 
> Jenkins version: 2.32.2
>
>
>
> *[PIPELINE SCRIPT]*import groovy.json.*
>
> node() {
>   saltresult = salt authtype: 'pam', clientInterface: local(arguments: 
> '"uname -r"', blockbuild: true, 
> function: 'cmd.run', jobPollTime: 16, target: '*', targetType: 
> 'glob'), 
> credentialsId: 'c58c819b-89f2-4400-bb94-1ec79920adb4', servername: '
> http://10.10.214.233:8181'
>   def prettyJson = JsonOutput.prettyPrint(saltresult)
>   println(prettyJson)
> }
>
>
>
>
> *[BUILD OUTPUT]*
>
> [Pipeline] nodeRunning on master in 
> /var/lib/jenkins/workspace/hello-world-pipeline-saltstack[Pipeline] 
> {[Pipeline] }[Pipeline] // node[Pipeline] End of 
> Pipelinejava.lang.NoSuchMethodError: No such DSL method 'salt' found among 
> steps [ansiColor, archive, bat, build, catchError, checkout, deleteDir, dir, 
> dockerFingerprintFrom, dockerFingerprintRun, echo, emailext, 
> emailextrecipients, error, exws, exwsAllocate, fileExists, findFiles, 
> getContext, git, input, isUnix, libraryResource, load, mail, milestone, node, 
> parallel, properties, pwd, readFile, readManifest, readMavenPom, 
> readProperties, readTrusted, readYaml, retry, sh, sleep, stage, stash, step, 
> svn, timeout, timestamps, tool, touch, unarchive, unstash, unzip, waitUntil, 
> withContext, withCredentials, withDockerContainer, withDockerRegistry, 
> withDockerServer, withEnv, wrap, writeFile, writeMavenPom, ws, zip] or 
> symbols [all, always, ant, antFromApache, antOutcome, antTarget, apiToken, 
> architecture, archiveArtifacts, artifactManager, batchFile, booleanParam, 
> buildButton, buildDiscarder, caseInsensitive, caseSensitive, choice, 
> choiceParam, clock, cloud, command, configFile, configFileProvider, cron, 
> crumb, defaultView, demand, disableConcurrentBuilds, downloadSettings, 
> downstream, dumb, envVars, fastestReadSpeed, fastestWriteSpeed, file, 
> fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, git, 
> hyperlink, hyperlinkToModels, installSource, jdk, jdkInstaller, jgit, 
> jgitapache, jnlp, jobName, junit, lastDuration, lastFailure, 
> lastGrantedAuthorities, lastStable, lastSuccess, legacy, list, local, 
> location, logRotator, loggedInUsersCanDoAnything, masterBuild, maven, 
> maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, mostUsableSpace, myView, 
> nodeProperties, nonStoredPasswordParam, none, overrideIndexTriggers, 
> paneStatus, parameters, password, pattern, pipelineTriggers, plainText, 
> plugin, pollSCM, projectNamingStrategy, proxy, queueItemAuthenticator, 
> quietPeriod, run, runParam, schedule, scmRetryCount, search, security, shell, 
> slave, stackTrace, standard, status, string, stringParam, swapSpace, text, 
> textParam, tmpSpace, toolLocation, unsecured, upstream, 
> usernameColonPassword, usernamePassword, viewsTabBar, weather, zfs, zip] or 
> globals [currentBuild, docker, env, params, scm, simpleBuild]
>   at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:149)
>   at 
> org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108)
>   at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source)
>   at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
>   at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
>   at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151)
>   at 
> org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21)
>   at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115)
>   at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149)
>   at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146)
>   at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123)
>   at 
> com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16)
>   at WorkflowScript.run(WorkflowScript:4)
>   at ___cps.transform___(Native Method)
>   at 
> com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)
>   at 
> com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)
>   at 
> com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82)
>   at sun.reflect.GeneratedMethodAccessor429.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
>

java.lang.NoSuchMethodError: No such DSL method 'salt' found among steps

Hi Everyone,

Can anyone tell me what I'm missing here? Salt API already installed. 
Jenkins version: 2.32.2



*[PIPELINE SCRIPT]*import groovy.json.*

node() {
  saltresult = salt authtype: 'pam', clientInterface: local(arguments: 
'"uname -r"', blockbuild: true, 
function: 'cmd.run', jobPollTime: 16, target: '*', targetType: 'glob'), 
credentialsId: 'c58c819b-89f2-4400-bb94-1ec79920adb4', servername: 
'http://10.10.214.233:8181'
  def prettyJson = JsonOutput.prettyPrint(saltresult)
  println(prettyJson)
}




*[BUILD OUTPUT]*

[Pipeline] nodeRunning on master in 
/var/lib/jenkins/workspace/hello-world-pipeline-saltstack[Pipeline] {[Pipeline] 
}[Pipeline] // node[Pipeline] End of Pipelinejava.lang.NoSuchMethodError: No 
such DSL method 'salt' found among steps [ansiColor, archive, bat, build, 
catchError, checkout, deleteDir, dir, dockerFingerprintFrom, 
dockerFingerprintRun, echo, emailext, emailextrecipients, error, exws, 
exwsAllocate, fileExists, findFiles, getContext, git, input, isUnix, 
libraryResource, load, mail, milestone, node, parallel, properties, pwd, 
readFile, readManifest, readMavenPom, readProperties, readTrusted, readYaml, 
retry, sh, sleep, stage, stash, step, svn, timeout, timestamps, tool, touch, 
unarchive, unstash, unzip, waitUntil, withContext, withCredentials, 
withDockerContainer, withDockerRegistry, withDockerServer, withEnv, wrap, 
writeFile, writeMavenPom, ws, zip] or symbols [all, always, ant, antFromApache, 
antOutcome, antTarget, apiToken, architecture, archiveArtifacts, 
artifactManager, batchFile, booleanParam, buildButton, buildDiscarder, 
caseInsensitive, caseSensitive, choice, choiceParam, clock, cloud, command, 
configFile, configFileProvider, cron, crumb, defaultView, demand, 
disableConcurrentBuilds, downloadSettings, downstream, dumb, envVars, 
fastestReadSpeed, fastestWriteSpeed, file, fileParam, filePath, fingerprint, 
frameOptions, freeStyle, freeStyleJob, git, hyperlink, hyperlinkToModels, 
installSource, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobName, junit, 
lastDuration, lastFailure, lastGrantedAuthorities, lastStable, lastSuccess, 
legacy, list, local, location, logRotator, loggedInUsersCanDoAnything, 
masterBuild, maven, maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, 
mostUsableSpace, myView, nodeProperties, nonStoredPasswordParam, none, 
overrideIndexTriggers, paneStatus, parameters, password, pattern, 
pipelineTriggers, plainText, plugin, pollSCM, projectNamingStrategy, proxy, 
queueItemAuthenticator, quietPeriod, run, runParam, schedule, scmRetryCount, 
search, security, shell, slave, stackTrace, standard, status, string, 
stringParam, swapSpace, text, textParam, tmpSpace, toolLocation, unsecured, 
upstream, usernameColonPassword, usernamePassword, viewsTabBar, weather, zfs, 
zip] or globals [currentBuild, docker, env, params, scm, simpleBuild]
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:149)
at 
org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108)
at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151)
at 
org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21)
at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123)
at 
com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16)
at WorkflowScript.run(WorkflowScript:4)
at ___cps.transform___(Native Method)
at 
com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)
at 
com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)
at 
com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82)
at sun.reflect.GeneratedMethodAccessor429.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at 
com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55)
at 
com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45)
at

MSBuild - roslyn files are copied to the wrong location

2017-02-21 Thread Ken Corley

Running Jenkins 2.19.2 and 1.27 MSBuild plugin.

Job is compiling a VS 2015 MVC 5 app.

Job has been trucking along nicely.

When I set true on the project file to 
precompile the Views, I get a failure:

(MvcBuildViews target) -> 
  ASPNETCOMPILER : error ASPRUNTIME: Could not find a part of the path 
'C:\Jenkins\MailIV.com.Build\_PublishedWebsites\MailIV.com\bin\roslyn\csc.exe'. 
[C:\Program Files 
(x86)\Jenkins\workspace\MailIV.com\MailIV.com\MailIV.com.csproj]


It turns out that the roslyn files that are supposed to be copied to 
/bin/roslyn/ are copies into /bin/ instead.

I've tried a number of variations of this build command in the project file 
to no avail


  

  
  
  


Does anyone know how to get this to run correctly and/or know why the files 
are being copied to the wrong location?

Thanks -Ken

-- 
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/138bdf66-d3c1-4228-8690-715554d6d90d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: credential plugin disappears after Jenkins upgrade to 1.658

2017-02-21 Thread Daniel Beck


> On 21.02.2017, at 18:13, Prasu S  wrote:
> 
> java.io.IOException: Failed to expand 
> D:\Build\Jenkins\apps\jenkins\jenkins_home\plugins\credentials.jpi
> 

My guess is that the plugin zip file is corrupt. Redownload and replace.

-- 
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/96132183-D4A4-4D70-B3AD-C8AB1249A49F%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Workspace root directory (Jenkinsfile)

2017-02-21 Thread jerome

What I have found so far:

Inside the Jenkins management you can change the Workspace directory. 


   1. http://MY_HOST/Jenkins/configure
   2. Right under the home directory into advanced button.
   3. Workspace Root Directory   ${JENKINS_HOME}/workspace/${ITEM_FULLNAME}

you could change it for something short indeed like  D:/work
I had the same problems with the zip archiving under Windows. The 256 char 
path limits is a pain. Keep your job project short, use description for 
more info. Try to avoid too many job folder under Windows since it does 
create 2 folder deep /job/name every time.

-- 
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/fef85f6b-90a8-4215-86c2-73e6028518cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: credential plugin disappears after Jenkins upgrade to 1.658

2017-02-21 Thread Prasu S

Daniel Thanks for the quick response. I have plugins directory back up , 
Can I copy the plugin from the backup or do I have to install different 
plugin version like 1.22. Please help. Appreciate your response.

I see these errors in the log:
***
SEVERE: Failed Inspecting plugin 
D:\Build\Jenkins\apps\jenkins\jenkins_home\plugins\credentials.jpi
java.io.IOException: Failed to expand 
D:\Build\Jenkins\apps\jenkins\jenkins_home\plugins\credentials.jpi
at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:532)
at 
hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:167)
at hudson.PluginManager$1$3$1.run(PluginManager.java:288)
at 
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$8.runTask(Jenkins.java:958)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: Problem creating zip: null
at org.apache.tools.ant.taskdefs.Zip.executeMain(Zip.java:741)
at org.apache.tools.ant.taskdefs.Zip.execute(Zip.java:568)
at 
hudson.ClassicPluginStrategy.createClassJarFromWebInfClasses(ClassicPluginStrategy.java:589)
at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:530)
... 10 more
Caused by: java.io.EOFException
at java.io.RandomAccessFile.readFully(RandomAccessFile.java:446)
at java.io.RandomAccessFile.readFully(RandomAccessFile.java:424)
at org.apache.tools.zip.ZipFile.resolveLocalFileHeaderData(ZipFile.java:522)
at org.apache.tools.zip.ZipFile.(ZipFile.java:187)
at org.apache.tools.zip.ZipFile.(ZipFile.java:163)
at 
org.apache.tools.ant.types.resources.ZipResource.getInputStream(ZipResource.java:133)
at 
org.apache.tools.ant.types.resources.ResourceDecorator.getInputStream(ResourceDecorator.java:125)
at org.apache.tools.ant.taskdefs.Zip.addResource(Zip.java:1041)
at org.apache.tools.ant.taskdefs.Zip.addResources(Zip.java:1098)
at org.apache.tools.ant.taskdefs.Zip.executeMain(Zip.java:665)

On Tuesday, February 21, 2017 at 9:23:58 AM UTC-5, Daniel Beck wrote:
>
>
> > On 21.02.2017, at 15:22, Prasu S  
> wrote: 
> > 
> > I upgraded Jenkins from 1.607 to 1.658 , after the upgrade credentials 
> plugin 1.18 is missing. Due to this, we are  not able to get code from 
> Github. When I tried to re-install the same version(1.18) , it is still not 
> showing under installed plugin list.  How can I recover credential plugin. 
> Any help is greatly appreciated. Thank you 
>
> Did you check the log for errors in loading the plugin on startup? 
>
> https://wiki.jenkins-ci.org/display/JENKINS/Logging 
>
>

-- 
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/39b9d644-123c-42d6-ab7e-28d65696a0d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Setting the description of a failed test in pipeline groovy

2017-02-21 Thread jerome

Add description on the side:

manager.addShortText("${APPLY_TAG}")

You can find a lot of property inside you syntax help page (change MY_HOST, 
MY_PIPELINE_JOB):

http://MY_HOST/Jenkins/job/MY_PIPELINE_JOB/pipeline-syntax/globals

this should with the properties of env/manager/currentBuild. the 
hudson/build object is inside the manager for example. As what is available 
on them after, you need to check the javadoc and try to make sense of it.

Hope this help,
Jerome

-- 
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/c548cc44-ebee-4de0-b201-0a6dc8c78b48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline Slack / XUnit posting test results

2017-02-21 Thread mike

Pre-pipeline, I had jobs that would post to slack with a summary of the 
XUnit tests results.

I've got slack posting and XUnit test results gathering all working in 
pipeline now, but what I miss, and what my team is not keen to lose is the 
test results detail in the slack posts.

I don't mind if I have to recreate them, but I'm not sure that the pipeline 
run has *access* to the result numbers in any concrete way.  

Anybody else dealing with this?

m.

-- 
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/585bf2dc-5782-4abc-bf34-90b72089c6ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AW: Workspace root directory (Jenkinsfile)

2017-02-21 Thread Spriggs, Jim

Hi Ryan,

Been there.

How about setting your JENKINS_HOME to something shorter before you start the
jenkins server?

For instance, this works for me:

JENKINS_HOME=”/jk” java -jar jenkins.war

[ Obviously, I enjoy the luxury of a sensible OS. ;-) ]

See the notes at the top of the “Manage Jenkins|Configure System” page for more
info.

Good Luck!
--
jim

Von: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com]
Im Auftrag von Ryan Hutchison
Gesendet: Dienstag, 21. Februar 2017 16:38
An: jenkinsci-users@googlegroups.com
Betreff: Workspace root directory (Jenkinsfile)

My JENKINS_HOME is C:\Program Files (x86)\Jenkins

I have allocated a separate drive for my workspace `D:\` and modified the
global workspace property to reflect this new location.

When my build job runs (Jenkinsfile), it always goes to
${JENKINS_HOME}\workspace.

My issue is that msbuild ends up failing due to long file names/paths. It does
not help that the randomly generated ${ITEM_FULLNAME} is quite long by itself.

Any thoughts or pointers would be appreciated.

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

RAYLASE AG
Argelsrieder Feld 2+4
82234 Wessling
Germany
Tel.: +49-(0)8153/88 98-0
Fax: +49-(0)8153/88 98-10
http://www.raylase.de

District Court Munich, HRB 131450

Board: Dr. Philipp Schön (Chairman), Berthold Dambacher, Christoph von Jan

Supervisory Board: Dr. Ulrich Lohmann (Chairman)

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht
gestattet.

This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is strictly
forbidden.

--
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/a59f45ff7b1947a9b1f6becebda52b6f%40raylase.de.
For more options, visit https://groups.google.com/d/optout.

Workspace root directory (Jenkinsfile)