[JIRA] (JENKINS-40522) "Started by" link on downstream jobs does not work correctly

2016-12-16 Thread nurupo.contributi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 nurupo nurupo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40522  
 
 
  "Started by" link on downstream jobs does not work correctly   
 

  
 
 
 
 

 
Change By: 
 nurupo nurupo  
 

  
 
 
 
 

 
 This seems to affect only downstream  projects  jobs  (downstreams, downstreams of downstreams, etc.).In correct.png, the "Started by GitHub push by iphydf" text links to https:///job/libtoxcore-toktok_src/43/pollingLog, which is the correct URL.In incorrect.png, the "Started by GitHub push by iphydf" text links to https:///pollingLog, which is incorrect URL and it returns 404. It should link to  https:///job/libtoxcore-toktok_src/43/pollingLog instead, but it doesn't.Job shown in incorrect.png is a downstream of the job shown in correct.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 

[JIRA] (JENKINS-40522) "Started by" link on downstream jobs does not work correctly

2016-12-16 Thread nurupo.contributi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 nurupo nurupo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40522  
 
 
  "Started by" link on downstream jobs does not work correctly   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kirill Merkushev  
 
 
Attachments: 
 correct.png, incorrect.png  
 
 
Components: 
 github-plugin  
 
 
Created: 
 2016/Dec/17 7:43 AM  
 
 
Environment: 
 Jenkins 2.19.4, GitHub plugin 1.25.0, Debian Linux  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 nurupo nurupo  
 

  
 
 
 
 

 
 This seems to affect only downstream projects (downstreams, downstreams of downstreams, etc.). In correct.png, the "Started by GitHub push by iphydf" text links to https:///job/libtoxcore-toktok_src/43/pollingLog, which is the correct URL. In incorrect.png, the "Started by GitHub push by iphydf" text links to https:///pollingLog, which is incorrect URL and it returns 404. It should link to https:///job/libtoxcore-toktok_src/43/pollingLog instead, but it doesn't. Job shown in incorrect.png is a downstream of the job shown in correct.png.  
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-26522) Annotated block/stage status

2016-12-16 Thread w...@anomalizer.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arvind Jayaprakash commented on  JENKINS-26522  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Annotated block/stage status   
 

  
 
 
 
 

 
 The stageStatus directive as shown above looks good for manual overrides. We will also have to get existing plugins to start setting this as opposed to the build status. For example, junit plugin on test failure, findbugs on exceeding violation thresholds etc. etc.  
 

  
 
 
 
 

 
 
 

 
 
 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-38126) Credentials dropdown empty on git scm

2016-12-16 Thread gun...@grodotzki.co.za (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gunter Grodotzki commented on  JENKINS-38126  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Credentials dropdown empty on git scm   
 

  
 
 
 
 

 
 I upgraded: 
 
jenkins: 2.19.4 
git-plugin: 3.0.1 
 Problem still remaining, similar to what Kristofer Hansson Aspman is describing. Unfortunately I have yet again to downgrade the git-plugin manually to 2.5.3. Obviously a error is happening, can someone in this thread be so kind to at least help with debugging? E.g. there surely must be somewhere a error log happening?  
 

  
 
 
 
 

 
 
 

 
 
 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-40175) Masked Passwords are shown while rebuild.

2016-12-16 Thread mwarken...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Warkentin commented on  JENKINS-40175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Masked Passwords are shown while rebuild.   
 

  
 
 
 
 

 
 We're having the same 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-40399) Release version of plugin not installable

2016-12-16 Thread hyper...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Reinhardt updated  JENKINS-40399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40399  
 
 
  Release version of plugin not installable   
 

  
 
 
 
 

 
Change By: 
 Martin Reinhardt  
 
 
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-40399) Release version of plugin not installable

2016-12-16 Thread hyper...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Reinhardt started work on  JENKINS-40399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Martin Reinhardt  
 
 
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-40399) Release version of plugin not installable

2016-12-16 Thread hyper...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Reinhardt updated  JENKINS-40399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40399  
 
 
  Release version of plugin not installable   
 

  
 
 
 
 

 
Change By: 
 Martin Reinhardt  
 
 
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-40399) Release version of plugin not installable

2016-12-16 Thread hyper...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Reinhardt commented on  JENKINS-40399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Release version of plugin not installable   
 

  
 
 
 
 

 
 solved with the latest 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-10239) org.tmatesoft.svn.core.SVNErrorMessage: svn: Operation cancelled from the SVN plugin

2016-12-16 Thread teknop...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 paul hinds commented on  JENKINS-10239  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: org.tmatesoft.svn.core.SVNErrorMessage: svn: Operation cancelled from the SVN plugin   
 

  
 
 
 
 

 
 Christian any change you could elaborate on your work around, I tried using the svn cli tool for a checkin but this did not help.  
 

  
 
 
 
 

 
 
 

 
 
 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-37182) Can't connect to a working svn server with username and password

2016-12-16 Thread teknop...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 paul hinds commented on  JENKINS-37182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't connect to a working svn server with username and password   
 

  
 
 
 
 

 
 might be the same as https://issues.jenkins-ci.org/browse/JENKINS-10239 Which makes Jenkins unusable.  
 

  
 
 
 
 

 
 
 

 
 
 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-40462) Wrappers in options

2016-12-16 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-40462  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Wrappers in options   
 

  
 
 
 
 

 
 PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/72, building on https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/70  
 

  
 
 
 
 

 
 
 

 
 
 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-40462) Wrappers in options

2016-12-16 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-40462  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40462  
 
 
  Wrappers in options   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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-40252) Items should have a Iterable getAllItemsUnsorted(Class)

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40252  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Items should have a Iterable getAllItemsUnsorted(Class)   
 

  
 
 
 
 

 
 Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Items.java test/src/test/java/hudson/model/ItemsTest.java http://jenkins-ci.org/commit/jenkins/cf0fea0c1f1dfca2530a0787384ddaf762b1e713 Log: [FIXED JENKINS-40252] Add an Iterable that returns all items unsorted  
 

  
 
 
 
 

 
 
 

 
 
 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-40521) Orphaned branch projects should not be considered buildable

2016-12-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40521  
 
 
  Orphaned branch projects should not be considered buildable   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 workflow-multibranch-plugin  
 
 
Created: 
 2016/Dec/16 11:46 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 WorkflowJob should consult WorkflowJobProperty for isBuildable, and BranchJobProperty should in turn consult Branch.isBuildable. This should prevent orphaned jobs from being scheduled. This attempt by Stephen Connolly is probably wrong, as it would not affect, for example, TimerTrigger. It is not a permission check which we want, but rather an emulation of disablement.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
  

[JIRA] (JENKINS-40492) How does a Groovy external library get its name?

2016-12-16 Thread jenk...@johnnado.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 John McGehee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40492  
 
 
  How does a Groovy external library get its name?   
 

  
 
 
 
 

 
Change By: 
 John McGehee  
 
 
Comment: 
 Now that I see how the library name is used, I cannot believe that it was not obvious earlier.  Anyway, in [PR #24|JENKINS-40492] I added some explanation to make sure that is absolutely clear.  
 

  
 
 
 
 

 
 
 

 
 
 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-40492) How does a Groovy external library get its name?

2016-12-16 Thread jenk...@johnnado.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 John McGehee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40492  
 
 
  How does a Groovy external library get its name?   
 

  
 
 
 
 

 
Change By: 
 John McGehee  
 

  
 
 
 
 

 
 The [documentation|https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/README.md#using-libraries] says:bq. @Library('somelib') From At first, I could not understand from  where  does this library name  "somelib"  come?This needs to be added to the documentation  came .   If   Now that I see how  the  documentation cannot be updated soon  library name is defined and used ,  quick answer here would be nice  I cannot believe that it was not obvious to me earlier . Anyway, in [PR #24|JENKINS-40492]   I  would happy  added some explanation  to  write the documentation  make sure that is absolutely clear.  The only task left  for you  is to review  and  submit a  accept the  pull request. Thank you.  
 

  
 
 
 
 

 
 
 

 
 
 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-40462) Wrappers in options

2016-12-16 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer started work on  JENKINS-40462  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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-40492) How does a Groovy external library get its name?

2016-12-16 Thread jenk...@johnnado.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 John McGehee commented on  JENKINS-40492  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: How does a Groovy external library get its name?   
 

  
 
 
 
 

 
 Now that I see how the library name is used, I cannot believe that it was not obvious earlier. Anyway, in PR #24 I added some explanation to make sure that is absolutely clear.  
 

  
 
 
 
 

 
 
 

 
 
 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-31605) Plugin manager allows uninstalling bundled plugins

2016-12-16 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31605  
 
 
  Plugin manager allows uninstalling bundled plugins   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 lts-candidate  regression  
 

  
 
 
 
 

 
 
 

 
 
 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-20618) upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException

2016-12-16 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-20618  
 
 
  upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 lts-candidate  
 

  
 
 
 
 

 
 
 

 
 
 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-37805) Jenkins startup task dependencies should be more explicit

2016-12-16 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-37805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins startup task dependencies should be more explicit   
 

  
 
 
 
 

 
 Oleg Nenashev It's not clear what this issue is about, and why it's an lts-candidate. Could you explain?  
 

  
 
 
 
 

 
 
 

 
 
 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-20618) upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException

2016-12-16 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 No response to comment in >1 year, so assuming this is long obsolete.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-20618  
 
 
  upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException   
 

  
 
 
 
 

 
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 Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] (JENKINS-39547) Corrupt node jar cache causes node to malfunction

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39547  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Corrupt node jar cache causes node to malfunction   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/remoting/Checksum.java src/main/java/hudson/remoting/FileSystemJarCache.java src/main/java/hudson/remoting/JarLoaderImpl.java src/test/java/hudson/remoting/ChecksumTest.java src/test/java/hudson/remoting/FileSystemJarCacheTest.java http://jenkins-ci.org/commit/remoting/cdd5bce5725d338b129c63c22b8e6a132e77865c Log: JENKINS-39547 - Corrupt jar cache (#130) 
 
Do not cache by URL 
 
 
Do not perform Checksum caching in Checksum class 
 We need a way to calculate reliable checksums and as implemented it causes temporary write-then-move files to have checksums cached never to use used. 
 
[FIXED JENKINS-39547] Verify cached slave jars before using them. 
 This moves checksum caching to FileSystemJarCache. 
 
Address review comments 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 
 

[JIRA] (JENKINS-39547) Corrupt node jar cache causes node to malfunction

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39547  
 
 
  Corrupt node jar cache causes node to malfunction   
 

  
 
 
 
 

 
Change By: 
 SCM/JIRA link daemon  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38624) MSBuild Projects no longer work after upgrading to 1.8.0

2016-12-16 Thread douglas....@teledynelecroy.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Douglas Lee commented on  JENKINS-38624  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MSBuild Projects no longer work after upgrading to 1.8.0   
 

  
 
 
 
 

 
 This problem happened to me with 1.8.0. Reverting to 1.7.3 resolved it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27748) Jenkins loses history (task page and overview)

2016-12-16 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-27748  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins loses history (task page and overview)   
 

  
 
 
 
 

 
 Kanstantsin Shautsou You reopened this, is it still an issue?  
 

  
 
 
 
 

 
 
 

 
 
 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-16417) Extensibility for Run.whyKeepLog

2016-12-16 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Can probably be considered fixed despite there not being extensibility.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-16417  
 
 
  Extensibility for Run.whyKeepLog   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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 

[JIRA] (JENKINS-16417) Extensibility for Run.whyKeepLog

2016-12-16 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-16417  
 
 
  Extensibility for Run.whyKeepLog   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 extension  lts-candidate  security  
 

  
 
 
 
 

 
 
 

 
 
 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-36240) Default repository permission are not considered

2016-12-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-36240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36240  
 
 
  Default repository permission are not considered   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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-39172) Not fully responsive on mobile

