-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat(docker): Avoid rebuilding images available #160
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@caviri Please correct to self.container_names
. I am just wondering whether the code would run correctly as you used one time self.container_names
and the other times self.container_name
. I did not test this PR by itself.
Hello @sabinem, you are right. I applied the modification and solved a conflict. |
|
||
self.image_names.append(image_name) | ||
self.repo_urls.append(repo_link) | ||
self.commits.append(commit_hash) | ||
self.instance_names.append(image_name) | ||
self.container_names.append(step_name) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix: I think here it should be image_name
:
self.container_names.append(image_name)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@caviri looks good to me: approved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@caviri This looks correct now.
If a component image is already built, then the workflow will create a new container based on that image.
I modified i
instance_name
tocontainer_name
to follow docker's naming.