[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-60979  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory   
 

  
 
 
 
 

 
 Unassigning from Natasha since she was working on the plugin-installation-manager-tool and this appears to be the actual PluginManager in Jenkins proper. I've also updated the component to reflect the change. Ben, if you have a solution, feel free to make a PR!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204447.1580906476000.7713.1586277360260%40Atlassian.JIRA.

[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60979  
 
 
  Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory   
 

  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
Component/s: 
 core  
 
 
Component/s: 
 plugin-installation-manager-tool  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204447.1580906476000.7711.1586277360233%40Atlassian.JIRA.

[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60979  
 
 
  Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory   
 

  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
Assignee: 
 Natasha Stopa  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204447.1580906476000.7707.1586277120421%40Atlassian.JIRA.

[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-60979  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory   
 

  
 
 
 
 

 
 Were you trying to download the plugin using the plugin installation manger tool or is this happening when you're launching Jenkins? If the later, we should change the component to be against core since the `plugin-installation-manager-tool` is a separate thing and under core this would get more attention.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204447.1580906476000.8177.1581521580588%40Atlassian.JIRA.

[JIRA] (JENKINS-58242) Look into Failed Junit Test on Ubuntu

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-58242  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Look into Failed Junit Test on Ubuntu   
 

  
 
 
 
 

 
 The tests with `buildPlugin` should cover this as it tests on linux and windows. I think this is safe to close.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200305.1561669084000.2266.1567018500613%40Atlassian.JIRA.

[JIRA] (JENKINS-58242) Look into Failed Junit Test on Ubuntu

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-58242  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Look into Failed Junit Test on Ubuntu   
 

  
 
 
 
 

 
 I don't think that we're hitting this anymore? I think we can close.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200305.1561669084000.1039.1566932880464%40Atlassian.JIRA.

[JIRA] (JENKINS-58662) Allow users to specify a mirror URL which would point to an internal mirror of the public plugin repo

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-58662  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow users to specify a mirror URL which would point to an internal mirror of the public plugin repo   
 

  
 
 
 
 

 
 Would the --jenkins-update-center flag (and corresponding environment variable) work for you? This allows you to point to a different update center.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200944.1564072122000.942.1566930060211%40Atlassian.JIRA.

[JIRA] (JENKINS-58308) Warn users if plugins require higher version of Jenkins

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-58308  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warn users if plugins require higher version of Jenkins
 

  
 
 
 
 

 
 1) Go with the most recent, and warn if the plugin is incompatible. If someone requires an older version, then they'll have to request it. 2) No, I don't think so? Especially if paired with the requirement from #1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200416.1562109025000.12555.1563300240273%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-58217) Support Maven repository as an installation source

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-58217  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support Maven repository as an installation source   
 

  
 
 
 
 

 
 1) Yes. each plugin should be processed separately, I don't see why individual lines can't specify where the download happens. 2) Tim Jacomb would be in a better position to answer this. I think they should be together, but I'm not very involved with CasC.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200277.1561569498000.12548.1563300120696%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-58350) Move the plugins used for test to /test/resources

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58350  
 
 
  Move the plugins used for test to /test/resources   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Natasha Stopa  
 
 
Components: 
 plugin-installation-manager-tool  
 
 
Created: 
 2019-07-04 15:30  
 
 
Labels: 
 plugin-manager  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kristin Whetstone  
 

  
 
 
 
 

 
 Going through the entire codebase this morning, I found that the plugins jpis that are used for tests are really stored in the /src/resources folder rather than the /test/resources folder. Just move the plugins for test and make sure the tests still work.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 

[JIRA] (JENKINS-58110) Move "writeFailedPluginsToFile" out of PluginManager

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58110  
 
 
  Move "writeFailedPluginsToFile" out of PluginManager   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Natasha Stopa  
 
 
Components: 
 plugin-installation-manager-tool  
 
 
Created: 
 2019-06-20 04:10  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kristin Whetstone  
 

  
 
 
 
 

 
 As something for phase 2, it would make writing failed plugins to a file something that's configurable. Certain library consumers might prefer having that as a return option instead.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This 

[JIRA] (JENKINS-58075) Create demo for end of Phase 1 coding period

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58075  
 
 
  Create demo for end of Phase 1 coding period   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Natasha Stopa  
 
 
Components: 
 plugin-installation-manager-tool  
 
 
Created: 
 2019-06-18 15:33  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Kristin Whetstone  
 

  
 
 
 
 

 
 For the end of Phase 1 demos, there's a presentation which would cover what you found during this period and what was produced. This ticket is just to track that work.  Description found in the abstract here: https://docs.google.com/document/d/1rEIzZ56CObCIcxtPlQoxn-7B9oAchB82Vh4zd61AJ98/edit You should probably also talk about the effort to pull out the Plugin Installation Manager since that was a significant effort, and how interconnected everything was.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
  

[JIRA] (JENKINS-57977) Investigate Use of File Locks for Plugin Manager Tool

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-57977  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Investigate Use of File Locks for Plugin Manager Tool
 

  
 
 
 
 

 
 This is something that can probably just be pulled out wholesale.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199961.1560287923000.2590.1560871560363%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-58016) Move Parsing to Plugin Management CLI from Library

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-58016  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Move Parsing to Plugin Management CLI from Library
 

  
 
 
 
 

 
 Just doing some updates: some of this task looks like it was covered in PR#3. This should be used to: 
 
