| << Back to previous view |
|
[QB-1769] QuickBuild repository option "latest finished build" should not fail downstream build even if the build is failed
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 5.0.36 |
| Fix Version/s: | 5.1.0-rc1, 5.1.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Robin Shen | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 1 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Comments |
| Comment by Bill Houglum [ 19/Sep/13 07:44 PM ] |
|
My repository has the build option set to "latest finished build", but I still get the following error:
17:00:23,068 INFO - Checking out revision 'configuration:root/RDM/12.0/Build/RC, build id:26835' of repository 'Packages'... 17:00:23,068 INFO - Waiting for finish of dependency build (configuration: root/RDM/12.0/Build/RC, build id: 26835) 17:01:57,908 INFO - Executing post-execute action... 17:01:57,908 ERROR - Step 'master>Release>Get Packages' is failed: Dependency build not successful (configuration:root/RDM/12.0/Build/RC, build id:26835) I don't care if the dependency build successful or not, I just want access to whatever artifacts have been published in that configuration. That is why I didn't choose "latest successful build" or "latest recommended build". I consider this a bug...let me know if I'm doing something wrong. |
| Comment by Robin Shen [ 20/Sep/13 12:36 AM ] |
| Yes, we have not yet solved the issue. Will get it into a release one or two weeks later together with many other important changes. |