[JIRA] (JENKINS-41936) configuration not migrated
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41936 Re: configuration not migrated Code changed in jenkins User: David van Laatum Path: src/main/java/hudson/plugins/emailext/GroovyTemplateConfig.java src/main/java/hudson/plugins/emailext/JellyTemplateConfig.java http://jenkins-ci.org/commit/email-ext-plugin/f5f1730d7e8da3eb2943a285031bd0ec2fb46086 Log: JENKINS-41936 configuration not migrated 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-40960) [DOCS] Clarify the way how to specify imagePullSecrets for podTemplate inside Jenkinsfile
Title: Message Title Carlos Sanchez commented on JENKINS-40960 Re: [DOCS] Clarify the way how to specify imagePullSecrets for podTemplate inside Jenkinsfile I think the current state is that you need imagePullSecrets: [[$class: 'PodImagePullSecret', name: 'acrregistrykey']] can you check if that works? 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-36946) Add hint for disabling Empty Ownership boxes
Title: Message Title Oleg Nenashev resolved as Fixed It has been fixed in 0.9 IIRC Jenkins / JENKINS-36946 Add hint for disabling Empty Ownership boxes Change By: Oleg Nenashev 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-41078) Cannot provision via jcloud (google-compute-engine)
Title: Message Title Fritz Elfert commented on JENKINS-41078 Re: Cannot provision via jcloud (google-compute-engine) Hmm, I had that idea (upgrade to 2.1.15.5) yesterday already, but it did not help - at least not with the config file types, provided by the jclouds-plugin. And there is more: The combo box selectors for selecting a comfig file show the id instead of the name after migration from 2.1.13 to 2.1.1[45]. I will tend to all that next weekend - now I have to work (not on jenkins unfortunately). -Fritz 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-35096) Add support for Jenkins Pipeline to the cppcheck-plugin
Title: Message Title
Marten Lootsma edited a comment on JENKINS-35096
Re: Add support for Jenkins Pipeline to the cppcheck-plugin
Thank you for your fast update [~marcosteffan]. Unfortunately building the plugin stops at the tests : , see stack trace below. Building without the test results in a usable HPI with indeed the reported bug fixed. {code}Tests run: 31, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.281 sec <<< FAILURE! - in InjectedTestcom/thalesgroup/hudson/plugins/cppcheck/CppcheckSource/index.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck) Time elapsed: 0.026 sec <<< FAILURE!java.lang.AssertionError: is missing in file:/home/marten/Projects/cppcheck-plugin/target/classes/com/thalesgroup/hudson/plugins/cppcheck/CppcheckSource/index.jelly at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck.runTest(JellyTestSuiteBuilder.java:108) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.jvnet.hudson.test.junit.GroupedTest.runGroupedTests(GroupedTest.java:67) at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite.doTests(JellyTestSuiteBuilder.java:152) at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite.access$100(JellyTestSuiteBuilder.java:138) at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite$2.call(JellyTestSuiteBuilder.java:160) at org.jvnet.hudson.test.HudsonTestCase$WebClient$5.run(HudsonTestCase.java:1610) at org.jvnet.hudson.test.ClosureExecuterAction.doIndex(ClosureExecuterAction.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108) at org.kohsuke.stapler.IndexDispatcher.dispatch(IndexDispatcher.java:26) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) 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 hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:86) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty
[JIRA] (JENKINS-41319) Not compatible with Pipeline restart feature
Title: Message Title Nicolas De Loof closed an issue as Won't Fix One-shot executor is designed to change the build:slave paradigm, relying on plain ephemeral nodes. The way pipeline expect executor to resurrect after a reboot just is incompatible, one-shot should just not be used in this context. Jenkins / JENKINS-41319 Not compatible with Pipeline restart feature Change By: Nicolas De Loof Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-35096) Add support for Jenkins Pipeline to the cppcheck-plugin
Title: Message Title Marten Lootsma commented on JENKINS-35096 Re: Add support for Jenkins Pipeline to the cppcheck-plugin Thank you for your fast update Marco Steffan. Unfortunately building the plugin stops at the tests: Tests run: 31, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.281 sec <<< FAILURE! - in InjectedTest com/thalesgroup/hudson/plugins/cppcheck/CppcheckSource/index.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck) Time elapsed: 0.026 sec <<< FAILURE! java.lang.AssertionError: default='true'?> is missing in file:/home/marten/Projects/cppcheck-plugin/target/classes/com/thalesgroup/hudson/plugins/cppcheck/CppcheckSource/index.jelly at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck.runTest(JellyTestSuiteBuilder.java:108) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.jvnet.hudson.test.junit.GroupedTest.runGroupedTests(GroupedTest.java:67) at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite.doTests(JellyTestSuiteBuilder.java:152) at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite.access$100(JellyTestSuiteBuilder.java:138) at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite$2.call(JellyTestSuiteBuilder.java:160) at org.jvnet.hudson.test.HudsonTestCase$WebClient$5.run(HudsonTestCase.java:1610) at org.jvnet.hudson.test.ClosureExecuterAction.doIndex(ClosureExecuterAction.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108) at org.kohsuke.stapler.IndexDispatcher.dispatch(IndexDispatcher.java:26) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) 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 hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:86) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter
[JIRA] (JENKINS-41078) Cannot provision via jcloud (google-compute-engine)
Title: Message Title Dominik Bartholdi commented on JENKINS-41078 Re: Cannot provision via jcloud (google-compute-engine) Fritz Elfert tahts a bug in the config-file-provider and was fixed a couple of days a go, I'll update the PR to depend on the latest version Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41078) Cannot provision via jcloud (google-compute-engine)
Title: Message Title Dominik Bartholdi edited a comment on JENKINS-41078 Re: Cannot provision via jcloud (google-compute-engine) [~felfert] tahts thats a bug in the config-file-provider and was fixed a couple of days a go, I'll update the PR to depend on the latest version Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41972) Slow page loading and page unresponsive in version 2.44
Title: Message Title Oleg Nenashev commented on JENKINS-41972 Re: Slow page loading and page unresponsive in version 2.44 Please provide more information, there is nothing to diagnose in the ticket. Plugins like Monitoring Pluhin and Support Core plugin can help to gather the data. 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-41971) Support for parameters in editor
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41971 Support for parameters in editor Change By: James Dumay Sprint: post-release 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-41970) Configurable retention of runs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41970 Configurable retention of runs Change By: James Dumay Sprint: post-release 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-41959) Supporting "post" steps at Pipeline and Stage level
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41959 Supporting "post" steps at Pipeline and Stage level Change By: James Dumay Sprint: post-release iapetus 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-41961) Developer can change the order of stages
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41961 Developer can change the order of stages Change By: James Dumay Sprint: post-release iapetus 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-41969) Support "when" in stage level config
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41969 Support "when" in stage level config Change By: James Dumay Sprint: post-release 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-41966) Entering and exiting the editor
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41966 Entering and exiting the editor Change By: James Dumay *Entry points** Creation (when there is no Jenkinsfile in the repository)* For a specific branch on the Branches tab* For a specific branch on the run screen*Saving options*Very similar to Githubs web file editing workflow.We present a dialog that allows users to:* Specify a commit message* Specify a commit description* Radio list** Commit to $CURRENT_BRANCH** Commit to new branch*** Text box: branch name* Buttons** Save - commits the Jenkinsfile** Cancel - exists this dialog and returns to the editor_Github example_ !github-new-file.png|thumbnail! *Authenticating* When saving we may have to ask for a "upgrade" to the stored Github token. Writing to the repository needs different scopes than what we may have setup during creation.*Editor header buttons** Save - triggers the save dialog* Try** Needs to be defined** Cancel - exists the editor without saving, goes back to entry point Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41966) Entering and exiting the editor
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41966 Entering and exiting the editor Change By: James Dumay *Entry points** Creation (when there is no Jenkinsfile in the repository)* For a specific branch on the Branches tab* For a specific branch on the run screen*Saving options*Very similar to Githubs web file editing workflow.We present a dialog that allows users to:* Specify a commit message* Specify a commit description* Radio list** Commit to $CURRENT_BRANCH** Commit to new branch*** Text box: branch name* Buttons** Save - commits the Jenkinsfile** Cancel - exists this dialog and returns to the editor_Github example_ !github-new-file.png|thumbnail! *Authenticating*When saving we may have to ask for a "upgrade" to the stored Github token. Writing to the repository needs different scopes than what we may have setup during creation. I'd imagine this looks very similar to the creation way of doing it (asking for a Key) *Editor header buttons** Save - triggers the save dialog* Try** Needs to be defined** Cancel - exists the editor without saving, goes back to entry point Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41966) Entering and exiting the editor
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41966 Entering and exiting the editor Change By: James Dumay *Entry points** Creation (when there is no Jenkinsfile in the repository)* For a specific branch on the Branches tab* For a specific branch on the run screen*Saving options*Very similar to Githubs web file editing workflow.We present a dialog that allows users to:* Specify a commit message* Specify a commit description* Radio list** Commit to $CURRENT_BRANCH** Commit to new branch*** Text box: branch name* Buttons** Save - commits the Jenkinsfile** Cancel - exists this dialog and returns to the editor_Github example_ !github-new-file.png|thumbnail! When saving we may have to ask for a "upgrade" to the stored Github token. Writing to the repository needs different scopes than what we may have setup during creation. *Editor header buttons** Save - triggers the save dialog* Try** Needs to be defined** Cancel - exists the editor without saving, goes back to entry point Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41869) Pipeline views header max width of 1200px
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41869 Pipeline views header max width of 1200px Change By: Brody Maclean Summary: Pipeline views header and body max width of 1200px 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-41869) Pipeline views header max width of 1200px
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41869 Pipeline views header max width of 1200px Change By: Brody Maclean Constrain the width of the Pipeline views header and body to 1200px, to align with the rest of BO. - If logs need to be wider we may role back but want to keep BO tidy and consistent. - Invision https://invis.io/Q2A110KM9#/218685699_Failed_Tests_1200pxZeplin https://zpl.io/Z4q3x2 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-41972) Slow page loading and page unresponsive in version 2.44
Title: Message Title Ed Sherwin Nonog created an issue Jenkins / JENKINS-41972 Slow page loading and page unresponsive in version 2.44 Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2017/Feb/13 6:32 AM Priority: Blocker Reporter: Ed Sherwin Nonog 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-41923) Different pipeline steps are executed in different directories
Title: Message Title Roberto Fasciolo commented on JENKINS-41923 Re: Different pipeline steps are executed in different directories Yes, adding reuseNode true seems to work around the issue. However it's very confusing if different steps of the same pipeline are executed in different directories as it means that the second step is potentially not working on the output of the first step (therefore, IMHO, breaking the whole concept of pipeline). I attached now here a cleaned-up version of the Jenkinsfile I've been using in my real project: Jenkinsfile-real. As you can see it first runs the gradle build (which generates a Dockerfile in the build directory), then a QA step and then it tries to generate a docker image. In the shape the pipeline is at the moment the docker image generation fails because there's no Dockerfile in the build directory. 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-41923) Different pipeline steps are executed in different directories
Title: Message Title Roberto Fasciolo updated an issue Jenkins / JENKINS-41923 Different pipeline steps are executed in different directories Change By: Roberto Fasciolo Attachment: Jenkinsfile-real 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-34742) FilePath#installIfNecessaryFrom consistently fails to download certain files
Title: Message Title Tiernan Messmer commented on JENKINS-34742 Re: FilePath#installIfNecessaryFrom consistently fails to download certain files I noticed gzip handling is being done by JZlib not apache commons compress (I had mistakenly assumed commons compress was handling both gzip and tar). The fact that it is relying on the size in the footer indicates it would likely also fail on >4GB (uncompressed) gz files. Changing to commons compress (which I believe handles >4GB) in FilePath would likely resolve this as a side effect to allow it to handle malformed gz files in addition to being able to handle >4GB gz files. 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-34742) FilePath#installIfNecessaryFrom consistently fails to download certain files
Title: Message Title Tiernan Messmer commented on JENKINS-34742 Re: FilePath#installIfNecessaryFrom consistently fails to download certain files On further investigation, this is caused by the same issue as JENKINS-39515 - The gz files on the golang site have an incorrect size in the gzip footer field. https://github.com/golang/go/issues/19052 has more 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-41427) artifactory buildinfo upload fails on upload
Title: Message Title Eyal Ben Moshe commented on JENKINS-41427 Re: artifactory buildinfo upload fails on upload To get a better sense of the issue, does any of the other Artifactory Pipeline examples work for you? If you choose the simplest example from: https://github.com/JFrogDev/project-examples/tree/master/jenkins-pipeline-examples Do you manage do have build-info deployed to Artifactory? 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-39515) Failed to install Go 1.7.3
Title: Message Title Tiernan Messmer commented on JENKINS-39515 Re: Failed to install Go 1.7.3 Interesting indeed. I checked 1.6.2 linux tarball and it was fine contrary to what is mentioned in that repository, but then I noticed the linked tarballs were for darwin not linux, so I re-ran my test against some of those files and it now matches the results, where 1.4.3 fails (but 1.4.2 works), and 1.5.1 works, while 1.5.2+ fails I'm not sure why this issue started appearing on the darwin builds before it started appearing on the linux builds, but it definitely appears to be the same problem! Size of go1.4.2.darwin-amd64-osx10.8.tar.gz from header 230127616 gunzipped size of go1.4.2.darwin-amd64-osx10.8.tar.gz230127616 Size of go1.4.3.darwin-amd64.tar.gz from header 683008 gunzipped size of go1.4.3.darwin-amd64.tar.gz221932544 Size of go1.5.darwin-amd64.tar.gz from header286595584 gunzipped size of go1.5.darwin-amd64.tar.gz 286595584 Size of go1.5.1.darwin-amd64.tar.gz from header 286660096 gunzipped size of go1.5.1.darwin-amd64.tar.gz286660096 Size of go1.5.2.darwin-amd64.tar.gz from header 242176 gunzipped size of go1.5.2.darwin-amd64.tar.gz281260544 Size of go1.6.2.darwin-amd64.tar.gz from header 222720 gunzipped size of go1.6.2.darwin-amd64.tar.gz321086976 (command used to generate the above is linked in the go github issue) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40177) Use BitBucket Server project icon for jenkins folder icon
Title: Message Title Tiernan Messmer commented on JENKINS-40177 Re: Use BitBucket Server project icon for jenkins folder icon I notice there's some commented out code in BitbucketTeamMetadataAction.java for getAvatarImageOf with the comment "TODO when bitbucket supports serving avatars with a size request - currently only works if using gravatar or server". Is there anything blocking this being enabled when BitBucket Server is in use and keeping current behaviour when BitBucket Cloud is in use until such a time it supports serving avatars with a size parameter? 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-39346) Cryptic serialization error when SimpleBuildWrapper throws AbortException in pipeline
Title: Message Title Lars Lawoko updated an issue Jenkins / JENKINS-39346 Cryptic serialization error when SimpleBuildWrapper throws AbortException in pipeline Change By: Lars Lawoko Environment: Jenkins 2. 7.3 45 Pipeline 2. 4 10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39521) Full Log does not render newlines - or use correct content type (weird HTML like artifacts)
Title: Message Title Michael Neale commented on JENKINS-39521 Re: Full Log does not render newlines - or use correct content type (weird HTML like artifacts) Oleg Korsak that one has been fixed in master and will be out in next release. 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-39515) Failed to install Go 1.7.3
Title: Message Title Christopher Orr commented on JENKINS-39515 Re: Failed to install Go 1.7.3 Interesting, but this problem has been around since at least Go 1.4.3 (though it could possible be the same issue): https://github.com/orrc/jenkins-filepath-untar#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-41869) Pipeline views header and body max width of 1200px
Title: Message Title Michael Neale commented on JENKINS-41869 Re: Pipeline views header and body max width of 1200px logs will need to be wider (and some peoples pipelines too) - so not sure if this is right. 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-41685) incorrect event received with workflow-api 2.8
Title: Message Title James Dumay commented on JENKINS-41685 Re: incorrect event received with workflow-api 2.8 Can't bump dependencies until we get this one fixed. See results. 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-41971) Support for parameters in editor
Title: Message Title Michael Neale commented on JENKINS-41971 Re: Support for parameters in editor Keith Zantow not sure what is known via metadata/model about job property types - is there anything in 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-41971) Support for parameters in editor
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41971 Support for parameters in editor Issue Type: New Feature Assignee: Brody Maclean Components: blueocean-pipeline-editor-plugin, blueocean-plugin Created: 2017/Feb/13 4:49 AM Priority: Minor Reporter: Michael Neale A user of the pipeline should be able to set, at a pipeline level, what parameters are required. This is configuring the inputs as can be seen in parametrised jobs (so you can refer to the design for parametrised jobs if it helps, for the types of fields configurable). In scope: User can set what fields are required and their type Design should also work when configuring "input" step type (even if input configuration is not implemented initially, as it is the same logic). Add Comment
[JIRA] (JENKINS-41869) Pipeline views header and body max width of 1200px
Title: Message Title Brody Maclean assigned an issue to Josh McDonald Jenkins / JENKINS-41869 Pipeline views header and body max width of 1200px Change By: Brody Maclean Assignee: Brody Maclean Josh McDonald 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-41869) Pipeline views header and body max width of 1200px
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41869 Pipeline views header and body max width of 1200px Change By: Brody Maclean Constrain the width of the Pipeline views header and body to 1200px, to align with the rest of BO.If logs need to be wider we may role back but want to keep BO tidy and consistent. Invision https://invis.io/Q2A110KM9#/218685699_Failed_Tests_1200pxZeplin https://zpl.io/Z4q3x2 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-41685) incorrect event received with workflow-api 2.8
Title: Message Title James Dumay commented on JENKINS-41685 Re: incorrect event received with workflow-api 2.8 Note that we still have these tests failing after upgrading workflow-api io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeTest.abortInput io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeTest.waitForInputTest io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeTest.submitInput io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeTest.nodesWithPartialParallels 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-41970) Configurable retention of runs
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41970 Configurable retention of runs Change By: Michael Neale At a pipeline level in the editor , a user may wish to configure a maximum number of runs, or age of runs to retain (to save storage). This is stored in job properties. (design required). 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-41970) Configurable retention of runs
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41970 Configurable retention of runs Issue Type: New Feature Assignee: Brody Maclean Components: blueocean-pipeline-editor-plugin, blueocean-plugin Created: 2017/Feb/13 4:40 AM Priority: Minor Reporter: Michael Neale At a pipeline level, a user may wish to configure a maximum number of runs, or age of runs to retain (to save storage). This is stored in job properties. (design required). Add Comment This message was sent b
[JIRA] (JENKINS-41969) Support "when" in stage level config
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41969 Support "when" in stage level config Issue Type: New Feature Assignee: Brody Maclean Components: blueocean-pipeline-editor-plugin, blueocean-plugin Created: 2017/Feb/13 4:24 AM Priority: Minor Reporter: Michael Neale A pipeline author will occasionally need to set criteria on which a stage is "skipped" or applied. This uses the "when" construct: (full docs here: https://jenkins.io/doc/book/pipeline/syntax/ search for "when" if you are curious). In Scope: User can choose a stage an optionally provide a condition underwhich it will run (called a "when") This may be one of: * branch name specified (string) * environment variable name and its value (when that variable = value, it will be allowed to run) * a text box that allows an arbitrary _expression_ to be entered
[JIRA] (JENKINS-41969) Support "when" in stage level config
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41969 Support "when" in stage level config Change By: Michael Neale Priority: Minor Major 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-41868) Locks within parallel tasks release other locks within the pipeline
Title: Message Title Mark Nysen commented on JENKINS-41868 Re: Locks within parallel tasks release other locks within the pipeline This may be the same issue seen in JENKINS-41183 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-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title
Mike Kobit commented on JENKINS-35230
Re: The environment variables of git plugin not working in pipeline script.
Little bit more research into this:
Run is an Actionable, so doing something like final BuildData buildData = run.getAction(BuildData.class); works to obtain that Action data.
GitSCM has a method buildEnvVars that seems to compute most of the environment variables. Maybe this can be abstracted out to be usable from both points?
So, a very basic implementation that I got working locally with the Bitbucket Branch Source Plugin could look like:
package jenkins.plugins.git;
import static hudson.Util.fixEmpty;
import com.google.common.collect.Iterables;
import hudson.EnvVars;
import hudson.Extension;
import hudson.model.EnvironmentContributor;
import hudson.model.Run;
import hudson.model.TaskListener;
import hudson.plugins.git.Branch;
import hudson.plugins.git.GitSCM;
import hudson.plugins.git.Revision;
import hudson.plugins.git.util.BuildData;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import java.io.IOException;
import javax.annotation.Nonnull;
@Extension
public class GitContributor extends EnvironmentContributor {
private static final Logger LOG = LoggerFactory.getLogger(GitContributor.class);
@Override
public void buildEnvironmentFor(@Nonnull final Run run,
@Nonnull final EnvVars envs,
@Nonnull final TaskListener listener)
throws IOException, InterruptedException {
final BuildData buildData = run.getAction(BuildData.class);
// This is all essentially copy pasted from GtiSCM
if (buildData != null) {
final Revision rev = buildData.getLastBuiltRevision();
if (rev!=null) {
Branch branch = Iterables.getFirst(rev.getBranches(), null);
if (branch!=null && branch.getName()!=null) {
String remoteBranchName = branch.getName();
if(remoteBranchName.startsWith("refs/remotes/")) {
//Restore expected previous behaviour
remoteBranchName = remoteBranchName.substring("refs/remotes/".length());
}
envs.put(GitSCM.GIT_BRANCH, remoteBranchName);
}
String sha1 = fixEmpty(rev.getSha1String());
if (sha1 != null && !sha1.isEmpty()) {
envs.put(GitSCM.GIT_COMMIT, sha1);
}
}
}
}
}
[JIRA] (JENKINS-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Mark Waite commented on JENKINS-35230 Re: The environment variables of git plugin not working in pipeline script. Unfortunately, I don't have any great ideas to offer, though I suspect that Jesse Glick has a reference implementation in the mercurial plugin. You might look at buildEnvVarsFromActionable. Jesse has tried to keep the mercurial plugin as a really good SCM reference implementation. I suspect that its implementation of exporting environment variables to pipeline jobs is also a good reference implementation. 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-39521) Full Log does not render newlines - or use correct content type (weird HTML like artifacts)
Title: Message Title Ivan Meredith started work on JENKINS-39521 Change By: Ivan Meredith Status: Reopened 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-41242) Blue Ocean views should include core version in footer
Title: Message Title Ivan Meredith updated JENKINS-41242 Jenkins / JENKINS-41242 Blue Ocean views should include core version in footer Change By: Ivan Meredith 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-41733) Review all the table columns and their responsive rules
Title: Message Title Brody Maclean closed an issue as Duplicate Jenkins / JENKINS-41733 Review all the table columns and their responsive rules Change By: Brody Maclean Status: In Progress Closed 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-41545) Empty states
Title: Message Title Brody Maclean assigned an issue to James Dumay Jenkins / JENKINS-41545 Empty states Change By: Brody Maclean Assignee: Brody Maclean 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 Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-39515) Failed to install Go 1.7.3
Title: Message Title Tiernan Messmer commented on JENKINS-39515 Re: Failed to install Go 1.7.3 There appears to be an issue with the gzip footer contents of the files hosted which the apache commons gzip library can not handle. https://github.com/golang/go/issues/19052 has more details. 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] (TEST-100) How to Launch a openstack windows instance from Jenkins
Title: Message Title jenkins jen started work on TEST-100 Change By: jenkins jen 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] (TEST-100) How to Launch a openstack windows instance from Jenkins
Title: Message Title jenkins jen stopped work on TEST-100 Change By: jenkins jen Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41582) Change official docker image to not use alpine
Title: Message Title Michael Neale started work on JENKINS-41582 Change By: Michael Neale 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-41582) Change official docker image to not use alpine
Title: Message Title Michael Neale commented on JENKINS-41582 Re: Change official docker image to not use alpine I think what I prefer is: https://github.com/jenkinsci/blueocean-plugin/pull/815 which whilst it doesn't include the kitchen sink of dev tools, people have the option to add them in pretty easily as needed (so image size does not blow out for those who use distributed builds and slaves). 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-41341) Standardize form descriptions
Title: Message Title James Dumay updated JENKINS-41341 Jenkins / JENKINS-41341 Standardize form descriptions 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-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title Karl Shultz commented on JENKINS-41945 Re: Eventual NPE while running many concurrent declarative pipelines Ran a test with 60 declarative pipelines running every minute, instead of 100. Still hit an out of memory condition. I'll attach a tarball of the logs. Inside that, jenkins.log.1 has a lot more historical data in it. jenkins.log is sort of its last gasp. Jenkins also generated an error report file. I'll attach that as well. logs.tar.gz hs_err_pid27051.log 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-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-41945 Eventual NPE while running many concurrent declarative pipelines Change By: Karl Shultz Attachment: logs.tar.gz Attachment: hs_err_pid27051.log 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-41193) Add log API for Org scanning and MBP indexing
Title: Message Title James Dumay resolved as Postponed Obsolete Jenkins / JENKINS-41193 Add log API for Org scanning and MBP indexing Change By: James Dumay Status: Open Resolved Resolution: Postponed 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-41579) API for Pipeline level for causeOfBlockage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41579 API for Pipeline level for causeOfBlockage Change By: James Dumay Sprint: release candidate, pannonian , iapetus 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Michael Neale commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit good to hear Stephen Connolly. 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-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title Nikolas Falco closed an issue as Fixed Fixed in 1.0.x This issue is similar to JENKINS-28578 Jenkins / JENKINS-28578 The NodeJS plugin breaks the Xvnc plugin Change By: Nikolas Falco Status: Open Closed 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-41968) Release management of Semantic Versioning plugin seems broken
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-41968 Release management of Semantic Versioning plugin seems broken Issue Type: Bug Assignee: Steven Christou Components: semantic-versioning-plugin Created: 2017/Feb/13 1:51 AM Priority: Major Reporter: Allan BURDAJEWICZ Although the semantic versioning plugin version 1.11 has been releases, it does not show up in the Update Center: https://updates.jenkins.io/current/update-center.actual.json The release does not show up in the maven repo: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/semantic-versioning-plugin/ Obsolete parent POM and no distributionManagement override means the repo URL is wrong. These releases don't get uploaded. Add Comment
[JIRA] (JENKINS-41948) Scanning MultiBranchProject fails and logs NoSuchMethodError
Title: Message Title Alastair D'Silva commented on JENKINS-41948 Re: Scanning MultiBranchProject fails and logs NoSuchMethodError Downgrading tho branch api 2.0.2 resolves the problem, looks like that method was deleted (rather than deprecated) since then. 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-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title
Nikolas Falco edited a comment on JENKINS-41857
Re: Correct path for installation is not provided to system/shells (build.steps)
In the workaround branch I've integrate most recent master commits that fix regression introduced with pipeline work. So please consider to build again.This build was used to reproduce your use case:# install a Jenkins 2.44 on a Windows 10 machine.# in setup page I skip any plugin from install.# install only the following plugins (need by your config):#* custom NodeJS [7ec6423|https://github.com/jenkinsci/nodejs-plugin/commit/7ec6423a5e3d0a353406e5528de2f45d8d214689]#* job-restrictions#* git-parameter#* throttle-concurrents#* shelve-project-plugin#* cobertura#* bitbucket-build-status-notifier#* envinject# configure a macviabuild01 node started by JNPL (Java Web Start)# create ShopAtHome Extension Core freestyle job# copy your config.xml in on top the existing# restart Jenkins# setup NodeJS configuration tool like in your screenshot# edit job configuration to remove:#* any SCM#* comment gulp command#* remove any job parameterFollow the output:{noformat}Started by user anonymous[EnvInject] - Loading node environment variables.Building remotely on viamacbuild01 in workspace /Users/me/jenkinsslave/workspace/ShopAtHome Extension CoreUnpacking https://nodejs.org/dist/v5.9.1/node-v5.9.1-darwin-x64.tar.gz to /Users/nikolasfalco/jenkinsslave/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/5.9.1 on viamacbuild01/Users/me/jenkinsslave/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/5.9.1/bin/npm install -g gulp jshint karma-phantomjs-launchernpm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue...CUTTED...npm WARN karma-phantomjs-launcher@1.0.2 requires a peer of karma@>=0.9 but none was installed.[ShopAtHome Extension Core] $ /bin/sh -xe /var/folders/jq/2l9t7bw1103_jjyv9rzk7kcrgn/T/hudson134818345472423975.sh+ echo /Users/me/jenkinsslave/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/5.9.1/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin/Users/me/jenkinsslave/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/5.9.1/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin+ npm installnpm WARN enoent ENOENT: no such file or directory, open '/Users/me/jenkinsslave/workspace/ShopAtHome Extension Core/package.json'npm WARN ShopAtHome Extension Core No descriptionnpm WARN ShopAtHome Extension Core No repository field.npm WARN ShopAtHome Extension Core No README datanpm WARN ShopAtHome Extension Core No license field.{noformat}The path in echo command was right and npm command was found but fail due no package.json in workspace (miss source code).In the future I will merge to this branch only released commits to avoid work in progress issues
Add Comment
[JIRA] (JENKINS-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Nikolas Falco commented on JENKINS-41857 Re: Correct path for installation is not provided to system/shells (build.steps) In the workaround branch I've integrate most recent master commits that fix regression introduced with pipeline work. So please consider to build again. This build was used to reproduce your use case: install a Jenkins 2.44 on a Windows 10 machine. in setup page I skip any plugin from install. install only the following plugins (need by your config): custom NodeJS 7ec6423 job-restrictions git-parameter throttle-concurrents shelve-project-plugin cobertura bitbucket-build-status-notifier envinject configure a macviabuild01 node started by JNPL (Java Web Start) create ShopAtHome Extension Core freestyle job copy your config.xml in on top the existing restart Jenkins setup NodeJS configuration tool like in your screenshot edit job configuration to remove: any SCM comment gulp command remove any job parameter Follow the output: Started by user anonymous [EnvInject] - Loading node environment variables. Building remotely on viamacbuild01 in workspace /Users/me/jenkinsslave/workspace/ShopAtHome Extension Core Unpacking https://nodejs.org/dist/v5.9.1/node-v5.9.1-darwin-x64.tar.gz to /Users/nikolasfalco/jenkinsslave/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/5.9.1 on viamacbuild01 /Users/me/jenkinsslave/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/5.9.1/bin/npm install -g gulp jshint karma-phantomjs-launcher npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue ...CUTTED... npm WARN karma-phantomjs-launcher@1.0.2 requires a peer of karma@>=0.9 but none was installed. [ShopAtHome Extension Core] $ /bin/sh -xe /var/folders/jq/2l9t7bw1103_jjyv9rzk7kcrgn/T/hudson134818345472423975.
[JIRA] (JENKINS-41874) Regression: Loading worm is blue
Title: Message Title Keith Zantow updated JENKINS-41874 Jenkins / JENKINS-41874 Regression: Loading worm is blue Change By: Keith Zantow 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-40624) nodejs installer not compatible with declarative pipeline definition
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40624 Re: nodejs installer not compatible with declarative pipeline definition Code changed in jenkins User: Nikolas Falco Path: src/main/java/jenkins/plugins/nodejs/NodeJSCommandInterpreter.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstallation.java http://jenkins-ci.org/commit/nodejs-plugin/240e4dd95a0db65453e7c11ccd350900973dc403 Log: Fix regression of JENKINS-40624 in path construction of executable and bin folder because all API similar to java.lang.File have to be wrapped in a callable executed on the target node or paths will be calculated based on the master node O.S. 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-41967) AWS Credentials Plugin v1.17+ is not API-compatible with ec2-plugin
Title: Message Title Arcadiy Ivanov created an issue Jenkins / JENKINS-41967 AWS Credentials Plugin v1.17+ is not API-compatible with ec2-plugin Issue Type: Bug Assignee: Nicolas De Loof Components: aws-credentials-plugin, ec2-plugin Created: 2017/Feb/13 1:12 AM Priority: Critical Reporter: Arcadiy Ivanov The AWSCredentialImpl API has changed in v1.17+: https://github.com/jenkinsci/aws-credentials-plugin/commit/d12ab1def72f1577abf282a5d223aaa17f22c68e#diff-c0710975ba9b6383fc743f063dfb420dR71 This will result in the following code simply breaking for lack of constructor signature: https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/EC2Cloud.java#L231 Add Comment
[JIRA] (JENKINS-41966) Entering and exiting the editor
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41966 Entering and exiting the editor Change By: James Dumay *Entry points** Creation (when there is no Jenkinsfile in the repository)* For a specific branch on the Branches tab* For a specific branch on the run screen*Saving options*Very similar to Githubs web file editing workflow.We present a dialog that allows users to:* Specify a commit message* Specify a commit description* * Radio list** Commit to $CURRENT_BRANCH** Commit to new branch*** Text box: branch name* Buttons** Save - commits the Jenkinsfile** Cancel - exists this dialog and returns to the editor_Github example_ !github-new-file.png|thumbnail! *Editor header buttons** Save - triggers the save dialog* Try** Needs to be defined** Cancel - exists the editor without saving, goes back to entry point 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 un
[JIRA] (JENKINS-41966) Entering and exiting the editor
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41966 Entering and exiting the editor Change By: James Dumay *Entry points** Creation (when there is no Jenkinsfile in the repository)* For a specific branch on the Branches tab* For a specific branch on the run screen*Saving options*Very similar to Githubs web file editing workflow.We present a dialog that allows users to:* Specify a commit message* Specify a commit description** Radio list** Commit to $CURRENT_BRANCH** Commit to new branch*** Text box: branch name* Buttons** Save - commits the Jenkinsfile** Cancel - exists this dialog and returns to the editor_Github example_ !github-new-file.png|thumbnail! *Editor header buttons** Save - triggers the save dialog* Try** Needs to be defined* ] * Cancel - exists the editor without saving, goes back to entry point 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 u
[JIRA] (JENKINS-41966) Entering and exiting the editor
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41966 Entering and exiting the editor Change By: James Dumay *Entry points** Creation (when there is no Jenkinsfile in the repository)* For a specific branch on the Branches tab* For a specific branch on the run screen*Saving options*Very similar to Githubs web file editing workflow.We present a dialog that allows users to:* Specify a commit message* Specify a commit description** Radio list** Commit to $CURRENT_BRANCH** Commit to new branch*** Text box: branch name* Buttons** Save - commits the Jenkinsfile** Cancel - exists this dialog and returns to the editor_Github example_ !github-new-file.png|thumbnail! *Editor header buttons** Save - triggers the save dialog* Try - * * Needs to be defined* ] * * On success there is an option on the run screen to "save" the changes* Cancel - exists the editor without saving, goes back to entry point Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this mes
[JIRA] (JENKINS-41966) Entering and exiting the editor
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41966 Entering and exiting the editor Change By: James Dumay *Entry points** Creation (when there is no Jenkinsfile in the repository)* For a specific branch on the Branches tab* For a specific branch on the run screen*Saving options*Very similar to Githubs web file editing workflow.We present a dialog that allows users to:* Specify a commit message* Specify a commit description** Radio list** Commit to $CURRENT_BRANCH** Commit to new branch*** Text box: branch name * Buttons ** Save - commits the Jenkinsfile** Cancel - exists this dialog and returns to the editor _Github example_ !github-new-file.png|thumbnail! *Editor header buttons** Save - triggers the save dialog* Try - *Needs to be defined*** On success there is an option on the run screen to "save" the changes* Cancel - exists the editor without saving, goes back to entry point Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message
[JIRA] (JENKINS-41966) Entering and exiting the editor
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41966 Entering and exiting the editor Issue Type: Improvement Assignee: Brody Maclean Attachments: github-new-file.png Components: blueocean-plugin Created: 2017/Feb/13 12:50 AM Priority: Major Reporter: James Dumay Entry points Creation (when there is no Jenkinsfile in the repository) For a specific branch on the Branches tab For a specific branch on the run screen Saving options Very similar to Githubs web file editing workflow. We present a dialog that allows users to: Specify a commit message Specify a commit description Radio list Commit to $CURRENT_BRANCH Commit to new branch Text box: branch name Github example
[JIRA] (JENKINS-37701) Manual trigger not running in build pipeline
Title: Message Title Kalyan Koduru commented on JENKINS-37701 Re: Manual trigger not running in build pipeline We ran into the same issue, and had to move the jobs, and pipeline from folders into "global view" to get the manual triggers work. Delivery Pipeline has the same issue as it uses Build Pipeline 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-41763) Show a column with the Java version of an agent
Title: Message Title Baptiste Mathus commented on JENKINS-41763 Re: Show a column with the Java version of an agent Christoph Obexer nope, but I actually already have the addition for that on my machine since ~November, but it stayed there because it's missing tests and I wanted to also ask sogabe if he was still working on the plugin or if I should adopt it. Also, I have in mind to propose a subject for GSoC about Java versions hints/improvements. I need to think about it more. Please feel free to ping me in late Feb if you have no news about this until then. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41965) Pipeline onboarding/walkthrough
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41965 Pipeline onboarding/walkthrough Issue Type: Improvement Assignee: Brody Maclean Components: blueocean-pipeline-editor-plugin Created: 2017/Feb/12 11:47 PM Priority: Major Reporter: James Dumay We want to guide new users to blueocean to create their first pipeline using the editor. This may include guiding users outside of the editor to use Blue Ocean. For the first time use of the Editor we need to teach them what stages, steps and parallels are and guide them to steps they are likely to want to use. Perhaps we even have a curated step listing for this first time use with only 5-6 common steps and a "show more". They could toggle between the curated step list and show more. Add Comment
[JIRA] (JENKINS-41963) Developer can configure tools
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41963 Developer can configure tools Change By: James Dumay *In Scope** Developer can configure tools* "Tools" only become available when a non-docker agent configuration is selected ** Cannot be used in Docker agents for technical and best practice reasons ** Tools should appear directly under the agent section 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-41963) Developer can configure tools
Title: Message Title James Dumay assigned an issue to Keith Zantow Jenkins / JENKINS-41963 Developer can configure tools Change By: James Dumay Assignee: Brody Maclean Keith Zantow 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-41964) Editor needs to go into regular page with header
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41964 Editor needs to go into regular page with header Issue Type: Improvement Assignee: Keith Zantow Attachments: header.png Components: blueocean-pipeline-editor-plugin Created: 2017/Feb/12 11:27 PM Priority: Minor Reporter: James Dumay In scope Move the design of the editor to use the new header instead of the full screen modal Add Comment
[JIRA] (JENKINS-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Mike Kobit commented on JENKINS-35230 Re: The environment variables of git plugin not working in pipeline script. I was making an attempt at fixing this today by trying to follow along with the implementation at https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/BranchNameContributor.java - my knowledge gaps of the Jenkins source code make it difficult to figure out how to actually implement this. So, any help from other core plugin authors or maintainers would be highly appreciated. EnvironmentContributor seems like the right class to extend from here EnvironmentContributor.buildEnvironmentFor is available for both Job and Run BranchNameContributor gets the BranchProjectFactory of the parent job and uses it to check if this BranchNameContributor uses types like ContributorMetadataAction and other actions to get metadata How do I obtain the Git metadata associated with a Job or Run (it seems like it should be associated with a certain Run? Will reflection be needed to get the workflow execution and revision info from the Run? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You re
[JIRA] (JENKINS-41963) Developer can configure tools
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41963 Developer can configure tools Change By: James Dumay Sprint: post-release 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-35801) Replay of a run with modified Jenkinsfile
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35801 Replay of a run with modified Jenkinsfile Change By: James Dumay Priority: Major Minor 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-41961) Developer can change the order of stages
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41961 Developer can change the order of stages Change By: James Dumay Sprint: post-release 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-41962) Environment variable and Tools widget needs a better empty state
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41962 Environment variable and Tools widget needs a better empty state Change By: James Dumay Sprint: post-release 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-41960) Developer can change the stage level configuration
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41960 Developer can change the stage level configuration Change By: James Dumay Sprint: post-release 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-41962) Environment variable and Tools widget needs a better empty state
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41962 Environment variable and Tools widget needs a better empty state Change By: James Dumay Summary: Environment variable and agent Tools widget needs a better empty state 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-41962) Environment variable and Tools widget needs a better empty state
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41962 Environment variable and Tools widget needs a better empty state Change By: James Dumay It is not clear what to do by looking at it . Both environment variables and tools widget use a similar design. 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-41962) Environment variable and agent widget needs a better empty state
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41962 Environment variable and agent widget needs a better empty state Change By: James Dumay Summary: Environment variable and agent widget needs a better empty state 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-41963) Developer can configure tools
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41963 Developer can configure tools Issue Type: Improvement Assignee: Brody Maclean Attachments: tools.png Components: blueocean-plugin Created: 2017/Feb/12 11:16 PM Priority: Minor Reporter: James Dumay In Scope Developer can configure tools "Tools" only become available when a non-docker agent configuration is selected Cannot be used in Docker agents for technical and best practice reasons Add Comment
[JIRA] (JENKINS-41962) Environment variable widget needs a better empty state
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41962 Environment variable widget needs a better empty state Issue Type: Improvement Assignee: Brody Maclean Attachments: empty state.png Components: blueocean-plugin Created: 2017/Feb/12 11:09 PM Priority: Minor Reporter: James Dumay It is not clear what to do by looking at it Add Comment
[JIRA] (JENKINS-41961) Developer can change the order of stages
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41961 Developer can change the order of stages Issue Type: Improvement Assignee: Brody Maclean Components: blueocean-plugin Created: 2017/Feb/12 11:06 PM Priority: Minor Reporter: James Dumay Scope Developer can use the drag handle to re-order stages (drag handle introduced in JENKINS-41960) Add Comment
[JIRA] (JENKINS-41960) Developer can change the stage level configuration
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41960 Developer can change the stage level configuration Issue Type: Improvement Assignee: Keith Zantow Attachments: stage_level_config.png Components: blueocean-plugin Created: 2017/Feb/12 11:04 PM Priority: Minor Reporter: James Dumay Scope Hovering over a stage column reveals the stage handle Clicking anywhere on the stage name or stage handle changes the sheet changes to show the config for the selected stage Developer can see settings for: Agent Environment
[JIRA] (JENKINS-40883) Supporting "post" steps at Pipeline and Stage level
Title: Message Title James Dumay closed an issue as Incomplete Jenkins / JENKINS-40883 Supporting "post" steps at Pipeline and Stage level Change By: James Dumay Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41959) Supporting "post" steps at Pipeline and Stage level
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41959 Supporting "post" steps at Pipeline and Stage level Change By: James Dumay Summary: Editor Supporting " post " steps at Pipeline and Stage level 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-41959) Editor post steps
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41959 Editor post steps Change By: James Dumay Sprint: post-release 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-39703) API to read/write a single file from/to the repository
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39703 API to read/write a single file from/to the repository Change By: James Dumay *Scope** Github*Out of scope** Git and Bitbucket support*Notes* For the [Blue Ocean Pipeline Editor|https://jenkins.io/blog/2016/09/19/blueocean-beta-declarative-pipeline-pipeline-editor/] we want to read the Jenkinsfile from the repository, let the user author it in the editor then commit it back to the repository.We need a new API and relevant implementations (Github and Bitbucket) that would allow Blue Ocean to read/write a file from the repository.[~jglick] said there is beginnings of this in the scm-api but no implementations. 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 h
[JIRA] (JENKINS-38323) Developer can drag and drop to reorder steps within a stage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38323 Developer can drag and drop to reorder steps within a stage Change By: James Dumay Sprint: pacific, atlantic, 1.0-b05/b-06, tasman, frank , post-release 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-38589) User can drag steps between step lists
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38589 User can drag steps between step lists Change By: James Dumay Sprint: post-release 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-41959) Editor post steps
Title: Message Title
James Dumay created an issue
Jenkins / JENKINS-41959
Editor post steps
Issue Type:
Improvement
Assignee:
Brody Maclean
Components:
blueocean-pipeline-editor-plugin
Created:
2017/Feb/12 10:53 PM
Priority:
Minor
Reporter:
James Dumay
Post steps
Runs after a stage has finished executing
Runs after a pipeline has finished executing
Can run when:
Always - even if the steps before the post steps fail, the post steps will always run
Failed - runs only when the proceeding steps have failed
Success - runs only when the proceeding steps have passed
unstable - runs only when the proceeding steps have been marked as unstable
changed - runs only when the state has changed relative to the previous run
e.g. stage "foo" was success in run 1, then fails in run 2 would these steps ever be run
https://jenkins.io/doc/pipeline/tour/post/ Example
pipeline {
agent any
stages {
stage('No-op') {
steps {
sh
[JIRA] (JENKINS-41876) Not respecting configuration in regards of global modules
Title: Message Title Alexander Komarov commented on JENKINS-41876 Re: Not respecting configuration in regards of global modules Confirmed, works for me (master) 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.
