[JIRA] (JENKINS-52421) Support PowerShell Core on Nano Server

2019-01-18 Thread esrahofst...@outlook.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 esra hofstede updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52421  
 
 
  Support PowerShell Core on Nano Server   
 

  
 
 
 
 

 
Change By: 
 esra hofstede  
 
 
Component/s: 
 powershell-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55689) Not able to connect to jenkins master from windows slave

2019-01-18 Thread mohit.sa...@ampf.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mohit Saraf commented on  JENKINS-55689  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to connect to jenkins master from windows slave   
 

  
 
 
 
 

 
 Hi Team, Any suggestions?  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55691) Cannot edit build information in Blue Ocean UI

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55691  
 
 
  Cannot edit build information in Blue Ocean UI   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2019-01-19 06:05  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Craig Rodrigues  
 

  
 
 
 
 

 
 In the classic UI, if I click on Edit Build Information, then I switch to Blue Ocean, it is possible to see this information in the Blue Ocean UI.   However, in Blue Ocean, there seems to be no way to edit the build information.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-54524) Improper Encoding of Sync Status

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54524  
 
 
  Improper Encoding of Sync Status   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Status: 
 Open Closed  
 
 
Assignee: 
 Craig Rodrigues  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39598) MultiSCM/config.jelly passes descriptors=null

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39598  
 
 
  MultiSCM/config.jelly passes descriptors=null   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Status: 
 Reopened Closed  
 
 
Assignee: 
 Craig Rodrigues  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55309) SCM Sync error messages when Multibranch pipeline branch gets removed

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55309  
 
 
  SCM Sync error messages when Multibranch pipeline branch gets removed   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Status: 
 Open Closed  
 
 
Assignee: 
 Craig Rodrigues  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53846) scm sync configuration plugin

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53846  
 
 
  scm sync configuration plugin   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Status: 
 Open Closed  
 
 
Assignee: 
 Craig Rodrigues  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-31335) phabricator-plugin unconditionally does git clean -fd -f

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31335  
 
 
  phabricator-plugin unconditionally does git clean -fd -f   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55690) PR Builds discovered, but not triggered

2019-01-18 Thread kmi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kong Minh Cap created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55690  
 
 
  PR Builds discovered, but not triggered   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 gitea-plugin  
 
 
Created: 
 2019-01-19 05:55  
 
 
Environment: 
 gitea 1.6  Jenkins 2.160  gitea Plugin 1.10.0  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kong Minh Cap  
 

  
 
 
 
 

 
 Pull Requests are discovered properly, but the builds are not triggered automatically via webhook even though the Webhook is received successfully. Manual triggering of the job does work.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

[JIRA] (JENKINS-55628) In Jenkins, Do we have any functionality similar to 'Finish build trigger of TeamCity

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55628  
 
 
  In Jenkins, Do we have any functionality similar to 'Finish build trigger of TeamCity
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Status: 
 Open Closed  
 
 
Assignee: 
 Craig Rodrigues  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-31335) phabricator-plugin unconditionally does git clean -fd -f

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 With the availability of Jenkins Pipeline, it is possible to write a Pipeline script to invoke Phabricator the way that I need, rather than depend on this plugin.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-31335  
 
 
  phabricator-plugin unconditionally does git clean -fd -f   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-31336) phabricator-plugin cannot do "arc patch" if source code is checked out to subdirectory

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31336  
 
 
  phabricator-plugin cannot do "arc patch" if source code is checked out to subdirectory   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-31336) phabricator-plugin cannot do "arc patch" if source code is checked out to subdirectory

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues updated  JENKINS-31336  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I think now with Jenkins Pipeline, it is easier to write a Pipeline script to invoke phabricator in the way that I want, rather than using this specific plugin.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-31336  
 
 
  phabricator-plugin cannot do "arc patch" if source code is checked out to subdirectory   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-31336) phabricator-plugin cannot do "arc patch" if source code is checked out to subdirectory

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues updated  JENKINS-31336  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31336  
 
 
  phabricator-plugin cannot do "arc patch" if source code is checked out to subdirectory   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Status: 
 Fixed but Unreleased Resolved  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49828) Commit viewer in Blue Ocean

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues commented on  JENKINS-49828  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Commit viewer in Blue Ocean   
 

  
 
 
 
 

 
 If I look here: https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins-test-harness-htmlunit/detail/master/4/changes   at least for git, I see the change is hyperlinked to the git repository, and the author and date of the commit are listed.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52825) Blue Ocean - Need to see executors

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues commented on  JENKINS-52825  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean - Need to see executors   
 

  
 
 
 
 

 
 I would recommend adding the blueocean-executor-info-plugin to the maven dependencies of Blue Ocean so it gets installed by default.  The UI for the blueocean-executor-info-plugin is not perfect, but it is a good start.  Being able to view executors is important, and it is annoying to have to switch to the classic UI every time I want to look at executors.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52825) Cannot see executors in Blue Ocean UI

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52825  
 
 
  Cannot see executors in Blue Ocean UI   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Summary: 
 Blue Ocean - Need to Cannot  see executors  in Blue Ocean UI  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53019) Changes tab does not group changes for multiple SCM providers by SCM

2019-01-18 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53019  
 
 
  Changes tab does not group changes for multiple SCM providers by SCM   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Summary: 
 Changes tab does not group  SCM  changes for multiple SCM providers  by SCM  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55461) Refactor code to conform to log4j style guide

