Connecting to CircleCI

@Billa123, I got that same problem you mentioned in your message on March 24, the “./manage.py no such file or directory” error. How did you fix it?

Hi @Howard. That usually means you are in the wrong directory when you are accessing the manage.py script. So you will need to fix the path.

Hi! I have received a build error: No configuration was found in your project. I run the first build while having a typo in folder, I think it has something to do with cache. How can I solve it?

Hi is there a poetry variant for this config.yml file?

I am having issues with the build in circleci, Build-agent version 1.0.147923-e34ae598 (2022-11-08T15:20:13+0000) System information: Server Version: 20.10.18 Storage Driver: overlay2 Backing Filesystem: xfs Cgroup Driver: cgroupfs Cgroup Version: 1 Kernel Version: 5.15.0-1021-aws Operating System: Ubuntu 20.04.5 LTS OSType: linux Architecture: x86_64

Starting container image cache not found on this host, downloading

invalid reference format

version: 2
jobs:
  build:
    docker:
      -image: circleci/python:3.9

      working_directory: ~/repo

      steps:
        - checkout
        - run:
            name: install dependencies
            command: |
              python3 -m venv venv
              . venv/bin/activate
              pip install -r requirement.txt

        - run:
            name: run tests
            command: |
              . venv/bin/activate
              flake8 --exclude=venv* --statistics
              pytest -v --cov=calculator

my python environment is 3.9 so in the ymal i changed the docker image to 3.9 instead of 3.7 but it is not working, even i changed it to 3.7 still complaints about invalid reference format… I am not sure which part of the format isn’t right?

Thanks for the tutorial. I just want to point out that circleci uses new images now so the config should be updated to something like this. cimg instead of circleci

docker:
    - image: cimg/python:3.12

Thanks for thinking along and posting this @Zeph Chai! :D

This CircleCI is an absolute pain! At first there were some authorization issues. Then I read about @Zeph Chai’s suggestion, and I fixed the docker image in my config. I have no idea how to refresh the link from GitHub to circleCI, so I had to unfollow my project and then set it up again. Then flake8 gave some silly errors about whitespace. We should have run the black library in the first place! Fixed those flake8 erros, unfollow and resetup my project. Now the pipeline ran successfully. Really not impressed with circle ci. I would rather stick to GitHub/Actions, it’s much more straight forward.

The next video explains that circle ci continuously tracks for updated commits to GitHub. This was not made clear in this lesson’s video, hence why I was confused if my commits were refreshed in circle ci.

@the1howie you’re right about the second point, and it’s a real gap in this lesson. The video walks through connecting the project but never says that CircleCI watches the repo from that moment on. It only comes up in passing in the next lesson, Making Changes and Triggering Automated Tests, where the narration mentions “since CircleCI is watching this, this should trigger a build.” Hearing that a lesson earlier would have saved you the trouble.

That also explains the unfollow and set-up-again cycle. Once a project is connected, every push to the branch kicks off a fresh pipeline by itself. There’s no link to refresh, so you could have pushed the corrected config.yml and watched a new build appear on its own.

On the Docker image, @Zeph Chai was right, and that change is now required rather than optional. The legacy circleci/* convenience images are deprecated and no longer maintained, and cimg/ is the current namespace:

docker:
  - image: cimg/python:3.12

About reaching for black first, that’s a reasonable instinct, though it wouldn’t have silenced flake8 on its own here. Black defaults to 88 character lines while flake8 defaults to 79, so black-formatted code can still fail this course’s flake8 --exclude=venv* --statistics step with E501. I checked, and a line that black is happy to leave at 81 characters still gets flagged. To get the two tools to agree, point flake8 at black’s defaults:

# setup.cfg
[flake8]
max-line-length = 88
extend-ignore = E203

E203 is in there because black puts a space before the colon in slices like items[n + 1 :], which flake8 still flags.

As for preferring GitHub Actions, that’s a fair conclusion. This course is one of our older ones and it shows, both in the deprecated image and in a setup walkthrough that no longer matches CircleCI’s current interface. I’m flagging it to the rest of the team for an update. You may have already come across our Python Continuous Integration and Deployment Using GitHub Actions course, which covers the same ground if you’d rather stay on Actions.

Thanks for posting both of these, especially the note about what the lesson left unsaid. That’s the kind of feedback that tells us where a video needs work.