2016-12-16 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39172  
 
 
  Not fully responsive on mobile   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 lts-candidate  
 

  
 
 
 
 

 
 
 

 
 
 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-39999) Add description to POM

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-3  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add description to POM   
 

  
 
 
 
 

 
 Code changed in jenkins User: Evaristo Gutiérrez Path: pom.xml http://jenkins-ci.org/commit/mailer-plugin/0fe18c7cbf5e81612c43c3c21b6cae536ca0b060 Log: JENKINS-3 Use same description than in Wiki page.  
 

  
 
 
 
 

 
 
 

 
 
 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-39999) Add description to POM

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-3  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add description to POM   
 

  
 
 
 
 

 
 Code changed in jenkins User: Evaristo Gutiérrez Path: pom.xml http://jenkins-ci.org/commit/mailer-plugin/b95b86928a1f1df31c6ce932d3f9ea4033326e39 Log: JENKINS-3 Use https for url.  
 

  
 
 
 
 

 
 
 

 
 
 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-39999) Add description to POM

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-3  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add description to POM   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oliver Gondža Path: pom.xml http://jenkins-ci.org/commit/mailer-plugin/22bf4daa9ae040a6941159d99e69008d81a0182a Log: Merge pull request #32 from varyvol/JENKINS-3 JENKINS-3 Add plugin description to POM. Compare: https://github.com/jenkinsci/mailer-plugin/compare/6f0bd6cfe844...22bf4daa9ae0  
 

  
 
 
 
 

 
 
 

 
 
 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-39354) Improve robustness of CreateSlaveTest test

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve robustness of CreateSlaveTest test   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/test/acceptance/plugins/ssh_credentials/SshCredentialDialog.java http://jenkins-ci.org/commit/acceptance-test-harness/eef83b2569ae8bf69fe3ef23c57f872f381744b0 Log: Merge pull request #218 from varyvol/JENKINS_39354/CreateSlaveTest_robustness JENKINS-39354 CreateSlaveTest robustness Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/bbf34f9b8baf...eef83b2569ae  
 

  
 
 
 
 

 
 
 

 
 
 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-39354) Improve robustness of CreateSlaveTest test

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve robustness of CreateSlaveTest test   
 

  
 
 
 
 

 
 Code changed in jenkins User: Evaristo Gutiérrez Path: src/main/java/org/jenkinsci/test/acceptance/plugins/ssh_credentials/SshCredentialDialog.java http://jenkins-ci.org/commit/acceptance-test-harness/dd3100d497d208c838d22499602f71b7769e06b6 Log: JENKINS-39354 Move to element before clicking. Also increase timeout.  
 

  
 
 
 
 

 
 
 

 
 
 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-39999) Add description to POM

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-3  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add description to POM   
 

  
 
 
 
 

 
 Code changed in jenkins User: Evaristo Gutiérrez Path: pom.xml http://jenkins-ci.org/commit/mailer-plugin/b3a8433851a12bb32f1af8a2223e7251d072e109 Log: JENKINS-3 Add plugin description to POM.  
 

  
 
 
 
 

 
 
 

 
 
 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-39354) Improve robustness of CreateSlaveTest test

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve robustness of CreateSlaveTest test   
 

  
 
 
 
 

 
 Code changed in jenkins User: Evaristo Gutiérrez Path: src/main/java/org/jenkinsci/test/acceptance/plugins/ssh_credentials/SshCredentialDialog.java http://jenkins-ci.org/commit/acceptance-test-harness/266e2780b905af1301115c236da998a2801ddf6b Log: JENKINS-39354 Revert timeout increase.  
 

  
 
 
 
 

 
 
 

 
 
 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-36408) Client-side replay (or store and forward) of SSE events

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-36408  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Client-side replay (or store and forward) of SSE events   
 

  
 
 
 
 

 
 Code changed in jenkins User: Tom Fennelly Path: src/test/resources/multibranch/test_results/Jenkinsfile http://jenkins-ci.org/commit/blueocean-acceptance-test/b3b447e3389c4f127fadbd60032799bae073774f Log: Add a small wait in the Jenkinsfile used by multibranch/testResults.js (#87) 
 
Add a small wait in the Jenkinsfile used by multibranch/testResults.js 
 This is to ensure we don't hit random flaky fails due to JENKINS-36408 
 
A bit more detail in the comment 
  
 

  
 
 
 
 

 
 
 

 
 
 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-39999) Add description to POM

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-3  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add description to POM   
 

  
 
 
 
 

 
 Code changed in jenkins User: Evaristo Gutiérrez Path: pom.xml http://jenkins-ci.org/commit/mailer-plugin/325c9de09d8cd5265a2490b299e90e12f9464847 Log: JENKINS-3 Remove final dot.  
 

  
 
 
 
 

 
 
 

 
 
 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-39835) Be super defensive in remoting read

2016-12-16 Thread jn...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord commented on  JENKINS-39835  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Be super defensive in remoting read   
 

  
 
 
 
 

 
 i believe this issue has now been observed on a live site  
 

  
 
 
 
 

 
 
 

 
 
 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-39835) Be super defensive in remoting read

2016-12-16 Thread jn...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39835  
 
 
  Be super defensive in remoting read   
 

  
 
 
 
 

 
Change By: 
 James Nord  
 
 
Labels: 
 lts- candiatw candidate  
 

  
 
 
 
 

 
 
 

 
 
 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-39835) Be super defensive in remoting read

2016-12-16 Thread jn...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39835  
 
 
  Be super defensive in remoting read   
 

  
 
 
 
 

 
Change By: 
 James Nord  
 
 
Labels: 
 lts-candiatw  
 

  
 
 
 
 

 
 
 

 
 
 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-40393) Internationalize all the error messages in Declarative

2016-12-16 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-40393  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40393  
 
 
  Internationalize all the error messages in Declarative   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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-40393) Internationalize all the error messages in Declarative

2016-12-16 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-40393  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Internationalize all the error messages in Declarative   
 

  
 
 
 
 

 
 PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/71  
 

  
 
 
 
 

 
 
 

 
 
 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-40491) Improve diagnostics of the preliminary FifoBuffer termination

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve diagnostics of the preliminary FifoBuffer termination   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/remoting/nio/FifoBuffer.java src/main/java/org/jenkinsci/remoting/nio/NioChannelHub.java http://jenkins-ci.org/commit/remoting/2f81d4c9604dfe490b8474b0c44c1ef90f4cbeca Log: JENKINS-40491 - Improve diagnostincs of the preliminary FifoBuffer termination. When NioChannelHub suffers from the preliminary buffer closure, it will print a SEVERE log to the Agent log. This change should improve diagnostics of issues like JENKINS-31050  
 

  
 
 
 
 

 
 
 

 
 
 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-40402) Define Build triggers

2016-12-16 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-40402  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Define Build triggers
 

  
 
 
 
 

 
 There is - see https://github.com/jenkinsci/pipeline-model-definition-plugin/wiki/Trigger-runs. But it only works if the trigger class has a @Symbol on it, and the GitLab trigger doesn't seem to have one - https://github.com/jenkinsci/gitlab-plugin/blob/master/src/main/java/com/dabsquared/gitlabjenkins/GitLabPushTrigger.java#L296 - should be easy enough to add, 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, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40393) Internationalize all the error messages in Declarative

