[JIRA] (JENKINS-40179) Stray comma at end of HTML value passed to build step

2016-12-05 Thread bitbucket...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Currier commented on  JENKINS-40179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stray comma at end of HTML  value passed to build step   
 

  
 
 
 
 

 
 After opening this issue I found that it is a duplicate of JENKINS-36806. The "fix" is to check the "Omit value field" box on the Active Choices Reactive Reference Parameter. While JENKINS-36806 was closed as "Not A Defect", I suggest implementing one or more of the following changes: A) Make the default behavior be that all Active Choice parameters get passed to the build steps and then get rid of the unintuitive "Omit value field" option. The whole point of build parameters is to modify build steps. B) Change the default of "Omit value field" to checked. At least for Formatted HTML and Formatted Hidden HTML parameters, this seems like the right answer somewhere between 99% and 100% of the time. C) Change the name of "Omit value field" to something meaningful to us mere mortals. Something along the lines of "Yes, I want my build parameter passed to my build step". But with fewer words, of course!  B)   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40179) Stray comma at end of HTML value passed to build step

2016-12-01 Thread bitbucket...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Currier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40179  
 
 
  Stray comma at end of HTML  value passed to build step   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Bruno P. Kinoshita  
 
 
Components: 
 active-choices-plugin  
 
 
Created: 
 2016/Dec/02 2:10 AM  
 
 
Environment: 
 Jenkins 2.19.4  Active Choices Plug-in 1.5.2  Windows 7  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Keith Currier  
 

  
 
 
 
 

 
 I have a build job with multiple Active Choices Reactive Reference Parameters. If the Choice Type is set to either "Formatted HTML" or "Formatted Hidden HTML" the parameter value is supposed to be passed to each build step as an environment variable. The problem is that the value passed has an extraneous comma (",") at the end of it. For example, if I set the value of parameter "FOO" to "BAR", the value passed to my build step is "BAR,".  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
  

[JIRA] [credentials-plugin] (JENKINS-35075) Credentials Plugin 2.x breaks node configuration page

2016-05-25 Thread bitbucket...@yahoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keith Currier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35075 
 
 
 
  Credentials Plugin 2.x breaks node configuration page  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 stephenconnolly 
 
 
 

Components:
 

 credentials-plugin 
 
 
 

Created:
 

 2016/May/23 9:01 PM 
 
 
 

Environment:
 

 Windows Jenkins 1.651.2 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Keith Currier 
 
 
 
 
 
 
 
 
 
 
When I upgrade the Credentials Plugin to version 2.0 or later, I can no longer add new nodes or reconfigure existing nodes. 
Steps to reproduce... 
 

Do fresh install of Jenkins 1.651.2 on Windows
 

Verify that you can add a new slave node and reconfigure an existing node
 

Upgrade Credentials Plugin to version 2.0 or 2.0.1
 

Attempt to add a new node or reconfigure an existing node
 
 

[JIRA] [ant-plugin] (JENKINS-33712) Empty parameterized build properties not quoted when passed to ant

2016-05-12 Thread bitbucket...@yahoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keith Currier commented on  JENKINS-33712 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Empty parameterized build properties not quoted when passed to ant  
 
 
 
 
 
 
 
 
 
 
Looks good. I tried Ant Plugin 1.3 with Jenkins 2.1, 2.2, and 2.3. In all cases, the behavior was as expected. 
Thanks for the help! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ant-plugin] (JENKINS-33712) Empty parameterized build properties not quoted when passed to ant

2016-03-21 Thread bitbucket...@yahoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keith Currier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33712 
 
 
 
  Empty parameterized build properties not quoted when passed to ant  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 build.xml, config.xml 
 
 
 

Components:
 

 ant-plugin, core 
 
 
 

Created:
 

 2016/Mar/22 1:12 AM 
 
 
 

Environment:
 

 Jenkins 1.654  Ant Plugin 1.2  Windows 7 x86_64 (master and slave)  Apache Ant 1.9.6 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Keith Currier 
 
 
 
 
 
 
 
 
 
 
I have a parameterized build job that defines multiple string parameters. The main build step in that job is "Invoke Ant". 
Even though I do not define any "Properties" under "Invoke Ant", all of my job parameters are being passed to ant using "-D=". That is fine, except when one of my string parameters is blank. In that case Jenkins passes ant "-D=", which causes ant to barf. 
If a job parameter is blank then either it should not be passed to ant, or (probably better) a quoted empty string ("") should be passed to ant.