Gibson

This repository owns the Gibson TN3270 test service. Gibson runs a pinned TK5 MVS 3.8j image for Zelnet functional tests.

The service is stateless. A restart returns it to the image state. The public endpoint is gibson.sean.farm. Cluster tests must use gibson.gibson.svc.cluster.local:3270 because the public load balancer does not support the cluster hairpin path.

manifests/gibson contains the runtime objects. apps/gibson.yaml records the Argo application contract. The live Argo CD application tracks this repository at main. Pipelines released the source handoff and retired its old bundle.

Binjovi owns the Build, Release, and Deploy lifecycle. The deployment target is gibson-development. Its availability gate opens a bounded TCP connection to gibson.gibson.svc.cluster.local:3270 after Argo CD converges.

Run the local contract with:

bash tests/check.sh

Native pipeline timing

Binjovi uses native agents for this project's Build, Release, and Deploy tasks. The configured deployment target is gibson-development. The deployment checks the TN3270 service at gibson.gibson.svc.cluster.local:3270.

Select an exact successful Build when you release:

binjovictl builds gibson
binjovictl release gibson --build BUILD_ID --wait
binjovictl status gibson

Open the project dashboard and expand an execution attempt to inspect its task timeline and available profiles. The latest completed pipeline summary includes Build and Release time as well as deployment time. Check the Deploy result separately after Release completes. Telemetry explains execution; the stored revision and verification evidence establish completion.