ci: docker
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Start by inspecting the repository's CI setup and any Docker-related configuration to determine where the bitcoind image should be defined and consumed. Verify that the image starts bitcoind in the background and that CI can use it to automate tests; the work is done when the CI workflow runs successfully with the service available.
Written by the indexing model from the issue text.
Description
There needs to be a docker image which runs bitcoind in the background so that CI can automate tests.
- Dominant language
- Go
- Stars
- 58
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 evstack/bitcoin-da
-
Tests failing in CI Open
evstack/bitcoin-da#27 · 1 assignee ·
-
evstack/bitcoin-da#25 · 1 assignee ·
-
feat: namespaces Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
evstack/bitcoin-da#20 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
evstack/bitcoin-da#12 ·
-
docs: spec Open
Difficulty 3/5 1-2 days Newbie friendliness 30/100
evstack/bitcoin-da#8 ·
All issues in evstack/bitcoin-da
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·