[JIRA] (JENKINS-57680) Design the clouds package to support AWS related method call

2019-05-24 Thread affei...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yufei Zhang created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57680  
 
 
  Design the clouds package to support AWS related method call   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Yufei Zhang  
 
 
Components: 
 external-workspace-manager-plugin  
 
 
Created: 
 2019-05-25 04:39  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Yufei Zhang  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-57679) Implement AwsEfsDisk class and rewrite Disk class as base class

2019-05-24 Thread affei...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yufei Zhang created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57679  
 
 
  Implement AwsEfsDisk class and rewrite Disk class as base class   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Yufei Zhang  
 
 
Components: 
 external-workspace-manager-plugin  
 
 
Created: 
 2019-05-25 04:37  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Yufei Zhang  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-57623) Update jenkins.io page

2019-05-24 Thread affei...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yufei Zhang updated  JENKINS-57623  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57623  
 
 
  Update jenkins.io page
 

  
 
 
 
 

 
Change By: 
 Yufei Zhang  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199552.1558579829000.11893.1558759020078%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57623) Update jenkins.io page

2019-05-24 Thread affei...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yufei Zhang started work on  JENKINS-57623  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Yufei Zhang  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199552.1558579829000.11892.1558755180203%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57622) Community Bounding Phase for Cloud features for EWM GSoC 2019

2019-05-24 Thread affei...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yufei Zhang started work on  JENKINS-57622  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Yufei Zhang  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199551.1558579622000.11891.1558755180158%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57678) Change getInstance() deprecated to get()

2019-05-24 Thread gustavobz...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gustavo Bezerra updated  JENKINS-57678  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57678  
 
 
  Change getInstance() deprecated to get()   
 

  
 
 
 
 

 
Change By: 
 Gustavo Bezerra  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199613.1558745152000.11890.1558745940069%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57678) Change getInstance() deprecated to get()

2019-05-24 Thread gustavobz...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gustavo Bezerra started work on  JENKINS-57678  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Gustavo Bezerra  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199613.1558745152000.11889.1558745760072%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57678) Change getInstance() deprecated to get()

2019-05-24 Thread gustavobz...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gustavo Bezerra created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57678  
 
 
  Change getInstance() deprecated to get()   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Gustavo Bezerra  
 
 
Attachments: 
 print.png  
 
 
Components: 
 core  
 
 
Created: 
 2019-05-25 00:45  
 
 
Labels: 
 newbie-friendly improvement jenkins  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Gustavo Bezerra  
 

  
 
 
 
 

 
 The method Jenkins.getInstance() is deprecated, and the recommendation is to use the get method instead.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57371) error message when building PR

2019-05-24 Thread audun.hall...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Audun Halland commented on  JENKINS-57371  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: error message when building PR   
 

  
 
 
 
 

 
 Thanks, excited to try it out. Though our famous PR-47 is already long gone, I'll be sure to keep my eyes open for failing PRs in the future! Thank you again for improving Jenkins and for great support on this 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.11887.1558737840219%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-23060) Promotion does not work if job name contains a whitespace

2019-05-24 Thread mco...@rgare.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Corum commented on  JENKINS-23060  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Promotion does not work if job name contains a whitespace   
 

  
 
 
 
 

 
 How do we increase the priority on this 5-year old issue?  This is a pretty serious issue if people have naming conventions for jobs.  This is still happening with Jenkins v2.173 and promoted build plugin version 3.2.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled

2019-05-24 Thread ullrich.haf...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-56007  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't copy source files from slave to master if security is enabled
 

  
 
 
 
 

 
 We created a test for this issue now: https://github.com/jenkinsci/warnings-ng-plugin/pull/90 Seems that we still miss something in your setup since the test passes. We currently enable the master-agent security and try to start a build on a slave.  Are we missing something obvious in the test? How do you connect master and agent? Which other kind of security settings did you enable? What Authorization did you enable?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-56333) Error reported as warning (high) for pc-lint parser

2019-05-24 Thread ullrich.haf...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-56333  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error reported as warning (high) for pc-lint parser   
 

  
 
 
 
 

 
 This will be possible in the near future: see https://github.com/jenkinsci/warnings-ng-plugin/pull/58. I'm not sure when the UI side is being changed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-34521) Text parameters are rendered as text input instead of text area

2019-05-24 Thread michael.kostu...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Kostukov commented on  JENKINS-34521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Text parameters are rendered as text input instead of text area   
 

  
 
 
 
 

 
 Added Sam back.   Sam, it's been 3 years since you mentioned that the fix is in the works. Any luck?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-34521) Text parameters are rendered as text input instead of text area

2019-05-24 Thread michael.kostu...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Kostukov assigned an issue to Sam Van Oort  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34521  
 
 
  Text parameters are rendered as text input instead of text area   
 

  
 
 
 
 

 
Change By: 
 Michael Kostukov  
 
 
Assignee: 
 Sam Van Oort  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria

2019-05-24 Thread jsoref+jenk...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54126  
 
 
  Jenkinsfile not found in PR on GitHub -- Does not meet criteria   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Summary: 
 Jenkinsfile not found in PR on GitHub  -- Does not meet criteria  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-42125) Bitbucket branch source plugin cannot scan jenkinsfile by branches whose names are followed by number sign (#)

2019-05-24 Thread jsoref+jenk...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42125  
 
 
  Bitbucket branch source plugin cannot scan jenkinsfile by branches whose names are followed by number sign (#)   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Summary: 
 Bitbucket branch source plugin cannot scan jenkinsfile by  branchs  branches  whose names are followed by number sign (#)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-56333) Error reported as warning (high) for pc-lint parser

2019-05-24 Thread davidlevy...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Levy commented on  JENKINS-56333  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error reported as warning (high) for pc-lint parser   
 

  
 
 
 
 

 
 Just ran basic tests, error is detected, build is correctly failed because of my quality gate. But in blue ocean, the step is still green, so its hard to detect where the fail comes from  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin

2019-05-24 Thread marky.r.jack...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson commented on  JENKINS-57677  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Create new repo for GSoC gitlab-branch-source-plugin   
 

  
 
 
 
 

 
 Please add me as an admin of the repo  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin

2019-05-24 Thread marky.r.jack...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57677  
 
 
  Create new repo for GSoC gitlab-branch-source-plugin   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 gitlab-branch-source-plugin  
 
 
Created: 
 2019-05-24 19:48  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Marky Jackson  
 

  
 
 
 
 

 
 For the GSoC project   gitlab-branch-source-plugin the student is requesting a new repo be created titled "gitlab-branch-plugin   Detailed reasoning for this is here:  2) I read the documentation of SCM API}}and {{Branch API Plugins to understand the classes needs to be implemented in GitLab Branch Source Plugin. Based on which I prepared the design document. This design document will be improved throughout the course of development. Will add apis, workflow, issues etc to it. 3) I have been studing the codebases of ArgelBargel's GitLab Branch Source Plugin, GitHub Branch Source Plugin}}and {{Gitea Plugin. My takeaway was GitLab BS has been implemented in a way that is not very different from the other Branch Source Plugins in terms of the underlying APIs implementation but still exists some differences that cannot be ignored. For example, i) The class names are different and many code refractories has been done so it creates a difficulty in implementing the same logic while extending the plugin. Like SCMSource has been broken down to other sub classes , SCMHeadCategory has some different implementation, SCMFileSystem is not implemented, APIs implementation also needs to be changed and the list goes on.. ii) The conclusion I have come to is that it would be rather lesser amount of work for me if I had to implement a new GitLab Branch Source Plugin which will be heavily inspired from Gitea Plugin (as suggested by Robert Sandall in mailing list) and also some inspiration will be taken from GitLab Branch Source and GitHub Branch Source Plugins. iii) I will send my compelete list of reasons not to develop the existing GitLab Branch Source Plugin.

[JIRA] (JENKINS-29037) Add Max interval to waitUntil

2019-05-24 Thread jgl...@cloudbees.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-29037  
 
 
  Add Max interval to waitUntil   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 stalled-pr  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-24 Thread jgl...@cloudbees.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 rherrick this was fixed weeks ago, you just need to update.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-24 Thread jgl...@cloudbees.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199007.1556619184000.11729.1558725300728%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-24 Thread jgl...@cloudbees.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Released As: 
 core 2.176  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57171) Permissive script security plugin is broken after updating to script security 1.58

2019-05-24 Thread be_...@sbcglobal.net (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Ray commented on  JENKINS-57171  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Permissive script security plugin is broken after updating to script security 1.58   
 

  
 
 
 
 

 
 0.5 seems to clear up the issue in my local test Jenkins now with permissive-script-security.enabled=true. We'll try 0.5 in production soon. Thank you Oliver Gondža.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57633) Finalise the "Skeleton" design for the plugin

2019-05-24 Thread 2017uec1...@mnit.ac.in (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Prastik Gyawali updated  JENKINS-57633  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57633  
 
 
  Finalise the "Skeleton" design for the plugin   
 

  
 
 
 
 

 
Change By: 
 Prastik Gyawali  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199563.1558604531000.11699.1558723860062%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57633) Finalise the "Skeleton" design for the plugin

2019-05-24 Thread 2017uec1...@mnit.ac.in (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Prastik Gyawali updated  JENKINS-57633  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57633  
 
 
  Finalise the "Skeleton" design for the plugin   
 

  
 
 
 
 

 
Change By: 
 Prastik Gyawali  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199563.1558604531000.11698.1558723800131%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57633) Finalise the "Skeleton" design for the plugin

2019-05-24 Thread 2017uec1...@mnit.ac.in (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Prastik Gyawali stopped work on  JENKINS-57633  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Prastik Gyawali  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199563.1558604531000.11697.1558723740111%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57676) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.244.0.51/10.244.0.51:58278

2019-05-24 Thread venkatesh100doll...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 venkatesh p created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57676  
 
 
  Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.244.0.51/10.244.0.51:58278   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 slave-utilization-plugin  
 
 
Created: 
 2019-05-24 18:41  
 
 
Environment: 
 unix centos  
 
 
Labels: 
 jenkins  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 venkatesh p  
 

  
 
 
 
 

 
 Facing below error Cloning the remote Git repository Cloning repository  https://github.com/venkateshpakanati/jenkins-test.git > git init /home/jenkins/workspace/Test # timeout=10 Fetching upstream changes from  https://github.com/venkateshpakanati/jenkins-test.git > git --version # timeout=10 using GIT_ASKPASS to set credentials  > git fetch --tags --progress  https://github.com/venkateshpakanati/jenkins-test.git +refs/heads/:refs/remotes/origin/ ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress  https://github.com/venkateshpakanati/jenkins-test.git +refs/heads/:refs/remotes/origin/" returned status code 128: stdout:  stderr: fatal: unable to access ' https://github.com/venkateshpakanati/jenkins-test.git/ ': Could not resolve host: github.com  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at

[JIRA] (JENKINS-57675) Pipeline steps running forever when executor fails

2019-05-24 Thread jenkins-ci....@meneguello.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno Meneguello created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57675  
 
 
  Pipeline steps running forever when executor fails   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 kubernetes-plugin, pipeline  
 
 
Created: 
 2019-05-24 18:29  
 
 
Environment: 
 Jenkins 2.164.3  Kubernetes Plugin 1.15.4  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Bruno Meneguello  
 

  
 
 
 
 

 
 I've been using Pipelines with EC2, ECS and now Kubernetes dynamic executors for some time. I always noted an strange behavior but never found more information: When, by any reason, my agent dies, some Pipeline steps don't fail and keep running forever, unless I use timeout steps. I just need to abort the job and it goes away. Another strange thing is the executor stay present with the "offline" label, even the log displaying the failed connection. And it goes away with the job, when aborted.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57674) CRON not working properly

2019-05-24 Thread brian.p...@highfive.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Pham created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57674  
 
 
  CRON not working properly   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Screen Shot 2019-05-24 at 11.22.12 AM.png, Screen Shot 2019-05-24 at 11.24.05 AM.png  
 
 
Components: 
 core  
 
 
Created: 
 2019-05-24 18:25  
 
 
Environment: 
 Jenkins version: 2.164.3  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Brian Pham  
 

  
 
 
 
 

 
 Have a job that is scheduled to run periodically using the following.  
 
1 * * 7 
 This should be running at every min past hour 1 on Sunday.    For some reason after the most recent update, ran every 5 mins accordingly to the build history.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57673) Add column sort to "Fixed Issues"

2019-05-24 Thread jfa...@tsunamit.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jason Faust created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57673  
 
 
  Add column sort to "Fixed Issues"   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Ulli Hafner  
 
 
Components: 
 warnings-ng-plugin  
 
 
Created: 
 2019-05-24 18:12  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jason Faust  
 

  
 
 
 
 

 
 Being able to sort the Fixed Issues display would be useful.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-57672) Determine Dependencies between PluginManager.java on Jenkins Core

2019-05-24 Thread natasha.st...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Natasha Stopa created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57672  
 
 
  Determine Dependencies between PluginManager.java on Jenkins Core
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Natasha Stopa  
 
 
Components: 
 core  
 
 
Created: 
 2019-05-24 18:05  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Natasha Stopa  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to

[JIRA] (JENKINS-1182) Discard old builds only if the latest build is stable

2019-05-24 Thread nisshah1...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah assigned an issue to Nisarg Shah  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-1182  
 
 
  Discard old builds only if the latest build is stable   
 

  
 
 
 
 

 
Change By: 
 Nisarg Shah  
 
 
Assignee: 
 Nisarg Shah  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-1182) Discard old builds only if the latest build is stable

2019-05-24 Thread nisshah1...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-1182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Discard old builds only if the latest build is stable   
 

  
 
 
 
 

 
 Okay so I will try to add this feature to discard old build plugin. I am assigning this issue to me.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57513  
 
 
  Split the large databound constructors into databound setters   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 jcasc-compatibility  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57580) Add support for JCasC xldeploy-plugin / deployitNotifier

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57580  
 
 
  Add support for JCasC xldeploy-plugin / deployitNotifier   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 jcasc-compatibility  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57659) jenkins share library Cannot cast object 'true' with class 'java.lang.Boolean'

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57659  
 
 
  jenkins share library Cannot cast object 'true' with class 'java.lang.Boolean'   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 pipeline  
 
 
Component/s: 
 jenkinsfile-runner  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57669) Write K8s spec for Zookeeper and Kafka nodes

2019-05-24 Thread vulongv...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Long Nguyen started work on  JENKINS-57669  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Long Nguyen  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199602.1558718399000.11660.1558718820183%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57667) Launching Zookeeper and Kafka in K8s

2019-05-24 Thread vulongv...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Long Nguyen started work on  JENKINS-57667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Long Nguyen  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199600.155871834.11659.1558718820140%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57670) Create new Helm chart from Jenkins Helm chart to launch Zookeeper and Kafka

2019-05-24 Thread vulongv...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Long Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57670  
 
 
  Create new Helm chart from Jenkins Helm chart to launch Zookeeper and Kafka   
 

  
 
 
 
 

 
Change By: 
 Long Nguyen  
 
 
Summary: 
 Extends Create new Helm chart from  Jenkins Helm chart to launch Zookeeper and Kafka  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-1182) Discard old builds only if the latest build is stable

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-1182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Discard old builds only if the latest build is stable   
 

  
 
 
 
 

 
 Discard Old Builds plugin might be preferable    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57671) Lauching configuration in Helm chart to install Remoting Kafka plugin

2019-05-24 Thread vulongv...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Long Nguyen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57671  
 
 
  Lauching configuration in Helm chart to install Remoting Kafka plugin   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Long Nguyen  
 
 
Components: 
 remoting-kafka-plugin  
 
 
Created: 
 2019-05-24 17:22  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Long Nguyen  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-57670) Extends Jenkins Helm chart to launch Zookeeper and Kafka

2019-05-24 Thread vulongv...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Long Nguyen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57670  
 
 
  Extends Jenkins Helm chart to launch Zookeeper and Kafka   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Long Nguyen  
 
 
Components: 
 remoting-kafka-plugin  
 
 
Created: 
 2019-05-24 17:21  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Long Nguyen  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-1182) Discard old builds only if the latest build is stable

2019-05-24 Thread nisshah1...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-1182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Discard old builds only if the latest build is stable   
 

  
 
 
 
 

 
 Oleg Nenashev Is it necessary to make a new plugin? Can't we just add few "if conditions" in LogRotator or discard old build plugin? Fetching the status of last build and checking whether it was stable or not. And then performing discard actions accordingly.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57669) Write K8s spec for Zookeeper and Kafka nodes

2019-05-24 Thread vulongv...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Long Nguyen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57669  
 
 
  Write K8s spec for Zookeeper and Kafka nodes   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Long Nguyen  
 
 
Components: 
 remoting-kafka-plugin  
 
 
Created: 
 2019-05-24 17:19  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Long Nguyen  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-57668) Extend K8s plugin's Cloud API to launch Kafka agents

2019-05-24 Thread vulongv...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Long Nguyen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57668  
 
 
  Extend K8s plugin's Cloud API to launch Kafka agents   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Long Nguyen  
 
 
Components: 
 remoting-kafka-plugin  
 
 
Created: 
 2019-05-24 17:19  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Long Nguyen  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-57667) Launching Zookeeper and Kafka in K8s

2019-05-24 Thread vulongv...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Long Nguyen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57667  
 
 
  Launching Zookeeper and Kafka in K8s   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Long Nguyen  
 
 
Components: 
 remoting-kafka-plugin  
 
 
Created: 
 2019-05-24 17:19  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Long Nguyen  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-57666) Coding Phase 1 for Remoting Kafka on K8s project