Pull out the parsing into a separate class 
Test that class 
Documenting how to run from the CLI 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200036.1560455413000.2588.1560871560340%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-58073) Can't install plugins when Jenkins is installed on a different subnet

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-58073  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't install plugins when Jenkins is installed on a different subnet   
 

  
 
 
 
 

 
 Hi, this is more of a docker problem, I think it has something to do with the networking there. I'd try asking on the jenkins IRC or gitter channel, or on the Jenkins mailing list. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200097.156086993.2503.1560870420130%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-58073) Can't install plugins when Jenkins is installed on a different subnet

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58073  
 
 
  Can't install plugins when Jenkins is installed on a different subnet   
 

  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
Component/s: 
 docker  
 
 
Component/s: 
 plugin-installation-manager-tool  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200097.156086993.2494.1560870300453%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-58073) Can't install plugins when Jenkins is installed on a different subnet

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58073  
 
 
  Can't install plugins when Jenkins is installed on a different subnet   
 

  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
Assignee: 
 Natasha Stopa  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200097.156086993.2497.1560870300502%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57971) Add user documentation to the Plugin Installation Manager tool

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-57971  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add user documentation to the Plugin Installation Manager tool   
 

  
 
 
 
 

 
 This should include how to launch the command line tool and how to use the library once it's ready for consumption.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199955.1560277111000.25756.1560320940131%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57972) Integrate the Plugin Manager tool into the Jenkins Docker image

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57972  
 
 
  Integrate the Plugin Manager tool into the Jenkins Docker image   
 

  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
Assignee: 
 Carlos Sanchez  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199956.1560277344000.25753.1560320760240%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57865) Enhance plugin installation manager by fixing installation script docker issues

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-57865  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Enhance plugin installation manager by fixing installation script docker issues   
 

  
 
 
 
 

 
 This seems like a good coding phase 2 goal. Right now, we're just focusing on getting the script to run.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199827.1559753516000.25750.1560320580110%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-36630) Migrate matrix-project to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-36630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Migrate matrix-project to parent pom   
 

  
 
 
 
 

 
 So after not working on this to eventually come back, I essentially discovered the same thing I ran into before, just now it's much more accurate. There was a subtle change in the htmlunit abilities which led to the input  

 

INFO: TESTING repeatable:INPUT.repeatable-delete @0 on 1 elements
Nov 22, 2016 5:38:23 AM com.gargoylesoftware.htmlunit.WebConsole$DefaultLogger info
INFO: @http://localhost:38685/jenkins/adjuncts/15a08f22/lib/form/repeatable/repeatable.js:131
@http://localhost:38685/jenkins/static/15a08f22/scripts/behavior.js:116
@http://localhost:38685/jenkins/static/15a08f22/scripts/behavior.js:107
@http://localhost:38685/jenkins/static/15a08f22/scripts/behavior.js:93
@http://localhost:38685/jenkins/adjuncts/15a08f22/lib/form/hetero-list/hetero-list.js:107
@http://localhost:38685/jenkins/static/15a08f22/scripts/hudson-behavior.js:558
next()@http://localhost:38685/jenkins/static/15a08f22/scripts/hudson-behavior.js:597
sequencer()@http://localhost:38685/jenkins/static/15a08f22/scripts/hudson-behavior.js:600
evalInnerHtmlScripts()@http://localhost:38685/jenkins/static/15a08f22/scripts/hudson-behavior.js:585
@http://localhost:38685/jenkins/static/15a08f22/scripts/hudson-behavior.js:556
@http://localhost:38685/jenkins/adjuncts/15a08f22/org/kohsuke/stapler/bind.js:57
@http://localhost:38685/jenkins/static/15a08f22/scripts/prototype.js:1655
@http://localhost:38685/jenkins/static/15a08f22/scripts/prototype.js:1600
@http://localhost:38685/jenkins/static/15a08f22/scripts/prototype.js:414
 

 I spent some time trying to determine if this is a jQuery thing since the physical act of issuing "on" falls in that section. However, really, the exact code that's failing the entire page render is for hover actions. Which is incredibly useless from the perspective of this situation. I'm currently investigating catching the failing script, and just continuing the render without setting the "hover" options.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 

[JIRA] (JENKINS-38437) The description for the deb package is cut off

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone updated  JENKINS-38437  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Delivered. Thanks all for the reviews.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38437  
 
 
  The description for the deb package is cut off   
 

  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
Status: 
 In Review 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 

[JIRA] (JENKINS-38437) The description for the deb package is cut off

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-38437  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The description for the deb package is cut off   
 

  
 
 
 
 

 
 The new printout: 

 
ubuntu@ip-172-31-24-219:~$ dpkg --info jenkins_oss_ubuntu.deb
 new debian package, version 2.0.
 size 206896358 bytes: control archive=2621 bytes.
  66 bytes, 3 lines  conffiles
1285 bytes,24 lines  control
 199 bytes, 3 lines  md5sums
3433 bytes,95 lines   *  postinst #!/bin/sh
 746 bytes,36 lines   *  postrm   #!/bin/sh
 204 bytes, 7 lines   *  prerm#!/bin/sh
 Package: jenkins
 Version: 2.7.19.1
 Architecture: all
 Maintainer: Kohsuke Kawaguchi 
 Installed-Size: 208108
 Depends: daemon, adduser, procps, psmisc, net-tools, default-jre-headless (>= 2:1.7) | java7-runtime-headless
 Conflicts: hudson
 Replaces: hudson
 Section: devel
 Priority: extra
 Homepage: http://jenkins.io/
 Description: Jenkins monitors executions of repeated jobs, such as building a software
  project or jobs run by cron. Among those things, current Jenkins focuses on the
  following two jobs:
  - Building/testing software projects continuously, just like CruiseControl or
DamageControl. In a nutshell, Jenkins provides an easy-to-use so-called
continuous integration system, making it easier for developers to integrate
changes to the project, and making it easier for users to obtain a fresh
build. The automated, continuous build increases the productivity.
  - Monitoring executions of externally-run jobs, such as cron jobs and procmail
jobs, even those that are run on a remote machine. For example, with cron,
all you receive is regular e-mails that capture the output, and it is up to
you to look at them diligently and notice when it broke. Jenkins keeps those
outputs and makes it easy for you to notice when something is wrong.

 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-38437) The description for the deb package is cut off

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-38437  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The description for the deb package is cut off   
 

  
 
 
 
 

 
 I decided to just end up using a custom file since the whole cost of trying to spin custom functions for different operating systems in the branding file didn't make sense. Still up for packaging 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-36499) Migrate openid to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone updated  JENKINS-36499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This was delivered and released in openid 2.2  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36499  
 
 
  Migrate openid to parent pom   
 

  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
Status: 
 In Review 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-38437) The description for the deb package is cut off

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone started work on  JENKINS-38437  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
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-38437) The description for the deb package is cut off

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-38437  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The description for the deb package is cut off   
 

  
 
 
 
 

 
 Found that the description isn't cut off, it's in fact just completely different from the descriptions in RHEL and in SUSE because it's hardcoded in the `control` file. Unlike rpm, there's no convenient automatic reading from a description file. So now the description reads from the appropriate file. Now if there's ever a change in description, all the packages will have the same information. The downside to this is the newlines aren't nicely spaced since make doesn't preserve new line characters, the method in which we're loading the branding doesn't preserve new lines anyway, and the version of make we're using doesn't support the file import command (available in make 4.1 and higher).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38437) The description for the deb package is cut off

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone updated  JENKINS-38437  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38437  
 
 
  The description for the deb package is cut off   
 

  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
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-38437) The description for the deb package is cut off

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38437  
 
 
  The description for the deb package is cut off   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Kristin Whetstone  
 
 
Components: 
 packaging  
 
 
Created: 
 2016/Sep/22 7:39 AM  
 
 
Environment: 
 Ubuntu  
 
 
Priority: 
  Trivial  
 
 
Reporter: 
 Kristin Whetstone  
 

  
 
 
 
 

 
 The description of the Ubuntu package is currently cut off in a really unusual manner. I would have expected this to be a truncation, but it looks like the first part of the package description has been removed. This is only for .deb packages as the rhel and suse packages are fine. I think it might be part of the dpkg scripts not properly picking up the results of the branding file. There could also be a malformed character 

 
ubuntu@ip-172-31-24-219:~$ dpkg --info jenkins_2.7.4_all.deb
 new debian package, version 2.0.
 size 68039982 bytes: control archive=2262 bytes.
  66 bytes, 3 lines  conffiles
 495 bytes,14 lines  control
 199 bytes, 3 lines  md5sums
3433 bytes,95 lines   *  postinst #!/bin/sh
 746 bytes,36 lines   *  postrm   #!/bin/sh
 204 bytes, 7 lines   *  prerm#!/bin/sh
 Package: jenkins
 Version: 2.7.4
 Architecture: all
 Maintainer: Kohsuke Kawaguchi 
 Installed-Size: 67334
 Depends: daemon, adduser, procps, psmisc, net-tools, default-jre-headless (>= 2:1.7) | java7-runtime-headless
 Conflicts: hudson
 Replaces: hudson
 Section: devel
 Priority: extra
 Homepage: http://jenkins.io/
 Description: continuous integration system
  Jenkins is an application that monitors 

[JIRA] (JENKINS-36499) Migrate openid to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-36499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Migrate openid to parent pom   
 

  
 
 
 
 

 
 All tests are passing. I'd appreciate some reviews and eventually a merge from the plugin maintainer. There are still changes that the openid plugin maintainer will want to review. PR10  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-36499) Migrate openid to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone updated  JENKINS-36499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36499  
 
 
  Migrate openid to parent pom   
 

  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
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-38206) Windows Installers show a garbage program name in the UAT Window

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-38206  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows Installers show a garbage program name in the UAT Window   
 

  
 
 
 
 

 
 I added a PR for giving a description. I just added the `/d` description option and reused the name of the installer file. This makes the name "jenkins" If there's something more descriptive, input is welcome.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38206) Windows Installers show a garbage program name in the UAT Window

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone started work on  JENKINS-38206  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
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-38206) Windows Installers show a garbage program name in the UAT Window

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38206  
 
 
  Windows Installers show a garbage program name in the UAT Window   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Kristin Whetstone  
 
 
Components: 
 core  
 
 
Created: 
 2016/Sep/14 4:15 PM  
 
 
Environment: 
 Windows  Any Jenkins installation  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kristin Whetstone  
 

  
 
 
 
 

 
 When running the .msi installer on Windows, a random string of characters shows up when the user is prompted to "let this program make changes to this computer". For a better user experience, this should be something a bit more obvious.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-36630) Migrate matrix-project to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone assigned an issue to Antonio Muñiz  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36630  
 
 
  Migrate matrix-project to parent pom   
 

  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
