[JIRA] (JENKINS-38484) Using test stability publisher in a Pipeline build will hang

2017-02-04 Thread s...@flanigan.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean Flanigan updated  JENKINS-38484  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Looks like RESOLVED is the state to use when the fix is merged. I should have amended the commit comment to add  

 
[FIXED JENKINS-38484]
 

  to have this done automatically. There's an hpi here if anyone wants to try installing it manually before the 2.0 release: https://jenkins.ci.cloudbees.com/job/plugins/job/test-stability-plugin/9/de.esailors.jenkins$test-stability/  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38484  
 
 
  Using test stability publisher in a Pipeline build will hang   
 

  
 
 
 
 

 
Change By: 
 Sean Flanigan  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 

[JIRA] (JENKINS-38484) Using test stability publisher in a Pipeline build will hang

2017-02-04 Thread s...@flanigan.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean Flanigan commented on  JENKINS-38484  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using test stability publisher in a Pipeline build will hang   
 

  
 
 
 
 

 
 Thanks kutzi. I've merged the pull request (thanks Dominik Bruhn!), but I'm working on a solution for JENKINS-33168, so I won't try to tackle the 2.0 release process just yet unless there's demand. I'm not sure of the process, so I'll leave this unresolved until the release happens. Or should I resolve it now, and close it upon release?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38484) Using test stability publisher in a Pipeline build will hang

2017-02-04 Thread s...@flanigan.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean Flanigan started work on  JENKINS-38484  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Sean Flanigan  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38484) Using test stability publisher in a Pipeline build will hang

2017-02-04 Thread s...@flanigan.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean Flanigan updated  JENKINS-38484  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38484  
 
 
  Using test stability publisher in a Pipeline build will hang   
 

  
 
 
 
 

 
Change By: 
 Sean Flanigan  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38484) Using test stability publisher in a Pipeline build will hang

2017-02-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38484  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using test stability publisher in a Pipeline build will hang   
 

  
 
 
 
 

 
 Code changed in jenkins User: Sean Flanigan Path: .gitignore src/main/java/de/esailors/jenkins/teststability/StabilityTestDataPublisher.java http://jenkins-ci.org/commit/test-stability-plugin/4d56b22043bcd3b187ca5ec95fd572fa2a914703 Log: Merge pull request #2 from theomega/useNonDeprecatedApi JENKINS-38484 Use non-deprecated API (now contributeTestData) https://issues.jenkins-ci.org/browse/JENKINS-38484 Compare: https://github.com/jenkinsci/test-stability-plugin/compare/4e250cb6f79b...4d56b22043bc  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-33168) Junit plugin took 7 hours to complete recording test failures

2017-02-04 Thread s...@flanigan.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean Flanigan started work on  JENKINS-33168  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Sean Flanigan  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-33168) Junit plugin took 7 hours to complete recording test failures

2017-02-04 Thread s...@flanigan.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean Flanigan assigned an issue to Sean Flanigan  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-33168  
 
 
  Junit plugin took 7 hours to complete recording test failures   
 

  
 
 
 
 

 
Change By: 
 Sean Flanigan  
 
 
Assignee: 
 Sean Flanigan  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41729) Using utf-8 letters in property files

2017-02-04 Thread de...@ikedam.jp (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ikedam started work on  JENKINS-41729  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 ikedam  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41729) Using utf-8 letters in property files

