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

Split up pipeline s3 syncing into separate steps #837

Open
mbertrand opened this issue Nov 30, 2021 · 1 comment
Open

Split up pipeline s3 syncing into separate steps #837

mbertrand opened this issue Nov 30, 2021 · 1 comment

Comments

@mbertrand
Copy link
Member

mbertrand commented Nov 30, 2021

Currently the copy-s3-buckets step in concourse pipelines includes multiple s3 sync commands. The final one, which conditionally runs for ocw-www only, could be split into a separate step that uses the s3-sync resource. https://mitodl.slack.com/archives/G01JPJZQX8E/p1637763373291400?thread_ts=1637685129.280200&cid=G01JPJZQX8E

@mbertrand mbertrand assigned mbertrand and unassigned mbertrand Nov 30, 2021
@mbertrand
Copy link
Member Author

On second thought, this might increase the number of containers used in each pipeline build, increasing the odds of hitting the max containers reached error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant