Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Undefined
Fix Version/s: openshift-4.14
Affects Version/s: None
Component/s: None
Labels:
None

Work Type:
Proactive Architecture
Story Points:
1
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Epic Link:
USHIFT-1600
Intelligence Requested:
Market:

Sprint:
uShift Sprint 245

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Schedule CI build cache update job to an S3 bucket in the MicroShift AWS account.

See this discussion about which S3 bucket should be used: https://redhat-internal.slack.com/archives/CBN38N3MW/p1699265727246839

blocks

USHIFT-1885 Reorganize test image blueprints to maximally benefit from layer1 caching

Closed

depends on

USHIFT-1547 cache group1 scenario images in private S3 bucket

Closed

is related to

USHIFT-1933 Set alerts for failed cache update jobs in CI

Closed

links to

openshift/microshift#2599: USHIFT-1845 USHIFT-1846: Update testing framework documentation with the new layering and caching techniques

openshift/microshift#2610: USHIFT-1845: Avoid overwriting existing build cache contents in S3 on upload

openshift/microshift#2613: USHIFT-1845: Verify build cache and skip CI rebuild and upload if data already exists

openshift/microshift#2631: USHIFT-1845: improve CI check_contents function in manage_build_cache

openshift/release#45582: USHIFT-1845: MicroShift metal cache update job

openshift/release#45765: USHIFT-1845: Add a presubmit job on cache-related script changes

openshift/release#45818: USHIFT-1845: Configure CI cache updates for MicroShift on ARM platform

openshift/release#45902: USHIFT-1845: Fix MicroShift CI cache presubmit condition on arm platform

(6 links to)

Assignee:: Gregory Giguashvili

Reporter:: Gregory Giguashvili

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2023/11/06 3:59 PM

Updated:: 2024/08/19 7:42 AM

Resolved:: 2023/11/23 12:57 PM