dan_manges

6 mesi fadiscuss

I've been working on this problem for the past couple of years. State of the art:

- local CLI instead of git push to run

- graph-based task definitions with automatic distributed execution, instead of the job/step abstraction

- automatic content-based caching to skip unnecessary executions (happens a lot in CI pipelines)

- container-based runtime (instead of proprietary base images) without using docker directly (too slow)

There are a lot of other ways to improve the developer experience. Happy to chat with anybody interested, I'm [email protected]

dan_manges

8 mesi fadiscuss

Hey! I'm one of the RWX cofounders. We don't have a self-hosted option yet, but we're interested in opening it up in the future. Our infrastructure is more complex to run than normal self-hosted runners infrastructure, due to extensive caching and provisioning optimizations.

dan_manges

10 mesi fadiscuss

We support anchors in our CI/CD syntax at RWX, but only in a specific `aliases` section. I think this is a nice compromise.

  aliases:
    common-env: &common-env
      key1: value1
      key2: value2

  tasks:
    - key: some-task
      run: ...
      env:
        <<: *common-env

https://www.rwx.com/docs/mint/aliases

dan_manges

Submissions

Now Available: Depot CI

Work in Progress Commits Are a Thing of the Past

What would GitHub Actions look like if you designed it today?

comments