New Jenkins User: Build Step Windows Batch Script missing/not-shown when trying to (re)Configure build

16 views
Skip to first unread message

Eric Edberg

unread,
Mar 31, 2015, 11:18:18 AM3/31/15
to jenkins...@googlegroups.com
Hello,

I am a new Jenkins user (SA) configuring Jenkins for use executing build jobs on collections of remote nodes.  Installing Jenkins and several slaves was pretty easy enough.  Writing a test Project that executed a Windows Batch Script build step also work too.  Email-ext plugin worked as expected.

Wanted to "edit" the original Build Step and change the Windows Batch script name and test parameter passing.   When I selected the Project -> Configure it loaded but the Build "step" I had originally defined was missing so I cannot change the program executable PATH or test adding variables/options for this build step.

Question:  Is this a known issue and/or how do I (re)Configure a Project Build Step?

After creating the initial job I updated all plugins and added a few, Email Extension, Config File Provider, Green Balls....

When I "copy" an existing project to a new one it also worked correctly but is missing the build step when I try to initially configure it .

Any hints on what may be the issue? 

Thanks for any hints....

Eric L. Edberg



Eric Edberg

unread,
Mar 31, 2015, 12:00:13 PM3/31/15
to jenkins...@googlegroups.com

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

Reply all
Reply to author
Forward
0 new messages