[JIRA] [email-ext-plugin] (JENKINS-35292) Nullpointer when try to add Trigger for Email

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
2.43 fixes 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-35292 
 
 
 
  Nullpointer when try to add Trigger for Email   
 
 
 
 
 
 
 
 
 

Change By:
 
 David van Laatum 
 
 
 

Status:
 
 In Progress Closed 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-33717) NullPointerException when submitting for watching a job

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
2.43 fixes 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33717 
 
 
 
  NullPointerException when submitting for watching a job  
 
 
 
 
 
 
 
 
 

Change By:
 
 David van Laatum 
 
 
 

Status:
 
 In Progress Closed 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-35289) The Content Token Reference shows 'ERROR: Failed to load help file: Server Error'

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
2.43 fixes 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-35289 
 
 
 
  The Content Token Reference shows 'ERROR: Failed to load help file: Server Error'  
 
 
 
 
 
 
 
 
 

Change By:
 
 David van Laatum 
 
 
 

Status:
 
 In Progress Closed 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [ssh-plugin] (JENKINS-24913) SSH Plugin displays password parameter values unencrypted in log

2016-06-03 Thread dpdav...@ftb.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Ftb stopped work on  JENKINS-24913 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Dan Ftb 
 
 
 

Status:
 
 In Progress Open 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [ssh-plugin] (JENKINS-24913) SSH Plugin displays password parameter values unencrypted in log

2016-06-03 Thread dpdav...@ftb.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Ftb started work on  JENKINS-24913 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Dan Ftb 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [pipeline-stage-view-plugin] (JENKINS-33700) Visualization color should not be green for an UNSTABLE build

2016-06-03 Thread abc...@163.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 feng yu commented on  JENKINS-33700 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Visualization color should not be green for an UNSTABLE build  
 
 
 
 
 
 
 
 
 
 
Yes. I find that the stage view is not correct if I use currentBuild.result. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [multijob-plugin] (JENKINS-30327) Failed to scout MultiJobBuildSelector - ClassNotFoundException: hudson.plugins.copyartifact.BuildSelector

2016-06-03 Thread jel+jenk...@cs.ovgu.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jens Elkner commented on  JENKINS-30327 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed to scout MultiJobBuildSelector - ClassNotFoundException: hudson.plugins.copyartifact.BuildSelector  
 
 
 
 
 
 
 
 
 
 
Same for jenkins 2.7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-35289) The Content Token Reference shows 'ERROR: Failed to load help file: Server Error'

2016-06-03 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-35289 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The Content Token Reference shows 'ERROR: Failed to load help file: Server Error'  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: David van Laatum Path: src/main/java/hudson/plugins/emailext/plugins/content/JellyScriptContent.java src/main/java/hudson/plugins/emailext/plugins/content/ScriptContent.java src/main/java/hudson/plugins/emailext/plugins/content/TemplateContent.java http://jenkins-ci.org/commit/email-ext-plugin/824b0ee5db48b3e0f955fafca5db052c212ac6de Log: Fix for https://issues.jenkins-ci.org/browse/JENKINS-35289 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [claim-plugin] (JENKINS-34905) Claims Plugin - Claim Related Email can be sent to the regular "Failed" and "Fixed" email recipients too

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum commented on  JENKINS-34905 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Claims Plugin - Claim Related Email can be sent to the regular "Failed" and "Fixed" email recipients too  
 
 
 
 
 
 
 
 
 
 
From my brief look it looks like this will require some changes on the claim plugin side to support sending the email via email-ext 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [maven-plugin] (JENKINS-34900) Naginator plugin throwing Null Pointer Exception

2016-06-03 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34900 
 
 
 
  Naginator plugin throwing Null Pointer Exception  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [maven-plugin] (JENKINS-34900) Naginator plugin throwing Null Pointer Exception

2016-06-03 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34900 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Naginator plugin throwing Null Pointer Exception  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: ikedam Path: src/main/java/com/chikli/hudson/plugin/naginator/NaginatorListener.java src/test/java/com/chikli/hudson/plugin/naginator/NaginatorListenerTest.java http://jenkins-ci.org/commit/naginator-plugin/ce036de06b64d734d89ed5a4cbc6d099e63be8a6 Log: Merge pull request #31 from ikedam/feature/

JENKINS-34900
_FixNPEforMavenModule 


JENKINS-34900
 Fix NPE when triggering single Maven module. 
Compare: https://github.com/jenkinsci/naginator-plugin/compare/27f461a9acbf...ce036de06b64 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [maven-plugin] (JENKINS-34900) Naginator plugin throwing Null Pointer Exception

2016-06-03 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34900 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Naginator plugin throwing Null Pointer Exception  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: ikedam Path: src/main/java/com/chikli/hudson/plugin/naginator/NaginatorListener.java http://jenkins-ci.org/commit/naginator-plugin/cbd89e56abe77230f0ad6eff43ee697b6d110925 Log: [FIXED JENKINS-34900] Fix NPE when single Maven module is triggered. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [maven-plugin] (JENKINS-34900) Naginator plugin throwing Null Pointer Exception

2016-06-03 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34900 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Naginator plugin throwing Null Pointer Exception  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: ikedam Path: src/test/java/com/chikli/hudson/plugin/naginator/NaginatorListenerTest.java http://jenkins-ci.org/commit/naginator-plugin/6762fc835f6be057c1dc1582b2736778975c5aa5 Log: 

JENKINS-34900
 Added a test to reproduce 

JENKINS-34900
. NPE when triggering single Maven module. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-34839) Add new provider UpstreamComitterSinceLastSuccess

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum assigned an issue to David van Laatum 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34839 
 
 
 
  Add new provider UpstreamComitterSinceLastSuccess  
 
 
 
 
 
 
 
 
 

Change By:
 
 David van Laatum 
 
 
 

Assignee:
 
 Alex Earl David van Laatum 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-35121) no "reply-to" header presented

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum closed an issue as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Closed due to no response 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-35121 
 
 
 
  no "reply-to" header presented  
 
 
 
 
 
 
 
 
 

Change By:
 
 David van Laatum 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-35289) The Content Token Reference shows 'ERROR: Failed to load help file: Server Error'

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum started work on  JENKINS-35289 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 David van Laatum 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-35121) no "reply-to" header presented

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum assigned an issue to David van Laatum 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35121 
 
 
 
  no "reply-to" header presented  
 
 
 
 
 
 
 
 
 

Change By:
 
 David van Laatum 
 
 
 

Assignee:
 
 Alex Earl David van Laatum 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-33980) Document (List) Pipeline features of email-ext-plugin

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum edited a comment on  JENKINS-33980 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Document (List) Pipeline features of email-ext-plugin  
 
 
 
 
 
 
 
 
 
 The reason triggers don't really make sense in a pipeline is because a plugin runs at a particular point in the pipeline not "at the end" so the correct way to implement the triggers in a pipeline is to call the plugin at the various points where you need to do it. for example to send an email on a failed build you could:{code:java}try {   // something that might fail} catch(e) { currentBuild.result = 'FAILURE' emailext body: e.toString(), subject: 'it failed :(', to: 'some...@noware.com'}{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-33980) Document (List) Pipeline features of email-ext-plugin

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum commented on  JENKINS-33980 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Document (List) Pipeline features of email-ext-plugin  
 
 
 
 
 
 
 
 
 
 
The reason triggers don't really make sense in a pipeline is because a plugin runs at a particular point in the pipeline not "at the end" so the correct way to implement the triggers in a pipeline is to call the plugin at the various points where you need to do it. for example to send an email on a failed build you could: 

 

try {
   // something that might fail
} catch(e) {
emailext body: e.toString(), subject: 'it failed :(', to: 'some...@noware.com'
}
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-33980) Document (List) Pipeline features of email-ext-plugin

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum assigned an issue to David van Laatum 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33980 
 
 
 
  Document (List) Pipeline features of email-ext-plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 David van Laatum 
 
 
 

Assignee:
 
 Alex Earl David van Laatum 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-34763) Email-ext plugin (culprits and committers) in Jenkins Pipeline

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum commented on  JENKINS-34763 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Email-ext plugin (culprits and committers) in Jenkins Pipeline  
 
 
 
 
 
 
 
 
 
 
As the new maintainer this will be one of my first priorities to try and get this working but I need to spend some time digging before I can answer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-34763) Email-ext plugin (culprits and committers) in Jenkins Pipeline

2016-06-03 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David van Laatum assigned an issue to David van Laatum 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34763 
 
 
 
  Email-ext plugin (culprits and committers) in Jenkins Pipeline  
 
 
 
 
 
 
 
 
 

Change By:
 
 David van Laatum 
 
 
 

Assignee:
 
 Alex Earl David van Laatum 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-35289) The Content Token Reference shows 'ERROR: Failed to load help file: Server Error'

2016-06-03 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-35289 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The Content Token Reference shows 'ERROR: Failed to load help file: Server Error'  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: David van Laatum Path: src/main/java/hudson/plugins/emailext/plugins/content/AbstractEvalContent.java src/main/java/hudson/plugins/emailext/plugins/content/JellyScriptContent.java src/main/java/hudson/plugins/emailext/plugins/content/ScriptContent.java src/main/java/hudson/plugins/emailext/plugins/content/TemplateContent.java http://jenkins-ci.org/commit/email-ext-plugin/5fd4108a221c8dea63f192302ba467b6dd6d9eaf Log: Fix for https://issues.jenkins-ci.org/browse/JENKINS-35289 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [maven-plugin] (JENKINS-35321) MavenModuleSetBuild swallows InterruptedIOException on doRun

2016-06-03 Thread ol...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 olamy commented on  JENKINS-35321 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: MavenModuleSetBuild swallows InterruptedIOException on doRun  
 
 
 
 
 
 
 
 
 
 
Arnaud Héritier sounds bad IMHO using the logger sounds a better option (but with the interesting stack trace!) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [pagerduty-plugin] (JENKINS-35353) PagerDuty plugin not compatible with Pipeline plugin

2016-06-03 Thread jswa...@alohaoi.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Swager created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35353 
 
 
 
  PagerDuty plugin not compatible with Pipeline plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Alexander Leibzon 
 
 
 

Components:
 

 pagerduty-plugin 
 
 
 

Created:
 

 2016/Jun/03 11:23 PM 
 
 
 

Environment:
 

 PagerDuty Plugin 0.2.4  Jenkins 1.651.1 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Jason Swager 
 
 
 
 
 
 
 
 
 
 
The PagerDuty Plugin is rather nice and works well from a FreeStyle job. Could it also be made to work from a Pipeline Job? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 

[JIRA] [script-security-plugin] (JENKINS-35352) unclassified new org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified field org.jenkinsci.plugins.workflow.support.steps.b

2016-06-03 Thread jriv...@osrfoundation.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jose Luis Rivero created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35352 
 
 
 
  unclassified new org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified field org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 script-security-plugin 
 
 
 

Created:
 

 2016/Jun/03 11:08 PM 
 
 
 

Labels:
 

 workflow 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jose Luis Rivero 
 
 
 
 
 
 
 
 
 
 
I'm not sure if this can be consider a bug but all the information I found using the exception name refers to classes not supported in the sandbox that should be so this case could be the another case. 
I did not find a way to allow this  

 
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified field org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper result
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.unclassifiedField(SandboxInterceptor.java:367)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onSetProperty(SandboxInterceptor.java:217)
	at org.kohsuke.groovy.sandbox.impl.Checker$5.call(Checker.java:297)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedSetProperty(Checker.java:294)
	at 

[JIRA] [active-directory-plugin] (JENKINS-3356) DNS lookup failed - Active Directory lookup broken

2016-06-03 Thread henry....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henry Yei edited a comment on  JENKINS-3356 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: DNS lookup failed - Active Directory lookup broken  
 
 
 
 
 
 
 
 
 
 I have the same issue with Jenkins 2.3 paired with 1.46 of the Active Directory plugin. I installed the plugin on this config only so far. intdomain.pvt. doesn't look like a valid domain namejavax.naming.NameNotFoundException: DNS name not found [response code 3]; remaining name 'eng.pvt.' at com.sun.jndi.dns.DnsClient.checkResponseCode(DnsClient.java:659) at com.sun.jndi.dns.DnsClient.isMatchResponse(DnsClient.java:577) at com.sun.jndi.dns.DnsClient.doUdpQuery(DnsClient.java:426) at com.sun.jndi.dns.DnsClient.query(DnsClient.java:211) at com.sun.jndi.dns.Resolver.query(Resolver.java:81) at com.sun.jndi.dns.DnsContext.c_getAttributes(DnsContext.java:430) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_getAttributes(ComponentDirContext.java:231) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(PartialCompositeDirContext.java:139) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(PartialCompositeDirContext.java:127) at javax.naming.directory.InitialDirContext.getAttributes(InitialDirContext.java:142) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.doValidate(ActiveDirectorySecurityRealm.java:412) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:49) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:44) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:106) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:44) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at javax.servlet.FilterChain$doFilter.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.ExceptionLoggingFilter.doFilter(ExceptionLoggingFilter.groovy:22) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at 

[JIRA] [active-directory-plugin] (JENKINS-3356) DNS lookup failed - Active Directory lookup broken

2016-06-03 Thread henry....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henry Yei commented on  JENKINS-3356 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: DNS lookup failed - Active Directory lookup broken  
 
 
 
 
 
 
 
 
 
 
I have the same issue with Jenkins 2.3 paired with 1.46 of the Active Directory plugin. I installed the plugin on this config only so far. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread b...@swimfrog.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Hawkins updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35349 
 
 
 
  java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 
 
First is screenshot of the multibranch config. 
Second is the branch that was detected during branch indexing. It's the only branch that currently has a Jenkinsfile. I can include the file contents if you want, but it seems to be failing before it even tries to read it. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Ben Hawkins 
 
 
 

Attachment:
 
 Screen Shot 2016-06-03 at 15.03.05.png 
 
 
 

Attachment:
 
 Screen Shot 2016-06-03 at 15.05.14.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [docker-build-step-plugin] (JENKINS-35322) NPE when trying to pull Docker image as first build step

2016-06-03 Thread stephen.don...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stephen Donner updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35322 
 
 
 
  NPE when trying to pull Docker image as first build step  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stephen Donner 
 
 
 
 
 
 
 
 
 
 Steps to Reproduce:1. With the above installed, create a job with "Execute Docker command" which does:Pull ImageName: owasp/zap2docker-weeklyTag: latestRegistry: [blank[ or DockerDocker Registry URL; https://hub.docker. com/ r/owasp/zap2docker-weekly/Registry Credentials: [none]2. In Jenkins, click "Build Now"Actual Results:I get the following stack trace/exception:Started by user anonymousBuilding in workspace /var/lib/jenkins/workspace/Docker-ZAP > /usr/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > /usr/bin/git config remote.origin.url https://github.com/stephendonner/docker-zap.git # timeout=10Fetching upstream changes from https://github.com/stephendonner/docker-zap.git > /usr/bin/git --version # timeout=10 > /usr/bin/git -c core.askpass=true fetch --tags --progress https://github.com/stephendonner/docker-zap.git +refs/heads/*:refs/remotes/origin/* > /usr/bin/git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > /usr/bin/git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10Checking out Revision 827ab1e2eb5888f8b612610fe3f6b9f62f7e219f (refs/remotes/origin/master) > /usr/bin/git config core.sparsecheckout # timeout=10 > /usr/bin/git checkout -f 827ab1e2eb5888f8b612610fe3f6b9f62f7e219f > /usr/bin/git rev-list 827ab1e2eb5888f8b612610fe3f6b9f62f7e219f # timeout=10ERROR: Build step failed with exceptionjava.lang.NullPointerException at com.github.dockerjava.jaxrs.DockerCmdExecFactoryImpl.init(DockerCmdExecFactoryImpl.java:105) at com.github.dockerjava.core.DockerClientImpl.withDockerCmdExecFactory(DockerClientImpl.java:64) at com.github.dockerjava.core.DockerClientBuilder.build(DockerClientBuilder.java:63) at org.jenkinsci.plugins.dockerbuildstep.DockerBuilder$DescriptorImpl.createDockerClient(DockerBuilder.java:132) at org.jenkinsci.plugins.dockerbuildstep.DockerBuilder$DescriptorImpl.getDockerClient(DockerBuilder.java:204) at org.jenkinsci.plugins.dockerbuildstep.DockerBuilder.perform(DockerBuilder.java:68) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Build step 'Execute Docker command' marked build as failureFinished: FAILURE 
 
 
 
 
 
 
 
 
 
 
 
 
  

[JIRA] [core] (JENKINS-35351) Rerun the running job to other availalbe slaves if connection channel lost in current slave

2016-06-03 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35351 
 
 
 
  Rerun the running job to other availalbe slaves if connection channel lost in current slave  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Jun/03 9:42 PM 
 
 
 

Environment:
 

 Ubuntu 14.04 server 64bit  Jenkins 1.651.1  oracle-java7 1.7.0_80 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Rick Liu 
 
 
 
 
 
 
 
 
 
 
Sometimes during the build, we randomly run into issues of:  java.io.IOException: Unexpected termination of the channel or hudson.remoting.ChannelClosedException: channel is already closed or java.io.EOFException 
where Jenkins master lost the connection channel  to the Jenkins slaves which are running the build job. When this happened, the build job is failed. This is inconvenient for long-build nightly jobs.  
Instead of failing the job, the Jenkins master to re-dispatch the same job (same build number / parameters / configurations) to the next available Jenkins slaves, and re-start over. 
 
 
 
 
 
 
 
 
 
 

[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto commented on  JENKINS-35349 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 
 
Ben Hawkins Could you send a screenshot with the job configuration? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto commented on  JENKINS-35349 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 
 
It is weird because there is a default implementation for SCMSource. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread b...@swimfrog.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Hawkins commented on  JENKINS-35349 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 
 
I'm using my own git server (gitlab) and using Git as the source. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto commented on  JENKINS-35349 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 
 
Ben Hawkins Are you sure that you are using Git as branch source? or GitHub? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35349 
 
 
 
  java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Recena Soto 
 
 
 

Comment:
 
 [~swimfrog] And for {{github-branch-source}}? Or are you using a git server? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto edited a comment on  JENKINS-35349 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 
 [~swimfrog] And for {{github-branch-source}}?  Or are you using a git server? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto commented on  JENKINS-35349 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 
 
Ben Hawkins And for github-branch-source? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread b...@swimfrog.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Hawkins edited a comment on  JENKINS-35349 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 
 branch-api is 1.9, scm-api is 1.2.  Tried downgrading branch-api to 1.7, but same issue occurred. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [core] (JENKINS-35350) New 2.7 install ignores the plugins I deselect and installs everything anyway.

2016-06-03 Thread matthewradam...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Adams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35350 
 
 
 
  New 2.7 install ignores the plugins I deselect and installs everything anyway.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Jun/03 8:59 PM 
 
 
 

Environment:
 

 ubuntu 14.04, jenkins 2.7, chrome, java 1.7 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Matthew Adams 
 
 
 
 
 
 
 
 
 
 
During fresh jenkins setup when I am asked to select my plugins, I uncheck things like ant, maven, git, etc, but they all get installed anyway. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 

[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread b...@swimfrog.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Hawkins commented on  JENKINS-35349 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 
 
branch-api is 1.9, scm-api is 1.2. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-plugin] (JENKINS-35340) ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

2016-06-03 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-35340 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.  
 
 
 
 
 
 
 
 
 
 
That was exactly the correct location, and I was very glad to see that someone already responded with answers to your questions. The Jenkins community tends to be very helpful to new users. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken

2016-06-03 Thread jakub.czapli...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jakub Czaplicki commented on  JENKINS-34948 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken  
 
 
 
 
 
 
 
 
 
 
Hi Pavel Dotsulenko, Many thanks for quick fix! I'll install it as soon as it's available. 
Earlier today I updated two other plugins that had a fresh new versions: 
 

https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Plugin
 

https://wiki.jenkins-ci.org/display/JENKINS/Branch+API+Plugin
 
 
At the same time I installed https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin I wanted to use it as a workaround. 
Now. It seems that one of the updates.. fixed the problem. The changelog in the Pipeline Multibranch Plugin says "Internal refactoring to expose multibranch functionality to other plugins" - perhaps this is what was causing the problem in the first place ? 
Anyhow, I am glad you've got a fix for this on your side.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto edited a comment on  JENKINS-35349 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 
 [~swimfrog] Which version of {{branch-api}} and {{scm-api }}are you using? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-client-plugin] (JENKINS-35338) Slave agent posts "Authentication Required" dialog when checking out from git

2016-06-03 Thread robert.s.ba...@unisys.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Baker commented on  JENKINS-35338 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Slave agent posts "Authentication Required" dialog when checking out from git  
 
 
 
 
 
 
 
 
 
 
Thanks Mark - I'll give that a try. Also appears to work when slave agent runs as a Windows service. This is not critical as I now have at least two workarounds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto commented on  JENKINS-35349 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 
 
Ben Hawkins Which version of branch-api and {{scm-api }}are you using? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [build-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name

2016-06-03 Thread devesh....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Devesh Kumar commented on  JENKINS-34512 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: error in build-name-setter plugin - Set build name  
 
 
 
 
 
 
 
 
 
 
oh just noticed that.. thanks for sticking with me for long. Really appreciated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken

2016-06-03 Thread pa...@assembla.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Dotsulenko closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34948 
 
 
 
  UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken  
 
 
 
 
 
 
 
 
 

Change By:
 
 Pavel Dotsulenko 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken

2016-06-03 Thread pa...@assembla.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Dotsulenko resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34948 
 
 
 
  UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken  
 
 
 
 
 
 
 
 
 

Change By:
 
 Pavel Dotsulenko 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken

2016-06-03 Thread pa...@assembla.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Dotsulenko commented on  JENKINS-34948 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken  
 
 
 
 
 
 
 
 
 
 
Hi Jakub Czaplicki, thanks for reporting the issue, new release with a bugfix has been pushed to jenkins repository. New plugin version will be available in the update center in about 8 hours. 
Also, you can download it here and install manually: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/assembla-auth/1.09/assembla-auth-1.09.hpi 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [workflow-multibranch-plugin] (JENKINS-35349) java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision

2016-06-03 Thread b...@swimfrog.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Hawkins created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35349 
 
 
 
  java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Manuel Recena Soto 
 
 
 

Components:
 

 workflow-multibranch-plugin 
 
 
 

Created:
 

 2016/Jun/03 8:17 PM 
 
 
 

Environment:
 

 Jenkins 1.651.2, Pipeline 2.1, Pipeline API 2.0, Pipeline Multibranch 2.6 (also tried with 2.3 and 2.5) 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Ben Hawkins 
 
 
 
 
 
 
 
 
 
 
After branch indexing, when I try to build a project in a MultiBranch workflow, I receive the following error in the build log: 

 
Started by user 
Setting origin to git@x/project.git
Fetching origin...
java.lang.NoSuchMethodError: jenkins.scm.api.SCMSource.getTrustedRevision(Ljenkins/scm/api/SCMRevision;Lhudson/model/TaskListener;)Ljenkins/scm/api/SCMRevision;
	at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:78)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:206)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:410)
