Say Goodbye to Makefile - Use Taskfile to Manage Tasks in CI/CD Pipelines and Locally

Discover the modern way of managing tasks in your development workflow with Taskfile, your Makefile alternative. In this video, we dive into how Taskfile simplifies task management both in CI/CD pipelines and local environments. Learn how to define and execute tasks with ease, gain insights into Taskfile's convenient features, and see practical examples that will help you streamline your development process. Say goodbye to the complexity of Makefiles and embrace the simplicity of Taskfile for more efficient and maintainable workflows.

#Taskfile #CICD #Makefile

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬

▬▬▬▬▬▬ 💰 Sponsorships 💰 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Introduction
01:51 GNU Make (Makefile) to the Rescue?
04:22 Task and Taskfile (Replacements for Make and Makefile)
12:50 Task (Taksfile) Pros and Cons

[DevOpsToolkit]

What do you think of Task and Taskfile? Could it be useful for those who prefer defining tasks in a declarative way?

[PeteDavison]

Great video! I've been helping to maintain Task for the last couple of years and you've done a fantastic job of introducing the project. It's always super motivating to see the community talking about it so positively.

[quentinsf]

I've been looking for a good Make replacement for about thirty years :-), and I've just converted one of my Makefiles to a Taskfile to try it out. This doesn't do everything, but it's so much nicer than Makefile syntax, and I suspect would be quite an improvement when it comes to managing a tree of tasks in subdirectories.

[torbendury]

Saving this for later. Wanted to look into Taskfiles some while ago, recently found another post on HN but with your video it'll definitely rank up on my "have a look at it" list!

[cheebadigga]

Awesome thanks for the video! One note: You can execute dependencies synchronously by adding them as "- task: taskname" under "cmds" rather than "deps".

[Rundik]

"just" is another good task runner

[sohansingh]

I was just exploring it because YAML feels much more comfortable to me! Thanks as usual.

[IvanRizzante]

Thanks for another great video! I didn't know about this, it's definitively interesting and more appealing than Makefile to me. That being said I stick with remote development so I don't feel the pain of replicating the tasks locally/remotely but I'll definitively keep this (and Dagger) in my toolbox

[andywilson]

I've been using Task for years, it's great! I find it's great for working across platforms (Windows, Linux) to run the same commands that would usually just be a short bash script or Makefile.
I don't quite understand your con about containers though? To me it's just a way of sequencing commands, which has nothing to do with containers.. and Dagger has a somewhat different use-case in mind which obviously *is* centered around containerised execution of things.
In fact I have a Taskfile execute dagger commands, which saves me from having to remember command syntax and flags etc..
I think Task is more just a replacement for bash scripts really. Makefile wasn't designed to be a generic command running tool, whereas Task is

[juanbreinlinger]

I've been using tasks for months now and can't recommend it more!

[rafaelpirolla]

you could create a "lock" file and exit if it exists as first step and remove in the last step to avoid parallel runs...

[Propherex]

That what we need! More yaml!!! And build logic workarounds like 8:30! Nah, for me its no go zone.

[zim]

I like it's simplicity. Look at Gradle. It can also be used for thi purpose. But it's too difficult and heavy. You need to read the whole gradle book and learn groovy. I like that modern IT is leaning towards simplicity again

[dankobgd]

Have you used justfile? It doesn't use yaml so it might seem leaner for defining tasks

[hkupty]

Use entr instead of the watcher... It can solve the issue with breaking a running execution

[thescourgeofathousan]

I use Ansible to implement the actual work (can be actual work or just integration with tools depending on what the task is) that needs to be done at each stage of the pipeline.
It’s perfect for this purpose.
It also allows me to use the inventory of Ansible as configuration for the pipeline which enables me to manage this configuration in versions control rather than putting configuration in pipeline tool config via admin pages.
The pipeline is purely orchestrator.
This also facilitates the evolution of how the tasks in the pipeline are accomplished to be developed, tested and deployed via CICD also

[joebowbeer]

A comparison to 'just' would be appreciated

[advertslaxxor]

I like the idea of Taskfile, but I think it's execution is lacking a bit.

You can't override env vars. You instead need to bloat your file with "{{.env}} some-cmd" or "{{.cmd}}" to override things.
It handles hashing of generative tasks poorly. It doesn't hash the output files, so effectively you want to run the generation every time, since sometimes users will modify the files accidentally (or worse :D)
It uses yaml. OK, OK, I know, I know; but I think yaml is riddled with bad designs (back to the yes/no bools, ...).
I wonder if this could be done with a better data format such as TOML, though I think it would be more verbose.

[RoaiDude]

Why did you use make instead of projects like jenkins for example?
Doesnt jenkins answer your commands needs?

[autohmae]

With this much YAML in my life... I guess I will come up with better tooling with dealing with them, so Taskfile seems like a good idea. I'll add it on my list for when it happens.
PS I assume you didn't see my comment on how to reach me on social media ? I know Youtube loves to block such things.