Details
-
Feature
-
Must have
-
None
-
Data Processing, Services
-
-
-
Inter Program
-
1
-
1
-
8
-
8
-
Team_PSS, Team_SYSTEM
-
Sprint 5
-
-
-
-
14.1
-
Stories Completed, Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO
-
-
SPO-1582
Description
During work done in SP-1881, the FPGA-based PSS modules within the Rabbit library was successfully built on the Kelvin reference server, but the CI pipeline could not store the artifacts from the build stage to the gitlab artifact repository because of the latters size limitations.
Currently the full build is disabled and only the much smaller emulator components are currently being built. This gitlab size limitation needs to be resolved by the Systems team before we can activate the CI pipeline for production
To give an examples of the problem. The FPGA device binary image of each module is greater than 150MB which exceeds the defined limit of 100MB Gitlab artifacts. There are currently 3 modules and more are expected to be added over time)
The pipeline is currently set up to create rpm packages. We need to add an additional stage to publish these packages to a central yum repository dedicated to pss. Systems support is required to set up this repository, and provide the tooling required to QA, sign, and publish these packages to this repository.
The publishing solution should have the following properties:
- The publication should be associated with a specific branch. In the first instance this will be master and will be our "production" version. In the future we may, for example, wish to add a "beta" branch to facilitate acceptance testing by the BO before we allow it to go into production.
- The packaging QA should be performed and passed before the merge into the branch is allowed
- The version number should be changed as part of the MR
- The merge shall trigger the publication of the rpm such that at any time the contents of the branch shall have a corresponding package in the yum repository.