You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some platforms, like EthPandaOps tests, work exclusively with Docker images. When I need to fix something, I cannot test it directly until I create an image from my commit and publish it on DockerHub, or until it is merged into the main branch.
My proposal is to create a job that any developer (starting with the Erigon Team) can trigger. This job would:
Create a Docker image from a specific commit (entered manually). The image would be automatically deleted after n days to conserve storage space.
Enforce a usage limit per user to prevent overuse (for example, allowing 2-3 jobs per day, or whatever is deemed suitable).
I believe this should not be automated, as the developer should take full responsibility for the commit they choose to create an image from.
The text was updated successfully, but these errors were encountered:
Rationale
Some platforms, like EthPandaOps tests, work exclusively with Docker images. When I need to fix something, I cannot test it directly until I create an image from my commit and publish it on DockerHub, or until it is merged into the main branch.
My proposal is to create a job that any developer (starting with the Erigon Team) can trigger. This job would:
Create a Docker image from a specific commit (entered manually). The image would be automatically deleted after n days to conserve storage space.
Enforce a usage limit per user to prevent overuse (for example, allowing 2-3 jobs per day, or whatever is deemed suitable).
I believe this should not be automated, as the developer should take full responsibility for the commit they choose to create an image from.
The text was updated successfully, but these errors were encountered: