Skip to main content

Windows .BAT Script to launch task, then loop until done

My last post described my discovery of the Windows Schtasks.exe utility to trigger via the command-line a scheduled task on a local or - more relevant to the challenges I was facing - on a remote server. I described its ability to query the state of the task, and to launch it.

Of course, since my whole purpose was to automate a tedious manual section of our build process, Schtasks.exe is helpful but hardly the end of the story.

To benefit from that new knowledge, I now need to create a Windows shell script that our Continuous-Integration tool Jenkins can launch. This post is almost a stream-of-consciousness blog as I play with this problem.

The requirements are that the script launch the remote scheduled task, poll its status until it is complete, and end with an appropriate result code. Some minimal logging of activity would also be nice.

To begin, I created a .BAT file and created a labelled section to trigger the remote task:
REM  QUESTION: What if it is already running? Should we wait? Abnormal-end? Skip?
schtasks /run /s MyRemoteServer /tn MyBuildTask

The REMark line raises a question that I will need to think about later. The remote scheduled task takes about 10 minutes to run (the manual steps took 20-30 minutes, so that's a vast improvement!). It might already be running. If it is, we should wait until it finishes. The Task Scheduler itself probably provides some assistance with this, so I make a note to look into this further, and return to the problem at hand.

I learned last time that I can query the state of the scheduled task with:
schtasks /v /query /s MyRemoteServer /tn MyBuildTask /FO LIST

But now I need to process the results and determine if the task has finished successfully, is still running, or is in some other state. By adding something like the following, I can parse the formatted output from the query:

FOR /F "tokens=1,2* delims=:" %%a in ('schtasks /v /query /s MyRemoteServer /tn MyBuildTask /FO LIST') DO (
if %%a==Status SET statusStr=%%b
if %%a==Last^ Result SET resultStr=%%b

Full confession: it took me a while to realize that I needed to escape the space in the comparison string. I was getting no value in the resultStr variable with "Last Result" with either single quotes, double quotes, or no quotes. But preceding it with the caret ^ character tells the IF comparison to treat the space as part of the string.

There is another step needed. The LIST formatted output has lots of spaces coming before the actual value, something like "              Running". We need to trim those spaces. I used this approach:
for /f "tokens=* delims= " %%a in ("%statusStr%") do set statusStr=%%a
for /f "tokens=* delims= " %%a in ("%resultStr%") do set resultStr=%%a

At last, I branched to a specific label-marked section of the script based on the status of the latest query:
IF %statusStr%==Ready GOTO:TaskReady
IF %statusStr%==Running GOTO:QueryStatus

So now I have a Windows .bat script that launches the remote scheduled task and monitors it so long as the status is Running. Once it switches to Ready, it breaks out of its loop. Now, it turns out that the Task Scheduler does not propagate error codes in quite the way I expected, so I have a little more work to do to get Jenkins to show an accurate status when the remote task fails.

But for now, with some light logging thrown in for sanity's sake, the final script looks more or less like the following. Again, I am not a SysAdmin and do not do a whole lot of work with .BAT files, but I am the lead for setting up Jenkins so it's me or no one.
REM @echo off
REM **************************************************
REM  This script launches the build task and queries the status while the task is still running.
REM **************************************************

SET output=MyBuildStepLog.txt

REM **************************************************
REM  LaunchBuild
REM  Run the Scheduled Task on the remote server.
REM **************************************************
REM QUESTION: What if it is already running? Should we wait? Abnormal-end? Skip?
CALL:Println "Launching the Build task on MyRemoteServer at %Time%"
schtasks /run /s MyRemoteServer /tn MyTask

REM **************************************************
REM  QueryStatus
REM  Query the current status of the Scheduled Task on the remote server.
REM   Scan the formatted output for the Status and the Last Result values.
REM     Since those values are padded with leading spaces, trim them.
REM  Branch either forward when status is Ready, or repeat the loop when Status is Running.
REM **************************************************
CALL:Println "Querying the status of the Build task at %Time%"
FOR /F "tokens=1,2* delims=:" %%a in ('schtasks /v /query /s MyRemoteServer /tn MyTask /FO LIST') DO (
if %%a==Status SET statusStr=%%b
if %%a==Last^ Result SET resultStr=%%b

for /f "tokens=* delims= " %%a in ("%statusStr%") do set statusStr=%%a
for /f "tokens=* delims= " %%a in ("%resultStr%") do set resultStr=%%a

CALL:Println "  Query result: at %Time% the status is: %statusStr% and the Last Result is: %resultStr%"

IF %statusStr%==Ready GOTO:TaskReady
IF %statusStr%==Running GOTO:QueryStatus

REM **************************************************
REM  TaskReady
REM **************************************************
CALL:Println "The Build task is no longer running, status is Ready."
CALL:Println "The Build's Last Result is %resultStr%."
SET ErrorLevel=%resultStr%

REM **************************************************
REM  Println
REM **************************************************
:Println %1
@echo %~1
@echo %~1 >> %output%

REM **************************************************
REM  PrintEmptyln
REM **************************************************
@echo. >> %output%

REM **************************************************
REM  End
REM **************************************************
IF NOT %ErrorLevel%==0 CALL:PrintEmptyln
IF NOT %ErrorLevel%==0 CALL:Println "Error Number: %ErrorLevel%"
EXIT /B %ErrorLevel%


Popular posts from this blog

Trigger Windows Scheduled Task from Remote Computer via Jenkins

One thing I love about working in Information Technology is the opportunity - the NEED - to constantly learn new things. If a week goes by in which I have not looked up something on StackOverflow or other message boards, I start lobbying my team for more challenges.

This week, I learned the power of running "SCHTASKS.exe" from a command-line script for a remote server in a Microsoft Windows environment.

If you don't know Schtasks, you can read up on it here:

In a nutshell, it is the command-line interface for the Windows Task Scheduler, and allows you (or a system administrator) to create, change, run, query, terminate, and delete scheduled tasks on a work-station, either the local one or a remote one.

Not all of the features are available in older versions. In my scenario below, this was relevant as the local computer will be a Windows 8 machine, and the remote server is, shall we say, a muc…

Adding Items to a ListView using Scala, ScalaFX and FXML

I have been playing with writing an application using Scala, with its API defined in ScalaFX, which wraps the powerful JavaFX library. For simple exercises, coding the UI by hand was enough. But for more complex forms, I began using the JavaFX Scene Builder tool.

Fortunately, others have blazed this trail, and there are fairly stable ScalaFX and ScalaFXML libraries available.

Using the Scene Builder tool, I laid out my form and included a ListBox to hold possible gender selections.

The Scene Builder tool generated fxml code such as:
<AnchorPane maxHeight="-Infinity" maxWidth="-Infinity" minHeight="-Infinity" minWidth="-Infinity" prefHeight="208.0" prefWidth="275.0" xmlns="" xmlns:fx="">
      <Label layoutX="14.0" layoutY="30.0" text="Name" />
      <Label layoutX="14.0" layoutY="71…

How to do Git Rebase in Eclipse

This is an abbreviated version of a fuller post about Git Rebase in Eclipse. See the longer one here:
One side-effect of merging Git branches is that it leaves a Merge commit. This can create a history view something like:
The clutter of parallel lines shows the life spans of those local branches, and extra commits (nine in the above screen-shot, marked by the green arrows icon).
Check out this extreme-case history:
Merge Commits show all the gory details of how the code base evolved. For some teams, that’s what they want or need, all the time.

Others may find it unnecessarily long and cluttered. They prefer the history to tell the bigger story, and not dwell on tiny details like every trivial Merge-commit.

Git Rebase offers us 2 benefits over Git Merge: First, Rebase allows us to clean up a set of local commits before pushing them to the shared, central repository. For this, the Eclipse EGit Rebase Interact…