Allow continuous build information and metadata to be serialized along with test runs
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
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.
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.
- Dominant language
- Python
- Stars
- 60
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from MarketSquare/DbBot
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
MarketSquare/DbBot#27 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
MarketSquare/DbBot#26 · 2 comments ·
-
Difficulty 2/5 Under an hour Newbie friendliness 48/100
MarketSquare/DbBot#25 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
MarketSquare/DbBot#24 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
MarketSquare/DbBot#23 ·
All issues in MarketSquare/DbBot
Similar issues
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31098 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
john-kurkowski/tldextract#382 ·
-
comp/tools duplicate P2 sweeper:risk-compatibility tool/mcp type/bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
NousResearch/hermes-agent#132042 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
deepset-ai/haystack#13092 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
feder-cr/invisible_playwright_mcp#1408 ·
Maintainers usually reply within 1 day