Skip to content

Conversion of CI tooling from BrightCodeCompany repo - #13

Draft
tonygermano wants to merge 3 commits into
tony/templated-dockerfilesfrom
tony/ci-tooling
Draft

tonygermano wants to merge 3 commits into
tony/templated-dockerfilesfrom
tony/ci-tooling

Conversation

@tonygermano

Copy link
Copy Markdown
Member

No description provided.

kpalang and others added 3 commits October 6, 2026 16:02
When README.md changes on main, or when the workflow is run by hand, publish
it as the Docker Hub repository description.

Adapted from BrightCodeCompany/engine-docker@450d8c0 (MPL-2.0).
Source commits: e6792bc b9b9f8a 163232b
Modifications from the BCC version:
- .github/workflows/update-dockerhub-description.yaml: repository is
  openintegrationengine/engine (BCC: brightcodecompany/openintegrationengine).

Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
Co-authored-by: Tony Germano <tony@germano.name>
Signed-off-by: Tony Germano <tony@germano.name>
Add a manually run workflow that scans a published image tag (linux/amd64)
with Docker Scout for critical and high CVEs, turns the SARIF output into
a Markdown report, and opens a GitHub issue with it. reports/local.sh does
the same scan locally.

Adapted from BrightCodeCompany/engine-docker@450d8c0 (MPL-2.0).
Source commits: 9c630f0 9e7cf91 e386fa2 351795d 599325f 1fc0440
Modifications from the BCC version:
- .github/workflows/generate-vulnerability-report.yaml: image repository is
  openintegrationengine/engine (BCC: brightcodecompany/openintegrationengine).
- reports/local.sh: imageRepo is openintegrationengine/engine (BCC:
  brightcodecompany/openintegrationengine). imageTag defaults to latest
  (BCC: 4.6.0-rc1-alpine-jre).
- reports/render-report.ts: the image reference in the report uses
  openintegrationengine/engine (BCC: brightcodecompany/openintegrationengine).
- .gitignore: ignore the generated reports/sarif.json and reports/report.md
  (not in BCC).

Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
Co-authored-by: Tony Germano <tony@germano.name>
Signed-off-by: Tony Germano <tony@germano.name>
On pull requests that touch the templates, releases.yaml, the render script
or dockerfiles/, check releases.yaml for duplicate version slugs, install a
checksum-verified copy of gomplate, re-render the templates, and fail if the
result differs from the committed dockerfiles/.

Adapted from BrightCodeCompany/engine-docker@450d8c0 (MPL-2.0).
Source commits: 5a68694 fcd9f13
Modifications from the BCC version:
- .github/workflows/render-docker-templates.yaml:
  - Merged the three jobs into one. In BCC, gomplate was installed in a
    separate job, so it was never on PATH in the render job.
  - The duplicate-slug check reads releases.yaml from the repository root
    (BCC: from the deleted deploy/ directory) and fails the job when
    duplicates are found (BCC: printed them only).
  - After rendering, the job fails if dockerfiles/ differs from the
    committed files (BCC: threw away the rendered output).
  - Added a pull_request trigger with path filters (BCC: workflow_dispatch
    only).
  - Removed the cache restore-keys fallback, so a cached binary is only used
    if it matches the pinned version and checksum. Removed the example
    "Show gomplate version" step and its numbered comments.

Signed-off-by: Kaur Palang <kaur.palang@brightcodecompany.com>
Co-authored-by: Tony Germano <tony@germano.name>
Signed-off-by: Tony Germano <tony@germano.name>
@tonygermano
tonygermano added this pull request to stack #14 October 15, 2026 14:13
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.

2 participants