fck: Fake Construction Kit
All text and code copyright (c) 2016 by Jérémie Chassaing. Used with permission.
Original post dated 2016-12-04 available at http://thinkbeforecoding.com/post/2016/12/04/fck%3A-Fake-Construction-Kit
By Jérémie Chassaing
Yeah it's christmas time again, and santa's elves are quite busy.
And when I say busy, I don't mean:
I mean busy like this:
So they decided to build some automation productivity tools, and they choose Santa's favorite language to do the job:
F# of course !
No body would seriously use a compiled language for automation tools. Requiring compilation or a CI server for this kind of things usually kills motivation.
Of course it is possible to write bash/batch files but the syntax if fugly once you start to make more advanced tools.
Writing F# script is easy and fast. Test it from the command line:
printfn "Merry Christmas !"
press :q to exit
now launch it on linux with:
fsharpi --exec test.fsx
or on windows:
fsianycpu --exec test.fsx
The only problem is that typing the
fsharpi --exec this is a bit tedious.
Bash/Batch to the rescue
We can create a bash/batch script to puth in the path that will launch the script (for linux):
fsharpi --exec test.fsx
chmod +x test
or on windows
fsianycpu --exec test.fsx
Better, but now we need to write a bash and/or a batch script for each F# script.
fck bash/batch dispatcher FTW !
We create a fck file (don't forget to chmod +x it) that takes a command
#!/usr/bin/env bash # fck tool path fckpath=$(readlink -f "$0") # fck tool dir dir=$(dirname $fckpath) script="$dir/fck-cmd/fck-$1.fsx" shell="$dir/fck-cmd/fck-$1.sh" cmd="$1" shift # packages if needed if [ ! -d "$dir/fck-cmd/packages" ] then pushd "$dir/fck-cmd" > /dev/null mono "$dir/fck-cmd/.paket/paket.bootstrapper.exe" --run restore popd > /dev/null fi # script command if it exists if [ -e $script ] then mono "$dir/fck-cmd/packages/FAKE/tools/FAKE.exe" "$script" -- $@ # shell command if it exists elif [ -e $shell ] then eval $shell $@ # help else pushd "$dir/fck-cmd" > /dev/null mono "$dir/fck-cmd/packages/FAKE/tools/FAKE.exe" "$dir/fck-cmd/fck-help.fsx" -- $cmd $@ popd > /dev/null fi
and the batch version:
@echo off set encoding=utf-8 set dir=%~dp0 set cmd=%1 set script="%dir%\fck-cmd\fck-%cmd%.fsx" set batch="%dir%\fck-cmd\fck-%cmd%.cmd" shift set "args=" :parse if "%~1" neq "" ( set args=%args% %1 shift goto :parse ) if defined args set args=%args:~1% if not exist "%dir%\fck-cmd\packages" ( pushd "%dir%\fck-cmd\" "%dir% popd ) if exist "%script%" ( "%dir%/fck-cmd/packages/fake/tools/fake.exe" "%script%" -- %args% ) else if exist "%batch%" ( pushd "%dir%\fck-cmd\" "%batch%" %cmd% %* popd ) else ( "%dir%/fck-cmd/packages/fake/tools/fake.exe" "%dir% )
Forget the paket part for now.
The bash take a command argument, and check whether a fck-cmd/fck-$cmd.fsx file exists. If it does, run it ! It also works with shell scripts name fck-$cmd.sh or batch scripts fck-$cmd.cmd to integrate quickly with existing tools.
Fake for faster startups
When F# scripts start to grow big, especially with things like Json or Xml type providers, load time can start to raise above acceptable limits for a cli.
Using Fake to launch scripts takes adventage of it's compilation cache. We get the best of both world:
- scriptability for quick changes and easy deployment
- automaticly cached jit compilation for fast startup and execution
We could have written all commands in a single fsx file and pattern maching on the command name, but once we start to have more commands, the script becomes bigger and compilation longer. The problem is also that the pattern matching becomes a friction point in the source control.
At some point we have recuring code in the tools. So we can create helper scripts that will be included by command scripts.
For instance parsing the command line is often useful so I created a helper:
// culture invariant, case insensitive string comparison let (==) x y = String.Equals(x,y, StringComparison.InvariantCultureIgnoreCase) open System.Xml.Linq module CommandLine = // get the command line, fck style... let getCommandLine() = System.Environment.GetCommandLineArgs() |> Array.toList |> List.skipWhile ((<>) "--") |> List.tail // check whether the command line starts with specified command let (|Cmd|_|) str cmdLine = match cmdLine with | s :: _ when s == str -> Some() | _ -> None
We use the
-- to delimit arguments reserved for the script. Since Fake is used to launch scripts, we can also include FakeLib for all the fantastic helpers it contains.
Here is a sample fck-cmd/fck-hello.fsx script that can write hello.
It uses FakeLib for the tracefn function and FckLib for getCommandLine.
You can call it with (once fck is in your Path environment variable):
fck hello Santa
A tool without help is just a nightmare, and writing help should be easy.
The last part of fck bash script lanch the fck-help.fsx script:
This script tries to find a fck-xxx.txt file and display it, or fallbacks to fck-help.txt.
For example the help for our fck hello command will be in fck-hello.txt:
Usage: fck hello [<name>] Display a friendly message to <name> or to you if <name> is omitted.
Of course we can pimp the fck-help.fsx to parse the txt help files and add codes for colors, verbosity etc.
Deployment is really easy. We can clone the git repository, and add it to $PATH.
Run the commands, it will automatically restore packages if missing, and lanch the script.
To upgrade to a new version, call fck update, defined in fck-update.sh :
script=$(readlink -f "$0") dir=$(dirname $script) pushd "$dir" > /dev/null git pull mono "$dir/.paket/paket.bootstrapper.exe" --run restore popd > /dev/null
or batch fck-update.cmd:
git pull .paket
Yep, that's that easy
Using Santa's elves tools, I hope you won't be stuck at work on xmas eve ! Enjoy !