This repository has been archived on 2024-04-08. You can view files and clone it, but cannot push or open issues or pull requests.
Gerhard Lazu fb09e2a1c6
Split CI workflow into individual workflows
I had to re-run all jobs in the CI workflow at least 10 times in the
past 2 days. The problem is that when one jobs fails, all jobs need to
re-run, which sometimes results in different jobs failing. It would be
great if we could only re-run the jobs that failed, rather than all the
jobs in the CI workflow. Going forward, we should focus on improving
flaky tests, and speed the jobs which take the longest, but for now this
is a good start.

Before this change, we were wasting a lot of dev time - 2h in total for
my last PR #1476 - but also wasting CI minutes. Some of us were even
tempted to ignore CI 😱. This is a very slipper slope, and while it may
feel liberating in the short-term, there are many "windmill monsters"
down this path - don't do it.

Have a look at the CI workflow before this change to see how many
failures we had:
https://github.com/dagger/dagger/actions/workflows/ci.yml

Without looking at the jobs that failed, can you guess which areas are
the flakiest and need our attention the most? Integration & Universe are
good guesses, and I wish we could see this without digging into the CI
workflow - this change does that.

There is a lot more that can be improved here, but I didn't want to get
too carried away. The biggest improvement that we can make is switch
this to Dagger, which has some challenges, but I definitely intend to
tackle them because it feels worth it. This is good enough for now.

This is a ship & show PR. If all tests pass, this is a straight merge. I
am keeping it atomic so that we can revert it if we don't like it.

cc @aluzzardi @talentedmrjones @jlongtine @samalba @shykes @grouville

Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
2022-01-25 18:44:42 +00:00
2022-01-13 15:52:13 -08:00
2022-01-20 16:10:14 -08:00
2022-01-20 16:29:07 +00:00
2022-01-18 09:38:50 +01:00
2022-01-21 12:45:59 -08:00
2022-01-20 16:10:14 -08:00
2022-01-11 16:51:54 -08:00
2021-12-14 09:08:58 -08:00
2022-01-21 21:23:57 +01:00
2021-10-13 15:25:30 -07:00
2021-02-17 13:13:17 -08:00
2022-01-20 19:38:24 -07:00
2022-01-20 19:38:24 -07:00
2021-06-30 17:54:48 +02:00
2021-05-03 17:20:45 -07:00
2021-01-14 12:36:19 -08:00
2022-01-20 16:29:07 +00:00
2022-01-25 11:42:46 +00:00
2021-07-09 09:47:36 +02:00

Dagger

Dagger is a portable devkit for CICD.

Using Dagger, software teams can develop powerful CICD pipelines with minimal effort, then run them anywhere. Benefits include:

  • Unify dev and CI environments. Write your pipeline once, Dagger will run it the same everywhere.
  • Reduce CI lock-in. No more re-writing everything from scratch every 6 months.

How does it work?

  1. Automate actions with your favorite programming language. No proprietary SDK: just regular shell, Go, Javascript, Python...
  2. Reuse actions from a large and growing catalog.
  3. Tie it all together in CUE - a revolutionary declarative language invented at Google. No more YAML hell!
  4. Test and debug instantly on your local machine. No more waiting 10min to catch a typo.
  5. Run your pipelines on any Docker-compatible runtime, for maximum portability. This means most modern CI runners can run Dagger out of the box.

Getting Started

Documentation website

Description
No description provided
Readme 13 MiB
Languages
Go 52%
CUE 29.3%
Shell 9.2%
JavaScript 4.4%
SCSS 2.3%
Other 2.7%