2019-05-24 Thread vulongv...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Long Nguyen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57666  
 
 
  Coding Phase 1 for Remoting Kafka on K8s project   
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Long Nguyen  
 
 
Components: 
 remoting-kafka-plugin  
 
 
Created: 
 2019-05-24 17:17  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Long Nguyen  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-52697) Logstash plugin: support JCasC

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52697  
 
 
  Logstash plugin: support JCasC   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Released As: 
 Logstash Plugin 2.3.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-43386) Not sending mail to user with permission to view

2019-05-24 Thread adams.david...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Adams commented on  JENKINS-43386  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not sending mail to user with permission to view   
 

  
 
 
 
 

 
 Experiencing similar issues as Steve Graham. Using github oauth client for a github organization and can't get email to send. I've tried checking "Allow sending to unregistered users" with no change. I still get:  "Not sending mail to user myem...@gmail.com with no permission to view My Project » my-branch#40An attempt to send an e-mail to empty list of recipients, ignored."  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call

2019-05-24 Thread bitwise...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57111  
 
 
  Base class setChannel does not handle exceptions from onOnline call   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Released As: 
 Jenkins 2.177 , LTS 2.176.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57583) "Ignore target branch" no longer working

2019-05-24 Thread bitwise...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57583  
 
 
  "Ignore target branch" no longer working   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199501.1558451822000.11607.1558714320208%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-52697) Logstash plugin: support JCasC

2019-05-24 Thread robin.sm...@forgerock.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robin Smith commented on  JENKINS-52697  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Logstash plugin: support JCasC   
 

  
 
 
 
 

 
 Brilliant - thank 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192583.1532331323000.11603.1558714200434%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57371) error message when building PR

2019-05-24 Thread bitwise...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated  JENKINS-57371  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57371  
 
 
  error message when building PR   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Status: 
 In Review Closed  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 2.5.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.11600.1558714200375%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-56775) Parameters are not replaced in the "Stream Codeline" field

2019-05-24 Thread pal...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated  JENKINS-56775  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56775  
 
 
  Parameters are not replaced in the "Stream Codeline" field   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198419.1553681537000.11595.1558713420256%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-56775) Parameters are not replaced in the "Stream Codeline" field

2019-05-24 Thread pal...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-56775  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameters are not replaced in the "Stream Codeline" field   
 

  
 
 
 
 

 
 https://swarm.workshop.perforce.com/changes/25655  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-49833) getApiJson: (url=...) failed due to Http error #403

2019-05-24 Thread kpshee...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Sheehan commented on  JENKINS-49833  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: getApiJson: (url="" failed due to Http error #403   
 

  
 
 
 
 

 
 I agree with Henryk Paluch, this is Jenkins calling Jenkins which gets 403 because we require authenticated users. Job status is updated so not really sure what this request is doing. We first saw this as a deny on our f/w but once we opened that up we see the 403.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-56775) Parameters are not replaced in the "Stream Codeline" field

2019-05-24 Thread pal...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen started work on  JENKINS-56775  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198419.1553681537000.11583.1558713180421%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-56775) Parameters are not replaced in the "Stream Codeline" field

2019-05-24 Thread pal...@perforce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen assigned an issue to Paul Allen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56775  
 
 
  Parameters are not replaced in the "Stream Codeline" field   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Assignee: 
 Paul Allen  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57665) Hubotapprove does not exclude build_user from approve/abort

2019-05-24 Thread rashminai...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rashmi Nair created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57665  
 
 
  Hubotapprove does not exclude build_user from approve/abort   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Naresh Rayapati  
 
 
Components: 
 hubot-steps-plugin  
 
 
Created: 
 2019-05-24 15:00  
 
 
Environment: 
 TEST  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Rashmi Nair  
 

  
 
 
 
 

 
 Hi Team,   I am using below code where in hubotApprove command do not have my id in submitter list but still it lets me approve or abort when I trigger this pipeline:   stage ('Request Approval from #devOps on rocket.chat') { steps { wrap([$class: 'BuildUser']) { sh """USER=${BUILD_USER_ID}""" hubotSend site: "forge_trial", message: "Permission requested to delete ${params.project_name} - Other users please approve except $BUILD_USER_ID who has triggered the deletion" hubotApprove site: "forge_trial", message: "Proceed or Abort $BUILD_URL/input/", submitter: "a,b,c,d", tokens: "$BUILD_NUMBER, $JENKINS_URL"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception

2019-05-24 Thread aaron.k....@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aaron Sua created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57664  
 
 
  On Release of a Version recieve a Null Pointer exception   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 jira-plugin  
 
 
Created: 
 2019-05-24 14:55  
 
 
Environment: 
 Jenkins version 2.164.3  Jira Plugin version 3.07  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Aaron Sua  
 

  
 
 
 
 

 
 After upgrading from Jenkins 2.107 and Jira Plugin 2.5 when executing the Release A Version step in a Jenkins job the output simply states: [JIRA] Marking version  in project  as released. FATAL: Unable to release jira version /: java.lang.NullPointerException Finished: FAILURE  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-46094) "Checkout over SSH" fails the build since it still uses HTTPS urls

2019-05-24 Thread bitwise...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman commented on  JENKINS-46094  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Checkout over SSH" fails the build since it still uses HTTPS urls   
 

  
 
 
 
 

 
 Al Forbes 2.4.5 of github branch source.  For bitbucket, the fix is in 2.4.2.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57663) Do not trigger all branch builds when regenerating a multibranchPipelineJob

2019-05-24 Thread costincarai...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Costin Caraivan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57663  
 
 
  Do not trigger all branch builds when regenerating a multibranchPipelineJob   
 

  
 
 
 
 

 
Change By: 
 Costin Caraivan  
 

  
 
 
 
 

 
 This is a super annoying issue that makes the jobDsl plugin really hard to use in some situations. When it regenerates a multibranchPipeline job, * * all* *  the branch builds are triggered. Of course, this can mean that * * hundreds* *  of builds are suddenly scheduled. This should, in my opinion, either: a) never happenb) or only happen when there are actual configuration changes.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57663) Do not trigger all branch builds when regenerating a multibranchPipelineJob