Assignee: 
 Jesse Glick Antonio Muñiz  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-36499) Migrate openid to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-36499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Migrate openid to parent pom   
 

  
 
 
 
 

 
 To get around this when using the new test harness, the version must minimally be 1.586 since the change wasn't backported to the 1.580 line.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-36499) Migrate openid to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-36499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Migrate openid to parent pom   
 

  
 
 
 
 

 
 I had to bump the version beyond the 1.580 bump in PR11 to handle JENKINS-25019. The left over failures would be related to this. Unfortunately, the problems left over from this pom bump are not related to the issues that I found earlier. I have actually fixed those issues. The new issue is actually related to serving up the openid xrds.jelly; either it can't be found or the proxy service is in error (fakeproxy.jenkins-ci.org: Name or service not known). This might be related to the move from jenkins-ci.org which I think the maintainer of the plugin should deal with. The "not found 404" errors I'm seeing I think relate to the actual location of the xrds.jelly file. JenkinsRule changed a bunch of things around with accessing files, and this is one of the things that was affected by that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-35348) Pipeline job loses connection with agent node

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-35348  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline job loses connection with agent node   
 

  
 
 
 
 

 
 Found a workaround for this, and I'm pretty sure the whole situation for this error is specific to my use case. I'm fine with closing 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-36630) Migrate matrix-project to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-36630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Migrate matrix-project to parent pom   
 

  
 
 
 
 

 
 This PR has been in development/hiatus/redevelopment for a while. I'm stuck on a few tests with a variation on the failure of matrix creation within a matrix job: Jul 11, 2016 9:24:04 PM com.gargoylesoftware.htmlunit._javascript_.background._javascript_JobManagerImpl runSingleJob SEVERE: Job run failed with unexpected RuntimeException: TypeError: Cannot find function on in object [object HTMLSpanElement]. (http://localhost:46836/jenkins/static/b7504d27/scripts/hudson-behavior.js#2806) === EXCEPTION START  Exception class=[net.sourceforge.htmlunit.corejs._javascript_._javascript_Exception] com.gargoylesoftware.htmlunit.ScriptException: TypeError: Cannot find function on in object [object HTMLSpanElement]. (http://localhost:46836/jenkins/static/b7504d27/scripts/hudson-behavior.js#2806) at com.gargoylesoftware.htmlunit._javascript_._javascript_Engine$HtmlUnitContextAction.run(_javascript_Engine.java:865) at net.sourceforge.htmlunit.corejs._javascript_.Context.call(Context.java:628) at net.sourceforge.htmlunit.corejs._javascript_.ContextFactory.call(ContextFactory.java:513) at com.gargoylesoftware.htmlunit._javascript_._javascript_Engine.callFunction(_javascript_Engine.java:796) at com.gargoylesoftware.htmlunit._javascript_.host.xml.XMLHttpRequest.setState(XMLHttpRequest.java:224) at com.gargoylesoftware.htmlunit._javascript_.host.xml.XMLHttpRequest.doSend(XMLHttpRequest.java:775) at com.gargoylesoftware.htmlunit._javascript_.host.xml.XMLHttpRequest.access$000(XMLHttpRequest.java:105) at com.gargoylesoftware.htmlunit._javascript_.host.xml.XMLHttpRequest$1.run(XMLHttpRequest.java:630) at net.sourceforge.htmlunit.corejs._javascript_.Context.call(Context.java:628) at net.sourceforge.htmlunit.corejs._javascript_.ContextFactory.call(ContextFactory.java:513) at com.gargoylesoftware.htmlunit._javascript_.background._javascript_XMLHttpRequestJob.run(_javascript_XMLHttpRequestJob.java:37) at com.gargoylesoftware.htmlunit._javascript_.background._javascript_JobManagerImpl.runSingleJob(_javascript_JobManagerImpl.java:428) at com.gargoylesoftware.htmlunit._javascript_.background.DefaultJavaScriptExecutor.run(DefaultJavaScriptExecutor.java:168) at java.lang.Thread.run(Thread.java:745) Caused by: net.sourceforge.htmlunit.corejs._javascript_._javascript_Exception: TypeError: Cannot find function on in object [object HTMLSpanElement]. (http://localhost:46836/jenkins/static/b7504d27/scripts/hudson-behavior.js#2806) at net.sourceforge.htmlunit.corejs._javascript_.Interpreter.interpretLoop(Interpreter.java:1006) at net.sourceforge.htmlunit.corejs._javascript_.Interpreter.interpret(Interpreter.java:798) at net.sourceforge.htmlunit.corejs._javascript_.InterpretedFunction.call(InterpretedFunction.java:105) at net.sourceforge.htmlunit.corejs._javascript_.ContextFactory.doTopCall(ContextFactory.java:411) at com.gargoylesoftware.htmlunit._javascript_.HtmlUnitContextFactory.doTopCall(HtmlUnitContextFactory.java:310) at net.sourceforge.htmlunit.corejs._javascript_.ScriptRuntime.doTopCall(ScriptRuntime.java:3286) at com.gargoylesoftware.htmlunit._javascript_._javascript_Engine$4.doRun(_javascript_Engine.java:789) at com.gargoylesoftware.htmlunit._javascript_._javascript_Engine$HtmlUnitContextAction.run(_javascript_Engine.java:850) ... 13 more _javascript_Exception value = TypeError: Cannot find function on in object [object HTMLSpanElement]. == CALLING _javascript_ == function () { var a = merge(args, arguments); return __method.apply(context, a); } === EXCEPTION END  While this error makes sense, I'm not sure how to solve 

