| << Back to previous view |
|
[QB-2923] Record changes does nothing in promoted builds, only in the entry point (the first build in the pipeline)
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 7.0.7 |
| Fix Version/s: | 7.0.8 |
| Type: | Bug | Priority: | Major |
| Reporter: | AlSt | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
We have one configuration which is scheduled every 10 minutes to check if there are new commits on 3 different git repositories. This configuration promotes to another stage and so on. We have a "Record Changes" step in every step to record the changes on the build since the last build. But this only works on the first pipeline stage and nothing is recorded for the other stages.
|
| Comments |
| Comment by AlSt [ 09/Mar/17 03:03 PM ] |
|
This was introduced in 7.0.4 as the changedRecorded flag is now part of the repository runtime and not of the repository itself. Which makes no sense as the changes recording should be build related and not pipeline related. And repository runtimes are passed over to promoted builds.
See: com.pmease.quickbuild/src/com/pmease/quickbuild/repositorysupport/Repository.java#432-442 com.pmease.quickbuild/src/com/pmease/quickbuild/DefaultBuildEngine.java#1774 |