Build Config Running Twice


Here’s the link to the travis build:

The build was passing for many days, but yesterday the build said it failed, even though the tests in the build passed.

I checked the Build Config section under the View Config tab, and for some reason the Build Config shows a build happening twice now:

Even though for many days before, the Build Config had only one build showing in the config, and looked like:

This has happened to many of our other repos as well.


What am I supposed to be looking at? This build failed because it is trying to invoke ../scripts/, which doesn’t exist.

In the command immediately preceding, you are running cd $logPath. Are you sure you are where you want to be?

cd $logPath is a part of the API payload, so whatever you did to generate this payload is probably to blame.

If you go to the View Config tab and compare the build config for the two travis tests that I sent,
The one which is working fine doesn’t have the red section:

There were no changes made to anything and suddenly that red section started appearing yesterday out of nowhere, which is causing the test cases to fail.

You can see that the first build execution is successful, and then the build ends up in the logs directory. However, because of the second build, which is appearing out of nowhere, it is trying to find the in that logs directory (which is in a different location) and that’s why it’s failing. But we did not add this second build in the first place.

I understand now. Thanks for the explanation.

this description is misleading; the resulting configuration is concatenating script sections from the API payload and the counterpart in .travis.yml instead of overwriting it.

We’ll take a look.


I was wondering if you were able to figure out the cause of this issue?


Sorry for the delay.

This is due to the currently undocumented change in processing the API payloads, which is part of the upcoming build configuration validation. We changed the default way of handling arrays in the API payload when there is existing data in the configuration.

While we wait for the documentation, you can try a couple of things:

  1. Turn off config validation
  2. change the merge mode to merge.

To take advantage of the configuration validation, I personally recommend the latter.

Please test this, and let us know how you get on.


Hi! Changing merge_mode to merge appears to be working for now, thanks!

1 Like