[JIRA] (JENKINS-36630) Migrate matrix-project to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone started work on  JENKINS-36630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
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-36630) Migrate matrix-project to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36630  
 
 
  Migrate matrix-project to parent pom   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 matrix-auth-plugin  
 
 
Created: 
 2016/Jul/12 4:31 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kristin Whetstone  
 

  
 
 
 
 

 
 For improved test-ability and upgrades, upgrade the parent pom to the 2.x line. The jenkins.version might also be a candidate for upgrades since it's on a line that's old.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

[JIRA] (JENKINS-36499) Migrate openid to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone started work on  JENKINS-36499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
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-36499) Migrate openid to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-36499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Migrate openid to parent pom   
 

  
 
 
 
 

 
 Nope, the problem with the failing test appears when trying to test with the jenkins.ci server from the master branch of the current test suite. The only option in trying to convert all these tests is to:a a) ignore all the tests and mark them as something that has to be fixed in the future b) accept the changeset with failing tests knowing that the solution has to be found in the future Of the 2 options, the 2nd seems more favorable to me, simply from the perspective that the changes go into the codebase. The major issue I've seen in the test case conversion is the openid4java throwing errors when the crumbIssuer can't be set after the service has been started. This shows up in old and new tests, and there's really no good way to set up that particular setting. (The jetty server errors on stop/restart and any other overrides aren't a good 1-1 replacement)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-36499) Migrate openid to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-36499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Migrate openid to parent pom   
 

  
 
 
 
 

 
 I've had to disable almost every test while attempting to convert this to use the parent pom. I'm perfectly fine with a simpler changeset that uses an older parent pom if it meant that the tests would also pass. I'm not entirely sure if this is a setup issue on my system, as I have witnessed at least part of the openid service working when configuring it manually in the 1.651.1 version of Jenkins. Some of the exceptions I've seen are a result of the jetty server messing with the trace of openid4java: no crumbIssuer should be configured for these tests while the crumbIssuer can't be set/modified after the server starts. (Somehow, both HudsonTestCase and JenkinsRule both start the server then attempt to change the crumbIssuer while I've only seen explicit errors around the situation while using JenkinsRule). This might just be an issue on my local setup.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-36499) Migrate openid to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-36499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Migrate openid to parent pom   
 

  
 
 
 
 

 
 Ran into this when attempting to run `OpenIdLoginServiceTest`s  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-36499) Migrate openid to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-36499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Migrate openid to parent pom   
 

  
 
 
 
 

 
 Also, the tests won't pass on their own regardless of the changes I've made with htmlunit. I think this plugin might need some expert eyes to try to fix some of the functionality on the newest versions.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-36499) Migrate openid to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone commented on  JENKINS-36499  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Migrate openid to parent pom   
 

  
 
 
 
 

 
 While investigating this conversion, I ran into a lot of issues with how the tests ran. Noteably, there are some tests that I don't think will ever pass. I think these test failures will have to be addressed by the maintainers of the plugin. Also, I think there are some legitimate issues with the plugin since I tried using it on the latest version of Jenkins and ran into 404 errors while trying to use the service.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-36499) Migrate openid to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36499  
 
 
  Migrate openid to parent pom   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Kristin Whetstone  
 
 
Components: 
 openid-plugin  
 
 
Created: 
 2016/Jul/07 2:43 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kristin Whetstone  
 

  
 
 
 
 

 
 For improved test-ability and upgrades, upgrade the parent pom to the 2.x line. The jenkins.version might also be a candidate for upgrades since it's on a line that's old.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

[JIRA] (JENKINS-36301) Migrate suppress-stack-trace-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone started work on  JENKINS-36301  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
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-36301) Migrate suppress-stack-trace-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36301  
 
 
  Migrate suppress-stack-trace-plugin to 2.x parent pom   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Kristin Whetstone  
 
 
Components: 
 suppress-stack-trace-plugin  
 
 
Created: 
 2016/Jun/29 7:32 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kristin Whetstone  
 

  
 
 
 
 

 
 Migrate the suppress-stack-trace-plugin to the parent pom for increased test-ability. Also, assess and fix any issues encountered with tests on the 2.x line.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by 

[JIRA] (JENKINS-35707) Migrate docker-build-publish-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Merged. Thanks everyone.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-35707  
 
 
  Migrate docker-build-publish-plugin to 2.x parent pom   
 

  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
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-35707) Migrate docker-build-publish-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone started work on  JENKINS-35707  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
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-35707) Migrate docker-build-publish-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35707  
 
 
  Migrate docker-build-publish-plugin to 2.x parent pom   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Kristin Whetstone  
 
 
Components: 
 docker-build-publish-plugin  
 
 
Created: 
 2016/Jun/14 6:51 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kristin Whetstone  
 

  
 
 
 
 

 
 Migrate the docker-build-publish-plugin to the parent pom for increased test-ability. Also, assess and fix any issues encountered with tests on the 2.x line.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by 

[JIRA] (JENKINS-35629) Migrate dockerhub-notification to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kristin Whetstone resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35629  
 
 
  Migrate dockerhub-notification to 2.x parent pom   
 

  
 
 
 
 

 
