Add CI
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
The issue only specifies running the tests on the JVM and names no CI file, command, or test path. First locate the project’s test entry point and determine whether CI configuration already exists. Done means an automated JVM job runs the tests successfully.
Written by the indexing model from the issue text.
Description
Run the tests to ensure the code is still working. JVM is good enough.
- Dominant language
- Java
- Stars
- 5
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
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.
More from Azure-Samples/java-native-telemetry
-
Enable Dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Azure-Samples/java-native-telemetry#72 · 1 reaction ·
-
Azure-Samples/java-native-telemetry#67 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in Azure-Samples/java-native-telemetry
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100