Discontinue go-ci-stable-debian-build container image?
#657
Comments
atc0005
added
question
|
From the current README:
Some additional context when deciding whether to keep it. |
|
Looking over CI jobs and the mysql2sqlite Makefile, this image is not used. Looking at older repos, I see where I originally used it in another CGO-enabled project. That project however is archived and I'm unlikely to work on it further. In short, I'm not using this image. Instead, I'm using the |
|
Dropped the |
|
I spot-checked the download count for this image via https://github.com/atc0005/go-ci/pkgs/container/go-ci/versions and found that for recent versions:
no downloads are recorded. For older images however, there are some downloads:
there are at least a few downloads of each. Some of the downloads may come from CI jobs for the archived repo/project I mentioned previously. Not sure about the others. Perhaps I'll hold off a little longer retiring this image. Will plan to revisit this in say, six months from now to see what the download counts show. |
|
FWIW, Docker Hub shows 0 downloads for v0.7.6 and newer versions of the image. This includes the |
Link to current GH issue asking for feedback. refs GH-657
Added it back for now. |
|
I stored a WIP PR branch that drops the image for later consideration/use. |
The `go-ci-stable-debian-build` image was poorly named and failed to convey the intended purpose: Provide an image to support cross-platform, static cgo-enabled builds for Windows and Linux. This set of changes reworks the image to drop linting support (which was always an afterthought) and rename it to `go-ci-stable-cgo-mingw-w64-build`. The README has been updated to remove the "Do you use this image?" prompt and provide an overview that better reflects the image's purpose. refs GH-657
The `go-ci-stable-debian-build` image was poorly named and failed to convey the intended purpose: Provide an image to support cross-platform, static cgo-enabled builds for Windows and Linux. This set of changes reworks the image to drop linting support (which was always an afterthought) and rename it to `go-ci-stable-cgo-mingw-w64-build`. The README has been updated to remove the "Do you use this image?" prompt and provide an overview that better reflects the image's purpose. refs GH-657
The `go-ci-stable-debian-build` image was poorly named and failed to convey the intended purpose: Provide an image to support cross-platform, static cgo-enabled builds for Windows and Linux. This set of changes reworks the image to drop linting support (which was always an afterthought) and rename it to `go-ci-stable-cgo-mingw-w64-build`. The README has been updated to remove the "Do you use this image?" prompt and provide an overview that better reflects the image's purpose. NOTE: The previous steps to create a temporary copy of the golangci-lint config file for each stable image being built and then prune the temporary file as part of the dedicated cleanup recipe and post-build cleanup have been removed. The "stable" variant of the linting config file has been moved directly into the stable/combined/ path. refs GH-657
While reviewing this image as part of #656 & #557 I realized that while the image continues to be maintained, I'm not sure that it is ever used.
https://github.com/atc0005/go-ci/pkgs/container/go-ci/23958027?tag=go-ci-stable-debian-build
It may have been used early on by the atc0005/mysql2sqlite project before switching over to Alpine images, but I'll need to dig back to confirm.
The text was updated successfully, but these errors were encountered: