[JIRA] (JENKINS-36379) Dynamic spot instance support
Title: Message Title Johnny Shields created an issue Jenkins / JENKINS-36379 Dynamic spot instance support Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Jul/01 5:35 AM Priority: Minor Reporter: Johnny Shields Jenkins should allow you to specify multiple spot instance types, as well as non-spots. When launching instance, Jenkins should check spot prices and select the cheapest one. (Possibly this could be based on average of spot price history of last 12h.) Near the end of each billing cycle, Jenkins should look for opportunities to kill the existing workers and restart with a new type if it is significantly cheaper. Add Comment
[JIRA] (JENKINS-13792) Support for conditional post-build actions
Title: Message Title Dominik Bartholdi assigned an issue to Unassigned Jenkins / JENKINS-13792 Support for conditional post-build actions Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36378) Jenkins Server caught Blue Dump Screen and crashed
Title: Message Title Amit Kumar assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-36378 Jenkins Server caught Blue Dump Screen and crashed Change By: Amit Kumar Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 James Dumay created an issue Jenkins / JENKINS-36377 When a developer creates a new branch it is automatically favourited Issue Type: Story Assignee: James Dumay Components: blueocean-plugin Created: 2016/Jul/01 3:02 AM Priority: Minor Reporter: James Dumay In Scope Add Comment This message was
[JIRA] (JENKINS-36209) Queued items should show on the activity tab
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36209 Queued items should show on the activity tab Change By: James Dumay Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36209) Queued items should show on the activity tab
Title: Message Title James Dumay commented on JENKINS-36209 Re: Queued items should show on the activity tab Tom FENNELLY looks like Vivek Pandey landed the change needed to fix this in https://github.com/jenkinsci/blueocean-plugin/commit/3a5969485e41fabd7a3ae5789f4e8846d7936b95 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title daryl piffre commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules I'm having the same problem as well. Poll still triggers after setting excluded messages/users It's kinda important to us and probably others because we use maven-release-plugin, as shown in the example in the snippet generator. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36170) API to determine if a step has logs or not
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-36170 API to determine if a step has logs or not Change By: Vivek Pandey Sprint: 1.0- m10 m11 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title Vivek Pandey resolved as Fixed Jenkins / JENKINS-36208 Queued items are not showing up Change By: Vivek Pandey Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35766) REST API must use CORS
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-35766 REST API must use CORS Change By: Vivek Pandey Sprint: 1.0- m10 m11 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35783) REST API must only be authenticated using JWT
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-35783 REST API must only be authenticated using JWT Change By: Vivek Pandey Sprint: 1.0- m10 m11 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35810) Developer sees the Branches tab organised by relevance
Title: Message Title Vivek Pandey commented on JENKINS-35810 Re: Developer sees the Branches tab organised by relevance Nothing needed from API. Branches API support favouriting rest I think is all needed to be done in UI code. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35884) API for testing a entities capabilities for the UI
Title: Message Title Vivek Pandey resolved as Fixed Jenkins / JENKINS-35884 API for testing a entities capabilities for the UI Change By: Vivek Pandey Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36376) Annotate API model classes with Capability annotation
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-36376 Annotate API model classes with Capability annotation Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Jul/01 1:15 AM Priority: Minor Reporter: Vivek Pandey At present /rest/classes/:id API gives model class names in the response to a given class that extends from them. To avoid any bug resulting from future refactoring its better we annotated them with @Capability annotation and assign them appropriate fully qualified capability names. See https://github.com/jenkinsci/capability-annotation for details. Add Comment
[JIRA] (JENKINS-35768) Developer can filter the activity list to a specific branch
Title: Message Title James Dumay commented on JENKINS-35768 Re: Developer can filter the activity list to a specific branch That's great thanks mate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36253) Add Annotations to Kubernetes Pod Template
Title: Message Title Michael Chletsos commented on JENKINS-36253 Re: Add Annotations to Kubernetes Pod Template I added a PR for this Issue - please review when you have time. Carlos Sanchez Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36273) Add "organization" filter to /search API
Title: Message Title Vivek Pandey resolved as Fixed Jenkins / JENKINS-36273 Add "organization" filter to /search API Change By: Vivek Pandey 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title Vivek Pandey commented on JENKINS-35768 Re: Developer can filter the activity list to a specific branch From API perspective, no additional work is needed. To get 10 branches using pagination, use start and limit query parameters. /rest/organizations/jenkins/pipelines/:id/branches/?start=0=10 will give 10 recent run branches. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35799) Developer wants to use Bitbucket as a branch source
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35799 Developer wants to use Bitbucket as a branch source Change By: James Dumay Sprint: 1.0-m11 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35795) API for acknowledging request for user input in a pipeline
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35795 API for acknowledging request for user input in a pipeline Change By: James Dumay Sprint: 1.0-m11 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35799) Developer wants to use Bitbucket as a branch source
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35799 Developer wants to use Bitbucket as a branch source Change By: James Dumay Sprint: 1.0-m11 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36368) Release BlueOcean alpha-1
Title: Message Title Vivek Pandey resolved as Fixed mvn release:prepare release:perform completed successfully. All artifacts appear in http://repo.jenkins-ci.org/public/io/jenkins/blueocean/. According to https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins, once the plugin artifacts land in the maven repo, its gets pushed to update center eventually. It updates every 4 hours. Jenkins / JENKINS-36368 Release BlueOcean alpha-1 Change By: Vivek Pandey Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Alastair D'Silva commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. the % encoding also breaks some makefiles, where the path ends up in the (generated) makefile - '%' is a special character and is misinterpreted. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35884) API for testing a entities capabilities for the UI
Title: Message Title Vivek Pandey started work on JENKINS-35884 Change By: Vivek Pandey 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-18141) BuildParameters: Support for "Password"
Title: Message Title mstave commented on JENKINS-18141 Re: BuildParameters: Support for "Password" Are you sure this made it in? I don't see it @ https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.jobs.FreeStyleJob.parameters and searching for passwordParameterDefinition didn't show 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-22126) envinject overrides build parameters with node environment
Title: Message Title Daniel Serodio updated an issue Jenkins / JENKINS-22126 envinject overrides build parameters with node environment Change By: Daniel Serodio Environment: Environment Injector Plugin 1.89 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title Coltrey Mather commented on JENKINS-34644 Re: Stage View Shows Excessively Long Full Run Time Figures For complete-ishness, here's 100.xml: "workflow-support@2.1"> "org.jenkinsci.plugins.workflow.cps.nodes.StepAtomNode" plugin="workflow-cps@2.3"> 99 100 org.jenkinsci.plugins.workflow.steps.SleepStep "workflow-api@2.1"> 1467300509547 I think the answer is yes: [root@jenkins-master1 workflow]# grep TimingAction -A1 * 100.xml:"workflow-api@2.1"> 100.xml- 1467300509547 100.xml: 100.xml- -- 101.xml:"workflow-api@2.1"> 101.xml- 1467300569571 101.xml: 101.xml- -- 102.xml:"workflow-api@2.1"> 102.xml- 1467300570898 102.xml: 102.xml- -- 103.xml:"workflow-api@2.1"> 103.xml- 1467300570899 103.xml: 103.xml- -- 104.xml:"workflow-api@2.1"> 104.xml- 1467300570900 104.xml: 104.xml- -- 105.xml:"workflow-api@2.1"> 105.xml- 1467300630933 105.xml: 105.xml- -- 106.xml:"workflow-api@2.1"> 106.xml- 1467300632244 106.xml: 106.xml- -- 107.xml:"workflow-api@2.1"> 107.xml- 1467300632244 107.xml: 107.xml- -- 108.xml:"workflow-api@2.1"> 108.xml- 1467300632245 108.xml: 108.xml- -- 109.xml:"workflow-api@2.1"> 109.xml- 1467300634605 109.xml: 109.xml- -- 10.xml:"workflow-api@2.1"> 10.xml- 1467299613477 10.xml: 10.xml- -- 110.xml:"workflow-api@2.1"> 110.xml- 1467300634606 110.xml: 110.xml- -- 111.xml:"workflow-api@2.1"> 111.xml- 1467300646581 111.xml: 111.xml- -- 112.xml:"workflow-api@2.1"> 112.xml- 1467300646587 112.xml: 112.xml- -- 113.xml:"workflow-api@2.1"> 113.xml- 1467300646624 113.xml: 113.xml- -- 114.xml:"workflow-api@2.1"> 114.xml- 1467300646688 114.xml: 114.xml- -- 115.xml:"workflow-api@2.1"> 115.xml- 1467300646745 115.xml: 115.xml- -- 11.xml:"workflow-api@2.1"> 11.xml- 1467299613478 11.xml: 11.xml- -- 12.xml:"workflow-api@2.1"> 12.xml- 1467299613479 12.xml: 12.xml- -- 13.xml:"workflow-api@2.1"> 13.xml- 1467299614366 13.xml: 13.xml- -- 14.xml:"workflow-api@2.1"> 14.xml- 1467299614605 14.xml: 14.xml- -- 15.xml:"workflow-api@2.1"> 15.xml- 1467299614605 15.xml: 15.xml- -- 16.xml:"workflow-api@2.1"> 16.xml- 1467299615321 16.xml: 16.xml- -- 17.xml:"workflow-api@2.1"> 17.xml- 1467299615960 17.xml: 17.xml- -- 18.xml:"workflow-api@2.1"> 18.xml- 1467299615961 18.xml: 18.xml- -- 19.xml:"workflow-api@2.1"> 19.xml- 1467299615962 19.xml: 19.xml- -- 20.xml:"workflow-api@2.1"> 20.xml- 1467299615962 20.xml: 20.xml- -- 21.xml:"workflow-api@2.1"> 21.xml- 1467299616246 21.xml: 21.xml- -- 22.xml:"workflow-api@2.1"> 22.xml- 1467299680467 22.xml: 22.xml- -- 23.xml:"workflow-api@2.1"> 23.xml- 1467299951871 23.xml: 23.xml- -- 24.xml:"workflow-api@2.1"> 24.xml- 1467300121319 24.xml: 24.xml- -- 25.xml:"workflow-api@2.1"> 25.xml- 1467300121337 25.xml:
[JIRA] (JENKINS-35314) p4 Plugin does not trigger Pipeline builds
Title: Message Title Kyle Mott commented on JENKINS-35314 Re: p4 Plugin does not trigger Pipeline builds I don't think it's running parallel sync (enable: false in 'parallel' block). Should I remove that 'parallel' option entirely? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35837) Developer can view the dashboard and see the cards update in realtime
Title: Message Title James Dumay commented on JENKINS-35837 Re: Developer can view the dashboard and see the cards update in realtime Cliff Meyers yes, if something is favourited it should not appear in the list below. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36375) Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Title: Message Title Eyzen Medina commented on JENKINS-36375 Re: Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs I'm using change-assembly-version-plugin 1.5.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-36375) Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Title: Message Title
Eyzen Medina created an issue
Jenkins / JENKINS-36375
Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Issue Type:
Bug
Assignee:
Sanketh PB
Components:
change-assembly-version-plugin
Created:
2016/Jun/30 9:49 PM
Environment:
master Linux, Slave: windows Jenkins ver. 2.11
Priority:
Minor
Reporter:
Eyzen Medina
The plugin is adding a "?" char to all AssemblyInfo.cs files, Ex. ?using System.Reflection; using System.Runtime.CompilerServices; using System.Runtime.InteropServices; // General Information about an assembly is controlled through the following // set of attributes. Change these attribute values to modify the information It do change the assembyVersion line correctly [assembly: AssemblyVersion("4.6.7.1")] But the build is failing because the ? at the beginning of the file
Add Comment
[JIRA] (JENKINS-36361) javax.servlet.ServletException in pluginmanager
Title: Message Title S Raigner edited a comment on JENKINS-36361 Re: javax.servlet.ServletException in pluginmanager Similar problem here. Will checkout subversion workaround. Jenkins wer. 1594. ubuntu 12.04 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36361) javax.servlet.ServletException in pluginmanager
Title: Message Title S Raigner commented on JENKINS-36361 Re: javax.servlet.ServletException in pluginmanager Similar problem here. Will checkout subversion workaround. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-880) Per module filtering of java.net commit e-mail
Title: Message Title Alex Earl closed an issue as Incomplete Jenkins / JENKINS-880 Per module filtering of java.net commit e-mail Change By: Alex Earl 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-35837) Developer can view the dashboard and see the cards update in realtime
Title: Message Title James Dumay commented on JENKINS-35837 Re: Developer can view the dashboard and see the cards update in realtime Cliff Meyers is JENKINS-35996 related? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35837) Developer can view the dashboard and see the cards update in realtime
Title: Message Title James Dumay commented on JENKINS-35837 Re: Developer can view the dashboard and see the cards update in realtime Cliff Meyers you had me at animations Yes, the animation style we discussed is relevant here. However, feel free to tweak it to get it 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-36374) troubleshooting ldap authentication failure
Title: Message Title Sajala Rajendran created an issue Jenkins / JENKINS-36374 troubleshooting ldap authentication failure Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ldap-plugin Created: 2016/Jun/30 9:27 PM Priority: Major Reporter: Sajala Rajendran I am trying to integrate my corporate LDAP with jenkins. I tried different combinations of the LDAP parameters, the authentication would simply not work. It does not throw any error. I do not see anything in the logs either. Is there a way to troubleshoot LDAP related issues. Is there anywhere else I could look to see what error it is actually throwing? Also is there a way I could test the LDAP authentication on the jenkins page directly something like a test connection. Add Comment
[JIRA] (JENKINS-36371) NullPointerException in WebappClassLoader.findResources
Title: Message Title Andres Garcia updated an issue Jenkins / JENKINS-36371 NullPointerException in WebappClassLoader.findResources Change By: Andres Garcia Summary: Builds failure triggered error NullPointerException in WebappClassLoader.findResources Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36287) Builds failure triggered via Poll SCM when execute a system groovy script.
Title: Message Title Andres Garcia resolved as Not A Defect Jenkins / JENKINS-36287 Builds failure triggered via Poll SCM when execute a system groovy script. Change By: Andres Garcia Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36287) Builds failure triggered via Poll SCM when execute a system groovy script.
Title: Message Title Andres Garcia closed an issue as Not A Defect Jenkins / JENKINS-36287 Builds failure triggered via Poll SCM when execute a system groovy script. Change By: Andres Garcia Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36372) After resuming build, newly loaded scripts do not share root binding
Title: Message Title Jesse Glick commented on JENKINS-36372 Re: After resuming build, newly loaded scripts do not share root binding Seems this can be fixed by explicitly storing scripts in the CpsThreadGroup. workflow-cps-global-lib does not seem to be affected, since apparently those scripts do not share a Binding with the main script to begin with. I do not exactly understand why not, but at any rate I see no reason to try to support sharing of root bindings here if no one is clamoring for it; better to pass in variables explicitly when you need them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36373) SAML Plugin Disappears when Jenkins is restarted
Title: Message Title Douglas Anastasia created an issue Jenkins / JENKINS-36373 SAML Plugin Disappears when Jenkins is restarted Issue Type: Bug Assignee: Ben McCann Components: saml-plugin Created: 2016/Jun/30 9:17 PM Environment: Jenkins version 2.10, Ubuntu Linux 14.04.4, AWS EC2 Instance Priority: Major Reporter: Douglas Anastasia This is the only plugin that disappears, once configured, when Jenkins is restarted. We had the plugin sucessfully working and was able to login to the server. Add Comment
[JIRA] (JENKINS-35828) Create a card component
Title: Message Title James Dumay commented on JENKINS-35828 Re: Create a card component Cliff Meyers when something is favourited in the card could we make the full star color white? That should make it work with any background colour Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35828) Create a card component
Title: Message Title James Dumay commented on JENKINS-35828 Re: Create a card component Cliff Meyers oh the indicators should be white Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35828) Create a card component
Title: Message Title James Dumay commented on JENKINS-35828 Re: Create a card component Cliff Meyers for the icons for commit and branch we are using https://octicons.github.com Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title K P commented on JENKINS-30744 Re: multibranch issues if branch contains / I tried the workaround above from Joost van der Griendt which worked for CMake (which does not like % in paths) but then my tests, which use Matlab, fail as now there is a '@' in the path instead (Matlab will also fail with % in the path) A real fix for this would be really useful, as now I'm having to copy everything to a temp folder to run everything (and clean-up is a pain). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35837) Developer can view the dashboard and see the cards update in realtime
Title: Message Title James Dumay commented on JENKINS-35837 Re: Developer can view the dashboard and see the cards update in realtime Thats in scope for this ticket. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36372) After resuming build, newly loaded scripts do not share root binding
Title: Message Title Jesse Glick started work on JENKINS-36372 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36371) Builds failure triggered error NullPointerException in WebappClassLoader.findResources
Title: Message Title Andres Garcia updated an issue Jenkins / JENKINS-36371 Builds failure triggered error NullPointerException in WebappClassLoader.findResources Change By: Andres Garcia Attachment: task_history.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-35837) Developer can view the dashboard and see the cards update in realtime
Title: Message Title Cliff Meyers commented on JENKINS-35837 Re: Developer can view the dashboard and see the cards update in realtime James Dumay I recall a conversation from Japan where we talked about hiding any favorited projects in the list below, so we aren't displaying them on the screen twice. Is that in scope for this ticket? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36371) Builds failure triggered error NullPointerException in WebappClassLoader.findResources
Title: Message Title
Andres Garcia updated an issue
Jenkins / JENKINS-36371
Builds failure triggered error NullPointerException in WebappClassLoader.findResources
Change By:
Andres Garcia
Builds triggered via Poll SCM end in errori see this page http://stackoverflow.com/questions/7482503/how-to-avoid-nullpointerexception-in-webappclassloader-findresources but i have the jar in /apache-tomcat-7.0.47/webapps/jenkins/WEB-INF/lib This error is solved after restar web server {noformat}ERROR: Build step failed with exceptionjava.lang.NullPointerException at org.apache.catalina.loader.WebappClassLoader.findResources(WebappClassLoader.java:1334) at java.lang.ClassLoader.getResources(ClassLoader.java:1185) at java.lang.ClassLoader.getResources(ClassLoader.java:1181) at hudson.util.MaskingClassLoader.getResources(MaskingClassLoader.java:89) at java.lang.ClassLoader.getResources(ClassLoader.java:1181) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) at hudson.PluginFirstClassLoader.findResources(PluginFirstClassLoader.java:79) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935) at hudson.PluginFirstClassLoader.findResources(PluginFirstClassLoader.java:87) at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44) at jenkins.ClassLoaderReflectionToolkit._findResources(ClassLoaderReflectionToolkit.java:103) at hudson.PluginManager$UberClassLoader.findResources(PluginManager.java:1171) at java.lang.ClassLoader.getResources(ClassLoader.java:1185) at java.lang.ClassLoader.getResources(ClassLoader.java:1181) at org.codehaus.groovy.transform.ASTTransformationVisitor.doAddGlobalTransforms(ASTTransformationVisitor.java:194) at org.codehaus.groovy.transform.ASTTransformationVisitor.addGlobalTransforms(ASTTransformationVisitor.java:187) at org.codehaus.groovy.transform.ASTTransformationVisitor.addPhaseOperations(ASTTransformationVisitor.java:150) at org.codehaus.groovy.control.CompilationUnit.(CompilationUnit.java:186) at org.codehaus.groovy.control.CompilationUnit.(CompilationUnit.java:118) at groovy.lang.GroovyClassLoader.createCompilationUnit(GroovyClassLoader.java:476) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:290) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:281) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:731) at groovy.lang.GroovyShell.parse(GroovyShell.java:743) at groovy.lang.GroovyShell.parse(GroovyShell.java:723) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:680) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:666) at hudson.plugins.groovy.SystemGroovy.perform(SystemGroovy.java:81) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at
[JIRA] (JENKINS-35837) Developer can view the dashboard and see the cards update in realtime
Title: Message Title Cliff Meyers commented on JENKINS-35837 Re: Developer can view the dashboard and see the cards update in realtime James Dumay did you have something in particular in mind for animation? Something like we talked about for the table anim when a card is added or removed? Are there other scenarios we should animate? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35837) Developer can view the dashboard and see the cards update in realtime
Title: Message Title Cliff Meyers started work on JENKINS-35837 Change By: Cliff Meyers Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36372) After resuming build, newly loaded scripts do not share root binding
Title: Message Title Jesse Glick commented on JENKINS-36372 Re: After resuming build, newly loaded scripts do not share root binding they are held implicitly somewhere Specifically: this - value: WorkflowScript #1 <- value - class: java.util.HashMap$Node, value: WorkflowScript #1 <- [8] - class: java.util.HashMap$Node[], value: java.util.HashMap$Node #36691 <- table - class: java.util.HashMap, value: java.util.HashMap$Node[] #11010 <- locals - class: com.cloudbees.groovy.cps.impl.FunctionCallEnv, value: java.util.HashMap #10890 <- parent - class: com.cloudbees.groovy.cps.impl.BlockScopeEnv, value: com.cloudbees.groovy.cps.impl.FunctionCallEnv #2 <- e - class: com.cloudbees.groovy.cps.impl.SequenceBlock$ContinuationImpl, value: com.cloudbees.groovy.cps.impl.BlockScopeEnv #1 <- k - class: com.cloudbees.groovy.cps.Continuable, value: com.cloudbees.groovy.cps.impl.SequenceBlock$ContinuationImpl #1 <- program - class: org.jenkinsci.plugins.workflow.cps.CpsThread, value: com.cloudbees.groovy.cps.Continuable #1 <- value - class: java.util.TreeMap$Entry, value: org.jenkinsci.plugins.workflow.cps.CpsThread #1 <- root - class: java.util.TreeMap, value: java.util.TreeMap$Entry #1434 <- threads - class: org.jenkinsci.plugins.workflow.cps.CpsThreadGroup, value: java.util.TreeMap #1363 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title Sam Van Oort commented on JENKINS-34644 Re: Stage View Shows Excessively Long Full Run Time Figures Note from investigation: last stage in the pipeline, negative pauseDuration could come from https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/src/main/java/com/cloudbees/workflow/rest/external/StageNodeExt.java#L122 if the durationMillis are negative. startTime for that stage is positive... and duration exactly equal to it, but negative. That means endTime was 0... which only happens if there's no TimingAction set on the next stage node or the flow end node, AFAICT. So the million dollar question to confirm the theory: in the last .xml file for jobs/$jobName/builds/2/workflow/ (something higher than 94), does the XML contain a TimingAction with a startTime? I think solution here is probably to check if the TimingAction is or is not set here, and not do duration computation if it isn't set. Coltrey Mather any chance you guys have that XML handy? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35828) Create a card component
Title: Message Title Cliff Meyers commented on JENKINS-35828 Re: Create a card component PR's: https://github.com/jenkinsci/jenkins-design-language/pull/68 https://github.com/jenkinsci/blueocean-plugin/pull/310 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36372) After resuming build, newly loaded scripts do not share root binding
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-36372 After resuming build, newly loaded scripts do not share root binding Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Jun/30 8:20 PM Priority: Major Reporter: Jesse Glick Normally a Binding from the main CpsScript is shared with those from scripts created via load, because InvokerHelper.createScript links them to the binding defined in CpsGroovyShell.context. After the build is resumed from disk, each time SerializableScript.readResolve is called, it uses a distinct Binding with the same variables as in the original program. So the main script and any scripts already loaded are OK, or at least have the same bindings as they did before; presumably subsequent changes to the main script's bindings would no longer be visible to loaded scripts. The more visible problem is that the shell's binding is now empty (because it is a fresh instance from CpsFlowExecution.parseScript), so the next time load is called, that new script gets a clone of an empty binding—so it only gets a DSL bound via CpsScript.$initialize, nothing more. Making SerializableScript save the original Binding to the stream is not an option, since Binding is not Serializable. You would think that reparse could somehow track the bindings in the Script it returns, but in fact this instance is discarded—only its Class is used, since the actual instance is produced by deserialization. You might then think that CpsFlowExecution.loadProgramAsync could make sure that the context of the shell got linked to the binding of the main script (and ideally the same for previously loaded scripts, too). But after deserialization, we only have a CpsThreadGroup, and it is not obvious how to find the CpsScript instance(s) associated with it: they are held implicitly somewhere in the Continuation. Kohsuke Kawaguchi help!
[JIRA] (JENKINS-35828) Create a card component
Title: Message Title Cliff Meyers commented on JENKINS-35828 Re: Create a card component James Dumay this is mostly ready but I do have a few notes / questions: Note: need to round corners. Could not find the glyphs from the original design file, so I quickly subbed in some things from material icons that are close-ish, but I am sure they are terrible It'd be nice if we could avoid too many one-off icons - maybe there's something else in Material you think fits better? Could you give me some direction as to what the queued, running and not-built status indicators should look like? These are the default styles the indicator is giving. Guessing we want things a bit more white. The selected favorite unfortunately blends in with the Unstable color. Thoughts? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36371) Builds failure triggered error NullPointerException in WebappClassLoader.findResources
Title: Message Title Andres Garcia created an issue Jenkins / JENKINS-36371 Builds failure triggered error NullPointerException in WebappClassLoader.findResources Issue Type: Bug Assignee: Unassigned Attachments: error_class_loader.png Components: jenkins-tracker Created: 2016/Jun/30 8:18 PM Environment: Red Hat Enterprise Linux Server release 6.1 x86_64 Labels: jenkins java tomcat web Priority: Minor Reporter: Andres Garcia Builds triggered via Poll SCM end in error i see this page http://stackoverflow.com/questions/7482503/how-to-avoid-nullpointerexception-in-webappclassloader-findresources but i have the jar in /apache-tomcat-7.0.47/webapps/jenkins/WEB-INF/lib ERROR: Build step failed with exception java.lang.NullPointerException at org.apache.catalina.loader.WebappClassLoader.findResources(WebappClassLoader.java:1334) at java.lang.ClassLoader.getResources(ClassLoader.java:1185) at java.lang.ClassLoader.getResources(ClassLoader.java:1181) at hudson.util.MaskingClassLoader.getResources(MaskingClassLoader.java:89) at java.lang.ClassLoader.getResources(ClassLoader.java:1181) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) at
[JIRA] (JENKINS-35828) Create a card component
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-35828 Create a card component Change By: Cliff Meyers Attachment: pipeline-card-status.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-36366) ATH AnalysisCollectorPluginTest#should_deactivate_all_other_trend_graphs failing
Title: Message Title Ulli Hafner commented on JENKINS-36366 Re: ATH AnalysisCollectorPluginTest#should_deactivate_all_other_trend_graphs failing I'll have a look at it as soon as my laptop is back from repair... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title Coltrey Mather commented on JENKINS-34644 Re: Stage View Shows Excessively Long Full Run Time Figures It does not include parallel structures, but it is in a finally block. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title Sam Van Oort commented on JENKINS-34644 Re: Stage View Shows Excessively Long Full Run Time Figures Thanks Joseph Smith – that shows where the problem is: Run time for run #2 includes: "queueDurationMillis": 5493, "pauseDurationMillis": -1467300506456, and this is due to stage "Opsworks Tear Down" having the following timing info: "startTimeMillis": 1467300506456, "durationMillis": -1467300506456, "pauseDurationMillis": -1467300506456 This points at a bug in the stage timing computation in the REST API (not entirely surprising, it's deceptively complex, and the overall algorithm has several known issues that are being addressed with a new implementation). One more question: is there anything odd about the "Opsworks Tear Down" stage in run #2? Does it include parallel structures? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1: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-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Daniel Spilker commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class Yes, Job DSL already uses the Structs plugin for it's "Automatically Generated DSL" feature (couldn't find a better name...) , see https://github.com/jenkinsci/job-dsl-plugin/wiki/Automatically-Generated-DSL. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36370) Can't set Credentials for SauceOnDemand plugin
Title: Message Title Xu Wang started work on JENKINS-36370 Change By: Xu Wang 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-36370) Can't set Credentials for SauceOnDemand plugin
Title: Message Title Xu Wang commented on JENKINS-36370 Re: Can't set Credentials for SauceOnDemand plugin Created pull request to fix it: https://github.com/jenkinsci/job-dsl-plugin/pull/875 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title Joseph Smith commented on JENKINS-34644 Re: Stage View Shows Excessively Long Full Run Time Figures It is currently displaying, Average stage times: (Average full run time: ~11y 230d) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title
Coltrey Mather commented on JENKINS-34644
Re: Stage View Shows Excessively Long Full Run Time Figures
j smith asked me to add this - this is one branch in a pipeline multibranch job:
[{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/wfapi/describe"
},
"changesets": {
"href": "/job/p-c-b/job/PSAE-61/4/wfapi/changesets"
},
"artifacts": {
"href": "/job/p-c-b/job/PSAE-61/4/wfapi/artifacts"
}
},
"id": "4",
"name": "#4",
"status": "SUCCESS",
"startTimeMillis": 1467303127055,
"endTimeMillis": 1467303874774,
"durationMillis": 742082,
"queueDurationMillis": 5637,
"pauseDurationMillis": 0,
"stages": [{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/11/wfapi/describe"
}
},
"id": "11",
"name": "Clean workspace",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303132692,
"durationMillis": 1061,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/14/wfapi/describe"
}
},
"id": "14",
"name": "Checkout source",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303133753,
"durationMillis": 1877,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/17/wfapi/describe"
}
},
"id": "17",
"name": "Build App",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303135630,
"durationMillis": 189881,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/27/wfapi/describe"
}
},
"id": "27",
"name": "Package Cookbook",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303325511,
"durationMillis": 23010,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/36/wfapi/describe"
}
},
"id": "36",
"name": "Publish to S3",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303348521,
"durationMillis": 5144,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/39/wfapi/describe"
}
},
"id": "39",
"name": "Archive site",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303353665,
"durationMillis": 2667,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/45/wfapi/describe"
}
},
"id": "45",
"name": "Opsworks auto deployment",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303356332,
"durationMillis": 314976,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/87/wfapi/describe"
}
},
"id": "87",
"name": "Test",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303671308,
"durationMillis": 1951,
"pauseDurationMillis": 0
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/4/execution/node/93/wfapi/describe"
}
},
"id": "93",
"name": "Opsworks Tear Down",
"execNode": "master",
"status": "SUCCESS",
"startTimeMillis": 1467303673259,
"durationMillis": 201515,
"pauseDurationMillis": 0
}]
},
{
"_links": {
"self": {
"href": "/job/p-c-b/job/PSAE-61/3/wfapi/describe"
},
"changesets": {
"href": "/job/p-c-b/job/PSAE-61/3/wfapi/changesets"
},
"artifacts": {
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title Sam Van Oort commented on JENKINS-34644 Re: Stage View Shows Excessively Long Full Run Time Figures j smith Since you have a case where it's actively occurring, any chance you could dump the /job/$JobName/wfapi/runs JSON content and attach it (along with what it's reporting for the full run time)? I've had difficulty figuring out what triggers this bug, and having the data it's using for the computation would make it infinitely easier to trace the cause and solve it. 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-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Jesse Glick commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class Kanstantsin Shautsou if you mean a reference implementation of using @Symbol generally, that is already on Daniel Spilker’s radar I think. job-dsl has no reason to use the particular syntax proposed here; it is already using builder syntax with hand-coded symbols, so it would just be a matter of using the official annotation. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34644) Stage View Shows Excessively Long Full Run Time Figures
Title: Message Title j smith commented on JENKINS-34644 Re: Stage View Shows Excessively Long Full Run Time Figures I am currently seeing this error occur on builds with under 10 runs and that have only been successful. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36281) Dashboard trend graphs not displayed following plugin upgrade
Title: Message Title Paul Eipper commented on JENKINS-36281 Re: Dashboard trend graphs not displayed following plugin upgrade Thanks it worked: remove JENKINS_HOME/plugins/dashboard-view/WEB-INF/lib/joda-time-1.6.jar copy JENKINS_HOME/plugins/analysis-core/WEB-INF/lib/joda-time-2.1.jar to that folder edit the files and change the version listed from "1.6" to "2.1": JENKINS_HOME/plugins/dashboard-view/WEB-INF/licenses.xml JENKINS_HOME/plugins/dashboard-view/META-INF/maven/org.jenkins-ci.plugins/dashboard-view/pom.xml restart Jenkins Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36370) Can't set Credentials for SauceOnDemand plugin
Title: Message Title Xu Wang created an issue Jenkins / JENKINS-36370 Can't set Credentials for SauceOnDemand plugin Issue Type: Bug Assignee: Xu Wang Components: job-dsl-plugin Created: 2016/Jun/30 6:36 PM Priority: Minor Reporter: Xu Wang SauceOnDemand plugin has a credentialId parameter (see https://github.com/jenkinsci/sauce-ondemand-plugin/blob/master/src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper.java), but job-dsl-plugin currently can't set it because it doesn't support credentialId (see https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/wrapper/SauceOnDemandContext.groovy). Add Comment
[JIRA] (JENKINS-36369) Jenkins ver. 1.651.3 SSL issue
Title: Message Title jurgezero created an issue Jenkins / JENKINS-36369 Jenkins ver. 1.651.3 SSL issue Issue Type: Bug Assignee: Unassigned Components: rally-plugin Created: 2016/Jun/30 6:25 PM Environment: Windows 2008 with Jenkins ver. 1.651.3 Priority: Major Reporter: jurgezero After upgrading to Jenkins ver. 1.651.3, we get the following error in the Rally Plugin: "uninitialized constant OpenSSL::SSL" If we downgrade to Jenkins ver. 1.642.4, the plugin works fine. Please advise. Add Comment
[JIRA] (JENKINS-31118) Workflow jobs that are waiting for input should have a visual cue in build history
Title: Message Title Marc Esher commented on JENKINS-31118 Re: Workflow jobs that are waiting for input should have a visual cue in build history Big +1 on this. Right now, it's very hard to tell when something is waiting on input unless you know exactly what you're looking for. Making it more obvious / prominent would be a big UX win. Related, I had a job that kicked off, and we didn't know it was waiting on input. Several days later, the thing is still waiting, and then it wouldn't abort or proceed when we clicked the links, no matter how many times. The job would not cancel, either. The only thing that cleared out its cobwebs was a Jenkins restart. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27552) If deleting older verions, provide option for sorting
Title: Message Title Brantone started work on JENKINS-27552 Change By: Brantone 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-35480) Execute shell FATAL: command execution failed
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-35480
Execute shell FATAL: command execution failed
Change By:
Rick Liu
When use "*Extended Choice Parameter plug-in*" together with "*JSON parameter type*",I'll hit the error below for "*Exeucte Shell*" in "*Promotion process / Action*".When use "*Extended Choice Parameter plug-in*" together with "*Basic Parameter Types*",then everything is ok.Below is the JSON groovy script I'm using:{code}import org.boon.Boon;def jsonEditorOptions = Boon.fromJson(/{disable_edit_json: true,disable_properties: true,no_additional_properties: false,disable_collapse: true,disable_array_add: false,disable_array_delete: false,disable_array_reorder: true,theme: "bootstrap2",iconlib:"bootstrap3",schema: {"type": "object","title": "Coverage Report Generator","properties": { "Report Description": { "type": "string", "propertyOrder": 1, "default": "Description", }, "Build File": { "type": "string", "propertyOrder": 2, "media" : { "binaryEncoding": "base64" }, "options" : { "include_filename": true }, }, "Coverage File": { "type": "string", "propertyOrder": 3, "media" : { "binaryEncoding": "base64" }, "options" : { "include_filename": true }, }, "Diff File": { "type": "string", "propertyOrder": 4, "media" : { "binaryEncoding": "base64" }, "options" : { "include_filename": true }, }, "Extra Coverage Files": { "type": "array", "propertyOrder": 5, "title": "Extra Coverage Files", "format": "table", "uniqueItems": true, "items": { "type": "object", "title": "Coverage Files", "properties": {"File": { "type": "string", "propertyOrder": 1, "media" : { "binaryEncoding": "base64" }, "options" : { "include_filename": true },} } } },}startval: [ ]}/);return jsonEditorOptions;{code} Under "Promotion process / Actions",I add an action "Execute shell" with commands below:{code}#!/bin/bashecho "test!!!"{code}And promotion job is always failed with:{code}[Test_Coverage_Report] $ /bin/bash -xe /tmp/hudson4980267768844983951.shFATAL: command execution failedjava.io.IOException: Cannot run program "/bin/bash" (in directory "/home/devops/jenkins_slave/workspace/ReviewBoard/Test_Coverage_Report"): error=7, Argument list too long at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1148) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title Rick Liu commented on JENKINS-35480 Re: Execute shell FATAL: command execution failed Ok I just found out this error happened only when I use "Extended Choice Parameter" plug-in and use "JSON parameter type". If I use "Extended Choice Parameter" plug-in and use "Basic Parameter Types ", then everything 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-27552) If deleting older verions, provide option for sorting
Title: Message Title Brantone commented on JENKINS-27552 Re: If deleting older verions, provide option for sorting Odd build results haven't posted here yet ... PR: https://github.com/jenkinsci/hockeyapp-plugin/pull/30 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-35480
Execute shell FATAL: command execution failed
Change By:
Rick Liu
Under "Promotion process / Actions",I add an action "Execute shell" with commands below:{code}#!/bin/bashecho "test!!!"{code}And promotion job is always failed with:{code}[Test_Coverage_Report] $ /bin/bash -xe /tmp/hudson4980267768844983951.shFATAL: command execution failedjava.io.IOException: Cannot run program "/bin/bash" (in directory "/home/devops/jenkins_slave/workspace/ReviewBoard/Test_Coverage_Report"): error=7, Argument list too long at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1148) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to jenkins-slave98(172.18.25.208)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.UserResponse.retrieve(UserRequest.java:220) at hudson.remoting.Channel.call(Channel.java:781) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:928) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:95) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:405) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:347) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.Run.run(Run.java:1676) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:286) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.io.IOException: error=7, Argument list too long at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:187) at java.lang.ProcessImpl.start(ProcessImpl.java:130) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1028) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-35480 Execute shell FATAL: command execution failed Change By: Rick Liu Component/s: extended-choice-parameter-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] (TEST-95) testlab1
Title: Message Title Svyatoslav Karachevcev closed an issue as Fixed test / TEST-95 testlab1 Change By: Svyatoslav Karachevcev 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] (TEST-95) testlab1
Title: Message Title Svyatoslav Karachevcev created an issue test / TEST-95 testlab1 Issue Type: Task Assignee: Svyatoslav Karachevcev Components: foo Created: 2016/Jun/30 6:06 PM Priority: Minor Reporter: Svyatoslav Karachevcev Add Comment This message was sent by 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-34953) pipeline-stage-view doesn't update when pipeline is in SCM
Title: Message Title Alex Suttmiller commented on JENKINS-34953 Re: pipeline-stage-view doesn't update when pipeline is in SCM I am seeing this behavior from behind a proxy, thus causing cross-domain _javascript_ refusals. Simon Watson do you see any errors in your browser console? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35480) Execute shell FATAL: command execution failed
Title: Message Title Rick Liu commented on JENKINS-35480 Re: Execute shell FATAL: command execution failed I just added the space between the hash-bang and /bin/bash, but still got error. #! /bin/bash -xe echo "test!!!" [Test_Coverage_Report] $ /bin/bash -xe /tmp/hudson1672939348743230101.sh FATAL: command execution failed java.io.IOException: Cannot run program "" (in directory "/home/devops/jenkins_slave/workspace/ReviewBoard/Test_Coverage_Report"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1148) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to jenkins-slave97(172.16.81.60)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.UserResponse.retrieve(UserRequest.java:220) at hudson.remoting.Channel.call(Channel.java:781) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:928) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:95) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:405) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:347) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.Run.run(Run.java:1676) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:286) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:187) at java.lang.ProcessImpl.start(ProcessImpl.java:130) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1028) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1148) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at
[JIRA] (JENKINS-34476) Allow the workflowLibs.git to be hosted someplace else
Title: Message Title Matt Traynham commented on JENKINS-34476 Re: Allow the workflowLibs.git to be hosted someplace else Michael Scharp I'm looking to do the same and find the https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Remote+Loader+Plugin somewhat lacking. Curious as why you have to restart? Does the original workflowLib.git have some commit hook that notifies Jenkins that the lib has been updated? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27552) If deleting older verions, provide option for sorting
Title: Message Title Brantone commented on JENKINS-27552 Re: If deleting older verions, provide option for sorting Pull Request inbound ... if you feel comfortable, download the code and give it a whirl ... I currently have it running on my system but we use an internal enterprise setup of HockeyApp. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27552) If deleting older verions, provide option for sorting
Title: Message Title Brantone assigned an issue to Brantone Jenkins / JENKINS-27552 If deleting older verions, provide option for sorting Change By: Brantone Assignee: Brantone Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36368) Release BlueOcean alpha-1
Title: Message Title Vivek Pandey started work on JENKINS-36368 Change By: Vivek Pandey 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-36334) Ability to configure Cisco Spark room at folder level
Title: Message Title Sikai Peng updated an issue Jenkins / JENKINS-36334 Ability to configure Cisco Spark room at folder level Change By: Sikai Peng Summary: Configure Ability to configure Cisco Spark room at folder level instead of system 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-36368) Release BlueOcean alpha-1
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-36368 Release BlueOcean alpha-1 Change By: Vivek Pandey Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36368) Release BlueOcean alpha-1
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-36368 Release BlueOcean alpha-1 Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Jun/30 5:38 PM Priority: Minor Reporter: Vivek Pandey We track any work related to blueocean alpha-1 release here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34517) Pipeline is unable to locate global libraries when build attempts to continue on restart
Title: Message Title Jesse Glick resolved as Fixed Released as 2.1. Jenkins / JENKINS-34517 Pipeline is unable to locate global libraries when build attempts to continue on restart Change By: Jesse Glick Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-36367) Pushing images from within withRegistry block sets tag without port number
Title: Message Title Lukasz Zachulski updated an issue Jenkins / JENKINS-36367 Pushing images from within withRegistry block sets tag without port number Change By: Lukasz Zachulski Summary: Pushing images from within withRegistry block set sets tag without port number Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36367) Pushing images from within withRegistry block set tag without port number
Title: Message Title
Lukasz Zachulski updated an issue
Jenkins / JENKINS-36367
Pushing images from within withRegistry block set tag without port number
Change By:
Lukasz Zachulski
Below pipeline DSL sets wrong tag when pushing image from within {{withRegistry}} block {code:java}DOCKER_REGISTRY_URL = "https://dockerregistry:443"DOCKER_REGISTRY_CREDENTIALS = 'myuser'node('docker') {stage 'checkout'checkout scmstage 'build'echo "${DOCKER_REGISTRY_URL}, ${DOCKER_REGISTRY_CREDENTIALS}"docker.withRegistry(DOCKER_REGISTRY_URL, DOCKER_REGISTRY_CREDENTIALS){def img = docker.build('myuser/img-deps:14.04', '14.04')img.push()}}{code}As the result I'm getting an error message:{code:java}docker tag --force=true myuser/img-deps:14.04 dockerregistry/myuser/img-deps:14.04Warning: '--force' is deprecated, it will be removed soon. See usage.[Pipeline] sh[master] Running shell script+ docker push dockerregistry/myuser/img-deps:14.04The push refers to a repository [docker.io/dockerregistry/myuser/img-deps]c3644055bd1d: Preparing...81a9ec52d927: Preparingunauthorized: authentication required[Pipeline] }[Pipeline] // withDockerRegistry...[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code 1Finished: FAILURE{code}It looks like the tag which is set by {{push}} method is set without missing proper *port number*.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36367) Pushing images from within withRegistry block set tag without port number
Title: Message Title Lukasz Zachulski assigned an issue to Jesse Glick Jenkins / JENKINS-36367 Pushing images from within withRegistry block set tag without port number Change By: Lukasz Zachulski Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36367) Pushing images from within withRegistry block set tag without port number
Title: Message Title Lukasz Zachulski assigned an issue to Unassigned Jenkins / JENKINS-36367 Pushing images from within withRegistry block set tag without port number Change By: Lukasz Zachulski Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36367) Pushing images from within withRegistry block set tag without port number
Title: Message Title
Lukasz Zachulski updated an issue
Jenkins / JENKINS-36367
Pushing images from within withRegistry block set tag without port number
Change By:
Lukasz Zachulski
Below pipeline DSL sets wrong tag when pushing image from within {{withRegistry}} block {code:java}DOCKER_REGISTRY_URL = "https://dockerregistry:443"DOCKER_REGISTRY_CREDENTIALS = 'myuser'node('docker') {stage 'checkout'checkout scmstage 'build'echo "${DOCKER_REGISTRY_URL}, ${DOCKER_REGISTRY_CREDENTIALS}"docker.withRegistry(DOCKER_REGISTRY_URL, DOCKER_REGISTRY_CREDENTIALS){def img = docker.build('myuser/img-deps:14.04', '14.04')img.push()}}{code}As the result I'm getting an error message:{code:java}docker tag --force=true myuser/img-deps:14.04 dockerregistry/myuser/img-deps:14.04Warning: '--force' is deprecated, it will be removed soon. See usage.[Pipeline] sh[master] Running shell script+ docker push dockerregistry/myuser/img-deps:14.04The push refers to a repository [docker.io/dockerregistry/myuser/img-deps]c3644055bd1d: Preparing...81a9ec52d927: Preparingunauthorized: authentication required[Pipeline] }[Pipeline] // withDockerRegistry...[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code 1Finished: FAILURE{code} It looks like the tag which is set by {{push}} is set without proper *port number*.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36367) Pushing images from within withRegistry block set tag without port number
Title: Message Title
Lukasz Zachulski updated an issue
Jenkins / JENKINS-36367
Pushing images from within withRegistry block set tag without port number
Change By:
Lukasz Zachulski
Below pipeline DSL sets wrong tag when pushing image from within {{withRegistry}} block {code:java}DOCKER_REGISTRY_URL = "https://dockerregistry:443"DOCKER_REGISTRY_CREDENTIALS = 'myuser'node('docker') {stage 'checkout'checkout scmstage 'build'echo "${DOCKER_REGISTRY_URL}, ${DOCKER_REGISTRY_CREDENTIALS}"docker.withRegistry(DOCKER_REGISTRY_URL, DOCKER_REGISTRY_CREDENTIALS){def img = docker.build('myuser/img-deps:14.04', '14.04')img.push()}}{code}As the result I'm getting an error message:{code:java}docker tag --force=true myuser/img-deps:14.04 dockerregistry/myuser/img-deps:14.04Warning: '--force' is deprecated, it will be removed soon. See usage. [Pipeline] sh[master] Running shell script+ docker push dockerregistry/myuser/img-deps:14.04The push refers to a repository [docker.io/dockerregistry/myuser/img-deps] {code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36367) Pushing images from within withRegistry block set tag without port number
Title: Message Title
Lukasz Zachulski updated an issue
Jenkins / JENKINS-36367
Pushing images from within withRegistry block set tag without port number
Change By:
Lukasz Zachulski
Below pipeline DSL sets wrong tag when pushing image from within {{withRegistry}} block {code:java}DOCKER_REGISTRY_URL = "https://dockerregistry:443"DOCKER_REGISTRY_CREDENTIALS = 'myuser'node('docker') {stage 'checkout'checkout scmstage 'build'echo "${DOCKER_REGISTRY_URL}, ${DOCKER_REGISTRY_CREDENTIALS}"docker.withRegistry(DOCKER_REGISTRY_URL, DOCKER_REGISTRY_CREDENTIALS){def img = docker.build('myuser/img-deps:14.04', '14.04')img.push()}}{code}As the result I'm getting an error message:{code:java}docker tag --force=true myuser/img-deps:14.04 dockerregistry/myuser/img-deps:14.04Warning: '--force' is deprecated, it will be removed soon. See usage.[Pipeline] sh[master] Running shell script+ docker push dockerregistry/myuser/img-deps:14.04The push refers to a repository [docker.io/dockerregistry/myuser/img-deps] c3644055bd1d: Preparing...81a9ec52d927: Preparingunauthorized: authentication required[Pipeline] }[Pipeline] // withDockerRegistry...[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code 1Finished: FAILURE {code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
