Skip check for runner architecture when item has arch="any" #3276
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
needs an update to drone-yaml to avoid linting errors when starting a pipeline with arch=any https://github.com/jnohlgard/drone-yaml/tree/arch-any |
|
Does anyone know what needs to be done to get this merged? The repo referenced by jnohlgard (https://github.com/drone/drone-yaml) is archived so presumably that doesn't need to be updated? |
|
This PR has been automatically closed due to inactivity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow using the special value "any" for the pipeline target platform architecture to bypass the checks for runner architecture when scheduling runs.
Use case: I have two servers, one amd64, one arm64, each with their own Drone runner instance connected to my Drone server. Some pipelines have no architecture dependent parts, for example scripts, as long as there is a docker image with the correct architecture that the runner can use.
If this is merged it will need a paragraph in the docs somewhere in the section about pipeline platform, but I didn't find the right place to edit that yet.