Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.3.6
-
Fix Version/s: None
-
Component/s: Distributed Builds
-
Labels:
-
Complexity:Intermediate
-
Number of attachments :
Description
I have a project with 2 build definitions and both have the same build environment( with attached build agent A)
1. Build project with build definition A
2. Project will build in build agent A
3. while project is still building, build project again using build definition B
Actual Result: Project will be queued/build in build agent A
Expected Result: Project will not be queued/build in build agent A because it's still building there.
If the build agent group only consist of one build agent, then the project will not build at all.
If the build agent group contains many build agent, then the project will build on the other build agents in the group where it isn't currently building.
Projects don't get queued in build agents. Can you clarify what you mean in the subject?
From the Expected Result, I don't like that it will build sometimes and not other times depending on the configuration (how many agents). That's going to be confusing for a user who doesn't know how many agents there are, he just wants his project to build.
Considering that there is another feature request open to split up a multi-module build across agents, it seems safer to say that if a project is currently building, it must not be built again until the first one is finished.
(I don't think that precludes queueing it, I just don't want it building at the same time, which seems like it would step all over itself in the remote repository.)
Do we have user stories for this feature? I'm concerned that changing this one bit of functionality will affect other things we're not considering. I'm going for simple and consistent.