MarketSquare / MarketSquare/DbBot
Allow continuous build information and metadata to be serialized along with test runs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 60
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Description
It would be useful, if the dbbot could save a table for continuous integration server information for each test run. Analysing the test results in context of CI server information would be a useful feature.
Some of the columns that could be saved
CI_REPO - repository name of the current build
CI_BRANCH - branch name for the current build
CI_COMMIT - git sha for the current build
CI_BUILD_NUMBER - build number for the current build
CI_PULL_REQUEST - pull request number of the current build
CI_BUILD_URL - url for the current build
CI_TAG - tag name for the current build
This is essentially more metadata for a test run and can be provided as a separate file or arguments to the command line.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by tracing the command-line serialization path and the SQLite test-run schema; determine how CI metadata is supplied and stored, then verify that a run preserves the listed CI fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python, sqlite
- Domain
- ci-cd, cli, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100