[JIRA] [docker-traceability-plugin] (JENKINS-28658) Support creation of named container fingerprints
Title: Message Title Oleg Nenashev reopened an issue we have not merged it to the master yet Jenkins / JENKINS-28658 Support creation of named container fingerprints Change By: Oleg Nenashev Resolution: Fixed Status: Resolved Reopened 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-28685) NullPointerException when saving Jenkins project
Title: Message Title Chin Boon Oh created an issue Jenkins / JENKINS-28685 NullPointerException when saving Jenkins project Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Jun/15 6:10 AM Environment: Jenkins Version 1.6.13 RHEL Java 7 Priority: Major Reporter: Chin Boon Oh When saving a Jenkins job, the following exception occurs: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) 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
[JIRA] [radiatorview-plugin] (JENKINS-28674) Timing mismatch between radiator and individual jenkin job
Title: Message Title Judah Benhur commented on JENKINS-28674 Re: Timing mismatch between radiator and individual jenkin job Hi Tyler, Can I get to know about issue reported and how could it be resolved and why is it happening or what has gone wrong? Regards, Judah 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-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman commented on JENKINS-28633 Re: Plugin update does not work any more 1. I did not use a custom update center. 2. This issue looks like is related to the JENKINS-28544 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-24673) SimpleBuildWrapper
Title: Message Title Jesse Glick resolved as Fixed Workflow 1.8 has the new wrap step. Jenkins / JENKINS-24673 SimpleBuildWrapper Change By: Jesse Glick 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] [repo-plugin] (JENKINS-28684) When checking for changes the Repo may not be run on the correct slave
Title: Message Title Matt Schuckmann created an issue Jenkins / JENKINS-28684 When checking for changes the Repo may not be run on the correct slave Issue Type: Bug Assignee: Unassigned Components: repo-plugin Created: 01/Jun/15 11:54 PM Environment: jenkins 1.613 repo plugin 1.7.1 Priority: Minor Reporter: Matt Schuckmann I have a master Jenkins slave configuration with: Master: linux ubuntu 12.04 slave1: linux ubuntu 14.04 slave2: windows server 2003 I have a project using the repo scm plugin to checkout the source code. The project is restricted to only run on slave1. When I enabled polling to check for changes every 15 min and then check the Gerrit Repo Polling Log I see that polling fails because it is attempting to poll on slave2 which does not have repo installed, I would have thought if the project was restricted to run on a specific slave then the polling would also occur on that slave? I do know that the Multiple-SCM plugin as the option "Force polling using workspace" to solve this problem, perhaps a similar option needs to be added to the Repo plugin.
[JIRA] [notification-plugin] (JENKINS-26162) Plugin results in error: "artifacts Map already contains mapping of location"
Title: Message Title Adriaan Moors commented on JENKINS-26162 Re: Plugin results in error: "artifacts Map already contains mapping of location" This bug renders the plugin unusable if you have multiple artifacts with the same filename (but different paths). 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-28561) Can't Setup Security
Title: Message Title Daniel Beck commented on JENKINS-28561 Re: Can't Setup Security Please provide the exact Jenkins version, it's shown at the bottom right on every page. Also, what security realm are you setting up? 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-28683) PeriodicWork.init() does not work for dynamically-loaded plugins
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-28683 PeriodicWork.init() does not work for dynamically-loaded plugins Issue Type: Bug Assignee: Unassigned Components: core Created: 01/Jun/15 10:01 PM Priority: Major Reporter: Jesse Glick PeriodicWork.init() is run after JOB_LOADED. If a plugin is subsequently installed which includes such an extension, its work is not run until after a Jenkins restart. Should use the new ExtensionListListener to detect this case and start the task. Add Comment
[JIRA] [core] (JENKINS-27854) iOS Unit Tests hang after Jenkins Update
Title: Message Title Konstantin Tchernov commented on JENKINS-27854 Re: iOS Unit Tests hang after Jenkins Update This issue is still present with Jenkins 1.616. It's a fairly critical issue and we are investigating alternatives to Jenkins as a result. Any chance of this being 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-27854) iOS Unit Tests hang after Jenkins Update
Title: Message Title Konstantin Tchernov updated an issue Jenkins / JENKINS-27854 iOS Unit Tests hang after Jenkins Update Change By: Konstantin Tchernov Environment: Jenkins 1. 608 616 , Xcode 6.2, Mac OS 10.9 & 10.10 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] [docker-traceability-plugin] (JENKINS-28655) Make Docker Traceability tolerant against FingerprintCleanupThread
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28655 Re: Make Docker Traceability tolerant against FingerprintCleanupThread Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceJob.java http://jenkins-ci.org/commit/docker-traceability-plugin/2ee1c9dfc567e41b04a43c6b52c62cb600c5f188 Log: JENKINS-28655 - Fix the map key 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] [docker-traceability-plugin] (JENKINS-28658) Support creation of named container fingerprints
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28658 Support creation of named container fingerprints 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] [docker-traceability-plugin] (JENKINS-28655) Make Docker Traceability tolerant against FingerprintCleanupThread
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28655 Re: Make Docker Traceability tolerant against FingerprintCleanupThread Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityHelper.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityReportListenerImpl.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerDeploymentRefFacet.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerInspectImageFacet.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceFactory.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceJob.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun.java src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceJob/sidepanel.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun/index.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun/main.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun/sidepanel.jelly http://jenkins-ci.org/commit/docker-traceability-plugin/215f719ca9c6f44019b499dac55b22877008014b Log: Merge branch 'JENKINS-28655-handle-cleanup' into JENKINS-28656 Conflicts: src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin.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 http
[JIRA] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28656 Re: Docker Traceability should support the creation of image fingerprints on-demand Code changed in jenkins User: Oleg Nenashev Path: README.md http://jenkins-ci.org/commit/docker-traceability-plugin/103362c5d17a4c38b27c739a71bf6d68327144fb Log: JENKINS-28656 - Update docs 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] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28656 Re: Docker Traceability should support the creation of image fingerprints on-demand Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityHelper.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityReportListenerImpl.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerDeploymentRefFacet.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerInspectImageFacet.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceFactory.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceJob.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun.java src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceJob/sidepanel.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun/index.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun/main.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun/sidepanel.jelly http://jenkins-ci.org/commit/docker-traceability-plugin/215f719ca9c6f44019b499dac55b22877008014b Log: Merge branch 'JENKINS-28655-handle-cleanup' into JENKINS-28656 Conflicts: src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin.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 option
[JIRA] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28656 Docker Traceability should support the creation of image fingerprints on-demand 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] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28656 Re: Docker Traceability should support the creation of image fingerprints on-demand Code changed in jenkins User: Oleg Nenashev Path: README.md src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin.java src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityHelper.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityReportListenerImpl.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerDeploymentRefFacet.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerInspectImageFacet.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceFactory.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceJob.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun.java src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin/config.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/config.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/config.properties src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/help-createImageFingerprints.html src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceJob/sidepanel.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun/index.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun/main.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun/sidepanel.jelly src/test/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginTest.java src/test/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootActionTest.java http://jenkins-ci.org/commit/docker-traceability-plugin/b3a096f564b77ab7aac788272d32c7333ae25a66 Log: Merge branch ' JENKINS-28656 ' into beta2-demo Compare: https://github.com/jenkinsci/docker-traceability-plugin/compare/763590ad54aa^...b3a096f564b7 Add Comment
[JIRA] [docker-traceability-plugin] (JENKINS-28655) Make Docker Traceability tolerant against FingerprintCleanupThread
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28655 Re: Make Docker Traceability tolerant against FingerprintCleanupThread Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin.java src/test/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginTest.java src/test/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootActionTest.java http://jenkins-ci.org/commit/docker-traceability-plugin/f064f58a353a1f8e13c5e55accf88e170490c353 Log: Unit tests for JENKINS-28655 and JENKINS-28656 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] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28656 Re: Docker Traceability should support the creation of image fingerprints on-demand Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin.java src/test/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginTest.java src/test/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootActionTest.java http://jenkins-ci.org/commit/docker-traceability-plugin/f064f58a353a1f8e13c5e55accf88e170490c353 Log: Unit tests for JENKINS-28655 and JENKINS-28656 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] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28656 Re: Docker Traceability should support the creation of image fingerprints on-demand Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityHelper.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityReportListenerImpl.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootAction.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerContainerRecord.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/DockerRecordsRegistry.java src/main/java/org/jenkinsci/plugins/docker/traceability/util/FingerprintsHelper.java src/main/resources/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootAction/_api.jelly src/test/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootActionTest.java src/test/java/org/jenkinsci/plugins/docker/traceability/test/FingerprintTestUtil.java http://jenkins-ci.org/commit/docker-traceability-plugin/72c606de82bfed74b65c671d9dfeff6ac46647f5 Log: Merge commit '5c8ffe9ddfd13a1194adf1ef30d617dc3eb4e734' into JENKINS-28656 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] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28656 Re: Docker Traceability should support the creation of image fingerprints on-demand Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityHelper.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityReportListenerImpl.java http://jenkins-ci.org/commit/docker-traceability-plugin/2ef14ea5a50d76eca3a55b413562a7e3f7424b00 Log: [FIXED JENKINS-28656] - Create image fingerprints on-demand 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] [docker-traceability-plugin] (JENKINS-28655) Make Docker Traceability tolerant against FingerprintCleanupThread
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28655 Re: Make Docker Traceability tolerant against FingerprintCleanupThread Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerEventsListenerImpl.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityHelper.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerDeploymentRefFacet.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerInspectImageFacet.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceFactory.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceJob.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun.java src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceJob/sidepanel.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun/index.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun/main.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun/sidepanel.jelly http://jenkins-ci.org/commit/docker-traceability-plugin/763590ad54aad7d58f96fa3cad99d0b708bcc155 Log: JENKINS-28655 - Skeleton of the docker traceability manager item 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] [docker-traceability-plugin] (JENKINS-28658) Support creation of named container fingerprints
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28658 Re: Support creation of named container fingerprints Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerEventsListenerImpl.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityHelper.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceFactory.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceJob.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceRun.java http://jenkins-ci.org/commit/docker-traceability-plugin/f8bd1916ad977a8b6586a4aa62118c403f48d1a0 Log: [FIXED JENKINS-28658] - Support the creation of named container fingerprints 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] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28656 Re: Docker Traceability should support the creation of image fingerprints on-demand Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin.java src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration.java src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin/config.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/config.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/config.properties src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/help-createImageFingerprints.html http://jenkins-ci.org/commit/docker-traceability-plugin/4cc831ab74dc00ac9182d9382f22073376273929 Log: JENKINS-28656 - DockerTraceabilityPlugin is configurable 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] [docker-traceability-plugin] (JENKINS-28655) Make Docker Traceability tolerant against FingerprintCleanupThread
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28655 Re: Make Docker Traceability tolerant against FingerprintCleanupThread Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceFactory.java src/main/java/org/jenkinsci/plugins/docker/traceability/model/jobs/DockerBuildReferenceJob.java http://jenkins-ci.org/commit/docker-traceability-plugin/2e9ac80b99cf0a07359ae0d1ff4abe76449f3b88 Log: JENKINS-28655 - Create DockerBuildReferenceJob on-demand + javadoc 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] [docker-traceability-plugin] (JENKINS-28663) DockerDeploymentFacet stores records without sorting by date
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28663 Re: DockerDeploymentFacet stores records without sorting by date Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerContainerRecord.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerDeploymentFacet.java http://jenkins-ci.org/commit/docker-traceability-plugin/207e3cc45d89b404cda0922f84e200990d046d5a Log: [FIXED JENKINS-28663] - Fix ordering of events in DockerDeploymentFacet 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] [docker-traceability-plugin] (JENKINS-28663) DockerDeploymentFacet stores records without sorting by date
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28663 Re: DockerDeploymentFacet stores records without sorting by date Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootAction.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerContainerRecord.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerDeploymentFacet.java http://jenkins-ci.org/commit/docker-traceability-plugin/1b03b3358dcc1f4c9b7e75725b6ca2d6aa2a86aa Log: Merge pull request #8 from oleg-nenashev/ JENKINS-28663 [FIXED JENKINS-28663] - Fix ordering of events in DockerDeploymentFacet Compare: https://github.com/jenkinsci/docker-traceability-plugin/compare/5c8ffe9ddfd1...1b03b3358dcc 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] [docker-traceability-plugin] (JENKINS-28663) DockerDeploymentFacet stores records without sorting by date
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28663 DockerDeploymentFacet stores records without sorting by date 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] [docker-build-publish-plugin] (JENKINS-28675) Create Docker image fingerprints after the build
Title: Message Title Oleg Nenashev started work on JENKINS-28675 Change By: Oleg Nenashev 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] [docker-build-publish-plugin] (JENKINS-28675) Create Docker image fingerprints after the build
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-28675 Create Docker image fingerprints after the build Change By: Oleg Nenashev Assignee: Michael Neale Oleg Nenashev 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-agent-plugin] (JENKINS-27555) ssh-agent plugin leaking file descriptors leaving behind jenkinsXXXXXX.jnr socket files
Title: Message Title Yoann Dubreuil commented on JENKINS-27555 Re: ssh-agent plugin leaking file descriptors leaving behind jenkinsXX.jnr socket files Current implementation uses accept() native call which is blocking current thread while waiting for client requests. At the end of a build, accept() can't be unblocked and the thread is leaked. accept() should only be called when there's a request waiting to be served. I've just proposed PR-3 to fix 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] [email-ext-plugin] (JENKINS-28682) Fails to connect SMTP server with Success trigger
Title: Message Title Alex Earl commented on JENKINS-28682 Re: Fails to connect SMTP server with Success trigger Please upload passing and failing case build logs and your configuration xml files. 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] [mstest-plugin] (JENKINS-28517) [MSTEST] XML coverage report file not found
Title: Message Title Ivo Bellin Salarin commented on JENKINS-28517 Re: [MSTEST] XML coverage report file not found Any news? 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] [email-ext-plugin] (JENKINS-28682) Fails to connect SMTP server with Success trigger
Title: Message Title Jose Munoz updated an issue Jenkins / JENKINS-28682 Fails to connect SMTP server with Success trigger Change By: Jose Munoz I have configured Extended Mail Notification to be send emails on Failure and Success.The proper notification is sent on Failure. But the notification on Success is not sent.I repeated the operations with Debug mode and I have noticed that the failure happens when trying to connect to the configured SMTP. The odd part is that the connection fails only when the trigger is on Success.When the build failed, I can see the next in the log:DEBUG SMTP: trying to connect to host "mail.foo.com", port 25, isSSL false220 Mail. CycleGear foo .com Kerio Connect 8.5.0 ESMTP readyDEBUG SMTP: connected to host "mail.foo.com", port: 25When the build succeeded, I see the next in the log:DEBUG SMTP: useEhlo true, useAuth falseDEBUG SMTP: trying to connect to host "mail.foo.com", port 25, isSSL falseMessagingException message: Unknown SMTP host: mail.foo.comThere is no more information provided when it tries to send the notification on success.I have tried changing the trigger to Always and the results are the same.I would expect that if this is a configuration error or a port issue, neither of the notification be sent. But they are sent on Failure every 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...@go
[JIRA] [email-ext-plugin] (JENKINS-28682) Fails to connect SMTP server with Success trigger
Title: Message Title Jose Munoz created an issue Jenkins / JENKINS-28682 Fails to connect SMTP server with Success trigger Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 01/Jun/15 8:08 PM Environment: OS Centos 6.5 Jenkins 1.615 email-ext-plugin 2.40.4 Priority: Minor Reporter: Jose Munoz I have configured Extended Mail Notification to be send emails on Failure and Success. The proper notification is sent on Failure. But the notification on Success is not sent. I repeated the operations with Debug mode and I have noticed that the failure happens when trying to connect to the configured SMTP. The odd part is that the connection fails only when the trigger is on Success. When the build failed, I can see the next in the log: DEBUG SMTP: trying to connect to host "mail.foo.com", port 25, isSSL false 220 Mail.CycleGear.com Kerio Connect 8.5.0 ESMTP ready DEBUG SMTP: connected to host "mail.foo.com", port: 25 When the build succeeded, I see the next in the log: DEBUG SMTP: useEhlo true, useAuth false DEBUG SMTP: trying to connect to host "mail.foo.com", port 25, isSSL false MessagingException mes
[JIRA] [matrix-project-plugin] (JENKINS-28681) mercurial-plugin doesn't work if matrix-project-plugin plugin is disabled
Title: Message Title spong man created an issue Jenkins / JENKINS-28681 mercurial-plugin doesn't work if matrix-project-plugin plugin is disabled Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin, mercurial-plugin Created: 01/Jun/15 7:49 PM Environment: Jenkins ver. 1.616 mercurial-plugin 1.52 matrix-project-plugin 1.2 Priority: Major Reporter: spong man if matrix-project-plugin is disabled in the the /pluginManager/installed page, then mercurial doesn't appear in the 'Source Code Management' section of the job's configuration page. Add Comment
[JIRA] [delivery-pipeline-plugin] (JENKINS-28619) Join Plugin & Delivery Pipeline Plugin: View logs warnings about existing downstream projects
Title: Message Title Patrik Boström closed an issue as Fixed Released in 0.9.2 Jenkins / JENKINS-28619 Join Plugin & Delivery Pipeline Plugin: View logs warnings about existing downstream projects Change By: Patrik Boström Status: Resolved Closed 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] [cmakebuilder-plugin] (JENKINS-27203) Broken env variable replacing
Title: Message Title Martin Weber commented on JENKINS-27203 Re: Broken env variable replacing hudson.Util.replaceMacro(String, Map) does what you need 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] [email-ext-plugin] (JENKINS-28680) Email Extension Plugin throwing a NullPointerException at startup
Title: Message Title Alex Earl commented on JENKINS-28680 Re: Email Extension Plugin throwing a NullPointerException at startup Also, are you sure you are on 2.40.4? I fixed an issue in 2.40.4 that was causing this. If you upgraded the plugin, did you restart Jenkins? 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] [email-ext-plugin] (JENKINS-28680) Email Extension Plugin throwing a NullPointerException at startup
Title: Message Title Alex Earl commented on JENKINS-28680 Re: Email Extension Plugin throwing a NullPointerException at startup Please attach the file in the exception. 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-14189) Discover permission gives Status Code 500 and Stacktrace
Title: Message Title jim jaeger updated an issue Jenkins / JENKINS-14189 Discover permission gives Status Code 500 and Stacktrace Change By: jim jaeger Attachment: $4393A05BF40BFD7D.bmp 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-14189) Discover permission gives Status Code 500 and Stacktrace
Title: Message Title jim jaeger commented on JENKINS-14189 Re: Discover permission gives Status Code 500 and Stacktrace — removed javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/srv/tomcat6/webapps/jenkins/WEB-INF/lib/jenkins-core-1.615.jar!/hudson/model/View/index.jelly:42:43: org.apache.commons.jelly.JellyTagException: jar:file:/srv/tomcat6/webapps/jenkins/WEB-INF/lib/jenkins-core-1.615.jar!/lib/hudson/projectView.jelly:67:24: Please login to access job — removed at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:813) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) 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-14189) Discover permission gives Status Code 500 and Stacktrace
Title: Message Title jim jaeger reopened an issue The issue occurs again. Jenkins ver. 1.615 Jenkins / JENKINS-14189 Discover permission gives Status Code 500 and Stacktrace Change By: jim jaeger Resolution: Fixed Status: Closed Reopened 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] [email-ext-plugin] (JENKINS-28680) Email Extension Plugin throwing a NullPointerException at startup
Title: Message Title jim jaeger created an issue Jenkins / JENKINS-28680 Email Extension Plugin throwing a NullPointerException at startup Issue Type: Bug Assignee: Alex Earl Attachments: catalina.out Components: email-ext-plugin Created: 01/Jun/15 6:14 PM Environment: Linux 64bit, Jenkins ver. 1.615, Plugin Version 2.40.4 Priority: Critical Reporter: jim jaeger Nullpointer during Jenkins startup caused by Email Extension Plugin java.io.IOException: Unable to read /opt/jenkins/hudson.plugins.emailext.ExtendedEmailPublisher.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at hudson.model.Descriptor.load(Descriptor.java:783) at hudson.plugins.emailext.ExtendedEmailPublisherDescriptor.(ExtendedEmailPublisherDescriptor.java:344) at hudson.plugins.emailext.ExtendedEmailPublisherDescriptor$$FastClassByGuice$$5dfa54d0.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructi
[JIRA] [core] (JENKINS-28676) Viewing archived files with UTF8 text shows garbled output
Title: Message Title
Leon Blakey edited a comment on JENKINS-28676
Re: Viewing archived files with UTF8 text shows garbled output
See below (didn't see a way to attach a file) {{ System PropertiesName ↓ Value user.timezone America/New_Yorkuser.name jenkinsuser.language enuser.home /var/lib/jenkinsuser.dir /user.country USsun.os.patch.level unknownsun.management.compiler HotSpot 64-Bit Tiered Compilerssun.jnu.encoding UTF-8sun.java.launcher SUN_STANDARDsun.java.command /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1sun.io.unicode.encoding UnicodeLittlesun.font.fontmanager sun.awt.X11FontManagersun.cpu.isalist sun.cpu.endian littlesun.boot.library.path /opt/java-build/jdk1.8.0_40_x64/jre/lib/amd64sun.boot.class.path /opt/java-build/jdk1.8.0_40_x64/jre/lib/resources.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/rt.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/sunrsasign.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/jsse.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/jce.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/charsets.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/jfr.jar:/opt/java-build/jdk1.8.0_40_x64/jre/classessun.arch.data.model 64securerandom.source file:/dev/./urandompath.separator :os.version 3.13.0-53-genericos.name Linuxos.arch amd64mail.smtps.sendpartial truemail.smtp.sendpartial trueline.separator lib.svnkit.ssh2.persistent falselib.svnkit.http.methods Digest,Basic,NTLM,Negotiatejnidispatch.path /tmp/jna--1712433994/jna3590656383749624890.tmpjna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/libjava.vm.version 25.40-b25java.vm.vendor Oracle Corporationjava.vm.specification.version 1.8java.vm.specification.vendor Oracle Corporationjava.vm.specification.name Java Virtual Machine Specificationjava.vm.name Java HotSpot(TM) 64-Bit Server VMjava.vm.info mixed modejava.version 1.8.0_40java.vendor.url.bug http://bugreport.sun.com/bugreport/java.vendor.url http://java.oracle.com/java.vendor Oracle Corporationjava.specification.version 1.8java.specification.vendor Oracle Corporationjava.specification.name Java Platform API Specificationjava.runtime.version 1.8.0_40-b26java.runtime.name Java(TM) SE Runtime Environmentjava.rmi.server.randomIDs truejava.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/libjava.io.tmpdir /tmpjava.home /opt/java-build/jdk1.8.0_40_x64/jrejava.ext.dirs /opt/java-build/jdk1.8.0_40_x64/jre/lib/ext:/usr/java/packages/lib/extjava.endorsed.dirs /opt/java-build/jdk1.8.0_40_x64/jre/lib/endorsedjava.class.version 52.0java.class.path /usr/share/jenkins/jenkins.warjava.awt.printerjob sun.print.PSPrinterJobjava.awt.headless truejava.awt.graphicsenv sun.awt.X11GraphicsEnvironmenthudson.diyChunking trueguice.disable.misplaced.annotation.check truefile.separator /file.encoding.pkg sun.iofile.encoding UTF-8executable-war /usr/share/jenkins/jenkins.warcom.sun.management.jmxremote.ssl falsecom.sun.management.jmxremote.port com.sun.management.jmxremote.authenticate falseawt.toolkit sun.awt.X11.XToolkitEnvironment VariablesName ↓ Value XFILESEARCHPATH /usr/dt/app-defaults/%L/DtXDG_SESSION_ID 13XDG_RUNTIME_DIR /run/user/0USER jenkinsTERM screenSHLVL 1SHELL /bin/bashPWD /var/lib/jenkinsPATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/lib/jvm/java-6-oracle/bin:/usr/lib/jvm/java-6-oracle/db/bin:/usr/lib/jvm/java-6-oracle/jre/bin:/opt/dell/srvadmin/binNLSPATH /usr/dt/lib/nls/msg/%L/%N.catMAIL /var/mail/jenkinsLOGNAME jenkinsLANG en_US.UTF-8JENKINS_HOME /var/lib/jenkinsJAVA_HOME /usr/lib/jvm/java-6-oracleJ2SDKDIR /usr/lib/jvm/java-6-oracleJ2REDIR /usr/lib/jvm/java-6-oracle/jreHOME /var/lib/jenkinsDERBY_HOME /usr/lib/jvm/java-6-oracle/db_ /usr/bin/daemonPluginsName ↓ Version Enabled Pinned xvnc 1.21 true falsews-cleanup 0.26 true falsewindows-slaves 1.0 true falsewarnings 4.47 true falsetranslation 1.12 true truetoken-macro 1.10 tr
[JIRA] [core] (JENKINS-28676) Viewing archived files with UTF8 text shows garbled output
Title: Message Title
Leon Blakey edited a comment on JENKINS-28676
Re: Viewing archived files with UTF8 text shows garbled output
See below (didn't see a way to attach a file) {{ System PropertiesName ↓ Value user.timezone America/New_Yorkuser.name jenkinsuser.language enuser.home /var/lib/jenkinsuser.dir /user.country USsun.os.patch.level unknownsun.management.compiler HotSpot 64-Bit Tiered Compilerssun.jnu.encoding UTF-8sun.java.launcher SUN_STANDARDsun.java.command /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1sun.io.unicode.encoding UnicodeLittlesun.font.fontmanager sun.awt.X11FontManagersun.cpu.isalist sun.cpu.endian littlesun.boot.library.path /opt/java-build/jdk1.8.0_40_x64/jre/lib/amd64sun.boot.class.path /opt/java-build/jdk1.8.0_40_x64/jre/lib/resources.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/rt.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/sunrsasign.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/jsse.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/jce.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/charsets.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/jfr.jar:/opt/java-build/jdk1.8.0_40_x64/jre/classessun.arch.data.model 64securerandom.source file:/dev/./urandompath.separator :os.version 3.13.0-53-genericos.name Linuxos.arch amd64mail.smtps.sendpartial truemail.smtp.sendpartial trueline.separator lib.svnkit.ssh2.persistent falselib.svnkit.http.methods Digest,Basic,NTLM,Negotiatejnidispatch.path /tmp/jna--1712433994/jna3590656383749624890.tmpjna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/libjava.vm.version 25.40-b25java.vm.vendor Oracle Corporationjava.vm.specification.version 1.8java.vm.specification.vendor Oracle Corporationjava.vm.specification.name Java Virtual Machine Specificationjava.vm.name Java HotSpot(TM) 64-Bit Server VMjava.vm.info mixed modejava.version 1.8.0_40java.vendor.url.bug http://bugreport.sun.com/bugreport/java.vendor.url http://java.oracle.com/java.vendor Oracle Corporationjava.specification.version 1.8java.specification.vendor Oracle Corporationjava.specification.name Java Platform API Specificationjava.runtime.version 1.8.0_40-b26java.runtime.name Java(TM) SE Runtime Environmentjava.rmi.server.randomIDs truejava.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/libjava.io.tmpdir /tmpjava.home /opt/java-build/jdk1.8.0_40_x64/jrejava.ext.dirs /opt/java-build/jdk1.8.0_40_x64/jre/lib/ext:/usr/java/packages/lib/extjava.endorsed.dirs /opt/java-build/jdk1.8.0_40_x64/jre/lib/endorsedjava.class.version 52.0java.class.path /usr/share/jenkins/jenkins.warjava.awt.printerjob sun.print.PSPrinterJobjava.awt.headless truejava.awt.graphicsenv sun.awt.X11GraphicsEnvironmenthudson.diyChunking trueguice.disable.misplaced.annotation.check truefile.separator /file.encoding.pkg sun.iofile.encoding UTF-8executable-war /usr/share/jenkins/jenkins.warcom.sun.management.jmxremote.ssl falsecom.sun.management.jmxremote.port com.sun.management.jmxremote.authenticate falseawt.toolkit sun.awt.X11.XToolkitEnvironment VariablesName ↓ Value XFILESEARCHPATH /usr/dt/app-defaults/%L/DtXDG_SESSION_ID 13XDG_RUNTIME_DIR /run/user/0USER jenkinsTERM screenSHLVL 1SHELL /bin/bashPWD /var/lib/jenkinsPATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/lib/jvm/java-6-oracle/bin:/usr/lib/jvm/java-6-oracle/db/bin:/usr/lib/jvm/java-6-oracle/jre/bin:/opt/dell/srvadmin/binNLSPATH /usr/dt/lib/nls/msg/%L/%N.catMAIL /var/mail/jenkinsLOGNAME jenkinsLANG en_US.UTF-8JENKINS_HOME /var/lib/jenkinsJAVA_HOME /usr/lib/jvm/java-6-oracleJ2SDKDIR /usr/lib/jvm/java-6-oracleJ2REDIR /usr/lib/jvm/java-6-oracle/jreHOME /var/lib/jenkinsDERBY_HOME /usr/lib/jvm/java-6-oracle/db_ /usr/bin/daemonPluginsName ↓ Version Enabled Pinned xvnc 1.21 true falsews-cleanup 0.26 true falsewindows-slaves 1.0 true falsewarnings 4.47 true falsetranslation 1.12 true truetoken-macro 1.10 tr
[JIRA] [core] (JENKINS-28676) Viewing archived files with UTF8 text shows garbled output
Title: Message Title Leon Blakey commented on JENKINS-28676 Re: Viewing archived files with UTF8 text shows garbled output See below (didn't see a way to attach a file) System Properties Name ↓ Value user.timezone America/New_York user.name jenkins user.language en user.home /var/lib/jenkins user.dir / user.country US sun.os.patch.level unknown sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.jnu.encoding UTF-8 sun.java.launcher SUN_STANDARD sun.java.command /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 sun.io.unicode.encoding UnicodeLittle sun.font.fontmanager sun.awt.X11FontManager sun.cpu.isalist sun.cpu.endian little sun.boot.library.path /opt/java-build/jdk1.8.0_40_x64/jre/lib/amd64 sun.boot.class.path /opt/java-build/jdk1.8.0_40_x64/jre/lib/resources.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/rt.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/sunrsasign.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/jsse.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/jce.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/charsets.jar:/opt/java-build/jdk1.8.0_40_x64/jre/lib/jfr.jar:/opt/java-build/jdk1.8.0_40_x64/jre/classes sun.arch.data.model 64 securerandom.source file:/dev/./urandom path.separator : os.version 3.13.0-53-generic os.name Linux os.arch amd64 mail.smtps.sendpartial true mail.smtp.sendpartial true line.separator lib.svnkit.ssh2.persistent false lib.svnkit.http.methods Digest,Basic,NTLM,Negotiate jnidispatch.path /tmp/jna--1712433994/jna3590656383749624890.tmp jna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib java.vm.version 25.40-b25 java.vm.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.specification.vendor Oracle Corporation java.vm.specification.name Java Virtual Machine Specification java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.info mixed mode java.version 1.8.0_40 java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.vendor.url http://java.oracle.com/ java.vendor Oracle Corporation java.specification.version 1.8 java.specification.vendor Oracle Corporation java.specification.name Java Platform API Specification java.runtime.version 1.8.0_40-b26 java.runtime.name Java(TM) SE Runtime Environment java.rmi.server.randomIDs true java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.io.tmpdir /tmp java.home /opt/java-build/jdk1.8.0_40_x64/jre java.ext.dirs /opt/java-build/jdk1.8.0_40_x64/jre/lib/ext:/usr/java/packages/lib/ext java.endorsed.dirs /opt/java-build/jdk1.8.0_40_x64/jre/lib/endorsed java.class.version 52.0 java.class.path /usr/share/jenkins/jenkins.war java.awt.printerjob sun.print.PSPrinterJob java.awt.headless true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment hudson.diyChunking true guice.disable.misplaced.annotation.check true file.separator / file.encoding.pkg sun.io file.encoding UTF-8 executable-war /usr/share/jenkins/jenkins.war com.sun.management.jmxremote.ssl false com.sun.management.jmxremote.port com.sun.management.jmxremote.authenticate false awt.toolkit sun.awt.X11.XToolkit Environment Variables Name ↓ Value XFILESEARCHPATH /usr/dt/app-defaults/%L/Dt XDG_SESSION_ID 13 XDG_RUNTIME_DIR /run/user/0 USER jenkins TERM screen SHLVL 1 SHELL /bin/bash PWD /var/lib/jenkins PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/lib/jvm/java-6-oracle/bin:/usr/lib/jvm/java-6-oracle/db/bin:/usr/lib/jvm/java-6-oracle/jre/bin:/opt/dell/srvadmin/bin NLSPATH /usr/dt/lib/nls/msg/%L/%N.cat MAIL /var/mail/jenkins LOGNAME jenkins LANG en_US.UTF-8 JENKINS_HOME /var/lib/jenkins JAVA_HOME /usr/lib/jvm/java-6-oracle J2SDKDIR /usr/lib/jvm/java-6-oracle J2REDIR /usr/lib/jvm/java-6-oracle/jre HOME /var/lib/je
[JIRA] [core] (JENKINS-28676) Viewing archived files with UTF8 text shows garbled output
Title: Message Title Daniel Beck commented on JENKINS-28676 Re: Viewing archived files with UTF8 text shows garbled output Please provide contents of the /systemInfo Jenkins URL. 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] [msbuild-plugin] (JENKINS-28679) msbuild plugin expects a path to msbuild.exe, but shows a warning if you specify it
Title: Message Title spong man updated an issue Jenkins / JENKINS-28679 msbuild plugin expects a path to msbuild.exe, but shows a warning if you specify it Change By: spong man Environment: Jenkins ver. 1.615msbuild -plugin 1.24 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] [msbuild-plugin] (JENKINS-28679) msbuild plugin expects a path to msbuild.exe, but shows a warning if you specify it
Title: Message Title spong man created an issue Jenkins / JENKINS-28679 msbuild plugin expects a path to msbuild.exe, but shows a warning if you specify it Issue Type: Bug Assignee: kdsweeney Components: msbuild-plugin Created: 01/Jun/15 5:51 PM Environment: Jenkins ver. 1.615 msbuild 1.24 Priority: Major Reporter: spong man in the msbuild system config section where you specify the msbuild installations, the "Path to MSBuild" textbox expects a directory (eg C:\windows\Microsoft.NET\Framework\v4.0.30319). if you specify the full path to msbuild.exe (eg C:\windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe) it shows a warning: C:\windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe is not a directory on the Jenkins master (but perhaps it exists on some slaves) however, if you omit the \msbuild.exe suffix, then builds fail with the following error: 'C:\windows\Microsoft.NET\Framework\v4.0.30319' is not recognized as an internal or external command, operable program or batch file. so, either:
[JIRA] [workflow-plugin] (JENKINS-28678) Snippet Generator Missing Parameter Syntax for "Build a Job"
Title: Message Title David Schott created an issue Jenkins / JENKINS-28678 Snippet Generator Missing Parameter Syntax for "Build a Job" Issue Type: Bug Assignee: Jesse Glick Attachments: Screen Shot 2015-06-01 at 12.11.17 PM.png Components: workflow-plugin Created: 01/Jun/15 5:47 PM Environment: 1.609 Labels: workflow Priority: Minor Reporter: David Schott See screenshot.
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Title: Message Title Daniel Beck commented on JENKINS-25370 Re: H in schedule does not work properly for minutes If I want it once an hour I have to define: "H/1 * * * *" what reads as execute every minute, but this way the job runs once an hour as I'd never expected. Execute every hour: H * * * * Execute every minute: * * * * * Not sure what the real problem here is. Maybe 'H/1' should be interpreted as '*' rather than 'H'? Will take a closer look at the others you mentioned. 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-28644) Trigger job when polling off if sha1 specified in push notification
Title: Message Title Leif Gruenwoldt updated an issue Jenkins / JENKINS-28644 Trigger job when polling off if sha1 specified in push notification Change By: Leif Gruenwoldt The documentation suggests that polling is not required when the "sha1" commitID param is given, so should it not be possible to trigger a build this way with polling turned off for the job? From testing it appears polling is still required in this case too."Commit ID is optional. If set, it will immediately trigger a build, without requirement to poll for changes."I have > 100 Jenkins jobs I'd like to migrate to this style post-receive job trigger however having to modify the job configuration in this way for eachone each one sounds like a very long afternoon. 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] [docker-build-publish-plugin] (JENKINS-28677) Use Docker tool Installations from Docker commons
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28677 Use Docker tool Installations from Docker commons Issue Type: New Feature Assignee: Michael Neale Components: docker-build-publish-plugin Created: 01/Jun/15 4:37 PM Priority: Minor Reporter: Oleg Nenashev Several platforms (like Mac + docker from homebrew) do not provide docker by default in the environment. It would be useful to have the Docker installation path configurable. Add Comment
[JIRA] [core] (JENKINS-28676) Viewing archived files with UTF8 text shows garbled output
Title: Message Title Leon Blakey created an issue Jenkins / JENKINS-28676 Viewing archived files with UTF8 text shows garbled output Issue Type: Bug Assignee: Unassigned Components: core Created: 01/Jun/15 4:34 PM Environment: Jenkins 1.616 Server: Ubuntu 14.04.2 LTS Browser: Firefox, Chrome, or IE on both Windows 7 and Debian Linux Labels: encoding Priority: Minor Reporter: Leon Blakey Steps to reproduce 1) Run a job that will archive a text file with UTF8 text 2) On the job page under build artifacts view that file In my case on all major browsers on multiple OS's on different machines I get this when viewing the file through Jenkins: â ⠓⠑⠊⠣⠞⠀â â ⠃⠧⠀â â Žâ ‘â â €â ⠇⠑⠧⠑⠇ instead of this (UTF8 braille) when viewing the file directly from the filesystem in a text editor ⠠⠓⠑⠊⠣⠞⠀⠠⠁⠃⠧⠀⠠⠎⠑⠁⠀⠠⠇⠑⠧⠑⠇
[JIRA] [core] (JENKINS-23147) Jenkins won't restart itself through the GUI
Title: Message Title
Kevin Phillips edited a comment on JENKINS-23147
Re: Jenkins won't restart itself through the GUI
I have reproduced this same problem in the latest LTS edition (1.596.3 atm) on a clean Windows 7 x64 OS as well. I'm using Java 64bit v1.7.0_80-b15 in case that is a factor.I've tried setting up the Jenkins service to run under the local system account as well as a local administrative user and neither setting works correctly.I have confirmed that the command line interface for the service, jenkins.exe, does correctly control the Windows service. Performing "jenkins start", "jenkins stop", "jenkins restart", "jenkins uninstall" and "jenkins install" all work correctly when run from a command prompt using the same local user profile the service runs within.I have also tried explicitly adding WMI permissions to all relevant users / groups as well using the process found [here|https://technet.microsoft.com/en-us/library/cc771551.aspx] in case this was some kind of security problem but that had no effect either.Finally, unlike the description above and other defects in the issue tracker like JENKINS-23395 and JENKINS-22685, I see no errors or warnings of any kind related to the service reboot. In fact the only reference to the reboot request at all in any of the logs is this short snippet I found in the jenkins.err.log file:{panel}Jun 01, 2015 12:10:43 PM jenkins.model.Jenkins$22 runSEVERE: Restarting VM as requested by anonymous{panel}If I try performing a "safe restart" (ie: http://jenkins/safeRestart), the results are the same but I get a couple of extra lines in the error log as shown below:{panel}May 26, 2015 8:41:05 AM hudson.model.UpdateCenter doSafeRestartINFO: Scheduling Jenkins rebootMay 26, 2015 8:41:05 AM jenkins.model.Jenkins$23 runINFO: Restart in 10 secondsMay 26, 2015 8:41:15 AM jenkins.model.Jenkins$23 runSEVERE: Restarting VM as requested by anonymous{panel}Also, after requesting the reboot, say via the http://jenkins/reboot REST call, the application does mark itself as "preparing for shutdown" but since the reboot never actually happens the service stays in this intermediate state indefinitely. You basically have to log into the server and manually for the service to restart.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-23147) Jenkins won't restart itself through the GUI
Title: Message Title Kevin Phillips commented on JENKINS-23147 Re: Jenkins won't restart itself through the GUI One other strategy I tried to work around this issue was to move the Jenkins installation folder to different locations, thinking that maybe putting it under Program Files may have caused some permission issues or something. However even if I relocate the folder to a new folder off the root partition (ie: c:\jenkins ) the same behavior ensues. I only mention it here just in case this helps isolate the cause of the problem. 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-23147) Jenkins won't restart itself through the GUI
Title: Message Title Kevin Phillips commented on JENKINS-23147 Re: Jenkins won't restart itself through the GUI I have reproduced this same problem in the latest LTS edition (1.596.3 atm) on a clean Windows 7 x64 OS as well. I'm using Java 64bit v1.7.0_80-b15 in case that is a factor. I've tried setting up the Jenkins service to run under the local system account as well as a local administrative user and neither setting works correctly. I have confirmed that the command line interface for the service, jenkins.exe, does correctly control the Windows service. Performing "jenkins start", "jenkins stop", "jenkins restart", "jenkins uninstall" and "jenkins install" all work correctly when run from a command prompt using the same local user profile the service runs within. I have also tried explicitly adding WMI permissions to all relevant users / groups as well using the process found here in case this was some kind of security problem but that had no effect either. Finally, unlike other defects in the issue tracker like JENKINS-23395 and JENKINS-22685 , I see no errors or warnings of any kind related to the service reboot. In fact the only reference to the reboot request at all in any of the logs is this short snippet I found in the jenkins.err.log file: Jun 01, 2015 12:10:43 PM jenkins.model.Jenkins$22 run SEVERE: Restarting VM as requested by anonymous If I try performing a "safe restart" (ie: http://jenkins/safeRestart), the results are the same but I get a couple of extra lines in the error log as shown below: May 26, 2015 8:41:05 AM hudson.model.UpdateCenter doSafeRestart INFO: Scheduling Jenkins reboot May 26, 2015 8:41:05 AM jenkins.model.Jenkins$23 run INFO: Restart in 10 seconds May 26, 2015 8:41:15 AM jenkins.model.Jenkins$23 run SEVERE: Restarting VM as requested by anonymous Also, after requesting the reboot, say via the http://jenkins/reboot REST call, the application does mark itself as "preparing for shutdown" but since the reboot never actually happens the service stays in this intermediate state indefinitely. You basically have to log into the server and manually for the service to restart. Add Comment
hi
Attn: Dear Winner. We are pleased to inform you of the result of the Euro millions Lottery Winners,an International E-mail program held on the 27th of April. 2015. Your E-mail address fall to the ticket number 653-908-321-675 with serial main number 345-790-241-671 drew lucky star numbers 34-32-90-43-32 which consequently won in the 2nd category of this program, you have therefore been approved for a lump sum pay out of €2.800.000.00 Euro.(Two Million Eight Hundred Thousand Euros) Your fund is now deposited with our paying Center – VITALICIO SEGUROS MADRID SPAIN.So you are advice to contact Dr. Smeets Freddy the President, Of Vitalicio Seguros Madrid Spain with the following informations to enable him to direct you on how you will receive your wining price. Your Agent Contact Informations.Dr. Smeets FreddyTEL : 0034 602 886 080, FAX : 00 34-917-903-844, Email : vitalicioseguros@qualityservice.comAfter this date all unclaimed funds will be included in the next stake.Please note in order to avoid unnecessary delays and complications please remember to quote your reference number and batch numbers in all correspondence. Congratulations once more from our members of staff and thank you for being part of our promotional program.Sincerely yours,Mrs Maria Leon Lopez.Lottery Coordinator. -- 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] [docker-build-publish-plugin] (JENKINS-28675) Create Docker image fingerprints after the build
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28675 Create Docker image fingerprints after the build Change By: Oleg Nenashev Docker Commons allows to create fingerprints, which may be reused in other plugins. It would be great to create such fingerprints when we create a new image in docker-build-publish 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] [docker-build-publish-plugin] (JENKINS-28675) Create Docker image fingerprints after the build
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28675 Create Docker image fingerprints after the build Issue Type: New Feature Assignee: Michael Neale Components: docker-build-publish-plugin Created: 01/Jun/15 3:50 PM Priority: Major Reporter: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscri
[JIRA] [script-security-plugin] (JENKINS-28586) Method access/properties inside Closure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28586 Re: Method access/properties inside Closure Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/resources/org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists/generic-whitelist src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SandboxInterceptorTest.java http://jenkins-ci.org/commit/script-security-plugin/50240737226721be75e913a70c5ad289975942cd Log: Merge pull request #13 from jenkinsci/ JENKINS-28586 [FIXED JENKINS-28586] handle method calls/property accesses via closure Compare: https://github.com/jenkinsci/script-security-plugin/compare/c6d43e762aa8...502407372267 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] [script-security-plugin] (JENKINS-28586) Method access/properties inside Closure
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28586 Method access/properties inside Closure 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] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
Title: Message Title kutzi commented on JENKINS-28175 Re: config change deadlock Jenkins when pircx.shutdown() is invoked Antoine, any chance you can try the unreleased IRC 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] [pretested-integration-plugin] (JENKINS-28590) Author of last commit becomes the author of the integration commit (Praqma case 13102)
Title: Message Title Bue Petersen updated an issue Jenkins / JENKINS-28590 Author of last commit becomes the author of the integration commit (Praqma case 13102) Change By: Bue Petersen Summary: Author of last commit becomes the author of the integration commit (Praqma case 13072 13102 ) 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] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title kutzi commented on JENKINS-28626 Re: IRC notification results in need to restart Jenkins Seems like this is a bug in PircBotX 1.9 which was fixed in 2.0 (see changelog: https://code.google.com/p/pircbotx/wiki/ChangeLog) You might want to try the unreleased version of the IRC plugin which already uses PircBotx 2.0 https://dl.dropboxusercontent.com/u/25863594/ircbot.hpi 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] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title
kutzi commented on JENKINS-28626
Re: IRC notification results in need to restart Jenkins
Yes, that looks like a bug in the IRC plugin, but I fail to see how the plugin caused Jenkins to shut down. The order in the log file is, that there's an info that the JVM is shutting down ('INFO: JVM is terminating. Shutting down Winstone') and only after that the irc plugin logs an exception.
Do you have additional logs which show how the irc plugin causes the Jenkins shutdown and/or do you have instructions on how to reproduce the issue?
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] [slack-plugin] (JENKINS-27985) Slack post may have failed. Response: Private integrations can't post to public channels
Title: Message Title Matthew Conte commented on JENKINS-27985 Re: Slack post may have failed. Response: Private integrations can't post to public channels Yes, that was indeed the issue. I had my Admin create a public integration for my team to post to public channels on Jenkins events. Thank 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] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title windows refund commented on JENKINS-28626 Re: IRC notification results in need to restart Jenkins May 28, 2015 2:11:49 PM winstone.Logger logInternal INFO: JVM is terminating. Shutting down Winstone 1432836709212 ### Your implementation of PircBotX is faulty and you have 1432836709212 ### allowed an uncaught Exception or Error to propagate in your 1432836709212 ### code. It may be possible for PircBotX to continue operating 1432836709212 ### normally. Here is the stack trace that was produced: - 1432836709212 ### 1432836709212 ### java.lang.UnsupportedOperationException: The method shutdownInput() is not supported in SSLSocket 1432836709212 ### at sun.security.ssl.BaseSSLSocketImpl.shutdownInput(BaseSSLSocketImpl.java:199) 1432836709212 ### at org.pircbotx.PircBotX.shutdown(PircBotX.java:2855) 1432836709212 ### at org.pircbotx.PircBotX$4.run(PircBotX.java:2817) 1432836709212 >>>QUIT : 1432836709213 *** Disconnected. 1432836709219 <<[Quit: ] 1432836709219 ### Your implementation of PircBotX is faulty and you have 1432836709219 ### allowed an uncaught Exception or Error to propagate in your 1432836709219 ### code. It may be possible for PircBotX to continue operating 1432836709219 ### normally. Here is the stack trace that was produced: - 1432836709219 ### 1432836709219 ### java.lang.UnsupportedOperationException: The method shutdownInput() is not supported in SSLSocket 1432836709219 ### at sun.security.ssl.BaseSSLSocketImpl.shutdownInput(BaseSSLSocketImpl.java:199) 1432836709219 ### at org.pircbotx.PircBotX.shutdown(PircBotX.java:2855) 1432836709219 ### at org.pircbotx.PircBotX.handleLine(PircBotX.java:1679) 1432836709219 ### at org.pircbotx.InputThread.run(InputThread.java:100) 1432836709219 *** Disconnected. 1432836710243 ### Your implementation of PircBotX is faulty and you have 1432836710243 ### allowed an uncaught Exception or Error to propagate in your 1432836710243 ### code. It may be possible for PircBotX to continue operating 1432836710243 ### normally. Here is the stack trace that was produced: - 1432836710243 ### 1432836710243 ### java.lang.UnsupportedOperationException: The method shutdownInput() is not supported in SSLSocket 1432836710243 ### at sun.security.ssl.BaseSSLSocketImpl.shutdownInput(BaseSSLSocketImpl.java:199) 1432836710243 ### at org.pircbotx.PircBotX.shutdown(PircBotX.java:2855) 1432836710243 ### at hudson.plugins.ircbot.v2.IRCConnection.close(IRCConnection.java:102) 1432836710243 ### at hudson.plugins.im.IMConnectionProvider.releaseConnection(IMConnectionProvider.java:86) 1432836710243 ### at hudson.plugins.im.IMPlugin.stop(IMPlugin.java:20) 1432836710243 ### at hudson.plugins.ircbot.PluginImpl.stop(PluginImpl.java:35) 1432836710243 ### at hudson.PluginWrapper.stop(PluginWrapper.java:375) 1432836710243 ### at hudson.PluginManager.stop(PluginManager.java:738) 1432836710243 ### at jenkins.model.Jenkins.cleanUp(Jenkins.java:2796) 1432836710243 ### at hudson.WebAppMain.contextDestroyed(WebAppMain.java:397) 1432836710243 ### at org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:823) 1432836710243 ### at org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:160) 1432836710243 ### at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:518) 1432836710243 ### at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) 1432836710243 ### at org.eclipse.jetty.server.handler.HandlerWrapper.doStop(HandlerWrapper.java:107) 1432836710243 ### at org.eclipse.jetty.server.handler.RequestLogHandler.doStop(RequestLogHandler.java:176) 1432836710243 ### at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) 1432836710243 ### at org.eclipse.jetty.server.handler.HandlerWrapper.doStop(HandlerWrapper.java:107) 1432836710243 ### at org.eclipse.jetty.server.Server.doStop(Server.ja
[JIRA] [radiatorview-plugin] (JENKINS-28674) Timing mismatch between radiator and individual jenkin job
Title: Message Title R. Tyler Croy commented on JENKINS-28674 Re: Timing mismatch between radiator and individual jenkin job I've moved this into the JENKINS project, INFRA is more for the Jenkins project's own internal infrastructure 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-28674) Timing mismatch between radiator and individual jenkin job
Title: Message Title R. Tyler Croy moved an issue Jenkins / JENKINS-28674 Timing mismatch between radiator and individual jenkin job Change By: R. Tyler Croy Project: Infrastructure Jenkins Key: INFRA JENKINS - 319 28674 Workflow: classic default workflow JNJira Component/s: radiatorview-plugin Component/s: ci 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 unsubscr
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Title: Message Title
Thomas Schweikle edited a comment on JENKINS-25370
Re: H in schedule does not work properly for minutes
{quote}It would help if you'd mention the Jenkins version affected.{quote}Jenkins 1.616{quote}Also, it's not clear how this is related to the reported issue. There's no 'H/1' anywhere in the report.{quote}{quote}I have several jobs configured with the same schedule interval:H/12 8-18 * * 1-5Which basically should mean: run every 12 minutes in business hours in work days.But the issue is that every of those jobs runs only 3 times. Like at 01, 13, 25 minutes. And none of them run in the second half of the hour.{quote}I have "H H/1 * * *" which means run this job every hour. But: the job is executed once a day only. If I want it once an hour I have to define: "H/1 * * * *" what reads as execute every minute, but this way the job runs once an hour as I'd never expected. Defining "H/2 * * * *" will indeed execute the job every two minutes. And defining "H H/2 * * *" will indeed execute the job every two hours.Regarding the description:H/1 * * * * -> execute every minute; real: execute once an hourH/2 * * * * -> execute every two minutes; real: execute every two minutesH H/1 * * * -> execute every hour; real: execute once a dayH H/2 * * * -> execute every two hours; real: execute every two hoursThe logic seems broken under circumstances. Maybe this helps reveal, whyH/12 8-18 * * 1-5does not do what is expected: run every 12 minutes from 8:00 until 18:00, every month, every year, on workdays. But instead does something like: run every 12 minutes, but only the first half of an hour, once a day -- since my findings are a lot simpler than what was reported, they may be a better starting point to find what the scheduler really makes out of "H/12 8-18 * * 1-5".PS: meanwhile I found some further not obvious errors with scheduls:H/40 * * * * -> run every 40 minutesThis works! Running the job at 00:40, 1:20, 3:00, 4:40, ...but:H/41 * * * * -> run every 41 minuteswill run the job once an hour: 0:41, 1:41, 2:41, 3:41, ...PPS: The same applies to " */1 * * * * " -> runs once an hour, not once every minute " * */1 * * * " -> runs once a day, not once an hour
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-25370) H in schedule does not work properly for minutes
Title: Message Title
Thomas Schweikle edited a comment on JENKINS-25370
Re: H in schedule does not work properly for minutes
{quote}It would help if you'd mention the Jenkins version affected.{quote}Jenkins 1.616{quote}Also, it's not clear how this is related to the reported issue. There's no 'H/1' anywhere in the report.{quote}{quote}I have several jobs configured with the same schedule interval:H/12 8-18 * * 1-5Which basically should mean: run every 12 minutes in business hours in work days.But the issue is that every of those jobs runs only 3 times. Like at 01, 13, 25 minutes. And none of them run in the second half of the hour.{quote}I have "H H/1 * * *" which means run this job every hour. But: the job is executed once a day only. If I want it once an hour I have to define: "H/1 * * * *" what reads as execute every minute, but this way the job runs once an hour as I'd never expected. Defining "H/2 * * * *" will indeed execute the job every two minutes. And defining "H H/2 * * *" will indeed execute the job every two hours.Regarding the description:H/1 * * * * -> execute every minute; real: execute once an hourH/2 * * * * -> execute every two minutes; real: execute every two minutesH H/1 * * * -> execute every hour; real: execute once a dayH H/2 * * * -> execute every two hours; real: execute every two hoursThe logic seems broken under circumstances. Maybe this helps reveal, whyH/12 8-18 * * 1-5does not do what is expected: run every 12 minutes from 8:00 until 18:00, every month, every year, on workdays. But instead does something like: run every 12 minutes, but only the first half of an hour, once a day -- since my findings are a lot simpler than what was reported, they may be a better starting point to find what the scheduler really makes out of "H/12 8-18 * * 1-5".PS: meanwhile I found some further not obvious errors with scheduls:H/40 * * * * -> run every 40 minutesThis works! Running the job at 00:40, 1:20, 3:00, 4:40, ...but:H/41 * * * * -> run every 41 minuteswill run the job once an hour: 0:41, 1:41, 2:41, 3:41, ... PPS: The same applies to*/1 * * * * -> runs once an hour, not once every minute* */1 * * * -> runs once a day, not once an hour
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [p4-plugin] (JENKINS-28448) "Publish Assets delete files when no shelve is used for review
Title: Message Title amit yedidia commented on JENKINS-28448 Re: "Publish Assets delete files when no shelve is used for review yes. well actually it can fit to "Submitted Cahngelist" anyway if no ChangeList number is given (Submitted or shelved), I think that "build review" should do nothing. 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-25370) H in schedule does not work properly for minutes
Title: Message Title
Thomas Schweikle edited a comment on JENKINS-25370
Re: H in schedule does not work properly for minutes
{quote}It would help if you'd mention the Jenkins version affected.{quote}Jenkins 1.616{quote}Also, it's not clear how this is related to the reported issue. There's no 'H/1' anywhere in the report.{quote}{quote}I have several jobs configured with the same schedule interval:H/12 8-18 * * 1-5Which basically should mean: run every 12 minutes in business hours in work days.But the issue is that every of those jobs runs only 3 times. Like at 01, 13, 25 minutes. And none of them run in the second half of the hour.{quote}I have "H H/1 * * *" which means run this job every hour. But: the job is executed once a day only. If I want it once an hour I have to define: "H/1 * * * *" what reads as execute every minute, but this way the job runs once an hour as I'd never expected. Defining "H/2 * * * *" will indeed execute the job every two minutes. And defining "H H/2 * * *" will indeed execute the job every two hours.Regarding the description:H/1 * * * * -> execute every minute; real: execute once an hourH/2 * * * * -> execute every two minutes; real: execute every two minutesH H/1 * * * -> execute every hour; real: execute once a dayH H/2 * * * -> execute every two hours; real: execute every two hoursThe logic seems broken under circumstances. Maybe this helps reveal, whyH/12 8-18 * * 1-5does not do what is expected: run every 12 minutes from 8:00 until 18:00, every month, every year, on workdays. But instead does something like: run every 12 minutes, but only the first half of an hour, once a day -- since my findings are a lot simpler than what was reported, they may be a better starting point to find what the scheduler really makes out of "H/12 8-18 * * 1-5". PS: meanwhile I found some further not obvious errors with scheduls:H/40 * * * * -> run every 40 minutesThis works! Running the job at 00:40, 1:20, 3:00, 4:40, ...but:H/41 * * * * -> run every 41 minuteswill run the job once an hour: 0:41, 1:41, 2:41, 3:41, ...
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 "Jen
[JIRA] [p4-plugin] (JENKINS-28448) "Publish Assets delete files when no shelve is used for review
Title: Message Title Paul Allen commented on JENKINS-28448 Re: "Publish Assets delete files when no shelve is used for review SCL? Shelved Changelist? 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-25370) H in schedule does not work properly for minutes
Title: Message Title
Thomas Schweikle edited a comment on JENKINS-25370
Re: H in schedule does not work properly for minutes
{quote}It would help if you'd mention the Jenkins version affected.{quote}Jenkins 1.616{quote}Also, it's not clear how this is related to the reported issue. There's no 'H/1' anywhere in the report.{quote}{quote}I have several jobs configured with the same schedule interval:H/12 8-18 * * 1-5Which basically should mean: run every 12 minutes in business hours in work days.But the issue is that every of those jobs runs only 3 times. Like at 01, 13, 25 minutes. And none of them run in the second half of the hour.{quote}I have "H H/1 * * *" which means run this job every hour. But: the job is executed once a day only. If I want it once an hour I have to define: "H/1 * * * *" what reads as execute every minute, but this way the job runs once an hour as I'd never expected. Defining "H/2 * * * *" will indeed execute the job every two minutes. And defining "H H/2 * * *" will indeed execute the job every two hours.Regarding the description:H/1 * * * * -> execute every minute; real: execute once an hourH/2 * * * * -> execute every two minutes; real: execute every two minutesH H/1 * * * -> execute every hour; real: execute once a dayH H/2 * * * -> execute every two hours; real: execute every two hoursThe logic seems broken under circumstances. Maybe this helps reveal, whyH/12 8-18 * * 1-5does not do what is expected: run every 12 minutes from 8:00 until 18:00, every month, every year, on workdays. But instead does something like: run every 12 minutes, but only the first half of an hour, once a day -- since my findings are a lot simpler than what was reported, they may be a better starting point to find what the scheduler really makes out of "H/12 8-18 * * 1-5".
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-25370) H in schedule does not work properly for minutes
Title: Message Title Thomas Schweikle commented on JENKINS-25370 Re: H in schedule does not work properly for minutes It would help if you'd mention the Jenkins version affected. Jenkins 1.616 Also, it's not clear how this is related to the reported issue. There's no 'H/1' anywhere in the report. I have several jobs configured with the same schedule interval: H/12 8-18 * * 1-5 Which basically should mean: run every 12 minutes in business hours in work days. But the issue is that every of those jobs runs only 3 times. Like at 01, 13, 25 minutes. And none of them run in the second half of the hour. I have "H H/1 * * *" which means run this job every hour. But: the job is executed once a day only. If I want it once an hour I have to define: "H/1 * * * *" what reads as execute every minute, but this way the job runs once an hour as I'd never expected. Defining "H/2 * * * *" will indeed execute the job every two minutes. And defining "H H/2 * * *" will indeed execute the job every two hours. Regarding the description: H/1 * * * * -> execute every minute; real: execute once an hour H/2 * * * * -> execute every two minutes; real: execute every two minutes H H/1 * * * -> execute every hour; real: execute once a day H H/2 * * * -> execute every two hours; real: execute every two hours The logic seems broken under circumstances. Maybe this helps reveal, why H/12 8-18 * * 1-5 does not do what is expected: run every 12 minutes from 8:00 until 18:00, every month, every year, on workdays. But instead does something like: run every 12 minutes, but only the first half of an hour, once a day – since my findings are a lot simpler than what was reported, they may be a better starting point to find what the scheduler really makes out of "H/12 8-18 * * 1-5". Add Comment
[JIRA] [workflow-plugin] (JENKINS-28673) ISE from BuildTriggerListener.onDeleted
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-28673 ISE from BuildTriggerListener.onDeleted Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 01/Jun/15 1:28 PM Priority: Major Reporter: Jesse Glick Observed in a log file from 1.4 on 1.580.3: ... hudson.model.listeners.RunListener report WARNING: RunListener failed java.lang.IllegalStateException: broken flow at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.runInCpsVmThread(CpsFlowExecution.java:506) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.scheduleNextRun(CpsStepContext.java:343) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.onFailure(CpsStepContext.java:313) at org.jenkinsci.plugins.workflow.support.steps.build.BuildTriggerListener.onDeleted(BuildTriggerListener.java:33) at hudson.model.listeners.RunListener.fireDeleted(RunListener.java:244) at hudson.model.Run.delete(Run.java:1488) at hudson.maven.MavenModuleSetBuild.delete(MavenModuleSetBuild.java:438) at hudson.tasks.LogRotator.perform(LogRotator.java:129) at hudson.model.Job.logRotate(Job.java:447) at ... This seems to be printed to the log even in the normal case that both upstream and downstream are long finished, and the downstream just got log-rotated. Probably onCompleted should delete BuildTriggerAction? Note that fcff78cd04b7410dcaa2a7bd124750f2bda7ba08 in 1.
[JIRA] [p4-plugin] (JENKINS-28450) Publish Assets submit files even if build steps marked as failure
Title: Message Title amit yedidia commented on JENKINS-28450 Re: Publish Assets submit files even if build steps marked as failure yes. I think it will be a good idea (currently such checkbox doesn't exist) 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] [p4-plugin] (JENKINS-28448) "Publish Assets delete files when no shelve is used for review
Title: Message Title amit yedidia commented on JENKINS-28448 Re: "Publish Assets delete files when no shelve is used for review Hi Paul. I think the proper behavior will be to ignore this build if no SCL is given. what is the point of doing "build review" with no SCL? Regards, Amit 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] [jclouds-plugin] (JENKINS-28672) Slave conflict when using multiple Jenkins instances
Title: Message Title Pedro Ribeiro created an issue Jenkins / JENKINS-28672 Slave conflict when using multiple Jenkins instances Issue Type: Bug Assignee: abayer Components: jclouds-plugin Created: 01/Jun/15 1:03 PM Priority: Minor Reporter: Pedro Ribeiro When using the same Google Compute Engine project (don't know if this happens with other providers, but I assume it does) to host slaves from multiple Jenkins instances, template/cloud quotas don't work as expected: slaves from both Jenkins instances are used when checking quotas instead of taking into account only slaves from that specific Jenkins instance. Add Comment
[JIRA] [slack-plugin] (JENKINS-27122) Resets values for folded parameters when you hit "Apply" but not "Save"
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-27122 Resets values for folded parameters when you hit "Apply" but not "Save" Change By: Sam Gleske Status: Open Resolved Assignee: Sam Gleske 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] [slack-plugin] (JENKINS-27122) Resets values for folded parameters when you hit "Apply" but not "Save"
Title: Message Title Sam Gleske commented on JENKINS-27122 Re: Resets values for folded parameters when you hit "Apply" but not "Save" I believe this was resolved in Slack Plugin 1.8. See release notes under bug fixes https://github.com/jenkinsci/slack-plugin/blob/master/CHANGELOG.md#180-release-notes 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] [slack-plugin] (JENKINS-27326) Slack plugin messes up Configure page
Title: Message Title Sam Gleske commented on JENKINS-27326 Re: Slack plugin messes up Configure page This will be resolved when Slack Plugin 2.0 is released. See https://github.com/jenkinsci/slack-plugin/pull/79 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] [slack-plugin] (JENKINS-27652) Workflow support for Slack Notifications (Pre and Post build)
Title: Message Title Sam Gleske commented on JENKINS-27652 Re: Workflow support for Slack Notifications (Pre and Post build) Contributions for this are welcome. I don't actively develop the slack plugin. I only maintain pull requests and releases. I think this would definitely be useful. 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] [slack-plugin] (JENKINS-27985) Slack post may have failed. Response: Private integrations can't post to public channels
Title: Message Title Sam Gleske resolved as Not A Defect Jenkins / JENKINS-27985 Slack post may have failed. Response: Private integrations can't post to public channels Change By: Sam Gleske Status: Open Resolved Assignee: Sam Gleske Resolution: Not A Defect 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] [slack-plugin] (JENKINS-27985) Slack post may have failed. Response: Private integrations can't post to public channels
Title: Message Title Sam Gleske commented on JENKINS-27985 Re: Slack post may have failed. Response: Private integrations can't post to public channels So this is a limitation imposed by slack. I would consider this not a bug and defer to ben slaughter's workaround or using a public integration. 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] [slack-plugin] (JENKINS-28201) Slack plugin check boxes for Include Test Summary and Notify Repeated Failure toggle wrong feature
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-28201 Slack plugin check boxes for Include Test Summary and Notify Repeated Failure toggle wrong feature Change By: Sam Gleske Status: Open Resolved Assignee: Sam Gleske 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] [slack-plugin] (JENKINS-27935) Slack plugin 1.7 fails to post to channel; had to revert to 1.2
Title: Message Title Sam Gleske commented on JENKINS-27935 Re: Slack plugin 1.7 fails to post to channel; had to revert to 1.2 There seems to be another user who is having trouble with a proxy as well. See https://github.com/jenkinsci/slack-plugin/issues/102 I don't have any way to do testing behind proxies so contributions are welcome for the fix. 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] [slack-plugin] (JENKINS-28201) Slack plugin check boxes for Include Test Summary and Notify Repeated Failure toggle wrong feature
Title: Message Title Sam Gleske commented on JENKINS-28201 Re: Slack plugin check boxes for Include Test Summary and Notify Repeated Failure toggle wrong feature This has been fixed in Slack Plugin 1.8. See release notes - https://github.com/jenkinsci/slack-plugin/blob/master/CHANGELOG.md#180-release-notes 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Kevin Phillips updated an issue Jenkins / JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Change By: Kevin Phillips Labels: lts-candidate 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-27492) Permission deprecation warning in authorization context
Title: Message Title Daniel Spilker resolved as Fixed Will be fixed in 1.35. Jenkins / JENKINS-27492 Permission deprecation warning in authorization context Change By: Daniel Spilker 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] [gerrit-trigger-plugin] (JENKINS-28593) Make gerrit comments configurable
Title: Message Title Gergely Polonkai commented on JENKINS-28593 Re: Make gerrit comments configurable I cannot really find it on the plugin’s wiki; how should I denote which file to use as a comment file? 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] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28656 Docker Traceability should support the creation of image fingerprints on-demand Change By: Oleg Nenashev Component/s: docker-traceability-plugin Component/s: docker-commons-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] [prioritysorter-plugin] (JENKINS-28621) Jenkins jobs get held up in queue waiting for available executors, even though all are available
Title: Message Title Travis Flint commented on JENKINS-28621 Re: Jenkins jobs get held up in queue waiting for available executors, even though all are available thanks, yes it seems to still be referencing the older version of java. Will try to figure out why it is getting that. 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-28503) White Buttons
Title: Message Title Tobias Köck resolved as Fixed Someone fiddled with the css file. Can be closed. Thanks. Jenkins / JENKINS-28503 White Buttons Change By: Tobias Köck 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] [docker-plugin] (JENKINS-28661) Docker builds do not work with matrix project plugin
Title: Message Title Kanstantsin Shautsou resolved as Duplicate Duplicates GH issue Jenkins / JENKINS-28661 Docker builds do not work with matrix project plugin Change By: Kanstantsin Shautsou 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] [prioritysorter-plugin] (JENKINS-28621) Jenkins jobs get held up in queue waiting for available executors, even though all are available
Title: Message Title Daniel Beck commented on JENKINS-28621 Re: Jenkins jobs get held up in queue waiting for available executors, even though all are available Make sure Jenkins is using that JRE. Determine on the /systemInfo URL. 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.
