CircleCi does not checkout latest code from GitHub

Build Environment
1

CircleCi does not checkout latest code from GitHub.
It always builds from initial checkout.

Am I missing something.
So far it is very hard to use…

2

Without more information, readers are almost certainly going to be unable to assist you. Is your repo and CircleCI project public?

If not, perhaps you could clarify what is happening: are you triggering a build on a schedule or a branch push? Is this master or a non-master branch? What do you mean by “initial checkout”?

1 Like
3

I created new project in CircleCi, triggered the build, it checked out master branch from github (public) and thats was it. CircleCI would not trigger another build on new check in of the code.
I have to do tribal dance around it with some sacrifices to gods for it to work.

Unfollowed the project, went back to Github, deleted all the CircleCi hook, followed project again and only then it started to work.

After that I got beautiful error
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.627 s
[INFO] Finished at: 2019-06-14T18:55:38Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project lookup: There are test failures.

After some googling it appears that CircleCi OpenJDK8 image uses and older version of OpenJDK8 which has some bugs…

UI is very unfriendly at all as well…

4

CircleCI has been rock-solid for me for probably a couple of years now, bar some very minor outages. So, if you want to fix this, you’ll need to find out what is different between your config and everyone else’s. Would you show your config? That would be best in a formatted block (as would your error above) - you can do that by adding a code gate like so:

```
code goes here
```

You can always switch the Docker image to one that works for you.