When offline, CLI should not fail steps that are 'latest' simply because they cannot update the step

#1

I’ve noticed that when using the CLI, and I’m offline, if I have any steps that have their version set to “Latest”, then the whole step fails because the CLI can’t update the step. The error looks something like this:

INFO[16:00:05] Step uses latest version – Updating StepLib …
INFO[16:00:05] Update StepLib (https://github.com/bitrise-io/bitrise-steplib.git)…
FATA[16:00:11] Failed to update StepLib (https://github.com/bitrise-io/bitrise-steplib.git), error: failed to pull library (https://github.com/bitrise-io/bitrise-steplib.git), error: exit status 1
WARN[16:00:11] Step uses latest version, but failed to update StepLib, err: exit status 1

I think in cases like this, it would be better to fail back to the latest installed step, and then process the step normally.

0 Likes

#2

Hey there @YellowstoneApps :wave:

Thanks for the feature request!
We’ll investigate and see how high the demand is for this :slight_smile:
Also, thanks for voting, anyone who thinks this should be implemented as soon as possible should give it a thumbs up :wink:

0 Likes