-
Notifications
You must be signed in to change notification settings - Fork 0
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
Review repo structure, audit images #847
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
Makefile
oldstable
stable
stable-build-only
stable-lint-only
unstable
Milestone
Comments
atc0005
added
documentation
Improvements or additions to documentation
enhancement
New feature or request
oldstable
unstable
stable
Makefile
stable-lint-only
stable-build-only
labels
Feb 10, 2023
atc0005
added a commit
to atc0005/check-cert
that referenced
this issue
Feb 15, 2023
Remove `push-validation.yml` workflow file. This in turn removes the dependency on the imported (upstream) `quick-validation.yml` workflow file. Linting functionality previously relied upon is already supplied by separate CI matrix managed workflow jobs. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/bridge
that referenced
this issue
Feb 16, 2023
Remove `push-validation.yml` workflow file. This in turn removes the dependency on the imported (upstream) `quick-validation.yml` workflow file. Linting functionality previously relied upon is already supplied by separate CI matrix managed workflow jobs. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/brick
that referenced
this issue
Feb 16, 2023
Remove `push-validation.yml` workflow file. This in turn removes the dependency on the imported (upstream) `quick-validation.yml` workflow file. Linting functionality previously relied upon is already supplied by separate CI matrix managed workflow jobs. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/bounce
that referenced
this issue
Feb 16, 2023
Remove `push-validation.yml` workflow file. This in turn removes the dependency on the imported (upstream) `quick-validation.yml` workflow file. Linting functionality previously relied upon is already supplied by separate CI matrix managed workflow jobs. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/check-illiad
that referenced
this issue
Feb 16, 2023
Remove `push-validation.yml` workflow file. This in turn removes the dependency on the imported (upstream) `quick-validation.yml` workflow file. Linting functionality previously relied upon is already supplied by separate CI matrix managed workflow jobs. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/check-mail
that referenced
this issue
Feb 16, 2023
Remove `push-validation.yml` workflow file. This in turn removes the dependency on the imported (upstream) `quick-validation.yml` workflow file. Linting functionality previously relied upon is already supplied by separate CI matrix managed workflow jobs. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/check-ntpt
that referenced
this issue
Feb 16, 2023
Remove `push-validation.yml` workflow file. This in turn removes the dependency on the imported (upstream) `quick-validation.yml` workflow file. Linting functionality previously relied upon is already supplied by separate CI matrix managed workflow jobs. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/check-path
that referenced
this issue
Feb 16, 2023
Remove `push-validation.yml` workflow file. This in turn removes the dependency on the imported (upstream) `quick-validation.yml` workflow file. Linting functionality previously relied upon is already supplied by separate CI matrix managed workflow jobs. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/check-process
that referenced
this issue
Feb 16, 2023
Remove `push-validation.yml` workflow file. This in turn removes the dependency on the imported (upstream) `quick-validation.yml` workflow file. Linting functionality previously relied upon is already supplied by separate CI matrix managed workflow jobs. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/check-restart
that referenced
this issue
Feb 16, 2023
Remove `push-validation.yml` workflow file. This in turn removes the dependency on the imported (upstream) `quick-validation.yml` workflow file. Linting functionality previously relied upon is already supplied by separate CI matrix managed workflow jobs. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/check-statuspage
that referenced
this issue
Feb 16, 2023
Remove `push-validation.yml` workflow file. This in turn removes the dependency on the imported (upstream) `quick-validation.yml` workflow file. Linting functionality previously relied upon is already supplied by separate CI matrix managed workflow jobs. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
This was referenced Feb 24, 2023
atc0005
added a commit
to atc0005/dnsc
that referenced
this issue
Feb 24, 2023
This workflow was removed recently, but the "status badge" was unintentionally left behind in the README file. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/elbow
that referenced
this issue
Feb 24, 2023
This workflow was removed recently, but the "status badge" was unintentionally left behind in the README file. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/go-lockss
that referenced
this issue
Feb 24, 2023
This workflow was removed recently, but the "status badge" was unintentionally left behind in the README file. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
This was referenced Feb 24, 2023
atc0005
added a commit
to atc0005/go-ezproxy
that referenced
this issue
Feb 24, 2023
This workflow was removed recently, but the "status badge" was unintentionally left behind in the README file. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/go-nagios
that referenced
this issue
Feb 24, 2023
This workflow was removed recently, but the "status badge" was unintentionally left behind in the README file. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/go-teams-notify
that referenced
this issue
Feb 24, 2023
This workflow was removed recently, but the "status badge" was unintentionally left behind in the README file. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/nagios-debug
that referenced
this issue
Feb 24, 2023
This workflow was removed recently, but the "status badge" was unintentionally left behind in the README file. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
This was referenced Feb 24, 2023
atc0005
added a commit
to atc0005/send2teams
that referenced
this issue
Feb 24, 2023
This workflow was removed recently, but the "status badge" was unintentionally left behind in the README file. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/tsm-pass
that referenced
this issue
Feb 24, 2023
This workflow was removed recently, but the "status badge" was unintentionally left behind in the README file. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/safelinks
that referenced
this issue
Feb 24, 2023
This workflow was removed recently, but the "status badge" was unintentionally left behind in the README file. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/query-meta
that referenced
this issue
Feb 24, 2023
This workflow was removed recently, but the "status badge" was unintentionally left behind in the README file. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
atc0005
added a commit
to atc0005/mysql2sqlite
that referenced
this issue
Feb 24, 2023
This workflow was removed recently, but the "status badge" was unintentionally left behind in the README file. refs atc0005/shared-project-resources#63 refs atc0005/go-ci#847
This was referenced Feb 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
Makefile
oldstable
stable
stable-build-only
stable-lint-only
unstable
Overview / Background
I found myself once again looking up how I was using the
combined
stable image in CI workflows. The README reminds me:The
LABEL
values attached via the Dockerfile indicate that the image title isgo-ci-stable
. I then look at the shared CI workflows and see that thego-ci-stable
,go-ci-oldstable
andgo-ci-unstable
images are all used for:go build -v -mod=vendor ./...
to validate that code will build on recent Go releasesThe intent is to provide a common image that can be used for all of these purposes.
In another workflow I've been using an image named
go-ci-lint-only
for "quick" lint & test code CI tasks. This was intended to run and finish by the time I finished filling out a PR as a fail-fast indicator. Because the associated workflows were marked as required by each dependent project's branch protection, this halted the PR process and I believe further CI jobs from running.Current images / sizes
From
v0.7.10
build summary output:Drop images?
As I finish building images for the v0.7.10 release I see that the difference between the
go-ci-stable
andgo-ci-lint-only
images is about 30 MB. Honestly, this doesn't seem worth having two separate images.Ultimately the difference comes down to the
go-ci-stable
having additional linters:Both contain (base):
We also have the
go-ci-stable-debian-build
image (see #657) that bundles all linters (additional & base) along with Mingw-w64 packages. This image is intended to support CGO-enabled builds, but I'm not currently using it in any of my projects and Dockerhub shows 0 downloads, so it's also under review to be dropped.An alternative is to rework the workflows in my projects (currently just one) to use this image instead of installing the
gcc-multilib
andgcc-mingw-w64
packages as a CI workflow task. This will give the image a purpose, but possibly making up a need where there really isn't one?Rename images
On the topic of not well defined names, the
go-ci-stable-debian-build
image provides a Mingw-w64 cross-compile environment to build CGO-enabled Windows binaries using the stable/current version Go (Go 1.20 as I write this).This should be renamed to reflect its purpose.
New images
Up until this point all images were intended to be used in CI for validation (linting, testing, build) purposes. To make tracking build dependencies easier (e.g.,
nfpm
for packages,tc-hib/go-winres
for Windows binary metadata), I'm considering creating a new image intended solely for generating release assets.I'm doing this to some degree now with the
alpine-buildx64
andalpine-buildx86
images for CGO-enabled builds.As noted previously, separate "linting only" and "combined" images were maintained with the intention that one would be super slim and for pre-PR CI tasks while the other would be more comprehensive and used for all validation tasks. The size difference between the two is negligible.
Current layout
Potential layout
I was working up a layout that I planned to use as a replacement, but the more I worked with the mock-up the more I questioned the purpose of some existing images.
Going to need to give this further thought.
In the meantime I'll keep updating existing images and keep things as-is until next steps are a bit clearer.
The text was updated successfully, but these errors were encountered: