[JIRA] (JENKINS-39339) Try BlueOcean button should keep currently open pipeline context
Title: Message Title Tom FENNELLY updated JENKINS-39339 Jenkins / JENKINS-39339 Try BlueOcean button should keep currently open pipeline context Change By: Tom FENNELLY Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38913) DSL for choiceParam not working
Title: Message Title ma pi updated an issue Jenkins / JENKINS-38913 DSL for choiceParam not working Change By: ma pi Attachment: 1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32048) Upgrade of Gerrit Trigger Plugin fails
Title: Message Title Andreas Pelzer closed an issue as Fixed Meanwhile we managed to upgrade with completely new versions Jenkins / JENKINS-32048 Upgrade of Gerrit Trigger Plugin fails Change By: Andreas Pelzer Status: Open Closed Assignee: rsandell Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
[JIRA] (JENKINS-39499) There is no way to set changeSet property of shared library checkout to false
Title: Message Title Martin Fousek created an issue Jenkins / JENKINS-39499 There is no way to set changeSet property of shared library checkout to false Issue Type: Bug Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2016/Nov/04 9:16 AM Priority: Major Reporter: Martin Fousek Once we have Shared Library sources in the same repository under different branch, all changes are made to the shared library scripting are listed in the list of build changes. The reason is perhaps that the pipeline shared library checkout is done using the pipeline generic checkout step with the changeset property set to true. Could you provide way how to control it using the global settings or disable it by default as you are rather interested in sources changes than in the pipeline scripting changes please? Add Comment
[JIRA] (JENKINS-39498) Missed Events Playback Feature fails at Jenkins restart
Title: Message Title Andreas Pelzer created an issue Jenkins / JENKINS-39498 Missed Events Playback Feature fails at Jenkins restart Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2016/Nov/04 9:15 AM Environment: Jenkins 2.27 Gerrit Trigger plugin 2.22.0 Gerrit 2.12.2 Jenkins and Gerrit on operating system SLES 11.3 Priority: Major Reporter: Andreas Pelzer Our Jenkins has some 2500 jobs, the majority of them connected to Gerrit projects with Gerrit Trigger plugin. When restarting Jenkins, the Jenkins job queue is filled with some 500 jobs, which have already been run before! In other words: the Gerrit Trigger plugin seems to forget that Jenkins has run theses jobs before. We experienced the same behavior in the passed when we stopped the Gerrit server in the Jenkins Gerrit Trigger configuration and then restarted it. Add Comment
[JIRA] (JENKINS-39497) No recursive expansion in promoted build
Title: Message Title
GMC Software Development B Corporate updated an issue
Jenkins / JENKINS-39497
No recursive expansion in promoted build
Change By:
GMC Software Development B Corporate
We have determined a problem with using an environment-variable, which are defined by using another variable (Ie. recursive expansion) in a promoted build.Following (minimal) scenario:a) Inject environment variable {noformat} Output2=E:\\Temp\\$PROMOTED_NUMBER {noformat} ... and the console shows ...{noformat}[EnvInject] - Injecting environment variables from a build step.[EnvInject] - Injecting as environment variables the properties content Output=E:\Temp\$PROMOTED_NUMBER{noformat}b) Using this variable as Remote File Location in ArtifactDeployer (I.e., $Output) will use "E:\Temp\$PROMOTED_NUMBER" as destination-folder (what was not our expectation).If we configure "E:\Temp\$PROMOTED_NUMBER" as Remote File Location, this will be expanded (eg.) "E:\Temp\42".Sorry - I'm not sure, whether this (assumed) expansion takes place in older versions of this plugin(s) or this behaviour is a regression ...Best regards from Salzburg,Markus
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39497) No recursive expansion in promoted build
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-39497 No recursive expansion in promoted build Issue Type: Bug Assignee: Oleg Nenashev Components: envinject-plugin Created: 2016/Nov/04 9:12 AM Environment: Jenkins 2.25 (on Windows Server 2008 R2 x64), envinject 1.93.1, promoted-builds 2.27 Priority: Major Reporter: GMC Software Development B Corporate We have determined a problem with using an environment-variable, which are defined by using another variable (Ie. recursive expansion) in a promoted build. Following (minimal) scenario: a) Inject environment variable Output2=E:\\Temp$PROMOTED_NUMBER ... and the console shows ... [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content Output=E:\Temp\$PROMOTED_NUMBER b) Using this variable as Remote File Location in ArtifactDeployer (I.e., $Output) will use "E:\Temp\$PROMOTED_NUMBER" as destination-folder (what was not our expectation). If we configure "E:\Temp\$PROMOTED_NUMBER" as Remote File Location, this will be expanded (eg.) "E:\Temp\42". Sorry - I'm not sure, whether this (assumed) expansion takes place in older versions of this plugin(s) or this behaviour is a regression ... Best regards from Salzburg, Markus
[JIRA] (JENKINS-39496) Make PullRequestSCMRevision public
Title: Message Title Raul Arabaolaza started work on JENKINS-39496 Change By: Raul Arabaolaza Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39496) Make PullRequestSCMRevision public
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-39496 Make PullRequestSCMRevision public Issue Type: New Feature Assignee: Raul Arabaolaza Components: github-branch-source-plugin Created: 2016/Nov/04 9:08 AM Priority: Minor Reporter: Raul Arabaolaza In a multibranch pipeline project there is the option to build PR merged with a base branch (typically master or integration branches) to ensure that changes in the final status (merged) are valid. In this cases the revision given by the build data refers to the merge commit, not the last PR commit in the remote `PullRequestSCMRevision` contains info about the pull hash and the base hash that is internally used to notify GitHub. This info could be very interesting to third parties like pipeline steps, but the class visibility is default so is not possible to access it. Add Comment
[JIRA] (JENKINS-39339) Try BlueOcean button should keep currently open pipeline context
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39339 Re: Try BlueOcean button should keep currently open pipeline context Code changed in jenkins User: Tom Fennelly Path: src/main/js/custom_assertions/urlEndsWith.js src/main/js/custom_commands/addOpenBlueOceanLinkToFooter.js src/main/js/custom_commands/openBlueOcean.js src/main/js/globals.js src/main/js/page_objects/blueocean/bluePipelineActivity.js src/main/js/page_objects/classic_jenkins/classicRun.js src/main/nightwatch.json src/test/js/edgeCases/folder.js src/test/js/smoke.js http://jenkins-ci.org/commit/blueocean-acceptance-test/cdf8d0d9c1e5db06951f9de01bf7498a84c7d254 Log: [FIX JENKINS-39339] contextual try Blue Ocean button (#65) Add "Open Blue Ocean" link to footer need it because we removed the header Added a few custom assertions Added some pipeline activity page empty state assertions Added openBlueOcean custom command Add smoke test for the "Open Blue Ocean" button remove urlMatches - unused Fix url encoding in urlEndsWith Make pipeline activity basic layout testing less fragile A test for "Open Blue Ocean" on a freestyle down in a folder Fix urlEndsWith assertion to handle weird characters in a more human way A test for "Open Blue Ocean" on a multibranch run down in a folder
[JIRA] (JENKINS-39495) org.apache.commons.jelly.JellyTagException when open up Jenkins Homepage
Title: Message Title Yun Ken Chow created an issue Jenkins / JENKINS-39495 org.apache.commons.jelly.JellyTagException when open up Jenkins Homepage Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Nov/04 8:55 AM Environment: 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Priority: Major Reporter: Yun Ken Chow Everything seems fine with no errors shown up on the log after using it for weeks. Today I rebooted Wildfly services, then when I open up Jenkins Homepage, I'm seeing this. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: vfs:/content/jenkins.war/WEB-INF/lib/jenkins-core-1.653.jar/hudson/model/View/index.jelly:42:43: org.apache.commons.jelly.JellyTagException: vfs:/content/jenkins.war/WEB-INF/lib/jenkins-core-1.653.jar/lib/hudson/projectView.jelly:67:24: java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:813) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:134) at
[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39289 Re: Better diagnostics on "Backing channel is disconnected" Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/Channel.java src/main/java/hudson/remoting/RemoteInvocationHandler.java http://jenkins-ci.org/commit/remoting/0d8a2af7cffa6aa5a6f2675e810b286a984af04e Log: JENKINS-39289 When a proxy fails, report what caused the channel to go down (#128) Today, this requires out of bound knowledge about which connection the proxy was representing, then use other means to figure out why it has failed. This exception chaining shortens that step and makes it easy to find the cause as to why the channel was shut down. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-28367) perforce plugin don't support P4 ticket authentication
Title: Message Title antonio bur reopened an issue Hi, I have installed the Jenkins server using the perforce plug in 1.3.36, but I still get the following error. Note I sure that the password is right. Can you help on this? [workspace] $ p4 -p ssl:myperforce:1666 trust -y [workspace] $ p4 login -a -p [workspace] $ p4 -P xx workspace -o -S //depot/abcd jenkins_workspace Caught exception communicating with perforce. Perforce password (P4PASSWD) invalid or unset.com.tek42.perforce.PerforceException: Perforce password (P4PASSWD) invalid or unset. Jenkins / JENKINS-28367 perforce plugin don't support P4 ticket authentication Change By: antonio bur Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-32851) Gerrit Connection Breaks on Jenkins 1.609.2 LTS
Title: Message Title Florent D. commented on JENKINS-32851 Re: Gerrit Connection Breaks on Jenkins 1.609.2 LTS Thanks for your fast answer. It doesn't work without posting score. I still have the message "Unable to post review: Request failed." in analysis logs. Nothing changed on Gerrit UI and there is no messages in httpd_log log file (Gerrit server side). I use the default "Code-Review" for posting score. It is already created in Gerrit. Is there a way to add traces in a file to get more information about what doesn't work ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-33326) Programmatic changes to Reactive Reference value do not cascade
Title: Message Title Bruno P. Kinoshita closed an issue as Not A Defect Closed as not a defect Jenkins / JENKINS-33326 Programmatic changes to Reactive Reference value do not cascade Change By: Bruno P. Kinoshita Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34818) Active Choice reactive parameter cannot access global parameters
Title: Message Title Bruno P. Kinoshita closed an issue as Not A Defect Not a defect Jenkins / JENKINS-34818 Active Choice reactive parameter cannot access global parameters Change By: Bruno P. Kinoshita Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34988) this.binding.jenkinsProject not returning project of current build
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Included in 1.5.0 Jenkins / JENKINS-34988 this.binding.jenkinsProject not returning project of current build Change By: Bruno P. Kinoshita Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36806) Extra comma character append at the end when passing Reactive Reference Values to the build
Title: Message Title Bruno P. Kinoshita closed an issue as Not A Defect Not an issue Jenkins / JENKINS-36806 Extra comma character append at the end when passing Reactive Reference Values to the build Change By: Bruno P. Kinoshita Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36868) Unable to get checkbox value from
Title: Message Title Bruno P. Kinoshita closed an issue as Duplicate Duplicated Jenkins / JENKINS-36868 Unable to get checkbox value from Change By: Bruno P. Kinoshita Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36590) Active-Choice jenkinsProject variable is not available under Folder
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Included in 1.5.0 Jenkins / JENKINS-36590 Active-Choice jenkinsProject variable is not available under Folder Change By: Bruno P. Kinoshita Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37027) 'View selected script option' in build configuration displays wrong scriptler script
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Released with 1.5.0 Jenkins / JENKINS-37027 'View selected script option' in build configuration displays wrong scriptler script Change By: Bruno P. Kinoshita Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-28732) Add support to the script security plug-in to Active Choices
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Released in 1.5.0 Jenkins / JENKINS-28732 Add support to the script security plug-in to Active Choices Change By: Bruno P. Kinoshita Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-16805) "Keep this build forever" build gets deleted by "Discard old builds"
Title: Message Title ej santos closed an issue as Cannot Reproduce Sorry, false alarm Jenkins / JENKINS-16805 "Keep this build forever" build gets deleted by "Discard old builds" Change By: ej santos Status: Reopened Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-16805) "Keep this build forever" build gets deleted by "Discard old builds"
Title: Message Title ej santos updated an issue Jenkins / JENKINS-16805 "Keep this build forever" build gets deleted by "Discard old builds" Change By: ej santos Comment: currently running jenkins v2.28 and this issue is happening with our jobsbuilds which got marked as "Keep this build forever" are deleted by "Discard old builds" even though the build.xml contains true.Using: Amazon Linux AMI release 2016.03, java version "1.7.0_101" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39494) Multijob : Incorrect status displayed for project when conditional execution is used
Title: Message Title Pooja Thaker updated an issue Jenkins / JENKINS-39494 Multijob : Incorrect status displayed for project when conditional execution is used Change By: Pooja Thaker Environment: Jenkins v2.7.4 Multijob plugin v1.23 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39010) Comment Added event does not work
Title: Message Title Fathi Boudra commented on JENKINS-39010 Re: Comment Added event does not work yes, unfortunately, reverting to 2.20.0 has incompatibilities with JGit4: http://jenkins-ci.361315.n4.nabble.com/JGit-api-changed-Handling-removal-of-methods-from-an-underlying-API-td4822183.html you'll also need to revert to git-client/1.19.6 and git/2.4.4 as well. Moving forward, the proper fix is really to get comments-added event support fixed. rsandell any chance to get your opinion please? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39494) Multijob : Incorrect status displayed for project when conditional execution is used
Title: Message Title Pooja Thaker created an issue Jenkins / JENKINS-39494 Multijob : Incorrect status displayed for project when conditional execution is used Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 2016/Nov/04 7:30 AM Environment: Jenkins v2.7.4 Priority: Major Reporter: Pooja Thaker Steps to reproduce: 1. Create a free-style project called 'Test Child' 2. Create a multjob project which accepts 1 boolean parameter. Create 1 phase in this project having 2 jobs in it - both are 'Test Child' jobs. Enable condition on both the jobs such that the first job should run if the boolean parameter is set to true & the second job should run if the boolean parameter is set to false. 3. Run the multijob project and observe Actual Result: Console of multijob project states that only 1 build of the 'Test Child' project has been triggered (which is as expected), but, the project status dashboard on the multijob project shows that both the 'Test Child' jobs have been executed and the link to the console of these jobs points to the same build number - giving an incorrect status that 2 jobs have been run whereas only 1 has been run. Expected Result: The project status should indicate clearly that only 1 job has been executed. If 2 builds have been run for the same job via the multijob project, then their links to the console should be different. Setup at our end: We have 'Test Child' as a parameterized job and we wish to pass parameters to this job via the multijob project depending upon the parameters passed to the multijob project.
[JIRA] (JENKINS-16805) "Keep this build forever" build gets deleted by "Discard old builds"
Title: Message Title ej santos reopened an issue currently running jenkins v2.28 and this issue is happening with our jobs Using: Amazon Linux AMI release 2016.03, java version "1.7.0_101" Jenkins / JENKINS-16805 "Keep this build forever" build gets deleted by "Discard old builds" Change By: ej santos Resolution: Incomplete Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-16805) "Keep this build forever" build gets deleted by "Discard old builds"
Title: Message Title ej santos edited a comment on JENKINS-16805 Re: "Keep this build forever" build gets deleted by "Discard old builds" currently running jenkins v2.28 and this issue is happening with our jobs builds which got marked as "Keep this build forever" are deleted by "Discard old builds" even though the build.xml contains true. Using: Amazon Linux AMI release 2016.03, java version "1.7.0_101" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34208) NullPointerException pops up randomly at different steps of a pipeline build
Title: Message Title lsb want commented on JENKINS-34208 Re: NullPointerException pops up randomly at different steps of a pipeline build I seem get the same problem: /opt/jenkins/workspace/COLLINE_SNAPSHOT@4/release/target/standalone/ServerInstall.colline/reform-collineapi-config-1.4.0.0.jar [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: null [INFO] [INFO] Reactor Summary: [INFO] [INFO] colline SUCCESS [ 1.274 s] [INFO] colline-common-parent .. SUCCESS [ 0.110 s] [INFO] colline-common . SUCCESS [ 15.335 s] [INFO] colline-logic .. SUCCESS [ 1.078 s] [INFO] colline-f3-parent .. SUCCESS [ 0.096 s] [INFO] colline-f3-infrastructure .. SUCCESS [ 9.672 s] [INFO] Colline Maven Plugin ... SUCCESS [ 3.333 s] [INFO] colline-build .. SUCCESS [ 0.475 s] [INFO] colline-licence-build .. SUCCESS [ 1.103 s] [INFO] colline-api-metadata ... SUCCESS [ 6.881 s] [INFO] colline-browser SUCCESS [ 0.757 s] [INFO] colline-organisation ... SUCCESS [ 3.270 s] [INFO] colline-trading SUCCESS [ 2.182 s] [INFO] colline-marketdata-parent .. SUCCESS [ 0.104 s] [INFO] colline-marketdata . SUCCESS [ 1.606 s] [INFO] colline-marketdata-client .. SUCCESS [ 0.702 s] [INFO] colline-valuation-parent ... SUCCESS [ 0.097 s] [INFO] colline-valuation-base . SUCCESS [ 1.256 s] [INFO] colline-reports-base-base .. SUCCESS [ 0.825 s] [INFO] colline-reports-base ... SUCCESS [ 2.818 s] [INFO] colline-fx . SUCCESS [ 1.793 s] [INFO] colline-rule-engine SUCCESS [ 1.725 s] [INFO] colline-collateral-parent .. SUCCESS [ 0.102 s] [INFO] colline-collateral-ejb3 SUCCESS [ 4.609 s] [INFO] colline-collateral . SUCCESS [ 35.185 s] [INFO] colline-selfservice SUCCESS [ 1.476 s] [INFO] colline-collateral-reports . SUCCESS [ 10.525 s] [INFO] colline-collateral-report-client ... SUCCESS [ 1.327 s] [INFO] colline-stp SUCCESS [ 1.902 s] [INFO] colline-reconciliation . SUCCESS [ 3.309 s] [INFO] colline-batch .. SUCCESS [ 18.593 s] [INFO] colline-web-service SUCCESS [ 1.855 s] [INFO] colline-api SUCCESS [ 11.734 s] [INFO] colline-ui-infrastructure .. SUCCESS [ 0.368 s] [INFO] lrsux .. SUCCESS [ 28.375 s] [INFO] lrsux-ui ... SUCCESS [ 8.188 s] [INFO] lrsux-legacy ... SUCCESS [ 2.239 s] [INFO] lrsux-legacy-ui SUCCESS [ 1.502 s] [INFO] lrsux-java . SUCCESS [ 4.450 s]
[JIRA] (JENKINS-39493) Improve UI to Abort Pipelines
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-39493 Improve UI to Abort Pipelines Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2016/Nov/04 6:14 AM Environment: Jenkins 2.7.3 Pipeline 2.4 Labels: pipeline user-experience Priority: Major Reporter: Allan BURDAJEWICZ Issue If you cancel a pipeline build (via the red X) but the build does not stop, you need to go to the Console Logs where a button will appears after ~15 seconds to be able to Forcibly terminate the process. Request This is not intuitive and poor UX. It would be great if the UI and/or the functionality in general could be improved. Add Comment
[JIRA] (JENKINS-39156) Unable to set "servers" option in the ActiveDirectory plugin through groovy
Title: Message Title Poornima Lokhande commented on JENKINS-39156 Re: Unable to set "servers" option in the ActiveDirectory plugin through groovy The same was working fine on active_directory version 1.47. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
