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

Investigate using GH native docker run action instead of addnab/docker-run-action #14274

Open
LKreutzer opened this issue Oct 26, 2022 · 0 comments
Labels
bazel changes for the Bazelification effort component: ci All updates on CI (Jenkins/CircleCi/Github Action) good first issue Good for newcomers willfix This will be worked on and shouldn't be reaped

Comments

@LKreutzer
Copy link
Contributor

LKreutzer commented Oct 26, 2022

Currently we are using addnab/docker-run-action in e.g. the bazel.yml workflow.

Could using https://docs.github.com/en/actions/using-jobs/running-jobs-in-a-container reduce complexity and improve docker support?

See #14579 for some links to examples within Magma.

@LKreutzer LKreutzer added bazel changes for the Bazelification effort willfix This will be worked on and shouldn't be reaped labels Oct 26, 2022
@LKreutzer LKreutzer added the component: ci All updates on CI (Jenkins/CircleCi/Github Action) label Jan 9, 2023
@mpfirrmann mpfirrmann added the good first issue Good for newcomers label Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bazel changes for the Bazelification effort component: ci All updates on CI (Jenkins/CircleCi/Github Action) good first issue Good for newcomers willfix This will be worked on and shouldn't be reaped
Projects
None yet
Development

No branches or pull requests

2 participants