Finished: FAILURE
 

 
A 

[JIRA] [build-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name

2016-06-03 Thread ljader...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Łukasz Jąder commented on  JENKINS-34512 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: error in build-name-setter plugin - Set build name  
 
 
 
 
 
 
 
 
 
 
Devesh Kumar thanks for the log - it clearly says that build failure is not from build-name-setter - it's caused by MSBuild plugin: 

Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [ssh-slaves-plugin] (JENKINS-18836) java.io.IOException: Unexpected termination of the channel

2016-06-03 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu commented on  JENKINS-18836 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.io.IOException: Unexpected termination of the channel  
 
 
 
 
 
 
 
 
 
 
Ubuntu 14.04 server 64-bit oracle-java7: 1.7.0_80 Jenkins: 1.651.1 LTS SSH Slaves plugin: 1.11 
The build sometimes randomly failed with this kind of error. 
This time happened in the post-build actions: FATAL: channel is already closed hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:578) at hudson.remoting.Request.call(Request.java:130) at hudson.remoting.Channel.call(Channel.java:780) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:953) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:540) at hudson.model.Run.execute(Run.java:1738) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:313) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

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

2016-06-03 Thread kwhetst...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone commented on  JENKINS-35348 
 
 
 
 
 
 
 
 
 
 

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

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [remoting] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel

2016-06-03 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu edited a comment on  JENKINS-6817 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel  
 
 
 
 
 
 
 
 
 
 Ubuntu 14.04 server 64-bitoracle-java7:  1.7.0_80Jenkins: 1.651.1 LTS In The build sometimes randomly failed with this kind of error.This time happened in  the post-build actions:FATAL: channel is already closedhudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:578) at hudson.remoting.Request.call(Request.java:130) at hudson.remoting.Channel.call(Channel.java:780) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:953) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:540) at hudson.model.Run.execute(Run.java:1738) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:313) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

2016-06-03 Thread kwhetst...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Kristin Whetstone 
 
 
 

Summary:
 
 Pipeline job loses connection with  slave  agent  node 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [core] (JENKINS-18781) Configurable channel timeout for slaves

2016-06-03 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu commented on  JENKINS-18781 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Configurable channel timeout for slaves  
 
 
 
 
 
 
 
 
 
 
Ubuntu 14.04 server 64-bit oracle-java7: 1.7.0_80 Jenkins: 1.651.1 LTS 
In the post-build actions: FATAL: channel is already closed hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:578) at hudson.remoting.Request.call(Request.java:130) at hudson.remoting.Channel.call(Channel.java:780) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:953) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:540) at hudson.model.Run.execute(Run.java:1738) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:313) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [core] (JENKINS-18781) Configurable channel timeout for slaves

2016-06-03 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu edited a comment on  JENKINS-18781 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Configurable channel timeout for slaves  
 
 
 
 
 
 
 
 
 
 Ubuntu 14.04 server 64-bitoracle-java7:  1.7.0_80Jenkins: 1.651.1 LTS In The build sometimes randomly failed with this kind of error.This time happened in  the post-build actions:FATAL: channel is already closedhudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:578) at hudson.remoting.Request.call(Request.java:130) at hudson.remoting.Channel.call(Channel.java:780) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:953) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:540) at hudson.model.Run.execute(Run.java:1738) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:313) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [remoting] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel

2016-06-03 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu commented on  JENKINS-6817 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel  
 
 
 
 
 
 
 
 
 
 
Ubuntu 14.04 server 64-bit oracle-java7: 1.7.0_80 Jenkins: 1.651.1 LTS 
In the post-build actions: FATAL: channel is already closed hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:578) at hudson.remoting.Request.call(Request.java:130) at hudson.remoting.Channel.call(Channel.java:780) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:953) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:540) at hudson.model.Run.execute(Run.java:1738) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:313) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

2016-06-03 Thread kwhetst...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kristin Whetstone created an issue 
 
 
 
 
 
 
 
 
 
 

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

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/Jun/03 7:52 PM 
 
 
 

Environment:
 

 Any version of Jenkins  pipeline 2 and higher 
 
 
 

Priority:
 
  Minor 
 
 
 

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

[JIRA] [core] (JENKINS-12543) CliAuthenticator (username/password) called too late to parse arguments (like job names)

