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.

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

Use Nix for builds on cdk-environment EC2 #2683

Closed
patchwork01 opened this issue Jun 12, 2024 · 0 comments · Fixed by #2818
Closed

Use Nix for builds on cdk-environment EC2 #2683

patchwork01 opened this issue Jun 12, 2024 · 0 comments · Fixed by #2818
Assignees
Milestone

Comments

@patchwork01
Copy link
Collaborator

patchwork01 commented Jun 12, 2024

Background

For development, we currently use a Docker container on the EC2 instance deployed by the cdk-environment module. That EC2 instance has the Sleeper CLI installed automatically, and we use the sleeper builder command to get a Docker container for builds and deployment.

We may want to deprecate that Docker image, and replace the Sleeper CLI with a version that runs directly in Java. One reason for this is a bug in GitHub Container Registry:

Description

We'd like to convert the build EC2 deployment in the cdk-environment module to use Nix to set up a build environment.

Analysis

We can install Nix as part of the cloud-init script for the build EC2.

We can remove the automatic installation of the Sleeper CLI. In practice we only use the current CLI to deploy and connect to the environment / build EC2, and to get a build environment on the build EC2. We won't need it on the build EC2 if we use Nix. We could leave that for a separate issue.

We can convert the nightly system tests cron job to run in nix-shell instead of a sleeper builder Docker container. We could leave that for a separate issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants