BuildStream-Migration-Bot opened a new issue #1387: URL: https://github.com/apache/buildstream/issues/1387
[See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/1387) In GitLab by [[Gitlab user @Qinusty]](https://gitlab.com/Qinusty) on Aug 24, 2020, 14:53 ## Background Currently [overnight-tests](https://gitlab.com/BuildStream/buildstream/-/blob/master/.gitlab-ci.yml#L318) run a build of FDSDK against a persistent external cache (https://cache-test.buildstream.build:11002). This test definition means that each run of tests may differ based on the state of the external cache state. This could lead to nightly tests passing due to a fully cached build state. ## Task description My proposed solution to this is as follows, however input via comments is expected. [//]: # (Short summary of the action to be executed) * [ ] Clean this external server nightly to ensure that WRITE operations work as expected. (Or salt build) * [ ] Perform a second build against the fully cached build to ensure that READ operations are also successful * [ ] Apply a patch to the FDSDK sources and cause an incremental build. Additionally, it would be ideal for these tests to be executed against both a bst-artifact-server deployment as well as a third party cache stack supporting buildstream i.e. buildbarn with [bb-asset-hub](https://github.com/qinusty/bb-asset-hub). ## Acceptance Criteria [//]: # (Acceptance criteria should follow the S.M.A.R.T. principle https://en.wikipedia.org/wiki/SMART_criteria ) - Buildstream CI must test the functionality of Buildstream to successfully cache builds using remote-asset/remote execution storage solutions. - Buildstream should ensure compatibility with a defined version of a third party cache deployment is maintained via overnight tests. (Follow up of https://gitlab.com/BuildStream/buildstream/-/merge_requests/2037) ---- [//]: # (To review information about possible relevant labels for this issue please view the list of labels: https://gitlab.com/BuildStream/buildstream/labels) ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
