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 default name for the ORFS docker image #25

Merged

Conversation

lpawelcz
Copy link
Contributor

This PR supersedes #22.

CC @oharboe

oharboe and others added 4 commits April 14, 2024 17:45
the user can specify a locked down version themself for
production.

For local testing, the same docker tag as ORFS is
convenient as that makes compiling a docker image
from ORFS the regular way an obvious alternative
to using "bazel run orfs_env"

This begs the question as to why "bazel run orfs_env"
now exists... Isn't that a CI concern for regression
testing of bazel-orfs and not a user-concern?

Users, such as megaboom, are responsible for publishing
and specifying the docker tag and url or furnishing
the docker image in some out of bounds way(such as
compiling locally).

Signed-off-by: Øyvind Harboe <[email protected]>
Use ORFS docker image built on top of [4ac2d011](The-OpenROAD-Project/OpenROAD-flow-scripts@4ac2d01)

Signed-off-by: Pawel Czarnecki <[email protected]>
Signed-off-by: Pawel Czarnecki <[email protected]>
Signed-off-by: Pawel Czarnecki <[email protected]>
@oharboe oharboe merged commit c56246c into The-OpenROAD-Project:main Apr 16, 2024
8 checks passed
@lpawelcz lpawelcz deleted the docker-image-fewer-surprises branch April 16, 2024 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants