build_push_fp.yaml workflow

Docker Build and Push Workflow

Builds and pushes forcingprocessor and forcingprocessor-deps Docker images to Docker Hub with multi-architecture support (x86 and ARM64).

How to Trigger a Build

Option 1: Update versions.yml (Recommended)

Update the version in versions.yml and merge to main:

forcingprocessor: "2.0.0"        # Change this to trigger fp build
forcingprocessor-deps: "latest"  # Change this to trigger deps build

Option 2: Manual Trigger

1. Go to Actions → Build and Push FP → Run workflow
2. Enter version tag in force_build_fp or force_build_deps
3. Click Run workflow

The manual trigger provides a safety net for scenarios like GitHub Actions outages or infrastructure failures, allowing re-pushes without another PR.

Docker Hub Images

Images are pushed to awiciroh:

Image	Description
awiciroh/forcingprocessor	Main forcing processor image
awiciroh/forcingprocessor-deps	Dependencies base image

Each image gets tagged with:

• <version> and latest for x86
• <version>-arm64 and latest-arm64 for ARM

Troubleshooting

Check Build Logs

X86 build: View logs directly in the GitHub Actions workflow run.

ARM build: Logs are uploaded to S3:

aws s3 cp s3://ciroh-community-ngen-datastream/forcingprocessor/test/docker_build_log.txt .
aws s3 cp s3://ciroh-community-ngen-datastream/forcingprocessor/test/docker_push_log.txt .

Common Issues

Issue	Solution
Build not triggered after PR merge	Use manual trigger with the version tag
ARM build timeout	Check Step Function logs in workflow artifacts
Push failed	Verify Docker Hub credentials in AWS Secrets Manager