Bug 1233507 - It is possible to run two builds concurrently
Summary: It is possible to run two builds concurrently
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Ben Parees
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-19 04:51 UTC by Tomas Schlosser
Modified: 2016-01-29 00:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-29 00:06:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tomas Schlosser 2015-06-19 04:51:42 UTC
When triggering a build, there should be a check whether the build is already running and if so, the new build should be queued and not run concurrently.

If two builds are running concurrently, the second one always fails.

Comment 2 Wenjing Zheng 2015-06-19 06:00:58 UTC
Comments from Openshift QE:
This is more like a feature request. It is not enough to just check whether there is build running under project before a new build, should also check whether the running build is using the same resources with the new-started build, for if they are using different resources, there is no conflict to have two running build.

Comment 3 Michal Fojtik 2015-06-19 13:05:08 UTC
The second one fail usually because you can push same image to one registry (the second push will fail).

Comment 4 Ben Parees 2015-10-02 09:05:39 UTC
In the case where both builds are building against "HEAD" it's difficult to know if they are building the same thing (the commits might or might not be the same).

we'd have to determine the commit to build before starting the build (which would also help with being able to rebuild an exact build).

Comment 5 Ben Parees 2016-01-29 00:06:22 UTC
trello'd: https://trello.com/c/Wz8FFwko/849-single-threaded-builds


Note You need to log in before you can comment on or make changes to this bug.