Duplicate build labels
We are running multiple build engines and trying to test concurrent builds running on the same machine (RTC 1.0.1). If we submit builds at the same time against the same build definition we sometimes end up having 2 builds with duplicate build labels. These builds are also suffering some test crashes which I guess may or may not be related to the build label duplication. So, questions....
1) is the build label duplication harmless or a problem? If a problem, is it known and is there a fix?
2) are there other issues known when running multiple build engines on one machine? They are using different directories to extract/build into.
Thanks, Alex.
1) is the build label duplication harmless or a problem? If a problem, is it known and is there a fix?
2) are there other issues known when running multiple build engines on one machine? They are using different directories to extract/build into.
Thanks, Alex.
One answer
Hi Alex,
Are the build engine (jbe) processes using the same engine id or different ones? We don't recommend running multiple build engine (jbe) processes for the same engine id, though it should mostly work. A given build request should only get claimed once.
The build label is assigned on the build machine based on the current time, so if both builds get started at the same time, they'll have the same label.
Having multiple builds with the same label should not cause problems, though. They're not intended to be unique, and aren't used in queries. Ant tasks that refer to a particular builds use build result item id (e.g. the buildResultUUID attribute of the various publishing tasks).
What crashes/failures are you seeing?
Are the build engine (jbe) processes using the same engine id or different ones? We don't recommend running multiple build engine (jbe) processes for the same engine id, though it should mostly work. A given build request should only get claimed once.
The build label is assigned on the build machine based on the current time, so if both builds get started at the same time, they'll have the same label.
Having multiple builds with the same label should not cause problems, though. They're not intended to be unique, and aren't used in queries. Ant tasks that refer to a particular builds use build result item id (e.g. the buildResultUUID attribute of the various publishing tasks).
What crashes/failures are you seeing?