Re: Pipeline: Resource Locking Plugin hangs

correct amount: 1.[nodeName3] [testing3-repository] is locked, waiting...[nodeName1] Lock acquired on [testing1-repository][Pipeline] [nodeName1] {[Pipeline] [nodeName1] echo[nodeName1] Testing lock resource[Pipeline] [nodeName1] sleep[nodeName1] Sleeping for 30 sec[Pipeline] [nodeName1] }[n

Re: Pipeline: Resource Locking Plugin hangs

Running two builds of pipeline-test2 works fine. The second build gets all three resources when the first build has released them. So seems the problem is when locking on label. The build will only get the first release lock. tirsdag 13. mars 2018 08.44.21 UTC+1 skrev Sverre Moe følgende: >

Re: Pipeline: Resource Locking Plugin hangs

Looks like there is a fix for this in the works. https://github.com/jenkinsci/lockable-resources-plugin/pull/70 -- 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

Re: Pipeline: Resource Locking Plugin hangs

tirsdag 13. mars 2018 15.52.32 UTC+1 skrev Steven Foster følgende: > > On Tuesday, March 13, 2018 at 1:02:02 PM UTC, Sverre Moe wrote: >> >> Looks like there is a fix for this in the works. >> https://github.com/jenkinsci/lockable-resources-plugin/pull/70 >> >

Feature Request: BlueOcean custom view

Not sure what the plans are for BlueOcean, but the main Pipeline View is very limited. Having favorites helps a little, but it would help a lot more with custom pipeline views. What we are looking for in BlueOcean Pipelines View: * Choose a release branch * List all pipeline jobs for selected br

Re: Pipeline: Support for DependencyGraph

UTC+1 skrev Sverre Moe følgende: > > Dependency Graph is very useful to display any upstream and downstream > dependencies. However with Pipeline it seems no longer an option. > > Is there any plans for *DependencyGraph* pipeline support with > *WorkflowMultiBranchProject*? Since *D

Re: BlueOcean observations from user

I have read some other discussions that say BlueOcean v1.5 should have some performance improvements. It is still in beta stage though. torsdag 12. april 2018 09.47.17 UTC+2 skrev LnT følgende: > > Hi All - > > I too find the same slow ness while opening blue ocean page for the > particular page

Using Gradle in Pipeline

We are currently using Maven for building our applications. Our Jenkins maven pipeline are using the withMaven step from Pipeline Maven Integration. I have written gradle build scripts for our projects and begun to write the Pipeline build script to build gradle. We could really use an Pipeli

Re: BlueOcean observations from user

We have upgraded to Blue Ocean v1.5.0 Loading the main Pipeline view is now faster. Sadly, loading activities and branches for a pipeline still takes a while. Aprox 35-40 seconds. Note: This is the initial load time, subsequent visits is much faster, 1-3 seconds. What details do you need on a J

Re: BlueOcean observations from user

lørdag 14. april 2018 01.04.29 UTC+2 skrev vivek følgende: > > > What are branches sorted by? It is certainly not Branch, Completed or any >> of the other columns. It seems none of the visible columns are used for >> sort criteria. >> > > ​We show pagin​ated list of branches. Branches are sorted

Blue Ocean: Last step always marked failed

In Blue Ocean the last step is marked failed. The step that actually failed is a few steps earlier I have deleteDir() at the very last in try-catch-finally on every parallel build node. This on order to clean up. "Recursively delete the current directory from the workspace" Blue Ocean has this s

Blue Ocean: Jump to first error and use highlighting

When opening a pipeline build in Blue Ocean it scroll automatically down to the bottom of the last failed step. If it is not possible it would be very helpful to control where it scrolls down to. For instance to scroll down to the first error in the failed step output. [ 12%] Building CXX obje

Pipeline: BUILD_URL for Blue Ocean

We have the following content to mail notifications. def content "Check console output at ${env.BUILD_URL} to view the results." Where env.BUILD_URL has the following URL https://build-ci.company.com:8443/job/projectA/job/user%252Fwork/115/ Is there an environment variable to get Blue Ocean build

Remove Jenkins navigation links

Is it possible to remove the Jenkins navigation bar links? It is irrelevant for regular users/developers. Just us Jenkins admins need it, and we already have it by clicking on Jenkins> at top. Ut just clutter up the UI for developers.

Pipeline: MissingPropertyException for class

The following pipeline script fails class Test implements Serializable { final def buildIn final def allUpstreamDependencies = [:] Test(buildIn) { this.buildIn = buildIn } void test() { buildIn.node("master") { allUpstreamDependencies["projecA"] =

Re: Blue Ocean: Last step always marked failed

Created an issue for this https://issues.jenkins-ci.org/browse/JENKINS-50923 onsdag 18. april 2018 12.15.50 UTC+2 skrev Sverre Moe følgende: > > In Blue Ocean the last step is marked failed. > The step that actually failed is a few steps earlier > > I have deleteDir() at the v

Multibranch Pipeline: GitLab Pull Requests

https://jenkins.io/doc/book/pipeline/multibranch/#supporting-pull-requests Is there any plans to support GitLab merge request with Jenkins? Seems Kohsuke started work on a GitLab Branch Source plugin a year ago. https://github.com/kohsuke/gitlab-branch-source-plugin -- You received this message

Re: Remove Jenkins navigation links

Inspecting the source gave me a way to hide the navigation panel #tasks{ Display:none } Could not use side-panel, because that would also hide Build Queue and Build Executor Status onsdag 18. april 2018 14.39.43 UTC+2 skrev Sverre Moe følgende: > > Is it possible to remove the J

Re: Remove Jenkins navigation links

It wasn't that easy after all. I wanted to remove it from Jenkins main page, but not from the projects page. Can't find an id or class that will allow me to do that. onsdag 25. april 2018 10.43.13 UTC+2 skrev Sverre Moe følgende: > > Inspecting the source gave me a way to hid

Re: Tap4j Plugin Exception

https://issues.jenkins-ci.org/browse/JENKINS-17488 I hope they can fix this issue soon. This warning is filling up about 90% of our Jenkins log. torsdag 8. mars 2018 17.08.18 UTC+1 skrev Sverre Moe følgende: > > Using Tap4j in Jenkins generates Exception in jenkins log output > >

Builds on lightweight executors no longer shown

Steps that was running on a lightweight executor was previously visible on master node in Build Executor Status. Now these builds are not visible on the either Build Queue or Build Executor Status after they have released an heavyweight executor. Our projects are executing downstream builds on a

Pipeline: Jenkins Release Plugin useless

What use has Jenkins Release Plugin to Pipeline jobs? According to documentation: "The release plugin supports the Maven2 and Free Style Job type". Still the release step is available as a pipeline step. Jobs to Release, gives up nothing when I start type. Enter an actual project and gets *ERRO

Storing custom build environment variables to build

I am unable to read my custom environment variables from a specific projects previous builds. stage("Test") { node("master) { env.TEST = "Hello World" } } stage("Previous") { final def lastBuild = currentBuild.rawBuild.getPreviousBuild() final def upstreamEnv = lastBu

Re: Blue Ocean: Does not show all steps during a stage with parallel

executions The classic Stage list shows only the steps in the master execution, but none of the parallel. The Blue Ocean shows only the steps in the parallel execution, but not the steps running prior on master. mandag 2. juli 2018 16.09.36 UTC+2 skrev Sverre Moe følgende: > > I wonder if I

Re: Getting cause for branch indexing in multibranch pipeline

import jenkins.branch.BranchIndexingCause final def jenkinsInstance = jenkins.model.Jenkins.getInstance() final def jenkinsProject = jenkinsInstance.getItemByFullName( jenkinsProjectName) if (jenkinsProject != null) { final def job = jenkinsProject.getAllJobs().first()

Re: Jenkinsfile to build 4 different docker images

mandag 10. september 2018 12.06.01 UTC+2 skrev Vijay V følgende: > > Is it possible to build 4 different docker images using 4 Dockerfiles with > one Jenkinsfile program? If so how to do it? > You can create Docker images from Scripted Pipeline with the Docker Pipeline plugin. https://jenkins.io

Cleanup workspace before/after build

This deleteDir() does not always work on a Windows build slave. Using Scripted PIpeline I am declaring a node within try-catch-finally. The finally will run deleteDir(), in order to delete the build workspace. This is done in order to get a fresh build each time. I cannot risk having stale data

Re: Cleanup workspace before/after build

I will see if I can find some more information about the problem. torsdag 11. oktober 2018 10.02.54 UTC+2 skrev Baptiste Mathus følgende: > > What is the JIRA number number for the Windows deleteDir() bug you say > you're seeing? > > Le jeu. 11 oct. 2018 à 09:33, Sve

Re: Cleanup workspace before/after build

fredag 12. oktober 2018 13.35.36 UTC+2 skrev Andreas Tscharner følgende: > > Hi Sverre, > > On 11.10.2018 09:33, Sverre Moe wrote: > > [snip] > > Is there some other means I can make sure that the build has a clean > > workspace? > > Our Windows agents are

Re: Cleanup workspace before/after build

ts. torsdag 11. oktober 2018 10.02.54 UTC+2 skrev Baptiste Mathus følgende: > > What is the JIRA number number for the Windows deleteDir() bug you say > you're seeing? > > Le jeu. 11 oct. 2018 à 09:33, Sverre Moe > > a écrit : > >> This deleteDir() does not

Pipeline: Identify different Jenkins instances

We have copied our Jenkins instance to have an identical test Jenkins. Is there a *proper* way to distinguish between production Jenkins and test Jenkins within a Scripted Pipeline? We need different behaviour for some parts of our builds, like publishing Yum artifacts, git tagging releases. T

Re: Pipeline: Identify different Jenkins instances

m;8443/ JENKINS_ENVIRONMENT > TEST Which can be read in scripted pipeline as env.JENKINS_ENVIRONMENT mandag 12. november 2018 15.43.20 UTC+1 skrev Sverre Moe følgende: > > > We have copied our Jenkins instance to have an identical test Jenkins. > > Is there a *proper* wa

Pipeline: Publish RPM to Nexus Repository Manager

Publish RPM artifacts to Sonatype Nexus yum repository. It seems the nexus artifact uploader plugin is used for uploading non-maven artifacts to Nexus Repository Manager. It says this plugin is used to upload non-maven artifacts to Nexus, but it requires a few properties that are quite not neces

Pipeline: Stage View has wrong build status

The Stage View is showing a build as FAILED, even though it is SUCCESS, and both Build History and Blue Ocean shows it as SUCCESS. [image: Screenshot_20181220_082735.png] Is there a known bug with the Stage View plugin that would account for the problem we are having? -- You received this me

Node getting CancellationException during startup

Having problems connecting to nodes getting CancellationException [02/20/19 11:15:03] [SSH] Starting sftp client. [02/20/19 11:15:03] [SSH] Copying latest remoting.jar... [02/20/19 11:15:03] [SSH] Copied 789,283 bytes. Expanded the channel window size to 4MB [02/20/19 11:15:03]

Re: Node getting CancellationException during startup

That was my fault. I forgot some lines and had paste it in from a different try [02/21/19 14:16:46] [SSH] Starting sftp client. [02/21/19 14:16:47] [SSH] Copying latest remoting.jar... [02/21/19 14:16:47] [SSH] Copied 789,283 bytes. Expanded the channel window size to 4MB [02/21/19 14:16:47] [

Re: Node getting CancellationException during startup

build32688 0.0 0.0 12912 1772 ?Ss 14:13 0:00 bash -c cd "/home/build/jenkins" && /usr/java/latest/bin/java -jar remoting.jar -workDir /home/build/jenkins torsdag 21. februar 2019 14.21.51 UTC+1 skrev Sverre Moe følgende: > > That was my fault. I f

Use AdoptOpenJDK as JDK Tool download source

Now that Oracle has shut down any commercial use of their JDK, Jenkins should add option to download JDK from AdoptOpenJDK Install automatically Extract *.zip/*.tar.gz Install from java.sun.com Run Batch Command Run Shell Command Now that the JDK from Oracle cannot be used in pro

Re: Use AdoptOpenJDK as JDK Tool download source

nteresting to you. > > On Feb 22, 2019, at 09:20, Sverre Moe > > wrote: > > Now that Oracle has shut down any commercial use of their JDK, Jenkins > should add option to download JDK from AdoptOpenJDK > > Install automatically > Extract *.zip/*.tar.gz >

Unknown Workflow CPS Exceptions in Jenkins log

Any idea what the following Exceptions are caused by? I have found these in the Jenkins log. Feb 26, 2019 11:43:58 AM WARNING org.jenkinsci.plugins.workflow.cps.DSL invokeStep Error storing the arguments for step: checkout org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBound

Multibranch Pipeline: Setting OrphanItemStrategy in Script Console

I am trying to update a Multibranch pipeline project I have looked into the source code for ComputedFolder and DefaultOrphanedItemStrategy to find out how to set it. DefaultOrphanedItemStrategy extends OrphanedItemStrategy and takes inn a boolean,String,String parameter list. Running Jenkins 2.4

Re: Multibranch Pipeline: Setting OrphanItemStrategy in Script Console

I can't believe I missed that. Thanks. torsdag 23. mars 2017 12.49.00 UTC+1 skrev Stephen Connolly følgende: > > you have misspelled the method and the error is telling you the correct > spelling... it's setOrphanedItemStrategy not setOprhanItemStrategy > -- You received this message because y

Pipeline: Remote call on node failed

I have been getting an IOException I cannot understand why it happens or if my builds are invalid because of it. Cannot contact r12-sles12.1-x86_64: java.io.IOException: Remote call on r12-sles12.1-x86_64 failed The build does seem to go fine with this error. On some operations there are seve

Pipeline: Changed behaviour of checkout scm

Have pipeline changed how it does checkout scm recently? Previously I got tags with each checkout, but no longer. I have to execute shell script 'git fetch --tags" after calling checkout scm. Makes me wonder what has changed, what else might have changed and how can I get back the previous behavi

Re: Pipeline: Changed behaviour of checkout scm

ition. > > Mark Waite > > On Wed, Aug 30, 2017 at 2:00 AM Sverre Moe > wrote: > >> Have pipeline changed how it does checkout scm recently? >> Previously I got tags with each checkout, but no longer. >> I have to execute shell script 'git fetch --tags"

Pipeline Maven: Running on Windows slave

I have connected a Windows slave to Jenkins with SSH+Cygwin. So running shell scripts like "sh 'mvn'" should work as I do it locally on the Windows. Running withMaven fails, and I cannot figure our why. [Pipeline] node Running on master-windows-x86_64 in /home/username/workspace/myApp_username_

Re: Pipeline Maven: Running on Windows slave

ble JAVA_HOME is set to C:\Program Files\Java\jdk1.8.0_121 mandag 11. september 2017 08.07.21 UTC+2 skrev Sverre Moe følgende: > > I have connected a Windows slave to Jenkins with SSH+Cygwin. > So running shell scripts like "sh 'mvn'" should work as I do it locally on

Re: Pipeline Maven: Running on Windows slave

sociated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org It would seem it is unable to use the "correct" home directory as Windows is using Cygwin. mandag 11. september 2017 08.18.38 UTC+2 skrev Sverre Moe følgende: > > I took a look at the Maven Pipelin

Re: Pipeline Maven: Running on Windows slave

The fix was to set the Windows slave Remote Root Directory to Windows URI C:\cygwin64\home\username mandag 11. september 2017 08.35.29 UTC+2 skrev Sverre Moe følgende: > > Well, adding a new JDK in Jenkins Tools pointing to the Windows path of > Java worked > Then withMaven(jdk:

Re: Pipeline Maven: Running on Windows slave

think >> could be made easier/better? And even if possibly a config error, if you >> think the error could help more quickly understand what is wrong? >> >> Thanks! >> >> Le 11 sept. 2017 09:03, "Sverre Moe" a écrit : >> >>> The fix

Pipeline: Global Library added to revisions

We have been using Global Pipeline Libraries stored at the jenkins server in workflowLibs directory. Now I have moved this repository to our remote git server and added the library in Jenkins configuration. I have checked "*Load implicitly" and* unchecked "*Include @Library changes in job recen

BlueOcean observations from user

Here follows some observations from running Jenkins in Blue Ocean: I know BluOcean is not yet finished: https://jenkins.io/projects/blueocean/roadmap/ A small list. I had expected more, but perhaps it near finish. Hope that some of my observation might lead to improvements on BlueOcean because I

Re: BlueOcean observations from user

t; list page. > > Arnaud. > > > 2017-10-23 8:59 GMT+02:00 Sverre Moe >: > >> Here follows some observations from running Jenkins in Blue Ocean: >> >> I know BluOcean is not yet finished: >> https://jenkins.io/projects/blueocean/roadmap/ >> A small

Re: BlueOcean observations from user

følgende: > > Hello, > > Does the favorites / personalization feature help you at all, or would the > list of favorite'd projects still be unmanageable for you? > > -Cliff > > > On Tue, Nov 7, 2017 at 3:44 AM, Sverre Moe > wrote: > >> I just updated m

Jenkinsfile merge conflicts because difference between branches

I am using the variable buildEnvironment to determine which set of nodes the branch should be built on. Each release branch (including git master) has their own list of slave nodes. Jenkinsfile: #!groovy def buildEnvironment = "master" def param2 = null String[] args = [buildEnvironment, param2

Re: Jenkinsfile merge conflicts because difference between branches

On Tuesday, 2 August 2016 07:19:22 UTC+1, Sverre Moe wrote: >> >> I am using the variable buildEnvironment to determine which set of nodes >> the branch should be built on. >> Each release branch (including git master) has their own list of slave >> nodes. &

Re: Multibranch Pipeline: How to parameterize?

, it won't be scalable. > > I do it for regular pipeline jobs by using the EnvInject plugin, can't use > that here though. > Do you have any solutions for this? > > On Wednesday, June 22, 2016 at 2:49:32 AM UTC-5, Sverre Moe wrote: >> >> It seems there is no po

Load Script Approval from another Jenkins instance

I have had a test instance of Jenkins running while programming my workflow scripts. In this process I have had to go into In-process Script Approval time and time again to add method calls to the approved list. Now I have the need to load these into Jenkins production instance and I cannot run

Re: Jenkinsfile merge conflicts because difference between branches

idy-up from time to > time. > > On Wednesday, 3 August 2016 08:08:38 UTC+1, Sverre Moe wrote: >> >> Yes, I am using Multibranch pipeline. >> I already have the branch name with env.BRANCH_NAME, but only some >> designated branches have a list of slave nodes. >&

Re: Load Script Approval from another Jenkins instance

> Am Montag, 8. August 2016 12:36:13 UTC+2 schrieb Sverre Moe: >> >> I have had a test instance of Jenkins running while programming my >> workflow scripts. In this process I have had to go into In-process Script >> Approval time and time again to add method calls to

Re: Archive multiple artifacts with same name

As it stands, using archive is useless unless it can be organized by the node it was built on. Building a single project on multiple linux distributions will produce the same named file, but not necessary the same. mandag 13. juni 2016 10.14.39 UTC+2 skrev Sverre Moe følgende: > > A

Multibranch Pipeline: Using notifyCommit does not indicate an SCM change

There is no longer an SCM change when using Multibranch Pipeline. "Started by an SCM change" Instead when the git server executes notifyCommit the branch that has changes shows "Branch indexing" and a question mark. Though at least the changes from SCM are shown on each build. Its just that Bra

Re: Multibranch Pipeline: Jenkins View missing last build information

https://issues.jenkins-ci.org/browse/JENKINS-37369 fredag 1. juli 2016 10.03.34 UTC+2 skrev Sverre Moe følgende: > > The Jenkins views has no information about "Last Success", "Last Failure" > and "Last Duration" for Multibranch Pipelines. > It shoul

Re: Multibranch Pipeline: Using notifyCommit does not indicate an SCM change

https://issues.jenkins-ci.org ? Any reproduction steps, examples, > screenshots, etc would be greatly appreciated. > > On Friday, August 12, 2016 at 4:50:22 PM UTC+10, Sverre Moe wrote: >> >> There is no longer an SCM change when using Multibranch Pipeline. >> "Star

Re: Using a Master Jenkinsfile for Multi-branch Pipelines

Take a look at Pipeline Global Library https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/README.md You can maintain all build logic within a global build script which is called from within each Jenkinsfile. You would still need a Jenkinsfile within each repository on all br

Re: Archive multiple artifacts with same name

; > The only downside is that the artifacts aren't saved with the build. If > you need that capability there may be a way to hack that however. > > On Thursday, August 11, 2016 at 11:15:31 PM UTC-7, Sverre Moe wrote: >> >> As it stands, using archive is useless unles

Re: Archive multiple artifacts with same name

; temp="to_archive" > sh """ > dir="${temp}/\$(lsb_release -si)-\$(lsb_release -sr)-\$(uname -m)" > mkdir -p "\${dir}" > cp *.rpm "${dir}" > """ > dir(temp){ archive '**' } > > > -M &

Change Build History date format

How can I change the date format in Build History? Aug 29, 2016 11:28 AM => 29.08.2016 11:28:45 Aug 24, 2016 3:51 PM = 24.08.2016 15:51:28 1) New date format 2) Use 24h time Format: "dd.MM. HH:mm:ss" -- You received this message because you are subscribed to the Google Groups "Jenkins Use

Re: GitLab integration: web hooks for GitLab CE with Jenkins multi-branch project?

Just have GitLab execute notifyCommit to Jenkins. https://jenkins.company.com:8443/git/notifyCommit?url=ssh://g...@git.company.com/project.git We are using this with a Git Hook in Gitolite. mandag 29. august 2016 17.35.56 UTC+2 skrev Michael Lasevich følgende: > > This is probably more of a GitLa

Pipeline: Doesn't always get commit authors in emailextrecipients

There seems to be a lottery of some sort what I get from emailextrecipients I expect to get the authors from the commits it is building, but most of the times emailextrecipients gives me nothing. /** * Notify developers of failed build */ void notifyFailedBuild() { final def projectName =

Re: Pipeline: Doesn't always get commit authors in emailextrecipients

+2 skrev Sverre Moe følgende: > > There seems to be a lottery of some sort what I get from emailextrecipients > > I expect to get the authors from the commits it is building, but most of > the times emailextrecipients gives me nothing. > > /** > * Notify developers of f

Re: Pipeline: Doesn't always get commit authors in emailextrecipients

erRecipientProvider']], subject: SUBJECT mail to: RECIPIENTS, cc: repositoryOwners, bcc: "devops", subject: SUBJECT, body: CONTENT However I do not always get anything out of emailextrecipients. mandag 5. september 2016 08.16.12 UTC+2 skrev Sverre Moe følgende: > > I fo

Re: Pipeline: Doesn't always get commit authors in emailextrecipients

It looks like email-ext has support for CC and BCC https://github.com/jenkinsci/email-ext-plugin/commit/4aacabf9b9fa9be326ebc362519e2f5d1bbb43fb However it is not present in the Pipeline syntax. mandag 5. september 2016 08.40.37 UTC+2 skrev Sverre Moe følgende: > > It would seem that th

Re: Pipeline: Doesn't always get commit authors in emailextrecipients

emailextrecipients does not give me any recipients running on a flyweight executor. mandag 5. september 2016 08.45.01 UTC+2 skrev Sverre Moe følgende: > > It looks like email-ext has support for CC and BCC > > https://github.com/jenkinsci/email-ext-plugin/commit/4aacabf9b9fa9be326e

Re: Pipeline: Doesn't always get commit authors in emailextrecipients

allow token replacement. An attempt to send an e-mail to empty list of recipients, ignored. Also seems it has some problems with ${PARAM} within the variables for SUBJECT and BODY. mandag 5. september 2016 09.16.36 UTC+2 skrev Sverre Moe følgende: > > Must run emailext within a heavy

Re: Pipeline: Doesn't always get commit authors in emailextrecipients

ins.io/doc/pipeline/steps/email-ext/). > > On Fri, Sep 2, 2016 at 1:36 AM Sverre Moe > wrote: > >> There seems to be a lottery of some sort what I get >> from emailextrecipients >> >> I expect to get the authors from the commits it is building, but mo

Re: Pipeline: Doesn't always get commit authors in emailextrecipients

+2 skrev slide følgende: > > mail is using the mailer plugin, if you want to use email-ext, you need to > use emailext (see https://jenkins.io/doc/pipeline/steps/email-ext/). > > On Fri, Sep 2, 2016 at 1:36 AM Sverre Moe > wrote: > >> There seems to be a lottery of so

Re: Pipeline: Doesn't always get commit authors in emailextrecipients

følgende: > > mail is using the mailer plugin, if you want to use email-ext, you need to > use emailext (see https://jenkins.io/doc/pipeline/steps/email-ext/). > > On Fri, Sep 2, 2016 at 1:36 AM Sverre Moe > wrote: > >> There seems to be a lottery of so

Re: Pipeline: Doesn't always get commit authors in emailextrecipients

In what parameter, to or recipientProviders? tirsdag 6. september 2016 19.07.42 UTC+2 skrev slide følgende: > > You can set cc and bcc in emailext using prefixes cc:som...@something.com > , bcc:som...@something.com > On another matter: Not sure why, Every time I try to reply on this discussi

Re: Pipeline: Doesn't always get commit authors in emailextrecipients

fredag 9. september 2016 14.44.33 UTC+2 skrev slide følgende: > > > On Thu, Sep 8, 2016 at 11:25 PM Sverre Moe > wrote: > >> In what parameter, to or recipientProviders? >> >> >> > In the "to" parameter. The recipient providers always use

Re: Pipeline: Doesn't always get commit authors in emailextrecipients

urce code git repository in the workspace? Perhaps I should include ALL the recipient providers, just in case. What I want is to notify the commit authors of failed build. Using only the 3 first recipient providers, something recipients are empty. fredag 9. september 2016 15.07.00 UTC+2 skrev S

Re: Pipeline: Doesn't always get commit authors in emailextrecipients

streamComitterRecipientProvider'] ]) tirsdag 6. september 2016 19.07.42 UTC+2 skrev slide følgende: > > You can set cc and bcc in emailext using prefixes cc:som...@something.com > , bcc:som...@something.com > > On Tue, Sep 6, 2016 at 9:16 AM Sverre Moe > wrote: >

Re: Detect the git repo for multi-branch pipeline

Use instead checkout scm It will checkout code from the repository fredag 9. september 2016 19.15.03 UTC+2 skrev Phil Swenson følgende: > > Hi, I have a multi branch pipeline configuration job working fine so > far > > However every single repository has exactly the same jenkinsfile except

The new Global Pipeline Library

There has been changes in the Global Pipeline Library plugin https://issues.jenkins-ci.org/browse/JENKINS-31155 Jenkins Configuration => Global Pipeline Libraries Choosing "Modern SCM" the next drop down list is empty. What does this option actually do? Choosing "Legacy SCM" I'm able to define a

Re: pipeline multi branch, how to continue if error occures

Either get return code from the executing shell script or surround with try-catch final def returnCode = sh returnStatus: true, script: "" if (returnCode != 0) { } try { sh "" } catch (e) { } tirsdag 13. september 2016 04.10.57 UTC+2 skrev R Tyler Croy følgende: > > (replies inline) > >

Latest changes to Jenkins Pipeline break serializable on KeySet

After upgrade to Jenkins 2.22 and the Pipeline plugins 2.x my build script failed [Pipeline] End of Pipeline java.io.NotSerializableException: java.util.LinkedHashMap$LinkedKeySet It failed when I called map.keySet() which did worked before the update. This was logic executing on a Jenkins flywe

Re: Latest changes to Jenkins Pipeline break serializable on KeySet

at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) tirsdag 13. september 2016 12.55.10 UTC+

Pipeline: Adding properties syntax changed

Using the snippet generator I see that the syntax for properties have changed I have broken it up in multiple lines with indentation so it is easier to read and see all the distinct parts. I have been using the following to add properties in my pipeline script: properties([ [$class: 'Parame

Label on steps in Stage View Log

I believe there was registered an issue with Jenkins regarding the ambiguity of the Stage Log display in Stage View. Having several similar steps in the Log is confusing. Cannot find out which is which. Anyone remember the Jenkins issue? I have tried searching for it, but cannot find it. For ins

Pipeline: Get SCM changes for build

The following will get me the top most git commit hash: def gitCommit = sh(returnStdout: true, script: 'git rev-parse HEAD').trim() The following will get me the top most git commit message: def gitCommitMessage = sh(returnStdout: true, script: 'git log -n 1 --format=%s').trim() However within o

Pipeline: Accessing parameters in build broken

I have previously accessed build parameters the following way: def upstreamNoVerify = false if (getBinding().hasVariable("PARAM")) { upstreamNoVerify = Boolean.parseBoolean(PARAM) } This no longer works and I had to change it to: final def upstreamNoVerify = Boolean.parseBoolean(PARAM) I am b

Re: Pipeline: Accessing parameters in build broken

mandag 26. september 2016 17.29.26 UTC+2 skrev Daniel Beck følgende: > > > > On 26.09.2016, at 13:15, Sverre Moe > > wrote: > > > > I am beginning to get frustrated by this constant changes that breaks > previous behaviour. I have read the changelog of plugins

Pipeline: Check if build parameter exist

I can no longer check if a build parameter exist before accessing it This has worked previously before I updated Jenkins and the Pipeline plugins: def myParam = false if (getBinding().hasVariable("MY_PARAM")) { myParam = Boolean.parseBoolean(MY_PARAM) } final def myParam = MY_PARAM The la

Pipeline: Abort build nightmare

Wanting to abort, but Jenkins would NOT let it be easy. I clikc abort several times (confirmation dialog box each time, clicked OK). I had to go into the Console output and click on the links popping up, but nothing happens, nothing. Aborted by Sverre Moe Aborted by Sverre Moe Aborted by

Multibranch Pipeline: Changes needed on naming

1. Pipeline usernameB/thisFixC Full project name: libraryA/usernameB%2FthisFixC URL: https://build-ci.company.com:8443/job/libraryA/job/usernameB%252FthisFixC/ Why can it not show: Full project name: libraryA/usernameB/thisFixC I can understand it for the URL, but not on the Jenkins job page or c

Re: pipeline - read artifact into node?

Stash it stash includes: 'file.ext', name: 'file' Then later do unstash 'file' mandag 10. oktober 2016 20.11.39 UTC+2 skrev Jonathan Hodgson følgende: > > Hi, > > My pipelne starts with code on the master that creates a file, which I > artifact. > > I need ti use that file in nodes running on th

Re: Jenkinsfile: How to iterate a properties file without having an "java.io.NotSerializableException: java.util.Hashtable$Entry" error

Put it in a method annotated with @NonCPS torsdag 13. oktober 2016 11.18.12 UTC+2 skrev eid badr følgende: > > Hi > > in jenkinsFile.groovy I want to iterate over a properties file, but I > always get an error > how can it be done properly with no error? > > node('master') { > Properties prop

Multibranch Pipeline: GCC errors does not stand out

The Pipeline Stage View, show Logs It should show red color for those steps that has error, I have seen it on some occasions. However it does not highlight those steps that has gcc compile errors. Our developers opinion is that the Console output is difficult to parse. since all the paralell ru

Re: pipeline: Is there a plugin to give a "better console"??

That plugin does not seem to support Pipeline. torsdag 20. oktober 2016 18.02.34 UTC+2 skrev Trever følgende: > > This plugin advertises to allow collapsing sections of the console > > https://wiki.jenkins-ci.org/display/JENKINS/Collapsing+Console+Sections+Plugin > > On Thursday, October 20, 2016

Re: Multibranch Pipeline: GCC errors does not stand out

png> onsdag 19. oktober 2016 09.55.27 UTC+2 skrev Sverre Moe følgende: > > The Pipeline Stage View, show Logs > It should show red color for those steps that has error, I have seen it on > some occasions. However it does not highlight those steps that has gcc > compile errors. >

<    1   2   3   4   >