Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Local CircleCI doesn't support 2.1 preview #79

Closed
brianmhunt opened this Issue Aug 27, 2018 · 7 comments

Comments

Projects
None yet
3 participants
@brianmhunt
Copy link

brianmhunt commented Aug 27, 2018

I just downloaded circleci from the usual:

curl https://raw.githubusercontent.com/CircleCI-Public/circleci-cli/master/install.sh --fail --show-error | bash

It reports version:

$ circleci version
0.1.1568+255077c

Possible aside: I noted that circleci switch does nothing.

When I run something locally with the config-preview-sdk (i.e. version: 2.1) it errors with config parsing issues that indicate that it's not using the preview SDK e.g.

version: 2.1
...
jobs:
  deploy:
     executor:
        name: some-custom-executor
...      
* Error in config file: The schema/shape of the YAML is incorrect: json: cannot unmarshal object into Go struct field JobDescription.Executor of type string

I seem to be missing something, and guidance would be appreciated.

@brianmhunt

This comment has been minimized.

Copy link
Author

brianmhunt commented Aug 27, 2018

I should mention that circleci config expand just prints the help, though it's mentioned in the config-preview-sdk/README.md:

Local builds do not support 2.1 configuration. There is a work-around, however: You can use the new circleci config expand command (requires upgrading your CLI to the new version) to process your configuration then save the result locally in your config.yml file and run it as a local build.

@zzak

This comment has been minimized.

Copy link
Contributor

zzak commented Aug 28, 2018

Hello @brianmhunt,

Thanks for your report!

The circleci switch command is for people with CLI verison 0.1.0 and less who wish to upgrade seamlessly to this CLI.

Could you send me your whole config, so that I can test it myself? Otherwise, our support staff would be happy to help assist with your config.

You've also found a doc bug! We renamed this command to circleci config process but missed some of the docs, sorry about that! I will fix it right away.

@zzak

This comment has been minimized.

Copy link
Contributor

zzak commented Aug 28, 2018

@brianmhunt Ahh, regarding your original problem, I re-read this and understand now!

So we don't support 2.1+ config syntax for local builds.

You can use circleci config process to pre-process your config into a version that local builds can run (see circleci help config process for more information).

This command should warn if your config version is unsupported as of #76.

@zzak zzak closed this in #80 Aug 28, 2018

@brianmhunt

This comment has been minimized.

Copy link
Author

brianmhunt commented Aug 28, 2018

Hi @zzak. Thanks for the great follow-up.

There've been a few errors that I diagnosed (once I found the Workflows panel), that now seem to be (or should shortly be) sorted.

Cheers

@zzak

This comment has been minimized.

Copy link
Contributor

zzak commented Aug 28, 2018

Hello @brianmhunt,

Thanks for your reply.

I was able to process your config locally, after removing the funky character around line 43.

Could you try running the build locally after processing the config?

i.e.

$ circleci config process .circleci/config.yml > process.yml
# Run the build locally
$ circleci local execute -c process.yml --job deploy-master

This got pretty far for me, at least until make install failed.

Please let me know if you have any other trouble using the CLI! 🙇

@brianmhunt

This comment has been minimized.

Copy link
Author

brianmhunt commented Aug 28, 2018

Thanks @zzak! I got it all sorted! Lots of tinkering, but nothing out of the ordinary for a preview release. :)

@danielcompton

This comment has been minimized.

Copy link

danielcompton commented Mar 7, 2019

Should this be reopened now that 2.1 is out of preview? Will running 2.1 config jobs locally be supported in the future?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.