Skip to content

Do not use explicit dependencies on Dockerfile #224

@spalladino

Description

@spalladino

We currently need to declare all package dependencies, including transitive ones, to the Dockerfile for each package for CI build:

https://github.com/AztecProtocol/aztec3-packages/blob/3e737216717f05c44d99a2aedc356257f9c3e15f/yarn-project/archiver/Dockerfile#L5-L11

This is error prone, and leads to frequent issues with the CI.

We should instead either:

  • Copy the entire project to the dockerfile (ie COPY . .)
  • Or have a yarn prepare step at the project root update them

I favor the first one for simplicity. We can move into the 2nd one if performance becomes an issue.

Metadata

Metadata

Assignees

Labels

A-devopsArea: Devops. E.g. CI / build systems

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions