Skip to content

Mobile DevOps CLI Integration Support Request

Problem Statement

The Mobile DevOps product category currently lacks dedicated engineering support, and has technical debt that needs to be addressed which at times has impacted the error budget. The most significant portion of tech debt will be resolved with the integration of the Secure Files feature into the gitlab-cli. This will allow for engineering to more efficiently maintain the category for existing users.

Current State

  • Secure Files: file storage mechanism with its own AWS/GCP storage buckets, currently requiring both UI interaction and a separate download-secure-files CLI tool
  • macOS Runners: Inventory builder integrated into build process, but no clear mobile-specific usage visibility (though customer feedback suggests 95% of macOS jobs are mobile-related)
  • Integrations: Apple/Android Store integrations via integrations library
  • Support Model: Looking only to "keep the lights on" through reduction of tech debt and maintaining our target error budget SLO

Requested Work: CLI Integration Focus

Primary Objective: Migrate the Secure Files downloader functionality into the main gitlab-cli to resolve current tech debt issues and make maintenance of existing workflows more efficient for engineering.

Scope:

  • Integrate secure files download/management into gitlab-cli (Details to be added)
  • Estimated effort: TBD
  • [Linke to Epic]

Not in Scope:

  • Adding additional requested features
  • Ideation on project future capabilities with stable counterparts
  • Updates to the MacOs image build process or supporting app store integrations

Resource Requirements

  • Go Engineer: An engineer skilled in Go to do the gitlab-cli integration
  • Go Engineering Mentorship: Senior Go engineer for technical guidance and code reviews
  • Project Management: Manager overseeing the scheduled work.

Next Steps

  • Identification of DRI and assigned engineers: @freinink
  • Discovery: An engineer to work with @darbyfrey to detail the work needed in an epic with clearly defined implementation issues
  • Scoping of the work
  • Timeline commitment and milestone assignment
  • Implementation

Exit Criteria

  • Secure files functionality fully integrated into gitlab-cli
  • Feature parity with current download-secure-files capabilities as outlined in [Link to Epic]
Edited by Fred Reinink