Updating docker image checks to make sure JMX image available and used for pipelines #1266
+56
−12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Added a check to make sure JMX image of the Agent is deployed. Also has a new function called
InternalRegistryFullImagePathExists
that allows me to use a computed Docker image path. This means that tests that don't care about the JMX image won't have to rely on that job in the gitlab pipeline.Which scenarios this will impact?
Docker end to end test.
Motivation
To run e2e tests for JMXFetch we need the Docker image with Java published.
Additional Notes
This PR will break
main
on the Agent if merged before the update the gitlab ci definitions that publish the JMX docker image for QA. It needs the PR here to be merged first.