[JIRA] (JENKINS-38164) Group changelog entries by Jenkins build numbers
Title: Message Title Lubo Varga commented on JENKINS-38164 Re: Group changelog entries by Jenkins build numbers What about to set "from commit" to last successful build (it is $GIT_PREVIOUS_SUCCESSFUL_COMMIT, see environment variables here: https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-AdvancedFeaturesorigin%2Fmaster) and till just current commit (it is $GIT_COMMIT variable). It would always give you git changelog from last successful build till current build. 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-38917) Version 1.8 stopped working with remote agents
Title: Message Title Denys Digtiar commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents If the priority is from the perspective of overall Jenkins, then you are absolutely correct. I downgraded the priority. It was just my misunderstanding. Thank you for your prompt response, very much appreciated. I will test the fix and provide a feedback. 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-34938) Access commit SHA of webhook payload in Jenkinsfile
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-34938 Re: Access commit SHA of webhook payload in Jenkinsfile I understand this is not gonna resolved this. Originally, the idea of this RFE is to guarantee that the commit that triggers the build is the commit that is being checkout too. 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-38917) Version 1.8 stopped working with remote agents
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-38917 Version 1.8 stopped working with remote agents Change By: Denys Digtiar Priority: Blocker 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-38917) Version 1.8 stopped working with remote agents
Title: Message Title rin_ne commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents As I described it, the only workaround for the issue is to build on the master which is not feasible in the production environments, therefore Blocker priority. I don't think so. Blocker priority should be used on Jenkins project if If core is affected by installed plugin with no configuration. This issue happens on the build that is started from a job which has this plugin related configurations. So this issue might be broker from the viewpoint of this plugin, but this is never blocker from the viewpoint of this issue tracker. Please confirm the meaning of priority in this issue tracker within bees. Unfortunately I still not reproduce this issue, but I found weakness code. So I uploaded a patch. Could you fetch the latest commit on 'JENKINS-38917' branch then build and test again? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents Code changed in jenkins User: rinrinne Path: src/main/java/org/jenkinsci/plugins/exportparams/ExportParametersBuilder.java http://jenkins-ci.org/commit/export-params-plugin/cef03bfd0044e0f359473aef4b4ca71f1069620e Log: Add inner class to ExportParametersBuilder Annonymous inner class that implements FileCallable uses external final String. This might be an issue regarding serialization on remote. This patch adds new inner class that implements FileCallable to keep such string. Issue: JENKINS-38917 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-38948) sbt plugin does not respect its own paramethers
Title: Message Title marcelo nagy closed an issue as Not A Defect Jenkins / JENKINS-38948 sbt plugin does not respect its own paramethers Change By: marcelo nagy Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38522) Long stage names overflow poorly on stage graph
Title: Message Title Brody Maclean started work on JENKINS-38522 Change By: Brody Maclean 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-38948) sbt plugin does not respect its own paramethers
Title: Message Title marcelo nagy updated an issue Jenkins / JENKINS-38948 sbt plugin does not respect its own paramethers Change By: marcelo nagy Sbt plugins does not respect the "Download URL for binary archive" parameter it always try to download the sbt from https://dl.bintray.com/sbt/native-packages/sbt/0.13.12/sbt-0.13.12.zip . What is bad for me all artifacts that we use must be downloaded from our artifactory. You can close these ticket the sbt-laucher is who try to download stuff from internet :( 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-38013) Profile and minifi blue ocean loading
Title: Message Title Brody Maclean commented on JENKINS-38013 Re: Profile and minifi blue ocean loading These are the scripting culpritsIncognito didn't take much longer. I tried in a diff browser and took < 12s. I ran it through Pingdom which took 3.25s https://tools.pingdom.com/#!/1ilTA/https://ci.blueocean.io/blue/pipelines/ 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-30035) Fail the build if alerts are discovered
Title: Message Title Goran Sarenkapa updated an issue Jenkins / JENKINS-30035 Fail the build if alerts are discovered Change By: Goran Sarenkapa 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-30035) Fail the build if alerts are discovered
Title: Message Title Goran Sarenkapa updated an issue Jenkins / JENKINS-30035 Fail the build if alerts are discovered Change By: Goran Sarenkapa Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30035) Fail the build if alerts are discovered
Title: Message Title Goran Sarenkapa assigned an issue to Goran Sarenkapa Jenkins / JENKINS-30035 Fail the build if alerts are discovered Change By: Goran Sarenkapa Assignee: Ludovic Roucoux Goran Sarenkapa 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-29686) ZAP process is left running if build is aborted
Title: Message Title Goran Sarenkapa closed an issue as Cannot Reproduce Cannot reproduce in version 2.0.0 of the plugin. Please re-open if persists. Jenkins / JENKINS-29686 ZAP process is left running if build is aborted Change By: Goran Sarenkapa Status: Open Closed Assignee: Ludovic Roucoux Goran Sarenkapa Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-29685) Set default home path within workspace
Title: Message Title Goran Sarenkapa closed an issue as Cannot Reproduce Jenkins / JENKINS-29685 Set default home path within workspace Change By: Goran Sarenkapa Status: Resolved Closed Assignee: Ludovic Roucoux Goran Sarenkapa 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-29685) Set default home path within workspace
Title: Message Title Goran Sarenkapa resolved as Cannot Reproduce Unsure of issue, feel free to re-open if persists. Closing old ticket. Jenkins / JENKINS-29685 Set default home path within workspace Change By: Goran Sarenkapa Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-29587) Allow dynamic port for ZAProxy
Title: Message Title Goran Sarenkapa resolved as Fixed Resolved in pull request: https://github.com/jenkinsci/zaproxy-plugin/pull/41 Jenkins / JENKINS-29587 Allow dynamic port for ZAProxy Change By: Goran Sarenkapa Status: Open Resolved Assignee: Ludovic Roucoux Goran Sarenkapa Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this
[JIRA] (JENKINS-38013) Profile and minifi blue ocean loading
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-38013 Profile and minifi blue ocean loading Change By: Brody Maclean Attachment: screenshot-2.png 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title Michael Neale commented on JENKINS-35864 Re: Step section in log sticks to result header when scrolling Have converted this into a todo ticket now design is done. It is not that urgent to do until we have meaningful step descriptions (given a lot of steps just say "Shell Script" its currently a little pointless... but SOON... SOON) 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-35864 Step section in log sticks to result header when scrolling Change By: Michael Neale Assignee: Michael Neale 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35864 Step section in log sticks to result header when scrolling Change By: Michael Neale Sprint: pacific , indian 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title Michael Neale stopped work on JENKINS-35864 Change By: Michael Neale 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35864 Step section in log sticks to result header when scrolling Change By: Michael Neale Sprint: pacific, atlantic indian 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-38933) allow mounting secrets to pod
Title: Message Title akostadinov commented on JENKINS-38933 Re: allow mounting secrets to pod My bad, I didn't notice the "secret volume" type under "volumes" when I looked for the option. I'll try it out. Thank you! 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title Brody Maclean assigned an issue to Michael Neale Jenkins / JENKINS-35864 Step section in log sticks to result header when scrolling Change By: Brody Maclean Assignee: Brody Maclean Michael Neale 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title Brody Maclean commented on JENKINS-35864 Re: Step section in log sticks to result header when scrolling Mockup with current 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-35864 Step section in log sticks to result header when scrolling Change By: Brody Maclean Attachment: Sticky Header.png 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-33310) Jenkins Pipeline (Workflow) support for HockeyApp plugin
Title: Message Title Kirill Marchuk updated an issue Jenkins / JENKINS-33310 Jenkins Pipeline (Workflow) support for HockeyApp plugin Change By: Kirill Marchuk Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38948) sbt plugin does not respect its own paramethers
Title: Message Title marcelo nagy created an issue Jenkins / JENKINS-38948 sbt plugin does not respect its own paramethers Issue Type: Bug Assignee: uzilan Components: sbt-plugin Created: 2016/Oct/13 3:48 AM Priority: Major Reporter: marcelo nagy Sbt plugins does not respect the "Download URL for binary archive" parameter it always try to download the sbt from https://dl.bintray.com/sbt/native-packages/sbt/0.13.12/sbt-0.13.12.zip . What is bad for me all artifacts that we use must be downloaded from our artifactory. Add Comment
[JIRA] (JENKINS-35864) Step section in log sticks to result header when scrolling
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-35864 Step section in log sticks to result header when scrolling Change By: Brody Maclean Attachment: Screen Capture on 2016-10-13 at 14-41-54.gif 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title Brody Maclean commented on JENKINS-35864 Re: Step section in log sticks to result header when scrolling Interaction Demo http://codepen.io/brody/full/rrKGBv/ 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-29272) Add ability to continue to poll while job is running
Title: Message Title Nick Grealy commented on JENKINS-29272 Re: Add ability to continue to poll while job is running Hi James Korzekwa, Is this issue still occurring? If so, can we move the issue into Github? -> https://github.com/jenkinsci/poll-mailbox-trigger-plugin/issues Thanks, Nick 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-29176) Better integration with MS Exchange Server
Title: Message Title Nick Grealy closed an issue as Won't Fix Jenkins / JENKINS-29176 Better integration with MS Exchange Server Change By: Nick Grealy 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" group. To unsubscribe from this group and stop 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-27575) Please add possibility to handle the attachment of mail to this plugin
Title: Message Title Nick Grealy closed an issue as Fixed Closing - issue is tracked in github (and has since been closed) - https://github.com/jenkinsci/poll-mailbox-trigger-plugin/issues/4 Jenkins / JENKINS-27575 Please add possibility to handle the attachment of mail to this plugin Change By: Nick Grealy 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
[JIRA] (JENKINS-38821) Global library class calling another global libraries static method fails
Title: Message Title Mike Kobit commented on JENKINS-38821 Re: Global library class calling another global libraries static method fails Jesse Glick - haven't tried it but yet, but right now at least the source code has METHOD value for @Target 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-33310) Jenkins Pipeline (Workflow) support for HockeyApp plugin
Title: Message Title Kirill Marchuk commented on JENKINS-33310 Re: Jenkins Pipeline (Workflow) support for HockeyApp plugin Found a PR on this functionality here: https://github.com/jenkinsci/hockeyapp-plugin/pull/31 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-24663) No such template for muiltipul eucalyptus cloud
Title: Message Title Yi Xu reopened an issue Still have same issue on Amazon EC2 plugin 1.36, Jenkins version is 2.25 . The second still raised following issue. java.lang.Exception: No such template:xxx-fedora-23-xxx at org.kohsuke.stapler.HttpResponses.error(HttpResponses.java:83) at hudson.plugins.ec2.EC2Cloud.doProvision(EC2Cloud.java:336) 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:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) 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:233) 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 com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.ja Jenkins / JENKINS-24663 No such template for muiltipul eucalyptus cloud Change By: Yi Xu Resolution: Cannot Reproduce Status: Closed Reopened
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: Michael Neale Priority: Critical 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-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title Michael Neale commented on JENKINS-38947 Re: A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Vivek Pandey I think this should be looked at once bismuth is in. This is a problem I think with the api ... needs investigation. 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-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: Michael Neale Sprint: indian 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-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38947
A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Change By:
Michael Neale
This is hard to explain so I will put an image attached. Basically, the current Jenkinsfile for blueocean has no stages, but it does call the ATH job towards the end. In the stage view things are correct (classic) as there are no stages. However, in blue ocean a "fake stage" which appears to be the dispatching of this external shows up as a stage in the stage graph. All steps as part of the build are also hidden. It is most odd. The job: https://ci.blueocean.io/blue/organizations/jenkins/blueocean/detail/master/415/pipeline !Screen Shot 2016-10-13 at 1.07.28 pm.png|thumbnail! (this should be showing a simple list of steps, no stages, and many more steps than that). The Jenkinsfile to see this: {noformat}#!groovy// only 20 buildsproperties([buildDiscarder(logRotator(artifactNumToKeepStr: '20', numToKeepStr: '20'))])node { deleteDir() checkout scm configFileProvider([configFile(fileId: 'blueocean-maven-settings', targetLocation: 'settings.xml')]) { docker.image('cloudbees/java-build-tools').inside {withEnv(['GIT_COMMITTER_EMAIL=m...@hatescake.com','GIT_COMMITTER_NAME=Hates','GIT_AUTHOR_NAME=Cake','GIT_AUTHOR_EMAIL=ha...@cake.com']) { try {sh "mvn clean install -B -DcleanNode -Dmaven.test.failure.ignore -s settings.xml -Dmaven.artifact.threads=30"sh "node ./bin/checkdeps.js"sh "node ./bin/checkshrinkwrap.js"step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml'])step([$class: 'ArtifactArchiver', artifacts: '*/target/*.hpi'])triggerATH(); } catch(err) {currentBuild.result = "FAILURE" } finally {sendhipchat()deleteDir() }} } }}def triggerATH() {// Assemble and archive the HPI plugins that the ATH should use.// The ATH build can copy this artifact and use it, saving the time it// would otherwise spend building and assembling again.sh 'cd blueocean && mvn hpi:assemble-dependencies && tar -czvf target/ath-plugins.tar.gz target/plugins'archiveArtifacts artifacts: 'blueocean/target/ath-plugins.tar.gz'// Trigger the ATH, but don't wait for it.try {echo "Will attempt to run the ATH with the same branch name i.e. '${env.BRANCH_NAME}'."build(job: "ATH-Jenkinsfile/${env.BRANCH_NAME}",parameters: [string(name: 'BLUEOCEAN_BRANCH_NAME', value: "${env.BRANCH_NAME}"), string(name: 'BUILD_NUM', value: "${env.BUILD_NUMBER}")],wait: false)} catch (e1) {echo "Failed to run the ATH with the same branch name i.e. '${env.BRANCH_NAME}'. Will try running the ATH 'master' branch."build(job: "ATH-Jenkinsfile/master",parameters: [string(name: 'BLUEOCEAN_BRANCH_NAME', value: "${env.BRANCH_NAME}"), string(name: 'BUILD_NUM', value:
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38947
A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Change By:
Michael Neale
This is hard to explain so I will put an image attached. Basically, the current Jenkinsfile for blueocean has no stages, but it does call the ATH job towards the end. In the stage view things are correct (classic) as there are no stages. However, in blue ocean a "fake stage" which appears to be the dispatching of this external shows up as a stage in the stage graph. All steps as part of the build are also hidden. It is most odd. The job: https://ci.blueocean.io/blue/organizations/jenkins/blueocean/detail/master/415/pipeline !Screen Shot 2016-10-13 at 1.07.28 pm.png|thumbnail! The Jenkinsfile to see this: {noformat}#!groovy// only 20 buildsproperties([buildDiscarder(logRotator(artifactNumToKeepStr: '20', numToKeepStr: '20'))])node { deleteDir() checkout scm configFileProvider([configFile(fileId: 'blueocean-maven-settings', targetLocation: 'settings.xml')]) { docker.image('cloudbees/java-build-tools').inside {withEnv(['GIT_COMMITTER_EMAIL=m...@hatescake.com','GIT_COMMITTER_NAME=Hates','GIT_AUTHOR_NAME=Cake','GIT_AUTHOR_EMAIL=ha...@cake.com']) { try {sh "mvn clean install -B -DcleanNode -Dmaven.test.failure.ignore -s settings.xml -Dmaven.artifact.threads=30"sh "node ./bin/checkdeps.js"sh "node ./bin/checkshrinkwrap.js"step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml'])step([$class: 'ArtifactArchiver', artifacts: '*/target/*.hpi'])triggerATH(); } catch(err) {currentBuild.result = "FAILURE" } finally {sendhipchat()deleteDir() }} } }}def triggerATH() {// Assemble and archive the HPI plugins that the ATH should use.// The ATH build can copy this artifact and use it, saving the time it// would otherwise spend building and assembling again.sh 'cd blueocean && mvn hpi:assemble-dependencies && tar -czvf target/ath-plugins.tar.gz target/plugins'archiveArtifacts artifacts: 'blueocean/target/ath-plugins.tar.gz'// Trigger the ATH, but don't wait for it.try {echo "Will attempt to run the ATH with the same branch name i.e. '${env.BRANCH_NAME}'."build(job: "ATH-Jenkinsfile/${env.BRANCH_NAME}",parameters: [string(name: 'BLUEOCEAN_BRANCH_NAME', value: "${env.BRANCH_NAME}"), string(name: 'BUILD_NUM', value: "${env.BUILD_NUMBER}")],wait: false)} catch (e1) {echo "Failed to run the ATH with the same branch name i.e. '${env.BRANCH_NAME}'. Will try running the ATH 'master' branch."build(job: "ATH-Jenkinsfile/master",parameters: [string(name: 'BLUEOCEAN_BRANCH_NAME', value: "${env.BRANCH_NAME}"), string(name: 'BUILD_NUM', value: "${env.BUILD_NUMBER}")],wait: false)}}def sendhipchat() {res =
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: Michael Neale Attachment: Screen Shot 2016-10-13 at 1.07.28 pm.png 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-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38947
A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Change By:
Michael Neale
This is hard to explain so I will put an image attached. Basically, the current Jenkinsfile for blueocean has no stages, but it does call the ATH job towards the end. In the stage view things are correct (classic) as there are no stages. However, in blue ocean a "fake stage" which appears to be the dispatching of this external shows up as a stage in the stage graph. All steps as part of the build are also hidden. It is most odd. The Jenkinsfile to see this: ``` {noformat} #!groovy// only 20 buildsproperties([buildDiscarder(logRotator(artifactNumToKeepStr: '20', numToKeepStr: '20'))])node { deleteDir() checkout scm configFileProvider([configFile(fileId: 'blueocean-maven-settings', targetLocation: 'settings.xml')]) { docker.image('cloudbees/java-build-tools').inside {withEnv(['GIT_COMMITTER_EMAIL=m...@hatescake.com','GIT_COMMITTER_NAME=Hates','GIT_AUTHOR_NAME=Cake','GIT_AUTHOR_EMAIL=ha...@cake.com']) { try {sh "mvn clean install -B -DcleanNode -Dmaven.test.failure.ignore -s settings.xml -Dmaven.artifact.threads=30"sh "node ./bin/checkdeps.js"sh "node ./bin/checkshrinkwrap.js"step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml'])step([$class: 'ArtifactArchiver', artifacts: '*/target/*.hpi'])triggerATH(); } catch(err) {currentBuild.result = "FAILURE" } finally {sendhipchat()deleteDir() }} } }}def triggerATH() {// Assemble and archive the HPI plugins that the ATH should use.// The ATH build can copy this artifact and use it, saving the time it// would otherwise spend building and assembling again.sh 'cd blueocean && mvn hpi:assemble-dependencies && tar -czvf target/ath-plugins.tar.gz target/plugins'archiveArtifacts artifacts: 'blueocean/target/ath-plugins.tar.gz'// Trigger the ATH, but don't wait for it.try {echo "Will attempt to run the ATH with the same branch name i.e. '${env.BRANCH_NAME}'."build(job: "ATH-Jenkinsfile/${env.BRANCH_NAME}",parameters: [string(name: 'BLUEOCEAN_BRANCH_NAME', value: "${env.BRANCH_NAME}"), string(name: 'BUILD_NUM', value: "${env.BUILD_NUMBER}")],wait: false)} catch (e1) {echo "Failed to run the ATH with the same branch name i.e. '${env.BRANCH_NAME}'. Will try running the ATH 'master' branch."build(job: "ATH-Jenkinsfile/master",parameters: [string(name: 'BLUEOCEAN_BRANCH_NAME', value: "${env.BRANCH_NAME}"), string(name: 'BUILD_NUM', value: "${env.BUILD_NUMBER}")],wait: false)}}def sendhipchat() {res = currentBuild.resultif(currentBuild.result == null) { res = "SUCCESS"}message = "${env.JOB_NAME} #${env.BUILD_NUMBER}, status: ${res}
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title
Michael Neale created an issue
Jenkins / JENKINS-38947
A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Issue Type:
Bug
Assignee:
Vivek Pandey
Components:
blueocean-plugin
Created:
2016/Oct/13 2:12 AM
Priority:
Critical
Reporter:
Michael Neale
This is hard to explain so I will put an image attached. Basically, the current Jenkinsfile for blueocean has no stages, but it does call the ATH job towards the end. In the stage view things are correct (classic) as there are no stages. However, in blue ocean a "fake stage" which appears to be the dispatching of this external shows up as a stage in the stage graph. All steps as part of the build are also hidden. It is most odd. The Jenkinsfile to see this: ``` #!groovy // only 20 builds properties([buildDiscarder(logRotator(artifactNumToKeepStr: '20', numToKeepStr: '20'))]) node { deleteDir() checkout scm configFileProvider([configFile(fileId: 'blueocean-maven-settings', targetLocation: 'settings.xml')]) { docker.image('cloudbees/java-build-tools').inside { withEnv(['GIT_COMMITTER_EMAIL=m...@hatescake.com','GIT_COMMITTER_NAME=Hates','GIT_AUTHOR_NAME=Cake','GIT_AUTHOR_EMAIL=ha...@cake.com']) { try { sh "mvn clean install -B -DcleanNode -Dmaven.test.failure.ignore -s settings.xml -Dmaven.artifact.threads=30" sh "node ./bin/checkdeps.js" sh "node ./bin/checkshrinkwrap.js" step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml']) step([$class: 'ArtifactArchiver', artifacts: '*/target/*.hpi']) triggerATH(); } catch(err) { currentBuild.result = "FAILURE" } finally { sendhipchat() deleteDir() } } } } } def triggerATH() { // Assemble and archive the HPI plugins that the ATH should use. // The ATH build can copy this artifact and use it, saving the time it // would otherwise spend building and assembling again. sh 'cd blueocean && mvn hpi:assemble-dependencies && tar -czvf target/ath-plugins.tar.gz target/plugins'
[JIRA] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title Denys Digtiar edited a comment on JENKINS-38917 Re: Version 1.8 stopped working with remote agents I have not found it in archives so I built it from source. I was able to reproduce it the issue . I can not reproduce it the issue on 1.1 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-38917) Version 1.8 stopped working with remote agents
Title: Message Title Denys Digtiar commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents I have not found it in archives so I built it from source. I was able to reproduce it. I can not reproduce it on 1.1 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-38946) Failed API calls not handled very well
Title: Message Title Ben Walding created an issue Jenkins / JENKINS-38946 Failed API calls not handled very well Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2016/Oct/13 1:58 AM Environment: Jenkins 2.21 + blueocean b08 Priority: Trivial Reporter: Ben Walding When using BlueOcean interface, the interface generally responds quickly. However if there is a problem contacting the Jenkins backend, the UI will either appear to be waiting, or claim to have completed whatever it was doing instantly. Simulating: I have my Jenkins behind a VPN, if I switch off the VPN then the BlueOcean UI does not notice. This could probably be replicated by stopping the Jenkins server (although it might be a slightly different failure). The reason I noticed it was due to favourites - I'd disabled the VPN, and then I clicked to favourite a few items. The favourite star went yellow, but there was no feedback in the UI that the favouriting had failed. Feel free to rewrite this as a specific favourites issue.
[JIRA] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title rin_ne commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents Could you reproduce this with export-params pkugin 1.5 once? 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-38917) Version 1.8 stopped working with remote agents
Title: Message Title Denys Digtiar commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents I have just been able to reproduce it again with the brand new jenkins:alpine image based container and the same ssh agent container I used with the previous experiment. As I described it, the only workaround for the issue is to build on the master which is not feasible in the production environments, therefore Blocker priority. Here is a link to the change log for the last release pointing to the change that I believe is a culprit. https://github.com/jenkinsci/export-params-plugin/compare/export-params-1.1...export-params-1.8#diff-760dab5c086e6b7560887018ac881ac7L137 I don't know that much about Jenkins remoting. But my guess is that FileCallable has to be Serializable. Since an anonymous inner class is used it captures its parent object which I am guessing is not serializable or has fields in its hierarchy that are not serializable. 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-38945) Pipeline script doesn't find method with explicit parameter type
Title: Message Title
Daniel Sobral created an issue
Jenkins / JENKINS-38945
Pipeline script doesn't find method with explicit parameter type
Issue Type:
Bug
Assignee:
Unassigned
Components:
script-security-plugin, workflow-cps-plugin
Created:
2016/Oct/13 1:13 AM
Environment:
Jenkins 2.23 Pipeline 2.4 Pipeline: Groovy 2.19 Script Security 1.23
Priority:
Minor
Reporter:
Daniel Sobral
Pipeline scripts fail to find method declaring parameter type. The script below will fail to execute "doStuff", with NoSuchMethodError. This used to work, but rolling back security and groovy didn't help, and utility steps (which defines readMavenPom) wasn't available for rollback. On a simple test, "Integer n" works as a type parameter, so this might well be specific to the object returned by readMavenPom().
import org.apache.maven.model.Model
stage ("initial") {
node ('mesos') {
git url: 'https://github.com/jglick/simple-maven-project-with-tests.git'
Model pom = readMavenPom()
echo "Class of pom is ${pom.class}"
doThings(pom)
doStuff(pom)
}
}
def doThings(pom) {
echo "Got something"
}
def doStuff(Model pom) {
echo "Got pom"
}
[JIRA] (JENKINS-38083) Branch/PR ordering should update when SSE happenermission and role checks for run, re-run and stop buttons
Title: Message Title Ivan Meredith started work on JENKINS-38083 Change By: Ivan Meredith 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-36573) API to retrieve link to pull request
Title: Message Title Ivan Meredith updated JENKINS-36573 Jenkins / JENKINS-36573 API to retrieve link to pull request 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-38913) DSL for choiceParam not working
Title: Message Title Oleg Nenashev commented on JENKINS-38913 Re: DSL for choiceParam not working Alex Raguero Please create an issue to CloudBees ZenDesk then. In such case I may get this assignment to work on it during office hours. My personal time plans do not include dealing with Promoted Builds in short term, sorry. Or other engineers from CB Support/Engineering team may handle 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-36573) API to retrieve link to pull request
Title: Message Title Ivan Meredith started work on JENKINS-36573 Change By: Ivan Meredith 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-36377) When a developer creates a new branch it is automatically favourited
Title: Message Title Ivan Meredith stopped work on JENKINS-36377 Change By: Ivan Meredith 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-37878) Implement a DisplayURLProvider for Blue Ocean
Title: Message Title Ivan Meredith updated JENKINS-37878 Jenkins / JENKINS-37878 Implement a DisplayURLProvider for Blue Ocean Change By: Ivan Meredith 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-38943) SVN_REVISION environment variable not set when URL includes capitalized hostname
Title: Message Title
David Potter updated an issue
Jenkins / JENKINS-38943
SVN_REVISION environment variable not set when URL includes capitalized hostname
Change By:
David Potter
When a project uses Subversion SCM and references the repository using an upper-case hostname, the SVN_REVISION environment variable is not set within the build.The Jenkins application log contains the following warning:{ nopanel panel } {noformat} Oct 12, 2016 1:19:24 PM hudson.scm.SubversionSCM buildEnvVarsWARNING: no revision found corresponding to https://MYSERVER.mydomain.com/svn/path/to/project/trunk; known: [https://myserver.mydomain.com/svn/path/to/project/trunk]{ nopanel noformat } {panel} This problem was resolved by updating the repository URL to use a lower-case hostname.
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
[JIRA] (JENKINS-38943) SVN_REVISION environment variable not set when URL includes capitalized hostname
Title: Message Title
David Potter updated an issue
Jenkins / JENKINS-38943
SVN_REVISION environment variable not set when URL includes capitalized hostname
Change By:
David Potter
When a project uses Subversion SCM and references the repository using an upper-case hostname, the SVN_REVISION environment variable is not set within the build.The Jenkins application log contains the following warning:{ code:title=error-message|borderStyle=solid nopanel }Oct 12, 2016 1:19:24 PM hudson.scm.SubversionSCM buildEnvVarsWARNING: no revision found corresponding to https://MYSERVER.mydomain.com/svn/path/to/project/trunk; known: [https://myserver.mydomain.com/svn/path/to/project/trunk]{ code nopanel }This problem was resolved by updating the repository URL to use a lower-case hostname.
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
[JIRA] (JENKINS-38943) SVN_REVISION environment variable not set when URL includes capitalized hostname
Title: Message Title
David Potter updated an issue
Jenkins / JENKINS-38943
SVN_REVISION environment variable not set when URL includes capitalized hostname
Change By:
David Potter
When a project uses Subversion SCM and references the repository using an upper-case hostname, the SVN_REVISION environment variable is not set within the build.The Jenkins application log contains the following warning:{ { code:title=error-message|borderStyle=solid} Oct 12, 2016 1:19:24 PM hudson.scm.SubversionSCM buildEnvVarsWARNING: no revision found corresponding to https://MYSERVER.mydomain.com/svn/path/to/project/trunk; known: [https://myserver.mydomain.com/svn/path/to/project/trunk] {code } } This problem was resolved by updating the repository URL to use a lower-case hostname.
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
[JIRA] (JENKINS-38944) webhook is not registering on creation
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-38944 webhook is not registering on creation Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2016/Oct/12 11:43 PM Priority: Minor Reporter: Jae Gangemi the plugin does not seem to be registering the webhook when i create a new project. i have the 'manage hooks' checkbox checked in the github plugin section and the webhook does register if i click 'register for all projects', but i need this to be automatically get up when the project gets created. Add Comment
[JIRA] (JENKINS-38943) SVN_REVISION environment variable not set when URL includes capitalized hostname
Title: Message Title
David Potter created an issue
Jenkins / JENKINS-38943
SVN_REVISION environment variable not set when URL includes capitalized hostname
Issue Type:
Bug
Assignee:
Unassigned
Components:
subversion-plugin
Created:
2016/Oct/12 11:43 PM
Environment:
Jenkins 2.7.4 running on CentOS 7 with Openjdk 1.8.0_91 Windows Build Agent running on Windows Server 2012 R2 (but I doubt the agent matters) Jenkins launched like this: {{export JENKINS_HOME=/opt/jenkins java -Dsvnkit.http.methods=Basic,NTLM,Negotiate,Digest -Djava.security.krb5.realm=mydomain.com -Djava.security.krb5.kdc=myhost.mydomain.com -Dsun.security.krb5.debug=false -Djavax.net.ssl.trustStore=cacerts -jar jenkins.war --httpPort=-1 --httpsPort=8080 --httpsKeyStore=/opt/jenkins/jenkins.jks --httpsKeyStorePassword=mypass &}}
Priority:
Minor
Reporter:
David Potter
When a project uses Subversion SCM and references the repository using an upper-case hostname, the SVN_REVISION environment variable is not set within the build. The Jenkins application log contains the following warning: {{Oct 12, 2016 1:19:24 PM hudson.scm.SubversionSCM buildEnvVars WARNING: no revision found corresponding to https://MYSERVER.mydomain.com/svn/path/to/project/trunk; known : https://myserver.mydomain.com/svn/path/to/project/trunk}} This problem was resolved by updating the repository URL to use a lower-case hostname.
[JIRA] (JENKINS-38013) Profile and minifi blue ocean loading
Title: Message Title Michael Neale commented on JENKINS-38013 Re: Profile and minifi blue ocean loading Brody Maclean yes the empty state flash is known and being fixed. I guess acceptable was more in your judgment compared to other rich web apps that are on the other side of the world, that you use (blue ocean has to reload more than is relistic, as there are daily deploys belowing away any caching). 6 seconds seems ok if a hard refresh - that seems like it is using the cache still somehow (if you use incognito, surely it is more like 20 to 30 seconds?) In that pie chart, what is "scripting"? 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title Brody Maclean started work on JENKINS-35864 Change By: Brody Maclean 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-38913) DSL for choiceParam not working
Title: Message Title Alex Raguero commented on JENKINS-38913 Re: DSL for choiceParam not working Also not working for version Jenkins ver. 2.7.19.1 (CloudBees Jenkins Enterprise 2.7.19.1-rolling) 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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Justen Britain commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json Frieder Rick I have cloned and built the develop branch of this project and tested with our Jenkins installation and the latest version of Bitbucket Server (formerly Stash), version 4.9.1. The problem that you and I are experiencing seems to be because Bitbucket Server is not explicitly supported in this way by this plugin (whether intentional or not). In fact, you will notice that in the code BitbucketHookReceiver.java there is a comment pointing to the Atlassian documentation for the webhooks. The URL provided results in a Page Not Found error with a suggestion to look at the documentation for Webhooks for Bitbucket Cloud (the latest branding for the hosted version of Bitbucket). It seems possible that at one time both "Stash" and the hosted Bitbucket may have been supported by the plugin. There are essentially three code paths available for the incoming payload, none of which are compatible with the payload that is being delivered by Bitbucket Server. That being said, the requirements to get this to work for Bitbucket Server would require the introduction of an additional code path to detect that the payload is being delivered from Bitbucket Server. The links below are from the "develop" branch and have been in pull request since April 30 with the latest comments on Aug 11. So it is unlikely that we will see a fix to this "bug" in the near future. I have attached the output from Bitbucket Server (modified to remove company information) and the links to the relevant code below: Note: Please notice these links point to the develop branch https://github.com/jenkinsci/bitbucket-plugin/blob/develop/src/main/java/com/cloudbees/jenkins/plugins/BitbucketHookReceiver.java#L81 https://github.com/jenkinsci/bitbucket-plugin/blob/develop/src/main/java/com/cloudbees/jenkins/plugins/payload/BitbucketPayload.java#L51 bb-server-4.9.1_payload.txt I was only able to dedicate a couple hours to investigating this issue so please forgive any oversights that may have been made. Add Comment
[JIRA] (JENKINS-38013) Profile and minifi blue ocean loading
Title: Message Title Brody Maclean commented on JENKINS-38013 Re: Profile and minifi blue ocean loading With a hard refresh https://ci.blueocean.io/blue/pipelines/ took 6 seconds to load. Theres a decent delay when pages loading but I'm not sure how long is acceptable. Also the empty state flashes up when opening a pipeline which is a little jarring http://d.pr/i/1bPZC 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-38013) Profile and minifi blue ocean loading
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-38013 Profile and minifi blue ocean loading Change By: Brody Maclean Attachment: screenshot-1.png 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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Justen Britain edited a comment on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json [~entfrickler] I have cloned and built the develop branch of this project and tested with our Jenkins installation and the latest version of Bitbucket Server (formerly Stash), version 4.9.1. The problem that you and I are experiencing seems to be because Bitbucket Server is not explicitly supported in this way by this plugin (whether intentional or not). In fact, you will notice that in the code [ BitbucketHookReceiver.java |https://github.com/jenkinsci/bitbucket-plugin/blob/develop/src/main/java/com/cloudbees/jenkins/plugins/BitbucketHookReceiver.java#L65] there is a comment pointing to the Atlassian documentation for the webhooks. The URL provided results in a Page Not Found error with a suggestion to look at the documentation for Webhooks for Bitbucket Cloud (the latest branding for the hosted version of Bitbucket). It seems possible that at one time both "Stash" and the hosted Bitbucket may have been supported by the plugin. There are essentially three code paths available for the incoming payload, none of which are compatible with the payload that is being delivered by Bitbucket Server. That being said, the requirements to get this to work for Bitbucket Server would require the introduction of an additional code path to detect that the payload is being delivered from Bitbucket Server. The links below are from the "develop" branch and have been in [pull request|https://github.com/jenkinsci/bitbucket-plugin/pull/30] since April 30 with the latest comments on Aug 11. So it is unlikely that we will see a fix to this "bug" in the near future.I have attached the output from Bitbucket Server (modified to remove company information) and the links to the relevant code below:_Note: Please notice these links point to the develop branch_* https://github.com/jenkinsci/bitbucket-plugin/blob/develop/src/main/java/com/cloudbees/jenkins/plugins/BitbucketHookReceiver.java#L81* https://github.com/jenkinsci/bitbucket-plugin/blob/develop/src/main/java/com/cloudbees/jenkins/plugins/payload/BitbucketPayload.java#L51[^bb-server-4.9.1_payload.txt]I was only able to dedicate a couple hours to investigating this issue so please forgive any oversights that may have been made. Add Comment
[JIRA] (JENKINS-38938) Add option for global data directory
Title: Message Title Steve Springett resolved as Done Feature is implemented and will be available in the next release (v1.4.4) Jenkins / JENKINS-38938 Add option for global data directory Change By: Steve Springett Status: In Progress Resolved Resolution: Done 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
[JIRA] (JENKINS-38938) Add option for global data directory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38938 Re: Add option for global data directory Code changed in jenkins User: stevespringett Path: src/main/java/org/jenkinsci/plugins/DependencyCheck/AbstractDependencyCheckBuilder.java src/main/java/org/jenkinsci/plugins/DependencyCheck/DependencyCheckBuilder.java src/main/java/org/jenkinsci/plugins/DependencyCheck/DependencyCheckUpdateOnlyBuilder.java src/main/resources/org/jenkinsci/plugins/DependencyCheck/DependencyCheckBuilder/global.jelly src/main/resources/org/jenkinsci/plugins/DependencyCheck/DependencyCheckBuilder/global.properties src/main/webapp/help-datadir.html http://jenkins-ci.org/commit/dependency-check-plugin/915576c33143adb99ed5d57c55ad31a6182f5e03 Log: #JENKINS-38938 - Adding support for global data directory (with per-job override). 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-38938) Add option for global data directory
Title: Message Title Steve Springett started work on JENKINS-38938 Change By: Steve Springett 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-38937) GitHub API cache is not working
Title: Message Title
Greg Smith commented on JENKINS-38937
Re: GitHub API cache is not working
With 1.22.2 installed, the problem listed in JENKINS-38935 was resolved. However, I still do not see any directory in my $ {JENKINS_HOME} /org.jenkinsci.plugins.github.GitHubPlugin.cache It does not appear that fixing the problem with loading the configuration load solved the problem with using / writing the cache. Is there some other logging I could provide to determine why the cache file is not being created, or confirm if the cache is being used?
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-38935) GitHub Plugin settings not surviving Jenkins restart
Title: Message Title Kirill Merkushev commented on JENKINS-38935 Re: GitHub Plugin settings not surviving Jenkins restart thanks for the report 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-29714) infinite polling with variable in branchspec
Title: Message Title Mark Waite commented on JENKINS-29714 Re: infinite polling with variable in branchspec Eyal David there is not a road map for this issue to be solved. I'd love to see one or more automated tests written which show the problem, then a proposed change which fixes the problem. I am unlikely to investigate this failure for a long time. 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-38935) GitHub Plugin settings not surviving Jenkins restart
Title: Message Title Greg Smith commented on JENKINS-38935 Re: GitHub Plugin settings not surviving Jenkins restart This is fixed in 1.22.2 After installing 1.22.2, I was able to restart Jenkins and the configuration was loaded from disk, without above original error. 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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Justen Britain updated an issue Jenkins / JENKINS-28877 Bitbucket Plugin unable to parse Bitbucket webhook response json Change By: Justen Britain Attachment: bb-server-4.9.1_payload.txt 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-38942) Stopped EC2 agents not waking up if the number of stopped EC2 agents equals the global Instance Cap
Title: Message Title Darin Pope created an issue Jenkins / JENKINS-38942 Stopped EC2 agents not waking up if the number of stopped EC2 agents equals the global Instance Cap Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Oct/12 9:57 PM Environment: ec2-plugin 1.34; aws-java-sdk 1.10.50 Priority: Minor Reporter: Darin Pope Steps to reproduce: set the global Instance Cap to 5 (or some other number) check the box for "Stop/Disconnect on Idle Timeout" so the instances stop instead of terminate set the "Idle termination time" to a low number so you don't have to wait too long after the jobs complete run a few jobs so you have some EC2 agents available to be stopped give some time for the EC2 agents to idle and stop change the global Instance Cap to equal the number of stopped EC2 agents Queue up some jobs to run again. The EC2 agents will not wake up and the following entry is in the log: hudson.plugins.ec2.EC2Cloud#provisionSlaveIfPossible: Cannot provision - no capacity for instances: -1 Variation on the issue: If you change the global Instance Cap to + 1 and you start running your jobs,
[JIRA] (JENKINS-34144) Don't fail the job if setting the GitHub status fails
Title: Message Title Kirill Merkushev closed an issue as Fixed Jenkins / JENKINS-34144 Don't fail the job if setting the GitHub status fails Change By: Kirill Merkushev Status: In Progress 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-34144) Don't fail the job if setting the GitHub status fails
Title: Message Title Kirill Merkushev commented on JENKINS-34144 Re: Don't fail the job if setting the GitHub status fails handler added 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-38929) testcase
Title: Message Title Kirill Merkushev closed an issue as Incomplete Jenkins / JENKINS-38929 testcase Change By: Kirill Merkushev 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-38867) Major Optimization: Create and Use FlowNode.getAction w/o TransientActionFactories
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-38867 Major Optimization: Create and Use FlowNode.getAction w/o TransientActionFactories Change By: Sam Van Oort In most cases we only care about the directly attached actions on flownodes. FlowNode.getAction has been identified as ~25% of runtime for pipeline flow analysis, and it is likely b/c this queries all TransientActionFactories for actions. We should:1. Add a FlowNode.getAction API version (name TBD) that only iterates through the directly added actions (already cached in-object)2. Switch the pipeline-graph-analysis plugin and stage view's REST API to use this exclusively3. Benchmark to see what the performance difference is UPDATE: *50% improvement in stage view performance, which should carry through to a large extent anywhere we use flow analysis.* 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
[JIRA] (JENKINS-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Alex Ehlke commented on JENKINS-33273 Re: Optimize Jenkinsfile loading and branch detection Just chiming in that this is a complete blocker for us (our repo takes too long to do a clone just to get the Jenkinsfile for each step). 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-38867) Major Optimization: Create and Use FlowNode.getAction w/o TransientActionFactories
Title: Message Title Sam Van Oort updated JENKINS-38867 Jenkins / JENKINS-38867 Major Optimization: Create and Use FlowNode.getAction w/o TransientActionFactories Change By: Sam Van Oort 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-38941) Cannot retrieve secrets if vault backend doesn't support fetching lists of secrets
Title: Message Title Gareth Harcombe-Minson commented on JENKINS-38941 Re: Cannot retrieve secrets if vault backend doesn't support fetching lists of secrets Upon further investigation, we might have a very restrictive policy in place that is not allowing lists of keys to be returned. Just mentioning as it might not be specific to Consul backends. I also found a workaround - setting the secret path to a single key and only defining one value in the pair does succeed, though it is more verbose. 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-38941) Cannot retrieve secrets if vault backend doesn't support fetching lists of secrets
Title: Message Title Gareth Harcombe-Minson edited a comment on JENKINS-38941 Re: Cannot retrieve secrets if vault backend doesn't support fetching lists of secrets Upon further investigation, we might have a very restrictive policy in place that is not allowing lists of keys to be returned. Just mentioning as it might not be specific to Consul backends. I don't have access to the configuration of Vault being used here, so i'm unable to dig into the configutation too much. I also found a workaround - setting the secret path to a single key and only defining one value in the pair does succeed, though it is more verbose. 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-38702) AccuRev for Jenkins Plugin does not display Depots
Title: Message Title Joseph Petersen commented on JENKINS-38702 Re: AccuRev for Jenkins Plugin does not display Depots Direct link for FIX: https://jenkins.ci.cloudbees.com/job/plugins/job/accurev-plugin/146/org.jenkins-ci.plugins$accurev/artifact/org.jenkins-ci.plugins/accurev/0.7.3-SNAPSHOT/accurev-0.7.3-SNAPSHOT.hpi Build: https://jenkins.ci.cloudbees.com/job/plugins/job/accurev-plugin/146/org.jenkins-ci.plugins$accurev/ Code change: https://github.com/jenkinsci/accurev-plugin/pull/32/commits/868922ccc9bbd0b06d85e6c3358a7da1bdaae20e 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-38702) AccuRev for Jenkins Plugin does not display Depots
Title: Message Title Joseph Petersen commented on JENKINS-38702 Re: AccuRev for Jenkins Plugin does not display Depots Here is the full exception: FATAL: HOSTNAME: login (login -H OTHERHOSTNAME:PORT NAME PASSWORD) failed with java.io.IOException: remote file operation failed: D:\slave\workspace\demo2 at hudson.remoting.Channel@6e9bf4b8:testnode: java.io.IOException: Remote call on testnode failed java.io.IOException: remote file operation failed: D:\slave\workspace\demo2 at hudson.remoting.Channel@6e9bf4b8:testnode: java.io.IOException: Remote call on testnode failed at hudson.FilePath.act(FilePath.java:992) at hudson.FilePath.act(FilePath.java:974) at hudson.plugins.accurev.AccurevLauncher.createProcess(AccurevLauncher.java:244) at hudson.plugins.accurev.AccurevLauncher.runCommand(AccurevLauncher.java:189) at hudson.plugins.accurev.AccurevLauncher.runCommand(AccurevLauncher.java:75) at hudson.plugins.accurev.cmd.Login.accurevLogin(Login.java:97) at hudson.plugins.accurev.cmd.Login.ensureLoggedInToAccurev(Login.java:70) at hudson.plugins.accurev.delegates.AbstractModeDelegate.setup(AbstractModeDelegate.java:63) at hudson.plugins.accurev.delegates.AbstractModeDelegate.checkout(AbstractModeDelegate.java:150) at hudson.plugins.accurev.AccurevSCM.checkout(AccurevSCM.java:371) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1720) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:401) Caused by: java.io.IOException: Remote call on testnode failed at hudson.remoting.Channel.call(Channel.java:805) at hudson.FilePath.act(FilePath.java:985) ... 18 more Caused by: java.lang.ExceptionInInitializerError at hudson.plugins.accurev.FindAccurevClientExe.invoke(FindAccurevClientExe.java:60) at hudson.plugins.accurev.FindAccurevClientExe.invoke(FindAccurevClientExe.java:13) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2731) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:332) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:88) at java.lang.Thread.run(Unknown Source) at ..remote call to testnode(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1433) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:797) ... 19 more Caused by: java.lang.NullPointerException at hudson.model.Descriptor.getConfigFile(Descriptor.java:898) at hudson.model.Descriptor.load(Descriptor.java:886) at hudson.scm.SCMDescriptor.load(SCMDescriptor.java:83) at hudson.plugins.accurev.AccurevSCM$AccurevSCMDescriptor.(AccurevSCM.java:491) at hudson.plugins.accurev.AccurevSCM.(AccurevSCM.java:43)
[JIRA] (JENKINS-36961) GithubCommitStatusSetter intermittently doesn't set status update in Jenkins Pipeline
Title: Message Title Kirill Merkushev closed an issue as Won't Fix Jenkins / JENKINS-36961 GithubCommitStatusSetter intermittently doesn't set status update in Jenkins Pipeline Change By: Kirill Merkushev 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" group. To unsubscribe from this group and stop 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-36961) GithubCommitStatusSetter intermittently doesn't set status update in Jenkins Pipeline
Title: Message Title Kirill Merkushev commented on JENKINS-36961 Re: GithubCommitStatusSetter intermittently doesn't set status update in Jenkins Pipeline Github plugin can find your repo automatically only by scm. With pipeline it populated only after first build. You can define repo url and sha manually 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-36510) GitHubCommitStatusSetter doesn't allow setting status url
Title: Message Title Kirill Merkushev edited a comment on JENKINS-36510 Re: GitHubCommitStatusSetter doesn't allow setting status url now you can setup backref provider and define any link manually (see https://github.com/jenkinsci/github-plugin/pull/138 for 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] (JENKINS-36510) GitHubCommitStatusSetter doesn't allow setting status url
Title: Message Title Kirill Merkushev commented on JENKINS-36510 Re: GitHubCommitStatusSetter doesn't allow setting status url now you can setup backref provider and define any link manually 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-36510) GitHubCommitStatusSetter doesn't allow setting status url
Title: Message Title Kirill Merkushev closed an issue as Fixed Jenkins / JENKINS-36510 GitHubCommitStatusSetter doesn't allow setting status url Change By: Kirill Merkushev 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-35011) GitHub Plugin allows unauthenticated access despite global security configuration
Title: Message Title Kirill Merkushev commented on JENKINS-35011 Re: GitHub Plugin allows unauthenticated access despite global security configuration Now plugin allows you to define hook secret on github side, so only those who knows secret can trigger build. Otherwise they can do nothing. This url can't be secured with password as github expects full access to this endpoint 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-35011) GitHub Plugin allows unauthenticated access despite global security configuration
Title: Message Title Kirill Merkushev closed an issue as Fixed Jenkins / JENKINS-35011 GitHub Plugin allows unauthenticated access despite global security configuration Change By: Kirill Merkushev 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-38024) GithubLinkAnnotator NPE
Title: Message Title Kirill Merkushev updated an issue Jenkins / JENKINS-38024 GithubLinkAnnotator NPE Change By: Kirill Merkushev 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-38937) GitHub API cache is not working
Title: Message Title Kirill Merkushev started work on JENKINS-38937 Change By: Kirill Merkushev 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-38937) GitHub API cache is not working
Title: Message Title Kirill Merkushev stopped work on JENKINS-38937 Change By: Kirill Merkushev 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-38829) "Kubernetes server certificate key" not working
Title: Message Title Carlos Sanchez commented on JENKINS-38829 Re: "Kubernetes server certificate key" not working This is supposed to be a X509 PEM encoded certificate. I have added some help text. You can see some tests in the fabric8 API https://github.com/fabric8io/kubernetes-client/blob/53471cdcfd04dce22026991d260c414e48934e23/kubernetes-tests/src/test/java/io/fabric8/kubernetes/client/mock/UntrustedCertTest.java#L48 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-38937) GitHub API cache is not working
Title: Message Title Kirill Merkushev assigned an issue to Kirill Merkushev Jenkins / JENKINS-38937 GitHub API cache is not working Change By: Kirill Merkushev Assignee: Kirill Merkushev 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.
