[JIRA] (JENKINS-37034) Deadlock in hudson.model.Executor
Title: Message Title Pavel Janoušek commented on JENKINS-37034 Re: Deadlock in hudson.model.Executor Oleg Nenashev This issue occurred on the Jenkins instance based on 1.609 which we still have been using in the production environment. Fortunately we weren't under the pressure of this issue later, so it seems it isn't a common race-condition. If occurs again, I'll post the full stacktrace here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40759) clarify use of structs-plugin and org.jenkins-ci:symbol-annotation for @Symbol definition
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-40759 clarify use of structs-plugin and org.jenkins-ci:symbol-annotation for @Symbol definition Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: structs-plugin Created: 2017/Jan/03 8:24 AM Priority: Minor Reporter: Dominik Bartholdi (1) describes that one should use the structs-plugin to add @Symbol to an extension point, but at (2) an other approach is described: one should use org.jenkins-ci:symbol-annotation. Which is correct? What are the benefits of one over the other? Why should I use (1) instead of (2)? (1) https://wiki.jenkins-ci.org/display/JENKINS/Structs+plugin (2) https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md#defining-symbols Add Comment
[JIRA] (JENKINS-40759) clarify use of structs-plugin and org.jenkins-ci:symbol-annotation for new @Symbol definition
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-40759 clarify use of structs-plugin and org.jenkins-ci:symbol-annotation for new @Symbol definition Change By: Dominik Bartholdi Summary: clarify use of structs-plugin and org.jenkins-ci:symbol-annotation for new @Symbol definition Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40759) clarify use of structs-plugin and org.jenkins-ci:symbol-annotation for @Symbol definition
Title: Message Title Dominik Bartholdi assigned an issue to Jesse Glick Jenkins / JENKINS-40759 clarify use of structs-plugin and org.jenkins-ci:symbol-annotation for @Symbol definition Change By: Dominik Bartholdi Assignee: Kohsuke Kawaguchi Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27872) Only first QTP test is executed, others are skipped with "QTP is not launched." error
Title: Message Title xiwen zhao commented on JENKINS-27872 Re: Only first QTP test is executed, others are skipped with "QTP is not launched." error cannot reproduce on my machine, QA will test again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27872) Only first QTP test is executed, others are skipped with "QTP is not launched." error
Title: Message Title xiwen zhao edited a comment on JENKINS-27872 Re: Only first QTP test is executed, others are skipped with "QTP is not launched." error cannot reproduce on my machine with UFT 14 build 1708 + Jenkins Plugin 5.0.1-beta-snapshot , by looking at the log i guess after the first run UFT is not closed properly for some reason. QA will test again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27872) Only first QTP test is executed, others are skipped with "QTP is not launched." error
Title: Message Title xiwen zhao resolved as Cannot Reproduce Jenkins / JENKINS-27872 Only first QTP test is executed, others are skipped with "QTP is not launched." error Change By: xiwen zhao Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40760) Use Credentials defined in GitHub plugin
Title: Message Title Asaf M created an issue Jenkins / JENKINS-40760 Use Credentials defined in GitHub plugin Issue Type: New Feature Assignee: Tomas Bjerre Components: violation-comments-to-github-plugin Created: 2017/Jan/03 8:39 AM Priority: Minor Reporter: Asaf M Currently I need to define the Github oauth2 token twice: once in the Github plugin and another time in the job dsl of this plugin. I would like to have this define once in Jenkins. Add Comment This message was sent by Atlassian JIR
[JIRA] (JENKINS-19374) issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the
Title: Message Title xiwen zhao started work on JENKINS-19374 Change By: xiwen zhao Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19374) issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the
Title: Message Title xiwen zhao updated an issue Jenkins / JENKINS-19374 issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://Almserver:Portnumber/qcbin/TDConnectivity_index.html Change By: xiwen zhao Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29957) Could not create scheduler
Title: Message Title xiwen zhao started work on JENKINS-29957 Change By: xiwen zhao Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY commented on JENKINS-39794 Re: API to check that MBP indexing has completed Need to add SSE events for start and stop of indexing An SSE event or a REST API? They seem like 2 different things in how they are described. Maybe the description is just wrong. Also, maybe a bit more detail on the problem that we're trying to solve. AFAIK, MBP indexing results in SSE events when new pipeline jobs are created etc. Is there a bug with that (not created or not consumed), or is something else needed? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29957) Could not create scheduler
Title: Message Title xiwen zhao updated an issue Jenkins / JENKINS-29957 Could not create scheduler Change By: xiwen zhao Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35656) Inconsistent timezone display
Title: Message Title Alexandre Aubert edited a comment on JENKINS-35656 Re: Inconsistent timezone display - It's now ok after upgrading to 1.37. -Time is well displayed at jenkins start but changes suddenly to UTC. It gets back to OK at restart then fails again after some time. I have not identified the exact moment it changes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40761) i18n does not changes language in Blueocean
Title: Message Title Jean-Philippe Briend created an issue Jenkins / JENKINS-40761 i18n does not changes language in Blueocean Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/03 9:02 AM Environment: Jenkins 2.8, Latest version of BlueOcean plugin (running on https://ci.blueocean.io/) Priority: Minor Reporter: Jean-Philippe Briend Reproduce the problem: Install any Locale changer extension for Chrome (or your browser), such as Quick Language Switcher for Chrome Switch to Spanish with the extension Go to https://ci.blueocean.io/ Check that Jenkins is displayed in Spanish. Go to https://ci.blueocean.io/blue/pipelines BlueOcean is displayed in English instead of Spanish Spanish translation is done in BlueOcean, so it should display BlueOcean pages in Spanish.
[JIRA] (JENKINS-40762) Logs can grow without bound when using timestamper plugin
Title: Message Title
Edwin Flores updated an issue
Jenkins / JENKINS-40762
Logs can grow without bound when using timestamper plugin
Change By:
Edwin Flores
When a single pipeline step generates a lot of logging all at once, the log on disk will repeat itself without end, eventually running the host out of disk space.This persists between Jenkins restarts and can only be stopped by stopping Jenkins, deleting the $JENKINS_HOME/jobs/[job]/build/[build id] directory, and starting Jenkins again.STR:1. Create a new pipeline job with the following pipeline script definition: {{ stage ('Boom') {node {timestamps {sh "seq 1 10"}}} }} 2. Run the job.Expected result:Job terminates eventually.Actual result:Job does not terminate, and fills the log continuously.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiv
[JIRA] (JENKINS-40762) Logs can grow without bound when using timestamper plugin
Title: Message Title
Edwin Flores created an issue
Jenkins / JENKINS-40762
Logs can grow without bound when using timestamper plugin
Issue Type:
Bug
Assignee:
Steven G Brown
Components:
timestamper-plugin
Created:
2017/Jan/03 9:32 AM
Environment:
Jenkins 2.19.1 Timestamper 1.8.7 (but observed in older versions as well)
Priority:
Minor
Reporter:
Edwin Flores
When a single pipeline step generates a lot of logging all at once, the log on disk will repeat itself without end, eventually running the host out of disk space. This persists between Jenkins restarts and can only be stopped by stopping Jenkins, deleting the $JENKINS_HOME/jobs/[job]/build/[build id] directory, and starting Jenkins again. STR: 1. Create a new pipeline job with the following pipeline script definition: {{stage ('Boom') { node { timestamps { sh "seq 1 10" } } }}} 2. Run the job. Expected result: Job terminates eventually. Actual result: Job does not terminate, and fills the log continuously.
Add Comment
[JIRA] (JENKINS-40762) Logs can grow without bound when using timestamper plugin
Title: Message Title
Edwin Flores updated an issue
Jenkins / JENKINS-40762
Logs can grow without bound when using timestamper plugin
Change By:
Edwin Flores
When a single pipeline step generates a lot of logging all at once, the log on disk will repeat itself without end, eventually running the host out of disk space.This persists between Jenkins restarts and can only be stopped by stopping Jenkins, deleting the $JENKINS_HOME/jobs/[job]/build/[build id] directory, and starting Jenkins again.STR:1. Create a new pipeline job with the following pipeline script definition:{{ stage ('Boom') {node {timestamps {sh "seq 1 10"}}} }}2. Run the job.Expected result:Job terminates eventually.Actual result:Job does not terminate, and fills the log continuously.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiv
[JIRA] (JENKINS-40723) Built Dockerfile images are never removed
Title: Message Title Gavin Llewellyn commented on JENKINS-40723 Re: Built Dockerfile images are never removed At the moment, the Dockerfile builds are fairly quick after the first build, as Docker's cache is used to avoid rebuilding any Dockerfile steps that haven't changed. This caching would be defeated if the built image was deleted after each build (unless the Docker node has similar images that are not managed by Jenkins). Determining whether an image should be rebuilt is not necessarily as simple as checking whether the Dockerfile has changed, or that a previous image built for that same Dockerfile still exists. I think this logic should be left to Docker, and not replicated in Jenkins. My suggestion would be the following: When building a Dockerfile, tag the resulting image with the job name/Id instead of the Dockerfile hash. Before building a Dockerfile, check for an existing image using the job's tag. If an image exists, note the image ID. After building a Dockerfile, check the image ID of the current image with the job's tag. If the image ID has changed (i.e. the tag has moved), delete the old image. If a job's name is changed, or a job is deleted, there may be some images left orphaned in the Docker node. However, it will be much easier for an admin to clean these up in the future, as the tags would make it obvious what the images were used for. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40763) Token expansion fails when workspace is not available
Title: Message Title Tommy Tynjä created an issue Jenkins / JENKINS-40763 Token expansion fails when workspace is not available Issue Type: Bug Assignee: Tommy Tynjä Components: delivery-pipeline-plugin Created: 2017/Jan/03 9:44 AM Environment: Jenkins 2.19 Delivery Pipeline Plugin 0.10.1 Token Macro Plugin 2.0 Priority: Critical Reporter: Tommy Tynjä If the workspace of a job is not available, task name token expansion fails since the token macro plugin is trying to get the workspace of the node where the build was performed. If the workspace or node is not available, token expansion fails which causes a TokenMacroException. A log message will be emitted and TokenUtils returns an empty string. If your view contains a lot of tasks / pipelines the Jenkins log will be flooded. See https://github.com/Diabol/delivery-pipeline-plugin/blob/master/src/main/java/se/diabol/jenkins/pipeline/token/TokenUtils.java#L51. Add Comment
[JIRA] (JENKINS-40763) Token expansion fails when workspace is not available
Title: Message Title Tommy Tynjä commented on JENKINS-40763 Re: Token expansion fails when workspace is not available The behavior of token-macro plugin has changed in 2.0 so it requires the workspace to be accessible. A workaround for this issue is to downgrade token-macro plugin to 1.10. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40137) Open in blue ocean button does not work for runs when the branch name contains a /
Title: Message Title Tom FENNELLY started work on JENKINS-40137 Change By: Tom FENNELLY Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33358) Groovy and PermGen memory leak
Title: Message Title Emmanuel Debanne commented on JENKINS-33358 Re: Groovy and PermGen memory leak Jenkins 2.19.4 uses Groovy 2.4.7 that contains a memory leak: https://issues.apache.org/jira/browse/GROOVY-7683 It will be fixed in Groovy 2.4.8 (not release yet). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40764) New Feature - Support Hidden Parameter Plugin
Title: Message Title Ebrahim Moshaya created an issue Jenkins / JENKINS-40764 New Feature - Support Hidden Parameter Plugin Issue Type: Improvement Assignee: mdonohue Components: configurationslicing-plugin Created: 2017/Jan/03 10:11 AM Priority: Minor Reporter: Ebrahim Moshaya Update the Parameter slicer to support the Hidden Parameter plugin https://github.com/jenkinsci/hidden-parameter-plugin The hidden parameter plugin is exactly the same as the string parameter but is not visible in the list of parameters when triggering builds. Add Comment
[JIRA] (JENKINS-39657) Chrome Dev Tools Extension for Blue Ocean
Title: Message Title Tom FENNELLY started work on JENKINS-39657 Change By: Tom FENNELLY Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39657) Chrome Dev Tools Extension for Blue Ocean
Title: Message Title Tom FENNELLY stopped work on JENKINS-39657 Change By: Tom FENNELLY Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39657) Chrome Dev Tools Extension for Blue Ocean
Title: Message Title Tom FENNELLY commented on JENKINS-39657 Re: Chrome Dev Tools Extension for Blue Ocean I did a small bit of hacking on this while on xmas hols and intend doing more in my own spare time, so marking it as in-progress. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39657) Chrome Dev Tools Extension for Blue Ocean
Title: Message Title Tom FENNELLY started work on JENKINS-39657 Change By: Tom FENNELLY Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40765) Make Release Plugin compatible with pipeline
Title: Message Title Alexey M created an issue Jenkins / JENKINS-40765 Make Release Plugin compatible with pipeline Issue Type: Improvement Assignee: Peter Hayes Components: release-plugin Created: 2017/Jan/03 10:19 AM Priority: Minor Reporter: Alexey M Allow to trigger release plugin from a pipeline dsl. It should be similar to trigger job's build. To support this the plugin would need to be refactored according to pipeline development instructions: https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md Add Comment
[JIRA] (JENKINS-40766) Make M2 Release Plugin compatible with pipeline
Title: Message Title Alexey M updated an issue Jenkins / JENKINS-40766 Make M2 Release Plugin compatible with pipeline Change By: Alexey M Component/s: m2release-plugin Component/s: release-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40766) Make M2 Release Plugin compatible with pipeline
Title: Message Title Alexey M created an issue Jenkins / JENKINS-40766 Make M2 Release Plugin compatible with pipeline Issue Type: Improvement Assignee: Peter Hayes Components: release-plugin Created: 2017/Jan/03 10:21 AM Priority: Minor Reporter: Alexey M Allow to trigger release plugin from a pipeline dsl. It should be similar to trigger job's build. To support this the plugin would need to be refactored according to pipeline development instructions: https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md Add Comment
[JIRA] (JENKINS-39657) Chrome Dev Tools Extension for Blue Ocean
Title: Message Title Tom FENNELLY commented on JENKINS-39657 Re: Chrome Dev Tools Extension for Blue Ocean Experimenting with adding something that allows us to easily turn on and off logging levels for different log categories. Currently looking at using @jenkins-cd/diag for the logging. Some Yak Shaving required though first because need to make some changes to @jenkins-cd/diag first in order to make it use client-side localStorage more sanely wrt log categories etc, which is leading to a bit more Yak Shaving as we need a better way of managing client-side localStorage, which resulted in me playing with @jenkins-cd/storage. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40767) Failures in scanning / indexing should prevent the orphaned item strategy from running
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-40767 Failures in scanning / indexing should prevent the orphaned item strategy from running Issue Type: Bug Assignee: Stephen Connolly Components: branch-api-plugin Created: 2017/Jan/03 10:34 AM Priority: Blocker Reporter: Stephen Connolly If scanning / indexing fails, we should not apply the orphaned item strategy otherwise we can end up deleting things that were missed from indexing just because an API rate limit has been hit Add Comment
[JIRA] (JENKINS-40749) Set greater threshold for disk full by default
Title: Message Title Daniel Beck commented on JENKINS-40749 Re: Set greater threshold for disk full by default Christoph Obexer We have no stats data on average free disk space. Do you expect many Jenkins instances to run on 1-10 GB free disk space? Note that like other admin monitors, this warning can easily be dismissed – it's not like the node monitors taking nodes offline. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40768) Jenkins client-side HTML5 storage API
Title: Message Title Tom FENNELLY created an issue Jenkins / JENKINS-40768 Jenkins client-side HTML5 storage API Issue Type: Task Assignee: Tom FENNELLY Components: blueocean-plugin Created: 2017/Jan/03 10:55 AM Priority: Minor Reporter: Tom FENNELLY Not specifically related to Blue Ocean, but it is driving the requirements for it atm. Problem: HTML5 localStorage is great for storing per-domain name/value pairs, but it's a totally flat structure. The lack of hierarchy/namespacing makes it difficult to perform operations on subsets of data stored in localStorage e.g. to clear out (invalidate) a subset of localStorage NVPs when a new instance of Jenkins is installed, or to group a subset of NVPs and have APIs that allow the client code to just navigate those properties only e.g. log categories. Requirements: Support for NVP namespacing with so that we can perform operations on a subset of NVPs i.e. set and get in the namespace. clear all NVPs in a namespace. Obviously, should not remove NVPs in other namespaces. This will e.g. allow us to clear all NVPs associated with a Jenkins "instance" after a new instance is installed, or plugins have ben added/removed/updated. iterate all NVPs in a namespace. Support more than just string values e.g. boolean, number, object. Not function though, obviously. Support subspaces i.e. namespaces inside namespaces e.g. you could have the "log-gategory" namespace inside t
[JIRA] (JENKINS-40768) Jenkins client-side HTML5 storage API
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-40768 Jenkins client-side HTML5 storage API Change By: Tom FENNELLY Not specifically related to Blue Ocean, but it is driving the requirements for it atm.*Problem*:HTML5 localStorage is great for storing per-domain name/value pairs, but it's a totally flat structure. The lack of hierarchy/namespacing makes it difficult to perform operations on subsets of data stored in localStorage e.g. to clear out (invalidate) a subset of localStorage NVPs when a new instance of Jenkins is installed, or to group a subset of NVPs and have APIs that allow the client code to just navigate those properties only e.g. log categories.*Requirements*:# Support for NVP namespacing with so that we can perform operations on a subset of NVPs i.e.## set and get in the namespace.## clear all NVPs in a namespace. Obviously, should not remove NVPs in other namespaces. This will e.g. allow us to clear all NVPs associated with a Jenkins "instance" after a new instance is installed, or plugins have ben added/removed/updated.## iterate all NVPs in a namespace.# Support more than just string values e.g. boolean, number, object. Not function though, obviously.# Support subspaces i.e. namespaces inside namespaces e.g. you could have the "log-gategory" namespace inside the "jenkins-instance" namespace i.e. "jenkins-instance/log-gategory". Another one might be "jenkins-instance/classes-info" for storing classes metadata Vs the client UI contantly firing REST API calls to get it (see [JENKINS-40080|https://issues.jenkins-ci.org/browse/JENKINS-40080]).# Support get fallback options whereby you can configure the get to look in parent namespaces, or if using a dot separated key in the name (the N part of the NVP) that it can be configured to check back along the "dot parent path" e.g. if "org.jenkins.a.b" has no value, then fallback and check "org.jenkins.a" etc. This would be useful for e.g. log categories. Add Comment
[JIRA] (JENKINS-40768) Jenkins client-side HTML5 storage API
Title: Message Title Tom FENNELLY commented on JENKINS-40768 Re: Jenkins client-side HTML5 storage API I did some playing with this over my xmas vacation. See https://github.com/tfennelly/jenkins-js-storage. Examples of how the namespace and subspacing APIs might work can be seen in spec/StorageNamespace.js tests. Examples of how the typing APIs might work can be seen in spec/types.js tests. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40768) Jenkins client-side HTML5 storage API
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-40768 Jenkins client-side HTML5 storage API Change By: Tom FENNELLY Not specifically related to Blue Ocean, but it is driving the requirements for it atm.*Problem*: HTML5 localStorage is great for storing per-domain name/value pairs, but it's a totally flat and untyped structure. The lack of hierarchy/namespacing makes it difficult to perform operations on subsets of data stored in localStorage e.g. to clear out (invalidate) a subset of localStorage NVPs when a new instance of Jenkins is installed, or to group a subset of NVPs and have APIs that allow the client code to just navigate those properties only e.g. log categories.*Requirements*:# Support for NVP namespacing with so that we can perform operations on a subset of NVPs i.e.## set and get in the namespace.## clear all NVPs in a namespace. Obviously, should not remove NVPs in other namespaces. This will e.g. allow us to clear all NVPs associated with a Jenkins "instance" after a new instance is installed, or plugins have ben added/removed/updated.## iterate all NVPs in a namespace.# Support more than just string values e.g. boolean, number, object. Not function though, obviously.# Support subspaces i.e. namespaces inside namespaces e.g. you could have the "log-gategory" namespace inside the "jenkins-instance" namespace i.e. "jenkins-instance/log-gategory". Another one might be "jenkins-instance/classes-info" for storing classes metadata Vs the client UI contantly firing REST API calls to get it (see [JENKINS-40080|https://issues.jenkins-ci.org/browse/JENKINS-40080]).# Support get fallback options whereby you can configure the get to look in parent namespaces, or if using a dot separated key in the name (the N part of the NVP) that it can be configured to check back along the "dot parent path" e.g. if "org.jenkins.a.b" has no value, then fallback and check "org.jenkins.a" etc. This would be useful for e.g. log categories. Add Comment
[JIRA] (JENKINS-40768) Jenkins client-side HTML5 storage API
Title: Message Title Tom FENNELLY commented on JENKINS-40768 Re: Jenkins client-side HTML5 storage API I'm working on this in the background in my spare time, so marking it as in-progress. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40768) Jenkins client-side HTML5 storage API
Title: Message Title Tom FENNELLY started work on JENKINS-40768 Change By: Tom FENNELLY Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40080) All pages make multiple /classes requests
Title: Message Title Tom FENNELLY commented on JENKINS-40080 Re: All pages make multiple /classes requests FYI, see JENKINS-40768 as something that can help make this happen. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39657) Chrome Dev Tools Extension for Blue Ocean
Title: Message Title Tom FENNELLY edited a comment on JENKINS-39657 Re: Chrome Dev Tools Extension for Blue Ocean Experimenting with adding something that allows us to easily turn on and off logging levels for different log categories.Currently looking at using [@jenkins-cd/diag|https://www.npmjs.com/package/@jenkins-cd/diag] for the logging. Some Yak Shaving required though first because need to make some changes to [@jenkins-cd/diag|https://www.npmjs.com/package/@jenkins-cd/diag] first in order to make it use client-side localStorage more sanely wrt log categories etc, which is leading to a bit more Yak Shaving :P as we need a better way of managing client-side localStorage, which resulted in me playing with [@jenkins-cd/storage|https://github.com/tfennelly/jenkins-js-storage] (see JENKINS-40768) . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40769) Option to generate one graph per trx file
Title: Message Title Jani Mäkelä created an issue Jenkins / JENKINS-40769 Option to generate one graph per trx file Issue Type: New Feature Assignee: Ivo Bellin Salarin Components: mstest-plugin Created: 2017/Jan/03 11:07 AM Labels: test test-results test-statistics-graph test-statistics-chart Priority: Minor Reporter: Jani Mäkelä It would be nice to have graphs for tests per trx file. This would enable separate test tracking of solutions in the same jenkins build. There is a java plugin for this so it should be in the realm of possibility. Add Comment
[JIRA] (JENKINS-40751) unable to configure credentials user password
Title: Message Title Brahim Hadu closed an issue as Incomplete Jenkins / JENKINS-40751 unable to configure credentials user password Change By: Brahim Hadu Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title dan tran commented on JENKINS-40484 Re: Unable to use withMaven step inside docker container Love to see this fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40715) Race condition in UpdateCenter#waitForInstallationToComplete
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40715 Re: Race condition in UpdateCenter#waitForInstallationToComplete Code changed in jenkins User: Manuel Franco Path: src/main/java/org/jenkinsci/test/acceptance/Matchers.java src/main/java/org/jenkinsci/test/acceptance/po/UpdateCenter.java http://jenkins-ci.org/commit/acceptance-test-harness/3305d543ed83b347cecd9af9bf0b4f4c8417a8e2 Log: JENKINS-40715 Fix race condition in 'UpdateCenter#waitForInstallationToComplete' Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40715) Race condition in UpdateCenter#waitForInstallationToComplete
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40715 Re: Race condition in UpdateCenter#waitForInstallationToComplete Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/test/acceptance/Matchers.java src/main/java/org/jenkinsci/test/acceptance/po/UpdateCenter.java http://jenkins-ci.org/commit/acceptance-test-harness/87a407ef80afb306cf944b065943d3fd93c7fbb0 Log: Merge pull request #249 from mafraba/JENKINS-40715 JENKINS-40715 Fix race condition in 'UpdateCenter#waitForInstallationToComplete' Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/735eb45653af...87a407ef80af Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40770) Take into account optional dependencies during plugins installation
Title: Message Title Evaristo Gutierrez created an issue Jenkins / JENKINS-40770 Take into account optional dependencies during plugins installation Issue Type: Task Assignee: Evaristo Gutierrez Components: acceptance-test-harness Created: 2017/Jan/03 11:41 AM Priority: Minor Reporter: Evaristo Gutierrez A plugin can declare a dependency as optional, so it's not taken into account when installing the plugin. In a test, that optional dependency can be required through @WithPlugins annotation. That is making the plugin to be installed but not necessarily before the plugin with the dependency, which can make some extension points not to be functional. In some occasions, that is making some tests to fail as there is no installation error (as the dependency is optional) and a restart is not therefore required. Thus: if a plugin has an optional dependency that is marked as required, that dependency needs to be installed before the plugin itself.
[JIRA] (JENKINS-40770) Take into account optional dependencies during plugins installation
Title: Message Title Evaristo Gutierrez started work on JENKINS-40770 Change By: Evaristo Gutierrez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40770) Take into account optional dependencies during plugins installation
Title: Message Title Evaristo Gutierrez edited a comment on JENKINS-40770 Re: Take into account optional dependencies during plugins installation To get some additional context on this issue: ( [ ATH PR #216|https://github.com/jenkinsci/acceptance-test-harness/pull/216 ) ] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40770) Take into account optional dependencies during plugins installation
Title: Message Title Evaristo Gutierrez commented on JENKINS-40770 Re: Take into account optional dependencies during plugins installation To get some additional context on this issue: (ATH PR #216|https://github.com/jenkinsci/acceptance-test-harness/pull/216) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40771) Pipeline causes job to hang infinitely on restart
Title: Message Title
Tuan Nguyen created an issue
Jenkins / JENKINS-40771
Pipeline causes job to hang infinitely on restart
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-aggregator-plugin
Created:
2017/Jan/03 12:01 PM
Priority:
Minor
Reporter:
Tuan Nguyen
Hi, We found a potential bug that can only be replicated in pipeline jobs. Essentially when a job a running and a Jenkins restart occurs, the job is left hanging infinitely:
Resuming build at Tue Jan 03 10:37:18 UTC 2017 after Jenkins restart
Waiting to resume part of TestRun2 #2: Waiting for next available executor
Waiting to resume part of TestRun2 #2: Waiting for next available executor
Waiting to resume part of TestRun2 #2: Waiting for next available executor
Waiting to resume part of TestRun2 #2: Waiting for next available executor
Waiting to resume part of TestRun2 #2: Waiting for next available executor
Waiting to resume part of TestRun2 #2: Waiting for next available executor
Waiting to resume part of TestRun2 #2: Waiting for next available executor
...
I noticed that this does not occur on any other job types. i.e. freestyle. Here is a simple test pipeline script:
node('X') {
stage 'Stage 1'
println 'Deploying to Stage 1...'
stage 'Stage 2'
println 'Running Tests in Stage 2'
sleep 120
println 'Tests passed!'
stage 'Stage 3'
println 'Deploying to Stage 3...'
}
...Restart
[JIRA] (JENKINS-40771) Pipeline causes job to hang infinitely on Jenkins restart
Title: Message Title
Tuan Nguyen updated an issue
Jenkins / JENKINS-40771
Pipeline causes job to hang infinitely on Jenkins restart
Change By:
Tuan Nguyen
Hi,We found a potential bug that can only be replicated in pipeline jobs. Essentially when a job a running and a Jenkins restart occurs, the job is left hanging infinitely:{noformat}Resuming build at Tue Jan 03 10:37:18 UTC 2017 after Jenkins restartWaiting to resume part of TestRun2 #2: Waiting for next available executorWaiting to resume part of TestRun2 #2: Waiting for next available executorWaiting to resume part of TestRun2 #2: Waiting for next available executorWaiting to resume part of TestRun2 #2: Waiting for next available executorWaiting to resume part of TestRun2 #2: Waiting for next available executorWaiting to resume part of TestRun2 #2: Waiting for next available executorWaiting to resume part of TestRun2 #2: Waiting for next available executor...{noformat}I noticed that this behaviour does not occur exhibit on any other job types. i.e. freestyle.Here is a simple test pipeline script:{noformat}node('X') { stage 'Stage 1'println 'Deploying to Stage 1...' stage 'Stage 2'println 'Running Tests in Stage 2'sleep 120println 'Tests passed!' stage 'Stage 3'println 'Deploying to Stage 3...'}{noformat}...Restart Jenkins as soon as it enters Stage 2, to replicate such behaviour.Currently I am using version 2.3, but I believe this issue was replicated in previous versions.Please can you help me explain why this behaviour only exists in pipeline jobs?Kind Regards,Tuan
Add Comment
[JIRA] (JENKINS-40771) Pipeline causes job to hang infinitely on Jenkins restart
Title: Message Title Tuan Nguyen updated an issue Jenkins / JENKINS-40771 Pipeline causes job to hang infinitely on Jenkins restart Change By: Tuan Nguyen Summary: Pipeline causes job to hang infinitely on Jenkins restart Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40715) Race condition in UpdateCenter#waitForInstallationToComplete
Title: Message Title Manuel Franco resolved as Fixed Jenkins / JENKINS-40715 Race condition in UpdateCenter#waitForInstallationToComplete Change By: Manuel Franco Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40770) Take into account optional dependencies during plugins installation
Title: Message Title Evaristo Gutierrez updated JENKINS-40770 Jenkins / JENKINS-40770 Take into account optional dependencies during plugins installation Change By: Evaristo Gutierrez Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40718) Search by build param values in Build history widget
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-40718 Search by build param values in Build history widget Change By: Daniel Beck Issue Type: Patch New Feature Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40710) Remoting plugin searches for case-sensitive headers
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-40710 Remoting plugin searches for case-sensitive headers Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40718) Search by build param values in Build history widget
Title: Message Title Daniel Beck started work on JENKINS-40718 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40718) Search by build param values in Build history widget
Title: Message Title Daniel Beck assigned an issue to Marcin Zajączkowski Jenkins / JENKINS-40718 Search by build param values in Build history widget Change By: Daniel Beck Assignee: Marcin Zajączkowski Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40716) JDK installer for windows does not accept exe file
Title: Message Title Daniel Beck resolved as Not A Defect Not a defect. The zip/tar installers do what they're supposed to do; you'll need to repackage the JDK in a form that works with this generic approach. Jenkins / JENKINS-40716 JDK installer for windows does not accept exe file Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an em
[JIRA] (JENKINS-31114) Ant escape incorrectly on Windows
Title: Message Title sradi commented on JENKINS-31114 Re: Ant escape incorrectly on Windows Hi there, I am facing the same issue with 1.4. Armando Fernandez: Can you provide a schedule, when the issue might be solved? If I can help with the fix, please contact me. I just don't have enough understanding of the code, and how to escape the command correctly, to start implementing a fix. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40754) Jenkins crashes on display of JUnit duration graph
Title: Message Title Daniel Beck commented on JENKINS-40754 Re: Jenkins crashes on display of JUnit duration graph Pretty sure the problem is… OpenJDK Runtime Environment (9.0) (build 9-internal+0-2016-04-14-195246.buildd.src) We don't support prerelease JREs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40754) Jenkins crashes on display of JUnit duration graph
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-40754 Jenkins crashes on display of JUnit duration graph Change By: Daniel Beck Labels: jdk9 junit Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40757) Thread has died in all executors
Title: Message Title Daniel Beck resolved as Not A Defect Issue does not contain enough information to investigate further. The Jenkins version is almost two years outdated, needs to happen on a current release for us to care Looks more like a support request than a bug report. Jenkins / JENKINS-40757 Thread has died in all executors Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40754) Jenkins crashes on display of JUnit duration graph
Title: Message Title Daniel Beck resolved as Duplicate Jenkins / JENKINS-40754 Jenkins crashes on display of JUnit duration graph Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31114) Ant escape incorrectly on Windows
Title: Message Title Armando Fernandez commented on JENKINS-31114 Re: Ant escape incorrectly on Windows sradi I'll try to get this done by the end of next week. Thanks and sorry for the delay. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40772) plugin not compatible to folders plugin version 4.10 and older
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-40772 plugin not compatible to folders plugin version 4.10 and older Issue Type: Bug Assignee: Magnus Sandberg Components: prioritysorter-plugin Created: 2017/Jan/03 12:30 PM Environment: Jenkins 1.580.3 Folders plugin 4.10 Priority: Major Reporter: Markus Winter The priority sorter plugin is currently built againt Jenkins 1.580. But also againt folders plugin version 5.0 Folders plugin 5.0 has as minimum version 1.609.1 of jenkins. I have a jenkins on 1.580.3 and folders plugin 4.10 If I enable in a jobgroup "Jobs and Folders marked for inclusion", I get the following exception when configuring a job Caused by: java.lang.NoClassDefFoundError: com/cloudbees/hudson/plugins/folder/AbstractFolder So either the plugin is fixed so it can handle also older version of the folders plugin, or the minimum required version of Jenkins is set to 1.609.1 Add Comment
[JIRA] (JENKINS-40679) There should be no abort button for input steps
Title: Message Title Thorsten Scherler updated JENKINS-40679 Jenkins / JENKINS-40679 There should be no abort button for input steps Change By: Thorsten Scherler Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40679) There should be no abort button for input steps
Title: Message Title Thorsten Scherler started work on JENKINS-40679 Change By: Thorsten Scherler Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40679) There should be no abort button for input steps
Title: Message Title Thorsten Scherler commented on JENKINS-40679 Re: There should be no abort button for input steps solved in JENKINS-38494 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40773) Plugin doesn't work with the matrix type and maven build step
Title: Message Title Dan Albu created an issue Jenkins / JENKINS-40773 Plugin doesn't work with the matrix type and maven build step Issue Type: Bug Assignee: Dominik Bartholdi Components: config-file-provider-plugin Created: 2017/Jan/03 12:34 PM Environment: Latest plugin and Jenkins LTS versions Priority: Critical Reporter: Dan Albu I setup the settings xml config file inside the job for both global and local i get this in the job console: ERROR: your Apache Maven build is setup to use a config with id 6124fe43-3efd-4dbc-a507-a1fb305c3577 but can not find the config I did not have this issues with the previous version of the plugin prior to upgrade to 2.15.* Add Comment
[JIRA] (JENKINS-40773) Plugin doesn't work with the matrix type and maven build step
Title: Message Title Dan Albu updated an issue Jenkins / JENKINS-40773 Plugin doesn't work with the matrix type and maven build step Change By: Dan Albu I setup the settings xml config file inside the job for both global and local i get this in the job console:ERROR: your Apache Maven build is setup to use a config with id 6124fe43-3efd-4dbc-a507-a1fb305c3577 but can not find the configI did not have this issues with the previous version of the plugin prior to upgrade to 2.15.* Both the id and configuration file are setup in the plugin config page.I can provide further information if needed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40773) Plugin doesn't work with the matrix type and maven build step
Title: Message Title Dominik Bartholdi commented on JENKINS-40773 Re: Plugin doesn't work with the matrix type and maven build step it would help if you could provide a support bundle generated with this plugin: https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40763) Token expansion fails when workspace is not available
Title: Message Title Tommy Tynjä commented on JENKINS-40763 Re: Token expansion fails when workspace is not available Proposed solution for solving task names defaulting to job names: https://github.com/Diabol/delivery-pipeline-plugin/pull/226 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40716) JDK installer for windows does not accept exe file
Title: Message Title A B updated JENKINS-40716 Jenkins / JENKINS-40716 JDK installer for windows does not accept exe file Change By: A B Status: Resolved In Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40763) Token expansion fails when workspace is not available
Title: Message Title Tommy Tynjä updated an issue Jenkins / JENKINS-40763 Token expansion fails when workspace is not available Change By: Tommy Tynjä If the workspace of a job is not available, task name token expansion fails since the token macro plugin is trying to get the workspace of the node where the build was performed. If the workspace or node is not available, token expansion fails which causes a TokenMacroException. A log message will be emitted and TokenUtils returns an empty string. If your view contains a lot of tasks / pipelines the Jenkins log will be flooded. See https://github.com/Diabol/delivery-pipeline-plugin/blob/master/src/main/java/se/diabol/jenkins/pipeline/token/TokenUtils.java#L51. This causes the configured task names not to be shown in the delivery pipeline view (even if no expandable variables exist), which makes the task names default to the job name.Workaround is to downgrade token-macro plugin to 1.x of 1.9 or later. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40716) JDK installer for windows does not accept exe file
Title: Message Title A B commented on JENKINS-40716 Re: JDK installer for windows does not accept exe file I agree. It is not a defect. It is rather a feature request. Taking into account that the package is delivered in form of exe file it would be fine to treat this case also. Namely, instead of delegating the conversion from exe to zip to fibnal users - perform this operation internally by Jenkins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40716) JDK installer for windows does not accept exe file
Title: Message Title Daniel Beck commented on JENKINS-40716 Re: JDK installer for windows does not accept exe file This feature already exists, and it's called Install from java.sun.com. If you can't use it, that's unfortunate, but looks like an edge case. Some legwork is to be expected. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40774) Pipeline project type not supported
Title: Message Title
David Staheli created an issue
Jenkins / JENKINS-40774
Pipeline project type not supported
Issue Type:
Bug
Assignee:
redsolo
Components:
tfs-plugin
Created:
2017/Jan/03 1:24 PM
Environment:
Jenkins Version: 2.19.3 Team Foundation Server Plug-in Version: 5.2.1
Priority:
Critical
Reporter:
David Staheli
The Pipeline type in Jenkins 2.19.x is not supported by the TFS Plugin. This is a new type introduced in the workflow plugin and the current TFS Plugin does not have a dependency on it, hence it fails on Pipelines. Line 206 of TeamBuildEndpoint.java attempts to retrieve an AbstractProject by name. If it is a pipeline, null is returned, resulting in an IllegalArgumentException("Project not found");. Can the TFS Plugin take a dependency on a later version of Jenkins that supports pipelines?
Add Comment
[JIRA] (JENKINS-31114) Ant escape incorrectly on Windows
Title: Message Title sradi commented on JENKINS-31114 Re: Ant escape incorrectly on Windows Thanks for the info! This issue seems to have the same cause, as JENKINS-37827. If it helps, here are the results of my little research: I created a little job, that takes a string parameter and executes a simple ant build. Build parameter: string "with" double quotes On Jenkins 1.587 with ant plugin 1.2 I see this in the console output: cmd.exe /C '"ant.bat "-Denv=string ""with"" double quotes" foo && exit %%ERRORLEVEL%%"' ..works fine On Jenkins 2.32.1 with ant plugin 1.4 I see: cmd.exe /C "ant.bat '"-Denv=string ""with"" double quotes"' foo && exit %%ERRORLEVEL%%" ... works fine, as well. Now I am adding backslashes, like e.g. the GitHub Pullrequest Builder Plugin does, in the environment variables injected into the job. Build parameter: string \"with\" double quotes On Jenkins 1.587 with ant plugin 1.2 I see this in the console output: cmd.exe /C '"ant.bat "-Denv=string \""with\"" double quotes" foo && exit %%ERRORLEVEL%%"' ..works fine On Jenkins 2.32.1 with ant plugin 1.4 I see: cmd.exe /C "ant.bat '"-Denv=string \""with\"" double quotes"' foo && exit %%ERRORLEVEL%%" ... works fine, as well. Now I am adding a whitespace in between the double quotes: Build parameter: string \"with double\" quotes On Jenkins 1.587 with ant plugin 1.2 I see this in the console output: cmd.exe /C '"ant.bat "-Denv=string \""with double\"" quotes" foo && exit %%ERRORLEVEL%%"' ..BUILD FAILED: Target "double"" quotes" does not exist in the project "foo". On Jenkins 2.32.1 with ant plugin 1.4 I see: cmd.exe /C "ant.bat '"-Denv=string \""with double\"" quotes"' foo && exit %%ERRORLEVEL%%" ...BUILD FAILED: Target "double"" quotes" does not exist in the project "foo". Conclusion: The problem occurs, if there are whitespaces in between the double quotes, Add Comment
[JIRA] (JENKINS-38494) User can see the input form on an input step (UI)
Title: Message Title Thorsten Scherler updated JENKINS-38494 Jenkins / JENKINS-38494 User can see the input form on an input step (UI) Change By: Thorsten Scherler Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title Cyrille Le Clerc commented on JENKINS-40712 Re: Exception when using mavenSettingsConfig FYI Alvaro Lobato has kindly released a few hours ago while he is on holidays. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40679) There should be no abort button for input steps
Title: Message Title Thorsten Scherler updated JENKINS-40679 Jenkins / JENKINS-40679 There should be no abort button for input steps Change By: Thorsten Scherler Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40648) Input state isn't updated in activity/branch listing from SSE
Title: Message Title Thorsten Scherler started work on JENKINS-40648 Change By: Thorsten Scherler Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39726) Don't rebuild all PRs on base branch update
Title: Message Title Justin Rainwater commented on JENKINS-39726 Re: Don't rebuild all PRs on base branch update I'm very excited to try v2.0.0 because this issue was blocking for us as well. Is there a way I could "watch" the releases of GitHub Branch Source plugin so I'm notified as soon as the official v2.0.0 is available? Thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title
Bruno Meneguello commented on JENKINS-40484
Re: Unable to use withMaven step inside docker container
Same here, with this simple use case:
node('master') {
docker.image('maven').inside {
withMaven {
sh 'mvn -version'
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40775) Explicit plugin builds can be overriden by Jenkins
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-40775 Explicit plugin builds can be overriden by Jenkins Issue Type: Bug Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2017/Jan/03 2:21 PM Priority: Major Reporter: Oliver Gondža The default plugin installation strategy performs dependency resolution on its own and upload plugins. Except for the maintenance cost and fragileness, latest Jenkins versions started to overwrite plugins controlled explicitly. The upload approach allows users to specify version or binary of the plugin to install. That is used instead of latest release available and installed. However, when the deploy of such plugin fails (which is ok as we detect that and restart) but installation of dependent plugin can cause different version of dependency to overrwrite the requested one. Actual example: test require openstack-cloud, that depends on config-file-provider that depend on bundled plugin. When running the tests I overwrite config-file-provider version. But since that needs bundled plugin updated (which require restart) it is not dynamically deployed until restart. When openstack-cloud is being uploaded, Jenkins detects its dependency is not loaded (only installed) and fetch latest version from update center. So my attempt to override the version is ignored silently. There is no log from core or ath indicating this is happening - just .bak file in plugins dir.
[JIRA] (JENKINS-40648) Input state isn't updated in activity/branch listing from SSE
Title: Message Title Thorsten Scherler commented on JENKINS-40648 Re: Input state isn't updated in activity/branch listing from SSE Not sure whether this is a minor thing, but it seems since the introduction of mbox we do not listen to sse events for that pages. Need to look deeper into the issue Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39571) Jenkins doesn't start after plugin update
Title: Message Title M U commented on JENKINS-39571 Re: Jenkins doesn't start after plugin update Dear Daniel Beck, I perfectly understand your situation, but try to understand my position: I've read https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+is+hanging and created the requested reports. Afterwards, I've opened an entry in your Google group https://groups.google.com/forum/#!topic/jenkinsci-users/t6P3hjM3DEA and got the advice to create a bug report. Within the ticket, I've added all the created reports. I see no point in your JIRA guidelines that would change my opinion of creating a bug report: I've checked all the existing tickets, but none of them did describe my problem exactly. I was using the current version of Jenkins when opening the ticket, so your general complaint that you often have to close tickets because the reported issues have been solved in newer versions may be right and comprehensible, but not relevant in my special case. This is an unobjective fact. To summarize and emphasize: the Jenkins-Update-UI provides a CheckBox to trigger a restart. As far as I understand a restart, it should stop and start the system properly so that it can be used again. When using the Restart-CheckBox, Jenkins gets stopped and partially started, but does not return so that it can be used - therefore it is a bug. Whether this behaviour occurs because of Jenkins, Java, Windows or the lord himself is not the point, it occurs within Jenkins. If you would find out that Java is responsible, then I would have to contact Oracle and closing the JIRA ticket would be the correct way. I really don't want to struggle, but saying that the requestor is the only person making a mistake and negating the fact that the software does not work properly is a little biased. Anyway, I know that we disagree about the communication, but I would appreciate focussing on the solution on the real issue of this ticket, because I still encounter the problem, even in Jenkins 2.37. So if you have further questions regarding the technical problems, please do not hesitate to contact me. If you have further words to say about the non-technical stuff, we should clarify this by PM, because this really pollutes the issue. Regards Add Comment
[JIRA] (JENKINS-36559) File pattern (e.g. archive) field validation can run forever
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-36559 File pattern (e.g. archive) field validation can run forever Change By: Daniel Beck Summary: UI hangs File pattern (e.g. archive) field validation can run forever Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40710) Remoting plugin searches for case-sensitive headers
Title: Message Title Daniel Beck started work on JENKINS-40710 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40710) Remoting plugin searches for case-sensitive headers
Title: Message Title Daniel Beck updated JENKINS-40710 Jenkins / JENKINS-40710 Remoting plugin searches for case-sensitive headers Change By: Daniel Beck Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40219) Add support for Folder level configuration
Title: Message Title Izek Greenfied commented on JENKINS-40219 Re: Add support for Folder level configuration not latest release, latest code they merge my pull request thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37478) OWASP does not release files from scan
Title: Message Title David Norman commented on JENKINS-37478 Re: OWASP does not release files from scan That java bug makes things sound hopeless, but then I wonder why it took 3 years for someone to report files not deleting after inspecting them in Windows. Did the inspection method change recently in a way that can be reverted? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40775) Explicit plugin builds can be overriden by Jenkins
Title: Message Title Daniel Beck commented on JENKINS-40775 Re: Explicit plugin builds can be overriden by Jenkins Jenkins detects its dependency is not loaded (only installed) and fetch latest version from update center Looks to me like the problem is here. This should not happen. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40613) DurableTaskStep.Execution.getWorkspace() should be subject to timeout
Title: Message Title Jesse Glick commented on JENKINS-40613 Re: DurableTaskStep.Execution.getWorkspace() should be subject to timeout Unfortunately I have not been able to reproduce the problem. For example, if I attach an agent (using CommandLauncher), obtain the Channel/FilePath (simulating the ws field here being populated), kill -9 the agent JVM, and call .isDirectory(), the command immediately fails: java.io.IOException: remote file operation failed: /tmp/slave at hudson.remoting.Channel@3b3848de:remote: hudson.remoting.ChannelClosedException: channel is already closed at hudson.FilePath.act(FilePath.java:1014) at hudson.FilePath.act(FilePath.java:996) at hudson.FilePath.isDirectory(FilePath.java:1532) at … Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:578) at hudson.remoting.Request.call(Request.java:130) at hudson.remoting.Channel.call(Channel.java:796) at hudson.FilePath.act(FilePath.java:1007) ... 84 more Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2626) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1321) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:373) at hudson.remoting.Command.readFrom(Command.java:94) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59) So there is some sort of failure mode of Remoting which is not trivially reproduced. Add Comment This message was sent by Atlassian JIRA (v7.1.7#710
[JIRA] (JENKINS-37486) NPE: Failed to abort at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.stop(FileMonitoringTask.java:167)
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-37486 NPE: Failed to abort at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.stop(FileMonitoringTask.java:167) Change By: Jesse Glick Component/s: workflow-durable-task-step-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37486) NPE: Failed to abort at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.stop(FileMonitoringTask.java:167)
Title: Message Title Jesse Glick started work on JENKINS-37486 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40775) Explicit plugin builds can be overriden by Jenkins
Title: Message Title Oliver Gondža commented on JENKINS-40775 Re: Explicit plugin builds can be overriden by Jenkins I do not dare to conclude that. Possibly the dependency needs restart or it is something that will never install correctly for some other reason. Alex Earl, wdyt, as an author? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