2019-05-24 Thread costincarai...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Costin Caraivan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57663  
 
 
  Do not trigger all branch builds when regenerating a multibranchPipelineJob   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2019-05-24 14:33  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Costin Caraivan  
 

  
 
 
 
 

 
 This is a super annoying issue that makes the jobDsl plugin really hard to use in some situations.   When it regenerates a multibranchPipeline job, *all* the branch builds are triggered. Of course, this can mean that *hundreds* of builds are suddenly scheduled. This should, in my opinion, either:   a) never happen b) or only happen when there are actual configuration changes.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-57186) New View href is an absolute URL but other menu items are relative URLs

2019-05-24 Thread nisshah1...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57186  
 
 
  New View href is an absolute URL but other menu items are relative URLs   
 

  
 
 
 
 

 
Change By: 
 Nisarg Shah  
 
 
Comment: 
 I tried applying the proposed solution, but few tests failed. So this solution won't work [~nap].  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57186) New View href is an absolute URL but other menu items are relative URLs

2019-05-24 Thread nisshah1...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57186  
 
 
  New View href is an absolute URL but other menu items are relative URLs   
 

  
 
 
 
 

 
Change By: 
 Nisarg Shah  
 
 
Comment: 
 Test Failures : [INFO] Results:[INFO][ERROR] Failures:[ERROR] FilePathTest.isDescendant_regularSymlinks:960[ERROR] FilePathTest.isDescendant_worksEvenInSymbolicWorkspace:1110[ERROR] UtilTest.resolveSymlinkToFile:570[ERROR] NewViewLinkTest.getActionsHasPermission:55 expected:<[https://127.0.0.1:8080]/newView> but was:<[]/newView>[ERROR] NewViewLinkTest.getActionsNoPermission:68 expected:<[https://127.0.0.1:8080]/newView> but was:<[]/newView>[ERROR] VirtualFileTest.forFilePath_isDescendant:277->checkCommonAssertionForIsDescendant:312[ERROR] VirtualFileTest.forFilePath_listOnlyDescendants_withoutIllegal:366->checkCommonAssertionForList:392Expected: iterable over [Has name: aa, Has name: ab, Has name: _b] in any order but: No item matches: Has name: _b in [, ][ERROR] VirtualFileTest.forFile_isDescendant:261->checkCommonAssertionForIsDescendant:312[ERROR] VirtualFileTest.forFile_listOnlyDescendants_withoutIllegal:351->checkCommonAssertionForList:392Expected: iterable over [Has name: aa, Has name: ab, Has name: _b] in any order but: No item matches: Has name: _b in [, ][ERROR] Errors:[ERROR] UtilTest.testIsSymlink_ParentIsSymlink:286 » FileSystem C:\OpenSource\core\tar...[ERROR] AtomicFileWriterTest.symlinkToDirectory:80 » FileSystem C:\OpenSource\core\tar...[ERROR] PathRemoverTest.testForceRemoveFile_ParentIsSymbolicLink:184 » FileSystem C:\O...[ERROR] PathRemoverTest.testForceRemoveFile_SymbolicLink:153 » FileSystem C:\OpenSourc...[ERROR] PathRemoverTest.testForceRemoveRecursive_ContainsSymbolicLinks:373 » FileSystem[ERROR] PathRemoverTest.testForceRemoveRecursive_ParentIsSymbolicLink:411 » FileSystem[INFO][ERROR] Tests run: 3712, Failures: 9, Errors: 6, Skipped: 28  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-57186) New View href is an absolute URL but other menu items are relative URLs

2019-05-24 Thread nisshah1...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-57186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New View href is an absolute URL but other menu items are relative URLs   
 

  
 
 
 
 

 
 Test Failures :  [INFO] Results: [INFO] [ERROR] Failures: [ERROR] FilePathTest.isDescendant_regularSymlinks:960 [ERROR] FilePathTest.isDescendant_worksEvenInSymbolicWorkspace:1110 [ERROR] UtilTest.resolveSymlinkToFile:570 [ERROR] NewViewLinkTest.getActionsHasPermission:55 expected: but was:<[]/newView> [ERROR] NewViewLinkTest.getActionsNoPermission:68 expected: but was:<[]/newView> [ERROR] VirtualFileTest.forFilePath_isDescendant:277->checkCommonAssertionForIsDescendant:312 [ERROR] VirtualFileTest.forFilePath_listOnlyDescendants_withoutIllegal:366->checkCommonAssertionForList:392 Expected: iterable over [Has name: aa, Has name: ab, Has name: _b] in any order but: No item matches: Has name: _b in [, ] [ERROR] VirtualFileTest.forFile_isDescendant:261->checkCommonAssertionForIsDescendant:312 [ERROR] VirtualFileTest.forFile_listOnlyDescendants_withoutIllegal:351->checkCommonAssertionForList:392 Expected: iterable over [Has name: aa, Has name: ab, Has name: _b] in any order but: No item matches: Has name: _b in [, ] [ERROR] Errors: [ERROR] UtilTest.testIsSymlink_ParentIsSymlink:286 » FileSystem C:\OpenSource\core\tar... [ERROR] AtomicFileWriterTest.symlinkToDirectory:80 » FileSystem C:\OpenSource\core\tar... [ERROR] PathRemoverTest.testForceRemoveFile_ParentIsSymbolicLink:184 » FileSystem C:\O... [ERROR] PathRemoverTest.testForceRemoveFile_SymbolicLink:153 » FileSystem C:\OpenSourc... [ERROR] PathRemoverTest.testForceRemoveRecursive_ContainsSymbolicLinks:373 » FileSystem [ERROR] PathRemoverTest.testForceRemoveRecursive_ParentIsSymbolicLink:411 » FileSystem [INFO] [ERROR] Tests run: 3712, Failures: 9, Errors: 6, Skipped: 28  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-57186) New View href is an absolute URL but other menu items are relative URLs

