fix: 🐛 pipeline task fixes validated by run11 success #163
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!163
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/163/head"
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?
Summary
Task bugs found during first real end-to-end pipeline run. Fixed iteratively across runs 3-11 until
release-tools-publish-v101-run11succeeded completely.build-image
.buildah/) sopush-by-digesttask can access it across pod boundaries (each task runs in its own pod with empty local storage)--storage-driverto allbuildahqueries to hit the same storebuildah imageswithout name filter (name-based lookup exits non-zero on unknown reference, killing script underset -e)push-image-by-digest
localhost/prefix when referencing the built image (buildah stores withlocalhost/prefix).buildah/store root to match build-image taskcosign-sign-image-by-digest
curlinstall —curl-minimalis pre-installed in ubi9-minimal; fullcurlconflicts with itdnffallback (ubi9-minimal hasmicrodnfonly)cosign-attach-sbom
tar gzip, notcurl(same curl-minimal conflict)dnffallbackVerified
release-tools-publish-v101-run11succeeded:fetch → resolve → build → push → cosign-sign → attach-sbom → promote-tag✓codeberg.org/operate-first/release-tools:v1.0.1is published and signed.Closes forgejo-mcp-aps
op1st Pipelines as Code/on-pull-request-hv6x9 is running.
Starting Pipelinerun on-pull-request-hv6x9 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-hv6x9 -fop1st Pipelines as Code/code-scans- has failed.
There was an error creating the PipelineRun: code-scans-
cannot use the API on the provider platform to create a in_progress status:
op1st Pipelines as Code/on-pull-request-hv6x9
Task Statuses:
fetch-source
build-and-test
Failure snippet:
task build-and-test has the status "TaskRunCancelled":