Change By: 
 Kristin Whetstone  
 
 
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] [external-monitor-job-plugin] (JENKINS-35284) Migrate external-monitor-job-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone started work on  JENKINS-35284 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [dockerhub-notification-plugin] (JENKINS-35629) Migrate dockerhub-notification to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone started work on  JENKINS-35629 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [dockerhub-notification-plugin] (JENKINS-35629) Migrate dockerhub-notification to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35629 
 
 
 
  Migrate dockerhub-notification to 2.x parent pom  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kristin Whetstone 
 
 
 

Components:
 

 dockerhub-notification-plugin 
 
 
 

Created:
 

 2016/Jun/10 6:02 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
Migrate the dockerhub-notification to the parent pom for increased test-ability. Also, assess and fix any issues encountered with tests on the 2.x line 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

  

[JIRA] [build-view-column-plugin] (JENKINS-35283) Migrate build-view-column to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35283 
 
 
 
  Migrate build-view-column to 2.x parent pom  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-view-column-plugin] (JENKINS-35283) Migrate build-view-column to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-35283 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Migrate build-view-column to 2.x parent pom  
 
 
 
 
 
 
 
 
 
 
Merged. Thanks all. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-server-plugin] (JENKINS-35510) Migrate git-server-plugin to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-35510 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Migrate git-server-plugin to parent pom  
 
 
 
 
 
 
 
 
 
 
This plugin relies on an older version of Jenkins, 1.480. I've been testing migrating to 1.580.1 to grab SECURITY-144, but there are some fundamental changes between versions. Because this plugin has been pretty much functionally untouched since 2014 (findbugs and maven dependency bumps) and it's popularity is rising meteorically, it might be worth keeping the jenkins.version at 1.480. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-server-plugin] (JENKINS-35510) Migrate git-server-plugin to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone started work on  JENKINS-35510 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-server-plugin] (JENKINS-35510) Migrate git-server-plugin to parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35510 
 
 
 
  Migrate git-server-plugin to parent pom  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kristin Whetstone 
 
 
 

Components:
 

 git-server-plugin 
 
 
 

Created:
 

 2016/Jun/09 6:01 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
For improved test-ability and upgrades, upgrade the parent pom to the 2.x line. The jenkins.version might also be a candidate for upgrades since it's on a line that's old. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

   

[JIRA] [acceptance-test-harness] (JENKINS-35090) ManagedCredentials PageObject not compatible with 2.x release of credentials-plugin

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-35090 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ManagedCredentials PageObject not compatible with 2.x release of credentials-plugin  
 
 
 
 
 
 
 
 
 
 
Made first commit to fix the problem. Fixed the CredentialsTest since it covers all the cases the other methods would need. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [pam-auth-plugin] (JENKINS-35285) Migrate pam-auth-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone closed an issue as Done 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35285 
 
 
 
  Migrate pam-auth-plugin to 2.x parent pom  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Status:
 
 In Progress Closed 
 
 
 

Resolution:
 
 Done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [workflow-plugin] (JENKINS-35348) Pipeline job loses connection with agent node

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-35348 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline job loses connection with agent node  
 
 
 
 
 
 
 
 
 
 
This is the last piece to getting the documentation automated! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [workflow-plugin] (JENKINS-35348) Pipeline job loses connection with agent node

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35348 
 
 
 
  Pipeline job loses connection with agent node  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Summary:
 
 Pipeline job loses connection with  slave  agent  node 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [workflow-plugin] (JENKINS-35348) Pipeline job loses connection with slave node

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35348 
 
 
 
  Pipeline job loses connection with slave node  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/Jun/03 7:52 PM 
 
 
 

Environment:
 

 Any version of Jenkins  pipeline 2 and higher 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
When running a job with a shell step on a remote node, there's a case where the master will lose connectivity with the remote node. All logging statements in trying to determine the functionality are dumped in the job log. After several hours, there is no reconnection for that pipeline, even if other jobs are run on that remote node successfully. The shell step was completed successfully. 
An example job with the error can be found in the links section 
This might be an issue with the pipeline and the durable-task plugin. 
 
 
 
 
 
 
 
 
 
 
 
 
 

[JIRA] [authentication-tokens-plugin] (JENKINS-35287) Migrate authentication-tokens-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone started work on  JENKINS-35287 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [authentication-tokens-plugin] (JENKINS-35287) Migrate authentication-tokens-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35287 
 
 
 
  Migrate authentication-tokens-plugin to 2.x parent pom  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kristin Whetstone 
 
 
 

Components:
 

 authentication-tokens-plugin 
 
 
 

Created:
 

 2016/Jun/02 5:41 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
Convert the parent pom to the 2.x line for increased test-ability. Also ensure the tests run successfully against the most recent 2.x build. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

[JIRA] [javadoc-plugin] (JENKINS-35286) Migrate javadoc-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone started work on  JENKINS-35286 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [javadoc-plugin] (JENKINS-35286) Migrate javadoc-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35286 
 
 
 
  Migrate javadoc-plugin to 2.x parent pom  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kristin Whetstone 
 
 
 

Components:
 

 javadoc-plugin 
 
 
 

Created:
 

 2016/Jun/02 5:29 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
Convert the parent pom to the 2.x line for increased test-ability. Also run the tests against the most recent 2.x build and fix any problems that rise there. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This 

[JIRA] [pam-auth-plugin] (JENKINS-35285) Migrate pam-auth-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone started work on  JENKINS-35285 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [pam-auth-plugin] (JENKINS-35285) Migrate pam-auth-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35285 
 
 
 
  Migrate pam-auth-plugin to 2.x parent pom  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kristin Whetstone 
 
 
 

Components:
 

 pam-auth-plugin 
 
 
 

Created:
 

 2016/Jun/02 5:24 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
Move the parent pom to the 2.x line to increase test-ability. Also run tests against the 2.0 line and confirm that those the plugin is compatible with the newest version of Jenkins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 

[JIRA] [external-monitor-job-plugin] (JENKINS-35284) Migrate external-monitor-job-plugin to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35284 
 
 
 
  Migrate external-monitor-job-plugin to 2.x parent pom  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kristin Whetstone 
 
 
 

Components:
 

 external-monitor-job-plugin 
 
 
 

Created:
 

 2016/Jun/02 5:14 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
Migrate the external-monitor-job to the parent pom for increased test-ability. Also, assess and fix any issues encountered with tests on the 2.x line. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

[JIRA] [build-view-column-plugin] (JENKINS-35283) Migrate build-view-column to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-35283 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Migrate build-view-column to 2.x parent pom  
 
 
 
 
 
 
 
 
 
 
I've added a pull request to build-view-column to update the parent pom. I updated the Jenkins version to a more recent LTS line. The 1.480.3 line is no longer found in the tagged releases in GitHub, so it'd be incredibly difficult to diagnose any core issues found with that version. Also, I kept the java version at 6 to match the requirement at 1.609.3. Any comments are welcome. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-view-column-plugin] (JENKINS-35283) Migrate build-view-column to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone started work on  JENKINS-35283 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-view-column-plugin] (JENKINS-35283) Migrate build-view-column to 2.x parent pom

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35283 
 
 
 
  Migrate build-view-column to 2.x parent pom  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kristin Whetstone 
 
 
 

Components:
 

 build-view-column-plugin 
 
 
 

Created:
 

 2016/Jun/02 4:55 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
For improved test-ability and upgrades, upgrade the parent pom to the 2.x line. The jenkins.version might also be a candidate for upgrades since it's on a line that's old. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

[JIRA] [acceptance-test-harness] (JENKINS-35134) Large numbers of ATH tests failing against 2.6

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-35134 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Large numbers of ATH tests failing against 2.6  
 
 
 
 
 
 
 
 
 
 
Oliver, I'm glad I'm not the only one seeing the CredentialsPluginTest run with only the 1.18 version of the plugin. Strangely, trying to set the version of the test using the 'env' flag doesn't appear to work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [acceptance-test-harness] (JENKINS-35090) ManagedCredentials PageObject not compatible with 2.x release of credentials-plugin

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-35090 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ManagedCredentials PageObject not compatible with 2.x release of credentials-plugin  
 
 
 
 
 
 
 
 
 
 
I'll take this as I've started working on getting the plugin working on PCT and ATH. This should get the credentials-plugin working on the 2.x line. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [acceptance-test-harness] (JENKINS-35090) ManagedCredentials PageObject not compatible with 2.x release of credentials-plugin

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone assigned an issue to Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35090 
 
 
 
  ManagedCredentials PageObject not compatible with 2.x release of credentials-plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Assignee:
 
 Armando Fernandez Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [acceptance-test-harness] (JENKINS-35090) ManagedCredentials PageObject not compatible with 2.x release of credentials-plugin

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone started work on  JENKINS-35090 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-25995) Cannot find function querySelectorAll while running HtmlUnit tests

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-25995 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot find function querySelectorAll while running HtmlUnit tests  
 
 
 
 
 
 
 
 
 
 
There have been a lot of changes around the test harness. Check out the jenkins-test-harness which has been updated and split from Jenkins core, and the plugin-pom which gives you granular control over your Jenkins dependencies. If you change the dependency of your plugin(s) to the plugin-pom, you can vary what version your tests will run from the command line, as well as in your pom. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-34281) Queue isn't saved on any shutdown

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-34281 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Queue isn't saved on any shutdown  
 
 
 
 
 
 
 
 
 
 
After some searching, found that the queue is persisted correctly on upgrades from 1.x, but not on a new install of 2.0. The only reason a job wouldn't be saved is if it was defined as a TransientTask. There might have been some change to jobs listing them all as TransientTasks or somehow everything is being listed as a TransientTask. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-34281) Queue isn't saved on any shutdown

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-34281 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Queue isn't saved on any shutdown  
 
 
 
 
 
 
 
 
 
 
Also further note on this: if the queue is full of freestyle jobs, then they will not be persisted or restarted at all. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-34281) Queue isn't saved on any shutdown

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34281 
 
 
 
  Queue isn't saved on any shutdown  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Apr/15 3:02 PM 
 
 
 

Environment:
 

 Jenkins 2.0-rc  Java 8  Windows 10 x64, MacOS X 
 
 
 

Labels:
 

 2.0 2.0-rc testfest regression 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
When Jenkins is stopped, the queue file is created except it's empty. No information about the running jobs or jobs pending in the queue exist. 
It essentially saves a file like:   42   
This behavior is a regression from Jenkins 2.0 beta2. 
 
 
 
 
 
 
 
 
 
 
   

[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-33926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 
 
Cool, so that's actually a regression from beta2 where that information was saved. I think that's a completely separate defect since this jetty issue happened before then. Good find during TestFest! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-30909) queue.xml only gets persisted on successful shutdown

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-30909 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: queue.xml only gets persisted on successful shutdown  
 
 
 
 
 
 
 
 
 
 
As part of an aside, I've been running tests on Jenkins 1.x and the 2 betas/rcs and am running into some interesting issues with saving the queue on Windows. If Jenkins is running as a process and it is stopped, it won't save a queue.xml. From looking at this pull request, this looks like it should have fixed the problem; are these cases related? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-33926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 
 
