<!--Epic Template Instructions: - Replace all placeholder text with your specific content - Remove these instruction comments before saving - Use the Issue Administration section template for all child issues - Update the Development log as work progresses - Add a Status section at the end when the epic is complete--> # Problem Statement As part of DRI duties I had seen quite some pipelines failing because - [example 1](https://gitlab.com/gitlab-org/build/CNG/-/jobs/11961447065#L230) - [example 2](https://dev.gitlab.org/gitlab/charts/components/images/-/jobs/31762084#L813) - [example 3](https://dev.gitlab.org/gitlab/charts/components/images/-/jobs/31762084#L806) I saw this problem across the CNG, charts and omnibus packages. I also have it locally. We are always referencing ftp.gnu.org but we should try to use mirrors to obtain the software we need. # Goal <!--Define the high-level objective and specific outcomes. Use checkboxes for measurable goals that can be tracked. Be specific about what success looks like.--> Reduce the number of pipeline failures caused by ftp.gnu.org downtime. - [ ] Replace ftp.gnu.org references with ftpmirror.gnu.org in CNG - [ ] Replace ftp.gnu.org references with ftpmirror.gnu.org in [charts](https://dev.gitlab.org/gitlab/charts/components/images/-/issues/1) - [ ] Replace ftp.gnu.org references with ftpmirror.gnu.org in omnibus # DRI <!--DRI = Directly Responsible Individual Tag the person who owns the overall success of this epic Use @username format--> @sconstantingl # Participants # Issue Administration <!--This template should be used for all child issues created under this epic. Update the epic number and labels to match your context. Copy this exact text block for contributors to use.--> For all new issues that are children of this Epic, utilize the following template: ``` /epic [group-path]#[epic-number] /label ~"[primary-label]" ~"[team-label]" ~"[category-label]" ~"[section-label]" ~"[type-label]" ``` # Development log <!--Use this section to track major decisions, discoveries, and progress updates. Add new entries at the top (most recent first). Use collapsible details sections for longer updates. Include dates and key participants in discussions.--> <details> <summary> ### \[YYYY-MM-DD\] - \[Brief description of update\] </summary> \\\[Detailed description of what was discussed, decided, or discovered\\\] ### \[Subsection if needed\] \[Additional details, decisions, or action items\] ### Actionable Items </details> --- <!--STATUS NOTE SECTION: This section will be managed and updated automatically by this project: https://gitlab.com/gitlab-com/gl-infra/epic-issue-summaries--> <!--STATUS NOTE START--> <!--STATUS NOTE END-->