Failure to recognize v2 build format on first commits on new branch


#1

We have our repo on bitbucket and we’ve set up Circle CI to only run builds that have active pull requests. On the first build per pull request, the build fails since Circle fails to recognize that it should run on Circle 2.

Sample build here: https://circleci.com/bb/zaptag/zapsrc/3748

Rebuilding does not work. The workaround has been to issue a new commit (possibly amending the last one).


#2

I reported this to our engineers. Thank you!


#4

This has now been resolved!


#5

Hm. Doesn’t look like it. Still fails to recognize as v2:

https://circleci.com/bb/zaptag/zapsrc/3957


#6

Interesting! Thank you. I will reopen the bug ticket.


#7

@jvliwanag Do you have a .circleci/config.yml file? It could be taking precedent over circle.yml.


#8

No we don’t. We only have circle.yml


#9

Thank you. We took a deep look at this and it’s an interesting issue you’re hitting. We opened a technical bug report on it; hopefully it’ll be resolved soon.


#10

I’m having a similar problem but I am using .circleci/circleci.yml and no circle.yml
https://circleci.com/gh/omnypay/pantheon-modules/1112

Its running it as a v1 run as far as i can tell.


#11

Looks like your config is invalid.


#12

Finally got things working. One thing was realizing its .circleci/config.yml and not .circleci/circle.yml!


#13

I’m afraid this isn’t solved yet for us. Looks like if repo is set up to only build if there’s a pull request open, then the first build upon opening that pull request is always recognized as circle 1.0. If we turn off building only on pull requests, then this sidesteps the issue.


#14

Can you link me to your builds so our engineers can further investigate?


#15