Hello community, I'm a novice in Jenkins and I need a piece of advise. Our build process is very simple: check-out, call an Ant script for the build, and send an email with the result. Unfortunately we are using a proprietary system for tasks tracking and we do not envision to integrate it with Jenkins. Nevertheless we need to report in the email the list of the tasks completed for the build, so we need to provide the tasks description in the build (mentioning the tasks in the commits to Version Control System (VCS) is not an appropriate practice). For this purpose I made the Jenkins build script parametrized and provided a text field for the tasks descriptions, which is usually filled with copy-paste. Now the problem is that the call of the Ant build task sometimes breaks because the tasks description list (at least): - could be long; - could include symbols that are not appropriate for the command line.
Currently I can see two approaches to solve this problem: 1. Skip the parameter value when calling the Ant task; 2. Manipulate the parameter's value in order to remove/replace inappropriate symbols. Unfortunately I do not see Jenkins to provide any tools to implement these approaches (I would prefer the first one). Please advise how to resolve this problem. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
