Get c3i working with a successful concourse update with tagging

anaconda-graveyard / conda-concourse-ci

Conda-driven Concourse CI for package building

BSD 3-Clause "New" or "Revised" License

13 stars 29 forks source link

Get c3i working with a successful concourse update with tagging #158

Open angloyna opened 3 years ago

angloyna commented 3 years ago

To ensure we don't break our usual workflow (users don't have to specify --worker-tag in order to kick off general builds), we need a default value for the --worker-tag. The default should be an array with a single value containing the tag that each worker shares.

jjhelmus commented 3 years ago

LGTM. I assume we should hold off on merging this until all the workers are tagged again?

angloyna commented 3 years ago

Yep, and we may need to test the resource (for rsync-recipe, etc) yaml generation to make sure that tagging workers won't prevent us from kicking off the resource tasks that pull the recipes off zeus. I think we saw some issues with that once we had all the workers tagged.