2016-06-03 Thread jeberh...@helixeducation.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jay Atwork edited a comment on  JENKINS-12543 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CliAuthenticator (username/password) called too late to parse arguments (like job names)  
 
 
 
 
 
 
 
 
 
 This issue has broken CLI operation for me.  I am using Windows and can not use  anonymous read access on Jobs nor  curl due to organizational restrictions in our prod environment and we need to be able to run builds via the CLI.  I am on Jenkins 1.646, perhaps would updating to a newer version of Jenkins resolve this issue?  I doubt it as this issue is still open.  Is there a way to get the name of the jobs that the build method needs, since it is not what is provided from list-jobs? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [build-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name

2016-06-03 Thread devesh....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Devesh Kumar commented on  JENKINS-34512 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: error in build-name-setter plugin - Set build name  
 
 
 
 
 
 
 
 
 
 
Here are the logs, I have removed Visual Studio logs for clarity: 
Started by user Devesh Kumar [EnvInject] - Loading node environment variables. Building in workspace D:\Jenkins\workspace\CCTFinanceBroker Updating https://***MASKED/trunk/src/FinanceBroker at revision '2016-04-28T16:51:59.368 -0400' At revision 49956 no change for https://***MASKED/trunk/src/FinanceBroker since the previous build No emails were triggered. Set build name. New build name is '#553' Path To MSBuild.exe: C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe Executing the command cmd.exe /C " C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe /t:Clean,Rebuild "/p:Configuration=Release,platform=Any CPU" FinanceBrokerServices\FinanceBroker.sln " && exit %%ERRORLEVEL%% from D:\Jenkins\workspace\CCTFinanceBroker [CCTFinanceBroker] $ cmd.exe /C " C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe /t:Clean,Rebuild "/p:Configuration=Release,platform=Any CPU" FinanceBrokerServices\FinanceBroker.sln " && exit %%ERRORLEVEL%% Microsoft (R) Build Engine version 4.0.30319.34209 [Microsoft .NET Framework, version 4.0.30319.34209] Copyright (C) Microsoft Corporation. All rights reserved. 
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch. Build started 4/28/2016 4:52:02 PM. Project "D:\Jenkins\workspace\CCTFinanceBroker\FinanceBrokerServices\FinanceBroker.sln" on node 1 (Clean;Rebuild target(s)). ValidateSolutionConfiguration: Building solution configuration "Release|Any CPU". * * * * Visual Studio build logs MASKED * * * * * Time Elapsed 00:00:00.32 Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure Set build name. New build name is '#553' Variable with name 'BUILD_DISPLAY_NAME' already exists, current value: '#553', new value: '#553' Recording NUnit tests results Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Sending email to: * Finished: FAILURE 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [core] (JENKINS-12543) CliAuthenticator (username/password) called too late to parse arguments (like job names)

2016-06-03 Thread jeberh...@helixeducation.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jay Atwork commented on  JENKINS-12543 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CliAuthenticator (username/password) called too late to parse arguments (like job names)  
 
 
 
 
 
 
 
 
 
 
This issue has broken CLI operation for me. I am using Windows and can not use curl due to organizational restrictions in our prod environment and we need to be able to run builds via the CLI. I am on Jenkins 1.646, perhaps would updating to a newer version of Jenkins resolve this issue? I doubt it as this issue is still open. Is there a way to get the name of the jobs that the build method needs, since it is not what is provided from list-jobs? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-client-plugin] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use

2016-06-03 Thread a...@gonebusy.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Agranov commented on  JENKINS-30318 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use  
 
 
 
 
 
 
 
 
 
 
I haven't tracked down the exact code that limits to clone/pull but their own man-page refers to their supported functionality: https://github.com/github/git-lfs/blob/master/docs/man/git-lfs-install.1.ronn#L27-L30 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [openstack-cloud-plugin] (JENKINS-35347) unable to test connection when using keystone V3 API

2016-06-03 Thread y...@mvista.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yufen Kuo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35347 
 
 
 
  unable to test connection when using keystone V3 API  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 openstack-cloud-plugin 
 
 
 

Created:
 

 2016/Jun/03 7:21 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Yufen Kuo 
 
 
 
 
 
 
 
 
 
 
Cannot connect to specified cloud, please check the identity and credentials: Not Found 
ClientResponseException {message=Not Found, status=404, status-code=NOT_FOUND} 
 at org.openstack4j.core.transport.HttpExceptionHandler.mapException(HttpExceptionHandler.java:38) at org.openstack4j.core.transport.HttpExceptionHandler.mapException(HttpExceptionHandler.java:23) at org.openstack4j.openstack.internal.OSAuthenticator.authenticateV2(OSAuthenticator.java:120) at org.openstack4j.openstack.internal.OSAuthenticator.invoke(OSAuthenticator.java:50) at org.openstack4j.openstack.client.OSClientBuilder$ClientV2.authenticate(OSClientBuilder.java:117) at org.openstack4j.openstack.client.OSClientBuilder$ClientV2.authenticate(OSClientBuilder.java:81) at jenkins.plugins.openstack.compute.internal.Openstack.(Openstack.java:95) at jenkins.plugins.openstack.compute.internal.Openstack$Factory.getOpenstack(Openstack.java:466) at jenkins.plugins.openstack.compute.internal.Openstack$FactoryEP.get(Openstack.java:450) at jenkins.plugins.openstack.compute.JCloudsCloud$DescriptorImpl.doTestConnection(JCloudsCloud.java:478) 
 
 
 
 
 
 
 
 
  

[JIRA] [delivery-pipeline-plugin] (JENKINS-35346) Description text is deleted after saving changes in Edit View

2016-06-03 Thread jeff.crawfo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Crawford created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35346 
 
 
 
  Description text is deleted after saving changes in Edit View  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Patrik Boström 
 
 
 

Components:
 

 delivery-pipeline-plugin 
 
 
 

Created:
 

 2016/Jun/03 7:16 PM 
 
 
 

Environment:
 

 Jenkins: 1.6.45  Delivery Pipeline Plugin: 0.9.11  CentOS 7 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jeff Crawford 
 
 
 
 
 
 
 
 
 
 
In the Delivery Pipeline View, I use the Jenkins' built-in Job description text field to provide instructions on how to use the pipeline and, specifically, what each job does in the pipeline. After saving in Edit View this description is always deleted. 
Steps to reproduce: 1) Click on "add description" in the Delivery Pipeline view. 2) Add some text. 3) Click on Edit View and click OK. 4) Text in description box is deleted. 
 
 
 
 
 
 
 
 
 
 
 
 

 
   

