Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interactive Debugging Guide #1733

Closed
Harwayne opened this issue Aug 23, 2019 · 4 comments
Closed

Interactive Debugging Guide #1733

Harwayne opened this issue Aug 23, 2019 · 4 comments
Assignees

Comments

@Harwayne
Copy link
Contributor

Create a guide that explains how to use squash to interactively debug a container running in K8s. Give a concrete example debugging the eventing controller.

@Harwayne
Copy link
Contributor Author

/assign

@jonjohnsonjr
Copy link

Might be worth committing it to the ko repo and linking to it from the knative repos, since it's not really knative specific.

@n3wscott
Copy link
Contributor

Tracked in the ko repo, closing from knative.
/close

@knative-prow-robot
Copy link
Contributor

@n3wscott: Closing this issue.

In response to this:

Tracked in the ko repo, closing from knative.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

matzew pushed a commit to matzew/eventing that referenced this issue May 3, 2022
… CI (knative#1733)

* Set ARTIFACTS based on ARTIFACT_DIR provided in CI

The tests are using the ARTIFACTS dir to store JUnit results so they
should be available in the job report.

* Add BUILD_NUMBER

Co-authored-by: Martin Gencur <mgencur@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants