Skip to content
This repository has been archived by the owner on Jun 1, 2022. It is now read-only.

Automatically publish development orb version every x days #9

Open
gmemstr opened this issue Oct 15, 2020 · 5 comments
Open

Automatically publish development orb version every x days #9

gmemstr opened this issue Oct 15, 2020 · 5 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@gmemstr
Copy link
Contributor

gmemstr commented Oct 15, 2020

Describe Request:

Similar to CircleCI-Archived/orb-starter-kit#44 - occasionally, orb dev:alpha versions will expire, which means that future commits for that orb will fail the pipeline. Ideally, we set up a cron job within the configuration to automatically refresh this version every 90 (or 89?) days.

@gmemstr gmemstr added enhancement New feature or request good first issue Good for newcomers labels Oct 15, 2020
@SimonBarendse
Copy link

We've done the same thing as you suggest in secrethub/secrethub-circleci-orb#39. Shall I submit a PR that adds the keep-dev-orb from that PR?

@daniel-shuy
Copy link

@SimonBarendse Yes please, I'm facing this issue as well, hopefully it will help others from facing it.

Meanwhile I'll copy the code from your PR, thanks!

@daniel-shuy
Copy link

But now that I think about it, I highly doubt CircleCI will merge the PR since they probably expired dev orbs for a reason 😅

@KyleTryon
Copy link
Contributor

Hey folks, we are currently working on the next iteration of Orb Tools (v11) and everything that goes with this, meaning this project here the Orb Project Template, and documentation. The update should be applied by the end of July.

In Orb tools 11, this will not be an issue and we won't need to use scheduled jobs either. Orb tools 11 will make use of CircleCI's new Dynamic Config to solve this.

The problem today, is the config file requires the dev orb (which only last 90 days), but it only needs this orb for the second workflow where there are integration tests. With Dynamic Config in orb tools 11, we will have 2 distinct config files, an initial "setup" config which contains our first workflow which does linting, shellchecking, unit testing, and finally publishes the dev version of the orb before continuing on to the second config file. The second config file is where the dev orb is required for integration testing.

With this new design, the config will never call on an orb that does not exist.

This work is still very early and there are many core changes planned that are not yet present here but this will give you an idea of the new config design if you would like a sneak peek: CircleCI-Public/orb-tools-orb#111

@netcazean
Copy link

#31

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

5 participants