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

Empty commits cause build failures #101

Open
elijahe opened this issue Jan 5, 2024 · 0 comments
Open

Empty commits cause build failures #101

elijahe opened this issue Jan 5, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@elijahe
Copy link

elijahe commented Jan 5, 2024

Orb version:

1.0.0

What happened:

When using a path-filtering configuration without a single continue_config.yml file an empty commit (e.g. git commit --allow-empty -m "[deploy-test] test deploy") causes a build failure. The build fails with the following message:

Checking For yq + CURL
Config list ===
.circleci/continue_config.yml
Generated YAML ===
Error: open .circleci/continue_config.yml: no such file or directory

Exited with code exit status 123

Sample circleci config which can be used to recreate the issue along with an empty commit:

---
version: 2.1

setup: true

orbs:
  path-filtering: circleci/[email protected]

workflows:
  generate-config:
    jobs:
      - path-filtering/filter:
          base-revision: << pipeline.git.branch >>
          mapping: |
            be/.* build-be true be/.circleci/config.yml
            fe/.* build-fe true fe/.circleci/config.yml
            .* build-root true .circleci/root_level_config.yml

Expected behavior:

The build should not fail. Ideally, any catch-all path filtering configs (e.g. .*) should also run.

@elijahe elijahe added the bug Something isn't working label Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant