Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Enable Command Execution Across Containers/Network

Open
#103 8 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
devops, testing-qa

Research direction

Review the dotnet-coverage collect and shutdown entry points and the container-a/container-b CI/CD scenario described here. Define done as allowing container-b to trigger a graceful shutdown or snapshot of the session running in container-a, including how the proposed --address hostname would be used.

Written by the indexing model from the issue text.

Description

enhancement

Hi!

This is probably an enhancement request, but my current issue is:

Consider a CI/CD pipeline @integration-tests stage.

container-a:
-./dotnet-coverage collect "Service.Api" --session-id integration-tests

container-b:
-dotnet tests IntegrationTests ... (against container A)
-dotnet-coverage shutdown integration-tests (unable to do it)

I want to be able to execute a gracefull shutdown (or snapshot) of container-a via container-b. How to do it?

A possible enhancement could involve setting something like --address container-a-hostname

Thanks in advance

Dominant language
C#
Stars
125
Forks
17
Avg merge
1h 17m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/codecoverage

All issues in microsoft/codecoverage

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.