Open philoserf opened 5 years ago
The same warning/exit-code zero should apply to other artifact handling actions that are not supported in local mode.
Thank you for filing this issue! Converting the errors to warnings is a very reasonable request. I've created an internal ticket for us to track this work.
(Link for CircleCI devs: https://circleci.atlassian.net/browse/CIRCLE-15697 )
cc @KunalJain
There are other related issues. Most seem to request a new feature to support these unsupported actions. This issue is different in that it requests that the error be suppressed on local execute.
Do you want to request a feature or report a bug?: feature
What is the current behavior?:
circleci local execute
exits with a none zero exit code and logs an error when encountering configuration features that are not supported in local mode.Can you provide an example?
With file `.circleci/config.yaml having the following content:
run
circleci local execute --job test
The results of the failing
store_test_results
step are as follows:and the process exits with a non-zero exit code.
What is the expected behavior?
With the same configuration file content running
circleci local execute --job test
would resulting in something simular to the following:Which version of the CLI and OS are you using? Did this work in previous versions?
circleci version: 0.1.4786 macos version: 10.14.2
Please provide the output of
circleci version
andcircleci diagnostic
.If you have any questions, feel free to ping us at @CircleCI-Public/dx-clients.