5 ms·

Thanks for the feedback, we have a tool in the works to translate the config. Sorry it's not available right now. For the 'dependencies: pre' step, you would r

Thanks for the feedback, we have a tool in the works to translate the config. Sorry it's not available right now. For the 'dependencies: pre' step, you would replace that with a 'run' step, the same as outlined for 'dependencies: override'. We'll update the docs - thanks for pointing it out.

nailer 9y ago
Is there something above 'steps:'? The indentation looks like there's a missing parent key - eg, it starts with a bunch of spaces at the top level - but it's hard to work out what it is. Edit: looking at another doc, https://circleci.com/docs/2.0/configuration-reference/#deploy https://circleci.com/docs/2.0/configuration-reference/#deplo..., the missing parent key is 'jobs:' Also shouldn't "Search and Replace Deprecated 2.0 Keys" be "Search and Replace Deprecated 1.0 Keys" (or better "Search and Replace Deprecated Keys")?
- nailer 9y ago
  Also https://circleci.com/docs/2.0/configuration-reference/#table-of-contents https://circleci.com/docs/2.0/configuration-reference/#table... Implies 'steps' is directly under 'jobs', whereas: https://circleci.com/docs/2.0/configuration-reference/#full-example https://circleci.com/docs/2.0/configuration-reference/#full-... shows that 'steps' is under 'jobs > build'
  - nailer 9y ago
    Some feedback: - Re: * missing executor type * is not supported executor type Include https://circleci.com/docs/2.0/executor-types https://circleci.com/docs/2.0/executor-types in the error. - This should be one error, not two. - Why is 'working_directory' mandatory now? It wasn't before. Why not provide a default? - 'working_directory: ~' fails. But 'working_directory: ~/' works (but then fails later). This is silly. Do path normalisation. - https://circleci.com/docs/2.0/executor-types https://circleci.com/docs/2.0/executor-types should include a node 8 image already. it's the current version of node and '@latest' won't be great when 9.x comes out. - Re: https://discuss.circleci.com/t/directory-tmp-you-are-trying-to-checkout-to-is-not-empty-and-not-git-repository/11370 https://discuss.circleci.com/t/directory-tmp-you-are-trying-.... The error is missing a word. Also checking out to a directory with existing contents should be fine. Edit: finally got it: https://gist.github.com/mikemaccana/b6a7be0351d769a9099f5fdbdc726b0c https://gist.github.com/mikemaccana/b6a7be0351d769a9099f5fdb...
    - gordonsyme 9y ago
      `~` is YAML for null - http://yaml.org/type/null.html http://yaml.org/type/null.html
      - nailer 9y ago
        Oh god.
      - OJFord 9y ago
        Wow. I've always thought I understood `$HOME` was generally considered safer/more portable, but I've never actually had a problem when (interactively) using `~`. Always use `$HOME`!
  - michelleluna 9y ago
    Thanks for the feedback, the nesting of keys in the configuration-reference doc is fixed.

nailer 9y ago

Is there something above 'steps:'? The indentation looks like there's a missing parent key - eg, it starts with a bunch of spaces at the top level - but it's hard to work out what it is. Edit: looking at another doc, https://circleci.com/docs/2.0/configuration-reference/#deploy https://circleci.com/docs/2.0/configuration-reference/#deplo..., the missing parent key is 'jobs:' Also shouldn't "Search and Replace Deprecated 2.0 Keys" be "Search and Replace Deprecated 1.0 Keys" (or better "Search and Replace Deprecated Keys")?

nailer 9y ago
Also https://circleci.com/docs/2.0/configuration-reference/#table-of-contents https://circleci.com/docs/2.0/configuration-reference/#table... Implies 'steps' is directly under 'jobs', whereas: https://circleci.com/docs/2.0/configuration-reference/#full-example https://circleci.com/docs/2.0/configuration-reference/#full-... shows that 'steps' is under 'jobs > build'
- nailer 9y ago
  Some feedback: - Re: * missing executor type * is not supported executor type Include https://circleci.com/docs/2.0/executor-types https://circleci.com/docs/2.0/executor-types in the error. - This should be one error, not two. - Why is 'working_directory' mandatory now? It wasn't before. Why not provide a default? - 'working_directory: ~' fails. But 'working_directory: ~/' works (but then fails later). This is silly. Do path normalisation. - https://circleci.com/docs/2.0/executor-types https://circleci.com/docs/2.0/executor-types should include a node 8 image already. it's the current version of node and '@latest' won't be great when 9.x comes out. - Re: https://discuss.circleci.com/t/directory-tmp-you-are-trying-to-checkout-to-is-not-empty-and-not-git-repository/11370 https://discuss.circleci.com/t/directory-tmp-you-are-trying-.... The error is missing a word. Also checking out to a directory with existing contents should be fine. Edit: finally got it: https://gist.github.com/mikemaccana/b6a7be0351d769a9099f5fdbdc726b0c https://gist.github.com/mikemaccana/b6a7be0351d769a9099f5fdb...
  - gordonsyme 9y ago
    `~` is YAML for null - http://yaml.org/type/null.html http://yaml.org/type/null.html
    - nailer 9y ago
      Oh god.
    - OJFord 9y ago
      Wow. I've always thought I understood `$HOME` was generally considered safer/more portable, but I've never actually had a problem when (interactively) using `~`. Always use `$HOME`!
- michelleluna 9y ago
  Thanks for the feedback, the nesting of keys in the configuration-reference doc is fixed.