Remove loadimpact/k6 Docker image from build process
#3494
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
olegbespalov
approved these changes
Dec 7, 2023
mstoykov
approved these changes
Dec 7, 2023
andrewslotin
force-pushed
the
stop_building_loadimpact_k6
branch
from
1ff9a3d to
7f578c9
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3494 +/- ##
=======================================
Coverage 73.20% 73.21%
=======================================
Files 267 267
Lines 20090 20090
=======================================
+ Hits 14707 14709 +2
+ Misses 4468 4466 -2
Partials 915 915
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
This PR updates the build pipeline to stop maintaining the
loadimpact/k6image on DockerHub.Why?
Earlier this year we have announced that we will stop maintaining the
loadimpact/k6Docker image. For two years afterk6has joined Grafana we have been maintaining this image for backward compatibility and starting Dec 31st we will officially stop pushing updates to this image.We expect
grafana/k6to be fully compatible and don't require any changes beyond updating the image name.Checklist
Related PR(s)/Issue(s)
Closes #3493