2016-12-16 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer started work on  JENKINS-40393  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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-31050) Slave goes offline during the build

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-31050  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Slave goes offline during the build   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/remoting/nio/FifoBuffer.java src/main/java/org/jenkinsci/remoting/nio/NioChannelHub.java http://jenkins-ci.org/commit/remoting/e500853bc8b50c12761ad63739fd27fd40183b3c Log: Merge pull request #138 from oleg-nenashev/bug/JENKINS-31050 JENKINS-40491 - Improve diagnostincs of the preliminary FifoBuffer termination Compare: https://github.com/jenkinsci/remoting/compare/cdd5bce5725d...e500853bc8b5  
 

  
 
 
 
 

 
 
 

 
 
 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-31050) Slave goes offline during the build

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-31050  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Slave goes offline during the build   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/remoting/nio/FifoBuffer.java src/main/java/org/jenkinsci/remoting/nio/NioChannelHub.java http://jenkins-ci.org/commit/remoting/2f81d4c9604dfe490b8474b0c44c1ef90f4cbeca Log: JENKINS-40491 - Improve diagnostincs of the preliminary FifoBuffer termination. When NioChannelHub suffers from the preliminary buffer closure, it will print a SEVERE log to the Agent log. This change should improve diagnostics of issues like JENKINS-31050  
 

  
 
 
 
 

 
 
 

 
 
 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-40491) Improve diagnostics of the preliminary FifoBuffer termination

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve diagnostics of the preliminary FifoBuffer termination   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/remoting/nio/FifoBuffer.java src/main/java/org/jenkinsci/remoting/nio/NioChannelHub.java http://jenkins-ci.org/commit/remoting/e500853bc8b50c12761ad63739fd27fd40183b3c Log: Merge pull request #138 from oleg-nenashev/bug/JENKINS-31050 JENKINS-40491 - Improve diagnostincs of the preliminary FifoBuffer termination Compare: https://github.com/jenkinsci/remoting/compare/cdd5bce5725d...e500853bc8b5  
 

  
 
 
 
 

 
 
 

 
 
 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-40451) Credentials are not being scoped to API endpoints

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40451  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Credentials are not being scoped to API endpoints   
 

  
 
 
 
 

 
 Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java src/main/resources/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator/config.jelly src/main/resources/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource/config-detail.jelly http://jenkins-ci.org/commit/github-branch-source-plugin/b7788c606b43f29fc91d277de81a67a65abe39d4 Log: [FIXED JENKINS-40451] Respect the API endpoint for credentials domains 
 
Also make the API Endpoint visible when there is more that one API endpoint to select from 
  
 

  
 
 
 
 

 
 
 

 
 
 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-34268) Lock multiple resources using the Pipeline lock step

2016-12-16 Thread bren...@shapesecurity.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brendan Mannix commented on  JENKINS-34268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lock multiple resources using the Pipeline lock step   
 

  
 
 
 
 

 
 Now that the PR that fixes this ticket is merged, I'd like to request a release of this plugin as soon as is appropriate.  
 

  
 
 
 
 

 
 
 

 
 
 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-38001) Cannot rename a GitHub Org Folder

2016-12-16 Thread chance.zibol...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chance Zibolski commented on  JENKINS-38001  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot rename a GitHub Org Folder   
 

  
 
 
 
 

 
 I'm hitting this myself. A huge pain because my original name had spaces in it, and it's making it a bit annoying to link to/reference in other places, but I don't really want to re-create everything just to rename it either.  
 

  
 
 
 
 

 
 
 

 
 
 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-36408) Client-side replay (or store and forward) of SSE events

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-36408  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Client-side replay (or store and forward) of SSE events   
 

  
 
 
 
 

 
 Code changed in jenkins User: tfennelly Path: src/test/resources/multibranch/test_results/Jenkinsfile http://jenkins-ci.org/commit/blueocean-acceptance-test/5c7a215b970cd299acfce0edeb6b10ff610e6cc9 Log: Add a small wait in the Jenkinsfile used by multibranch/testResults.js This is to ensure we don't hit random flaky fails due to JENKINS-36408  
 

  
 
 
 
 

 
 
 

 
 
 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-40286) EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of reimplementing it

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40286  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of reimplementing it   
 

  
 
 
 
 

 
 Code changed in jenkins User: kbrowder Path: core/src/main/java/jenkins/slaves/EncryptedSlaveAgentJnlpFile.java http://jenkins-ci.org/commit/jenkins/37806a53c87855cbdd9eda073600ad828ec6f5c0 Log: [FIXED JENKINS-40286] - Delegate JnlpMac computation to SlaveComputers if possible (#2658) [FIXED JENKINS-40286] - Delegate JnlpMac computation to SlaveComputers if possible  
 

  
 
 
 
 

 
 
 

 
 
 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-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38228  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Incorrect implementation of `loadUserByUsename`, Users are added on demand   
 

  
 
 
 
 

 
 Code changed in jenkins User: Denys Digtiar Path: src/main/java/org/jenkinsci/plugins/saml/SamlUserDetailsService.java http://jenkins-ci.org/commit/saml-plugin/227d80860f144113a42e40bfce22971ba28f345e Log: JENKINS-38228 - User lookup method is changed in Details Services. (#16) Loading existing user by name should not be creating new users. Therefore, the User lookup method is updated to disable automatic creation of users.  
 

  
 
 
 
 

 
 
 

 
 
 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-38903) Split the Exceptions handling for node provision and adding a node to Jenkins in NodeProvisioner

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38903  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Split the Exceptions handling for node provision and adding a node to Jenkins in NodeProvisioner   
 

  
 
 
 
 

 
 Code changed in jenkins User: Pavel Janousek Path: core/src/main/java/hudson/slaves/CloudProvisioningListener.java core/src/main/java/hudson/slaves/NodeProvisioner.java http://jenkins-ci.org/commit/jenkins/15e69874190ce56e228b823aa1584b8497fc673b Log: JENKINS-38903 Split Exception handling for node provision and adding to Jenkins (#2591) 
 
JENKINS-38903 Split Exception handling for node provision and adding to Jenkins 
 
 
Defined new static helper methods that ensure exceptions are not propagated 
 
 
Added onCommit and onRollback signals to CloudProvisioningListener 
 Added the new signals to be able to notify the state after Jenkins.addNode(Node) All Listener's calls moved to an exception-tolerant static helpers 
 