2017-02-04 Thread de...@ikedam.jp (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ikedam commented on  JENKINS-41729  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using utf-8 letters in property files   
 

  
 
 
 
 

 
 https://github.com/kohsuke/localizer/pull/13  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41729) Using utf-8 letters in property files

2017-02-04 Thread de...@ikedam.jp (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ikedam created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41729  
 
 
  Using utf-8 letters in property files   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 ikedam  
 
 
Components: 
 core  
 
 
Created: 
 2017/Feb/05 3:56 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 ikedam  
 

  
 
 
 
 

 
 Property files for localization requires to be encoded in ISO-8859-1. It results difficulties in reviewing localizing pull requires such as https://github.com/jenkinsci/maven-plugin/pull/86. It would be nice if property files in source directories can be written in UTF-8 letters. There are two approaches: 
 
Encode property files when compiling. 
 
maven-resources-plugin copies files in the resources directory into the target directory. It doesn't provide a feature to encode property files. 
Though native2ascii-maven-plugin encodes property files, it is provided only as beta for long time. 
 
This might mean encoding property files in compilation time isn't a standard approach. 
  
maven-antrun-plugin can run native2ascii (But it feels strange approach to me). 
This approach would cause problems when testing plugins with "mvn hpi:run". 
 
As property files aren't compiled and read from source directories directly at that time. 

[JIRA] (JENKINS-41121) GitHub Branch Source upgrade can cause a lot of rebuilds

2017-02-04 Thread king...@tuesdaystudios.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kingdon Barrett commented on  JENKINS-41121  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub Branch Source upgrade can cause a lot of rebuilds   
 

  
 
 
 
 

 
 I can tell you that I did not download any plugins by hand, and only used the update center. And still wound up reading this issue. Echo everything that Morgan Goose said. I downgraded some plugins because that appeared to be the recommended path, and I only narrowly avoided deleting my settings after reading the same warnings that you saw about old data. Maybe I caught the upgrade moments before you blacklisted the 2.0.1 update? Not sure. The timing is about right though. Thanks for reposting the ZIP link. I see that you're planning a Monday release, I will wait for that, thanks for providing a clear(ish) path in the issue documentation. FWIW none of the plugins that complained at me about bad dependency versions, actually appeared to be malfunctioning, but I am not using Blue Ocean or advanced GitHub API plugins yet.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40976) NullPointerException in soFinishLogin()

2017-02-04 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-40976  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException in soFinishLogin()   
 

  
 
 
 
 

 
 recampbell Seems somebody has deleted the screenshot from the issue. But yes, without it there is no way to diagnose again  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41341) Standardize form descriptions

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated  JENKINS-41341  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41341  
 
 
  Standardize form descriptions   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 In  Review  Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41341) Standardize form descriptions

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay started work on  JENKINS-41341  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40526) Developer would like to get the logs for a stage or parallel

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40526  
 
 
  Developer would like to get the logs for a stage or parallel   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 

  
 
 
 
 

 
 *Scope** Log toolbar buttons should open or download the log for the selected stage or parallel** Freestyle behaviour remains the same as before this change*  "Show complete log" should only show the log for the step it appears on*  Link to full Pipeline log appears on Artifact tab (looks like an artifact)*Problem*There is no way to get the log for the whole stage or parallel. The full log is not useful as it intermingles logs from different parallel branches.*Design brief*What we'd like to do is change the download/view links for the log so that they only produce logs for the stage/parallel that has been selected. We should then have download/view links for the whole log somewhere else - I am thinking the same has to go above the graph? Need to think about what this looks like when the graph is present and not present.* Full log appears as an artifact *Original request*Will be nice to have "expand all" button to see all steps (view whole log doesn't help due multiple parallels) !image-2016-12-18-12-41-56-651.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

[JIRA] (JENKINS-40526) Developer would like to get the logs for a stage or parallel

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40526  
 
 
  Developer would like to get the logs for a stage or parallel   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Attachment: 
  jenkins-design-language #1 2017-01-23 20-29-39.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41341) Standardize form descriptions

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated  JENKINS-41341  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41341  
 
 
  Standardize form descriptions   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41717) Blue Ocean - Steps section should show full log for given step.

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41717  
 
 
  Blue Ocean - Steps section should show full log for given step.
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Attachment: 
 -jenkins-design-language #1 2017-01-23 20-29-39.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items

2017-02-04 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Liu commented on  JENKINS-41722  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job folder loading performance is worse when folder contains fewer items   
 

  
 
 
 
 

 
 so does that mean Jenkins will always compute the status recursively to the leave of the item? Then this still doesn't explain why I can open the page quick at higher level ("Project" folder), which would contain more leave items. Secondly, I didn't open the matrix job at all. I only opened "Projects" folders contains 34 folders only, and opened "Project-A" folders contains 1 folder and 5 multibranch-job (which has folder at top level). I didn't click to open into multibranch-job to load the matrix branch jobs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-34210) Memory leak in Jenkins frontend when updating executors

2017-02-04 Thread d...@acm.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Darryl Champagne commented on  JENKINS-34210  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Memory leak in Jenkins frontend when updating executors   
 

  
 
 
 
 

 
 I can't guarantee seeing the same issue, but I am regularly finding my Firefox bogging down, and I go check and find a background Jenkins tab with memory up around a gig (900M - 1.2+G). This is viewing a system with 5 slaves (with at least one usually offline), where there are usually 6-8 long running jobs going. I check on it periodically, and sometimes forget an leave a tab on it in the background.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40523) Include Jenkins Project Name in Log message

2017-02-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40523  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Include Jenkins Project Name in Log message   
 

  
 
 
 
 

 
 Code changed in jenkins User: Boguslaw Klimas Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/FilePathWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/AbstractJobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/JobWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/jobs/WorkflowJobWrapper.java http://jenkins-ci.org/commit/git-parameter-plugin/7fb1ef45346cd6fa68a8f6c46529d6b9723c4ad8 Log: Merge pull request #44 from jenkinsci/feature/JENKINS-40523 Include Jenkins Project Name in Log message Compare: https://github.com/jenkinsci/git-parameter-plugin/compare/d4972a116951...7fb1ef45346c  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40899) Transitive plugin dependencies not correctly checked when using snapshots

2017-02-04 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz edited a comment on  JENKINS-40899  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Transitive plugin dependencies not correctly checked when using snapshots
 

  
 
 
 
 

 
 The issue is not in core but maven-hpi-plugin and it is fixed  by  in 1.121.It can be closed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40899) Transitive plugin dependencies not correctly checked when using snapshots

2017-02-04 Thread amu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Muñiz commented on  JENKINS-40899  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Transitive plugin dependencies not correctly checked when using snapshots
 

  
 
 
 
 

 
 The issue is not in core but maven-hpi-plugin and it is fixed by in 1.121. It can be closed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27745) A `device_id` and `device_name` should be provided to allow private IP.

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-27745  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: A `device_id` and `device_name` should be provided to allow private IP.   
 

  
 
 
 
 

 
 Or this? http://stackoverflow.com/questions/10296681/is-there-an-oauth-2-0-provider-implementation-in-java-not-oauth-client  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27745) A `device_id` and `device_name` should be provided to allow private IP.

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell edited a comment on  JENKINS-27745  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: A `device_id` and `device_name` should be provided to allow private IP.   
 

  
 
 
 
 

 
 Or this? http://stackoverflow.com/questions/ 10296681 24736168 / is error - there invalid - an request - oauth device - 2 id - 0 and - provider device - implementation name - in are - java required - not for - oauth private - client ip  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36706) When OAuth session expires, an ugly NPE is shown in Jenkins

2017-02-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-36706  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When OAuth session expires, an ugly NPE is shown in Jenkins   
 

  
 
 
 
 

 
 Code changed in jenkins User: Ryan Campbell Path: src/main/java/org/jenkinsci/plugins/googlelogin/GoogleOAuth2SecurityRealm.java src/main/java/org/jenkinsci/plugins/googlelogin/OAuthSession.java http://jenkins-ci.org/commit/google-login-plugin/3d999a0a3ab79f3b0715c7cb293a4a9e58a7881f Log: JENKINS-36706 Handle session timeout better  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36706) When OAuth session expires, an ugly NPE is shown in Jenkins

2017-02-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-36706  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When OAuth session expires, an ugly NPE is shown in Jenkins   
 

  
 
 
 
 

 
 Code changed in jenkins User: Ryan Campbell Path: src/main/java/org/jenkinsci/plugins/googlelogin/GoogleOAuth2SecurityRealm.java src/main/java/org/jenkinsci/plugins/googlelogin/OAuthSession.java http://jenkins-ci.org/commit/google-login-plugin/36670d149a2c5748c61f087a2cd035108461bc5c Log: JENKINS-36706: Handle session timeout better  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27467) Also authenticate users using Jenkins built-in database (aka "On the side mode")

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell edited a comment on  JENKINS-27467  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Also authenticate users using Jenkins built-in database (aka "On the side mode")   
 

  
 
 
 
 

 
 OK, so in this case, it sounds like you want Google Apps to be your primary source of truth but then have the built-in database available for users who are not in Google Apps, right?So perhaps the right way to do this is to have add an option to the Google Oauth Security Realm which allows you to "Also authenticate users using the Jenkins User database". In this case, the login screen would show a username password login with a "Login with Google" button below it.This is *not* how the "on the side" feature works in the old OpenID plugin. In that case, the user must explicitly configure their account to allow access using OpenID. But that doesn't seem like what you want in the use-case you are describing. You want someone known as "u...@mygoogledomain.com" to be able to authenticate as that identity on Jenkins using their Google session without having to take special steps prior. And I imagine you want their Jenkins account to automatically be created if it does not exist. Finally, I think you want them to lose access to Jenkins if you disable their account in your Google Apps domain.So this is not exactly like the "On the side" feature. And what is especially important is that Google Apps users lose access to Jenkins once you decommission them in Google Apps.The more I think about it, this is going to require a bit of work and especially thought to make sure we don't accidentally prevent logins somehow or (even worse) open up some kind of security hole.Given the risks, the work to get this right and the relatively low votes on this issue, I think its safe to say we have no plans in the foreseeable future to add this feature. This may change if someone steps up to do the work or the demand increases.I will say that if someone actually volunteers to add this change, I think it may be possible by creating another plugin which somehow wraps this one.  This would be much lower risk than adding the feature to this plugin.  If someone wants this enough to do the investigation to tell me what they need, I can make changes to support that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

  

[JIRA] (JENKINS-27467) Also authenticate users using Jenkins built-in database (aka "On the side mode")

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-27467  
 
 
  Also authenticate users using Jenkins built-in database (aka "On the side mode")   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Summary: 
 Also authenticate users using Jenkins built-in database  (aka "On the side mode")  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27467) Also authenticate users using Jenkins built-in database

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-27467  
 
 
  Also authenticate users using Jenkins built-in database   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Summary: 
 Add an "On the side" mode similar to the OpenID plugin Also authenticate users using Jenkins built-in database  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27467) Add an "On the side" mode similar to the OpenID plugin

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-27467  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add an "On the side" mode similar to the OpenID plugin   
 

  
 
 
 
 

 
 OK, so in this case, it sounds like you want Google Apps to be your primary source of truth but then have the built-in database available for users who are not in Google Apps, right? So perhaps the right way to do this is to have add an option to the Google Oauth Security Realm which allows you to "Also authenticate users using the Jenkins User database". In this case, the login screen would show a username password login with a "Login with Google" button below it. This is not how the "on the side" feature works in the old OpenID plugin. In that case, the user must explicitly configure their account to allow access using OpenID. But that doesn't seem like what you want in the use-case you are describing. You want someone known as "u...@mygoogledomain.com" to be able to authenticate as that identity on Jenkins using their Google session without having to take special steps prior. And I imagine you want their Jenkins account to automatically be created if it does not exist. Finally, I think you want them to lose access to Jenkins if you disable their account in your Google Apps domain. So this is not exactly like the "On the side" feature.  And what is especially important is that Google Apps users lose access to Jenkins once you decommission them in Google Apps. The more I think about it, this is going to require a bit of work and especially thought to make sure we don't accidentally prevent logins somehow or (even worse) open up some kind of security hole. Given the risks, the work to get this right and the relatively low votes on this issue, I think its safe to say we have no plans in the foreseeable future to add this feature. This may change if someone steps up to do the work or the demand increases. I will say that if someone actually volunteers to add this change, I think it may be possible by creating another plugin which somehow wraps this one. If someone wants this enough to do the investigation to tell me what they need, I can make changes to support that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

[JIRA] (JENKINS-27467) Add an "On the side" mode similar to the OpenID plugin

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-27467  
 
 
  Add an "On the side" mode similar to the OpenID plugin   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27745) A `device_id` and `device_name` should be provided to allow private IP.

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-27745  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: A `device_id` and `device_name` should be provided to allow private IP.   
 

  
 
 
 
 

 
 Uh, OK. Anyone have a link to the docs for these? I guess we could just add them to the form and pass them through.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-28010) Use Google Apps group for Authorization

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell edited a comment on  JENKINS-28010  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use Google Apps group for Authorization   
 

  
 
 
 
 

 
 As to the first commenter, you are doing something wrong. Just enter a valid Google apps domain and you will get a 401 if you select a user who isn't a member of that domain.  Please open a seperate bug report with steps to reproduce if that doesn't work.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-28010) Use Google Apps group for Authorization

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-28010  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use Google Apps group for Authorization   
 

  
 
 
 
 

 
 As to the first commenter, you are doing something wrong. Just enter a valid Google apps domain and you will get a 401 if you select a user who isn't a member of that domain.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-28010) Use Google Apps group for Authorization

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell edited a comment on  JENKINS-28010  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use Google Apps group for Authorization   
 

  
 
 
 
 

 
 Yeah, I've thought about this. I guess this would be per-domain. Like "cloudbees.com:engineering" for a group called "engineering" in the cloudbees.com domain. This would just be a list of  principle's  principals  for the user which you could then map into an Authorization realm like matrix-auth or cloudbees RBAC.Perhaps this can be requested as a part of the oauth dance or as an optional followup API request.If you want this to happen faster, please confirm the above information and provide me with links to which API's I should use. Or provide a patch! #lazyoss  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-28152) Better error messages

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-28152  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Better error messages   
 

  
 
 
 
 

 
 I think the current experience is correct. Jenkins is broken because your environment is broken. Perhaps the generic Jenkins error page could be improved, but I think even that directs users in the right direction.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-28152) Better error messages

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-28152  
 
 
  Better error messages   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35124) Allow limiting by domain without google apps

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is present in 1.3  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-35124  
 
 
  Allow limiting by domain without google apps   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40976) NullPointerException in soFinishLogin()

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell closed an issue as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please provide steps to reproduce with expected and actual experience.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40976  
 
 
  NullPointerException in soFinishLogin()   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-41728) Unexpected behavior when TestReport or TestResults is not available in a specific build of a Jenkins job

2017-02-04 Thread sharathshashid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sharath Shashidhar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41728  
 
 
  Unexpected behavior when TestReport or TestResults is not available in a specific build of a Jenkins job   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Karl-Heinz Marbaise  
 
 
Components: 
 java-client-api  
 
 
Created: 
 2017/Feb/04 6:55 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Sharath Shashidhar  
 

  
 
 
 
 

 
 Unexpected behavior when TestReport or TestResults is not available in a specific build of a Jenkins job Here's what i am trying to do: I want to print the passCount, failCount and skipCount for the last 5 builds for a specific job. There are some jobs in our system that has failed even before the test starts hence the testReport and results are not available. I would be able to do a null check if they are not available in the build. Here' what i am doing: If(specificBuild.details().getTestResult() != null) { //capture test pass, fails and skip count } For some reason this does not work as expected. Please fix. Also, please let me know if i am missing anything. Thanks in advance.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] (JENKINS-28010) Use Google Apps group for Authorization

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-28010  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use Google Apps group for Authorization   
 

  
 
 
 
 

 
 Yeah, I've thought about this.  I guess this would be per-domain. Like "cloudbees.com:engineering" for a group called "engineering" in the cloudbees.com domain.  This would just be a list of principle's for the user which you could then map into an Authorization realm like matrix-auth or cloudbees RBAC. Perhaps this can be requested as a part of the oauth dance or as an optional followup API request. If you want this to happen faster, please confirm the above information and provide me with links to which API's I should use. Or provide a patch! #lazyoss  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-32536) Allow for multiple domains

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Added in 1.3 thanks to https://github.com/gkrat https://github.com/jenkinsci/google-login-plugin/commit/6fea3b29a0c35301ed16024e4d2f07d2a8ab402b  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-32536  
 
 
  Allow for multiple domains   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-31362) Google authentication with Swarm plugin

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This plugin doesn't authenticate you with your google username & password. Just set an API key on your user for this use-case. Please google Jenkins API key.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-31362  
 
 
  Google authentication with Swarm plugin   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37607) Get user name from google?

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37607  
 
 
  Get user name from google?   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36706) When OAuth session expires, an ugly NPE is shown in Jenkins

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-36706  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When OAuth session expires, an ugly NPE is shown in Jenkins   
 

  
 
 
 
 

 
 OK, I was able to reproduce this by restarting Jenkins instead of step 5 above. And you were nice enough to tell me exactly where the bug was, so thanks for that. The full stack trace: 

 