2019-01-18 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55461  
 
 
  Refactor code to conform to log4j style guide   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Assignee: 
 David Olorundare  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55461) Refactor code to conform to log4j style guide

2019-01-18 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare stopped work on  JENKINS-55461  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-46830) Add a way to generate "deprecated" text on step and global variable documentation

2019-01-18 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46830  
 
 
  Add a way to generate "deprecated" text on step and global variable documentation   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 gsoc-2019-project-idea  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-37596) Global Variable Reference should cite the plugin which provides the variable

2019-01-18 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37596  
 
 
  Global Variable Reference should cite the plugin which provides the variable   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 gsoc-2019-project-idea  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54438) Documentation is not generating for wait parameter in build job

2019-01-18 Thread martin.danjo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54438  
 
 
  Documentation is not generating for wait parameter in build job   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 documentation  gsoc-2019-project-idea  triaged-2018-11  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41667) Generated pipeline steps documentation is too large

2019-01-18 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41667  
 
 
  Generated pipeline steps documentation is too large   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 gsoc-2019-project-idea  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54418) Ability to select images based on OS_FAMILY and select lastest version

2019-01-18 Thread ing...@ingwar.eu.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Lassak edited a comment on  JENKINS-54418  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to select images based on OS_FAMILY and select lastest version   
 

  
 
 
 
 

 
 We are using terraform + API directly to create templates (terraform  nor  and  gcloud  dont  have  some  such  options)..And seems like UI have only option to set image..But via templates its possible to set every parameter of created machine (At least I did not found any parameter when its not possible)  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54418) Ability to select images based on OS_FAMILY and select lastest version

2019-01-18 Thread ing...@ingwar.eu.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Lassak commented on  JENKINS-54418  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to select images based on OS_FAMILY and select lastest version   
 

  
 
 
 
 

 
 We are using terraform + API directly to create templates.. And seems like UI have only option to set image.. But via templates its possible to set every parameter of created machine (At least I did not found any parameter when its not possible)  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54418) Ability to select images based on OS_FAMILY and select lastest version

2019-01-18 Thread ing...@ingwar.eu.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karol Lassak edited a comment on  JENKINS-54418  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to select images based on OS_FAMILY and select lastest version   
 

  
 
 
 
 

 
 We are using terraform + API directly to create templates  (terraform nor gcloud have some options) ..And seems like UI have only option to set image..But via templates its possible to set every parameter of created machine (At least I did not found any parameter when its not possible)  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55668) Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)

2019-01-18 Thread mar...@jitbase.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Courtois updated  JENKINS-55668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55668  
 
 
  Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)   
 

  
 
 
 
 

 
Change By: 
 Martin Courtois  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55689) Not able to connect to jenkins master from windows slave

2019-01-18 Thread mohit.sa...@ampf.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mohit Saraf updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55689  
 
 
  Not able to connect to jenkins master from windows slave   
 

  
 
 
 
 

 
Change By: 
 Mohit Saraf  
 
 
Attachment: 
 jenkins-error.PNG  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55668) Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)

2019-01-18 Thread mar...@jitbase.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Courtois commented on  JENKINS-55668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)   
 

  
 
 
 
 

 
 Thanks Wadeck Follonier your fix seems work  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55689) Not able to connect to jenkins master from windows slave

2019-01-18 Thread mohit.sa...@ampf.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mohit Saraf created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55689  
 
 
  Not able to connect to jenkins master from windows slave   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Emilio Escobar   
 
 
Components: 
 windows-slaves-plugin  
 
 
Created: 
 2019-01-18 21:50  
 
 
Environment: 
 Jenkins Version: 2.150.1  Master is running in Docker Container in DC/OS (Mesos) environment.  web browser: chrome   
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Mohit Saraf  
 

  
 
 
 
 

 
 Hi Team, we are running jenkins master as docker container in DC/OS environment.  we have two ports available for setting up the configuration.  container port 8080 is mapped to service port 29XXXfor jenkins. container port 5 is mapped to service port  29XXX for jenkins-agent. I have configured the jenkins-agent port in manage Jenkins->Global Security->TCP port for JNLP agents. and also tried to give the default port and multiple random ports but while running the agent i get the error as port is not reachable. SEVERE: https://develop.qa.ampf.com/jenkins/ provided port:41172 is not reachable java.io.IOException: https://develop.qa.ampf.com/jenkins/ provided port:41172 is not reachable at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:286) at hudson.remoting.Engine.innerRun(Engine.java:523) at hudson.remoting.Engine.run(Engine.java:474) Suppressed: java.io.IOException: http://develop.qa.ampf.com/jenkins/tcpSlaveAgentListener/ is invalid: 302 Found at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:201) ... 2 more   Any suggestions would be really helpful        
 

  
 
 
   

[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace

2019-01-18 Thread rynlo...@lutron.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ryan Lopez commented on  JENKINS-55597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins JNLP agent disconnects when it fails to delete an old build workspace   
 

  
 
 
 
 

 
 We are running into the same problem described above. Jenkins tries to delete files which are created by a Docker script as owned by root with no regular user write permissions. Jenkins tries to clean up the obsolete workspaces and immediately disconnects and reconnects. If anyone knows of a workaround or fix, we are very interested. 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55527) Builds fail randomly when running sh in container