Added @Nonnull annotation Changed the method signature CloudProvisioningListener.onRollback() 
 
 
Re-throw Error in the fireOnXXX() Removed re-thrown Throwable in the main try/catch block (an instance of the Error is handled separately) 
 
 
Handling of Error changed 
 
 
Fixed Error instance handling in NodeProvisioner.fireOnFailure() 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
   

[JIRA] (JENKINS-32797) Access to check for unprotected/never secured paths

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-32797  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Access to check for unprotected/never secured paths   
 

  
 
 
 
 

 
 Code changed in jenkins User: Bryson Gibbons Path: core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/0060335b8cf6d36641bd610817bae98873c32746 Log: JENKINS-32797 Break the catch clause contents of Jenkins.getTarget(… (#2652) 
 
JENKINS-32797 Break the catch clause contents of Jenkins.getTarget() out into a separate, publicly accessible function. 
 This will allow plugins (particularly authentication plugins that override the normal authentication process) to determine if authentication is not required for a particular path by calling isPathUnprotected(restOfPath). 
 
Add @since TODO to comment 
 
 
Change name of function to something that is accurate and clear 
 isPathUnprotected is misleading, and the Javadoc was worse. isSubjectToMandatoryReadPermissionCheck is a much better name, and the return value is reversed to match the name,  
 

  
 
 
 
 

 
 
 

 
 
 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-39971) Manual update button hidden if no plugins to update availabe.

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39971  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Manual update button hidden if no plugins to update availabe.   
 

  
 
 
 
 

 
 Code changed in jenkins User: bpedersen2 Path: core/src/main/resources/hudson/PluginManager/table.jelly http://jenkins-ci.org/commit/jenkins/8634965a4f4833c93cf6f7f368891d7b54e7983f Log: JENKINS-39971 Always display the recheck button in the Plugin Manager (#2668) The re-check updatecenter button should be visible even if there are currently no pending updates.  
 

  
 
 
 
 

 
 
 

 
 
 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-40435) Job configuration submission should be a bulk change

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40435  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job configuration submission should be a bulk change   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/Job.java http://jenkins-ci.org/commit/jenkins/a0262d2fec648fe98e83a08f1735394a9f243f4d Log: JENKINS-40435 - Use BulkChange when processing config changes in Job#doConfigSubmit. (#2664) When an empty Freestyle job config gets submitted in the default configuration of Jenkins 2.35, the data is being saved to the disk 8 times. All of them happen in this code: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Job.java#L1227-L1246 
 
setDisplayName 
Project#getBuildWrappersList().rebuild (onModified handler) 
Project#getBuilderList().rebuild (onModified handler) 
Project#getPublisherList().rebuild (onModified handler) 
AbstractProject#makeDisabled 
AbstractProject#setScm 
AbstractProject#triggers.replaceBy 
final save() 
 There is not so much sense to save partial configurations to the disk due to the risk of data inconsistency there. This change just wraps the config submission section of the job into the BulkChange clause.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 


[JIRA] (JENKINS-40365) Node should have a getProperty method to get aNodeProperty for specific class

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40365  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Node should have a getProperty method to get aNodeProperty for specific class   
 

  
 
 
 
 

 
 Code changed in jenkins User: Markus Winter Path: core/src/main/java/hudson/model/Node.java http://jenkins-ci.org/commit/jenkins/a1258c0009bbdbe1a7de19ce383b5eac8bf4296f Log: JENKINS-40365 add Node#getNodeProperty methods (#2663) 
 
JENKINS-40365 add getNodeProperty methods 
 
 
implement getNodeProperty in DummySlave 
 
 
implement getNodeProperty in Node 
 avoid binary imcompatible change dded javadoc 
 
revert Slave.jar to original 
 
 
fix formatting 
 
 
more formatting 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  

[JIRA] (JENKINS-39433) Make checkURIEncoding an admin monitor

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39433  
 
 
  Make checkURIEncoding an admin monitor   
 

  
 
 
 
 

 
Change By: 
 SCM/JIRA link daemon  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40362) SSHD Module - Handshake fails (wrong shared secret) 1 out of 256 times (SSHD-330)

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40362  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSHD Module - Handshake fails (wrong shared secret) 1 out of 256 times (SSHD-330)   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: war/pom.xml http://jenkins-ci.org/commit/jenkins/ef8ddd8a48df04952e59d242e713ff6e05b972c5 Log: [FIXED JENKINS-40362] - Update SSHD Module to 1.9 (#2662)  
 

  
 
 
 
 

 
 
 

 
 
 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-40362) SSHD Module - Handshake fails (wrong shared secret) 1 out of 256 times (SSHD-330)

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40362  
 
 
  SSHD Module - Handshake fails (wrong shared secret) 1 out of 256 times (SSHD-330)   
 

  
 
 
 
 

 
Change By: 
 SCM/JIRA link daemon  
 
 
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-39433) Make checkURIEncoding an admin monitor

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39433  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make checkURIEncoding an admin monitor   
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Beck Path: core/src/main/java/jenkins/diagnostics/URICheckEncodingMonitor.java core/src/main/java/jenkins/management/AdministrativeMonitorsDecorator.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/jenkins/diagnostics/Messages.properties core/src/main/resources/jenkins/diagnostics/URICheckEncodingMonitor/message.jelly core/src/main/resources/jenkins/model/Jenkins/manage.jelly http://jenkins-ci.org/commit/jenkins/7bb4a592d462f30310e0ad82b2fda4fb32321796 Log: [FIX JENKINS-39433] Make URI encoding check into admin monitor (#2661)  
 

  
 
 
 
 

 
 
 

 
 
 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-40501) Reactive Reference Parameter not working with "List Subversion Tags" parameter

2016-12-16 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-40501  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Reactive Reference Parameter not working with "List Subversion Tags" parameter   
 

  
 
 
 
 

 
 Hi Christoph Obermair, today I do not have time to try to reproduce the issue completely. But maybe a quick reply on this part would help? >When returning the class of the referenced "List Subversion Tags" parameter to the text box I see the value "class java.lang.String". However, I would have expected something like "class hudson.scm.listtagsparameter.ListSubversionTagsParameterValue". If I understand it correctly, your active choices parameter returned, when executing your Groovy script, value from another parameter as a String, opposed to an object from the Jenkins code base API. That would be the expected behaviour. The plug-in works by parsing the HTML DOM. So it has access to only objects in the screen (plus the jenkinsProject variable we inject). So in an active choices parameter, the value returned from other parameters would be a string. And then in your Groovy script for that active choices parameter, you would have to query Jenkins in Groovy, retrieving the item/action/etc, and then populate the current active choices element. Hope that helps Bruno  
 

  
 
 
 
 

 
 
 

 
 
 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-40520) Breaks Save button on Manage Jenkins/Configure System

