- Introduced a new step in the CI workflow to trigger a Portainer deployment using a webhook.
- Added checks for the presence of the PORTAINER_WEBHOOK_URL secret and handled HTTP response codes from the webhook call.
- Ensured that the workflow does not fail if the webhook call is unsuccessful.
This enhancement streamlines the deployment process by automating updates to the Portainer stack upon successful CI runs.
Reviewed-on: #12
Co-authored-by: Juan Sebastian Montoya <juansmm@outlook.com>
Co-committed-by: Juan Sebastian Montoya <juansmm@outlook.com>
- Introduced a step to validate PR titles, ensuring they start with the correct prefixes (Release/, Feature/, Hotfix/, Bugfix/).
- Enhanced versioning logic to determine version type based on PR title or merge commit message, allowing for appropriate version increments.
- Improved handling of versioning for different types of changes, including major, minor, and patch updates.
This update aims to enforce consistent PR title formatting and streamline version management in the CI process.
Reviewed-on: #11
Co-authored-by: Juan Sebastian Montoya <juansmm@outlook.com>
Co-committed-by: Juan Sebastian Montoya <juansmm@outlook.com>
- Removed complex remote URL configuration logic for authentication.
- Updated comments to clarify that the remote should already be configured with the token before pushing to the main branch.
Reviewed-on: #10
Co-authored-by: Juan Sebastian Montoya <juansmm@outlook.com>
Co-committed-by: Juan Sebastian Montoya <juansmm@outlook.com>
- Improved handling of the {{COMMITS}} placeholder to support multi-line content.
- Introduced a while loop for safe replacement of multi-line commit messages.
- Added temporary files for intermediate processing to ensure accurate output.
Reviewed-on: #9
Co-authored-by: Juan Sebastian Montoya <juansmm@outlook.com>
Co-committed-by: Juan Sebastian Montoya <juansmm@outlook.com>
# Add CI/CD Pipeline with Docker Build and Publish
## Summary
This PR adds a complete CI/CD pipeline for building and publishing Docker images of the Three.js game to the Forgejo container registry. The workflow automatically builds, validates, and publishes Docker images with semantic versioning when code is merged to main.
## Changes
### 🚀 CI/CD Workflow (`.forgejo/workflows/ci.yaml`)
- **Build & Validation**: Automatically builds Docker image on PRs and validates it works
- **Semantic Versioning**: Auto-increments patch version on each merge to main
- First version: `0.1.0` (when no tags exist)
- Subsequent merges: Auto-increments patch (e.g., `0.1.0` → `0.1.1` → `0.1.2`)
- **Publishing**: Publishes images to `git.jusemon.com/jusemon/threejs-test:<version>` and `latest` tag
- **Git Tagging**: Automatically creates git tags (e.g., `v0.1.0`) for releases
- **Registry Integration**: Uses Forgejo container registry with secrets-based authentication
### 🐳 Docker Setup
- **Dockerfile**: Custom nginx:alpine image with the game HTML file
- **docker-compose.yml**: Simple orchestration for local development
- **nginx.conf**: Minimal nginx configuration with gzip compression
## Workflow Behavior
### On Pull Requests
- ✅ Builds Docker image
- ✅ Validates image by running container and checking HTTP response
- ❌ Does NOT publish (validation only)
### On Merge to Main
- ✅ Builds Docker image
- ✅ Validates image
- ✅ Publishes to registry with version tag
- ✅ Tags as `latest`
- ✅ Creates git tag for the release
## Required Setup
Before merging, ensure these secrets are configured in the repository:
- `REGISTRY_USERNAME`: Forgejo username
- `REGISTRY_PASSWORD`: Personal Access Token with package write permissions
## Versioning Strategy
- **First Release**: `0.1.0` (when no tags exist)
- **Subsequent Releases**: Auto-increments patch version on each merge
- **Image Tags**:
- `git.jusemon.com/jusemon/threejs-test:0.1.0`
- `git.jusemon.com/jusemon/threejs-test:latest` (always points to latest main)
## Testing
The workflow includes validation steps that:
1. Build the Docker image
2. Run a test container
3. Verify the web server responds correctly
4. Only publish if all validations pass
## Benefits
- ✅ Automated builds and deployments
- ✅ Consistent versioning
- ✅ Image validation before publishing
- ✅ Easy rollback using version tags
- ✅ Latest tag for easy deployment
Reviewed-on: #1
Co-authored-by: Juan Sebastian Montoya <juansmm@outlook.com>
Co-committed-by: Juan Sebastian Montoya <juansmm@outlook.com>
