New project builds on CircleCI 1.0 even with 2.0 config.yaml

Steps done:

  • Created a brand new repo on GitHub
  • Added and committed a .circleci/config.yaml file (see below)
  • Clicked Add Project in CircleCI
  • Clicked “Build” for the first time

The build starts but I get a warning that the (new) project is on CircleCI 1.0. I took care not to build the project before a config.yaml was added as this will start the build process on 1.0.

I used the example config.yaml verbatim. I don’t expect it to work for my project specifically without editing it, but surely it should at least build on CircleCI 2.0?

.circleci/config.yaml

# Clojure CircleCI 2.0 configuration file
#
# Check https://circleci.com/docs/2.0/language-clojure/ for more details
#
version: 2
jobs:
  build:
    docker:
      # specify the version you desire here
      - image: circleci/clojure:lein-2.7.1
      
      # Specify service dependencies here if necessary
      # CircleCI maintains a library of pre-built images
      # documented at https://circleci.com/docs/2.0/circleci-images/
      # - image: circleci/postgres:9.4

    working_directory: ~/repo

    environment:
      LEIN_ROOT: "true"
      # Customize the JVM maximum heap limit
      JVM_OPTS: -Xmx3200m
    
    steps:
      - checkout

      # Download and cache dependencies
      - restore_cache:
          keys:
          - v1-dependencies-{{ checksum "project.clj" }}
          # fallback to using the latest cache if no exact match is found
          - v1-dependencies-

      - run: lein deps

      - save_cache:
          paths:
            - ~/.m2
          key: v1-dependencies-{{ checksum "project.clj" }}
        
      # run tests!
      - run: lein test

What am I doing wrong?

Try renaming config.yaml to config.yml – this should solve your problem. Let me know if there’re any more issues!

Thanks for the suggestion, but no dice.

# Create a new branch
git checkout -b ci20
# Rename config extension to .yml
mv .circleci/config.yaml .circleci/config.yml
# Trigger a CI build
git add -A
git commit -m "This should use Circle CI 2.0"
git push origin ci20

And I still see the following warning on the Job dashboard for the new ci20 branch

This project is currently running on CircleCI 1.0 which will no longer be supported after August 31, 2018. Please start migrating this project to CircleCI 2.0.

Whoops! I fat fingered the config file name when moving it.

That worked. Thanks, Cormac!

1 Like

Haha, it happens to all of us – happy building!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.