javax.servlet.ServletException: java.lang.NullPointerException
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
	at 

[JIRA] (JENKINS-36706) When OAuth session expires, an ugly NPE is shown in Jenkins

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-36706  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When OAuth session expires, an ugly NPE is shown in Jenkins   
 

  
 
 
 
 

 
 What would make this bug report more useful: 
 
Cut and paste the entire error message. Your screen shot cuts off the most important part and I can't cut this into my editor to find the relevant lines. 
Provide actual steps to reproduce. I have no idea what you mean by "oauth session expires" I'm just guessing, but I think this is? 
 
 
Login to google with at least two accounts 
Setup the security realm with a valid oauth token and secret 
Attempt to login to Jenkins using the login link in the upper right hand side 
You are presented with a list of accounts to use for login 
Wait for some long period? 
Finally select the account you want to login with 
 Is that what you mean?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups 

[JIRA] (JENKINS-33286) logging-out with google-login-plugin is not work

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in 1.3  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-33286  
 
 
  logging-out with google-login-plugin is not work   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37749) Client-id and Secret gets overwritten by username and password hash

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in 1.3  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37749  
 
 
  Client-id and Secret gets overwritten by username and password hash
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36483) Unable to login with google-login plugin with 401 error

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell edited a comment on  JENKINS-36483  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to login with google-login plugin with 401 error   
 

  
 
 
 
 

 
 Well, Jenkins is returning a 401 because the domain of Google account selected by the user doesn't match the domain you have provided. However, I think you have a space in the Google Apps Domain field.Or at least I've reproduced this problem by adding trailing spaces.   I'll just clean that input up.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36483) Unable to login with google-login plugin with 401 error

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 resolved toward 1.4  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36483  
 
 
  Unable to login with google-login plugin with 401 error   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36483) Unable to login with google-login plugin with 401 error

2017-02-04 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-36483  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to login with google-login plugin with 401 error   
 

  
 
 
 
 

 
 Code changed in jenkins User: Ryan Campbell Path: src/main/java/org/jenkinsci/plugins/googlelogin/GoogleOAuth2SecurityRealm.java src/test/java/org/jenkinsci/plugins/googlelogin/GoogleOAuth2SecurityRealmTest.java http://jenkins-ci.org/commit/google-login-plugin/bd9d82204ef28f995331102ffd3cb20e41554495 Log: JENKINS-36483 Removes spaces from the Domain  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36483) Unable to login with google-login plugin with 401 error

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell edited a comment on  JENKINS-36483  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to login with google-login plugin with 401 error   
 

  
 
 
 
 

 
 I think you have a space in the Google Apps Domain field.I'll just clean that input up.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36483) Unable to login with google-login plugin with 401 error

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-36483  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to login with google-login plugin with 401 error   
 

  
 
 
 
 

 
 I think you have a space in the Google Apps Domain field. I'll just clean that input up.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27117) google login plugin not working

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell edited a comment on  JENKINS-27117  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: google login plugin not working   
 

  
 
 
 
 

 
 I'm fairly certain that this is some kind of configuration problem. I tried to reproduce this by changing my Jenkins location to something invalid, but this gave me a reasonable error message from Google, not this NPE. It seems like Google is returning an error code, but that Google's own oauth client isn't able to parse this correctly. Maybe some weird servlet api issue getting in the way. For the record, I don't think this has anything to do with your Google apps domain configuration.To reproduce this effectively, I'm going to need to know the following information from someone experiencing the problem:* Jenkins Location URL* The "Authorized redirect URIs" from your google "Client ID for Web application" in the Google oauth console. * Servlet container, ie, Tomcat or just the default jetty or what?   Ideally this plugin would provide better input validation or diagnostics in the logs to help you determine the problem.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27117) google login plugin not working

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell edited a comment on  JENKINS-27117  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: google login plugin not working   
 

  
 
 
 
 

 
 I'm fairly certain that this is some kind of configuration problem. I tried to reproduce this by changing my Jenkins location to something invalid, but this gave me a reasonable error message from Google, not this NPE.For the record, I don't think this has anything to do with your Google apps domain configuration.To reproduce this effectively, I'm going to need to know the following information from someone experiencing the problem:* Jenkins Location URL* The "Authorized redirect URIs" from your google "Client ID for Web application" in the Google oauth console. Ideally this plugin would provide better input validation or diagnostics in the logs to help you determine the problem.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27117) google login plugin not working

2017-02-04 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I'm fairly certain that this is some kind of configuration problem. I tried to reproduce this by changing my Jenkins location to something invalid, but this gave me a reasonable error message from Google, not this NPE. For the record, I don't think this has anything to do with your Google apps domain configuration. To reproduce this effectively, I'm going to need to know the following information from someone experiencing the problem: 
 
Jenkins Location URL 
The "Authorized redirect URIs" from your google "Client ID for Web application" in the Google oauth console. 
  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-27117  
 
 
  google login plugin not working   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-41721) NodeJS Plugin fails when using the pipeline