2019-01-18 Thread apow...@llbean.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andy Powell commented on  JENKINS-55527  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Builds fail randomly when running sh in container   
 

  
 
 
 
 

 
 Update: We were able to isolate this to a security scanner within our GKE cluster.  Turning it off made the problems go away.    
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55075) Pipeline: If job fails it will run again on next poll.

2019-01-18 Thread nancy.bel...@genesys.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nancy Belser commented on  JENKINS-55075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline: If job fails it will run again on next poll.   
 

  
 
 
 
 

 
 We are experiencing this problem as well. We cannot execute builds so it is a critical problem.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55305) Add user creation listener-methods to SecurityListener

2019-01-18 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare updated  JENKINS-55305  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55305  
 
 
  Add user creation listener-methods to SecurityListener   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55307) Update HudsonPrivateSecurityRealm use of SecurityListener

2019-01-18 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare updated  JENKINS-55307  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55307  
 
 
  Update HudsonPrivateSecurityRealm use of SecurityListener   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-45942) Bad error message/silent death with incorrectly setup permissions in the RoleBasedAuthorizationStrategy

2019-01-18 Thread deepanshnaga...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Deepansh Nagaria assigned an issue to Deepansh Nagaria  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45942  
 
 
  Bad error message/silent death with incorrectly setup permissions in the RoleBasedAuthorizationStrategy   
 

  
 
 
 
 

 
Change By: 
 Deepansh Nagaria  
 
 
Assignee: 
 Deepansh Nagaria  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55668) Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)

2019-01-18 Thread r...@ranker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rafi Greenberg commented on  JENKINS-55668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)   
 

  
 
 
 
 

 
 +1    Jenkins is broken after upgrade due to this  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-47701) Git Poll Detects Spurious Changes

2019-01-18 Thread nittanymount...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David D commented on  JENKINS-47701  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Poll Detects Spurious Changes   
 

  
 
 
 
 

 
 this happens random on one of my tasks with polling. sometimes it just keeps saying found changes and kicks off a build. (my task set to 15min polling interval) 
 
yesterday afternoon, removed the scm-polling.log file under the task, then it fixed the problem 
 
 
this morning, there is a commit, triggered a build, but then it started keep building, even no change in repo... 
 hope this can be fixed, or someone could explain how jenkins determines a change? does it compare the sha1 in scm-polling.log and the one from polling?  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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents

2019-01-18 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-55257  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55257  
 
 
  Timestamper break builds on Windows agents   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 toward 2.161  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents

2019-01-18 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55257  
 
 
  Timestamper break builds on Windows agents   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 lts-candidate remoting  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents

2019-01-18 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-55257  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55257  
 
 
  Timestamper break builds on Windows agents   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Review  Progress  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents

2019-01-18 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick stopped work on  JENKINS-55257  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55688) Anchore Whitelisted Images not shown in report

2019-01-18 Thread plapo...@nuglif.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pascal Laporte created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55688  
 
 
  Anchore Whitelisted Images not shown in report   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Daniel Nurmi  
 
 
Components: 
 anchore-container-scanner-plugin  
 
 
Created: 
 2019-01-18 18:09  
 
 
Environment: 
 anchore-container-scanner-plugin: 1.0.18  jenkins-core: 2.147  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Pascal Laporte  
 

  
 
 
 
 

 
 The Jenkins plugins is super awesome! But… in the case of whitelisted_images, I feel sad that it doesn’t show within the report that it pass because it was whitelisted. For example:  1- Seending multiples images to scan/evaluate. 2- Jenkins mark the job has failed, because some images aren’t compilant with the policies (Great!) 3- Looking at the report we see that every image are having problem. So people, aren’t able to see which images should be fix and which are just to be ignored (because they were whitelisted).   So people are trying to fix trouble that they shouldn't care about.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
  

[JIRA] (JENKINS-55676) Promotion appears to be linking to the wrong build

2019-01-18 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-55676  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Promotion appears to be linking to the wrong build   
 

  
 
 
 
 

 
 Thanks for the report. I'm not aware of any recent changes to the plugin that might affect this (really I am not aware of any recent changes at all), so maybe you've just hit a long-standing bug. Has anything changed in the Job configuration or in your Jenkins instance recently (upgrades, new plugins, etc.)? If you have steps to reproduce the issue from scratch that would be interesting. I do not have any time to work on this plugin, but if you submit a pull request to to the repository I would be more than happy to review it.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55676) Promotion appears to be linking to the wrong build

2019-01-18 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55676  
 
 
  Promotion appears to be linking to the wrong build   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Assignee: 
 Devin Nusbaum  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53140) Intermittent Random Stage Failures - No Changes Detected - Parallel Stages

2019-01-18 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53140  
 
 
  Intermittent Random Stage Failures - No Changes Detected - Parallel Stages   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 subversion-plugin  
 
 
Component/s: 
 pipeline  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53140) Intermittent Random Stage Failures - No Changes Detected - Parallel Stages

2019-01-18 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-53140  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Intermittent Random Stage Failures - No Changes Detected - Parallel Stages   
 

  
 
 
 
 

 
 Not sure if this is a complete duplicate of JENKINS-34313, but it's definitely similar.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55621) how can logstash plugin send multiple line once time to es with block usage?

