-
Epic
-
Resolution: Won't Do
-
Medium
-
None
-
None
-
None
-
offline-download
-
Done
Download part of our offline platform build/packaging is rarely used (we usually have platform downloaded once) - more issues are happening with freshly downloaded platform.
Scripts are not working reliably (see BuildGuide)
Our goal is to improve that so we can add it into our CI pipeline.
DoD:
- improve reliability of download artifacts (retries ? callbacks ?)
- in case of failure, script must announce it in better way
- in case of success, some flag file might be generated ... to confirm that download was successful. all artifacts were collected and platform can be used in nexts steps (nexus blobs build, installation , ...)
- we should consider also "delta-download" e.g. in case of previous failure => not whole download is triggered again but just some delta
(stretch goal is to reflect changes in datalists, so just updated/new artifacts will be downloaded)
- relates to
-
OOM-1847
Prepare initial Dublin platform for early testing
-
- Closed
-
-
OOM-1849
Adding download procedure into pipeline
-
- Closed
-
-
OOM-1924 Remove binaries preparation from download process
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
OOM-1964 Wrong shebang for download scripts
-
- Closed
-
-
OOM-1917
Change data lists to more structured format
-
- Closed
-