Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ci: use nested dagger for testdev #7223

Closed
wants to merge 4 commits into from
Closed

ci: use nested dagger for testdev #7223

wants to merge 4 commits into from

Commits on Apr 30, 2024

  1. ci: don't use random id in cache volume name for dev 

    Signed-off-by: Justin Chadwell <me@jedevc.com>
    @jedevc
    jedevc committed Apr 30, 2024
    Configuration menu
    Copy the full SHA
    1b9f2ba View commit details
    Browse the repository at this point in the history

  2. ci: use nested dagger for testdev 

    Specifically! This doesn't spin up a docker container with a dev version
of dagger, it spins up a dagger service with a dev version of dagger -
dagger in dagger!

This simplifies deployment to the new CI runners.

Signed-off-by: Justin Chadwell <me@jedevc.com>
    @jedevc
    jedevc committed Apr 30, 2024
    Configuration menu
    Copy the full SHA
    af740e7 View commit details
    Browse the repository at this point in the history

  3. hack: bump client to v0.11.1 to match legacy runners 

    Signed-off-by: Justin Chadwell <me@jedevc.com>
    @jedevc
    jedevc committed Apr 30, 2024
    Configuration menu
    Copy the full SHA
    8f01bb7 View commit details
    Browse the repository at this point in the history

  4. fix: ensure separate ips for tests and service 

    This should allow nested networking to actually work.

Signed-off-by: Justin Chadwell <me@jedevc.com>
    @jedevc
    jedevc committed Apr 30, 2024
    Configuration menu
    Copy the full SHA
    fdf023c View commit details
    Browse the repository at this point in the history