2019-01-18 Thread m_win...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Markus Winter commented on  JENKINS-55621  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: how can logstash plugin send multiple line once time to es with block usage?   
 

  
 
 
 
 

 
 You can use the with maxLines set to negative value. logstashSend failBuild: }}{{true, maxLines: -1 This will send the complete log and not just the last lines.{{}}  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55621) how can logstash plugin send multiple line once time to es with block usage?

2019-01-18 Thread m_win...@gmx.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Markus Winter edited a comment on  JENKINS-55621  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: how can logstash plugin send multiple line once time to es with block usage?   
 

  
 
 
 
 

 
 You can use the  logstashSend step  with maxLines set to negative value.{{logstashSend failBuild:  }}{{ true}}{{, maxLines: -1}}This will send the complete log and not just the last lines. {{}}  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55668) Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)

2019-01-18 Thread ryan.desm...@radiantsolutions.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ryan Desmond commented on  JENKINS-55668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)   
 

  
 
 
 
 

 
 Ditto with 0.7 of the plugin  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55609) Submitted JCL no longer supports variable substitution

2019-01-18 Thread candidusl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Shcherbakov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55609  
 
 
  Submitted JCL no longer supports variable substitution   
 

  
 
 
 
 

 
Change By: 
 Alexander Shcherbakov  
 
 
Attachment: 
 zos-connector.hpi  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55609) Submitted JCL no longer supports variable substitution

2019-01-18 Thread candidusl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Shcherbakov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55609  
 
 
  Submitted JCL no longer supports variable substitution   
 

  
 
 
 
 

 
Change By: 
 Alexander Shcherbakov  
 
 
Attachment: 
 zos-connector.hpi  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-37632) Bitbucket Pull Request plugin has no socket timeout and hangs indefinitely

2019-01-18 Thread jer...@sevenrooms.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeremy P commented on  JENKINS-37632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket Pull Request plugin has no socket timeout and hangs indefinitely   
 

  
 
 
 
 

 
 You can access `/threadDump` on a running Jenkins server to obtain the thread dumps.  See https://wiki.jenkins.io/display/JENKINS/Obtaining+a+thread+dump  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55609) Submitted JCL no longer supports variable substitution

2019-01-18 Thread candidusl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Shcherbakov updated  JENKINS-55609  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Will either drop issue in a week if no response or update (if have ability to test myself).  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55609  
 
 
  Submitted JCL no longer supports variable substitution   
 

  
 
 
 
 

 
Change By: 
 Alexander Shcherbakov  
 
 
Status: 
 In Progress Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 attachment  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55687) A problem occurred while processing the request

2019-01-18 Thread ranjith.rajre...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ranjith reddy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55687  
 
 
  A problem occurred while processing the request   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Ranjith reddy  
 
 
Components: 
 micro-focus-performance-center-integration-plugin  
 
 
Created: 
 2019-01-18 17:06  
 
 
Environment: 
 SUSE linux  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Ranjith reddy  
 

  
 
 
 
 

 
 Till yesterday my jenkins jobs are working fine. But today its giving me the following error. Please explain me the situation and help me to fix it.    A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users listmight be also useful in understanding what has happened. Stack trace org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.108.jar!/lib/form/block.jelly:32:22:  hudson/matrix/MatrixProject at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commo

[JIRA] (JENKINS-55609) Submitted JCL no longer supports variable substitution

2019-01-18 Thread candidusl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Shcherbakov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55609  
 
 
  Submitted JCL no longer supports variable substitution   
 

  
 
 
 
 

 
Change By: 
 Alexander Shcherbakov  
 
 
Comment: 
 I've uploaded new version as attachment. I'll wait for a week before releasing if I have no feedback from you.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55609) Submitted JCL no longer supports variable substitution

2019-01-18 Thread candidusl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Shcherbakov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55609  
 
 
  Submitted JCL no longer supports variable substitution   
 

  
 
 
 
 

 
Change By: 
 Alexander Shcherbakov  
 
 
Issue Type: 
 Bug Improvement  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55683) Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication

2019-01-18 Thread ryan.desm...@radiantsolutions.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ryan Desmond commented on  JENKINS-55683  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication   
 

  
 
 
 
 

 
 JENKINS-55669 and JENKINS-55668 are variations of this on the LTS.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55609) Submitted JCL no longer supports variable substitution

2019-01-18 Thread candidusl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Shcherbakov commented on  JENKINS-55609  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Submitted JCL no longer supports variable substitution   
 

  
 
 
 
 

 
 I've uploaded new version as attachment. I'll wait for a week before releasing if I have no feedback from you.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55609) Submitted JCL no longer supports variable substitution

2019-01-18 Thread candidusl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Shcherbakov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55609  
 
 
  Submitted JCL no longer supports variable substitution   
 

  
 
 
 
 

 
Change By: 
 Alexander Shcherbakov  
 
 
Attachment: 
 zos-connector.hpi  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55683) Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication

2019-01-18 Thread ryan.desm...@radiantsolutions.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ryan Desmond commented on  JENKINS-55683  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication   
 

  
 
 
 
 

 
 I am using the Bitbucket OAuth 0.7, and just updated from 2.150.1 to 2.150.2 (it looks likethe security patch causing your problem was backported to the LTS release).  I see the same problem.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55686) Updating to 2.150.2 breaks openid plugin

2019-01-18 Thread eric_font...@bose.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Fontana created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55686  
 
 
  Updating to 2.150.2 breaks openid plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 openid-plugin  
 
 
Created: 
 2019-01-18 16:58  
 
 
