brandonchinn178 / brandonchinn178/mergit

Store version of merge bot in deployment

Open
#195 0 comments 0 reactions 0 assignees View on GitHub
infrastructure
Dominant language
Haskell
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

We should know what version of mergit is currently deployed at all times.

Maybe instead of making just the `mergit` binary a CI artifact, make a `mergit-bundle.tar.gz` bundle that contains the `mergit` binary and a text file with the current commit. Then uploading that bundle in the merge bot deployment would maintain a file on the EC2 instance with the commit stored in it.

Possibly also show it in the web UI

Related: #194

Contributor guide

No contributing guide indexed for this repository

Research direction

Trace the CI artifact creation and merge bot deployment mentioned in the issue, including how the bundle reaches the EC2 instance. Determine how the deployed commit would be stored and identify whether the web UI is in scope. Done means the deployed instance retains a file identifying the currently deployed mergit commit.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, github, haskell
Domain
cloud, devops, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.