|
…
|
||
|---|---|---|
| .. | ||
| bin | ||
| lib/gitlab | ||
| spec | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .rspec | ||
| .rubocop.yml | ||
| Gemfile | ||
| Gemfile.lock | ||
| README.md | ||
| Rakefile | ||
| gitlab-housekeeper.gemspec | ||
README.md
Gitlab::Housekeeper
Housekeeping following https://gitlab.com/gitlab-org/gitlab/-/merge_requests/134487
Running
Technically you can skip steps 1-2 below if you don't want to create a fork but
it's recommended as using a bot account with no permissions in
gitlab-org/gitlab will ensure we can't cause much damage if the script makes
a mistake. The alternative of using your own API token with it's permissions to
gitlab-org/gitlab has slightly more risks.
- Create a fork of
gitlab-org/gitlabwhere your MRs will come from - Create a project access token for that project
- Set
housekeeperremote to the fork you createdgit remote add housekeeper git@gitlab.com:DylanGriffith/gitlab.git - Open a Postgres.ai tunnel on localhost port 6305
- Set the Postgres AI env vars matching the tunnel details for your tunnel
export POSTGRES_AI_CONNECTION_STRING='host=localhost port=6305 user=dylan dbname=gitlabhq_dblab' export POSTGRES_AI_PASSWORD='the-password' - Set the GitLab client details. Will be used to create MR from housekeeper remote:
export HOUSEKEEPER_FORK_PROJECT_ID=52263761 # Same project as housekeeper remote export HOUSEKEEPER_TARGET_PROJECT_ID=52263761 # Can be 278964 (gitlab-org/gitlab) when ready to create real MRs export HOUSEKEEPER_GITLAB_API_TOKEN=the-api-token - Run it:
bundle exec gitlab-housekeeper -d -m3 -r keeps/overdue_finalize_background_migration.rb -k Keeps::OverdueFinalizeBackgroundMigration