Environment: 
 Kubernetes  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Eric Fontana  
 

  
 
 
 
 

 
 I updated to 2.150.2 from 2.150.1 and the openid plugin no longer works. Jenkins hangs at startup with nothing in the logs.  Had to roll back to 2.150.1 and it started working again.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
   

[JIRA] (JENKINS-55681) Release the JAXB Plugin

2019-01-18 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus commented on  JENKINS-55681  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Release the JAXB Plugin   
 

  
 
 
 
 

 
 I plan to release an alpha version as soon as https://github.com/jenkins-infra/repository-permissions-updater/pull/999 is merged to be able to do more tests easily. Then I think I'll sync with the Java 11 support team before actually releasing into the main 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55681) Release the JAXB Plugin

2019-01-18 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus started work on  JENKINS-55681  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55654) infinite redirect loop when auth provider is oidc (after update to 2.160)

2019-01-18 Thread tobias.h...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tobias Herrmann Hinz commented on  JENKINS-55654  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: infinite redirect loop when auth provider is oidc (after update to 2.160)   
 

  
 
 
 
 

 
 Wadeck Follonier - on it.   
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55595) S3 plugin Configuration as Code support

2019-01-18 Thread j...@hazelcast.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jiri Holusa assigned an issue to Jiri Holusa  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55595  
 
 
  S3 plugin Configuration as Code support   
 

  
 
 
 
 

 
Change By: 
 Jiri Holusa  
 
 
Assignee: 
 Alexander A Jiri Holusa  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55595) S3 plugin Configuration as Code support

2019-01-18 Thread j...@hazelcast.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jiri Holusa commented on  JENKINS-55595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: S3 plugin Configuration as Code support   
 

  
 
 
 
 

 
 I figured it out and sent a PR: https://github.com/jenkinsci/s3-plugin/pull/118  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55685) Claim plugin should not require node block in scripted Pipeline

2019-01-18 Thread joerg.schwaerz...@infineon.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joerg Schwaerzler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55685  
 
 
  Claim plugin should not require node block in scripted Pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Arnaud TAMAILLON  
 
 
Components: 
 claim-plugin  
 
 
Created: 
 2019-01-18 16:14  
 
 
Environment: 
 claim plugin version 2.15  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joerg Schwaerzler  
 

  
 
 
 
 

 
 Currently the claim plugin refuses to work in case it is not called from within a node block in scripted Pipeline. However I do not see a reason why the claim plugin should require a node block at all.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
  

[JIRA] (JENKINS-55629) Bitbucket source missing after upgrade to 2.4.0

2019-01-18 Thread kvijay...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vijay K closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55629  
 
 
  Bitbucket source missing after upgrade to 2.4.0   
 

  
 
 
 
 

 
Change By: 
 Vijay K  
 
 
Status: 
 Open Closed  
 
 
Assignee: 
 Karl Shultz  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55629) Bitbucket source missing after upgrade to 2.4.0

2019-01-18 Thread kvijay...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vijay K commented on  JENKINS-55629  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket source missing after upgrade to 2.4.0   
 

  
 
 
 
 

 
 Thanks a lot for your Feedback here. I'll plan to upgrade Jenkins and check if things work fine. Closing the issue in regards to your suggestions.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55562) Plugin can not be loaded anymore due to JDK Problems

2019-01-18 Thread raphael.pio...@t-systems.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raphael Pionke updated  JENKINS-55562  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55562  
 
 
  Plugin can not be loaded anymore due to JDK Problems   
 

  
 
 
 
 

 
Change By: 
 Raphael Pionke  
 
 
Status: 
 Fixed but Unreleased Closed  
 
 
Released As: 
 Performance Signature 3.0.3  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55629) Bitbucket source missing after upgrade to 2.4.0

2019-01-18 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz commented on  JENKINS-55629  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket source missing after upgrade to 2.4.0   
 

  
 
 
 
 

 
 Vijay K - thanks for filing this   I noticed that you've mentioned running "Jenkins 2.7.4." Is that correct? Because, if so, I bet that's why stuff isn't working for you. I took a look at the plugin's pom.xml file, and it specifies a minimum Jenkins version of 2.60.3, here, on L54.  Are you able to move to a more up to date version of Jenkins itself? I'd recommend doing so anyway. Lots and lots of enhancements have gone in since 2.7.4, including a whole bunch of security enhancements that would be good to pick up. In any event, I can't recreate it either. Here it is running locally on my laptop, by building the plugin at the cloudbees-bitbucket-branch-source-2.4.0 tag, and running it in development mode via mvn hpi:run. That ends me up with Jenkins core 2.60.3:I've also installed it to my more traditional system, which is running core 2.160 along with various beta-level plugins from the experimental 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55629) Bitbucket source missing after upgrade to 2.4.0

2019-01-18 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55629  
 
 
  Bitbucket source missing after upgrade to 2.4.0   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Attachment: 
 screenshot-3.png  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55629) Bitbucket source missing after upgrade to 2.4.0

2019-01-18 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55629  
 
 
  Bitbucket source missing after upgrade to 2.4.0   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Attachment: 
 screenshot-2.png  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55350) Open Tasks Scanner throws java.nio.charset.UnmappableCharacterException

2019-01-18 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-55350  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Open Tasks Scanner throws java.nio.charset.UnmappableCharacterException   
 

  
 
 
 
 

 
 Hmm, I don't know how I can help here in the plugin configuration. I need to choose an encoding if I read a file. I don't see how we can make the configurable for each file. Do you have an idea? Wouldn't it be easier if you use the same encoding for each job?  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-44650) Slave is not connecting to jenkins server with version 2.63

