The place of GitLab within a mobile team's processes
summary
Concrete use of GitLab APIs and GitLab CI for a mobile app: Review Apps deploy feature branches so designers, PMs and SQA can test; CI triggers per-branch builds running lint, unit and integration tests on runners. A small CLI normalizes branch names and creates merge requests from Jira tickets; a changelog site pulls tags and labels to generate release notes and CSVs; scheduled weekly promos and on-merge master deployments demonstrate the full pipeline.
AI-written summary · about
chapters (12)
- 0:00GitLab in mobile processes
- 2:07Team and mobile context
- 3:10Mobile processes matter
- 5:19GitLab as project tool
- 7:24Automation with GitLab CI
- 10:22Code review and tests
- 12:51Onboarding best practices
- 13:54Sharing builds with testers
- 15:23Integration tests and QA
- 16:51Release management and changelog
- 18:38Experience and extra tools
- 20:07GitLab process gains
related talks
50mEmpowering Mobile Team to Harness Real Power of CI/CD
11mGitLab CI Integration: Automated Testing and Deployment
16mMobile CI Server with GitLab CI and Fastlane
19mAgents at work: plan - test - CR - deploy - repeat
52mFrom 0 to Continuous Deployments with Kubernetes, Helm and GitLab
24mReinvent your pipeline with GitLab, Kubernetes, and Amazon EKS
21mDriving Cultural Change to Improve Software Development and CI/CD
47mGitLab and PHP? It Works! Tips, Tricks and Learnings