You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this should help teams manage breaking changes and also ensure that they can take whatever version required for their specific project to work
Signed-off-by: Sean Simmons <ssimmons@progress.com>
perform-docker-scan: false # scan Dockerfile and built images with Docker Scout or Trivy; see repo custom properties matching "container"
83
88
84
89
# report to central developer dashboard
90
+
# quality-dashboard-version: 'main' # Version of quality dashboard workflow (main, v1.0.7, etc.)
85
91
report-to-atlassian-dashboard: false
86
92
quality-product-name: 'Chef-360'# product name for quality reporting, like Chef360, Courier, Inspec
87
93
# quality-product-name: ${{ github.event.repository.name }} # like 'Chef-360' - the product name for quality reporting, like Chef360, Courier, Inspec
@@ -105,6 +111,7 @@ jobs:
105
111
publish-packages: false # Publish packages (e.g., container from Dockerfile to ECR, go-releaser binary to releases page, omnibus to artifactory, gems, choco, homebrew, other app stores)
106
112
107
113
# generate and export Software Bill of Materials (SBOM) in various formats
114
+
# sbom-version: 'main' # Version of SBOM workflow (main, v1.0.7, etc.)
108
115
generate-sbom: true
109
116
export-github-sbom: true # SPDX JSON artifact on job instance
110
117
perform-blackduck-sca-scan: true # combined with generate sbom & generate github-sbom, also needs version above
When code is merged to `main` in `common-github-actions`, a new patch tag is automatically created via the `create-release-tag.yml` workflow. Manual version bumps can be triggered via workflow dispatch.
104
110
111
+
### Sub-Workflow Versioning (NEW)
112
+
113
+
**Each security scan can be pinned to its own version independently**, giving you fine-grained control over which scan versions to use:
**Recommendation:** Pin to specific versions (e.g., `v1.0.7`) for production repositories. Use `main` for development/testing repositories to get latest features.
C -->|secrets| D[POLARIS_SERVER_URL<br/>POLARIS_ACCESS_TOKEN]
235
293
C -->|inputs| E[polaris-application-name<br/>polaris-project-name<br/>polaris-working-directory<br/>polaris-config-path<br/>polaris-coverity-config-path<br/>polaris-coverity-build-command<br/>polaris-coverity-clean-command<br/>polaris-coverity-args<br/>polaris-detect-search-depth<br/>polaris-detect-args<br/>polaris-assessment-mode<br/>wait-for-scan]
294
+
C -->|version| F[polaris-version: string]
236
295
237
296
style A fill:#ffe1e1
238
297
style B fill:#ffd4d4
239
298
```
240
299
241
-
**Workflow File:** Inline implementation (no separate workflow)
- `polaris-version` (string) - Version of Polaris SAST workflow to use (e.g., 'main', 'v1.0.7'), default: 'main'
242
304
243
305
**Required Secrets:**
244
306
- `POLARIS_SERVER_URL`- BlackDuck Polaris server URL
@@ -429,12 +491,17 @@ graph LR
429
491
430
492
C -->|secrets| D[HAB_PUBLIC_BLDR_PAT]
431
493
C -->|inputs| E[publish-habitat-hab_package<br/>publish-habitat-hab_version<br/>publish-habitat-hab_release<br/>publish-habitat-hab_channel<br/>publish-habitat-hab_auth_token]
494
+
C -->|version| F[grype-version or grype-hab-version]
C -->|secrets| D[BLACKDUCK_SBOM_URL<br/>BLACKDUCK_SCA_TOKEN]
551
618
C -->|inputs| E[version<br/>export-github-sbom<br/>perform-blackduck-sca-scan<br/>blackduck-project-group-name<br/>blackduck-project-name<br/>generate-msft-sbom<br/>license_scout<br/>go-private-modules]
C -->|inputs| D[perform-build<br/>build-profile<br/>language<br/>report-unit-test-coverage<br/>report-to-atlassian-dashboard<br/>quality-product-name<br/>quality-sonar-app-name<br/>quality-testing-type<br/>quality-service-name<br/>quality-junit-report<br/>visibility<br/>go-private-modules<br/>udf1, udf2, udf3]
678
+
C -->|version| E[quality-dashboard-version: string]
0 commit comments