Publish server builds from compile tasks
Server release candidate artifacts are not published until after an extensive set of tests have passed in the CI pipeline. These tests include ICW and all the CLI test suites. It is not unusual for time between a commit being pushed to a release candidate being published to be several hours, potentially slowing down the feedback cycle for component teams. This commit adds a "published" output to the compliation tasks. The new build artifact is stored in an immutable GCS bucket with the version in the filename. This makes it trivial for other pipelines to safely consume the latest build. This artifact **has not** passed any sort of testing (e.g., ICW) and should only be used in development pipelines that need near-instantaneous feedback on commits going into GPDB. For the server-build artifact, `((rc-build-type-gcs))` will resolve to `.debug` for the with asserts pipeline and `''` (i.e., empty string) for the without asserts pipeline. The two types of server artifacts that are "published" are: 1. server-build 2. server-rc server-build is the output of the compilation task and has had no testing; server-rc is a release candidate of the server component. Authored-by: NBradford D. Boyle <bboyle@pivotal.io> (cherry picked from commit 94a8ffc9)
Showing
想要评论请 注册 或 登录