I set up two .circleci/config.yml files with the same stuff in them and I pushed them up. But for some reason my builds fail with an odd error so when I click configuration to see what the config is I see this:
``` jobs: Build Error: docker: - image: bash:4.4.19 steps: - run: name: Config Processing Error command: |- # Unable to parse YAML # while scanning for the next token # found character '\\t(TAB)' that cannot start any token. (Do not use \\t(TAB) for indentation) # in 'string', line 7, column 1: # \t- build-* # ^ false workflows: version: 2 Build Error: jobs: - Build Error version: 2 # Original config.yml file: # version: 2 # jobs: # build: # branches: # only: # - test-build-initial # \t- build-* # docker: # - image: debian:stretch # steps: # - checkout # - run: # name: Greeting # command: echo Hello, world. # - run: # name: Print the Current Time # command: date ```
My build fails with this error on both projects:
#!/bin/sh -eo pipefail # Unable to parse YAML # while scanning for the next token # found character '\\t(TAB)' that cannot start any token. (Do not use \\t(TAB) for indentation) # in 'string', line 7, column 1: # \t- build-* # ^ false Exited with code 1
Why is it that my config.yml is being commented out and called “Old Config” and being replaced with this other config I’ve never seen before. My projects are even using docker…
Never had this happen before, why isn’t it using the config I set up? Where is it getting that other config from?
I got it to work finally, however my master branch is now having the circleci builds run even though my config is as follows:
``` version: 2 jobs: build: branches: only: - test-build-initial - build-* docker: - image: debian:stretch steps: - checkout - run: name: Greeting command: echo Hello, world. - run: name: Print the Current Time command: date ```
The test-build-initial branch runs, as does any build-* branch. But master runs as well. Why is this? From my past experience it shouldn’t run master’s builds with my current config (it doesn’t in other projects I have as far as I can recall). Any idea why this is happening? Is my config flawed? What could possibly be causing it to build master without it being specified in the config.yml?