After posting the article above I deleted the 3 offending jobs missing the
Build Step and recreated them again. Once I did that the new build jobs
correctly showed the Windows Batch build step and I was able to correctly
edit it's parameters....
--> I assume that the Build Step may not have even been executing on the
remote systems at this point.
I reviewed the logfile output of the script and it appears that build step
was lost at some point during the SW or plugin upgrade...
Anyway, I think I am ok at this point.
I'll hijack this issue with another question :-)
- What is the easiest way when you are "Configuring" a build to specify
arguments to an executable?
- Classically, I'd like to be able to pass arguments on the CLI command
line of the script using form fields input in the build job (if possible)
One option is to pass an XML file to the workspace. I believe that there
are ways to attach a file to the build job that would reside in the
workspace.
Q: is there a way to build the XML file with pre-defined questions/answers
(var/value) pairs?
Any pointers where to look for answers?
Thanks again,
Eric L. Edberg
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/a98c4302-c5f1-450f-a780-a634d3f0085f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
