ci: test remote tasks #30
Conversation
|
One thought I'm having is the remote task files are could be tied to a particular version of the UDS/Zarf binary. Maybe it is on the importer to know which versions the source repo installed. |
|
@rjferguson21 Not sure if this comment was meant for here or the common-tasks PR, but that's totally valid. Not a complete solve but I have the tasks being tested in that repo with specific uds-cli and zarf versions, with the same version documented in the readme. Those versions are all tracked by renovate and should be updated at the same time. The versioning also might get simpler if we start publishing actions with the setup stuff (installing uds/zarf) as well as the task pieces, then a repo is just consuming a given action and doesn't have to worry about their own version setup. |
|
Sorry @TristanHoladay Is this still relevant/ready for review? If so can you resolve conflicts and ping me again for review. Thanks! |
|
This is OBE as of #60 |
WIP: Need to add renovate tracking + validate the publish pattern with remote tasks and versioning.