Bug 1233507
| Summary: | It is possible to run two builds concurrently | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Tomas Schlosser <tschloss> |
| Component: | Build | Assignee: | Ben Parees <bparees> |
| Status: | CLOSED UPSTREAM | QA Contact: | Gaoyun Pei <gpei> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.0.0 | CC: | bparees, dmcphers, libra-bugs, mfojtik, wzheng |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-01-29 00:06:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tomas Schlosser
2015-06-19 04:51:42 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. The second one fail usually because you can push same image to one registry (the second push will fail). 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). |