Dagger: a new way to build CI/CD pipelines • Hacker News Board

Re: Dagger: a new way to build CI/CD pipelines

#201

Post by klohto » Thu, Mar 31, 2022, 6:28 AM UTC

ec109685 wrote: post #199

EddieRingle wrote: post #116

Earlier quoted context omitted.

> We will not rely on unusual licences to restrict competitors from running Dagger as a service. Your "Trademark Guidelines" appear to contradict you: > Third-party products may not use the Marks to suggest compatibility or interoperability with our platform. For example, the claims “xxx is compatible with Dagger”, “xxx can run your Dagger configurations”, are not allowed. > but you have to build your own brand, and…

How is possible to restrict someone from making a factual statement like X is compatible with Y?

If Y is a trademarked term, you are free to not allow statements about your brand.

Re: Dagger: a new way to build CI/CD pipelines

#202

Post by pjmlp » Thu, Mar 31, 2022, 6:32 AM UTC

simulate-me wrote: post #155

nickysielicki wrote: post #44

I’m highly jealous of teams that can containerize all their build tools. If you deal with proprietary toolchains that are tens of gigabytes (Windows WDK, Xilinx Vivado/Vitis) it’s just untenable, and that’s before even mentioning licensing. Even Azure doesn’t have a great solution for WDK development. It’s hard to feel like we’re not being left behind. Bind mounting the tools into the container is an option but at th…

In my personal experience, Windows development is absolutely awful. Nothing about it is ergonomic, and the management of the development environment is just painful. Obviously you don't always have a choice, but creating a nice development experience is clearly not a priority for Microsoft. One really basic example: I was deploying files to a Windows Server box using scp, but my internet connection died midway throug…

Usually it helps by adopting Windows development practices instead of trying to cram UNIX workflows into it.

Who on their right mind uses ssh/scp on Windows development other than connecting to UNIX boxes?

Re: Dagger: a new way to build CI/CD pipelines

#203

Post by klohto » Thu, Mar 31, 2022, 6:32 AM UTC

swozey wrote: post #198

Worst company name I've experienced in years. Absolute embarassment. How do I introduce an app named "Dagger" into my stack without sounding caustic or ignorant to my staff? How do you make a service called this without feeling caustic or ignorant. And you have investors? Are you serious? Did you think Mailgun was a good name? edit: Figures Paul Graham is pimping this trash. Good work Sykes, you found a way to float…

It’s not the name that’s the problem with your introduction it seems.

Re: Dagger: a new way to build CI/CD pipelines

#204

Post by maxloh » Thu, Mar 31, 2022, 6:33 AM UTC

nickysielicki wrote: post #44

I’m highly jealous of teams that can containerize all their build tools. If you deal with proprietary toolchains that are tens of gigabytes (Windows WDK, Xilinx Vivado/Vitis) it’s just untenable, and that’s before even mentioning licensing. Even Azure doesn’t have a great solution for WDK development. It’s hard to feel like we’re not being left behind. Bind mounting the tools into the container is an option but at th…

I saw a lot of projects build Windows artifacts with GitHub Actions.

It doesn't seem too hard.

Re: Dagger: a new way to build CI/CD pipelines

#205

Post by pjmlp » Thu, Mar 31, 2022, 6:34 AM UTC

Nice choice of naming, really no research done on it?

https://dagger.dev/

https://developer.android.com/training/dependency-injection/...

Now good luck searching for using Dagger CI/CD for Android development.

Re: Dagger: a new way to build CI/CD pipelines

#206

Post by justRafi » Thu, Mar 31, 2022, 6:48 AM UTC

Been using Drone CI for several years, it has a cli and a command to run locally. Drone Runners allow executing builds on different platforms. CUE is interesting, but I can’t see any major advantages to switching to Dagger.

Re: Dagger: a new way to build CI/CD pipelines

#207

Post by ianpurton » Thu, Mar 31, 2022, 6:49 AM UTC

shykes wrote: post #63

seeekr wrote: post #58

This seems similar to what https://earthly.dev is doing?

Yes, I believe that is a fair comparison. Earhly is more focused on builds, whereas Dagger has a wider scope: build, test, deployment, any part of a CI/CD pipeline really. But the overall philosophy is the same: run everything in containers. The choice of buildkit as a runtime is also a key similarity. One big difference is that we use CUE as a configuration language, and Earthly uses YAML. We have a lot of respect (…

I've been using Earthly for about 6 months.

Earthly uses Dockerfile style syntax so I don't have to learn a new language, I can leverage my existing knowledge.

Another advantage is that in Earthly I can run up a docker compose within my pipeline so that I have selenium, envoy and postgres running for integration testing.

You can see my integration tests here https://github.com/purton-tech/cloak/blob/main/Earthfile#L14...

Is that possible in dagger?

Re: Dagger: a new way to build CI/CD pipelines

#208

Post by swozey » Thu, Mar 31, 2022, 6:52 AM UTC

klohto wrote: post #203

swozey wrote: post #198

Worst company name I've experienced in years. Absolute embarassment. How do I introduce an app named "Dagger" into my stack without sounding caustic or ignorant to my staff? How do you make a service called this without feeling caustic or ignorant. And you have investors? Are you serious? Did you think Mailgun was a good name? edit: Figures Paul Graham is pimping this trash. Good work Sykes, you found a way to float…

It’s not the name that’s the problem with your introduction it seems.

It's not my introduction we're critiquing here. I don't give one fuck what Paul Graham invests in and I can't wait until he realizes nobody younger than him who isn't desperate to be a CEO-bro gives a shit about his opinion.

Re: Dagger: a new way to build CI/CD pipelines

#209

Post by malkia » Thu, Mar 31, 2022, 7:00 AM UTC

pid-1 wrote: post #171

malkia wrote: post #169

Earlier quoted context omitted.

I love unix tools (grep, sed, cut, etc.), and while there are some good sub-systems (msys2, cygwin), they might be bit heavey. For that the windows version of busybox - https://frippery.org/busybox/ - and then I make sure my scripts are not using too powerful features of said tools (grep especially), such that the version in busybox works. Great, and also possible to port some of that back to linux (but I mostly use…

I use scoop to install this sort of tool in Windows. iwr -useb get.scoop.sh | iex # install scoop scoop install coreutils vim nano [...] # yay

Nice! I'll try it out tomorrow finally.. after giving up on choco, and possibly on winget.

But in my case I wanted to leave something small (and busybox.exe is that small) /portable - for others to use (without the requirement to install scoop).

Re: Dagger: a new way to build CI/CD pipelines

#210

Post by malkia » Thu, Mar 31, 2022, 7:06 AM UTC

gregmac wrote: post #189

pc86 wrote: post #130

Earlier quoted context omitted.

OT but is Scoop competing with Chocolatey? I'm having trouble seeing the difference and I've never heard of Scoop before

There's a good comparison on the Scoop wiki [1]. Chocolatey is a mixed bag. Since it is basically just wrapper scripts around upstream installers, it very much depends on what the upstream installer does. To me, it acts less like a package manager (apt) and more like a rudimentary installer runner. This causes all kinds of annoying usability issues. Chocolatey doesn't know if you uninstall via Add/Remove programs, or…

I gave up on chocolatey (though some software from google relies on it to build). Have been using WinGet for a while, but feels bit underwhelming, and at work already several folks have recommended scoop - I guess it's the time!