[JIRA] (JENKINS-45509) Xcode 9 requires provisioning profile to be specified when using manual code signing
Title: Message Title Jay Trivedi commented on JENKINS-45509 Re: Xcode 9 requires provisioning profile to be specified when using manual code signing Gaurav Borole You need to mention provisioning profile in ExportOptions.plist file. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title bentoi created an issue Jenkins / JENKINS-49686 NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-02-22 07:36 Environment: Jenkins 2.89.4 Priority: Major Reporter: bentoi I have 2 jobs stuck in the build queue waiting, jobs are apparently waiting for 2 other jobs to complete but the nodes executors are free. I don't if these NPE can cause this behavior but they don't look right anyway. Feb 21, 2018 8:38:55 PM org.jenkinsci.plugins.workflow.cps.CpsFlowExecution onLoad WARNING: Pipeline state not properly persisted, cannot resume job/ice/job/3.7/221/ Feb 21, 2018 8:38:55 PM org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService reportProblem WARNING: Unexpected exception in CPS VM thread: CpsFlowExecution[Owner[ice/3.7/221:ice/3.7 #221]] java.lang.NullPointerException at org.jenkinsci.plugins.workflow.job.WorkflowRun$GraphL.onNewHead(WorkflowRun.java:997) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:1368) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.run(CpsThreadGroup.java:412) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35) 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:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
[JIRA] (JENKINS-48662) Provide a means for determining the result of running kubernetesDeploy.
Title: Message Title Menghua Xiao resolved as Fixed Fixed in release 0.1.5. The build aborts if the deployment failed. If you need to recover from the failure, use try...catch... in your pipeline. Jenkins / JENKINS-48662 Provide a means for determining the result of running kubernetesDeploy. Change By: Menghua Xiao Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send
[JIRA] (JENKINS-48662) Provide a means for determining the result of running kubernetesDeploy.
Title: Message Title Menghua Xiao updated an issue Jenkins / JENKINS-48662 Provide a means for determining the result of running kubernetesDeploy. Change By: Menghua Xiao Labels: PendingRelease Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49685) Unable to download the NVD CVE data. Caused by: java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required"
Title: Message Title Philipp Moeller created an issue Jenkins / JENKINS-49685 Unable to download the NVD CVE data. Caused by: java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required" Issue Type: Improvement Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2018-02-22 07:18 Environment: Jenkins 2.89.4, JDK 8u161 Priority: Major Reporter: Philipp Moeller My Jenkins Instance is sitting behind a proxy that requires basic authentication, which is configured in the Jenkins Instance. Updating plugins via https works without problems with the configured proxy. When trying to run the dependencyCheckAnalyzer from a Jenkins Pipeline I get the following error and stack trace: [DependencyCheck] One or more exceptions were thrown while executing Dependency-Check [DependencyCheck] Exception Caught: org.owasp.dependencycheck.data.update.exception.UpdateException [DependencyCheck] Cause: java.util.concurrent.ExecutionException: org.owasp.dependencycheck.utils.DownloadFailedException: Error making HTTP GET request. [DependencyCheck] Message: Unable to download the NVD CVE data. [DependencyCheck] org.owasp.dependencycheck.data.update.exception.UpdateException: Unable to download the NVD CVE data. [DependencyCheck] at org.owasp.dependencycheck.data.update.NvdCveUpdater.update(NvdCveUpdater.java:130) [DependencyCheck] at org.owasp.dependencycheck.Engine.doUpdates(Engine.java:889) [DependencyCheck] at org.owasp.dependencycheck.Engine.initializeAndUpdateDatabase(Engine.java:716) [DependencyCheck] at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:642) [DependencyCheck] at
[JIRA] (JENKINS-49105) Can't send data to influx
Title: Message Title Aleksi Simell commented on JENKINS-49105 Re: Can't send data to influx Timo Sand Looking at your configuration the only things I can think of is that you have http://localhost:8186 instead of http://127.0.0.1:8186 as your url. I have tried to reproduce this with different Jenkins versions without success and if Kevin Phillips is experiencing the same with 2.60.2, then I don't believe this issue is Jenkins version dependant. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49105) Can't send data to influx
Title: Message Title Aleksi Simell edited a comment on JENKINS-49105 Re: Can't send data to influx [~deiga] Looking at your configuration the only things thing I can think of is that you have [http://localhost:8186|http://localhost:8186/] instead of [http://127.0.0.1:8186|http://127.0.0.1:8186/] as your url.I have tried to reproduce this with different Jenkins versions without success and if [~leedega] is experiencing the same with 2.60.2, then I don't believe this issue is Jenkins version dependant. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48662) Provide a means for determining the result of running kubernetesDeploy.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48662 Re: Provide a means for determining the result of running kubernetesDeploy. Code changed in jenkins User: Menghua Xiao Path: src/main/java/com/microsoft/jenkins/kubernetes/KubernetesDeploy.java src/main/resources/com/microsoft/jenkins/kubernetes/Messages.properties http://jenkins-ci.org/commit/kubernetes-cd-plugin/660a7d9e5eeb2714e07b1181603d0d4b547ca2dc Log: Abort build on error, addressing JENKINS-48662 (#12) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49636) git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set
Title: Message Title Mark Waite commented on JENKINS-49636 Re: git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set I don't know of any technique that will give you a different behavior than the current behavior. You could check if the Bitbucket webhook is passing additional parameters which are somehow influencing the plugin. I doubt that is what is happening, but there have been cases in the past where notifyCommit (a different form of notification) was honoring extra parameters and changing behavior as a result of those extra parameters. The webhooks might have a similar behavior. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49636) git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-49636 git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45742) Workspace directory not created
Title: Message Title Tomas Salazar resolved as Fixed Solved in 0.1.5 Jenkins / JENKINS-45742 Workspace directory not created Change By: Tomas Salazar Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48563) Agent Labels missing in GUI
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-48563 Re: Agent Labels missing in GUI Note that when reproducing, I noticed that the labels in the node status page are not missing immediately after adding the faulty label to the freestyle project. Even when reloading the page. Reloading the page after some time exposes it though. I am not too sure why. But the double quotes are definitely the culprit. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46585) Do not generate *.env files in the workspace
Title: Message Title Tomas Salazar commented on JENKINS-46585 Re: Do not generate *.env files in the workspace seems feasible Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49682) Blue Ocean - hangs after selecting github organization
Title: Message Title Alex Kravetz commented on JENKINS-49682 Re: Blue Ocean - hangs after selecting github organization HAR attached: har.txt From the browser console: blueocean-core-js.js:2963 Browser configuration of @jenkins-cd/logging is explained at https://tfennelly.github.io/jenkins-js-logging/index.html#browser-config jenkins-js-extension.js:117367 TypeError: Cannot read property 'items' of undefined at GithubFlowManager._updateRepositories (jenkins-js-extension.js:117384) at executeAction (jenkins-js-extension.js:57770) at GithubFlowManager.res (jenkins-js-extension.js:57742) at jenkins-js-extension.js:117365 at Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49682) Blue Ocean - hangs after selecting github organization
Title: Message Title Alex Kravetz updated an issue Jenkins / JENKINS-49682 Blue Ocean - hangs after selecting github organization Change By: Alex Kravetz Attachment: har.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48198) "TypeError: Cannot read property 'toLowerCase' of undefined" for i18n title
Title: Message Title Vivek Pandey commented on JENKINS-48198 Re: "TypeError: Cannot read property 'toLowerCase' of undefined" for i18n title Øyvind Rørtveit oh sorry, my intent was not to just close the ticket. As you can see comments/evaluation from Josh, we did what we could as it’s not something we can fix in blueocean and this error will go away. Fix made here is to report better error so that you know where/which plugin is failing and with that info we can fix appropriate plugin. If you disagree you can reopen but we did what we could as explained in this ticket. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49682) Blue Ocean - hangs after selecting github organization
Title: Message Title Vivek Pandey commented on JENKINS-49682 Re: Blue Ocean - hangs after selecting github organization Can you check browser console for any error? It will also help debug if you can include HAR file. If there are sensitive info then send it directly to me: vpandey at cloudbees.com. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title jaeyun jeong commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Why is this hash code behind the folder name? is that collision between branches? So, Why does not jenkins.branch.WorkspaceLocatorImpl.PATH_MAX=0 have any problems? Please let me know Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26810) File attribute/symlink support in VirtualFile
Title: Message Title Jesse Glick updated JENKINS-26810 Jenkins / JENKINS-26810 File attribute/symlink support in VirtualFile Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22637) "Copy Artifacts Plugin" should support ArtifactManager
Title: Message Title Jesse Glick updated JENKINS-22637 Jenkins / JENKINS-22637 "Copy Artifacts Plugin" should support ArtifactManager Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49635) Permit VirtualFile to serve external file contents
Title: Message Title Jesse Glick updated JENKINS-49635 Jenkins / JENKINS-49635 Permit VirtualFile to serve external file contents Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title olamy commented on JENKINS-49596 Re: User session memory leak Hi Devin Nusbaum I'd like to do some testing with and without JavaMelody because the issue is not really clear for me. Do you know which version of the monitoring plugin have you tested with to reproduce the problem? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49636) git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set
Title: Message Title Vishal Agrawal assigned an issue to Mark Waite Jenkins / JENKINS-49636 git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set Change By: Vishal Agrawal Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-6701) 404 Error If Parent View of a Nested View Is Set to the Default View
Title: Message Title Ben Kletzine assigned an issue to Unassigned Jenkins / JENKINS-6701 404 Error If Parent View of a Nested View Is Set to the Default View Change By: Ben Kletzine Assignee: Ben Kletzine Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-6701) 404 Error If Parent View of a Nested View Is Set to the Default View
Title: Message Title Ben Kletzine assigned an issue to Ben Kletzine Jenkins / JENKINS-6701 404 Error If Parent View of a Nested View Is Set to the Default View Change By: Ben Kletzine Assignee: Alan Harder Ben Kletzine Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49684) Job DSL Seed job fails on ClassCastException
Title: Message Title
Jeremy Kie created an issue
Jenkins / JENKINS-49684
Job DSL Seed job fails on ClassCastException
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin, promoted-builds-plugin
Created:
2018-02-21 23:09
Environment:
Windows 7, Jenkins 2.89.4, promoted-builds-plugin 2.31.1
Labels:
job-dsl-plugin
Priority:
Minor
Reporter:
Jeremy Kie
Running this Job DSL job('a-test-build') { properties { promotions { promotion { name('Deploy a-test to Production') icon('star-gold') conditions { manual('bob') } actions { actions { triggerBuilder { configs { blockableBuildTriggerConfig { projects('a-test-deploy-prod') block { buildStepFailureThreshold('FAILURE') failureThreshold('FAILURE') unstableThreshold('UNSTABLE') } configs { predefinedBuildParameters { properties('X=Y') textParamValueOnNewLine(false) } } } } } } } } } } } Results in java.lang.ClassCastException: java.lang.String cannot be cast to groovy.util.Node Using actions { steps { ... } } Runs without errors, but is not the desired job result I need. Using a single "steps{}" also results in same ClassCastException. Any help is very much appreciated.
[JIRA] (JENKINS-49683) Minor syntactic fixes, correct handling of NPE while working with SVN SCM
Title: Message Title Michael Seldin created an issue Jenkins / JENKINS-49683 Minor syntactic fixes, correct handling of NPE while working with SVN SCM Issue Type: Improvement Assignee: Michael Seldin Components: hp-application-automation-tools-plugin Created: 2018-02-21 22:57 Labels: 5.3.4-beta Priority: Major Reporter: Michael Seldin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49683) Minor syntactic fixes, correct handling of NPE while working with SVN SCM
Title: Message Title Michael Seldin updated an issue Jenkins / JENKINS-49683 Minor syntactic fixes, correct handling of NPE while working with SVN SCM Change By: Michael Seldin Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49681) Scripts always fail when run in build, but succeed from command line
Title: Message Title Daniel Heid closed an issue as Fixed Jenkins / JENKINS-49681 Scripts always fail when run in build, but succeed from command line Change By: Daniel Heid Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49681) Scripts always fail when run in build, but succeed from command line
Title: Message Title Daniel Heid resolved as Fixed Jenkins / JENKINS-49681 Scripts always fail when run in build, but succeed from command line Change By: Daniel Heid Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49681) Scripts always fail when run in build, but succeed from command line
Title: Message Title Daniel Heid commented on JENKINS-49681 Re: Scripts always fail when run in build, but succeed from command line Okay, there will no longer be problems with spaces in front of the shebang with the upcoming version 2.5.1. Thanks for making the PostBuildScript plugin better! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49681) Scripts always fail when run in build, but succeed from command line
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49681 Re: Scripts always fail when run in build, but succeed from command line Code changed in jenkins User: Daniel Heid Path: README.md pom.xml src/main/java/org/jenkinsci/plugins/postbuildscript/service/CommandExecutor.java src/test/java/org/jenkinsci/plugins/postbuildscript/service/CommandExecutorIT.java src/test/resources/shebang_with_spaces.sh http://jenkins-ci.org/commit/postbuildscript-plugin/a72f93f18317ada38215a9d8569d5a79005ef74f Log: JENKINS-49681 Allowing spaces in front of interpreter Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
Title: Message Title mishal shah commented on JENKINS-43038 Re: Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins Renjith Pillai Did you find a workaround for the x4 slowness? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48011) Calling buildInfo.env.collect after buildInfo.append(server.upload(uploadSpec)) causing NPE in Env.java
Title: Message Title Neelesh Jain commented on JENKINS-48011 Re: Calling buildInfo.env.collect after buildInfo.append(server.upload(uploadSpec)) causing NPE in Env.java We are encountering this NullPointerException as well with the following code : def buildInfo = Artifactory.newBuildInfo() buildInfo.append(server.upload(uploadSpecification)) buildInfo.env.capture = true buildInfo.retention maxBuilds: 10, maxDays: 30, deleteBuildArtifacts: true buildInfo.env.collect() server.publishBuildInfo(buildInfo) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis commented on JENKINS-49625 Re: Config pages of Maven jobs do no load Indeed related, but can be closed as the root cause provided in JENKINS-49630 is in fact the Violations plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49616) Estimated time remaining NA
Title: Message Title Matthias Keller updated an issue Jenkins / JENKINS-49616 Estimated time remaining NA Change By: Matthias Keller Attachment: image-2018-02-21-19-28-24-208.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43911) Environment variables can't be used in agent configuration
Title: Message Title Caleb Mayeux commented on JENKINS-43911 Re: Environment variables can't be used in agent configuration My use case is that I have a pipeline, and part of the way through it I check out a git repo, and set the latest git commit hash to a variable which is used to tag and push a docker image. Later on I have a stage that uses that image, and thus I need the hash to run the stage using an agent based on that image. The only workaround to do this is to take the stage that checks out the code out of the declarative pipeline and do it before. If there were other steps that had to happen before that, I'd have to take them out of the pipeline too, so at that point I'd be basically just not using declarative pipeline because of this issue. I think being able to dynamically assign agents based on the pipeline is an important and powerful ability, and is something that exists in both scripted pipeline and freestyle jobs (you can assign node/label as a parameter for a freestyle job, and a pipeline of freestyle jobs effectively makes each job the equivalent of a "stage" in pipeline terminology). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48820) Blue Ocean plug-in causes stack overflow for big pipeline jobs
Title: Message Title Vivek Pandey updated JENKINS-48820 Jenkins / JENKINS-48820 Blue Ocean plug-in causes stack overflow for big pipeline jobs Change By: Vivek Pandey Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49679) Return value unpacking in pipelinescript causes function to execute twice.
Title: Message Title
Uli Hierl created an issue
Jenkins / JENKINS-49679
Return value unpacking in pipelinescript causes function to execute twice.
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-02-21 19:51
Environment:
Jenkins version: 2.89.1 It is installed via this docker image: https://github.com/jenkinsci/docker.git The docker host runs Debian 8.9
Labels:
pipeline
Priority:
Minor
Reporter:
Uli Hierl
Consider the following pipeline script.
jenkinsfile
def str1 = ''
def str2 = ''
(str1, str2) = addStage()
def addStage()
{
stage('Stage 1')
{
node('master')
{
sh 'echo run stage'
}
}
return ['foo', 'bar']
}
When running the pipeline it will execute the shell command twice. This came unexpected to me and I think it is a bug. When the parameter unpacking is removed from the third line, the script behaves as expected.
[JIRA] (JENKINS-49682) Blue Ocean - hangs after selecting github organization
Title: Message Title Alex Kravetz created an issue Jenkins / JENKINS-49682 Blue Ocean - hangs after selecting github organization Issue Type: Bug Assignee: Unassigned Attachments: blueocean github token.png, blueocean hang.png, var-log-jenkins-jenkins.log Components: blueocean-plugin Created: 2018-02-21 21:40 Environment: Jenkins ver. 2.89.4 BlueOcean ver. 1.4.2 openjdk version "1.8.0_161" OpenJDK Runtime Environment (build 1.8.0_161-b14) OpenJDK 64-Bit Server VM (build 25.161-b14, mixed mode) Amazon Linux EC2 AMI - jenkins installed via yum Using GitHub + access token. Work organization, login via SSH Labels: plugin configuration github token Priority: Major Reporter: Alex Kravetz I am attempting to link a github repository from my company to Blue Ocean. Note that I have my personal github and repositories for the company I work for (see blueocean hang.png). When I get to the "Which organization does the repository belong to", if I just click my personal one it shows all my repositories with no problem. If I select my work organization, it hangs on the next step (see blueocean hang.png screenshot). I've attached the jenkins.log file which shows the following error: "Github accessToken does not have required scopes. Expected scopes 'user:email, repo'" But if you look at the blueocean github token.png, you'll see the appropriate scope is set.
[JIRA] (JENKINS-49680) [Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Title: Message Title Nat Sr updated an issue Jenkins / JENKINS-49680 [Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages Change By: Nat Sr ** ! Please comment the ticket URL if this ticket is duplicated (but I couldn't find the same one yet) ** ! Currently, we have a beautiful presenting of each stages both sequential and parallel stages; however, we cannot repeat the same stage as long as we want yet (I don't see the feature how to do it). For example, at a building a candidate build for qa testing. It is possible that we need to rebuild as many as we until got QA sign off. Do we have a way to repeat this stage and/or have a user interact/input to let the script knows that this is good to go to the next step? The current pipeline blue ocean (groovy) script can run only 1 time and go to the next step. The script itself doesn't have the option that it needs to repeat the step or not. Ex. Stage 1 --> executed following the script of stage 1 --> go to Stage 2 can we have Stage 1 --> executed & ask if you need to re-execute Stage 1 or not before go to Stage 2If we can have this feature, it would be great and practical since we sometimes need to rerun the same stage by using the same script. Without it, we can automate only 1st time and still do the rest of times we need manually. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49680) [Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Title: Message Title Nat Sr created an issue Jenkins / JENKINS-49680 [Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-02-21 20:00 Priority: Major Reporter: Nat Sr Please comment the ticket URL if this ticket is duplicated (but I couldn't find the same one yet) ** Currently, we have a beautiful presenting of each stages both sequential and parallel stages; however, we cannot repeat the same stage as long as we want yet (I don't see the feature how to do it). For example, at a building a candidate build for qa testing. It is possible that we need to rebuild as many as we until got QA sign off. Do we have a way to repeat this stage and/or have a user interact/input to let the script knows that this is good to go to the next step? The current pipeline blue ocean (groovy) script can run only 1 time and go to the next step. The script itself doesn't have the option that it needs to repeat the step or not. Ex. Stage 1 --> executed following the script of stage 1 --> go to Stage 2 can we have Stage 1 --> executed & ask if you need to re-execute Stage 1 or not before go to Stage 2 If we can have this feature, it would be great and practical since we sometimes need to rerun the same stage by using the same script. Without it, we can automate only 1st time and still do the rest of times we need manually.
[JIRA] (JENKINS-49681) Scripts always fail when run in build, but succeed from command line
Title: Message Title Sam Jones commented on JENKINS-49681 Re: Scripts always fail when run in build, but succeed from command line I've updated the issue with a working config/script to reproduce the error, along with what I think the problem is. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49681) Scripts always fail when run in build, but succeed from command line
Title: Message Title
Sam Jones updated an issue
Jenkins / JENKINS-49681
Scripts always fail when run in build, but succeed from command line
Change By:
Sam Jones
[^config.xml] [^testScript.sh] Each time my build runs, PostBuildScript is saying there is an error (project names redacted): {code}[PostBuildScript] - Executing post build scripts.[PostBuildScript] - Executing the script /var/lib/jenkins/workspace///mvp-contexts/updateVms.sh with parameters [/var/lib/jenkins/workspace/].[MCP] $ /bin/bash /tmp/jenkins416424957985231.sh /var/lib/jenkins/workspace/[PostBuildScript] - [ERROR] Problem occurred: Error while executing scriptBuild step 'Execute Scripts' changed build result to FAILUREBuild step 'Execute Scripts' marked build as failure{code}But if I SSH into the Jenkins machine and su to the Jenkins user, I can copy that command from the [MCP] line and run it just fine.I've tried it with just a hello world echo statement in the script with the same result.The parameter is workspace project location so the script can reference workspace files. h1. EDITI think I've figured it out. If there is a space after the shebang (#!) in the script, it fails in the plugin, but running the command from the log output works. I've attached my config.xml and testScript.sh for reproducing the bug.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49681) Scripts always fail when run in build, but succeed from command line
Title: Message Title Sam Jones updated an issue Jenkins / JENKINS-49681 Scripts always fail when run in build, but succeed from command line Change By: Sam Jones Attachment: config.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49681) Scripts always fail when run in build, but succeed from command line
Title: Message Title Sam Jones updated an issue Jenkins / JENKINS-49681 Scripts always fail when run in build, but succeed from command line Change By: Sam Jones Attachment: testScript.sh Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49585) [Question] Assign MASTER role
Title: Message Title Daniel Heid commented on JENKINS-49585 Re: [Question] Assign MASTER role Sorry, I tried and tried, but I still cannot reproduce the problem. I used your configuration and it works on the agent as well as the master. Could you please open your job configuration, save it and send me the resulting config.xml (http://your-jenkins-host:8080/jenkins/job/the-job-name/config.xml)? It seems to me, that the newly introduced role is for whatever reason is not correctly migrated (should be BOTH by default, but seems to be MASTER in your case). With the config.xml provided by you, I want to check, whether the role is correctly assigned. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) UI support for milestone and lock
Title: Message Title Alejandro del Castillo commented on JENKINS-40871 Re: UI support for milestone and lock I ended up re-submitting the reference PR, which just got merged [1], which means that the work on this feature request should be unblocked. [1] https://github.com/jenkinsci/pipeline-milestone-step-plugin/pull/15 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Thanks a lot for the analysis! There is a branch for Violations plugin with a serious rewrite by Tomas Bjerre: https://github.com/jenkinsci/violations-plugin/commits/master . If somebody can try that and verify that the issue dissapears, it could be an additional justification to move forward with that Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49680) [Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Title: Message Title
Nat Sr updated an issue
Jenkins / JENKINS-49680
[Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Change By:
Nat Sr
{color:#14892c}*!!! Please comment the ticket URL if this ticket is duplicated (but I couldn't find the same one yet ) !!!*{color}Currently, we have a beautiful presenting of each stages both sequential and parallel stages; however, we cannot repeat the same stage as long as we want yet (I don't see the feature how to do it). For example, at a building a candidate build for qa testing. It is possible that we need to rebuild as many as we until got QA sign off. Do we have a way to repeat this stage and/or have a user interact/input to let the script knows that this is good to go to the next step? The current pipeline blue ocean (groovy) script can run only 1 time and go to the next step. The script itself doesn't have the option that it needs to repeat the step or not.Ex. Stage 1 --> executed following the script of stage 1 --> go to Stage 2 can we have Stage 1 --> executed & ask if you need to re-execute Stage 1 or not before go to Stage 2If we can have this feature, it would be great and practical since we sometimes need to rerun the same stage by using the same script. Without it, we can automate only 1st time and still do the rest of times we need manually.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Harsimrat Khattra updated an issue Jenkins / JENKINS-49033 Issue with HPE Application Automation Tools plugin Change By: Harsimrat Khattra Attachment: jenkins_output.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev Component/s: warnings-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49665) Failed intial boot attempt.
Title: Message Title John Daniel Babu closed an issue as Fixed fixed Jenkins / JENKINS-49665 Failed intial boot attempt. Change By: John Daniel Babu Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49675) screenResolution cookie set without explicit permission, likely GDPR violation
Title: Message Title Wadeck Follonier commented on JENKINS-49675 Re: screenResolution cookie set without explicit permission, likely GDPR violation First point, related to the Cookie Consent, the law is clear concerning which cookie are exempt from any consent. One type of exemption is for the "user‑interface customisation" (source). I consider the resolution to be used only for customization of the interface and nothing else. As the product is open-source, you can check yourself that the resolution is never used for any other objective. From my PoV it comply completely to be put in that category and so, do not require any consent. Second point, related to the GDPR, the definition of what is personal data : "‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;" (source) As you may know, the resolution distribution among the population is somewhat standard and cannot be used to strictly identify someone. So from my PoV, there is no reason the screen resolution is a personal data or an information usable to identify the person. If you find something else that could be impacted by the GPDR or are not convinced by my arguments, just tell me. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this
[JIRA] (JENKINS-14463) email ext plugin : full console log mail
Title: Message Title Alex Earl commented on JENKINS-14463 Re: email ext plugin : full console log mail Please use the mailing list for questions. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49680) [Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Title: Message Title
Nat Sr updated an issue
Jenkins / JENKINS-49680
[Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Change By:
Nat Sr
{color:#14892c}*!!! Please comment the ticket URL if this ticket is duplicated !!!*{color}Currently, we have a beautiful presenting of each stages both sequential and parallel stages; however, we cannot repeat the same stage as long as we want yet (I don't see the feature how to do it). For example, at a building a candidate build for qa testing. It is possible that we need to rebuild as many as we until got QA sign off. Do we have a way to repeat this stage and/or have a user interact/input to let the script knows that this is good to go to the next step? The current pipeline blue ocean (groovy) script can run only 1 time and go to the next step. The script itself doesn't have the option that it needs to repeat the step or not.Ex. Stage 1 --> executed following the script of stage 1 --> go to Stage 2 (sequential)/1.1(parallel) can we have Stage 1 --> executed & ask if you need to re-execute Stage 1 or not before go to Stage 2 (sequential)/1.1(parallel) If we can have this feature, it would be great and practical since we sometimes need to rerun the same stage by using the same script. Without it, we can automate only 1st time and still do the rest of times we need manually.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49680) [Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Title: Message Title Nat Sr updated an issue Jenkins / JENKINS-49680 [Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages Change By: Nat Sr !!! !! Please comment the ticket URL if this ticket is duplicated (but I couldn't find the same one yet) !!! !! Currently, we have a beautiful presenting of each stages both sequential and parallel stages; however, we cannot repeat the same stage as long as we want yet (I don't see the feature how to do it). For example, at a building a candidate build for qa testing. It is possible that we need to rebuild as many as we until got QA sign off. Do we have a way to repeat this stage and/or have a user interact/input to let the script knows that this is good to go to the next step? The current pipeline blue ocean (groovy) script can run only 1 time and go to the next step. The script itself doesn't have the option that it needs to repeat the step or not.Ex. Stage 1 --> executed following the script of stage 1 --> go to Stage 2 can we have Stage 1 --> executed & ask if you need to re-execute Stage 1 or not before go to Stage 2If we can have this feature, it would be great and practical since we sometimes need to rerun the same stage by using the same script. Without it, we can automate only 1st time and still do the rest of times we need manually. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49681) Scripts always fail when run in build, but succeed from command line
Title: Message Title Sam Jones created an issue Jenkins / JENKINS-49681 Scripts always fail when run in build, but succeed from command line Issue Type: Bug Assignee: Daniel Heid Components: postbuildscript-plugin Created: 2018-02-21 20:28 Environment: Ubuntu 16.04.3 LTS Jenkins 2.89.4 PostBuildScript plugin 2.5.0 Priority: Major Reporter: Sam Jones Each time my build runs, PostBuildScript is saying there is an error: [PostBuildScript] - Executing post build scripts. [PostBuildScript] - Executing the script /var/lib/jenkins/workspace///mvp-contexts/updateVms.sh with parameters [/var/lib/jenkins/workspace/]. [MCP] $ /bin/bash /tmp/jenkins416424957985231.sh /var/lib/jenkins/workspace/ [PostBuildScript] - [ERROR] Problem occurred: Error while executing script Build step 'Execute Scripts' changed build result to FAILURE Build step 'Execute Scripts' marked build as failure But if I SSH into the Jenkins machine and su to the Jenkins user, I can copy that command from the [MCP] line and run it just fine. I've tried it with just a hello world echo statement in the script with the same result. The parameter is workspace project location so the script can reference workspace files.
[JIRA] (JENKINS-49681) Scripts always fail when run in build, but succeed from command line
Title: Message Title Daniel Heid commented on JENKINS-49681 Re: Scripts always fail when run in build, but succeed from command line Thanks for submitting this issue! I must reproduce the problem in order to fix it. Could you please provide the script and the job configuration (config.xml)? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49675) screenResolution cookie set without explicit permission, likely GDPR violation
Title: Message Title Oleg Nenashev commented on JENKINS-49675 Re: screenResolution cookie set without explicit permission, likely GDPR violation In the current state Jenkins Web UI won't work without cookies, its session manager depends on that. Technically it would be possible to ask for permissions if the approval cookie is not set. Whether it is feasible or not -TBD Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-49596
Re: User session memory leak
[~olamy] Yes it is a JavaMelody class, [here|https://github.com/javamelody/javamelody/blob/master/javamelody-core/src/main/java/net/bull/javamelody/SessionListener.java] is the source code. I am not super familiar with JavaMelody, but it looks like it provides monitoring of various information, including http sessions, and allows http sessions to be invalidated manually. There is a JavaMelody Jenkins plugin with some details [here|https://wiki.jenkins.io/display/JENKINS/Monitoring].Thanks for preparing the {{winstone-4.1.x}} branch with so the fix can be backported! Is there anything I can do to help you get that branch released?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title Devin Nusbaum commented on JENKINS-49596 Re: User session memory leak olamy Yes it is a JavaMelody class, here is the source code. I am not super familiar with JavaMelody, but it looks like it provides monitoring of various information, including http sessions, and allows http sessions to be invalidated manually. There is a JavaMelody Jenkins plugin with some details here. Thanks for preparing the winstone-4.1.x branch with so the fix can be backported! Is there anything I can do to help you get that branch released? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis closed an issue as Duplicate Jenkins / JENKINS-49625 Config pages of Maven jobs do no load Change By: Christoph Dreis Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Grim Reaper edited a comment on JENKINS-12783 Re: Delete workspace before build starts ignores Exlude patterns (for directories) Jenkins Versions: 2.60.3 & 2.73.3 (WAR deployments on WildFly)Plugin Version: 0.34Platform: LinuxPlugins:Git client plugin 2.6.0Git plugin 3.6.4Details:No issues when the SCM is CVS. However we are migrating from CVS to GIT.When I configure a freestyle job to use GIT as the SCM and with "Delete workspace before build starts" checked it ignores any "Advanced" options I use (I'm trying to exclude ' * * .build.* * ' and a 'reports/**' directory) and just deletes everything in the entire workspace.In troubleshooting I also testing the Post Build Action > "Delete workspace when build is done". This half works. I can tell it to "Exclude" specific files, but as soon as the "Apply pattern also on directories" is checked it goes back to the above behavior of deleting everything regardless of excludes.Really hoping someone can have a look at this and find the root cause and a fix.Thanks in advance! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49616) Estimated time remaining NA
Title: Message Title
Matthias Keller edited a comment on JENKINS-49616
Re: Estimated time remaining NA
Same here, we're seeing this since the last updates. Most projects are pipelines as well. Right after starting (and probably before the pipeline really starts), the ETA is displayed. However, shortly afterwards and until the build is completely finished, the time isn't here anymore:!image-2018-02-21-19-28-24-208.png!According to [https://groups.google.com/forum/#!topic/jenkinsci-users/BdKmRrkjir4] the bug is very easy to fix:Resetting the executableEstimatedDuration only when there is no asynchrounous execution seems to solve the problem. So the resulting Code in hudson.model.Executor is { color code : #00 java } [...] {color}{color:#00} {color}{color:#00} 458 {color } {color:#00} {color}{color:#00}}{color} {color:#88} finally{ color} {color:#00}\{{color}{color:#00} {color}{color:#00} 459 {color}{color:#00} {color}{color:#88} if {color} {color:#00} ( {color}{color:#00} asynchronousExecution {color}{color:#00} == {color} {color:#88} null {color}{color:#00} ){ color} {color:#00}\{{color}{color:#00} {color}{color:#00} 460 {color}{color:#00} finish2 {color}{color:#00} (); {color}{color:#00} {color}{color:#00} 461 {color}{color:#00} executableEstimatedDuration {color}{color:#00} = {color}{color:#00} DEFAULT_ESTIMATED_DURATION {color}{color:#00} ; {color}{color:#00} {color}{color:#00} 462 {color } {color:#00} {color}{color:#00}}{color}{color:#00} {color}{color:#00} 463 {color } {color:#00} {color}{color:#00}}{color}{color:#00} {color}{color:#00} [...]{ color code }
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43427) git-plugin with both LFS and Sparse checkout behaviour pulls too many files
Title: Message Title Pamela B commented on JENKINS-43427 Re: git-plugin with both LFS and Sparse checkout behaviour pulls too many files I am also having this issue. Any updates? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Harsimrat Khattra commented on JENKINS-49033 Re: Issue with HPE Application Automation Tools plugin Hi so i fixed all the issues and now i get a clean log, but still i get NoData for a lot fo tests. Also I see that the hits/sec are not as much when i run the scenario manually. Running manually, i get about 350 hits/sec on average. here the hits/sec are just 62. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49680) [Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Title: Message Title
Nat Sr updated an issue
Jenkins / JENKINS-49680
[Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Change By:
Nat Sr
{color:#14892c}*!!! Please comment the ticket URL if this ticket is duplicated (but I couldn't find the same one ) !!!*{color}Currently, we have a beautiful presenting of each stages both sequential and parallel stages; however, we cannot repeat the same stage as long as we want yet (I don't see the feature how to do it). For example, at a building a candidate build for qa testing. It is possible that we need to rebuild as many as we until got QA sign off. Do we have a way to repeat this stage and/or have a user interact/input to let the script knows that this is good to go to the next step? The current pipeline blue ocean (groovy) script can run only 1 time and go to the next step. The script itself doesn't have the option that it needs to repeat the step or not.Ex. Stage 1 --> executed following the script of stage 1 --> go to Stage 2 can we have Stage 1 --> executed & ask if you need to re-execute Stage 1 or not before go to Stage 2If we can have this feature, it would be great and practical since we sometimes need to rerun the same stage by using the same script. Without it, we can automate only 1st time and still do the rest of times we need manually.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49681) Scripts always fail when run in build, but succeed from command line
Title: Message Title
Sam Jones updated an issue
Jenkins / JENKINS-49681
Scripts always fail when run in build, but succeed from command line
Change By:
Sam Jones
Each time my build runs, PostBuildScript is saying there is an error (project names redacted) : {code}[PostBuildScript] - Executing post build scripts.[PostBuildScript] - Executing the script /var/lib/jenkins/workspace///mvp-contexts/updateVms.sh with parameters [/var/lib/jenkins/workspace/].[MCP] $ /bin/bash /tmp/jenkins416424957985231.sh /var/lib/jenkins/workspace/[PostBuildScript] - [ERROR] Problem occurred: Error while executing scriptBuild step 'Execute Scripts' changed build result to FAILUREBuild step 'Execute Scripts' marked build as failure{code}But if I SSH into the Jenkins machine and su to the Jenkins user, I can copy that command from the [MCP] line and run it just fine.I've tried it with just a hello world echo statement in the script with the same result.The parameter is workspace project location so the script can reference workspace files.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Tomas Bjerre commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 For the record, future of violations plugin is discussed here: https://github.com/jenkinsci/violations-plugin/issues/88 I don't mind releasing it. Should require minimal effort from my part to maintain as I already maintain the lib for a bunch of other tools. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49616) Estimated time remaining NA
Title: Message Title Aaron Curley commented on JENKINS-49616 Re: Estimated time remaining NA Also seeing this on LTS 2.89.4 after upgrading from 2.89.2. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49680) [Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Title: Message Title
Nat Sr updated an issue
Jenkins / JENKINS-49680
[Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Change By:
Nat Sr
{color:#14892c}* !!! Please comment the ticket URL if this ticket is duplicated (but I couldn't find the same one yet) !!! *{color} Currently, we have a beautiful presenting of each stages both sequential and parallel stages; however, we cannot repeat the same stage as long as we want yet (I don't see the feature how to do it). For example, at a building a candidate build for qa testing. It is possible that we need to rebuild as many as we until got QA sign off. Do we have a way to repeat this stage and/or have a user interact/input to let the script knows that this is good to go to the next step? The current pipeline blue ocean (groovy) script can run only 1 time and go to the next step. The script itself doesn't have the option that it needs to repeat the step or not.Ex. Stage 1 --> executed following the script of stage 1 --> go to Stage 2 can we have Stage 1 --> executed & ask if you need to re-execute Stage 1 or not before go to Stage 2If we can have this feature, it would be great and practical since we sometimes need to rerun the same stage by using the same script. Without it, we can automate only 1st time and still do the rest of times we need manually.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49680) [Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Title: Message Title
Nat Sr updated an issue
Jenkins / JENKINS-49680
[Blue Ocean][Jenkinsfile] repeat stage requests for both sequential and parallel stages
Change By:
Nat Sr
{color:#14892c}*!!! Please comment the ticket URL if this ticket is duplicated (but I couldn't find the same one) !!!*{color}Currently, we have a beautiful presenting of each stages both sequential and parallel stages; however, we cannot repeat the same stage as long as we want yet (I don't see the feature how to do it). For example, at a building a candidate build for qa testing. It is possible that we need to rebuild as many as we until got QA sign off. Do we have a way to repeat this stage and/or have a user interact/input to let the script knows that this is good to go to the next step? The current pipeline blue ocean (groovy) script can run only 1 time and go to the next step. The script itself doesn't have the option that it needs to repeat the step or not.Ex. Stage 1 --> executed following the script of stage 1 --> go to Stage 2 can we have Stage 1 --> executed & ask if you need to re-execute Stage 1 or not before go to Stage 2If we can have this feature, it would be great and practical since we sometimes need to rerun the same stage by using the same script. Without it, we can automate only 1st time and still do the rest of times we need manually.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Harsimrat Khattra updated an issue Jenkins / JENKINS-49033 Issue with HPE Application Automation Tools plugin Change By: Harsimrat Khattra Attachment: HTML.html Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Harsimrat Khattra commented on JENKINS-49033 Re: Issue with HPE Application Automation Tools plugin Attached the output and the html report generated. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26810) File attribute/symlink support in VirtualFile
Title: Message Title Jesse Glick commented on JENKINS-26810 Re: File attribute/symlink support in VirtualFile Also: support for explicit and default excludes in list. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49665) Failed intial boot attempt.
Title: Message Title John Daniel Babu commented on JENKINS-49665 Re: Failed intial boot attempt. Hi Oleg, Got the solution. Changed the port number in jenkins.xml file and restarted the system. It worked. Regards John Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14463) email ext plugin : full console log mail
Title: Message Title santhosh s commented on JENKINS-14463 Re: email ext plugin : full console log mail Hi Dev D, i am using the below code for Build_log maxline override but it is not working.Could you pls help me. emailext body: '''$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS: $BUILD_LOG maxLines=8000, escapeHtml=true Check console output at $BUILD_URL to view the results.''', subject: '$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS!', to: 'santhosha.shankaramur...@sanofi.com' Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49616) Estimated time remaining NA
Title: Message Title
Matthias Keller commented on JENKINS-49616
Re: Estimated time remaining NA
Same here, we're seeing this since the last updates. Most projects are pipelines as well. Right after starting (and probably before the pipeline really starts), the ETA is displayed. However, shortly afterwards and until the build is completely finished, the time isn't here anymore: According to https://groups.google.com/forum/#!topic/jenkinsci-users/BdKmRrkjir4 the bug is very easy to fix: Resetting the executableEstimatedDuration only when there is no asynchrounous execution seems to solve the problem. So the resulting Code in hudson.model.Executor is [...]458 {color:#00}} finally {459 if (asynchronousExecution == null) {460 finish2();461 executableEstimatedDuration = DEFAULT_ESTIMATED_DURATION;462 {color:#00}}463 {color:#00}}[...]
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Grim Reaper updated an issue Jenkins / JENKINS-12783 Delete workspace before build starts ignores Exlude patterns (for directories) Change By: Grim Reaper Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Grim Reaper updated an issue Jenkins / JENKINS-12783 Delete workspace before build starts ignores Exlude patterns (for directories) Change By: Grim Reaper Environment: OP - Linux, Jenkins ver. 1.451, plugin 0.7, job running on master or slaveGrim: Jenkins Versions: 2.60.3 & 2.73.3 (WAR deployments on WildFly) Plugin Version: 0.34 Platform: Linux Plugins: Git client plugin 2.6.0 Git plugin 3.6.4 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34140) Allow to specify node for load from SCM (Jenkinsfile)
Title: Message Title Andrew Bayer commented on JENKINS-34140 Re: Allow to specify node for load from SCM (Jenkinsfile) No, that just skips the automatic checkout on the agent. This ticket is about where the Jenkinsfile gets read in the first place - which is just on master. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Grim Reaper updated an issue Jenkins / JENKINS-12783 Delete workspace before build starts ignores Exlude patterns (for directories) Change By: Grim Reaper Environment: OP - Linux, Jenkins ver. 1.451, plugin 0.7, job running on master or slaveGrim - : Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Grim Reaper updated an issue Jenkins / JENKINS-12783 Delete workspace before build starts ignores Exlude patterns (for directories) Change By: Grim Reaper Environment: OP - Linux, Jenkins ver. 1.451, plugin 0.7, job running on master or slave Grim - Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33995) ExecutorStep::labels should be recorded in the FlowNode graph
Title: Message Title Andrew Bayer commented on JENKINS-33995 Re: ExecutorStep::labels should be recorded in the FlowNode graph Is this still relevant or can we close it as won't fix? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Grim Reaper commented on JENKINS-12783 Re: Delete workspace before build starts ignores Exlude patterns (for directories) Jenkins Versions: 2.60.3 & 2.73.3 (WAR deployments on WildFly) Plugin Version: 0.34 Platform: Linux Plugins: Git client plugin 2.6.0 Git plugin 3.6.4 Details: No issues when the SCM is CVS. However we are migrating from CVS to GIT. When I configure a freestyle job to use GIT as the SCM and with "Delete workspace before build starts" checked it ignores any "Advanced" options I use (I'm trying to exclude ' .build. ' and a 'reports/**' directory) and just deletes everything in the entire workspace. In troubleshooting I also testing the Post Build Action > "Delete workspace when build is done". This half works. I can tell it to "Exclude" specific files, but as soon as the "Apply pattern also on directories" is checked it goes back to the above behavior of deleting everything regardless of excludes. Really hoping someone can have a look at this and find the root cause and a fix. Thanks in advance! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33869) Run tests for previous commits
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-33869 Run tests for previous commits Change By: Andrew Bayer Component/s: core Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49675) screenResolution cookie set without explicit permission, likely GDPR violation
Title: Message Title Jesse Glick commented on JENKINS-49675 Re: screenResolution cookie set without explicit permission, likely GDPR violation Never mind, I was not searching properly. It is used, for example here. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47170) Project-Cheetah: More complex improvements to pipeline storage and scaling
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-47170 Project-Cheetah: More complex improvements to pipeline storage and scaling Change By: Sam Van Oort Summary: Improvements Project-Cheetah: More complex improvements to pipeline storage and performance scaling Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48824) Fast mode: declarative job persists after attempted kills. Jenkins restart shows com.thoughtworks.xstream.io.StreamException on bringup
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-48824 Fast mode: declarative job persists after attempted kills. Jenkins restart shows com.thoughtworks.xstream.io.StreamException on bringup Change By: Sam Van Oort Labels: project-cheetah Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33837) Option to wait for transitive downstream builds to complete
Title: Message Title Andrew Bayer resolved as Won't Fix If the downstream build doesn't itself wait for its own downstreams to complete, I don't think it makes sense to add additional logic to the build step to watch for downstreams of the downstreams and so forth and wait for them too. Jenkins / JENKINS-33837 Option to wait for transitive downstream builds to complete Change By: Andrew Bayer Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-49086) Lazy-initialize FlowNodeStorage and heads, etc
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-49086 Lazy-initialize FlowNodeStorage and heads, etc Change By: Sam Van Oort Labels: performance pipeline project-cheetah Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49084) Reduce the amount of data written for FlowNodes by reducing size on disk
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-49084 Reduce the amount of data written for FlowNodes by reducing size on disk Change By: Sam Van Oort Labels: performance pipeline pipeline-improvement project-cheetah Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48826) Branches within a MBP run under a previously-overridden mode after the override has been removed
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-48826 Branches within a MBP run under a previously-overridden mode after the override has been removed Change By: Sam Van Oort Labels: project-cheetah Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49512) Mac Slave is getting disconnected frequently
Title: Message Title Sapan Garg updated an issue Jenkins / JENKINS-49512 Mac Slave is getting disconnected frequently Change By: Sapan Garg Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33614) Link to script approval from build console
Title: Message Title Andrew Bayer commented on JENKINS-33614 Re: Link to script approval from build console PR up to add a console log link to the script approval page when a RejectedAccessException pops up. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47174) Optimize incidental persistence calls during pipeline execution
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-47174 Optimize incidental persistence calls during pipeline execution Change By: Sam Van Oort Labels: performance project-cheetah Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33761) Ability to disable Pipeline durability and "resume" build.
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-33761 Ability to disable Pipeline durability and "resume" build. Change By: Sam Van Oort Labels: project-cheetah Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48806) Inline help for speed/durability override is missing from multibranch project Configure page
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-48806 Inline help for speed/durability override is missing from multibranch project Configure page Change By: Sam Van Oort Labels: project-cheetah Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47173) Offer a high-performance storage engine for pipeline at some cost to resumability
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-47173 Offer a high-performance storage engine for pipeline at some cost to resumability Change By: Sam Van Oort Labels: performance project-cheetah Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