2019-05-24 Thread nisshah1...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-57186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New View href is an absolute URL but other menu items are relative URLs   
 

  
 
 
 
 

 
 I tried applying the proposed solution, but few tests failed. So this solution won't work Napoleon BlownApart.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57642) Wrong parameter type and squashing its content when trigger a job

2019-05-24 Thread sco...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Hebert commented on  JENKINS-57642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Wrong parameter type and squashing its content when trigger a job   
 

  
 
 
 
 

 
 Pavel Janoušek akostadinov We were actually hardcoding the use of StringParameterValue instead of looking at what the job was using for its CI_MESSAGE parameter. I am working on a fix with proper tests for this use case.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-56890) IOException: "cannot find current thread"

2019-05-24 Thread jgl...@cloudbees.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-56890  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IOException: "cannot find current thread"   
 

  
 
 
 
 

 
 

I wonder if there could be other problems with running the completion callback in GeneralNonBlockingStepExecution on a separate thread (maybe we need to fix that instead of just making the collection thread safe)
 Long before this API was introduced, steps were sometimes calling StepContext.get from arbitrary threads, whether that happened to be part of callback processing or not. (simple example) It is expected to be thread-safe.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57662) A blog post about our project workflow

2019-05-24 Thread marky.r.jack...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson commented on  JENKINS-57662  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: A blog post about our project workflow   
 

  
 
 
 
 

 
 Parichay Barpanda I agree with this flow and the entire blog post. Let's wait for Rick to also 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199595.1558706565000.11512.1558707360171%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once

2019-05-24 Thread mahmoud.al-a...@intel.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mahmoud Al-Ashi commented on  JENKINS-44930  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow sh to return exit status, stdout and stderr all at once   
 

  
 
 
 
 

 
 I believe command "sh" should always return an object with all relevant output (stdout, stderr, exit_code) and at the same time it should also print the output live to the console unless some argument (no_stdout) or so is given. This way you can access all at once. The other problem that I see now is that when "returnStdout" is provided, the output is not printed to the console. I would prefer to print the output to the console live anyway but also get the output to parse it or do something special with 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183003.149756330.11436.1558707241454%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57662) A blog post about our project workflow

2019-05-24 Thread parichay.barpa...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated  JENKINS-57662  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57662  
 
 
  A blog post about our project workflow   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199595.1558706565000.11434.1558706760173%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57662) A blog post about our project workflow

2019-05-24 Thread parichay.barpa...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57662  
 
 
  A blog post about our project workflow   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 

  
 
 
 
 

 
 This blog post describes how the workflow of our project will be carried. Talk about how we are using Jira and the git workflow model we are employing.  https://baymac.github.io/2019/05/project-workflow-for-gsoc  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57662) A blog post about our project workflow

2019-05-24 Thread parichay.barpa...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda assigned an issue to Marky Jackson  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57662  
 
 
  A blog post about our project workflow   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Assignee: 
 Parichay Barpanda Marky Jackson  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57662) A blog post about our project workflow

2019-05-24 Thread parichay.barpa...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57662  
 
 
  A blog post about our project workflow   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Parichay Barpanda  
 
 
Components: 
 gitlab-api-plugin, gitlab-branch-source-plugin  
 
 
Created: 
 2019-05-24 14:02  
 
 
Environment: 
 Ubuntu, Git  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Trivial  
 
 
Reporter: 
 Parichay Barpanda  
 

  
 
 
 
 

 
 This blog post describes how the workflow of our project will be carried. Talk about how we are using Jira and the git workflow model we are employing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57581) Jenkins job created by seed job using jobdsl script does't shows JMS message checks on job UI.

2019-05-24 Thread sco...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Hebert updated  JENKINS-57581  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57581  
 
 
  Jenkins job created by seed job using jobdsl script does't shows JMS message checks on job UI.   
 

  
 
 
 
 

 
Change By: 
 Scott Hebert  
 
 
Status: 
 Reopened 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199498.1558437008000.11427.1558705440239%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57581) Jenkins job created by seed job using jobdsl script does't shows JMS message checks on job UI.

2019-05-24 Thread sco...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Hebert commented on  JENKINS-57581  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins job created by seed job using jobdsl script does't shows JMS message checks on job UI.   
 

  
 
 
 
 

 
 So 3 things. 
 
my script is not a pipeline script. it is a DSL script. 
You mis-spelled msgCheck. 
Using your method of configure is not correctly creating the CIBuildTrigger object in that Jenkins complains that it is missing a parameter from a class that CIBuildTrigger inherited. 
   Here is my version of your DSL script that works for me:   

 
import groovy.json.JsonSlurper
def uuid = UUID.randomUUID().toString()

folder('test-job')  {
 description ('folder containing jobs for Rhel-8')
}



job("test-job/job-2") {
	description()
	keepDependencies(false)
  
multiscm {
  git{

remote{
  url("https://gitlab.cee.redhat.com/g11n-qe/Rhel-8.0-Automation.git")
credentials ("demo-creds")
  
   
  }
  branch("*/master")
  }
}
  
 //label('pooja-openqa')

	disabled(false)
	concurrentBuild(false)
	steps {
		shell("""sudo cp -R * /var/lib/openqa/tests/
ls""")
 }
triggers {
ciBuildTrigger {
providerData {
activeMQSubscriberProviderData {
checks {   
  msgCheck { 
  	expectedValue("RHEL-7.7")
field("release-id")   
}
} 
name ("Red Hat UMB")
overrides
{
topic("Consumer.rh-jenkins-ci-plugin."+uuid+".VirtualTopic.distill.compose-moved")
}
selector("mtype =  'compose-moved' AND environment = 'prod' AND service = 'distill'")
}
}
noSquash(true)
}
}
 

}
 

 At this point, I will not be addressing any code changes for this issue. I am closing the ticket.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-12615) Discard Old Builds does not warn the user when no builds will be discarded

