For triggers, you can activate an option called “Force Repository Check” which ensures, that you get the latest stuff.
However, when you have a configuration that is started only manually (all of our version configurations), there is no trigger, so there is no check forced.
this means, if you start a build that is below that global polling frequency of the repository and your merge, you miss some change sets.
is there a way to have this “Force Repository Check” button for manually started builds e.g. at the “Details” page of a configuration?
We want to make sure that you cannot miss something, when the version is pulled because you were starting the build too fast.
Hi Christian,
Manually started builds always check all associated repositories for new changes before starting the build.
If a build is missing a changeset, then it could be that the change has not yet been registered with the svn server … or there’s a bug. We would need to see a debug log of the build running to troubleshoot a bug in this area.
i can say, its very reliable reproducable. Asking der SVN server for new change sets directly after committing one shows it (would be strange if not). So i assume it must be Continua.
What should i do in detail for the logs you require?
hm, i’ve noticed on option that i have never seen before: “Match branch pattern against top-level folders only” in the repository options.
well, for ourstructure, this is not true, it switched it off.
but therefore, this could mean that continua didn’t noticed the merged changesets because it didn’t monitored them right?
Hi Christian,
Yes, this could be the reason that Continua didn’t detect the changeset. It is, however, hard for me to say what happened without knowing the full repository settings and the repository structure. Also, this would mean that the changeset is never picked up - not just missed when you start the build. Is this what is happening? You can see which changsets are picked up by Continua on the Changes tab of the Configuration view.
The “Match branch pattern against top-level folders only” option is used to decide which folders are scanned when detecting branches. Subversion branches can be any folder, so we generally need to scan the whole folder structure to find which folders match the branch pattern - and this can be slow. This option tells Continua to only search the top level folders under the Branches Path and is off by default.
If your branches path is “/branches/” and branch pattern is “/[^/]+/” this will increase performance significantly when first initialising the repository. If this option is switched on and the branch pattern is “/[^/]+/subfolder” for example then Continua will not detect any branches, and you will only detect changesets on the default branch.
To troubleshoot your issue further, we would need the current repository settings. The easiest way to supply these is by downloading the diagnostics report from the Administration -> Event Log page. Send this to support@finalbuilder.com along with details of the repository folder structure.
This still may not be enough information to work out what is happening in your situation. To help us diagnose the issue quickly, enable debug logging and restart the service before making the commit to the repository. Then run the build. If the build does not pick up the new changeset as expected, email the debug log to us along with the other details.