2017-02-04 Thread nfalc...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41721  
 
 
  NodeJS Plugin fails when using the pipeline   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35768) Developer can filter the activity list to a specific branch

2017-02-04 Thread kamikaze.is.waiting....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Korsak edited a comment on  JENKINS-35768  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Developer can filter the activity list to a specific branch   
 

  
 
 
 
 

 
 Emmm... this kinda may take more user actions than just clicking a "History" tab in particular branch/build view. Are there any plans to get something similar to pipeline view in classic UI? When user is able to see all build progresses for particular branch at once.  (just asking)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35768) Developer can filter the activity list to a specific branch

2017-02-04 Thread kamikaze.is.waiting....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Korsak commented on  JENKINS-35768  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Developer can filter the activity list to a specific branch   
 

  
 
 
 
 

 
 Emmm... this kinda may take more user actions than just clicking a "History" tab in particular branch/build view. Are there any plans to get something similar to pipeline view in classic UI? When user is able to see all build progresses for particular branch at once.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41727) Upgrading/downgrading Jenkins needs to invalidate update site cache

2017-02-04 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41727  
 
 
  Upgrading/downgrading Jenkins needs to invalidate update site cache   
 

  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Project: 
 Infrastructure Jenkins  
 
 
Key: 
 INFRA JENKINS - 1055 41727  
 
 
Workflow: 
 classic default workflow JNJira + In-Review  
 
 
Component/s: 
 core  
 
 
Component/s: 
 core  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this 

[JIRA] (JENKINS-41725) Provisioned agent Kubernetes Pod Template failed to launch

2017-02-04 Thread ioca...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Canellos commented on  JENKINS-41725  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Provisioned agent Kubernetes Pod Template failed to launch   
 

  
 
 
 
 

 
 For people that don't know what `dockerTemplate` and `mavenTemplate`are They are shortcuts to podTemplate for maven and docker used in the fabric8-pipeline-library. I think that this error is caused because the required templates are not found or are not in a valid state.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41662) Proceed button fails

2017-02-04 Thread kamikaze.is.waiting....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Korsak commented on  JENKINS-41662  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Proceed button fails   
 

  
 
 
 
 

 
 Sure, will do on monday )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41725) Provisioned agent Kubernetes Pod Template failed to launch

2017-02-04 Thread ioca...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Canellos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41725  
 
 
  Provisioned agent Kubernetes Pod Template failed to launch   
 

  
 
 
 
 

 
Change By: 
 Ioannis Canellos  
 
 
Component/s: 
 kubernetes-plugin  
 
 
Component/s: 
 kubernetes-pipeline-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41726) form auth in http-request plugin getting HTTP/1.1 408 Request Timeout response

2017-02-04 Thread lichao....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roger Lei created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41726  
 
 
  form auth in http-request plugin getting HTTP/1.1 408 Request Timeout response   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Janario Oliveira  
 
 
Attachments: 
 another-try.jpg, build_console_output.jpg, global_auth.jpg, job_config.jpg  
 
 
Components: 
 http-request-plugin  
 
 
Created: 
 2017/Feb/04 4:13 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Roger Lei  
 

  
 
 
 
 

 
 I have a webapp deployed in my local tomcat configged with form auth and I'm trying to send a request using the http request plugin on Jenkins. I've added Form Authentication in the global configuration.   Now I setup an job to send a request to get some info as response.   But I keep getting 408 code as response.   I had another try without the "j_security_check" suffix. The job can pass and get an 200 code, but the request wasn't successfully submitted and it's return a login page as response.   Please kindly check and advice,  Many thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[JIRA] (JENKINS-41600) Parallel step running forever if too much console output is logged

2017-02-04 Thread jenk...@philgrayson.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Phil Grayson commented on  JENKINS-41600  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parallel step running forever if too much console output is logged   
 

  
 
 
 
 

 
 I've also seen this type of issue. A script that outputs large amounts of text at once causes a job to loop forever and continues to grow the job's log file on the Jenkins master. I've not seen it related to Parallel though. Are you able to reproduce this with a single bat command?  I've done some debugging and seen this timeout being tripped. Specifically this is causing the timeout (called here). That is copying bytes from the script's output on the slave back to Jenkins master. If it takes longer than 10 seconds for the script's output to be copied, the timeout is triggered and prevents the read byte offset from being updated. Therefore Jenkins master will keep trying to read from the same offset and triggering the timeout. Ideally there would be a way to tell how many bytes have been written in this OutputStream.write call and move the timeout handling so that the `newLocation` variable will accurately say how much script output has really been read. This comment hints that the timeout should be handled in the Remoting library. As a work around, I was able to prevent the bug from affecting my specific test by increasing the timeout to 60 seconds. It's not a suitable general fix though.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-41413) no downloads for Windows

2017-02-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated  JENKINS-41413  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This has been fixed for 2.43, 2.44.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41413  
 
 
  no downloads for Windows   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41711) Prevent installation of plugins with unresolvable dependencies

2017-02-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-41711  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prevent installation of plugins with unresolvable dependencies   
 

  
 
 
 
 

 
 Alternatively, this could be something the update center could do – only offer plugins with satisfied dependencies. This would also prevent this problem on past releases of Jenkins.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41711) Prevent installation of plugins with unresolvable dependencies