2019-05-24 Thread nisshah1...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-12615  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Discard Old Builds does not warn the user when no builds will be discarded   
 

  
 
 
 
 

 
 Jesse Glick  In implementation, I have just added one if condition(type of flag) in LogRotator.java. Whenever value of numToKeep and daysToKeep are not blank, then according to flag(new variable declared) message will be displayed. Currently I have added only if condition and I got error. I have searched regarding this error, but I am not getting it clear. Error is of failure of JUnit tests. But I don't know why it failed. [ERROR] Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 0.006 s <<< FAILURE! - in hudson.cli.PrivateKeyProviderTest [ERROR] loadKeyBroken(hudson.cli.PrivateKeyProviderTest) Time elapsed: 0.001 s <<< ERROR! java.lang.Exception: Unexpected exception, expected but was at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:28) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) Caused by: java.nio.file.NoSuchFileException: C:\Open%20Source\cli\target\test-classes\hudson\cli\openssh-broken at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) at sun.nio.fs.WindowsFileSystemProvider.newByteChannel(WindowsFileSystemProvider.java:230) at java.nio.file.Files.newByteChannel(Files.java:361) at java.nio.file.Files.newByteChannel(Files.java:407) at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384) at java.nio.file.Files.newInputStream(Files.java:152) at hudson.cli.PrivateKeyProvider.readPemFile(PrivateKeyProvider.java:132) at hudson.cli.PrivateKeyProvider.loadKey(PrivateKeyProvider.java:128) at hudson.cli.PrivateKeyProviderTest.loadKeyBroken(PrivateKeyProviderTest.java:102) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at

[JIRA] (JENKINS-57402) Let diagrams interact with Details table

2019-05-24 Thread heiko.th...@hpi.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 sunblack commented on  JENKINS-57402  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Let diagrams interact with Details table   
 

  
 
 
 
 

 
 In general I prefer a combined view, like it is done by old CppCheck plugin. This shows all warnings in on table, bug highlight rows (green => fixes, red => new, white => not changed). This is a view I really miss here, especially this plugin generates a new warning if only line number changed (e.g. if you have 5 warnings and add or remove a line before these warnings, this plugins shows 5 fixed and 5 new warnings, during old CppCheck plugin count this as not changed). With combined view of all 3 categories (new, fixed, outstanding) it would be much easier to see, which new warnings were only generated because of changed lines. And of course this would allow interacting with the diagrams .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57400) Add option to filter warnings

2019-05-24 Thread heiko.th...@hpi.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 sunblack commented on  JENKINS-57400  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add option to filter warnings   
 

  
 
 
 
 

 
 Oh thanks, searched for this in tool option, and not in general settings (event it makes sense how it is). Nevertheless: filter is using absolute path and not relativ paths, so it is more complex with multiple build server.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit

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


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-57660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit   
 

  
 
 
 
 

 
 I believe the stack trace message is correct.  The refspec is invalid.  It needs to be corrected.If the Amazon Code Commit plugin created that refspec, it needs to be changed to provide a correct refspec.If a person entered that refspec, then they need to change the refspec to use a correct value. I  agree that this is a bug, since the stack trace is much too ugly a way of showing a failure to the user. When I use that invalid refspec in the "Advanced" section of the git repository configuration, saving the form shows the following message:{noformat}java.lang.IllegalArgumentException: Invalid wildcards refs/remotes/*/master/* at org.eclipse.jgit.transport.RefSpec.(RefSpec.java:196) at org.eclipse.jgit.transport.RefSpec.(RefSpec.java:226) at org.eclipse.jgit.lib.DefaultTypedConfigGetter.getRefSpecs(DefaultTypedConfigGetter.java:302) at org.eclipse.jgit.lib.Config.getRefSpecs(Config.java:502) at org.eclipse.jgit.transport.RemoteConfig.(RemoteConfig.java:195) at org.eclipse.jgit.transport.RemoteConfig.getAllRemoteConfigs(RemoteConfig.java:124) at hudson.plugins.git.GitSCM$DescriptorImpl.createRepositoryConfigurations(GitSCM.java:1612)Caused: hudson.plugins.git.GitException: Error creating repositories at hudson.plugins.git.GitSCM$DescriptorImpl.createRepositoryConfigurations(GitSCM.java:1614) at hudson.plugins.git.GitSCM.updateFromUserData(GitSCM.java:264) at hudson.plugins.git.GitSCM.(GitSCM.java:214) at jdk.internal.reflect.GeneratedConstructorAccessor213.newInstance(Unknown Source) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:474) at hudson.model.Descriptor.newInstance(Descriptor.java:596){noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-57661) The incrementals-publisher does not provide a reason for some 400 Bad Request errors

2019-05-24 Thread chris+jenk...@chriskilding.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Kilding commented on  JENKINS-57661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The incrementals-publisher does not provide a reason for some 400 Bad Request errors   
 

  
 
 
 
 

 
 Related discussion on the mailing list: https://groups.google.com/forum/m/#!topic/jenkinsci-dev/dpfPf-qyPzQ    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57661) The incrementals-publisher does not provide a reason for some 400 Bad Request errors

2019-05-24 Thread chris+jenk...@chriskilding.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Kilding created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57661  
 
 
  The incrementals-publisher does not provide a reason for some 400 Bad Request errors   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-05-24 12:34  
 
 
Environment: 
 Server: ci.jenkins.io  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Chris Kilding  
 

  
 
 
 
 

 
 When my plugin deploys to Jenkins Incrementals on ci.jenkins.io, sometimes I get a 400 Bad Request response but with no explanation in the body. This means that I (the plugin author) cannot know what has gone wrong. In addition, the deploy step of the plugin build passes, even though an error has occurred. An example build: https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Faws-secrets-manager-credentials-provider-plugin/detail/support%2Fdocumentation/5/pipeline Note: I filed this under ‘core’ because there was no component for ‘community-functions’.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit

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


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-57660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit   
 

  
 
 
 
 

 
 I believe the stack trace message is correct. The refspec is invalid. It needs to be corrected. If the Amazon Code Commit plugin created that refspec, it needs to be changed to provide a correct refspec. If a person entered that refspec, then they need to change the refspec to use a correct value. I agree that this is a bug, since the stack trace is much too ugly a way of showing a failure to the user.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit

2019-05-24 Thread audrius.meskaus...@meska.info (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Audrius Meskauskas updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57660  
 
 
  Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit   
 

  
 
 
 
 

 
Change By: 
 Audrius Meskauskas  
 

  
 
 
 
 

 
 When using Jenkins inside Amazon EC cloud (and using Amazon Code Commit git provider), the attached stack trace was observed while trying to modify and save the build project settings. The crash is relevant to hudson.plugins.git.GitSCM.The project uses git to fetch the sources. This initially worked, and the project actually even runs the build no problem, but it cannot be modified because of the crash. Strange to see the Git plugin crash on action that itself should not include any interaction with repository.Using Jenkins  2.164.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199593.1558700538000.11403.1558700760239%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit

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


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57660  
 
 
  Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit

2019-05-24 Thread audrius.meskaus...@meska.info (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Audrius Meskauskas updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57660  
 
 
  Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit   
 

  
 
 
 
 

 
Change By: 
 Audrius Meskauskas  
 

  
 
 
 
 

 
 When using Jenkins inside Amazon EC cloud (and using Amazon Code Commit git provider), the attached stack trace was observed while trying to modify and save the build project settings. The crash is relevant to hudson.plugins.git.GitSCM.The project uses git to fetch the sources. This initially worked, and the project actually even runs the build no problem, but it cannot be modified because of the crash. Strange to see the Git plugin crash on action that itself should not include any interaction with repository. Using Jenkins   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit

2019-05-24 Thread audrius.meskaus...@meska.info (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Audrius Meskauskas updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57660  
 
 
  Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit   
 

  
 
 
 
 

 
Change By: 
 Audrius Meskauskas  
 
 
Summary: 
 Git plugin crash on saving the project on Amazon EC while using git  from  for  Amazon  Code Commit  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git from Amazon

2019-05-24 Thread audrius.meskaus...@meska.info (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Audrius Meskauskas created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57660  
 
 
  Git plugin crash on saving the project on Amazon EC while using git from Amazon   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Attachments: 
 trace.txt  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2019-05-24 12:22  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Audrius Meskauskas  
 

  
 
 
 
 

 
 When using Jenkins inside Amazon EC cloud (and using Amazon Code Commit git provider), the attached stack trace was observed while trying to modify and save the build project settings. The crash is relevant to hudson.plugins.git.GitSCM. The project uses git to fetch the sources. This initially worked, and the project actually even runs the build no problem, but it cannot be modified because of the crash. Strange to see the Git plugin crash on action that itself should not include any interaction with repository.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-52697) Logstash plugin: support JCasC

2019-05-24 Thread bochenski.kuba+jenk...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski updated  JENKINS-52697  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Done  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52697  
 
 
  Logstash plugin: support JCasC   
 

  
 
 
 
 

 
Change By: 
 Jakub Bochenski  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192583.1532331323000.11389.1558700100264%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57631) No credentials found for id

2019-05-24 Thread jiaozi362...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 zern king assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57631  
 
 
  No credentials found for id   
 

  
 
 
 
 

 
Change By: 
 zern king  
 
 
Assignee: 
 zern king  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost

2019-05-24 Thread svcj...@keitalbame.net (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nuno Costa edited a comment on  JENKINS-55220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch Pipeline jobs get randomly lost   
 

  
 
 
 
 

 
 This is happening to me today , although is not showing any errors .  The Scan log shows that is not detecting jenkinsfile on a specific branch but the file is there. Other branches with jenkinsfile are been shown in the log.  I had this happening a few weeks ago and without any change from our part, it reenabled the branch.We are using bitbucket.org Team.Using jenkins 2.164.2 and nginx, both as containers.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost

2019-05-24 Thread svcj...@keitalbame.net (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nuno Costa edited a comment on  JENKINS-55220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch Pipeline jobs get randomly lost   
 

  
 
 
 
 

 
 This  is  happening to me today. I had this happening a few weeks ago and without any change from our part, it reenabled the branch.We are using bitbucket.org Team.Using jenkins 2.164.2 and nginx, both as containers.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost

2019-05-24 Thread svcj...@keitalbame.net (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nuno Costa commented on  JENKINS-55220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch Pipeline jobs get randomly lost   
 

  
 
 
 
 

 
 This happening to me today. I had this happening a few weeks ago and without any change from our part, it reenabled the branch. We are using bitbucket.org Team. Using jenkins 2.164.2 and nginx, both as containers.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57425) Implement JMH benchmark in pull request build

2019-05-24 Thread sharmaabhyud...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57425  
 
 
  Implement JMH benchmark in pull request build   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Sprint: 
 GSoC 2019. Coding Phase 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57654) Propose a Maven profile for JMH in Plugin POM

2019-05-24 Thread sharmaabhyud...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57654  
 
 
  Propose a Maven profile for JMH in Plugin POM   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Sprint: 
 GSoC 2019. Coding Phase 1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57653) Extract the JMH framework to standalone lib or to JTH

2019-05-24 Thread sharmaabhyud...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57653  
 
 
  Extract the JMH framework to standalone lib or to JTH   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Sprint: 
 GSoC 2019. Coding Phase 1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57425) Implement JMH benchmark in pull request build

2019-05-24 Thread sharmaabhyud...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57425  
 
 
  Implement JMH benchmark in pull request build   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Sprint: 
 GSoC 2019. Coding Phase  2  1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57424) Parse JMH benchmark Results

2019-05-24 Thread sharmaabhyud...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57424  
 
 
  Parse JMH benchmark Results   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Sprint: 
 GSoC 2019. Coding Phase 1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

  1   2   >