gobl is an experimental build system that uses Go to define and run build tasks. Although it is actively used to develop other programs, it is by no means stable and may have breaking API changes if any redesigns are required. However, syntax should largely remain the same, as I find its current syntax to be simple to use, which is one of the primary goals of it.
In your project root directory, simply create a file called gobl.go and fill its contents with the following:
package main
import (
. "github.com/kettek/gobl"
)
func main() {
Task("listFiles").
Exec("ls")
Go()
}You will likely have to get the gobl dependency by issuing go get -d github.com/kettek/gobl.
At this point, you can list the tasks by issuing go run . and then run the specific task with go run . listFiles
A more complex example that would allow automatic rebuilding + running, would be:
package main
import (
. "github.com/kettek/gobl"
)
func main() {
Task("build").
Exec("go", "build", "./cmd/mycmd")
Task("run").
Exec("mycmd")
Task("watch").
Watch("./pkg/*/*.go").
Signaler(SigQuit).
Run("build").
Run("run")
Go()
}For a complete rundown of available steps, see the godoc task reference.
There is a task provider extension for VSCode that allows using gobl tasks as VSCode tasks. It is available as Gobl Task Provider and has a GitHub repository here.
* 1. I like Go.
* 2. Having the full power of Go available for setting up and running build tasks is very convenient.
* 3. Go's syntax is elegant.
* 4. It's an interesting concept.
Of course, there are some inconveniences, such as:
* 1. Technically running `go run .` does first compile the task script and run it from a temporary directory.
* 2. It takes the place of `main() {...}` in whatever directory it is in. This shouldn't be problem for most popular go project layout styles, but could be an issue for some.
* 3. `go.mod` and `go.sum` adds some clutter.