2017-02-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-41711  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prevent installation of plugins with unresolvable dependencies   
 

  
 
 
 
 

 
 … or just hide plugins with broken dependencies. FWIW the setup wizard checks that the offered plugin is compatible with the current release and only offers then – needs to ensure dependencies are satisfied as well at the same location. https://github.com/jenkinsci/jenkins/blob/c4dcffaf4d08f087ed521682349de194a4fac1b7/core/src/main/java/jenkins/install/SetupWizard.java#L420  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41695) Recording fingerprints fails on symbolic links when archiving artifacts

2017-02-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 

Jenkins 1.609.3 LTS 
 Please reopen if this occurs on a recent release. This baseline is almost two years old. (I'm not trying to be rude here by resolving immediately, just spent way too much time trying to reproduce issues that have long been fixed.)  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41695  
 
 
  Recording fingerprints fails on symbolic links when archiving artifacts   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
   

[JIRA] (JENKINS-41696) Recording fingerprints ignores the excludes when archiving artifacts

2017-02-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please reopen if this occurs on a recent release. This baseline is almost two years old. (I'm not trying to be rude here by resolving immediately, just spent way too much time trying to reproduce issues that have long been fixed.)  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41696  
 
 
  Recording fingerprints ignores the excludes when archiving artifacts   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 

[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items

2017-02-04 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 There's no bug here. It's more expensive to compute the status of matrix jobs as each combination is considered an individual build and must be loaded.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41722  
 
 
  Job folder loading performance is worse when folder contains fewer items   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-41725) Provisioned agent Kubernetes Pod Template failed to launch

2017-02-04 Thread kurren...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anton Hughes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41725  
 
 
  Provisioned agent Kubernetes Pod Template failed to launch   
 

  
 
 
 
 

 
Change By: 
 Anton Hughes  
 

  
 
 
 
 

 
 When attempting to run the following Jenkinsfile, Jenkins errors. No slave pod is created. {code:java}dockerTemplate { //This will ensure that docker socket is mounted and related env vars set.mavenTemplate(label: 'maven-and-docker') { //This will ensure maven container is available and properlly configuredpodTemplate(label: buildLabel, containers:[containerTemplate(name: 'jhipster', image: 'jhipster/jhipster', privileged: true)]) {node (buildLabel) {checkout scm{code}h2. Version Info * Kubernetes plugin: 0.10 0.10-SNAPSHOT (private-70e60d4e-jamesrawlings) * OpenShift Pipeline Jenkins Plugin:  1.0.4-SNAPSHOT (private-e437d877-jamesrawlings) * OpenShift Master: v1.4.1+3f9807a  * Kubernetes Master: v1.4.0+776c994 See attached log.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this 

[JIRA] (JENKINS-41725) Provisioned agent Kubernetes Pod Template failed to launch

2017-02-04 Thread kurren...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anton Hughes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41725  
 
 
  Provisioned agent Kubernetes Pod Template failed to launch   
 

  
 
 
 
 

 
Change By: 
 Anton Hughes  
 

  
 
 
 
 

 
  When attempting to run the following Jenkinsfile, Jenkins errors. No slave pod is created. {code:java}dockerTemplate { //This will ensure that docker socket is mounted and related env vars set.mavenTemplate(label: 'maven-and-docker') { //This will ensure maven container is available and properlly configuredpodTemplate(label: buildLabel, containers:[containerTemplate(name: 'jhipster', image: 'jhipster/jhipster', privileged: true)]) {node (buildLabel) {checkout scm{code} h2. Version Info * Kubernetes plugin: 0.10 0.10-SNAPSHOT (private-70e60d4e-jamesrawlings) * OpenShift Pipeline Jenkins Plugin:  1.0.4-SNAPSHOT (private-e437d877-jamesrawlings) See attached log.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins 

[JIRA] (JENKINS-41568) Failing to provision new agents despite not being at maxumum

2017-02-04 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy commented on  JENKINS-41568  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failing to provision new agents despite not being at maxumum   
 

  
 
 
 
 

 
 I believe they are related, yes  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41725) Provisioned agent Kubernetes Pod Template failed to launch

2017-02-04 Thread kurren...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anton Hughes created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41725  
 
 
  Provisioned agent Kubernetes Pod Template failed to launch   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ioannis Canellos  
 
 
Attachments: 
 jenkins.log  
 
 
Components: 
 kubernetes-pipeline-plugin  
 
 
Created: 
 2017/Feb/04 1:52 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Anton Hughes  
 

  
 
 
 
 

 
 When attempting to run the following Jenkinsfile, Jenkins errors. No slave pod is created.  

 

dockerTemplate { //This will ensure that docker socket is mounted and related env vars set.
mavenTemplate(label: 'maven-and-docker') { //This will ensure maven container is available and properlly configured
podTemplate(label: buildLabel, containers:[
containerTemplate(name: 'jhipster', image: 'jhipster/jhipster', privileged: true)
]) {
node (buildLabel) {

checkout scm
 

 See attached log.  
 

  
 
 
 
 

 
 
 

 
  

[JIRA] (JENKINS-41710) Annotate test results with a test run name

2017-02-04 Thread thors...@meinl.bnv-bamberg.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thorsten Meinl commented on  JENKINS-41710  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Annotate test results with a test run name   
 

  
 
 
 
 

 
 This is a very good idea and makes replacing matrix jobs with (parallel) pipelines easier.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41724) Cannot pull from bitbucket

2017-02-04 Thread dimakie...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmytro Zhernosiekov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41724  
 
 
  Cannot pull from bitbucket   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2017/Feb/04 12:10 PM  
 
 
Environment: 
 CentOs 7.1 + Java 1.8 + Jenkins  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Dmytro Zhernosiekov  
 

  
 
 
 
 

 
 Hi, I'm upload machine ssh key in bitbucket. Create Job in Jenkins to pull repo. In job I could see that it connect to bitbucket did fetch, but cannot pull with error that cannot checkout to branch. Could you help me?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 
   

[JIRA] (JENKINS-41717) Blue Ocean - Steps section should show full log for given step.

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Thorsten Scherler  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41717  
 
 
  Blue Ocean - Steps section should show full log for given step.
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Major Minor  
 
 
Sprint: 
 iapetus  
 
 
Assignee: 
 Thorsten Scherler  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41717) Blue Ocean - Steps section should show full log for given step.

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-41717  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean - Steps section should show full log for given step.
 

  
 
 
 
 

 
 Actually we can handle this one sooner and seperately   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41717) Blue Ocean - Steps section should show full log for given step.

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay edited a comment on  JENKINS-41717  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean - Steps section should show full log for given step.
 

  
 
 
 
 

 
 Actually we can handle this one sooner and  seperately  separately
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41717) Blue Ocean - Steps section should show full log for given step.

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41717  
 
 
  Blue Ocean - Steps section should show full log for given step.
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Resolution: 
 Duplicate  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41717) Blue Ocean - Steps section should show full log for given step.

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41717  
 
 
  Blue Ocean - Steps section should show full log for given step.
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 

  
 
 
 
 

 
 *Scope** Show complete log button should only show the complete log for that step*Original request* "Show complete log" button will take me to plain text and it really hard to parse the information when pipeline steps are executed in parallel. Blue Ocean makes it easy to see steps with the UI diagram but truncating the log makes it impossible to find the error inside of blue ocean UI. Going into pain text requires downloading the logs and parsing the information by cat  | grep "\[stage name\]" this makes it really difficult to find issues.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For 

[JIRA] (JENKINS-41716) Upgrade Breaks NodeJS Tool Installations

2017-02-04 Thread nfalc...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco commented on  JENKINS-41716  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Upgrade Breaks NodeJS Tool Installations   
 

  
 
 
 
 

 
 I think this is a duplicate of JENKINS-41535 , update to 1.0.1 to resolve tools definition disappear in reboot/upgrade. Can you confirm the issue also with 1.0.1?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41717) Blue Ocean - Steps section should show full log for given step.

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-41717  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean - Steps section should show full log for given step.
 

  
 
 
 
 

 
 mishal shah we want to do it soon so its pretty high atm. Just waiting on a backend change   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40526) Developer would like to get the logs for a stage or parallel

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40526  
 
 
  Developer would like to get the logs for a stage or parallel   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 post-release panthalassa  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41717) Blue Ocean - Steps section should show full log for given step.