2016-12-16 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40520  
 
 
  Breaks Save button on Manage Jenkins/Configure System   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
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-40520) Breaks Save button on Manage Jenkins/Configure System

2016-12-16 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40520  
 
 
  Breaks Save button on Manage Jenkins/Configure System   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 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-40520) Breaks Save button on Manage Jenkins/Configure System

2016-12-16 Thread ifernandezca...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40520  
 
 
  Breaks Save button on Manage Jenkins/Configure System   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Catalin Luta  
 
 
Components: 
 jiratestresultreporter-plugin  
 
 
Created: 
 2016/Dec/16 9:21 PM  
 
 
Environment: 
 Jenkins Core 1.625.3  JiraTestResultReporter 2.0.3  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ivan Fernandez Calvo  
 

  
 
 
 
 

 
 In a clean installation when you install JiraTestResultReporter 2.0.3 it seems to break the normal behaviour of button save on Manage Jenkins/Configure System Steps to replicate the issue 
 
start a clean instance of Jenkins 
install JiraTestResultReporter 2.0.3 
restart 
go to Manage Jenkins/Configure System 
click on save 
It should return to Manage Jenkins but instead it stay on Manage Jenkins/Configure System 
 this issue it is pretty similar to JENKINS-33515  
 

  
 
 
 
 

 
 
  

[JIRA] (JENKINS-36240) Default repository permission are not considered

2016-12-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Jesse Glick  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36240  
 
 
  Default repository permission are not considered   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36240) Default repository permission are not considered

2016-12-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-36240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40342) No way to specify in the UI the network/IP address to use for SSH

2016-12-16 Thread tim.soderstrom+jenk...@teamsnap.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Soderstrom closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 2.12 appeas to be working great! Thanks so much for getting this fixed up and in rapid order too!  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40342  
 
 
  No way to specify in the UI the network/IP address to use for SSH   
 

  
 
 
 
 

 
Change By: 
 Tim Soderstrom  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-20309) Repo(Gerrit) is behaving differently than from the command line.

2016-12-16 Thread beth.grif...@amd.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Beth Griffin commented on  JENKINS-20309  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Repo(Gerrit) is behaving differently than from the command line.
 

  
 
 
 
 

 
 So it looks like the recommended solution, at least from the command line, is to install the dependencies via the Cygwin install, and to install repo as though on a Linux system from inside the Cygwin terminal window. And to use the cygpath Jenkins plugin so that the windows machines know how to convert Linux paths to local Cygwin paths.  
 

  
 
 
 
 

 
 
 

 
 
 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-40519) Add team.scm.workspaceUUID to list of RTC related Environment Variables available to the Build

2016-12-16 Thread nicolasx.pois...@bnc.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas Poisson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40519  
 
 
  Add team.scm.workspaceUUID to list of RTC related Environment Variables available to the Build   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 teamconcert-plugin  
 
 
Created: 
 2016/Dec/16 8:42 PM  
 
 
Environment: 
 Jenkins 2.7.1  Team Concert plugin 1.2.0.2  
 
 
Labels: 
 rtc teamconcert team-concert  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Nicolas Poisson  
 

  
 
 
 
 

 
 The Team Concert plugin page at https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin#TeamConcertPlugin-RTCrelatedEnvironmentVariablesavailabletotheBuild has a list of variables exposed to Jenkins from RTC, but the RTC Build Workspace is not one of them when building from a RTC Build Definition.  In the case of Jenkins jobs based on RTC Streams (new in teamconcert-plugin 1.2.0.0), this is mitigated by the presence of the new rtcTempRepoWorkspaceUUID property, but for jobs based on RTC Build Definitions (teamconcert-plugin 1.1.9.* and below), this value is not provided even though it is a mandatory field in the RTC Build Definition (and we use it in some of our custom plugins). We would like the RTC property team.scm.workspaceUUID to be part of the environment variables provided to Jenkins by RTC.  
 

  
 
 
 
 

 

[JIRA] (JENKINS-39739) NPE when using a credentials parameter with multi-configuration project

2016-12-16 Thread ultraz...@mail.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Z stopped work on  JENKINS-39739  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Alexander Z  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 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-39739) NPE when using a credentials parameter with multi-configuration project

2016-12-16 Thread ultraz...@mail.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Z started work on  JENKINS-39739  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Alexander Z  
 
 
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-38179) Authentication Error with GIT Client version 2.0.0

2016-12-16 Thread benjamin.d.gold...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Benjamin Goldman commented on  JENKINS-38179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Authentication Error with GIT Client version 2.0.0   
 

  
 
 
 
 

 
 Mark Waite it was a ID10-T error or PEBCAK. Not an instance of the bug. I cannot reproduce 4 times in a row now rebuilding entirely on my own from scripts. Sorry   
 

  
 
 
 
 

 
 
 

 
 
 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-36240) Default repository permission are not considered

2016-12-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-36240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Default repository permission are not considered   
 

  
 
 
 
 

 
 A 403 is also possible in certain cases.  
 

  
 
 
 
 

 
 
 

 
 
 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-38825) MultiJob does not build Pipeline jobs

2016-12-16 Thread si...@simonmweber.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Simon Weber commented on  JENKINS-38825  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MultiJob does not build Pipeline jobs   
 

  
 
 
 
 

 
 Maybe Sam Van Oort or Jesse Glick would be able to help (given their work on https://issues.jenkins-ci.org/browse/JENKINS-26050)?  
 

  
 
 
 
 

 
 
 

 
 
 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-38825) MultiJob does not build Pipeline jobs

2016-12-16 Thread si...@simonmweber.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Simon Weber edited a comment on  JENKINS-38825  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MultiJob does not build Pipeline jobs   
 

  
 
 
 
 

 
 I'm happy to work on this if someone can point me in the right direction.Notably, the trigger plugin seems to work fine on its own (see https://issues.jenkins-ci.org/browse/JENKINS-38998?focusedCommentId=280639=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-280639); this problem  seem's  seems  to be on multijob's end.  
 

  
 
 
 
 

 
 
 

 
 
 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-38825) MultiJob does not build Pipeline jobs