[JIRA] [stash-pullrequest-builder-plugin] (JENKINS-34847) Missing parameters

2016-06-03 Thread daniel.bar...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Barcay commented on  JENKINS-34847 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing parameters  
 
 
 
 
 
 
 
 
 
 
Thanks Dieter... I'll give this a shot.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-plugin] (JENKINS-35340) ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

2016-06-03 Thread freddy.paxt...@hotmail.co.uk (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Freddy Paxton commented on  JENKINS-35340 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.  
 
 
 
 
 
 
 
 
 
 
Sorry Mark, I think I have now posted in the correct place. Is it the Google group for Jenkins Users? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-client-plugin] (JENKINS-35338) Slave agent posts "Authentication Required" dialog when checking out from git

2016-06-03 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite edited a comment on  JENKINS-35338 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Slave agent posts "Authentication Required" dialog when checking out from git  
 
 
 
 
 
 
 
 
 
 I've seen the same condition in Windows slave based automated tests of the git client plugin.  I don't know when I will have a chance to investigate it further, but I think the case is visible when the git client plugin automated tests run on a Jenkins slave hosted on Windows. The work around is to install and use command line git on the Windows slave. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-client-plugin] (JENKINS-35338) Slave agent posts "Authentication Required" dialog when checking out from git

2016-06-03 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-35338 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Slave agent posts "Authentication Required" dialog when checking out from git  
 
 
 
 
 
 
 
 
 
 
I've seen the same condition in Windows slave based automated tests of the git client plugin. I don't know when I will have a chance to investigate it further, but I think the case is visible when the git client plugin automated tests run on a Jenkins slave hosted on Windows. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [acceptance-test-harness] (JENKINS-34004) Git Plugin ATH Tests may fail if global identity not configured

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto edited a comment on  JENKINS-34004 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git Plugin ATH Tests may fail if global identity not configured  
 
 
 
 
 
 
 
 
 
 This The  PR involved here was merged. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [acceptance-test-harness] (JENKINS-34004) Git Plugin ATH Tests may fail if global identity not configured

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto resolved as Done 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34004 
 
 
 
  Git Plugin ATH Tests may fail if global identity not configured  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Recena Soto 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-plugin] (JENKINS-35340) ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

2016-06-03 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Freddy Paxton welcome to Jenkins. Glad to have you learning. 
We find it is much more effective for new user questions to be raised on the Jenkins mailing list rather than being raised as bug reports. Could you bring your questions to the mailing list so that you can have the benefit of help from many more people than just the maintainer of the git plugin? 
In your specific case, you may want to watch the screencast I created a few years ago called "Jenkins in Five Minutes".  
You may also want to consider learning about "ant" or "maven" or "gradle" as tools that can help you compile your software.  
Alternately, you could open a free Java integrated development environment (Netbeans is the one I use, others use Eclipse) and use it to create a project for your HelloWorld test. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-35340 
 
 
 
  ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [git-plugin] (JENKINS-33874) Upgrade git-plugin to new parent POM

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto resolved as Done 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The PR involved here was merged. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33874 
 
 
 
  Upgrade git-plugin to new parent POM  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Recena Soto 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [acceptance-test-harness] (JENKINS-34004) Git Plugin ATH Tests may fail if global identity not configured

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34004 
 
 
 
  Git Plugin ATH Tests may fail if global identity not configured  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Recena Soto 
 
 
 

Resolution:
 
 Done 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [acceptance-test-harness] (JENKINS-34004) Git Plugin ATH Tests may fail if global identity not configured

2016-06-03 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto closed an issue as Done 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
This PR involved here was merged. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34004 
 
 
 
  Git Plugin ATH Tests may fail if global identity not configured  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Recena Soto 
 
 
 

Status:
 
 In Progress Closed 
 
 
 

Resolution:
 
 Done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35343) Allow to delete each bundle(s)

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier started work on  JENKINS-35343 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35342) Allow to download a bundle

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier started work on  JENKINS-35342 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35341) List bundles stored on the instance

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier started work on  JENKINS-35341 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35345) Allow to automatically purge old bundles

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35345 
 
 
 
  Allow to automatically purge old bundles  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 
 
 
 
 
 
 
 For each bundle listed in the UI A configuration panel  ( see JENKINS-35341) the administrator must be able to browse its content.Maybe something like  in  the workspace browse which could  Jenkins global config ?) should  allow  us  to  preview the content of each file in a bundle.The main "issue" is to unpack  configure how many  ( in memory numbers  ?  days ?  )  bundle we want to keep and to delete automatically  the  content of archives  ones which are too old. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35345) Allow to automatically purge old bundles

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35345 
 
 
 
  Allow to automatically purge old bundles  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Priority:
 
 Major Minor 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35345) Allow to automatically purge old bundles

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35345 
 
 
 
  Allow to automatically purge old bundles  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Minudika Malshan 
 
 
 

Components:
 

 support-core-plugin 
 
 
 

Created:
 

 2016/Jun/03 6:08 PM 
 
 
 

Labels:
 

 gsoc gsoc-2016 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Arnaud Héritier 
 
 
 
 
 
 
 
 
 
 
For each bundle listed in the UI (see JENKINS-35341) the administrator must be able to browse its content. Maybe something like in the workspace browse which could allow us to preview the content of each file in a bundle. The main "issue" is to unpack (in memory ? ) the content of archives 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 

[JIRA] [support-core-plugin] (JENKINS-35341) List bundles stored on the instance

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35341 
 
 
 
  List bundles stored on the instance  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Sprint:
 
 Bundles management UI Sprint 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35344) Allow to browse the content of bundles

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35344 
 
 
 
  Allow to browse the content of bundles  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Sprint:
 
 Bundles management UI Sprint 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35343) Allow to delete each bundle(s)

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35343 
 
 
 
  Allow to delete each bundle(s)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Sprint:
 
 Bundles management UI Sprint 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35342) Allow to download a bundle

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35342 
 
 
 
  Allow to download a bundle  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Sprint:
 
 Bundles management UI Sprint 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35344) Allow to browse the content of bundles

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35344 
 
 
 
  Allow to browse the content of bundles  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 
 
 
 
 
 
 
 For each bundle listed in the UI (see JENKINS-35341) the administrator must be able to  delete it  browse its content.  It should be able to delete all of themA confirmation panel should be triggered to validate such action*Nice to have:* Like Maybe something like  in the  plugins manager a checkbox  workspace browse which could  allow  us  to  select  preview the content of  each  entry,  file in  a  link allow  bundle.The main "issue" is  to  select or unselect all  unpack (in memory ? ) the content  of  them and an action allow to delete all selected entries  archives 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35344) Allow to browse the content of bundles

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35344 
 
 
 
  Allow to browse the content of bundles  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 
 
 
 
 
 
 
 For each bundle listed in the UI (see JENKINS-35341) the administrator must be able to delete itIt should be able to delete all of themA confirmation panel should be triggered to validate such action * Nice to have: *  Like in the plugins manager a checkbox allow to select each entry, a link allow to select or unselect all of them and an action allow to delete all selected entries 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35342) Allow to download a bundle

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35342 
 
 
 
  Allow to download a bundle  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 
 
 
 
 
 
 
 For each bundle listed in the UI (see JENKINS-35341) the administrator should be able to download it *Nice to have:* Like in the plugins manager a checkbox allow to select each entry, a link allow to select or unselect all of them and an action allow to download all selected entries 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35344) Allow to browse the content of bundles

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35344 
 
 
 
  Allow to browse the content of bundles  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Minudika Malshan 
 
 
 

Components:
 

 support-core-plugin 
 
 
 

Created:
 

 2016/Jun/03 5:57 PM 
 
 
 

Labels:
 

 gsoc gsoc-2016 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Arnaud Héritier 
 
 
 
 
 
 
 
 
 
 
For each bundle listed in the UI (see JENKINS-35341) the administrator must be able to delete it It should be able to delete all of them A confirmation panel should be triggered to validate such action 
Nice to have: Like in the plugins manager a checkbox allow to select each entry, a link allow to select or unselect all of them and an action allow to delete all selected entries 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
  

[JIRA] [support-core-plugin] (JENKINS-35343) Allow to delete each bundle(s)

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35343 
 
 
 
  Allow to delete each bundle(s)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 
 
 
 
 
 
 
 List bundles stored on For each bundle listed in  the  instance  UI  ( name + creation date + size see JENKINS-35341 )  the administrator must be able to delete itIt should be able to delete all of themA confirmation panel should be triggered to validate such actionNice to have: Like in the plugins manager a checkbox allow to select each entry, a link allow to select or unselect all of them and an action allow to delete all selected entries 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35343) Allow to delete each bundle(s)

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35343 
 
 
 
  Allow to delete each bundle(s)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Minudika Malshan 
 
 
 

Components:
 

 support-core-plugin 
 
 
 

Created:
 

 2016/Jun/03 5:53 PM 
 
 
 

Labels:
 

 gsoc gsoc-2016 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Arnaud Héritier 
 
 
 
 
 
 
 
 
 
 
List bundles stored on the instance (name + creation date + size) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 

[JIRA] [support-core-plugin] (JENKINS-35341) List bundles stored on the instance

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35341 
 
 
 
  List bundles stored on the instance  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Issue Type:
 
 Bug New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35342) Allow to download a bundle

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35342 
 
 
 
  Allow to download a bundle  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 
 
 
 
 
 
 
 List bundles stored on For each bundle listed in  the  instance  UI  ( name + creation date + size see JENKINS-35341 )  the administrator should be able to download it 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35342) Allow to download a bundle

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35342 
 
 
 
  Allow to download a bundle  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Issue Type:
 
 Bug New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-35342) Allow to download a bundle

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35342 
 
 
 
  Allow to download a bundle  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Minudika Malshan 
 
 
 

Components:
 

 support-core-plugin 
 
 
 

Created:
 

 2016/Jun/03 5:50 PM 
 
 
 

Labels:
 

 gsoc gsoc-2016 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Arnaud Héritier 
 
 
 
 
 
 
 
 
 
 
List bundles stored on the instance (name + creation date + size) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 

[JIRA] [support-core-plugin] (JENKINS-35341) List bundles stored on the instance

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35341 
 
 
 
  List bundles stored on the instance  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Labels:
 
 gsoc gsoc-2016 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-21670) Option to anonymize customer labels

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-21670 
 
 
 
  Option to anonymize customer labels  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Epic Name:
 
 Bundle anonymization 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [support-core-plugin] (JENKINS-33091) Allow to create an issue and submit a bundle into the OSS tracker

2016-06-03 Thread aherit...@apache.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud Héritier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33091 
 
 
 
  Allow to create an issue and submit a bundle into the OSS tracker  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud Héritier 
 
 
 

Epic Name:
 
 Bundle uploader 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-plugin] (JENKINS-35340) ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

2016-06-03 Thread freddy.paxt...@hotmail.co.uk (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Freddy Paxton assigned an issue to Mark Waite 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35340 
 
 
 
  ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Freddy Paxton 
 
 
 

Assignee:
 
 Freddy Paxton Mark Waite 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


  1   2   3   >