Skip to content

ci: disable unused container_description workflow#1940

Open
sibasispadhi wants to merge 1 commit into
prometheus:mainfrom
sibasispadhi:fix/disable-unused-container-workflow
Open

ci: disable unused container_description workflow#1940
sibasispadhi wants to merge 1 commit into
prometheus:mainfrom
sibasispadhi:fix/disable-unused-container-workflow

Conversation

@sibasispadhi

Copy link
Copy Markdown

Fixes #1938

This workflow was added via automated sync (PrometheusBot) in May 2024 but has never worked because client_golang is a library, not a containerized service that publishes container images.

The workflow fails because:

  • DOCKER_IMAGE_NAME is not defined in the Makefile
  • The 'docker-repo-name' Makefile target doesn't exist
  • The only Dockerfile is for building local examples, not distribution

This change disables the workflow (rather than deleting) to:

  • Stop failing CI runs that have occurred since May 2024
  • Document why client_golang doesn't need container image publishing
  • Prevent future automated syncs from re-enabling it
  • Preserve the file for historical context
  • Allow manual trigger if ever needed in the future

The workflow trigger is changed from 'push' to 'workflow_dispatch' (manual only) with detailed comments explaining the situation and jobs that exit with an error if accidentally triggered.

Fixes prometheus#1938

This workflow was added via automated sync (PrometheusBot) in May 2024
but has never worked because client_golang is a library, not a
containerized service that publishes container images.

The workflow fails because:
- DOCKER_IMAGE_NAME is not defined in the Makefile
- The 'docker-repo-name' Makefile target doesn't exist
- The only Dockerfile is for building local examples, not distribution

This change disables the workflow (rather than deleting) to:
- Stop failing CI runs that have occurred since May 2024
- Document why client_golang doesn't need container image publishing
- Prevent future automated syncs from re-enabling it
- Preserve the file for historical context
- Allow manual trigger if ever needed in the future

The workflow trigger is changed from 'push' to 'workflow_dispatch'
(manual only) with detailed comments explaining the situation and
jobs that exit with an error if accidentally triggered.

Signed-off-by: Sibasis Padhi <sibasis.padhi@gmail.com>
@sibasispadhi

Copy link
Copy Markdown
Author

@vesari per my analysis, I thought its best to disable the feature. Kindly take a look on the changes, and let me know what is your thought process on same or any further changes needed.

@kakkoyun

Copy link
Copy Markdown
Member

@vesari could you take a look at it?

@sibasispadhi This needs a rebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

container_description.yml workflow failing

2 participants