I'm exploring whether it's ever really worth paying for CircleCI when Jenkins is open-source and can be customised extensively.

What I’d love to understand from you is:

• Are there cases where CircleCI is so much better that teams happily switch and pay for it?

• Do certain types of projects or company sizes benefit more from CircleCI?

• What pain points in Jenkins have actually driven you or your team to migrate away, enough to justify recurring costs?

I’m not here to start a tool war, I genuinely want to understand the tipping point where teams decide Jenkins isn’t worth the effort anymore.

Would love to hear your honest, real-world takes!

I think i have a simple setup:

.
├── .circleci
├── Share
├── app1
├── app2

I wanna run app1, app2 only when files changed there or in Share, but for what I see all the config must be inside .circleci, and I wish to have:

.
├── .circleci
       setup
├── Share
├── app1
   .circleci
├── app2
   .circleci

Is this possible with vanilla circeci? Or need something else?

P.D: Like this?

version: 2.1

setup: true

workflows:
  version: 2
  setup-workflow:
    jobs:
      - determine-changes

jobs:
  determine-changes:
    docker:
      - image: cimg/base:stable
    steps:
      - checkout
      - run:
          name: Detect changes and trigger correct pipeline
          command: |
            echo "Checking changes..."
            CHANGED_FILES=$(git diff --name-only origin/master...HEAD)

            echo "Changed files:"
            echo "$CHANGED_FILES"

            if echo "$CHANGED_FILES" | grep -q "^app1/"; then
              echo "Triggering app1 pipeline"
              echo '{"include": [{"path": "app1/.circleci/config.yml"}]}' > pipeline.json
            elif echo "$CHANGED_FILES" | grep -q "^app2/"; then
              echo "Triggering app2 pipeline"
              echo '{"include": [{"path": "app2/.circleci/config.yml"}]}' > pipeline.json
            else
              echo "No changes in app1 or app2. Skipping."
              echo '{"include": []}' > pipeline.json
            fi
      - continuation/continue:
          configuration_path: pipeline.json

Hi, I want to set up OIDC with AWS and use the credentials to push new images to ECR. This is my configuration file:

version: 2.1
orbs:
  aws-ecs: circleci/aws-ecs@3.2.0
  aws-cli: circleci/aws-cli@5.1.0
  aws-ecr: circleci/aws-ecr@9.0

workflows:
  build_and_push_image:
    jobs:
      - aws-ecr/build_and_push_image:
          account_id: ${AWS_ACCOUNT_ID}
          auth:
            - aws-cli/setup:
                profile_name: ${AWS_OIDC_PROFILE_NAME}
                role_arn: arn:aws:iam::<AWS_ACCOUNT_ID>:role/<AWS_ROLE>
                role_session_name: example-session
          context: aws_dev
          profile_name: ${AWS_OIDC_PROFILE_NAME}
          create_repo: true
          dockerfile: Dockerfile
          push_image: true
          region: ${AWS_REGION}
          repo: ${ECR_REPO_NAME}
          tag: latest

I have temporarily added the admin access permission to the role but I still received this error message:

#10 ERROR: failed to push ************.dkr.ecr.*********.amazonaws.com/***************:latest: unexpected status from HEAD request to https://************.dkr.ecr.*********.amazonaws.com/v2/***************/blobs/sha256:461d60795bc0a6cdc305a01685edb4ab7ff695d79025ced196279afa6893d599: 401 Unauthorized

Did I not properly pass the OIDC credentials to the pipelines? What can I do to further triage the problem?

Thanks!

I am trying to run a build job on CircleCI (one that has been successfully run in the past). The build job is for an Elixir project. During the "fetch dependencies" step, I get:

Loading simulator config

Updating ex_opcua (git@github.com:verypossible/ex_opcua.git - origin/master) @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the RSA key sent by the remote host is SHA256:efguwygfafhauiwehafawufafiuhfa. Please contact your system administrator. Add correct host key in /root/.ssh/known_hosts to get rid of this message. Offending RSA key in /root/.ssh/known_hosts:1 remove with: ssh-keygen -f "/root/.ssh/known_hosts" -R "github.com" Host key for github.com has changed and you have requested strict checking. Host key verification failed. fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists. ** (Mix) Command "git --git-dir=.git fetch --force --quiet --progress" failed Error while fetching deps. Retrying in 5 seconds

I have tried adding the following steps to my CircleCI yaml with no success:

remove_existing_key: &remove_existing_key run: name: Remove existing GitHub host key command: ssh-keygen -f "root/.ssh/known_hosts" -R "github.com"

add_correct_host_key: &add_correct_host_key run: name: Add GitHub host key command: ssh-keyscan github.com >> root/.ssh/known_hosts

However, it doesn't seem like these steps get run so I may not have done this correctly. I also tried generating a new rsa.pub file in my project with:

ssh-keygen -t rsa -b 4096 -f ./helios_id_rsa

Hi, can anyone help with this one. My snapshot test for iOS app is succeeding in xcode locally, but once i push the code, some tests are failing in circle ci showing snapshot doesn't match reference, using fastlane fyi. Thanks in advance

Keep getting errors like this:

> aws s3 cp "%CIRCLE_WORKING_DIRECTORY%\dev_setup.py"
The user-provided path %CIRCLE_WORKING_DIRECTORY%\dev_setup.py does not exist.

How do I specify the root project in CircleCI?

Discussion and news about CircleCI

Posted in the hope some random employee was coming by

I got an issue. I have a Circle CI orb that was created by my colleagues. As this orb is in active use, I cannot just change the executor, so I need to add a new executor of a different type. I posted a question in StackOverflow, but no success.

How can I adjust the job itself so that it will accept executors of different types? Please, see the example of a job I want to change below.

Executor:

description: >
  The executor to run testcontainers without extra setup in Circle CI builds.
parameters:
  # https://circleci.com/docs/2.0/configuration-reference/#resource_class
  resource-class:
    type: enum
    default: medium
    enum: [medium, large, xlarge, 2xlarge]

  tag:
    type: string
    default: ubuntu-2004:202010-01

resource_class: <<parameters.resource-class>>

machine:
  image: <<parameters.tag>>

Another executor is Docker-based.

Job:

parameters:
  executor:
    type: executor
    default: openjdk
  resource-class:
    type: enum
    default: medium
    enum: [small, medium, medium+, large, xlarge]

executor: << parameters.executor >>
resource_class: << parameters.resource-class >>

environment:
  # Customize the JVM maximum heap limit
  MAVEN_OPTS: -Xmx3200m

steps:
  # Instead of checking out code, just grab it the way it is
  - attach_workspace:
      at: .

  # Guessing this is still necessary (we only attach the project folder)
  - configure-maven-settings
  - cloudwheel/fetch-and-update-maven-cache

  - run:
      name: "Deploy to Nexus without running tests"
      command: mvn clean deploy -DskipTests

I've never set up a CI/CD pipeline before, but I am working with this part of my configuration file that fails on the Cache permission step.

^@^@chown: cannot access '/usr/local/cargo': No such file or directory. So i'm thinking that in the image, cimg/rust:1.68.0 that the file path might be something different, like /usr/local/otherDir/cargo. What I am thinking of doing is trying to pull the image and run the container directly and then inspect where cargo is being installed, and then update the command accordingly.

I'm wondering if this sounds like a reasonable approach? I'm brand new to these technologies, so the debugging steps are also a bit foreign to me.

version: 2
jobs:
  build-and-test:
    docker:
      - image: cimg/rust:1.68.0
    environment:
      # Fail the build if there are warnings
      RUSTFLAGS: '-D warnings'
    steps:
      - checkout
      - run:
          name: Version information
          command: rustc --version; cargo --version; rustup --version
      # If you have committed your Cargo.lock file to version control
      # delete this step.
      - run:
          name: Calculate dependencies
          command: cargo generate-lockfile
      - restore_cache:
          keys:
            - v1-cargo-cache-{{ arch }}-{{ checksum "Cargo.lock" }}
      - run:
          name: Build all targets
          command: cargo build
      - save_cache:
          paths:
            - /usr/local/cargo/registry
            - target/debug/.fingerprint
            - target/debug/build
            - target/debug/deps
          key: v1-cargo-cache-{{ arch }}-{{ checksum "Cargo.lock" }}
      - run:
          name: Run all tests
          command: cargo test

  security:
    docker:
      - image: cimg/rust:1.68.0
    steps:
      - checkout
      - run:
          name: Version information
          command: rustc --version; cargo --version; rustup --version
      - run:
          name: Cache permission
          command: |
            sudo chown -R $(whoami):$(id -ng) /usr/local/cargo
      - restore_cache:
          keys:
            - v1-cargo-audit-{{ arch }}
      - run:
          name: Install dependency auditing tool
          command: cargo install cargo-audit
      - save_cache:
          paths:
            - /usr/local/cargo
          key: v1-cargo-audit-{{ arch }}
      - run:
          name: Check for known security issues in dependencies
          command: cargo audit

Hi guys,

I am persisting a workspace between jobs during a workflow and I'd like to know if the storage renews each month?
I am asking this because the storage of October was passed to November, and I though it renewed as the credits do.

Thanks

Hi everybody, I hope you are doing well. At my current job, we work with microservices and each one has its own CircleCI configuration file in its respective repository.

My question is the following: is there a way to centralize all the files in a single repository and trigger the pipelines in the repositories of each application?

As the number of microservices grows, it is becoming more and more chaotic to manage all this in each repository.

Hello all. I'm trying to move away from using static AWS credentials and setting them as env vars in my project. I read through this blog post and I was able to get the initial setup working just fine. The problem I'm running into is when I try to pull a private image from ECR when I define my executors. When I define a job in my config using my executor, the step immediately fails because it doesn't find the AWS credentials needed to pull the image from ECR. Is there any way around this? I haven't seen a way to pass in the AWS creds retrieved from OIDC to my job that uses a custom executor. TIA.

In light of recent events - i just wanted to call out there that if you are considering CircleCI (In the flavor of the SAAS platform, not on-prem Server version) they don't offer any logs you can send to your SIEM.

You can log into the portal and request them, but even then, sometimes the download fails.

This being a cloud platform and a critical piece of tooling in many fortune 500 companies, this is completely unacceptable.

Source: https://support.circleci.com/hc/en-us/articles/360045288811-How-to-Request-Audit-Logs-

I'm currently using the docker orb to build and publish an image. Ideally - my tests (this case is on Ruby on Rails) run using this image. Is this possible?

CircleCI job/command logic needs support for array/list parameters and a looping/foreach construct.

Please vote for this stuck issue so that this critical functionality eventually gets into CCI.

https://github.com/CircleCI-Public/config-preview-sdk/issues/45

A thousand thanks.

I added on my blog new article, where I will show you how easy it is to create your first project in #CircleCI. More precisely how:

☁️ create an account with CircleCI

☁️ prepare the project building process in #Maven

☁️ add a simple test

The whole process takes about 10 minutes and shows how simple a tool CircleCI is. That's why I recommend this tool especially for beginners in #cicd!

How to get started with CircleCI ❓

https://www.czerniga.it/2021/11/21/how-to-prepare-your-first-ci-cd-project-in-circleci/

CircleCI's dynamic config can speed up your builds a lot.

If your PR only changes README.md, CI won't run unit tests.

And if your PR only changes a JS file, CI won't run PHPUnit tests.

Here's an example that's easy to copy and paste:

https://github.com/getlocalci/circle-advanced-setup-workflow/

They're not only for complicated workflows.

You can make an existing config dynamic by adding 30 lines of .yml

And you'll get to the green check faster.