Details
-
Enabler
-
Should have
-
None
-
True
-
Data Processing
-
-
-
2
-
2
-
5.5
-
Team_ORCA
-
Sprint 5
-
-
-
-
-
Com-G2
Description
Release processes could roughly as follows - for every involved repository (in dependency order!) do:
- update to newest released (!!) dependencies (or hold back manually), e.g. using `poetry update`
- commit the new dependencies (i.e. poetry.lock)
- create a tag for the registry
- push and have CI build the actual registry package
- ... continue for next layer
To ensure that this does not generate new surprises, CI tests should ideally also be adjusted to run `poetry update` (to get current external dependency releases) and ideally `skairt update` (to get "bleeding edge" packages - likely needs work!). If nightlies were staggered in dependency order with a ~1 hour gap this would mean we build everything every night from the bottom up, giving us strong assurances that
- Problems are going to get spotted as early as possible
- The above release process has a high likelihood to succeed
See also considerations from SP-1372 (now discarded)
Attachments
Issue Links
- relates to
-
SP-1372 SDP CI Pipeline improvements (continued)
- Discarded
- split from
-
SP-1524 Improve SDP configurability
- Done
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...