When lifecycle is released ahead of pack, the combinatorial testing for the pack pipeline causes both "previous" (latest release) and "current" (master) lifecycles to be the same. This results in not actually testing the previous release of lifecycle against the upcoming version of pack.
We should fix the logic in the pipeline to account for this and ensure we're properly testing combinations of pack and lifecycle.
simonjjones
commented
5 years ago
When
lifecycleis released ahead ofpack, the combinatorial testing for the pack pipeline causes both "previous" (latest release) and "current" (master)lifecycles to be the same. This results in not actually testing the previous release oflifecycleagainst the upcoming version ofpack.We should fix the logic in the pipeline to account for this and ensure we're properly testing combinations of
packandlifecycle.