Bug 15638 - Need to change gitlab-ci.yml tags in all branches to avoid CI bill
Summary: Need to change gitlab-ci.yml tags in all branches to avoid CI bill
Status: ASSIGNED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Build (show other bugs)
Version: unspecified
Hardware: All All
: P1 major (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-22 19:42 UTC by Andrew Bartlett
Modified: 2024-06-19 14:35 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Bartlett 2024-04-22 19:42:54 UTC 
It looks like unless we change some tags, our CI jobs may get scheduled to the Rackspace runners rather than the GitLab.com runners.

https://docs.gitlab.com/ee/update/deprecations.html?removal_milestone=17.0#removal-of-tags-from-small-saas-runners-on-linux

(We will also need to re-provision the rackspace runners to that private CI can operate on the same tree. )

This is time-critical as it will cost money if we we don't get the change made in time.

17.0 is to be released on May 16, 2024 but they also list 3 breaking change windows for gitlab.com:

    2024-04-22 09:00 UTC to 2024-04-24 22:00 UTC

    2024-04-29 09:00 UTC to 2024-05-01 22:00 UTC

    2024-05-06 09:00 UTC to 2024-05-08 22:00 UTC
Comment 1 Andrew Bartlett 2024-05-02 07:04:07 UTC 
Per https://gitlab.com/gitlab-com/Product/-/issues/13310#note_1869717388 this will start to happen for us at:

2024-05-06 09:00 UTC to 2024-05-08 22:00 UTC

So we have until Monday to avoid costs.
Comment 2 Andrew Bartlett 2024-05-07 02:43:29 UTC 
Current status: Jobs are now running only on the Rackspace runners.
Comment 3 Samba QA Contact 2024-05-07 13:41:03 UTC 
This bug was referenced in samba master:

d58a72c572f63619111f43f6ea39ff84ae0df16e
Comment 4 Samba QA Contact 2024-05-29 19:26:23 UTC 
This bug was referenced in samba v4-19-test:

5502aa893cc02a7c8583113f67f2b22cac9804ee
Comment 5 Samba QA Contact 2024-05-30 10:58:46 UTC 
This bug was referenced in samba v4-20-test:

d5638013962fb9a8343ef7bf25ccb45a4fcd25dd
Comment 6 Stefan Metzmacher 2024-05-30 12:06:34 UTC 
https://gitlab.com/samba-team/devel/samba/-/pipelines/1311764986
has a pipeline for v4-18-test with all the relevant patches
Comment 7 Samba QA Contact 2024-06-10 15:31:46 UTC 
This bug was referenced in samba v4-19-stable (Release samba-4.19.7):

5502aa893cc02a7c8583113f67f2b22cac9804ee
Comment 8 Samba QA Contact 2024-06-19 14:35:26 UTC 
This bug was referenced in samba v4-20-stable (Release samba-4.20.2):

d5638013962fb9a8343ef7bf25ccb45a4fcd25dd