neuron-technologies/el
2
0
Fork 0
Code Issues 1 Pull Requests 6 Actions Packages Projects Releases 5 Wiki Activity

ci(stage,main): decouple ci-base rebuild, make SDK publish fail loudly #75

Merged
will.anderson merged 1 commits from hotfix/ci-stage-main-publish-hardening into dev 2026-07-15 21:15:37 +00:00
Conversation 0 Commits 1 Files Changed 2
+30
will.anderson commented 2026-07-15 21:15:04 +00:00
Owner
Copy Link
Copy Source

Mirrors the PR #72 fix onto ci-stage.yaml and sdk-release.yaml so the stage and prod release jobs go GREEN when the SDK publish succeeds, instead of red-but-published.

The ci-base Docker rebuild (a CI-cache optimization on the fragile host-mode GCE runner) was reddening the whole job even though el-runtime-c/-h published fine. This adds:

  • Rebuild ci-base step: continue-on-error: true (never blocks/reddens the job).
  • Publish step: set -euo pipefail + empty-key guard + active-account echo (a real publish failure still fails loud).

Flowing hotfix -> dev -> stage -> main via GitFlow. Judge each hop by whether the workflow-file change lands, NOT by the ci-base red (that is the very thing being fixed).

Mirrors the PR #72 fix onto ci-stage.yaml and sdk-release.yaml so the stage and prod release jobs go GREEN when the SDK publish succeeds, instead of red-but-published. The ci-base Docker rebuild (a CI-cache optimization on the fragile host-mode GCE runner) was reddening the whole job even though el-runtime-c/-h published fine. This adds: - Rebuild ci-base step: continue-on-error: true (never blocks/reddens the job). - Publish step: set -euo pipefail + empty-key guard + active-account echo (a real publish failure still fails loud). Flowing hotfix -> dev -> stage -> main via GitFlow. Judge each hop by whether the workflow-file change lands, NOT by the ci-base red (that is the very thing being fixed).
will.anderson added 1 commit 2026-07-15 21:15:09 +00:00
ci(stage,main): decouple ci-base rebuild, make SDK publish fail loudly
El SDK CI - dev / build-and-test (pull_request) Failing after 14m30s
Details
dd7827059a 
Mirror the PR #72 fix (applied to ci-dev.yaml) onto ci-stage.yaml and
sdk-release.yaml. The stage and prod release jobs reported FAILURE even
when the el-runtime-c/-h publish SUCCEEDED, because the ancillary ci-base
Docker rebuild (a CI-cache optimization on the fragile host-mode GCE
runner) reddened the whole job.

- Rebuild ci-base step: continue-on-error: true — never blocks/reddens
  the job; the SDK publish is the deliverable.
- Publish step: set -euo pipefail + empty-key guard + active-account echo
  so a real publish failure still fails loud and is diagnosable.
will.anderson merged commit bcb356fe69 into dev 2026-07-15 21:15:36 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
tim.lingo (Tim Lingo) will.anderson (Will Anderson)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: neuron-technologies/el#75
Delete Branch "hotfix/ci-stage-main-publish-hardening"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?