2019-01-18 Thread nagavenkateshna...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Naga Naidu commented on  JENKINS-44650  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Slave is not connecting to jenkins server with version 2.63   
 

  
 
 
 
 

 
 Upgarding Java is onething, but still i had issue with windows slave connectivity. FIX: Deleted the Node from the Master and created new workspace in the slave and created node slave again the master. That fixed the issue.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55611) Make EXECUTOR_NUMBER available for yaml definition

2019-01-18 Thread bigdr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Drum Big commented on  JENKINS-55611  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make EXECUTOR_NUMBER available for yaml definition   
 

  
 
 
 
 

 
 hmm. Is it possible for the kubernetes plugin to allocate and provide some variable like this by itself? (Some kind of unique id that does not collide with other concurrent run, but is reused once the job is finished).  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55620) SloccountPublisher fails on Java 11 without --add-modules java.xml.bind

2019-01-18 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus commented on  JENKINS-55620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SloccountPublisher fails on Java 11 without --add-modules java.xml.bind   
 

  
 
 
 
 

 
 the PR is proposing a fix, which implies releasing the new JAXB plugin (JENKINS-55681). I created a dedicated Docker image for anyone to test this easily https://github.com/batmat/jaxb-java11-demo  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55682) Portlet view for warnings-ng doesn't get styled properly

2019-01-18 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-55682  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Portlet view for warnings-ng doesn't get styled properly   
 

  
 
 
 
 

 
 Ah, I see, the wether icons are wrong. Or is something else not working?  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines

2019-01-18 Thread jonas.d.lindst...@netent.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonas Lindström edited a comment on  JENKINS-55308  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: intermittent "terminated" messages using sh in Pipelines   
 

  
 
 
 
 

 
 We run the jenkins-alpine docker image and we also get these messages. I tried switching to the Debian image  (2.150.2)  and the intermittent "terminated" message are still there, so I don't think it's specifically related to the OS.This seems to have been introduced after v1.22 of durable-task-plugin. I guess the error is lurking somewhere in this line in BourneShellScript.java:{code:java}cmd = String.format("pid=$$; { while [ \\( -d /proc/$pid -o \\! -d /proc/$$ \\) -a -d '%s' -a \\! -f '%s' ]; do touch '%s'; sleep 3; done } & jsc=%s; %s=$jsc %s '%s' > '%s' 2> '%s'; echo $? > '%s.tmp'; mv '%s.tmp' '%s'; wait", ... more args ...{code}It's difficult to downgrade to 1.22 since so many other plugins depend on later versions of this plugin.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines

2019-01-18 Thread jonas.d.lindst...@netent.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonas Lindström commented on  JENKINS-55308  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: intermittent "terminated" messages using sh in Pipelines   
 

  
 
 
 
 

 
 We run the jenkins-alpine docker image and we also get these messages. I tried switching to the Debian image and the intermittent "terminated" message are still there, so I don't think it's specifically related to the OS. This seems to have been introduced after v1.22 of durable-task-plugin. I guess the error is lurking somewhere in this line in BourneShellScript.java: 

 

cmd = String.format("pid=$$; { while [ \\( -d /proc/$pid -o \\! -d /proc/$$ \\) -a -d '%s' -a \\! -f '%s' ]; do touch '%s'; sleep 3; done } & jsc=%s; %s=$jsc %s '%s' > '%s' 2> '%s'; echo $? > '%s.tmp'; mv '%s.tmp' '%s'; wait", 
... more args ... 

 It's difficult to downgrade to 1.22 since so many other plugins depend on later versions of this plugin.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents

2019-01-18 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-55257  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Timestamper break builds on Windows agents   
 

  
 
 
 
 

 
 Reproduced the stack trace under somewhat artificial conditions in a functional test, so I am pretty confident my core patch would fix it even if the timestamper plugin patch continues to be delayed. For affected users, the workaround is simple: upgrade your agent JARs.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55655) BlueOcean Pipeline creation does not respect ssh ProxyCommand even though classic project creation does

2019-01-18 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-55655  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BlueOcean Pipeline creation does not respect ssh ProxyCommand even though classic project creation does   
 

  
 
 
 
 

 
  Those other cases that you note are using more arguments to the Git object before they request the GitClient object. The extra arguments are a good thing in those cases because they tell the Git object the repository directory and the implementation to be used. The Blue Ocean plugin doesn't need to provide those extra arguments because it is performing an early permission check. It doesn't need a repository directory and shouldn't need to pass an implementation to be used. I suspect the specific issue you're seeing could also be solved by changing Blue Ocean to have it read the list of available git implementations and pass the first implementation as the implementation for that call. However, that is more work for Blue Ocean and gives it knowledge of the git plugin implementation that it really should not need.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55595) S3 plugin Configuration as Code support

2019-01-18 Thread j...@hazelcast.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jiri Holusa commented on  JENKINS-55595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: S3 plugin Configuration as Code support   
 

  
 
 
 
 

 
 Alexander A I was digging through the code. I tried following snippet: 

 