2016-12-16 Thread si...@simonmweber.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Simon Weber commented on  JENKINS-38825  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MultiJob does not build Pipeline jobs   
 

  
 
 
 
 

 
 I'm happy to work on this if someone can point me in the right direction. Notably, the trigger plugin seems to work fine on its own (see https://issues.jenkins-ci.org/browse/JENKINS-38998?focusedCommentId=280639=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-280639); this problem seem's to be on multijob's end.  
 

  
 
 
 
 

 
 
 

 
 
 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-34276) docker.inside within a withRegistry block seems to use image.id instead of image.imageName()

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-34276  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: docker.inside within a withRegistry block seems to use image.id instead of image.imageName()   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: demo/JENKINS_HOME/jobs/puller/config.xml demo/plugins.txt src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy http://jenkins-ci.org/commit/docker-workflow-plugin/417acf3af06e277071b87a7fec065d6dc50fdcad Log: [FIXED JENKINS-34276] Allow Image.inside to run with either a local or registry-prefixed name.  
 

  
 
 
 
 

 
 
 

 
 
 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-38998) Cannot trigger pipeline job

2016-12-16 Thread si...@simonmweber.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Simon Weber commented on  JENKINS-38998  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot trigger pipeline job   
 

  
 
 
 
 

 
 Ok, I think the trigger plugin actually works as of 2.29; what I was describing was done in https://issues.jenkins-ci.org/browse/JENKINS-26050. I'm able to trigger a build both blocking and nonblocking builds of a pipeline, just not as part of a multijob phase. So, I think this can be closed, but https://issues.jenkins-ci.org/browse/JENKINS-38825 is still valid. My environment is trigger 2.32 and jenkins 2.34, in case it's relevant.  
 

  
 
 
 
 

 
 
 

 
 
 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-36240) Default repository permission are not considered

2016-12-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick edited a comment on  JENKINS-36240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Default repository permission are not considered   
 

  
 
 
 
 

 
 In my experiments, it does work, with one caveat: if the scan token does not have administrative permission on the repository, the result is a 404. Which means that JENKINS-37608 is  a nonstarter  not satisfiable without loss of functionality .  
 

  
 
 
 
 

 
 
 

 
 
 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-36240) Default repository permission are not considered

2016-12-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-36240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Default repository permission are not considered   
 

  
 
 
 
 

 
 In my experiments, it does work, with one caveat: if the scan token does not have administrative permission on the repository, the result is a 404. Which means that JENKINS-37608 is a nonstarter.  
 

  
 
 
 
 

 
 
 

 
 
 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-36240) Default repository permission are not considered

2016-12-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-36240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Default repository permission are not considered   
 

  
 
 
 
 

 
 Good news: there is a new experimental endpoint which should give us exactly what we need.  
 

  
 
 
 
 

 
 
 

 
 
 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-40446) Links broken in GitHub status for matrix projects

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40446  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Links broken in GitHub status for matrix projects   
 

  
 
 
 
 

 
 Code changed in jenkins User: James William Dumay Path: pom.xml src/main/java/org/jenkinsci/plugins/blueoceandisplayurl/BlueOceanDisplayURLImpl.java http://jenkins-ci.org/commit/blueocean-display-url-plugin/b69894665fccd09a2f9d84566ab91d3d1cd5fe1b Log: JENKINS-40446 Links broken in GitHub status for matrix projects (#3)  
 

  
 
 
 
 

 
 
 

 
 
 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-40518) Give the unzip step a parameter to suppress verbose output

2016-12-16 Thread be_...@sbcglobal.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Ray created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40518  
 
 
  Give the unzip step a parameter to suppress verbose output   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 rsandell  
 
 
Components: 
 pipeline-utility-steps-plugin  
 
 
Created: 
 2016/Dec/16 7:28 PM  
 
 
Environment: 
 Pipeline Utility Steps 1.2.2  Pipeline 2.4  Jenkins LTS 2.19.4  Zulu OpenJDK 1.8.0_102-b14  Windows 7 Pro  
 
 
Labels: 
 plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Brian Ray  
 

  
 
 
 
 

 
 The unzip step logs for every file extracted, which can clutter up the console (similar to JENKINS-14541). It would be nice if it took an argument to reduce verbosity. Maybe just a one-line log message reporting how many files were extracted, after the initial Extracting from: message. Currently if I have a big ZIP and do the following 

 

node {
  unzip( zipFile: 'biggy.zip', dir: 'over/there' )
}
 

 Then it could yield hundreds of lines after the initial message like 

 

Extracting: somefile -> c:\jenkins_agent\workspace\cool-job\over\there\somefile
 .
 .
 .
 

  
  

[JIRA] (JENKINS-34998) Make CMake plugin compatible with pipeline

2016-12-16 Thread fifteenknots...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Weber commented on  JENKINS-34998  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make CMake plugin compatible with pipeline   
 

  
 
 
 
 

 
 Currently there is no implementation plan. Implementing it as a  

 
DurableTaskStep 

  turned out to be a nearly complete re-write.  
 

  
 
 
 
 

 
 
 

 
 
 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-40494) Administrative monitor for installed unsafe plugins

2016-12-16 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-40494  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Administrative monitor for installed unsafe plugins   
 

  
 
 
 
 

 
 I suppose you could create a separate Downloadable but I see no particular advantage to that. Would seem easier to add a new top-level section to update-center.json and thus to UpdateSite.Data. I would suggest something like: 

 

"pluginWarnings": [
  {
"name": "do-anything-you-like",
"message": "This plugin allows all users to do anything they like and so it is not safe to install."
  },
  {
"name": "acme-builder",
"version": "1.2",
"Versions 1.2 and older of this plugin are known to initiate meltdowns in the Acme reactor core. Please update to 1.3 or above right away."
  }
]
 

 Since I happen to know that you have access to a vendor plugin which provides customized update sites, I would encourage you to prototype delivering comparable metadata from that plugin, or work with someone who could do such a prototype.  
 

  
 
 
 
 

 
 
 

 
 
 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-38998) Cannot trigger pipeline job

2016-12-16 Thread si...@simonmweber.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Simon Weber commented on  JENKINS-38998  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot trigger pipeline job   
 

  
 
 
 
 

 
 Having read over https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md#historical-background, I'm guessing all the references to AbstractProject/Build would need to be changed? It looks like an awful lot of code...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40492) How does a Groovy external library get its name?

2016-12-16 Thread jenk...@johnnado.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 John McGehee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40492  
 
 
  How does a Groovy external library get its name?   
 

  
 
 
 
 

 
