Our great sponsors
gotaskr | goyek | |
---|---|---|
8 | 10 | |
17 | 504 | |
- | 3.2% | |
6.9 | 7.9 | |
about 2 months ago | 6 days ago | |
Go | Go | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gotaskr
-
Generic Task Runner in Go -> gotaskr
Feel free to head over to GitHub and check the wiki for more details and I would be happy to get feedback or improvement ideas for gotaskr.
-
Build / Makefile templates for Go monorepo?
I created https://github.com/Roemer/gotaskr for that and we are very happy with it for a very complex build system. Give it a try if you want.
-
Is your makefile supposed to be a justfile?
May I present my alternative https://github.com/Roemer/gotaskr It is kind of similar to magefile but provides some other features similar to cake build and inbuilt tools useful for devops. And also it is a plain go program so no magic compilation in the background. It replaced basically 100 bash files in our rather complex build/deploy setup. Sometimes a declarative approach is just not enough.
-
Unpopular opinion: CI/CD engines are an awful idea
I have used many CI systems on large scale and to be honest, Jenkins is still my favorite. Everything you need is provided and works. You have 100% control over the workflow. With code. All those declarative yaml based ones need sooooo much workarounds to get more complex workflows to run and often you are just stuck with a less optimal solution. Beside the build workflow, we do not write any build logic in the ci engine but use external code runners instead. For .Net I used Cake or Nuke build for example but now my absolute preference for build logic is go. There we use a task runner like gotaskr. This helps having the build logic centralized and usually you can also run different build tasks locally to debug and test them. Also with go, you don‘t need any runtime to run the logic. Just build the task runner once and then you can copy the binary anywhere (eg for parallel build tasks) and just run it. This is optimal to integrate it in Docker base builds so you don‘t need to change the base image at all.
-
Task runner like go-task/task, but in pure Go, no external DSLs
May I present my solution: https://github.com/Roemer/gotaskr Heavily inspired by cake build. It has no compile magic anywhere. Just write your go file and run the tasks in it. Or build it and re-use it in a ci for example.
-
Utility library, most gopher way for namespaces/packages
The current refactoring is in: https://github.com/Roemer/gotaskr/tree/feature/toolsrefactoring
-
Any open source projects need help ?
I'm a go youngling that tried to create a task runner (inspired by cake build for .net) in go as an alternative to magefile. What I would like is to get some feedback about how it is implemented and if there are go-principles that are violated and where the code should be improved. So if you want to do some reviewing, feel free to have a look at https://github.com/Roemer/gotaskr
goyek
- Goyek: Build Automation in Go
-
Reason to use other Build Tool than Make?
You can also take a look at https://github.com/goyek/goyek. Personally I use either Make or goyek. Disclaimer: I am the author of goyek
-
Is your makefile supposed to be a justfile?
I think that Make is so popular, because Go comes from C. Many C and C++ devs migrated to Go. Personally, I created goyek as an alternative.
-
Task runner like go-task/task, but in pure Go, no external DSLs
how about https://github.com/goyek/goyek
-
Build\task automation in Go
It's also what I'm using currently as direct make/makefile replacement. What I plan to use next time though is goyek: https://github.com/goyek/goyek . Concept looks really nice but I haven't tried it yet in any real case scenario.
-
goyek v2 is coming soon
https://github.com/goyek/goyek v2.0.0 is to be released in two months. Now it is the best time to provide feedback.
-
goyek v2 RC - feedback needed
In my "free time" I develop https://github.com/goyek/goyek
- goyek v1.0.0 is released
-
goyek is looking for feedback before going v1
https://github.com/goyek/goyek (initially `taskflow`) first release was more than a year ago. So far been slightly improved.
-
The first release of goyek - a library for creating build pipelines
Check out: https://github.com/goyek/goyek#make Also reusing Make targets between multiple repositories is harder (e.g. via git submodules) Here are some presentation if you are more interested: https://github.com/goyek/goyek#presentations
What are some alternatives?
weaver - Programming framework for writing and deploying cloud applications.
mage - a Make/rake-like dev tool using Go
go-gitlab - GitLab Go SDK
taskflow - Create build pipelines in Go [Moved to: https://github.com/goyek/goyek]
kertish-dfs - Kertish-dfs is a simple distributed storage platform, implements file storage on a single distributed computer cluster, and provides interfaces for file/folder handling. Kertish-dfs aims primarily for completely distributed operation without a single point of failure, scalable to the exabyte level.
golang-templates/seed - Go application GitHub repository template.
devtron - Tool integration platform for Kubernetes
ziti - The parent project for OpenZiti. Here you will find the executables for a fully zero trust, application embedded, programmable network @OpenZiti
Task - A task runner / simpler Make alternative written in Go
mkdkr - mkdkr = Makefile + Docker
pants - The Pants Build System