{color:#80}s3upload:
{color}{color:#80}  profiles:
{color} - {color:#80}name: {color}{color:#008000}"jenkins-profile"
{color}   {color:#80}accessKey: {color}{color:#008000}"haha"
{color}   {color:#80}secretKey: {color}{color:#008000}"haha"{color}

 

   But it didn't work with stacktrace: 

 


Invalid configuration elements for type class hudson.plugins.s3.S3BucketPublisher$DescriptorImpl : profiles.

 

   So kept digging. I think it's not possible because https://github.com/jenkinsci/s3-plugin/blob/master/src/main/java/hudson/plugins/s3/S3BucketPublisher.java#L394 , the field is private and there is no constructor for it. Now I'm stuck. I'm willing to invest some time into this and make it work, but I need some guidenance. Any thoughts? Or perhaps Nicolas De Loof ?  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55595) S3 plugin Configuration as Code support

2019-01-18 Thread j...@hazelcast.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jiri Holusa commented on  JENKINS-55595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: S3 plugin Configuration as Code support   
 

  
 
 
 
 

 
 Alexander A I was digging through the code. I tried following snippet: 

 


{color:#80}s3upload:
{color}{color:#80}  profiles:
{color} - {color:#80}name: {color}{color:#008000}"jenkins-profile"
{color}   {color:#80}accessKey: {color}{color:#008000}"haha"
{color}   {color:#80}secretKey: {color}{color:#008000}"haha"{color}

 

   But it didn't work with stacktrace: 

 


Invalid configuration elements for type class hudson.plugins.s3.S3BucketPublisher$DescriptorImpl : profiles.

 

   So kept digging. I think it's not possible because https://github.com/jenkinsci/s3-plugin/blob/master/src/main/java/hudson/plugins/s3/S3BucketPublisher.java#L394 , the field is private and there is no constructor for it. Now I'm stuck. I'm willing to invest some time into this and make it work, but I need some guidenance. Any thoughts? Or perhaps Nicolas De Loof ?  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54058) Old agent.jar causes JNLP agent to fail checkout with java.lang.IllegalAccessError

2019-01-18 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 JENKINS-55257 has more discussion (though this Summary is perhaps more helpful).  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-54058  
 
 
  Old agent.jar causes JNLP agent to fail checkout with java.lang.IllegalAccessError   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54058) Old agent.jar causes JNLP agent to fail checkout with java.lang.IllegalAccessError

2019-01-18 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54058  
 
 
  Old agent.jar causes JNLP agent to fail checkout with java.lang.IllegalAccessError   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Resolution: 
 Not A Defect  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55585) Powershell plugin inside container hangs

2019-01-18 Thread chiranth.bagivaluramasw...@citrix.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chiranth Bagivalu Ramaswamy commented on  JENKINS-55585  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Powershell plugin inside container hangs   
 

  
 
 
 
 

 
 Update: I have also tested with a different image i.e docker.image("julkwiec/dotnet-mono-powershell-build:latest") and the issue is still the same. Could anyone help look into the issue?  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents

2019-01-18 Thread daniel.pa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 D Pasto commented on  JENKINS-55257  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Timestamper break builds on Windows agents   
 

  
 
 
 
 

 
 Looks similar to JENKINS-54058,[ as does the current characterization of this issue.  What do you think?  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55684) Parameterized Remote Trigger Plugin

2019-01-18 Thread vika-ulbut...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 VIKTORIYA ULBUTOVA created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55684  
 
 
  Parameterized Remote Trigger Plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 KaiHsiang Chang  
 
 
Attachments: 
 JenkinsJob.png, RemoteJenkins1.png, RemoteJenkins2.png, RemoteJenkins3.png  
 
 
Components: 
 parameterized-remote-trigger-plugin  
 
 
Created: 
 2019-01-18 14:28  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 VIKTORIYA ULBUTOVA  
 

  
 
 
 
 

 
 My Jenkins version 2.116; remote Jenkins version 2.66.  At first I configured the remote job call in my jenkins master ( you can see on a screen JenkinsJob.png). After I wrote a function in pipeline:  void runIntegrationTests()  { def handle = triggerRemoteJob(remoteJenkinsName: 'AFT_Desk', job: 'AFTDesk_RunTM_Allure_NDO', parameters: 'TESTMODEL_ID=46') } I have also configured remote jenkins job (screen RemoteJenkins1.png, RemoteJenkins2.png, RemoteJenkins3.png).  Then I run my jenkins pipeline and got this error:    http://jenkins-rc.moscow.alfaintra.net:8080/blue/organizations/jenkins/cashrequest-ui/detail/feature%2FRCNDO-343/113/pipeline#step-58-log-2 Parameterized Remote Trigger Configuration:  - job: AFTDesk_RunTM_Allure_NDO  - remoteJenkinsName: AFT_Desk  - parameters: [TESTMODEL_ID=46]  - blockBuildUntilComplete: true  - connectionRetryLimit: 5      http://jenkins-rc.moscow.alfaintra.net:8080/blue/organizations/jenkins/cashrequest-ui/detail/feature%2FRCNDO-343/113/pipeline#step-58-log-9Connection to remote server failed , waiting for to retry - 10 seconds until next attempt. URL: http://ltjenkins:8080/job/MDMi_Pipeline/job/NDO/job/AFTDesk_RunTM_Allure_NDO/api/json, parameters: 

[JIRA] (JENKINS-55683) Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication

2019-01-18 Thread f...@geekplace.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Florian Schmaus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55683  
 
 
  Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication   
 

  
 
 
 
 

 
Change By: 
 Florian Schmaus  
 
 
Environment: 
 Jenkins 2.160  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55683) Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication

2019-01-18 Thread f...@geekplace.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Florian Schmaus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55683  
 
 
  Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication   
 

  
 
 
 
 

 
Change By: 
 Florian Schmaus  
 
 
Component/s: 
 core  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55683) Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication

2019-01-18 Thread f...@geekplace.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Florian Schmaus created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55683  
 
 
  Endless loop on login when using OpenID plugin after upgrading to 2.160, preventing user authentication   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 openid-plugin  
 
 
Created: 
 2019-01-18 14:22  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Florian Schmaus  
 

  
 
 
 
 

 
 Our users where unable to login using OpenID after upgrading our Jenkins instance from 2.159 to 2.160. Downgrading to 2.159 makes the issue disappear. From a HTTP perspective, Jenkins forwards the user to the OpenID provider URL, which authenticates the user and redirects him back to Jenkins, where a 403 is returned. Which, in turn, causes Jenkins to redirect the user to the OpenID provider, resulting in an endless loop. Unfortunately the logs do not yield any hints. Nevertheless here they are, newest log messages on top:   Jan 18 12:48:00 ourJenkins jenkins[29449]: Jan 18, 2019 12:48:00 PM org.openid4java.shaded.apache.http.client.protocol.ResponseProcessCookies processCookies Jan 18 12:48:00 ourJenkins jenkins[29449]: INFO: Starting discovery on URL identifier: http://openid.example.org/user # Here the loop starts again. Jan 18 12:48:00 ourJenkins jenkins[29449]: Jan 18, 2019 12:48:00 PM org.openid4java.discovery.Discovery discover Jan 18 12:48:00 ourJenkins jenkins[29449]: INFO: Received positive auth response. Jan 18 12:48:00 ourJenkins jenkins[29449]: Jan 18, 2019 12:48:00 PM org.openid4java.consumer.ConsumerManager verify Jan 18 12:48:00 ourJenkins jenkins[29449]: INFO: Verifying authentication response... Jan 18 12:48:00 ourJenkins jenkins[29449]: Jan 18, 2019 12:48:00 PM org.openid4java.consumer.ConsumerManager verify Jan 18 12:48:00 ourJenkins jenkins[29449]: INFO: Return URL: https://jenkins.example.org/jenkins/securityRealm/finishLogin matches realm: https://jenkins.example.org/jenkins/securityRealm/finishLogin Jan 18 12:48:00 ourJenkins jenkins[29449]: Jan 18, 2019 12:48:00 PM org.openid4java.server.RealmVerifier match Jan 18 12:48:00 ourJenk

[JIRA] (JENKINS-55681) Release the JAXB Plugin

2019-01-18 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55681  
 
 
  Release the JAXB Plugin   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 

  
 
 
 
 

 
 Acceptance criteria: * JAXB Plugin is released to the Common Update Center ** [https://github.com/jenkinsci/jaxb-plugin]  * There are few plugins using this plugin as a dependency * minimumJavaVersion is set to 8 unless it blows up * (?) JAXB Plugin as a detached plugin on Java 11 + (Core patch), and it's bundled into WAR ** We need to explore whether it is feasible. It may be helpful to keep plugins compatible without patches on the plugin sideWhat do we need to test? * Jetty && SLOCCount Plugin * Tomcat  && SLOCCount Plugin      
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55681) Release the JAXB Plugin

2019-01-18 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55681  
 
 
  Release the JAXB Plugin   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 

  
 
 
 
 

 
 Acceptance criteria: * JAXB Plugin is released to the Common Update Center ** [https://github.com/jenkinsci/jaxb-plugin]  * There are few plugins using this plugin as a dependency * minimumJavaVersion is set to 8 unless it blows up * (?) JAXB Plugin as a detached plugin on Java 11 + (Core patch), and it's bundled into WAR ** We need to explore whether it is feasible. It may be helpful to keep plugins compatible without patches on the plugin sideWhat do we need to test? * Jetty && SLOCCount Plugin * Tomcat  && SLOCCount Plugin      
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55350) Open Tasks Scanner throws java.nio.charset.UnmappableCharacterException

2019-01-18 Thread luebbe.opensou...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lübbe Onken commented on  JENKINS-55350  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Open Tasks Scanner throws java.nio.charset.UnmappableCharacterException   
 

  
 
 
 
 

 
 OK, now I re-ran the build with sourceCodeEncoding: UTF-8 outside the task statement and now taskscanner fails to read 99% of the files because 'defined encoding 'UTF-8' seems to be wrong'. The old task scanner had no problem reading in the files and finding the open tasks regardless of encoding. The new one fails if the encoding of the file doesn't match the advertised encoding. In my opinion this is a regression, because the results are worse. I'll revert to not defining an encoding, because unfortunately we have different file encodings throughout the legacy code base.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55681) Release the JAXB Plugin

2019-01-18 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55681  
 
 
  Release the JAXB Plugin   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Component/s: 
 jaxb-plugin  
 
 
Component/s: 
 other  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-46555) Lockable Resource Plugin throws null pointer exception

2019-01-18 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-46555  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Merged, releasing as 2.4.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-46555  
 
 
  Lockable Resource Plugin throws null pointer exception   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-46555) Lockable Resource Plugin throws null pointer exception

2019-01-18 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-46555  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46555  
 
 
  Lockable Resource Plugin throws null pointer exception   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


  1   2   >