Change By: 
 John McGehee  
 

  
 
 
 
 

 
 The [documentation|https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/README.md#using-libraries] says:bq. @Library('somelib')From where does this library name "somelib" come?This needs to be added to the documentation.  If the documentation cannot be updated soon, quick answer here would be nice.   I would happy to write the documentation for you and submit a pull request. Thank you.  
 

  
 
 
 
 

 
 
 

 
 
 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-18730) Allow triggering of backups from CLI

2016-12-16 Thread heilon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin R. commented on  JENKINS-18730  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow triggering of backups from CLI   
 

  
 
 
 
 

 
 the dream is real, but reality is failing meee  
 

  
 
 
 
 

 
 
 

 
 
 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-34268) Lock multiple resources using the Pipeline lock step

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-34268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lock multiple resources using the Pipeline lock step   
 

  
 
 
 
 

 
 Code changed in jenkins User: Antonio Muniz Path: src/main/java/org/jenkins/plugins/lockableresources/BackwardCompatibility.java src/main/java/org/jenkins/plugins/lockableresources/LockStep.java src/main/java/org/jenkins/plugins/lockableresources/LockStepExecution.java src/main/java/org/jenkins/plugins/lockableresources/LockableResource.java src/main/java/org/jenkins/plugins/lockableresources/LockableResourcesManager.java src/main/java/org/jenkins/plugins/lockableresources/actions/LockableResourcesRootAction.java src/main/java/org/jenkins/plugins/lockableresources/queue/LockRunListener.java src/main/java/org/jenkins/plugins/lockableresources/queue/LockableResourcesStruct.java src/main/java/org/jenkins/plugins/lockableresources/queue/QueuedContextStruct.java src/main/resources/org/jenkins/plugins/lockableresources/LockStep/config.jelly src/main/resources/org/jenkins/plugins/lockableresources/LockStep/help-label.html src/main/resources/org/jenkins/plugins/lockableresources/LockStep/help-quantity.html src/main/resources/org/jenkins/plugins/lockableresources/LockStep/help-resource.html src/test/java/org/jenkins/plugins/lockableresources/LockStepTest.java http://jenkins-ci.org/commit/lockable-resources-plugin/974572db98214f7b9293a303c9fd8371877250a0 Log: Merge pull request #42 from amuniz/pr-26-fix JENKINS-34268JENKINS-34273 Lock multiple resources with specific quantity Compare: https://github.com/jenkinsci/lockable-resources-plugin/compare/ba48550fa5bc...974572db9821  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 
   

[JIRA] (JENKINS-40446) Links broken in GitHub status for matrix projects

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40446  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Links broken in GitHub status for matrix projects   
 

  
 
 
 
 

 
 Code changed in jenkins User: James Dumay Path: pom.xml src/main/java/org/jenkinsci/plugins/blueoceandisplayurl/BlueOceanDisplayURLImpl.java http://jenkins-ci.org/commit/blueocean-display-url-plugin/f67ea827eb8520be77d5a07f9623600756fd003f Log: JENKINS-40446 Links broken in GitHub status for matrix projects  
 

  
 
 
 
 

 
 
 

 
 
 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-34273) Extend quantity configuration to Pipeline lock step

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-34273  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Extend quantity configuration to Pipeline lock step   
 

  
 
 
 
 

 
 Code changed in jenkins User: Antonio Muniz Path: src/main/java/org/jenkins/plugins/lockableresources/BackwardCompatibility.java src/main/java/org/jenkins/plugins/lockableresources/LockStep.java src/main/java/org/jenkins/plugins/lockableresources/LockStepExecution.java src/main/java/org/jenkins/plugins/lockableresources/LockableResource.java src/main/java/org/jenkins/plugins/lockableresources/LockableResourcesManager.java src/main/java/org/jenkins/plugins/lockableresources/actions/LockableResourcesRootAction.java src/main/java/org/jenkins/plugins/lockableresources/queue/LockRunListener.java src/main/java/org/jenkins/plugins/lockableresources/queue/LockableResourcesStruct.java src/main/java/org/jenkins/plugins/lockableresources/queue/QueuedContextStruct.java src/main/resources/org/jenkins/plugins/lockableresources/LockStep/config.jelly src/main/resources/org/jenkins/plugins/lockableresources/LockStep/help-label.html src/main/resources/org/jenkins/plugins/lockableresources/LockStep/help-quantity.html src/main/resources/org/jenkins/plugins/lockableresources/LockStep/help-resource.html src/test/java/org/jenkins/plugins/lockableresources/LockStepTest.java http://jenkins-ci.org/commit/lockable-resources-plugin/974572db98214f7b9293a303c9fd8371877250a0 Log: Merge pull request #42 from amuniz/pr-26-fix JENKINS-34268JENKINS-34273 Lock multiple resources with specific quantity Compare: https://github.com/jenkinsci/lockable-resources-plugin/compare/ba48550fa5bc...974572db9821  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

[JIRA] (JENKINS-40446) Links broken in GitHub status for matrix projects

2016-12-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40446  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Links broken in GitHub status for matrix projects   
 

  
 
 
 
 

 
 Code changed in jenkins User: James Dumay Path: pom.xml src/main/java/org/jenkinsci/plugins/blueoceandisplayurl/BlueOceanDisplayURLImpl.java http://jenkins-ci.org/commit/blueocean-display-url-plugin/983465ef14544ce8afc9f429097d7add80d9f872 Log: JENKINS-40446 Links broken in GitHub status for matrix projects  
 

  
 
 
 
 

 
 
 

 
 
 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-35392) ec2 plugin throws NoClassDefFoundError - HttpContext

2016-12-16 Thread philip.shap...@claritasgenomics.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Phil Shapiro commented on  JENKINS-35392  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ec2 plugin throws NoClassDefFoundError - HttpContext   
 

  
 
 
 
 

 
 We noticed that many plugins were out of date, so I updated all the plugins and the error went away, even after restarting.  
 

  
 
 
 
 

 
 
 

 
 
 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-35392) ec2 plugin throws NoClassDefFoundError - HttpContext

2016-12-16 Thread philip.shap...@claritasgenomics.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Phil Shapiro resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35392  
 
 
  ec2 plugin throws NoClassDefFoundError - HttpContext   
 

  
 
 
 
 

 
Change By: 
 Phil Shapiro  
 
 
Status: 
 Reopened 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.


  1   2   3   >