[JIRA] [conditional-buildstep-plugin] (JENKINS-25763) Conditional steps plugin with wrong syntax parameters

2014-11-25 Thread wojciech.hajducze...@gmail.com (JIRA)














































Wojciech Hajduczenia
 commented on  JENKINS-25763


Conditional steps plugin with wrong syntax parameters















If workload to implement some syntax verification for the options/makros used in plugins is to great, please close this issue with appropriate comment attached. As mentioned, in text editors some verification is used tracking if brackets or other special characters are used in tandems, opening/closing given functionality completing the correct syntax. 
A small thing like a missing , or " may be difficult and very frustrating to track in bigger jobs if the proper syntax is not used. An assumption that the person using a given plugin, knows correct syntax is spot on, but we are all human and mistakes lie in our nature.

Thanks anyhow for the time and support.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups 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] [conditional-buildstep-plugin] (JENKINS-25763) Conditional steps plugin with wrong syntax parameters

2014-11-25 Thread wojciech.hajducze...@gmail.com (JIRA)












































 
Wojciech Hajduczenia
 edited a comment on  JENKINS-25763


Conditional steps plugin with wrong syntax parameters
















If workload to implement some syntax verification for the options/makros used in plugins is to great, please close this issue with appropriate comment attached. As mentioned, in text editors some verification is used tracking if brackets or other special characters are used in tandems, opening/closing given functionality completing the correct syntax. 
A small thing like a missing , or " may be difficult and very frustrating to track in bigger jobs if the proper syntax is not used. An assumption that the person using a given plugin, knows correct syntax is spot on, but we are all human and mistakes lie in our nature.

Nevertheless this could be an interesting option in the future releases.

Thanks for the time and support.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups 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] [conditional-buildstep-plugin] (JENKINS-25763) Conditional steps plugin with wrong syntax parameters

2014-11-24 Thread wojciech.hajducze...@gmail.com (JIRA)














































Wojciech Hajduczenia
 created  JENKINS-25763


Conditional steps plugin with wrong syntax parameters















Issue Type:


Bug



Assignee:


Dominik Bartholdi



Attachments:


config.PNG, execution.PNG



Components:


conditional-buildstep-plugin



Created:


24/Nov/14 4:11 PM



Description:


While running the plugin and having the typo/wrong syntax in "token" field (missing " in my case), allows to execute further steps even when in advanced options of this plugin "fail the build" is set on evaluation failure (see config.png for setup example). Execution.png has the steps that are placed after the plugin that is having bad behaviour and they are executed.

In my opinion there should be a syntax verification performed there, and when syntax is not correct, should fail the job at this step or at least this situation should be treated as condition evaluation failure.

If i can assist with more information please let me know to improve this wonderfull tool.
Thank you.




Environment:


RH 6.5




Project:


Jenkins



Labels:


plugins




Priority:


Major



Reporter:


Wojciech Hajduczenia

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups 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] [conditional-buildstep-plugin] (JENKINS-25763) Conditional steps plugin with wrong syntax parameters

2014-11-24 Thread wojciech.hajducze...@gmail.com (JIRA)














































Wojciech Hajduczenia
 commented on  JENKINS-25763


Conditional steps plugin with wrong syntax parameters















Any chances that it can evaluate if the syntax is correct or not when the first " is entered?
Dont know what are the exact rulles for the syntax there but i think that when " is entered it should expect a second to close like it is in shell unless tehre is an escape character cancelling the propper usage.
Sorry if i have opened this issue and took your time but i am teaching a friend from work some tricks and i did a mistake on purpose and i was suprised that the build not failed and stayed "green" and executed the tasks that were later indicated. I though that if tghe condition is not met or something is not correct with that (syntax error) it would behave like the verification failure. and would fail the job as it was indicated in the advanced option. Could use some help with configuring something like that to fail the job in case the condition is not met or syntax is wrong.

Thanks



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups 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.