Closed kilahm closed 1 year ago
Your development orb has been published. It will expire in 30 days. You can preview what this will look like on the CircleCI Orb Registry at the following link: https://circleci.com/developer/orbs/orb/circleci/orb-tools?version=dev:faeb34c3272eda2814f0c61a33bb41cf1c23e0b9
Your development orb has been published. It will expire in 30 days. You can preview what this will look like on the CircleCI Orb Registry at the following link: https://circleci.com/developer/orbs/orb/circleci/orb-tools?version=dev:77d207d38f3907fb5ffeca96cef61cd4b0c439c0
Your development orb has been published. It will expire in 30 days. You can preview what this will look like on the CircleCI Orb Registry at the following link: https://circleci.com/developer/orbs/orb/circleci/orb-tools?version=dev:b21ac739a57580616ea10cab6c8bf0cf28fbeadc
Your development orb has been published. It will expire in 30 days. You can preview what this will look like on the CircleCI Orb Registry at the following link: https://circleci.com/developer/orbs/orb/circleci/orb-tools?version=dev:b21ac739a57580616ea10cab6c8bf0cf28fbeadc
Your orb has been published to the CircleCI Orb Registry. You can view your published orb on the CircleCI Orb Registry at the following link: https://circleci.com/developer/orbs/orb/circleci/orb-tools?version=11.5.0
Thanks for getting this pushed through!
This feature is modeled after https://github.com/CircleCI-Public/shellcheck-orb/blob/master/src/jobs/check.yml#L7 .
I'm attempting to author an Orb within my company's CircleCI Server v3 instance. We have imported the orbs published under the
circleci/*
namespace. When using the jobs defined in this Orb, I'm getting the following error message at thecheckout
step:I'd like this feature as a work-around to the potential underlying issue described here. The workaround is to use an Alpine or Ubuntu 21.04 based image.