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
worker: remove ContainerProvider #3546
Conversation
😮 |
Preliminary thoughts? One of the things we are not happy with is the length of concourse/atc/worker/worker.go Lines 324 to 465 in 9555027
The main advantage that this refactor gives us is the isolation of concourse/atc/worker/worker.go Line 187 in 9555027
CreatingContainer creation for #3301
The second advantage is that it attempts to decouple volume and container creation in preparation for concourse/rfcs#20 |
combine containerProvider and worker add workerHelper which stores helper functions Signed-off-by: Divya Dadlani <ddadlani@pivotal.io> Co-authored-by: Krishna Mannem <kmannem@pivotal.io> #3052
Signed-off-by: Divya Dadlani <ddadlani@pivotal.io> Co-authored-by: Krishna Mannem <kmannem@pivotal.io>
Our other streams of work are based on this branch. We wanna integrate it into master. We pulled apart as much as we could without artifacts gc (volumes not dependent on containers). Another reason is to remove a the |
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.
tbh not much to review here since it's primarily slingin' code around, but it passes testflight/watsjs, so let's see how it fares in prod. 💥
combine containerProvider and worker
add workerHelper which stores helper functions
Signed-off-by: Divya Dadlani ddadlani@pivotal.io
Co-authored-by: Krishna Mannem kmannem@pivotal.io
fixes #3052