[JIRA] (JENKINS-32532) User build variables are not injected on "Before Build" step

2016-10-25 Thread electric.blue.jag...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 John Tal commented on  JENKINS-32532  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User build variables are not injected on "Before Build" step   
 

  
 
 
 
 

 
 +1 for the 1 hour fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] [project-inheritance-plugin] (JENKINS-22885) Creation of Inheritance Project throws Exception

2016-05-26 Thread electric.blue.jag...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Tal commented on  JENKINS-22885 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Creation of Inheritance Project throws Exception  
 
 
 
 
 
 
 
 
 
 
Bump, this is still and issue with latest version of this plugin 1.5.3 and Jenkins 2.5. Can we get a fix ?? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

2016-05-25 Thread electric.blue.jag...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Tal edited a comment on  JENKINS-18935 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make Subversion plugin support Subversion 1.8  
 
 
 
 
 
 
 
 
 
 This issue occurs in RHEL 5.11 with Jenkins 2.5 and the SVN plugin 2.5.7.Base svn installed on RHEL is svn, version 1.8.15 (r1718365)[ERROR] The svn command failed.[ERROR] Command output:[ERROR] svn: E155036: Please see the 'svn upgrade' commandsvn: E155036: The working copy at '/snipped'is too old (format 8) to work with client version '1.8.15 (r1718365)' (expects format 31). You need to upgrade the working copy first. It's not clear This issue resolved by Manage Jenkins -> Configure system -> Subversion Workspace Version update  from  this bug report how  the  issue is fixed if it's still happening  default of 1 . 4 to 1.8  (seems like at least 1.7 should be default) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

2016-05-25 Thread electric.blue.jag...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Tal edited a comment on  JENKINS-18935 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make Subversion plugin support Subversion 1.8  
 
 
 
 
 
 
 
 
 
 This issue occurs in RHEL 5.11 with Jenkins 2.5 and the SVN plugin 2.5.7.Base svn installed on RHEL is svn, version 1.8.15 (r1718365)[ERROR] The svn command failed.[ERROR] Command output:[ERROR] svn: E155036: Please see the 'svn upgrade' commandsvn: E155036: The working copy at '/snipped'is too old (format 8) to work with client version '1.8.15 (r1718365)' (expects format 31). You need to upgrade the working copy first. It's not clear from this bug report how the issue is fixed if it's still happening. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

2016-05-25 Thread electric.blue.jag...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Tal commented on  JENKINS-18935 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make Subversion plugin support Subversion 1.8  
 
 
 
 
 
 
 
 
 
 
This issue occurs in RHEL 5.11 with Jenkins 2.5 and the SVN plugin 2.5.7. Base svn installed on RHEL is svn, version 1.8.15 (r1718365) [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: E155036: Please see the 'svn upgrade' command svn: E155036: The working copy at '/snipped' is too old (format 8) to work with client version '1.8.15 (r1718365)' (expects format 31). You need to upgrade the working copy first. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-35050) Create a new node causes jenkins to go into a 100% cpu usage spin

2016-05-24 Thread electric.blue.jag...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Tal commented on  JENKINS-35050 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create a new node causes jenkins to go into a 100% cpu usage spin  
 
 
 
 
 
 
 
 
 
 
Also solved for editing existing nodes imported/copied from earlier versions of Jenkins. What version of Jenkins will have 2.0.3 packaged/recommended/referenced? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.