Skip to content

fix: preserve long test and scanning name compatibility for 4.3.0#4707

Open
huanghongbo-hhb wants to merge 2 commits into
koderover:release-4.3.0from
huanghongbo-hhb:fix/test-scanning-long-name-compat-4.3.0-v1
Open

fix: preserve long test and scanning name compatibility for 4.3.0#4707
huanghongbo-hhb wants to merge 2 commits into
koderover:release-4.3.0from
huanghongbo-hhb:fix/test-scanning-long-name-compat-4.3.0-v1

Conversation

@huanghongbo-hhb
Copy link
Copy Markdown
Contributor

@huanghongbo-hhb huanghongbo-hhb commented May 21, 2026

Summary

  • Backport the long test and scanning name compatibility fix to release-4.3.0.
  • Preserve compatibility for existing long test and scanning names by normalizing generated workflow job names to lowercase and truncating them to 32 characters.

Why

  • Some historical test and scanning configurations already use names longer than 32 characters.
  • release-4.3.0 needs the same compatibility fix so existing data can still be saved and executed.

Main Changes

  • Add a shared workflow job name normalization helper for test and scanning modules.
  • Normalize generated job names to lowercase and trim them to the workflow job-name limit before validation.
  • Keep test and scanning behavior consistent for create, update, and execution paths.

Risk / Compatibility

  • Low risk: the change is scoped to generated workflow job names for test and scanning modules.
  • This is a compatibility fix for historical long names; stored module names are unchanged.

Test

  • GOCACHE=/private/tmp/zadig-go-build-cache go test -vet=off ./pkg/microservice/aslan/core/common/util
  • GOCACHE=/private/tmp/zadig-go-build-cache go test -vet=off ./pkg/microservice/aslan/core/workflow/testing/service

Contact


This change is Reviewable

Signed-off-by: huanghongbo-hhb <huanghongbo@koderover.com>
Signed-off-by: huanghongbo-hhb <huanghongbo@koderover.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants