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

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

Separating build failure from test failures

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

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 Tue

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

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 t

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

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.la

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 > depend

Re: Workspace root directory (Jenkinsfile)

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 t

RE: Updated Hotlist please share your daily requirements..

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 r

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*

Re: QUESTION: Jenkins initialization has not reached the COMPLETED

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, wheth

Re: Jenkins PR triggers a build of PR

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 m

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

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]

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 Jen

Jenkins PR triggers a build of PR

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.

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:4

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-B

Re: credential plugin disappears after Jenkins upgrade to 1.658

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

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\jenki

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 (x8

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

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.4

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.

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 > t

Slave Container accessing GitHub private repository via SSH keys

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: impo

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

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

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 th

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

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

Jenkins build says successful but no output is seen

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 bu

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 > > > > *[PIPELI

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', jobPoll

MSBuild - roslyn files are copied to the wrong location

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 p

Re: credential plugin disappears after Jenkins upgrade to 1.658

> 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

Re: Workspace root directory (Jenkinsfile)

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

Re: credential plugin disappears after Jenkins upgrade to 1.658

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 Insp

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

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 h

Pipeline Slack / XUnit posting test results

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

AW: Workspace root directory (Jenkinsfile)

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

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

Re: ERROR: Timeout after 10 minutes

The reference repository and clone timeout can be set in the pipeline job definition as well, so long as you choose "Git" as the SCM source. I don't think the same options are available if you choose another SCM source (like GitHub). If you don't need the full history of the repository, then you

Re: Upgrading to Jenkins LTS 2.32.x

> On 21.02.2017, at 14:58, Makarand Jadhav wrote: > > Are the instructions listed in > https://jenkins.io/doc/book/getting-started/installing/ & > https://jenkins.io/doc/book/hardware-recommendations/ suffice for the upgrade > process as well? Jenkins has no substantially different hardware

Re: credential plugin disappears after Jenkins upgrade to 1.658

> 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

Re: ERROR: Timeout after 10 minutes

Thanks Mark for comprehensive reply. Yes timeout is due to large repository. I can try the solution of generating custom command through pipeline syntax and creating reference repo but when I start the built, it will checkout automatically and that step will itself fail due to timeout so Jenkin

credential plugin disappears after Jenkins upgrade to 1.658

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. An

Upgrading to Jenkins LTS 2.32.x

Hi, We are planning to upgrade Jenkins from ver. 1.640 to LTS 2.32.1. I checked the upgrade guides listed on https://jenkins.io/doc/upgrade-guide/2.32/#upgrading-to-jenkins-lts-2-32-1 but it does not seem to give direct information on the upgrade requirements from server resources & software's

Re: Milestone incompatible with maven release process and recommendations?

Le mardi 21 février 2017 10:39:09 UTC+1, Erwan QUEINNEC a écrit : > > Thanks Adrien > Creating a release branch could solve the problem yes. > But I have to check the impact of the git-flow approach as we have many > projects and teams using the maven approach... > > Le mardi 21 février 2017 10:

Re: Coverity build error

A "no translation units" typically means nothing was actually compiled. On Mon, Feb 20, 2017 at 4:54 AM, Nitzan Yemal wrote: > Hello, > > I'm trying to create a job with coverity plugin for static analysis and I > get this error (using Coverity plugin 1.8.1 and coverity version 8.6 on > Ubuntu m

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

Hi Baptiste, > On 16 Feb 2017, at 08:45, Baptiste Mathus wrote: > > Hi Vincent, > I think the first step to convert that kind of thing is probably to > externalize it in a @NonCPS function to avoid potential issues while > refactoring. > Also, probably disable temporarily sandbox while convert

Build details of pipeline job via API

Hi, I'm trying to get information about running builds on Jenkins agents, with and without pipelines. 'Old-style' jobs show up just fine but pipelines only ever appear as placeholder tasks: { "currentExecutable": { "_class": "org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExe

Re: createItem (with view) via REST API fails in Jenkins 2.x

> On 21.02.2017, at 11:58, Alex Ellis wrote: > > To get the exact version for you will involve downloading every iteration > between 1.6 and 2.3 and installing/testing one-by-one Not quite. A binary search takes at most log2(n) iterations. Also, please note that "1.6" isn't a version of Jenki

Re: createItem (with view) via REST API fails in Jenkins 2.x

Please see this issue logged - https://issues.jenkins-ci.org/browse/JENKINS-41128?jql=text%20~%20%22createitem%20view%22 On 21 February 2017 at 10:58, Alex Ellis wrote: > I do not know which version introduced breakage - I moved straight from > 1.6 to 2.3/2.4. And the error is easily reproduci

Re: createItem (with view) via REST API fails in Jenkins 2.x

I do not know which version introduced breakage - I moved straight from 1.6 to 2.3/2.4. And the error is easily reproducible. To get the exact version for you will involve downloading every iteration between 1.6 and 2.3 and installing/testing one-by-one - are there any Java developers in the team o

Re: createItem (with view) via REST API fails in Jenkins 2.x

I think it would be very helpful if you can narrow down the exact Jenkins version it started failing with. Using jenkinsci/jenkins you will also have weeklies on the docker hub (only LTS are published on the official image, so there are pretty big version jumps there). Thanks Alex ! Le 20 févr.

Re: Milestone incompatible with maven release process and recommendations?

Or you could more simply do a `if (env.BRANCH_NAME == "master"){}` and do the maven release in this block. Then all you need is to merge into master to make Jenkins do the release. Le mar. 21 févr. 2017 à 10:39, Erwan QUEINNEC a écrit : > Thanks Adrien > Creating a release branch could solve the

Re: Milestone incompatible with maven release process and recommendations?

Thanks Adrien Creating a release branch could solve the problem yes. But I have to check the impact of the git-flow approach as we have many projects and teams using the maven approach... Le mardi 21 février 2017 10:23:11 UTC+1, Adrien Lecharpentier a écrit : > > Hello, > > the problem is that mi

Re: Jenkins dkr container on top of CoreOS + Kubernetes - DNS Issue resolving mirrors.jenkins-ci.org

That's pretty odd as the blueocean container is based on the jenkins docker image. 2017-02-21 7:02 GMT+01:00 : > Thanks Mark. Since I can't send docker-specific args via Kubernetes pods, > I've shifted to the blueocean container and the issue doesn't happen there. > > It's a pity I can't use the

Re: Milestone incompatible with maven release process and recommendations?

Hello, the problem is that milestone is independent of Maven. The release in two steps is a maven "problem". What you could do is use the git-flow approach and do the real release in separate branch (or in master). You could even use https://bitbucket.org/atlassian/jgit-flow/wiki/Home to automate

Milestone incompatible with maven release process and recommendations?

Hi If I implement milestone in stage like: https://jenkins.io/blog/2016/10/16/stage-lock-milestone/ stage('Build') { milestone() echo "Building" } stage('Test') { milestone() echo "Testing" } And I execute a release: maven release:prepare -DreleaseVersion=X -Dtag=X -DdevelopmentVersion=