Skip to content

Remove deploy-s3 job

Darby Frey requested to merge remove-s3-deploy-job into main

The deploy-s3 job appears to be a redundant deploy script, and from what I can tell, the deployed content isn't actually used. I'm proposing we remove this job for now and see if we notice any issues. If something comes up, this change can be reverted quickly. We should leave the ROLE_ARN and S3_BUCKET CI variables in place until we feel comfortable this job isn't necessary.

@cynthia @dnsmichi what do you all think?

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Division: If the update affects your division, share the MR in your division Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Commits

  • Remove deploy-s3 job

Merge request reports