2017-02-04 Thread shahmis...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 mishal shah commented on  JENKINS-41717  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean - Steps section should show full log for given step.
 

  
 
 
 
 

 
 James Dumay Is it possible to increases the priority of JENKINS-40526? Thanks!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41545) Empty states

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay started work on  JENKINS-41545  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40979  
 
 
  Developer would like to see why the Pipeline has been triggered   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41541) Support Agent and environment config at a stage level (currently is only global)

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41541  
 
 
  Support Agent and environment config at a stage level (currently is only global)   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41638) "Open Blue Ocean" button doesn't work unless the server URL is set correctly

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41638  
 
 
  "Open Blue Ocean" button doesn't work unless the server URL is set correctly   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41433) Add new API for "permissions"

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41433  
 
 
  Add new API for "permissions"   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41566) Reconnect ping request goes crazy

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41566  
 
 
  Reconnect ping request goes crazy   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38982) User would like to have a fast smart search to find jobs from the dashboard

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38982  
 
 
  User would like to have a fast smart search to find jobs from the dashboard   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 atlantic, frank, christmas , panthalassa  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38751) Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38751  
 
 
  Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Critical Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41096) Only show admin link in header if the user has privileges

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41096  
 
 
  Only show admin link in header if the user has privileges
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38982) User would like to have a fast smart search to find jobs from the dashboard

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38982  
 
 
  User would like to have a fast smart search to find jobs from the dashboard   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 atlantic, frank, christmas , iapetus  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41663) UI tends to not update

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41663  
 
 
  UI tends to not update   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 panthalassa iapetus  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38767) Header link on branch name should be moved to pipeline name

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38767  
 
 
  Header link on branch name should be moved to pipeline name   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 panthalassa iapetus  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39705) Remove Show More button instead of disabling it

2017-02-04 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39705  
 
 
  Remove Show More button instead of disabling it   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 arctic, frank,  release candidate  iapetus  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


  1   2   >