-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Extend skaffold debug
integration tests to buildpacks
#4352
Extend skaffold debug
integration tests to buildpacks
#4352
Conversation
Extends integration tests to test `debug` with GCP Buildpacks using both Procfiles and the new project.toml.
Codecov Report
@@ Coverage Diff @@
## master #4352 +/- ##
==========================================
- Coverage 71.76% 71.71% -0.05%
==========================================
Files 324 324
Lines 12512 12514 +2
==========================================
- Hits 8979 8975 -4
- Misses 2965 2969 +4
- Partials 568 570 +2
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with a couple of nits
configurations: | ||
|
||
- `skaffold.yaml` configures docker- and jib-based builders | ||
- `skaffold-bp.yaml` configures buildpacks-based builders |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you use two profiles?
integration/debug_test.go
Outdated
args []string | ||
deployments []string | ||
pods []string | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
linter complains on the new line
Description
Extends integration tests for
debug
to test building with GCP Buildpacks using both Procfiles and the new project.toml. We reuse the existing test projects rather than define new projects. Like the existing tests, it continues to check that the language debugging runtimes are enabled and responding.These tests verify that pods and deployments are annotated with the debug configuration metadata and contains the working-directory and runtime. These annotations are used to drive the
DebuggingContainerEvent
event.Other changes:
jib
tests tojava
since the buildpacks mode doesn't use Jib.check-jdwp.sh
script to be placed in/workspace/scripts
to be in the same place with both Jib and Buildpacks images.