[JIRA] (JENKINS-33846) Restart pipeline from specific stage, after failure
Title: Message Title dan tran edited a comment on JENKINS-33846 Re: Restart pipeline from specific stage, after failure Ah, this is Jenkins Enterprise supports this feature Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33846) Restart pipeline from specific stage, after failure
Title: Message Title dan tran commented on JENKINS-33846 Re: Restart pipeline from specific stage, after failure Ah, this is Jenkins Enterprise supports this feature Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33846) Restart pipeline from specific stage, after failure
Title: Message Title dan tran commented on JENKINS-33846 Re: Restart pipeline from specific stage, after failure same here, it is very convenient with the build pipeline plugin. Can this be reopened and have user vote? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40737) Managed script/configs aren't found/cannot be read/throw exceptions
Title: Message Title Stephen Donner updated an issue Jenkins / JENKINS-40737 Managed script/configs aren't found/cannot be read/throw exceptions Change By: Stephen Donner First, apologies in advance, as I might be filing this issue in the wrong component and/or hopefully there's a potential workaround or better way of working through this.Since upgrading the Managed Script Plugin and Config File Provider Plugin (and a few others) to the latest versions - 1.3 and 2.15.1, respectively, we're seeing the following bustage:1. With our current configuration, whenever we load our non-Pipeline jobs' /configure pages, we get HTTP 500s in:* fillFileIdItems* fillBuildStepIdItems* descriptorByName/org.jenkinsci.plugins.managedscripts.ScriptBuildStep/checkBuildStepId?value=org.jenkinsci.plugins.managedscripts.ScriptConfig1429801884194=org.jenkinsci.plugins.managedscripts.ScriptConfig1429801884194 2. This presents itself as "ERROR" links in the "Execute managed script" sections of our "Build" portion in the job's config.3. Clicking on "view selected script" in the screenshot yields a 404 for that script.4. The stack trace/exception for the 2nd managed-script's error looks like this:javax.servlet.ServletException: java.lang.IllegalStateException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) 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:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:37) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title ikedam assigned an issue to ikedam Preparing additional changes to release: https://github.com/jenkinsci/authorize-project-plugin/pull/27 Jenkins / JENKINS-35081 Separate authorization configuration page Change By: ikedam Assignee: Stephen Connolly ikedam Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40739) Introduce "Don't restrict users to configuring the job"
Title: Message Title ikedam created an issue Jenkins / JENKINS-40739 Introduce "Don't restrict users to configuring the job" Issue Type: New Feature Assignee: ikedam Components: authorize-project-plugin Created: 2016/Dec/31 5:24 AM Priority: Major Reporter: ikedam https://github.com/jenkinsci/authorize-project-plugin/pull/26#discussion_r79290571 I plan to introduce an alternate feature like "Don't restrict users to configuring the job": `hasConfigurePermission` returns always `true` if checked. `readResolve` blocks CLI and RestWebAPI by a user other than the one to run as. This is an option expected to be used when appropriate permissions are configured for that job. May makes sense to introduce it as a field of AuthorizeProjectProperty. Add Comment
[JIRA] (JENKINS-37478) OWASP does not release files from scan
Title: Message Title Steve Springett commented on JENKINS-37478 Re: OWASP does not release files from scan I'm wondering if this issue is related to an unresolved Java issue that cannot be fixed. http://bugs.java.com/bugdatabase/view_bug.do?bug_id=4715154 dependency-check-utils/src/main/java/org/owasp/dependencycheck/utils/Checksum.java uses FileChannel and may be triggering the issue since all scanned files get checksummed as part of the analysis. I also wonder if introducing a delay at the end of the job would provide a workaround? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40738) Optimization - avoid 6ms lookup for checking artifacts on disk
Title: Message Title James Dumay updated JENKINS-40738 Jenkins / JENKINS-40738 Optimization - avoid 6ms lookup for checking artifacts on disk Change By: James Dumay Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40738) Optimization - avoid 6ms lookup for checking artifacts on disk
Title: Message Title James Dumay started work on JENKINS-40738 Change By: James Dumay Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40738) Optimization - avoid 6ms lookup for checking artifacts on disk
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40738 Optimization - avoid 6ms lookup for checking artifacts on disk Issue Type: Bug Assignee: James Dumay Components: blueocean-plugin Created: 2016/Dec/31 3:04 AM Priority: Minor Reporter: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/test/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticatorTest.java http://jenkins-ci.org/commit/authorize-project-plugin/9431366571343f6b965b125366e533cc32ef4ce1 Log: JENKINS-35081 Fixed these tests Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty.java src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectStrategyDescriptor.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/TriggeringUsersAuthorizationStrategy.java http://jenkins-ci.org/commit/authorize-project-plugin/5664d9f32e56a96e5c7ffb3a11756ee6c32b6765 Log: JENKINS-35081 Move the permission check to the constructor/readResolve Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/main/resources/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty/AuthorizationAction/action.jelly http://jenkins-ci.org/commit/authorize-project-plugin/052ea591b278614ff6ee616671186acd24e1becd Log: JENKINS-35081 Hide the action from users that do not have the required permissions Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty.java http://jenkins-ci.org/commit/authorize-project-plugin/7a04dbe7a2158b873e450b01e3f03ea715d82247 Log: JENKINS-35081 Remove redundant null check Thanks findbugs for finding that one Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/test/java/org/jenkinsci/plugins/authorizeproject/GlobalQueueItemAuthenticatorTest.java src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest.java http://jenkins-ci.org/commit/authorize-project-plugin/498735c78f97843521be7e507642f61d472edb48 Log: JENKINS-35081 Fix tests Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/main/resources/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty/AuthorizationAction/index.jelly http://jenkins-ci.org/commit/authorize-project-plugin/d2926ccd24c4c704950366a2fce3e5801c2828ed Log: JENKINS-35081 Oops checking the wrong permission on this Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/help-noNeedReauthentication.html src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/help-noNeedReauthentication_ja.html src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategyTest.java http://jenkins-ci.org/commit/authorize-project-plugin/5e13d24962ebcc8dfc2067e159777ce0a75a32e0 Log: JENKINS-35081 The reconfiguration stuff no longer makes sense with screen separation Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/test/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticatorTest.java http://jenkins-ci.org/commit/authorize-project-plugin/dba0d59890693da379a6338248b7ce44b20ebe97 Log: JENKINS-35081 Fix failing test The test case was failing for a now invalid condition as the stronger validation fo Guice will ensure that any AuthorizationProjectStrategy that uses a Descriptor which is not extending AuthorizationProjectStrategyDescriptor will not be instantiated. For this reason I removed the parts of the test that are now invalid Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest.java http://jenkins-ci.org/commit/authorize-project-plugin/c303dbdec32a2070544d992b20df67b6958f28a4 Log: JENKINS-35081 More tests fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: ikedam Path: pom.xml src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty.java src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectStrategyDescriptor.java src/main/java/org/jenkinsci/plugins/authorizeproject/ConfigurationPermissionEnforcer.java src/main/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticator.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/TriggeringUsersAuthorizationStrategy.java src/main/resources/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty/AuthorizationAction/action.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty/AuthorizationAction/index.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty/authorize.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/ConfigurationPermissionEnforcer/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/Messages.properties src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/help-noNeedReauthentication.html src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/help-noNeedReauthentication_ja.html src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy/global-security.jelly src/test/java/org/jenkinsci/plugins/authorizeproject/GlobalQueueItemAuthenticatorTest.java src/test/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticatorTest.java src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategyTest.java src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategyTest.java http://jenkins-ci.org/commit/authorize-project-plugin/4b8379e73e3e1eb2359636500c5be3d642bdd965 Log: Merge pull request #26 from stephenc/jenkins-35081 JENKINS-35081 Split the configuration of authentication into a separate screen Compare: https://github.com/jenkinsci/authorize-project-plugin/compare/25b5015c42a1...4b8379e73e3e Add Comment
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty.java src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/ConfigurationPermissionEnforcer.java src/main/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticator.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SystemAuthorizationStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/TriggeringUsersAuthorizationStrategy.java src/main/resources/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty/AuthorizationAction/index.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty/authorize.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty/config.jelly http://jenkins-ci.org/commit/authorize-project-plugin/79d7bd575740aea53c0dae1f636451a08a3cac66 Log: JENKINS-35081 Split the configuration of authentication into a separate screen I still have some tests to fix up before this change is ready Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectStrategy.java src/main/resources/org/jenkinsci/plugins/authorizeproject/Messages.properties http://jenkins-ci.org/commit/authorize-project-plugin/d5caebdabb4d004379a9163ade3dc65ae22b6f55 Log: JENKINS-35081 Give a more meaningful error message Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/main/resources/org/jenkinsci/plugins/authorizeproject/ConfigurationPermissionEnforcer/config.jelly http://jenkins-ci.org/commit/authorize-project-plugin/41a3f88b44e7afd861139107de7e2275a1401f9b Log: JENKINS-35081 Oops without this file the veto does not work Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java http://jenkins-ci.org/commit/authorize-project-plugin/4ebd13f03eccb0f82702e0bff4a7e13be4ff290a Log: JENKINS-35081 Need a @DataBoundConstructor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/authorizeproject/ConfigurationPermissionEnforcer.java http://jenkins-ci.org/commit/authorize-project-plugin/1505f29d1c7ac6fe12918886fd2cd7cd4aa5988c Log: JENKINS-35081 Adding some javadocs Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40721) Wrappers provided by plugins not working correctly
Title: Message Title Andrew Bayer commented on JENKINS-40721 Re: Wrappers provided by plugins not working correctly So...surprise! I think I got it working. PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/82 but I am still wary of it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40721) Wrappers provided by plugins not working correctly
Title: Message Title Andrew Bayer updated JENKINS-40721 Jenkins / JENKINS-40721 Wrappers provided by plugins not working correctly Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40721) Wrappers provided by plugins not working correctly
Title: Message Title Andrew Bayer started work on JENKINS-40721 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40737) Managed script/configs aren't found/cannot be read/throw exceptions
Title: Message Title Stephen Donner created an issue Jenkins / JENKINS-40737 Managed script/configs aren't found/cannot be read/throw exceptions Issue Type: Bug Assignee: Dominik Bartholdi Attachments: Screen Shot 2016-12-30 at 6.10.06 PM.png, support_2016-12-31_01.59.54.zip Components: managed-scripts-plugin Created: 2016/Dec/31 2:25 AM Environment: Jenkins: 2.32.1 Config File Provider Plugin: 2.15.1 Environment Injector Plugin: 1.93.1 Managed Scripts: 1.3 We have a bunch of others installed; let me know if you need them listed with versions, too (it should be in the support file, attach). Priority: Critical Reporter: Stephen Donner First, apologies in advance, as I might be filing this issue in the wrong component and/or hopefully there's a potential workaround or better way of working through this. Since upgrading the Managed Script Plugin and Config File Provider Plugin (and a few others) to the latest versions - 1.3 and 2.15.1, respectively, we're seeing the following bustage: 1. With our current configuration, whenever we load our non-Pipeline jobs' /configure pages, we get HTTP 500s in: fillFileIdItems fillBuildStepIdItems
[JIRA] (JENKINS-40723) Built Dockerfile images are never removed
Title: Message Title Patrick Wolf commented on JENKINS-40723 Re: Built Dockerfile images are never removed building the image for every build kind of defeats the purpose doesn't it? Then it would be wiser to just build the image once and publish it to docker hub to use with a regular docker statement. I think this might fall under general workspace management more than something to be solved in Declarative. We could add some sugar to clean workspace in post but beyond that what can we do? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40723) Built Dockerfile images are never removed
Title: Message Title Andrew Bayer commented on JENKINS-40723 Re: Built Dockerfile images are never removed Yes, but in Declarative, we possibly generate a lot more of 'em without the user ever having to really think about it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40721) Wrappers provided by plugins not working correctly
Title: Message Title
Andrew Bayer commented on JENKINS-40721
Re: Wrappers provided by plugins not working correctly
And the probably easier alternative would be to have better error messages - don't just say "not a wrapper, GTFO" but instead "not a wrapper, here's what wrapper syntax is - foo(), bar("arg"), baz(oneArg: 1, twoArg: 2)" or something like that.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40721) Wrappers provided by plugins not working correctly
Title: Message Title Andrew Bayer commented on JENKINS-40721 Re: Wrappers provided by plugins not working correctly Note to myself - if it's viable to solve this, then we need to do two things: First, get the parser and validator to detect MethodASTMethodCall without args without parentheses in the right cases. Second, get the runtime to probably do a propertyMissing implementation that will return script."barething"() in that case as well. Not 100% sure that's possible but I'll see what I can do. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40723) Built Dockerfile images are never removed
Title: Message Title Patrick Wolf commented on JENKINS-40723 Re: Built Dockerfile images are never removed This isn't specific to pipeline-model-definition though is it? This would be true of any build using a dockerfile, no? Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40723) Built Dockerfile images are never removed
Title: Message Title Andrew Bayer commented on JENKINS-40723 Re: Built Dockerfile images are never removed Interesting question here - how do we handle this? Do we want to delete the image after every build? Michael Neale, James Dumay, Patrick Wolf - thoughts? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40699) Post-stage/build test results etc doesn't play well with parallel on multiple nodes
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-40699 Post-stage/build test results etc doesn't play well with parallel on multiple nodes Change By: Andrew Bayer Summary: Declarative pipeline beta docs: how to collect Post-stage/build test results from different etc doesn't play well with parallel on multiple nodes Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40699) Declarative pipeline beta docs: how to collect test results from different nodes
Title: Message Title Andrew Bayer commented on JENKINS-40699 Re: Declarative pipeline beta docs: how to collect test results from different nodes Huh, interesting point. Hadn't thought about that case. I'm gonna leave this open and rename it - this seems like a valid problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40721) Wrappers provided by plugins not working correctly
Title: Message Title Andrew Bayer commented on JENKINS-40721 Re: Wrappers provided by plugins not working correctly So this is a little dumb, but if you do timestamps() rather than just timestamps, it works. I know, I know. I'll see if I can make it smarter. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40524) Rework agent syntax to be more extensible
Title: Message Title Andrew Bayer commented on JENKINS-40524 Re: Rework agent syntax to be more extensible Ouch, nested maps is gonna take some time, so I'm pulling that for now and going with the current state. We don't have a need for nested maps support right now anyway. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37478) OWASP does not release files from scan
Title: Message Title David Norman edited a comment on JENKINS-37478 Re: OWASP does not release files from scan I made a job in Jenkins 2.32.1 on a Windows 2008 master that just runs dependency checker 1.4.4 , then publishes the results from the xml. At the end of the build, it's supposed to delete the workspace, but it can't because of locks on all the .jar files it scanned. Stop/start on the Jenkins service lets me manually clear the workspace in Windows Explorer. This sounds like the right issue to jump aboard. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37478) OWASP does not release files from scan
Title: Message Title
David Norman edited a comment on JENKINS-37478
Re: OWASP does not release files from scan
I made a job in Jenkins 2.32.1 on a Windows 2008 master that just runs dependency checker, then publishes the results from the xml. At the end of the build, it's supposed to delete the workspace, but it can't because of locks on all the {{**/* .jar }} files it scanned. Stop/start on the Jenkins service lets me manually clear the workspace in Windows Explorer. This sounds like the right issue to jump aboard.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37478) OWASP does not release files from scan
Title: Message Title
David Norman edited a comment on JENKINS-37478
Re: OWASP does not release files from scan
I made a job in Jenkins 2.32.1 on a Windows 2008 master that just runs dependency checker, then publishes the results from the xml. At the end of the build, it's supposed to delete the workspace, but it can't because of locks on all the {{ **/*.jar }} files it scanned. Stop/start on the Jenkins service lets me manually clear the workspace in Windows Explorer. This sounds like the right issue to jump aboard.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37478) OWASP does not release files from scan
Title: Message Title David Norman commented on JENKINS-37478 Re: OWASP does not release files from scan I made a job in Jenkins 2.32.1 on a Windows 2008 master that just runs dependency checker, then publishes the results from the xml. At the end of the build, it's supposed to delete the workspace, but it can't because of locks on all the */.jar files it scanned. Stop/start on the Jenkins service lets me manually clear the workspace in Windows Explorer. This sounds like the right issue to jump aboard. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40370 Re: Run stage when branch name matches Code changed in jenkins User: Andrew Bayer Path: SYNTAX.md pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTMethodCall.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStep.java pipeline-model-api/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ast/Messages.properties pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Aborted.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Always.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Changed.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Failure.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Success.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Unstable.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/Parser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/model/BuildCondition.java pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/Messages.properties pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Messages.properties pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/DeclarativeLinterCommandTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ValidatorTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/WhenStageTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ModelConverterActionTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/parser/GroovyShellDecoratorImplTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParserTest.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/221d6e800a36ac9980a099f71a7106a54191c97f Log: Merge branch 'master' into JENKINS-40370 Conflicts: pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/Messages.properties
[JIRA] (JENKINS-40406) References to created jobs stored undefinitely
Title: Message Title Daniel Spilker commented on JENKINS-40406 Re: References to created jobs stored undefinitely The seed job stores the generated jobs in each build. If you do not discard old builds, it will keep the history forever. But if you only keep one build, the seed job will forget the history and will not delete previously deleted jobs again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40693) badMessage: 400 Bad Host header for HttpChannelOverHttp
Title: Message Title olamy edited a comment on JENKINS-40693 Re: badMessage: 400 Bad Host header for HttpChannelOverHttp Sorry for delay I was a bit busy those last days. I'm having a look. Shouldn't be a drama to backport this fix. We will let you know. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39769) update to latest config-file-provider
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-39769 update to latest config-file-provider Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39769) update to latest config-file-provider
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39769 Re: update to latest config-file-provider Code changed in jenkins User: imod Path: job-dsl-plugin/build.gradle job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/ConfigFileProviderHelper.groovy job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JenkinsJobManagement.java http://jenkins-ci.org/commit/job-dsl-plugin/221e9dc0e514d13cf8b89df0c5b74402237f532e Log: JENKINS-39769 update to latest config-file-provider plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39769) update to latest config-file-provider
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39769 Re: update to latest config-file-provider Code changed in jenkins User: imod Path: job-dsl-plugin/build.gradle http://jenkins-ci.org/commit/job-dsl-plugin/07890e8d4af5c552fefb13b0badcf62d6ee336d4 Log: JENKINS-39769 update to latest beta version of config-file-provider Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39769) update to latest config-file-provider
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39769 Re: update to latest config-file-provider Code changed in jenkins User: imod Path: job-dsl-plugin/build.gradle http://jenkins-ci.org/commit/job-dsl-plugin/cfccf1e044453b658fdd91ebe3dfeae53c13c22a Log: [FIXED JENKINS-39769] update to released config-file-provider and managed-scripts Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40728) Invalid class cast in Disk Usage Plugin when ItemGroup is not a TopLevelItem
Title: Message Title Oleg Nenashev commented on JENKINS-40728 Re: Invalid class cast in Disk Usage Plugin when ItemGroup is not a TopLevelItem Reassigned the plugin to Lucie Votypkova, who is a maintainer of the Disk Usage plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40728) Invalid class cast in Disk Usage Plugin when ItemGroup is not a TopLevelItem
Title: Message Title Oleg Nenashev assigned an issue to Lucie Votypkova Jenkins / JENKINS-40728 Invalid class cast in Disk Usage Plugin when ItemGroup is not a TopLevelItem Change By: Oleg Nenashev Assignee: Oleg Nenashev Lucie Votypkova Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40728) Invalid class cast in Disk Usage Plugin when ItemGroup is not a TopLevelItem
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40728 Invalid class cast in Disk Usage Plugin when ItemGroup is not a TopLevelItem Change By: Oleg Nenashev Component/s: disk-usage-plugin Component/s: config-file-provider-plugin Component/s: managed-scripts-plugin Component/s: promoted-builds-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-40728) Managed scripts 1.3 breaks promotions
Title: Message Title Oleg Nenashev commented on JENKINS-40728 Re: Managed scripts 1.3 breaks promotions So the failing codeline is here: https://github.com/jenkinsci/disk-usage-plugin/blob/disk-usage-0.28/src/main/java/hudson/plugins/disk_usage/DiskUsageProperty.java#L342. Promoted Build's Job Property is an ItemGroup (https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/JobPropertyImpl.java#L54), hence it can be legitimately returned in the owner.getParent() call. DiskUsage plugin performs the invalid and unchecked class cast, hence it is a root cause of the issue. Even if the issue appears during the upgrade of other plugins, Disk Usage Plugin is the one to be fixed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40728) Invalid class cast in Disk Usage Plugin when ItemGroup is not a TopLevelItem
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40728 Invalid class cast in Disk Usage Plugin when ItemGroup is not a TopLevelItem Change By: Oleg Nenashev Summary: Managed scripts 1.3 breaks promotions Invalid class cast in Disk Usage Plugin when ItemGroup is not a TopLevelItem Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40728) Managed scripts 1.3 breaks promotions
Title: Message Title Bryson Gibbons commented on JENKINS-40728 Re: Managed scripts 1.3 breaks promotions I don't have the job-dsl plugin installed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27281) Provide more control over EC2 instance spawn rate
Title: Message Title Mark Brown commented on JENKINS-27281 Re: Provide more control over EC2 instance spawn rate Sorry, I didn't - I gave up on using EC2 entirely for that application (switched to fixed nodes instead) due to this and other issues with EC2 performance in that particular application. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40524) Rework agent syntax to be more extensible
Title: Message Title Andrew Bayer commented on JENKINS-40524 Re: Rework agent syntax to be more extensible Yeah, I'm gonna go with the current implementation but reserve the right to revisit this in the future, 'cos it's an area that I think we'll need to have more agent implementations to really know what's best. But for now, yeah. We're good. Just gotta make a few tweaks to the PR to properly support nested maps and we should be good to go. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16360) Print DSL formatted config.xml for an existing Job
Title: Message Title Raymond Barbiero commented on JENKINS-16360 Re: Print DSL formatted config.xml for an existing Job Wasn't too bad to implement. Works for the 350 jobs I have access to so far. https://github.com/visualphoenix/jenkins-xml-to-jobdsl Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40256) Enhancements to form controls
Title: Message Title Cliff Meyers updated JENKINS-40256 Jenkins / JENKINS-40256 Enhancements to form controls Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40256) Enhancements to form controls
Title: Message Title Cliff Meyers commented on JENKINS-40256 Re: Enhancements to form controls Final PR that completed task: https://github.com/jenkinsci/blueocean-plugin/pull/666 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40662) Deep-linking to Run Details screen with no tab specified causes problem when closing modal
Title: Message Title Cliff Meyers started work on JENKINS-40662 Change By: Cliff Meyers Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40736) Jenkins to schedule a test to run from ALM
Title: Message Title srikanth reddy created an issue Jenkins / JENKINS-40736 Jenkins to schedule a test to run from ALM Issue Type: Bug Assignee: Ofir Shaked Attachments: 2016-12-29_15-02-15.png Components: hp-application-automation-tools-plugin Created: 2016/Dec/30 4:26 PM Priority: Blocker Reporter: srikanth reddy I am getting the error as shown in the screenshot. Please help Add Comment
[JIRA] (JENKINS-40735) Gradle filling up /tmp folder
Title: Message Title Jed Jacobs created an issue Jenkins / JENKINS-40735 Gradle filling up /tmp folder Issue Type: Bug Assignee: wolfs Components: gradle-plugin Created: 2016/Dec/30 3:33 PM Environment: OS: Linux Jenkins: v1.64 Gradle plug-in v1.24 Priority: Minor Reporter: Jed Jacobs The /tmp directory on our master and/or slave (depending on where the build is run) is being filled up with files such as the examples below. init-artifactory8251121422779630554gradle buildInfo4555888004620870892.properties Shouldn't gradle be cleaning up after itself? Add Comment
[JIRA] (JENKINS-40734) Shell step cannot use environment variables that contain $$
Title: Message Title
Ben Dean created an issue
Jenkins / JENKINS-40734
Shell step cannot use environment variables that contain $$
Issue Type:
Bug
Assignee:
Unassigned
Components:
durable-task-plugin, pipeline, workflow-durable-task-step-plugin
Created:
2016/Dec/30 2:59 PM
Environment:
CentOS 6.8 Jenkins 2.38 durable-task-plugin 1.12 workflow-aggregator (pipeline) 2.4 and all its dependencies: workflow-cps (version:2.17) workflow-support (version:2.5) workflow-basic-steps (version:2.1) pipeline-input-step (version:2.1) pipeline-milestone-step (version:1.0) pipeline-build-step (version:2.2) pipeline-stage-view (version:2.0) workflow-multibranch (version:2.8) workflow-durable-task-step (version:2.4) workflow-api (version:2.3) pipeline-stage-step (version:2.2) workflow-scm-step (version:2.2) workflow-cps-global-lib (version:2.3) workflow-step-api (version:2.3) workflow-job (version:2.6)
Labels:
pipeline credentials environment-variables shell
Priority:
Minor
Reporter:
Ben Dean
When I run a Jenkinsfile that has a sh step that uses an environment variable (such as a password) that has two $$ in a row, they get replaced with one $. Here's the steps to reproduce: 1. Make a global credential id "foo", username "foo", password "bar$$baz" 2. Use this Jenkinsfile:
node('linux') {
withCredentials([[$class: 'UsernamePasswordMultiBinding', credentialsId: 'foo',
[JIRA] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title
Anton Lundin commented on JENKINS-34268
Re: Lock multiple resources using the Pipeline lock step
I did a really ugly workaround for the missing resourceVariable : lock(label: 'LABEL', quantity: 1) { echo org.jenkins.plugins.lockableresources.LockableResourcesManager.class.get().getResourcesFromBuild(currentBuild.getRawBuild())[0].getName() } That will get you which resource you locked.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40256) Enhancements to form controls
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40256 Re: Enhancements to form controls Code changed in jenkins User: Cliff Meyers Path: src/test/js/i18n/loadGerman.js http://jenkins-ci.org/commit/blueocean-acceptance-test/e9087cb63b7bf2674c2226fb64669351c71c6379 Log: JENKINS-40256 use a semantic selector (#91) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39790) API to create credential from Github access token (and validate)
Title: Message Title Vivek Pandey updated JENKINS-39790 Jenkins / JENKINS-39790 API to create credential from Github access token (and validate) Change By: Vivek Pandey Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38848) API to enumerate available credentials
Title: Message Title Vivek Pandey updated JENKINS-38848 Jenkins / JENKINS-38848 API to enumerate available credentials Change By: Vivek Pandey Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37419) Git plugin checking out non-existent submodule from different branch
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37419 Re: Git plugin checking out non-existent submodule from different branch Code changed in jenkins User: Ethan Trewhitt Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/28db63d60dca2c20c714036c26b9208bd2a6 Log: Reference the .gitmodules file to get a list of current submodules, rather than the .git/config file, which may have old submodules from other branches. JENKINS-37419 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37495) [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37495 Re: [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout Code changed in jenkins User: Ethan Trewhitt Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/a035c00bc2553ad8c4b1b621d31f2ce2856eaa23 Log: Explicitly look up the submodule path in .gitmodules rather than assuming that the path is the same as the module name. JENKINS-37495 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38805) User can run parametrised pipeline
Title: Message Title Vivek Pandey commented on JENKINS-38805 Re: User can run parametrised pipeline James Dumay Parameters are available only after run has started and the input steps (with parameters) are in paused state. Otherwise underlying pipeline/workflow libraries do not give any ways to get these parameter definitions. Sam Van Oort do you know any ways we can get them before and after run? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40733) git-plugin uses same default job parameters on notifyCommit
Title: Message Title Hasans Nakipovs created an issue Jenkins / JENKINS-40733 git-plugin uses same default job parameters on notifyCommit Issue Type: Bug Assignee: Mark Waite Attachments: job1.png, job2.png, parametters.png Components: git-plugin Created: 2016/Dec/30 1:36 PM Priority: Minor Reporter: Hasans Nakipovs If two Multijobs are listening for same repository, same branch and have parameters with same name but with different parameter values then only one value will be used. Example: There is job1 and job2 who listen to same repository and have String parameter with same name. call git notifyCommit which triggers jobs: http://xx/git/notifyCommit?url=""> Scheduled job1 Scheduled job2 No Git consumers using SCM API plugin for: /home/mvndev/plugin_src/git-plugin/.git as result triggered build use both parameters.
[JIRA] (JENKINS-37303) .eachDir() iterate only once
Title: Message Title Daniel Beck resolved as Duplicate Jenkins / JENKINS-37303 .eachDir() iterate only once Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36767) Property hudson.script.noCache breaks the New Item page
Title: Message Title Daniel Beck commented on JENKINS-36767 Re: Property hudson.script.noCache breaks the New Item page Tom FENNELLY Could you release js-modules with the change mentioned above? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40524) Rework agent syntax to be more extensible
Title: Message Title Peter Leibiger commented on JENKINS-40524 Re: Rework agent syntax to be more extensible Michael Neale Sounds good. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38769) Pipeline job hangs when agent loses network connectivity
Title: Message Title recampbell updated an issue Jenkins / JENKINS-38769 Pipeline job hangs when agent loses network connectivity Change By: recampbell Labels: pipeline-hangs robustness Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34909) Handler hang with 100% cpu usage with schedule
Title: Message Title Willi Ecker commented on JENKINS-34909 Re: Handler hang with 100% cpu usage with schedule Same for eg. H 12 31 12 6 Server CPU 100% Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title John Smith commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Sorry, I definitely did not intend to assign myself as the owner of this bug. I suspect that I accidentally pressed one of the JIRA shortcut keys to assign this to myself. I have since disabled keyboard shortcuts because it appears that I am too clumsy to have them enabled. There is a problem related to git credentials and submodules that I intend to resolve, but that work should be done in a separate issue because it is related to git LFS. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36235) Add optional 'timeout' parameter to 'input' step
Title: Message Title
Vsevolod Kalinin commented on JENKINS-36235
Re: Add optional 'timeout' parameter to 'input' step
While in progress the [quite ugly] workaround is
long startTime = System.currentTimeMillis()
try {
timeout(time: timeoutInSeconds, unit: 'SECONDS') {
input 'Test'
}
} catch (err) {
long timePassed = System.currentTimeMillis() - startTime
if (timePassed >= timeoutInSeconds * 1000) {
echo 'Timed out'
} else {
throw err
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40619) Visualizing (list of sequential steps) as groups, as part of one stage
Title: Message Title
Michael Hüttermann commented on JENKINS-40619
Re: Visualizing (list of sequential steps) as groups, as part of one stage
Here a concrete example. The following snippet defines four tasks which are processed in parallel. In Blue Ocean pipeline view, this is wonderfully displayed as four boxes one after the other, see screenshot.
stage 'Check preconditions'
parallel "Sanity check 1": {
echo "1"
}, "Sanity check 2": {
echo "2i"
}, "Sanity check 3": {
echo "3"
}, "Sanity check 4": {
echo "4"
}
The idea now is to define the four example steps as a sequence of steps which have to be processed sequentially and still displayed as four paths as part of the stage (similar to the four parallel paths displayed now when run in parallel). The current solution does not allow that. If I now define sequential steps as part of a stage, the single steps are displayed in the lower part of pipeline view, but the upper part of the pipeline view just shows one graphical control i.e. the stage (which sums up all steps). This is fine, but not as powerful as the requested functionality. With other words, such a notation is requested:
stage 'Check preconditions'
sequential "Sanity check 1": {
echo "1"
}, "Sanity check 2": {
echo "2"
}, "Sanity check 3": {
echo "3"
}, "Sanity check 4": {
echo "4"
}
This would lead to a very similar graphical presentation as the parallel processing, see attachment, but the difference is, that the four parts are run sequentially, not in parallel. It seems to be an implementation detail whether a key word sequential is used or something like group. Looks like JENKINS-38442 offers a generic approach to much more functionality than what is requested here.
Add Comment
[JIRA] (JENKINS-40619) Visualizing (list of sequential steps) as groups, as part of one stage
Title: Message Title Michael Hüttermann updated an issue Jenkins / JENKINS-40619 Visualizing (list of sequential steps) as groups, as part of one stage Change By: Michael Hüttermann Attachment: parallel.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35319) Hide code coverage report links when user lacks "workspace" permission
Title: Message Title mike pipo started work on JENKINS-35319 Change By: mike pipo Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34437) Enable amazon-ecr-plugin behind proxy
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-34437 Re: Enable amazon-ecr-plugin behind proxy Vincent Latombe ok cool, I will make the PR in few days Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40614) L10N: Switch language of UI.
Title: Message Title Michael Hüttermann commented on JENKINS-40614 Re: L10N: Switch language of UI. Test: I've now deactivated Jenkins Locale plugin. Blue Ocean now runs on English. The start condition is different now though: I raised the ticket because, initially, Blue Ocean partly showed German words. It completely switched to English after using the Locale plugin. I'm running on Firefox. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-40712 Re: Exception when using mavenSettingsConfig Hello [~merijn_vogel] and [~kengra], I have successfully used the latest snapshot of the pipeline-maven-plugin ( with including PR https://github.com/jenkinsci/pipeline-maven-plugin/pull/10) with with config-file-provider:2.15.1.Could you test please? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40712) Exception when using mavenSettingsConfig
Title: Message Title Cyrille Le Clerc commented on JENKINS-40712 Re: Exception when using mavenSettingsConfig Hello Merijn Vogel and Kent Granström, I have successfully used the latest snapshot of the pipeline-maven-plugin (with PR https://github.com/jenkinsci/pipeline-maven-plugin/pull/10) with with config-file-provider:2.15.1. Could you test please? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39769) update to latest config-file-provider
Title: Message Title Dominik Bartholdi commented on JENKINS-39769 Re: update to latest config-file-provider Daniel Spilker version 2.15 of config-file-provider is now released, feel free to do a release of your plugin to keep compatibility Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40728) Managed scripts 1.3 breaks promotions
Title: Message Title Dominik Bartholdi commented on JENKINS-40728 Re: Managed scripts 1.3 breaks promotions the only dependency between the promotion plugin and the config-file-provider/managed scripts plugins, is via the job-dsl plugin. And there is an open PR to solve the issue (JENKINS-39769): https://github.com/jenkinsci/job-dsl-plugin/pull/951 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title Markus May commented on JENKINS-39664 Re: Docker builds do not work with Kubernetes Pipeline plugin Should I provide any additional information? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40732) Add closest modifiable ancestor LookupStrategy
Title: Message Title Frédéric Chuong created an issue Jenkins / JENKINS-40732 Add closest modifiable ancestor LookupStrategy Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/Dec/30 9:06 AM Environment: job-dsl 1.53 Labels: job-dsl-plugin folders Priority: Minor Reporter: Frédéric Chuong Given the following item hierarchy: Jenkins root ModifiableFolder (such as com.cloudbees.hudson.plugins.folder.Folder) ComputedFolder (such as org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject) JobDslAwareJob (such as org.jenkinsci.plugins.workflow.job.WorkflowJob with Jenkinsfile making use of the jobDsl pipeline DSL) Without prior knowledge of ModifiableFolder, it is not
[JIRA] (JENKINS-40732) Add closest modifiable ancestor LookupStrategy
Title: Message Title Frédéric Chuong updated an issue Jenkins / JENKINS-40732 Add closest modifiable ancestor LookupStrategy Change By: Frédéric Chuong Environment: Jenkins 2.19.x job-dsl 1.53 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40731) Unhandled Exception: System.NullReferenceException: Your Quality Center session has been disconnected
Title: Message Title mike pipo started work on JENKINS-40731 Change By: mike pipo Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40361) Acceptance test must be runnable in CI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40361 Re: Acceptance test must be runnable in CI Code changed in jenkins User: Wisen Tanasa Path: src/test/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTriggerAcceptanceTest.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/dd252909b88f6bdc2c701b3a53583378507788a8 Log: JENKINS-40361 Use Spock mock and stub correctly. Compare: https://github.com/jenkinsci/jira-trigger-plugin/compare/5e4560ce0122...dd252909b88f Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40361) Acceptance test must be runnable in CI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40361 Re: Acceptance test must be runnable in CI Code changed in jenkins User: Wisen Tanasa Path: src/test/groovy/com/ceilfors/jenkins/plugins/jiratrigger/integration/FakeJiraRunner.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/a3e99a5f7a0dbc1c54de2049c43cb799087d05da Log: JENKINS-40361 Dry rest client methods. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40361) Acceptance test must be runnable in CI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40361 Re: Acceptance test must be runnable in CI Code changed in jenkins User: Wisen Tanasa Path: src/test/groovy/com/ceilfors/jenkins/plugins/jiratrigger/integration/JiraChangelogTriggerConfigurer.groovy src/test/groovy/com/ceilfors/jenkins/plugins/jiratrigger/integration/JiraCommentTriggerConfigurer.groovy src/test/groovy/com/ceilfors/jenkins/plugins/jiratrigger/integration/JiraTriggerConfigurer.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/5e1a35e0f4d0117d0ff7214a43d126e895ab8b79 Log: JENKINS-40361 Rename instance field to jenkins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40361) Acceptance test must be runnable in CI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40361 Re: Acceptance test must be runnable in CI Code changed in jenkins User: Wisen Tanasa Path: src/test/groovy/com/ceilfors/jenkins/plugins/jiratrigger/integration/JiraRunner.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/c143f53170dc7ef5aeeb226bcb5097856d4f89e2 Log: JENKINS-40361 Deprecate shouldBeNotifiedWithComment method. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40361) Acceptance test must be runnable in CI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40361 Re: Acceptance test must be runnable in CI Code changed in jenkins User: Wisen Tanasa Path: src/test/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTriggerAcceptanceTest.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/d8535a48e64039c5d7c10d35a728971c225fee2d Log: JENKINS-40361 Mock JiraClient to the rest of test cases. Do not set JiraClient by default. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40361) Acceptance test must be runnable in CI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40361 Re: Acceptance test must be runnable in CI Code changed in jenkins User: Wisen Tanasa Path: src/main/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTriggerExecutor.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/4e16d34296a93d0b74fb20cc823131b151d819d1 Log: JENKINS-40361 Delete unused field. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40361) Acceptance test must be runnable in CI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40361 Re: Acceptance test must be runnable in CI Code changed in jenkins User: Wisen Tanasa Path: src/test/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTriggerAcceptanceTest.groovy src/test/groovy/com/ceilfors/jenkins/plugins/jiratrigger/integration/JenkinsRunner.groovy src/test/groovy/com/ceilfors/jenkins/plugins/jiratrigger/integration/JiraTriggerConfigurer.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/d6f5d83a43d1b3be9fac84de966a3517c868347d Log: JENKINS-40361 Mock JiraClient on jira reply feature. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
