We split the policy CSITs into the individual repos, thinking that developers would update the CSITs when making other code updates, but we haven't been doing that so far. Furthermore, this creates a number of problems:
- To test updates to a CSIT, the developer has to modify docker/csit to have it use the desired repo contents, instead of downloading the latest copy of the repo.
- Jenkins verification of CSITs is difficult, as the docker/csit would have to be modified to be able to pull code associated with the particular review. Furthermore, it would have to be modified to pull the docker image from the verify job instead of simply pulling the snapshot image
We should re-consider this approach and perhaps move the CSIT code from the individual repos back into docker/csit.
|121240,2||Merge csits into docker/csit||master||policy/docker||Status: MERGED||+2||+1|
|121290,2||Move remaining CSITs from to docker/csit||master||policy/docker||Status: MERGED||+2||+1|
|121342,1||Update comments in test plans||master||policy/docker||Status: MERGED||+2||+1|
|121352,1||Trigger CSITs on docker merge||master||ci-management||Status: MERGED||+2||+1|
|121448,2||Merge csits into docker/csit||honolulu||policy/docker||Status: MERGED||+2||+1|
|121449,1||Move remaining CSITs from to docker/csit||honolulu||policy/docker||Status: MERGED||+2||+1|