Artifact Repository Migration
Greetings fellow Traveloka engineers
Background
We will be migrating our internal artifact repository from self-hosted Artifactory to S3.
Motivation
We want to have an artifactory repository which is:
- Highly available.
- Proper authentication and authorization.
- Publicly accessible, but protected.
- Low maintenance effort.
- Auditable.
Why S3?
- Availability
- 99.99% availability
- 99.999999999% objects durability
- Authentication and authorization
- Accessibility
- S3 is publicly accessible
- Protected via IAM
- Maintenance
- S3 requires almost zero (0) maintenance effort
- Auditability
Migration Plan
- Provision S3 maven artifact bucket (s3://beiartf-maven-artifacts-517530806209-5a48cdbd0210491c)
- PIC: Backend Infra
- Status: DONE
- Provision sync process between Artifactory and S3
- PIC: Backend Infra
- Status: DONE
- Allow read and write access for Jenkins
- PIC: Backend Infra
- Status: DONE
- Setup
beiartf-refresh on your machine
- PIC: You
- due date: 2nd of May 2018
- Change backend monorepo configuration
- PIC: Backend Infra
- Due date: 2nd of May 2018
- Change repository configuration
- PIC: Repository owner
- Due date: 1st of June 2018
- Revoke read and write access to Artifactory
- PIC: Backend Infra
- Due date: 1st of June 2018
- Change your old monorepo Jenkinsfile configuration
- PIC: Repository owner / All team
- Due date: 1st of June 2018
References
Thank you for your attention.
Cheers.