[JIRA] [cloudbees-folder-plugin] (JENKINS-25240) DeadBranchStrategy should avoid deleting projects with active jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25240 Re: DeadBranchStrategy should avoid deleting projects with active jobs Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/DefaultOrphanedItemStrategy.java src/test/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/39ad52053cf5f4a65192ac9338d515113a0694a6 Log: Merge pull request #44 from jglick/orphaned-job-running-build- JENKINS-25240 JENKINS-25240 Do not delete branch projects with running builds Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/8df445af2675...39ad52053cf5 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pipeline-stage-view-plugin] (JENKINS-33656) Can't expand logs in Stage Log Popover
Title: Message Title Logan Glickfield created an issue Jenkins / JENKINS-33656 Can't expand logs in Stage Log Popover Issue Type: Bug Assignee: Antonio Muñiz Attachments: test pipeline Jenkins .png Components: pipeline-stage-view-plugin Created: 2016/Mar/18 3:38 PM Environment: Chrome: 48.0.2564.116 Jenkins: 1.652 Priority: Minor Reporter: Logan Glickfield The different nodes in the Stage Log Popover do not expand to show the associated logs. I noticed in Chrome Inspector, the details are there, but clicking anywhere on the node makes no changes. I do not see any console errors.
[JIRA] [subversion-plugin] (JENKINS-33617) Can't see SVN_URL and SVN_REVISION in environment variable
Title: Message Title pras sawant created an issue Jenkins / JENKINS-33617 Can't see SVN_URL and SVN_REVISION in environment variable Issue Type: Bug Assignee: Unassigned Attachments: Subversion issue.jpg Components: subversion-plugin Created: 2016/Mar/17 11:55 AM Environment: CI server Priority: Blocker Reporter: pras sawant Hi I can't see SVN_URL and SVN_REVISION in environment variable I am using Jenkins 1.652 on windows server with Subversion Plugin 2.5.7 and Subversion Tag Plugin 1.18 Attached screen shot , it's holding me from creating build tags in SVN
[JIRA] [core] (JENKINS-33038) FutureImpl.cancel() doesn't cancel the linked job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33038 Re: FutureImpl.cancel() doesn't cancel the linked job Code changed in jenkins User: Yoann Dubreuil Path: core/src/main/java/hudson/model/queue/WorkUnit.java core/src/main/java/hudson/model/queue/WorkUnitContext.java http://jenkins-ci.org/commit/jenkins/8d3eb20e5d82cf3528849301493ec5b2ddf9dd87 Log: JENKINS-33038 correctly set executor in FutureImpl This patch fixes cancellation of the build linked to the Future object. Before, the executor set in FutureImpl was always empty, because WorkUnitContext.createWorkUnit() is not called from an Executor thread anymore. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [branch-api-plugin] (JENKINS-32670) Improperly filtered branch properties for multibranch pipelines
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32670 Re: Improperly filtered branch properties for multibranch pipelines Code changed in jenkins User: Jesse Glick Path: multibranch/pom.xml multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/WorkflowMultiBranchProjectTest.java http://jenkins-ci.org/commit/workflow-plugin/96460b497b3427fcfba461fbcf45933318b91b34 Log: JENKINS-32670 Integration test showing that branch property strategies are hidden by default for multibranch Pipeline projects. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33571) Installing "All" plugins in Getting Started dialogue results in a broken Jenkins installation
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33571 Installing "All" plugins in Getting Started dialogue results in a broken Jenkins installation Change By: Jesse Glick Component/s: slack-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-trigger-plugin] (JENKINS-26103) Workflow step to send approval "vote" to a change
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26103 Re: Workflow step to send approval "vote" to a change Code changed in jenkins User: Teemu Murtola Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpander.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemory.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/workflow/GerritReviewStep.java src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/workflow/GerritReviewStep/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/workflow/GerritReviewStep/help-customUrl.html src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/WorkflowTest.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/3e31f724712d5a6f43605f18f601ca0d18d63423 Log: Allow setting custom url in workflow Extend the gerritReview workflow step to also allow setting the URL to post. Use the existing mechanism (BuildMemory) for storing the value while the build is running. Implements a limited part of JENKINS-26103. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [emailext-template-plugin] (JENKINS-33612) Provision error (Tried proxying due circular dependency) reported at startup
Title: Message Title
GMC Software Development B&R Corporate updated an issue
Jenkins / JENKINS-33612
Provision error (Tried proxying due circular dependency) reported at startup
Change By:
GMC Software Development B&R Corporate
Hi,On start-up of out our jenkins-master, I've got following Email Extension Template Plugin related entry in the Jenkins Log:{noformat}Mar 16, 2016 1:08:18 PM WARNING hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorFailed to instantiate Key[type=org.jenkinsci.plugins.emailext_template.ExtendedEmailTemplatePublisher$DescriptorImpl, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Guice provision errors:1) Tried proxying org.jenkinsci.plugins.emailext_template.ExtendedEmailTemplatePublisher$DescriptorImpl to support a circular dependency, but it is not an interface.1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:389) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1231) at hudson.plugins.emailext.plugins.recipients.UpstreamComitterRecipientProvider.(UpstreamComitterRecipientProvider.java:36) at sun.misc.Unsafe.allocateInstance(Native Method) at com.thoughtworks.xstream.converters.reflection.SunLimitedUnsafeReflectionProvider.newInstance(SunLimitedUnsafeReflectionProvider.java:76) at hudson.util.RobustReflectionConverter.instantiateNewInstance(RobustReflectionConverter.java:395) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:228) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:80) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.A
[JIRA] [core] (JENKINS-33619) Script definition area rendered over header section
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-33619 Script definition area rendered over header section Change By: Antonio Muñiz Attachment: config.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [support-core-plugin] (JENKINS-21670) Option to anonymize customer labels
Title: Message Title Arnaud Héritier commented on JENKINS-21670 Re: Option to anonymize customer labels +1 with Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [branch-api-plugin] (JENKINS-25240) DeadBranchStrategy should avoid deleting projects with active jobs
Title: Message Title Jesse Glick started work on JENKINS-25240 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pipeline-stage-view-plugin] (JENKINS-33625) Enhanced APIs for pipeline stage view, to return specifically needed UI data WITH PAGING
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-33625 Enhanced APIs for pipeline stage view, to return specifically needed UI data WITH PAGING Issue Type: Improvement Assignee: Antonio Muñiz Components: pipeline-stage-view-plugin Created: 2016/Mar/17 3:18 PM Priority: Minor Reporter: Sam Van Oort It would be helpful to provide data that the UI needs in more selective ways, and enable paging for all APIs rather than just hard-capping specific items: Number of artifacts (MAX_ARTIFACTS_COUNT) Number of child stage nodes (MAX_CHILD_NODES) Size of returned log (MAX_RETURN_CHARS) Number of runs per page (RUN_PAGE_SIZE) To support this: APIs should support an offset and count for pageable items
[JIRA] [core] (JENKINS-33619) Script definition area rendered over header section
Title: Message Title Daniel Beck commented on JENKINS-33619 Re: Script definition area rendered over header section gus reiber should probably take a look at this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33597) White Screen of Death (in the web UI) when updating to Jenkins 1.653
Title: Message Title Brian Wilson commented on JENKINS-33597 Re: White Screen of Death (in the web UI) when updating to Jenkins 1.653 I've been able to spin up a private VM with a similar profile: Linux 2.6.18-402.el5 jdk1.8.0_66 etc. I went through the web UI update from 1.652 to 1.653 and checked the restart button. The system seemed to restart and the 1.653 revision did show in the lower right corner. When I executed the "http://:8080/restart" option, I again got the blank white web UI screen. This has happened on three different Master servers very consistently. I think there is a serious issue with the 1.653 release. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33599) Finding security token from console log can be very hard
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-33599 Re: Finding security token from console log can be very hard I'm taking this over to free up time of Keith Zantow so that he can work on other stuff for 2.0 that only he can do, like scrollspy. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33534) Missing content when executing the plugin installs
Title: Message Title Keith Zantow commented on JENKINS-33534 Re: Missing content when executing the plugin installs gus reiber I've reproduced this in IE Edge - it looks like the DOM isn't getting updated in some cases. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-pipeline-plugin] (JENKINS-33178) Build pipeline displays incorrectly when triggering the same project multiple times with different parameters
Title: Message Title Ezbon Jacob commented on JENKINS-33178 Re: Build pipeline displays incorrectly when triggering the same project multiple times with different parameters I have the same issue. Is there any fix or workaround for this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [scripted-cloud-plugin] (JENKINS-33654) Cannot specify number of executors for Scripted Cloud nodes
Title: Message Title
Giuseppe Landolfi updated an issue
Jenkins / JENKINS-33654
Cannot specify number of executors for Scripted Cloud nodes
Change By:
Giuseppe Landolfi
Number of executors for Scripted Cloud nodes is set to 1 and cannot be changed.Workaround:- change manually the value in $JENKINS_HOME/nodes//config.xml file: {{{color:red}*1*{color}}}- restart Jenkins. Note: the value will be reset to 1 every time you open the node configuration page and click "Save"
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-33568) Upgrading to 2.0 for an existing installation forces the Getting Started dialogue
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-33568 Re: Upgrading to 2.0 for an existing installation forces the Getting Started dialogue It is critical that upgrading users get the same level of functionalities that those who are installing 2.0 fresh. But I hear what R. Tyler Croy is saying. I wrote my proposal to wiki to address this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33219) Job.updateNextBuildNumber can cause deadlock
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33219 Job.updateNextBuildNumber can cause deadlock Change By: Jesse Glick Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [packaging] (JENKINS-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Title: Message Title
Sam Van Oort commented on JENKINS-23273
Re: RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Volker I like the approach of adding a marker file here, but have an even better idea: by default we chown -R (maintaining old behavior), but only if the top-level directory is not owned by the Jenkins user. This way, we only chown where needed (improving performance tremendously), and if the JENKINS_INSTALL_SKIP_CHOWN option is set, we never chown.
If a chown is performed, a marker file is created indicating the original user/group listing.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [git-plugin] (JENKINS-33202) Enhance Git Plugin LocalBranch to better support Maven release builds
Title: Message Title Mark Waite commented on JENKINS-33202 Re: Enhance Git Plugin LocalBranch to better support Maven release builds Merged to the master branch 17 Mar 2016, will be included in the git plugin 2.4.3 and later releases. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-33658) Add ability to launch a pipeline script from a generic job
Title: Message Title Andrea Baccega created an issue Jenkins / JENKINS-33658 Add ability to launch a pipeline script from a generic job Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Mar/18 4:00 PM Priority: Minor Reporter: Andrea Baccega It would super nice to be able to use workflow plugin code within a generic job creator. This would ease the integration of workflow plugin with others which are not compatible with it right now. Add Comment
[JIRA] [core] (JENKINS-33395) Jenkins should install a default UncaughtExceptionHander
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-33395 Jenkins should install a default UncaughtExceptionHander Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-plugin] (JENKINS-24474) gitlab-plugin
Title: Message Title owenmehegan closed an issue as Fixed This may be due to an old version of GitLab. Please test with at least GitLab 7.14.x and the latest version of the plugin. Reopen if the issue remains. Jenkins / JENKINS-24474 gitlab-plugin Change By: owenmehegan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [scripted-cloud-plugin] (JENKINS-33654) Cannot specify number of executors for Scripted Cloud nodes
Title: Message Title Giuseppe Landolfi created an issue Jenkins / JENKINS-33654 Cannot specify number of executors for Scripted Cloud nodes Issue Type: Bug Assignee: Unassigned Components: scripted-cloud-plugin Created: 2016/Mar/18 3:21 PM Priority: Major Reporter: Giuseppe Landolfi Number of executors for Scripted Cloud nodes is set to 1 and cannot be changed. Workaround: change manually the value in $JENKINS_HOME/nodes//config.xml file and restart Jenkins. Add Comment
[JIRA] [antisamy-markup-formatter-plugin] (JENKINS-27948) Script timeout during start of configure a jenkins job
Title: Message Title Chris Cralle updated an issue Jenkins / JENKINS-27948 Script timeout during start of configure a jenkins job Change By: Chris Cralle Labels: codemirror configuration jenkins performance Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33296) Initial plugin setup needs to consider implied dependencies
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33296 Re: Initial plugin setup needs to consider implied dependencies Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/ClassicPluginStrategy.java core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/model/UpdateSite.java core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/_entryForm.jelly war/src/main/js/api/plugins.js war/src/main/js/pluginSetupWizardGui.js http://jenkins-ci.org/commit/jenkins/449719ca8aaad1a177f81dbb6a35df76ca82d012 Log: Merge pull request #2122 from kzantow/2.0 JENKINS-33296 - plugin dependency issues during install Compare: https://github.com/jenkinsci/jenkins/compare/f4817411c403...449719ca8aaa Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [antisamy-markup-formatter-plugin] (JENKINS-27948) Script timeout during start of configure a jenkins job
Title: Message Title Chris Cralle commented on JENKINS-27948 Re: Script timeout during start of configure a jenkins job There is a problem with CodeMirror and textarea windows. I just upgraded to LTS 1.642.3 this weekend and getting a little rubbing from my comrades about how long the configure load times are. I have one 2x4 Matrix multi-step job with conditionals that have shell, python, and windows batch executes. The configure page for this job generates 8-10 timeouts in codemirror.js and takes minutes to load. Common timeouts are on lines 1247, 1207, 853 These deal with the gutter and scrollbar as far as I can tell. I've spent Saturday trying everything I can to somehow just DISABLE codemirror. But since it's core, not a plugin, and there's no exposed configuration for it, I'm pretty much stuck with it's behavior. Is it possible to turn it off? The setting in security for syntax highlighting is not related, the number of builds or history is not related. This is purely codemirror barfing on complex jobs with recursive textareas. I'm surprised codemirror is not a tag/label on this ticket. I am creating a sanitized config.xml which I hope to upload to this ticket in the hope that it helps with a resolution. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33296) Initial plugin setup needs to consider implied dependencies
Title: Message Title Daniel Beck resolved as Fixed Jenkins / JENKINS-33296 Initial plugin setup needs to consider implied dependencies Change By: Daniel Beck Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [test-results-analyzer-plugin] (JENKINS-33397) Test results analyzer plugin
Title: Message Title Varun Menon commented on JENKINS-33397 Re: Test results analyzer plugin I had verified the plugin in 1.609 and 1.648 version of jenkins and I am able to use the plugin properly without any issues. Can you check if jenkins was restarted after installation of the plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jira-issue-updater-plugin] (JENKINS-31755) Jenkins "Jira Issue Updater Plugin" pasrsing error when "Affects Version/s" is not empty
Title: Message Title Ian Sparkes commented on JENKINS-31755 Re: Jenkins "Jira Issue Updater Plugin" pasrsing error when "Affects Version/s" is not empty Probably you can get the update on build success out of the box by simply putting the Jenkins JIRA Issue updater at the right point in the configuration. I generally include Jenkins Jira Issue Updater at least twice in each build: once as a "Build Post Step" to say that I'm going to try to test it, and once as a "Post-build Action" to say that it was built and tested correctly (we use FitNesse for this). You might also want to use the "Flexible Publish" plug in if you need finer control of what and when to update. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-33629) `checkout scm` surprisingly fails when multibranch plugin is not installed
Title: Message Title
c089 updated an issue
Jenkins / JENKINS-33629
`checkout scm` surprisingly fails when multibranch plugin is not installed
Change By:
c089
Since JENKINS-31386 we can use `checkout scm` to get SCM sources using the values configured for the "Pipeline script from SCM" job. However, this only works if the multibranch plugin is installed, otherwise it fails (see stack trace below). I only realised that after finding the mentioned issue and looking at the diff of the commit.{ { code} groovy.lang.MissingPropertyException: No such property: scm for class: groovy.lang.Bindingat groovy.lang.Binding.getVariable(Binding.java:62)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:185)at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241)at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238)at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:221)at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:221)at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:23)at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17)at WorkflowScript.run(WorkflowScript:16)at ___cps.transform___(Native Method)at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:62)at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:54)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:497)at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)at com.cloudbees.groovy.cps.Next.step(Next.java:58)at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19)at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33)at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:106)at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30)at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:277)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:77)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:186)at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:184)at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47)at java.util.concurrent.FutureTask.r
[JIRA] [emailext-template-plugin] (JENKINS-33612) Provision error (Tried proxying due circular dependency) reported at startup
Title: Message Title Alex Earl commented on JENKINS-33612 Re: Provision error (Tried proxying due circular dependency) reported at startup I am unable to reproduce this at all. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33620) Clearing the search box fully hides the configuration page
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-33620 Clearing the search box fully hides the configuration page Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Mar/17 1:29 PM Environment: 2.0-alpha-3 Labels: 2.0 Priority: Minor Reporter: Antonio Muñiz Steps to reproduce it: Create freestyle job In the configuration page, write "SCM" in the search box (top left) Then click on the little X in the search field
[JIRA] [prioritysorter-plugin] (JENKINS-33588) Branches and Repositories prioritization
Title: Message Title Alexander Vorobiev created an issue Jenkins / JENKINS-33588 Branches and Repositories prioritization Issue Type: Improvement Assignee: Magnus Sandberg Components: prioritysorter-plugin, workflow-plugin Created: 16/Mar/16 12:53 PM Environment: Jenkins 2.0, organization folders Labels: workflow github Priority: Major Reporter: Alexander Vorobiev As a development team with github organization account and with limited CI servers bandwidth we would like to have commits on production branches to be built before the intermediate commits to personal development branches. In addition some repositories are more critical then the others, so builds for that repositories need to be prioritized. In Jenkins 1.x I could manage this with Priority Sorter Plugin in combination with Views and Jobs properties. I could not find a way to do it for the organization folder with pipeline as code. For example for Git Flow I need branches that match 'hotfix/.' have more priori
[JIRA] [clover-plugin] (JENKINS-33610) IOException with Clover 4.6 plugin
Title: Message Title
Trevor Baker updated an issue
Jenkins / JENKINS-33610
IOException with Clover 4.6 plugin
Change By:
Trevor Baker
I am seeing a new IOException since upgrading to v4.60 of the clover plugin in a job running on a linux ec2 slave{ { quote} Archiving artifactsPublishing Clover coverage report...Publishing Clover HTML report...Publishing Clover XML report...IOException when checking workspace path:remote file operation failed: /home/ec2-user/jenkins/workspace/the-job at hudson.remoting.Channel@69b58179:: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@4836f4e9Publishing Clover coverage results... {quote } }
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [dashboard-view-plugin] (JENKINS-20796) Deletion of project from frontpage (All view) via dropdown pop-up fails with 403
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-20796 Deletion of project from frontpage (All view) via dropdown pop-up fails with 403 Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cli] (JENKINS-31847) Extract clear-queue CLI command from Core to CLI
Title: Message Title Oliver Gondža resolved as Fixed Jenkins / JENKINS-31847 Extract clear-queue CLI command from Core to CLI Change By: Oliver Gondža Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-32525) Error 500 using Build other Projects in Promotion process of a template
Title: Message Title Jesse Glick stopped work on JENKINS-32525 Change By: Jesse Glick Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ssh-plugin] (JENKINS-12191) Support build variables (substitution variables) during command execution
Title: Message Title
Nikita Danilov edited a comment on JENKINS-12191
Re: Support build variables (substitution variables) during command execution
Hello,We have the same issue with SSH plugin versions 2.3-2.4.We see that plugin translates script like this to the server:{code}export MY_VAR="asd"echo $MY_VAR{code}Variable value sent via export command. But unfortunately our server cannot to process complex scripts . He , he is awaiting just 1 predefined command with 1 parameter.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [pipeline-stage-view-plugin] (JENKINS-33625) Enhanced APIs for pipeline stage view, to return specifically needed UI data WITH PAGING
Title: Message Title Antonio Muñiz assigned an issue to Unassigned Jenkins / JENKINS-33625 Enhanced APIs for pipeline stage view, to return specifically needed UI data WITH PAGING Change By: Antonio Muñiz Assignee: Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cloudbees-folder-plugin] (JENKINS-33006) "Periodically if not otherwise run" interval value acts erratically
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-33006 "Periodically if not otherwise run" interval value acts erratically Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [multi-branch-project-plugin] (JENKINS-33582) empty parser listbox in multi-branch project
Title: Message Title Benedikt Spranger closed an issue as Cannot Reproduce Close this issue, since it is obvious buried in my configuration/installation. Thx for your help. Jenkins / JENKINS-33582 empty parser listbox in multi-branch project Change By: Benedikt Spranger Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitbucket-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Kevin Phillips commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json I see a pull request was made for this months ago, and the changes appear to have been integrated back in January, but from what I can tell there has been no release of this plugin since the fix was integrated. Given the fact it has been nearly 2 months since the fix has been made, shouldn't there be a new version of the plugin by now? Unless there is some reason not to, I'd appreciate it if someone could push a new version to the Jenkins plugin server sooner rather than later. Without this fix the plugin simply does not work with any recent version of Bitbucket, making it effectively useless. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [packaging] (JENKINS-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Title: Message Title
Sam Van Oort assigned an issue to Sam Van Oort
Jenkins / JENKINS-23273
RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Change By:
Sam Van Oort
Assignee:
Daniel Beck Sam Van Oort
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [build-user-vars-plugin] (JENKINS-33618) Not possible to enable for BuildFlow job type
Title: Message Title Fredrik Andersson created an issue Jenkins / JENKINS-33618 Not possible to enable for BuildFlow job type Issue Type: Improvement Assignee: Unassigned Components: build-user-vars-plugin Created: 2016/Mar/17 12:35 PM Environment: Jenkins ver. 1.642.2 CloudBees Build Flow plugin 0.18 user build vars plugin 1.5 Priority: Minor Reporter: Fredrik Andersson The option to enable build user variables is not showing in the GUI for BuildFlow job types. I also tried adding the buildWrapper config manually in the config.xml but this did not work either. Add Comment
[JIRA] [build-pipeline-plugin] (JENKINS-16098) Nested View Plugin shows FAIL build staus whenever Build Pipeline Plugin is used as a Nested View
Title: Message Title Michael Andrews edited a comment on JENKINS-16098 Re: Nested View Plugin shows FAIL build staus whenever Build Pipeline Plugin is used as a Nested View To reproduce - create two pipelines (each with different jobs). Create two Build Pipeline views. Add the "Status" Ball to the each view. Break a job in one view, and both views are red. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [testlink-plugin] (JENKINS-33642) Error communicating with testlink
Title: Message Title Ed Sherwin Nonog updated an issue Jenkins / JENKINS-33642 Error communicating with testlink Change By: Ed Sherwin Nonog Summary: Testlink integration Error communicating with jenkins testlink Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cloudbees-folder-plugin] (JENKINS-33006) "Periodically if not otherwise run" interval value acts erratically
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33006 "Periodically if not otherwise run" interval value acts erratically Change By: Jesse Glick Component/s: cloudbees-folder-plugin Component/s: branch-api-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [copyartifact-plugin] (JENKINS-33577) "Unable to find a build" when using DownstreamBuildSelector with Jenkins Pipelines
Title: Message Title Jesse Glick commented on JENKINS-33577 Re: "Unable to find a build" when using DownstreamBuildSelector with Jenkins Pipelines Andy Pemberton from the perspective of the downstream build there is indeed an UpstreamCause. But the upstream/downstream relationships are specific to AbstractProject. UpstreamCause is only considered by TriggeredBuildSelector, which is in the wrong direction for this use case. Anyway as the PR demonstrates, SpecificBuildSelector is all you need, and is much more straightforward and reliable than trying to make Jenkins infer the right build number: you have it right in front of you. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [image-gallery-plugin] (JENKINS-31364) Image width is set to "0" in previous builds
Title: Message Title Christopher Orr commented on JENKINS-31364 Re: Image width is set to "0" in previous builds Nope, the width doesn't remain stable — I checked a build this morning, and it looked fine. Now that a couple of other builds have been made, all of the builds now have image width = 0. The job config is still correct and hasn't changed, but all image galleries have HTML like this now: "stylesheet" type="text/css" href="" class="code-quote" style="color: #009100">"/adjuncts/36717366/org/jenkinsci/plugins/imagegallery/stapler/colorbox/css/colorbox.css"> Screenshot from linux-slave-1"screenshot.png" class="gallery" href="" class="code-quote" style="color: #009100">"artifact/screenshot.png">"Image 0" width="0" src="" class="code-quote" style="color: #009100">"artifact/screenshot.png"> Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33534) Missing content when executing the plugin installs
Title: Message Title Daniel Beck commented on JENKINS-33534 Re: Missing content when executing the plugin installs FWIW I was just able to reproduce it once on my regular machine. Could it be related to hiding the browser window/switching to a different tab? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-12462) Jenkins configuration page could be improved
Title: Message Title twolfart commented on JENKINS-12462 Re: Jenkins configuration page could be improved Another pain point are plugins that add lists of configurations. E.g. the "Publish over SSH"-Plugin adds lots of SSH Servers. 3 Servers (without "Advanced") fit on my screen, currently I have about 50 (numbers growing) - and this is only the list of one plugin. It would be a great improvement, if lists initially were not fully expanded with opened form items, but shown in a more compact variant where individual entries can be edited. Example: The plugin listing can fit 20 on a screen. A more sophisticated UX could enable sorting of the list entries depending on column, re-ordering, deleting from the list view, etc. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [radiatorview-plugin] (JENKINS-33645) Multibranch Pipelines do not show up in Radiator Views
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-33645 Multibranch Pipelines do not show up in Radiator Views Issue Type: Bug Assignee: Baptiste Mathus Components: radiatorview-plugin Created: 2016/Mar/18 9:57 AM Priority: Major Reporter: Baptiste Mathus Basically, multibranch pipelines should show in the RadiatorView if some branch is failing. To be defined: either show the whole project, or possibly show the precision of the failing branch. Not sure, but would be better to try and not have to go into the Multibranch Pipeline Job's structure to not have to create a hard dependency on it. Add Comment
[JIRA] [cppcheck-plugin] (JENKINS-29741) Add Job DSL support for CppCheck
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-29741 Add Job DSL support for CppCheck Change By: Daniel Spilker Summary: Support Add Job DSL support for CppCheck Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pipeline-stage-view-plugin] (JENKINS-33656) Can't expand logs in Stage Log Popover
Title: Message Title Antonio Muñiz closed an issue as Duplicate Jenkins / JENKINS-33656 Can't expand logs in Stage Log Popover Change By: Antonio Muñiz Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jobconfighistory-plugin] (JENKINS-33289) nullpointerexception when clicking on 'show diffs' on a job config history page (since 1.651 update)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33289 Re: nullpointerexception when clicking on 'show diffs' on a job config history page (since 1.651 update) Code changed in jenkins User: Stefan Brausch Path: pom.xml src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryBaseAction.java src/main/resources/hudson/plugins/jobConfigHistory/ComputerConfigHistoryAction/index.jelly src/main/resources/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectAction/index.jelly src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectActionTest.java http://jenkins-ci.org/commit/jobConfigHistory-plugin/4b36915239849db047c503337638d6450dc32f5b Log: [FIXED JENKINS-33289] Test fixed, Typo in jelly Compare: https://github.com/jenkinsci/jobConfigHistory-plugin/compare/009f555d2249...4b3691523984 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33652) Job Name and Cancel button gets displayed outside of the Build Queue Pane
Title: Message Title Peter Willekens created an issue Jenkins / JENKINS-33652 Job Name and Cancel button gets displayed outside of the Build Queue Pane Issue Type: Bug Assignee: Unassigned Attachments: Jenkins_Build_Pane_Chrome.PNG, Jenkins_Build_Pane_IE.PNG Components: core Created: 2016/Mar/18 2:58 PM Priority: Minor Reporter: Peter Willekens Jenkins 1.642.2 IE 11 When job names are longer then the width of the build queue pane, part of the name + the cancel button gets displayed outside of the pane (as you can see in Jenkins_Build_Pane_IE.PNG). Wrapping the job name works fine tho when using Chrome (shown in Jenkins_Build_Pane_Chrome.PNG). Same thing seems to happen in the Build Executor Status Pane.
[JIRA] [gitlab-plugin] (JENKINS-25844) Can't fetch branch from remote builds
Title: Message Title owenmehegan closed an issue as Fixed Jenkins / JENKINS-25844 Can't fetch branch from remote builds Change By: owenmehegan Status: Open Closed Assignee: owenmehegan Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-18032) "Delete Project" link fails with 403 Exception: No valid crumb was included in the request
Title: Message Title SCM/JIRA link daemon commented on JENKINS-18032 Re: "Delete Project" link fails with 403 Exception: No valid crumb was included in the request Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/lib/layout/breadcrumbs.js http://jenkins-ci.org/commit/jenkins/37111bf12e5038fcd240bbefb3aa9474e45585c2 Log: Merge pull request #2131 from jglick/requiresConfirmation-post-context-menu- JENKINS-18032 JENKINS-18032 Fix Delete Project from context menu when using CSRF defense Compare: https://github.com/jenkinsci/jenkins/compare/35ec989afffc...37111bf12e50 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33557) Setup wizard shows blank page when Jenkins is behind proxy
Title: Message Title R. Tyler Croy commented on JENKINS-33557 Re: Setup wizard shows blank page when Jenkins is behind proxy Daniel Beck I think we can still improve the user experience here and show some form of an error instead of simply a white screen that doesn't help the user diagnose the issue at all. Even just a link at the bottom of the page with something like "(Browser Support)" to the wiki page you linked would be better IMHO Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [image-gallery-plugin] (JENKINS-32447) BUILD_NUMBER in include pattern
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32447 BUILD_NUMBER in include pattern Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pipeline-stage-view-plugin] (JENKINS-33430) Stage view UI loses history when stages are changed
Title: Message Title Sam Van Oort commented on JENKINS-33430 Re: Stage view UI loses history when stages are changed Marco Lijoi I'm not sure what you mean - are you saying that only the current run is displaying when the number of stages changes? I've seen that happen intermittently, mostly with very large stages. Usually refreshing the page fixes the issue, though. I suspect it has to do with the way the JS code renders cached builds, possibly some sort of ordering bug. Worth looking into. Do you have a case that consistently replicates the issue? (I haven't been able to get it to do this consistently.) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [scm-sync-configuration-plugin] (JENKINS-33302) Deleting a user on jenkins is not syncing up
Title: Message Title Edgar Madrigal updated an issue Jenkins / JENKINS-33302 Deleting a user on jenkins is not syncing up Change By: Edgar Madrigal Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-33409) GitSCM.guessBrowser does not work if there are multiple refspecs
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-33409 GitSCM.guessBrowser does not work if there are multiple refspecs Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-branch-source-plugin] (JENKINS-31552) GitHub Multibranch Workflow: anonymous checkout credentials should be renamed
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31552 GitHub Multibranch Workflow: anonymous checkout credentials should be renamed Change By: Jesse Glick Labels: 2.0 2.0 -planned UX Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33534) Missing content when executing the plugin installs
Title: Message Title Alex Earl commented on JENKINS-33534 Re: Missing content when executing the plugin installs Keith Zantow Looks much better with that war Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33223) Can't view/delete a job
Title: Message Title Daniel Beck resolved as Won't Do Oops. We had an epidemic of identical issue reports and this looked similar. Install and/or enable the Matrix Authorization Plugin. It's a dependency of the Multibranch Plugin. Jenkins / JENKINS-33223 Can't view/delete a job Change By: Daniel Beck Status: Reopened Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [template-project-plugin] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title Jason Azze commented on JENKINS-31712 Re: Use SCM from another project is removed after upgrading to 1.5.1 See also JENKINS-30243 Specifically https://issues.jenkins-ci.org/browse/JENKINS-30243?focusedCommentId=238643&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-238643 To work around this problem I had to install the Multiple SCMs plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33534) Missing content when executing the plugin installs
Title: Message Title Keith Zantow edited a comment on JENKINS-33534 Re: Missing content when executing the plugin installs [~slide_o_mix] is it consistent for you? I'm investigating the code that populates the plugin status indicators in the empty section, but again, it seems to be fairly consistently working across browsers in my testing. My leading hypothesis is that it's a timing issue. Anyway, it would be helpful if you could test the build from the PR I created: https:// github jenkins . ci.cloudbees. com/ jenkinsci job / core/job/ jenkins -core / pull 4365 / 2135 artifact/war/target/jenkins.war Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33619) Script definition area rendered over header section
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-33619 Script definition area rendered over header section Issue Type: Bug Assignee: Jesse Glick Components: core, workflow-plugin Created: 2016/Mar/17 1:11 PM Labels: 2.0 Priority: Minor Reporter: Antonio Muñiz The script definition area is rendered over the head section of the configuration page. See attached screenshot. Filing this in both core and workflow-plugin because I'm not sure where the bug is. I think it's core. Add Comment
[JIRA] [core] (JENKINS-4819) Enable/disable build step by one click
Title: Message Title Daniel Beck commented on JENKINS-4819 Re: Enable/disable build step by one click Sam Darwin Nobody disputes that. It's just a matter of priorities and finding the time to do this. As usual, contributions welcome FWIW I had a prototype of this in https://github.com/daniel-beck/jenkins/commit/18d434fa6bf8b3efc8b0b39cb9cc064368dc4bec but it was shot down by Jesse Glick, complete with explanation how to do it right. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jobconfighistory-plugin] (JENKINS-33289) nullpointerexception when clicking on 'show diffs' on a job config history page (since 1.651 update)
Title: Message Title Stefan Brausch commented on JENKINS-33289 Re: nullpointerexception when clicking on 'show diffs' on a job config history page (since 1.651 update) Fix is released and should be available in update center soon. Sorry for the delay, but I saw the issue this morning the first time Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [_unsorted] (JENKINS-31550) Configure System Page shows Oops page (/configure)
Title: Message Title owenmehegan closed an issue as Fixed Fixed in latest version of the plugin. Jenkins / JENKINS-31550 Configure System Page shows Oops page (/configure) Change By: owenmehegan Status: Open Closed Assignee: owenmehegan Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [fstrigger-plugin] (JENKINS-33598) Directory blob expansion fails
Title: Message Title luke shaughnessy updated an issue Jenkins / JENKINS-33598 Directory blob expansion fails Change By: luke shaughnessy Under Trigger Monitor Files In File Path Field enter: /tmp/temp/tmp/*Result in Trigger Log:Polling on master.Checking one file: '/tmp/temp/tmp/testfile'.Polling complete. Took 0 ms.This is the expected behavior.In File Path Field enter: "/tmp/* \ */tmp/*"Error in Trigger Log: Polling on master.The folder path '/tmp/**/tmp' doesn't exist.The computed file doesn't exist.Expected behavior:the glob for the directory at ** (temp) should have been expanded. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-reviewbot] (JENKINS-29742) Add Job DSL support for Reviewbot
Title: Message Title Daniel Spilker assigned an issue to Unassigned Jenkins / JENKINS-29742 Add Job DSL support for Reviewbot Change By: Daniel Spilker Assignee: Daniel Spilker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-33474) Pipeline job hanging
Title: Message Title Luis Echegaray edited a comment on JENKINS-33474 Re: Pipeline job hanging Same issue, could not kill the threads at all. Had to eventually stop the Jenkins process and delete the job folders. Jenkins ver. 1653 Pipeline ver 1.14 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-29209) Exception when trying to use notifyCommit
Title: Message Title
Zalan Meggyesi commented on JENKINS-29209
Re: Exception when trying to use notifyCommit
This seems to have re-surfaced as of git 2.4.2 and git-client 1.19.6, under Jenkins 1.653. I get the following stacktrace when trying to run a build from hook:
{{javax.servlet.ServletException: java.lang.NoClassDefFoundError: jenkins/scm/api/SCMSourceOwners at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) 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:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:134) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:125) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle
[JIRA] [bitbucket-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Kevin Phillips commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json I am running 1.596.3 of Jenkins core and have confirmed I have v1.1.5 of this plugin and this problem is still reproducible. I took another look at the pull request, and I think my earlier assessment may have been incorrect. The last comment on this issue was left on January 31st which lead me to believe the fix hadn't been integrated until that date, which was after v1.1.5 had been released - but that isn't the case. I will have to take a closer look at my local configuration, but it would appear the fix for this issue is not working as intended. In my case I'm using the latest version of Bitbucket Server (v4.4.1) in case that makes any difference. Perhaps I'm hitting a different problem, however the error message I am current seeing exactly matches the one included in the description above (ie: JSONObject["user"] not found) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-27039) Option for input or stage step to cancel older executions
Title: Message Title James Nord commented on JENKINS-27039 Re: Option for input or stage step to cancel older executions .bq as a collateral benefit we have a fix for this issue, as it is granted that only the latest build will be waiting for input when using milestone concurrency: 1, so there will be no need to cancel any old build manually. That is very dangerous.. if you cancel currently running thing in the miletestone then you may never deploy anything to production as you are constantly killing the build under test in Jesse's "testing" example above (if that had concurrency 1 due to the fact you hare hardware limited). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-18032) "Delete Project" link fails with 403 Exception: No valid crumb was included in the request
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-18032 "Delete Project" link fails with 403 Exception: No valid crumb was included in the request Change By: Jesse Glick Labels: 1.509.3-fixed crumb Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-plugin] (JENKINS-33613) Null value not allowed as an environment variable gitlabUserEmail
Title: Message Title Max Trunov created an issue Jenkins / JENKINS-33613 Null value not allowed as an environment variable gitlabUserEmail Issue Type: Bug Assignee: owenmehegan Attachments: selected.png Components: gitlab-plugin Created: 2016/Mar/17 9:45 AM Environment: gitlab-plugin v1.1.31 jenkins 1.642.2 LTS Priority: Minor Reporter: Max Trunov After update this plugin some jobs was failed with this error FATAL: Null value not allowed as an environment variable: gitlabUserEmail java.lang.IllegalArgumentException: Null value not allowed as an environment variable: gitlabUserEmail at hudson.EnvVars.put(EnvVars.java:356) at hudson.model.StringParameterValue.buildEnvironment(StringParameterValue.java:56) at hudson.model.ParametersAction.buildEnvVars(ParametersAction.java:89) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:950) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1046) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.d
[JIRA] [github-oauth-plugin] (JENKINS-33661) Plugin permissions not supported
Title: Message Title Sam Gleske commented on JENKINS-33661 Re: Plugin permissions not supported If you make use of another authorization strategy (such as a matrix-based authorization strategy) then you can support it. GitHub organizations and teams are surfaced as groups in Jenkins. https://wiki.jenkins-ci.org/display/JENKINS/Github+OAuth+Plugin#GithubOAuthPlugin-MatrixbasedAuthorizationstrategy Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-token-root-plugin] (JENKINS-33664) GET requests cause a build to be scheduled
Title: Message Title Kai Groner created an issue Jenkins / JENKINS-33664 GET requests cause a build to be scheduled Issue Type: Bug Assignee: Jesse Glick Components: build-token-root-plugin Created: 2016/Mar/18 7:51 PM Priority: Minor Reporter: Kai Groner I shared a curl command to trigger a build via a slack channel. When slack tried to preview the url, it kicked off a build. I don't think GET requests should be triggering builds. Add Comment T
[JIRA] [core] (JENKINS-32831) "None of the Update Sites passed the signature check" w/ Jenkins v1.647
Title: Message Title dogfood commented on JENKINS-32831 Re: "None of the Update Sites passed the signature check" w/ Jenkins v1.647 Integrated in jenkins_main_trunk #4512 JENKINS-32831 if metadata for tool installer does not exist should not (Revision d2b1f15fc56f382f1d578c9317fca917ddabac92) Result = UNSTABLE valentina.armenise : d2b1f15fc56f382f1d578c9317fca917ddabac92 Files : core/src/main/java/hudson/model/DownloadService.java Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33496) Add tests for scrollspy widget
Title: Message Title Tom FENNELLY started work on JENKINS-33496 Change By: Tom FENNELLY Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33647) Old Build are deleted from Disk when I upgraded Jenkins on Windows Server
Title: Message Title pras sawant updated an issue Jenkins / JENKINS-33647 Old Build are deleted from Disk when I upgraded Jenkins on Windows Server Change By: pras sawant HiI have upgraded jenkins from 1/624 to 1.652 , surprisingly I have lost some old bulls from some jobs and complete jobs got deleted from disk , is it possible? it's worried the entire team Could you please help on priority , Thanks & RegardsPrashant Sawantprashant.saw...@mastek.com Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33037) hudson.model.Fingerprint.RangeSet.fromString(...) accepts malformed ranges
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33037 Re: hudson.model.Fingerprint.RangeSet.fromString(...) accepts malformed ranges Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/model/Fingerprint.java core/src/test/java/hudson/model/FingerprintTest.java http://jenkins-ci.org/commit/jenkins/8ba59197e4d4631c9cf2570749d49f25a724 Log: Merge pull request #2049 from pjanouse/ JENKINS-33037 [FIXED JENKINS-33037] Fixed malformed ranges in RangeSet.fromString() Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitbucket-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title
Kevin Phillips commented on JENKINS-28877
Re: Bitbucket Plugin unable to parse Bitbucket webhook response json
Correct. However I believe they use the same application code for the cloud service that they provide for the on-premises version. Even if that is not the case you can actually download a free copy of the on-premises version from Atlassian's website for testing if necessary. It requires a free activation of course, but that's easy enough to get.
I have also confirmed that this is not a configuration problem on my end. I do have the latest version of the plugin. I restarted our Jenkins server just to be sure all of the components and plugins were up to date and installed correctly, and I am still getting this problem. Here is a more complete snippet from my Jenkins logs in case it helps (it looks like it has at least some of the package contents right there in the log):
Mar 18, 2016 1:14:48 PM com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor processPostServicePayload
INFO: Received commit hook notification for {"slug":"pytools","id":2,"name":"pytools","scmId":"git","state":"AVAILABLE","statusMessage":"Available","forkable":true,"project":{"key":"DOT","id":4,"name":"DevOps Tools","description":"Projects related to DevOps team","public":true,"type":"NORMAL"},"public":true}
Mar 18, 2016 1:14:48 PM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Error while serving http://builds.caris.priv/bitbucket-hook/
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$2.dispatch(MetaClass.java:165)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
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:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176)
at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85)
at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.Cr
[JIRA] [kubernetes-plugin] (JENKINS-33649) ArrayIndexOutOfBoundsException building node selector map when field is empty on the configuration
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-33649 ArrayIndexOutOfBoundsException building node selector map when field is empty on the configuration Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Mar/18 11:16 AM Priority: Major Reporter: Alvaro Lobato ArrayIndexOutOfBoundsException is thrown building node selector map when the node selector field is empty on the advanced configuration configuration: Mar 18, 2016 10:54:48 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback call SEVERE: Error in provisioning; slave=KubernetesSlave name: , template=org.csanchez.jenkins.plugins.kubernetes.PodTemplate@7fe4ab15 java.lang.ArrayIndexOutOfBoundsException: 1 at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.getNodeSelectorMap(KubernetesCloud.java:284) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.getPodTemplate(KubernetesCloud.java:266) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.access$100(KubernetesCloud.java:60) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback.call(KubernetesCloud.java:352) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback.call(KubernetesCloud.java:334) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecut
[JIRA] [core] (JENKINS-33330) Cron hashing syntax is ignored in Poll SCM
Title: Message Title Christopher Orr commented on JENKINS-0 Re: Cron hashing syntax is ignored in Poll SCM Daniel Beck: It would be weird if this had never worked correctly, but I don't know whether this is a regression or not, sorry. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [coverity-plugin] (JENKINS-33640) The coverity plug-in should be able to run for specific build steps only.
Title: Message Title Michael Genau created an issue Jenkins / JENKINS-33640 The coverity plug-in should be able to run for specific build steps only. Issue Type: New Feature Assignee: Ken Dang Components: coverity-plugin Created: 2016/Mar/18 8:14 AM Environment: Coverity plugin 1.7.1 Labels: coverity Priority: Major Reporter: Michael Genau At the moment coverity will analyze the whole build process which is configured for a jenkins job. It would be much better to configure coverity for specific build steps. Furthermore, it would be nice to allow different configurations for different build steps. At the moment I have to configure a lot of jenkins jobs, because the plugin creates batch files which wrap the whohle build process.
[JIRA] [core] (JENKINS-32831) "None of the Update Sites passed the signature check" w/ Jenkins v1.647
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32831 Re: "None of the Update Sites passed the signature check" w/ Jenkins v1.647 Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/DownloadService.java core/src/main/java/hudson/tools/DownloadFromUrlInstaller.java http://jenkins-ci.org/commit/jenkins/d8241ff7803ca134fa39fb88bb990fc6a0abef93 Log: Merge pull request #2050 from varmenise/ JENKINS-32831 [FIXED JENKINS-32831] do not fail if there are no metadata for tool installers Compare: https://github.com/jenkinsci/jenkins/compare/37111bf12e50...d8241ff7803c Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pipeline-stage-view-plugin] (JENKINS-33624) Improve performance of Pipeline Stage View even with very long FlowGraphs
Title: Message Title
Sam Van Oort created an issue
Jenkins / JENKINS-33624
Improve performance of Pipeline Stage View even with very long FlowGraphs
Issue Type:
Improvement
Assignee:
Sam Van Oort
Components:
pipeline-stage-view-plugin
Created:
2016/Mar/17 3:08 PM
Priority:
Major
Reporter:
Sam Van Oort
The algorithms in pipeline stage view cover the normal use case well, but have issues with excessively large FlowGraphs. This is most commonly caused when someone runs a loop (with steps and/or blocks embedded in it) that executes many times.
To reproduce, create and run a build with the following pipeline code and then view in stageview: for(int i=0; i<; i++) { echo "Cycle $ {i}
" }
The result is combination of high master CPU load, very long or incomplete UI requests, very large response datasets (MB), and/or high memory use.
Add Comment
[JIRA] [core] (JENKINS-33557) Setup wizard shows blank page when Jenkins is behind proxy
Title: Message Title Sven Schultschik commented on JENKINS-33557 Re: Setup wizard shows blank page when Jenkins is behind proxy IE 8 you get just a white page (yeah its old, but it's a standard win7 VM for testing ...) Without any pop-up, so you can't do anything. When I skipped as written above the pop-up from another PC the IE works fine. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33296) Initial plugin setup needs to consider implied dependencies
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33296 Re: Initial plugin setup needs to consider implied dependencies Code changed in jenkins User: kzantow Path: core/src/main/java/hudson/model/UpdateSite.java core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/_entryForm.jelly war/src/main/js/api/plugins.js war/src/main/js/pluginSetupWizardGui.js http://jenkins-ci.org/commit/jenkins/3edb9fdcecedb4514e4b0396306cb0f115a0b321 Log: JENKINS-33296 - plugin dependency issues during install Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-33439) Support CloudBees Docker Build and Publish plugin 1.2
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-33439 Support CloudBees Docker Build and Publish plugin 1.2 Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-33617) Can't see SVN_URL and SVN_REVISION in environment variable
Title: Message Title pras sawant updated an issue Jenkins / JENKINS-33617 Can't see SVN_URL and SVN_REVISION in environment variable Change By: pras sawant Hi I can't see SVN_URL and SVN_REVISION in environment variable I am using Jenkins 1.652 on windows server with Subversion Plugin 2.5.7 and Subversion Tag Plugin 1.18Attached screen shot , it's holding me from creating build tags in SVN Thanks & RegardsPrashant Sawantprashant.saw...@mastek.com Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-30896) Unoptimized node & log storage
Title: Message Title Sam Van Oort edited a comment on JENKINS-30896 Re: Unoptimized node & log storage A couple thoughts after spending time in the innards of this structure for pipeline stage view work (the easier ones are things that multiple people could hack away on):*Indexing:*Some operations on a FlowGraph require linear iteration over all nodes to generate summary statistics, for example to generate data for visualization or UI. Where the complete FlowNode set isn't needed, a FlowGraphIndex Action could be created that collects summary information about meaningful branches/milestones (parallel steps, stages, etc). Things that would be useful to know: pause/run duration, final status of steps within that milestone, if any of those steps include NotExecutedNodeActions (or similar), etc. It would also be helpful to know the node ids of steps that mark the start/end of those sections. This could be persisted on the WorkflowRun (since it implements Actionable).*Aggregate storage:*A large amount of information about each persisted flownode is identical. This could potentially be stored in very compact serialization, while allowing the APIs to transparently retrieve this as if it was stored individually with each item. For example, XStream supports storing common actions as attributes on a Node element where a SingleValueConverter can handle them. Aliasing allows for shorter names for classes (ex, common actions such as log encoding). Node trees for non-head nodes might be stored as an XML tree structure (either with the head at the top, or starting from the initial execution). It would make sense to store the current heads in individual files, until the step completes, and pack into the more compact XML objects periodically (to avoid serializing a large object often). Alternately, we append FlowNode data to a run log file as execution occurs, then periodically regenerate the packed file and empty the log.It could be possible to only store unique values for actions, and provide just a mapping table of these actions to FlowNodes. Many actions are used as markers, and nearly all nodes are usually identical (Log encoding, for example). This requires more complexity to handle, however.XStream [reference here|http://x-stream.github.io/alias-tutorial.html] which assists with some of this.For implementation, the FlowActionStorage interface provides storage/retrieval of Actions for each FlowNode, and implementations of this have some freedom with how they do storage/recall. FlowNodeStorage extends this to provide storage/recall for individual nodes. The actions need not read/write to the same files as the node hierarchy, however. SimpleXStreamFlowNodeStorage is the only existing implementation.*Compression:*Due to the duplication mentioned above, FlowGraphs are highly compressible by nature, even moreso than general XML. LZ4/QuickLZ/LZF/Snappy offer compression options that can compress and decompress as a passthrough filter on an InputStream/OutputStream. They compress less than GZIP, but can compress at hundreds of MB/s on modern CPUs, and can be memory-bandwidth bound on decompression (sometimes GB/s). Might be worth considering to reduce disk use by large FlowGraphs in single files. They also can be used for in-memory compression, and might reduce the memory footprint considerably.For Jesse, this may all be trivial and self-evident, but for someone else, it may offer a useful point to contribute on this. Notes on previous optimization:https://github.com/jenkinsci/workflow-plugin/pull/213