To me, the file showing up in the first place and that it's successfully read on startup means the file was created correctly (there's no missing information when being written and it's not formatted incorrectly) it might just be incomplete. Obviously I'm making some assumptions on the queue behavior, and spent some time trying to go through where the queue was written so figure out how it came into being. Apparently there are 2 types of shutdown: one that writes the queue and one that's "quick" not counting the error case, the secret not-so-fun shutdown. From what I understand the error case just completely tanks jetty, et al. If it's able to save state enough to pick back up on a restart, I think that's slightly better than not having anything at all. 
I'd check out if the queue being incomplete issue exists on the latest 1.x release. That will at least give some context into whether it's something new or not. Either way it's not good, but at least it's not worse! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-33926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 
 
Sam, it sounds like your defect is something different than what the original problem covered by this work item. While the queue is saved, it's not saving everything. That might be a bug in the queue.save(). In the Windows version it's not getting saved at all during Ctrl-C. We should open a ticket for that problem so it could be fixed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-33926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 
 
James, I'm sending it over to you since I couldn't reproduce it on beta while Ctrl-C or while stopping the service. I'm going to see if I can reproduce it on the RC, but I must not be going through the correct steps or something. 
Note: the part about losing the job queue when restarted as a Windows service looks like an older problem. I definitely think that this should be a bug if it's not already. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone assigned an issue to James Nord 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33926 
 
 
 
  Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Assignee:
 
 Kristin Whetstone James Nord 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-33926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 
 
So I ran through a number of scenarios on Windows and Linux on 2.0 and 1.X and it appears that for Windows we never actually save the queue when we stop the service. Linux is fine; I started and stopped the service while every executor is used, and everything is saved and restarted. I think this might be a difference in the command signals sent to the service when stopping in Windows vs Linux, but that's just a theory at this point. 
As to other shutdown actions taken when the system is shutting down, since I'm not able to replicate the initial condition, all of my exit conditions (TermMilestones, etc) are hit. Other than this queue conditional, I don't see anything odd with the service.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone edited a comment on  JENKINS-33926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 
 After installing Jenkins 2.0 as a Windows service and running a heavy mock load, I'm still seeing the  `  {{ queue.xml ` }}  file appear.  Since the service is able to start up earlier than I can access my file system, I know this file is created because of  `  {{ queue.xml.bak ` }}  which isn't removed & contains the same information.The logs left in  `  {{ jenkins.out.log ` }}  and  `  {{ jenkins.err.log ` }}  don't have any messages for shutting down, but I have a feeling they're overwritten on service restart, so they're likely not useful.  Checking the log on the Jenkins instance also only covers the current run.I linked to JENKINS-30909 to highlight the behavior I'm seeing as part of restarting/destroying-recreating the service.  Nothing really appears to be out of the ordinary.From what I can tell during these tests, I don't think this is a blocker issue for 2.0 release. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone edited a comment on  JENKINS-33926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 
 I think this  (JENKINS-30909)  is similar  since it's referring to a missing queue log.In testing where I physically go through the whole computer shutdown process ,  though  it appears that things run properly.  (  I  find a properly timestamped queue.xml.bak file)  When I just stop the process from the command line, I don ' m not running into t see any queue.xml file.  I assume  this  problem during  case falls under  this  testing phase  defect . So far, the behavior I've seen echos this work item.  I'll have to look to a different mechanism (James Nord brought up TermMilestone) to see if there's another issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-33926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 
 
After installing Jenkins 2.0 as a Windows service and running a heavy mock load, I'm still seeing the `queue.xml` file appear. Since the service is able to start up earlier than I can access my file system, I know this file is created because of `queue.xml.bak` which isn't removed & contains the same information. 
The logs left in `jenkins.out.log` and `jenkins.err.log` don't have any messages for shutting down, but I have a feeling they're overwritten on service restart, so they're likely not useful. Checking the log on the Jenkins instance also only covers the current run. 
I linked to JENKINS-30909 to highlight the behavior I'm seeing as part of restarting/destroying-recreating the service. Nothing really appears to be out of the ordinary. 
From what I can tell during these tests, I don't think this is a blocker issue for 2.0 release. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-33926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 
 
I think this is similar, though I'm not running into this problem during this testing phase. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-33926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins no longer appears to shutdown correctly  
 
 
 
 
 
 
 
 
 
 
While investigating, I didn't see any error show up consistently before missing the log statement. I didn't see this occur as often on 2.0 before clicking the "Install New Features". Luckily it doesn't seem to be disruptive to my Jenkins, so that's a plus. Trying to see if there's a problem after "Installing new features" or running it under heavy stress. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33941) When using a custom build directory, the moving a job folder does not initially carry over previous builds

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-33941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: When using a custom build directory, the moving a job folder does not initially carry over previous builds  
 
 
 
 
 
 
 
 
 
 
I've been looking at this and found some other odd behavior depending on the different combinations of home directories. Investigating and fixing. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33941) When using a custom build directory, the moving a job folder does not initially carry over previous builds

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone started work on  JENKINS-33941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-33941) When using a custom build directory, the moving a job folder does not initially carry over previous builds

[kwhetst...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone assigned an issue to Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33941 
 
 
 
  When using a custom build directory, the moving a job folder does not initially carry over previous builds  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kristin Whetstone 
 
 
 

Assignee:
 
 Kristin Whetstone 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.