baktainer/.forgejo/workflows/ci.yml

118 lines
3 KiB
YAML
Raw Normal View History

Add Forgejo Actions workflows for CI/CD ## Forgejo Actions Setup ### Directory Structure - `.forgejo/workflows/` - Forgejo Actions workflows directory - `ci.yml` - Main CI pipeline (test + build + notify) - `test.yml` - Test-only workflow for development - `build.yml` - Build-only workflow for releases - `docker.yml` - Advanced Docker workflow with caching - `README.md` - Comprehensive documentation ### Key Features #### 1. Main CI Pipeline (ci.yml) - Runs RSpec tests in Ruby 3.3 Alpine container - Builds and pushes Docker images to Docker Hub - Supports version tagging and latest tags - Provides pipeline status notifications #### 2. Test Workflow (test.yml) - Dedicated testing workflow for PRs - Runs unit and integration tests separately - Generates coverage reports - Uploads test artifacts #### 3. Build Workflow (build.yml) - Standalone Docker build workflow - Triggers on main branch and version tags - Includes build status notifications #### 4. Advanced Docker Workflow (docker.yml) - Uses Docker Buildx for advanced builds - Implements Docker layer caching - Automatic metadata extraction and tagging ### Forgejo vs GitHub Actions Differences #### Technical Adaptations - **Directory**: `.forgejo/workflows/` vs `.github/workflows/` - **Runners**: `runs-on: docker` with container specification - **Dependencies**: Explicit Alpine package installation - **Caching**: Adapted for Forgejo environment - **Execution**: Optimized for Docker container runtime #### Compatibility - Uses same action references (`actions/checkout@v4`, etc.) - Same secret management (`${{ secrets.* }}`) - Same environment variables (`${{ github.* }}`) - Maintains workflow syntax compatibility ### Required Configuration - Enable Repository Actions in Forgejo settings - Configure Docker Hub secrets (DOCKER_USERNAME, DOCKER_PASSWORD, DOCKER_IMAGE_NAME) - Ensure Forgejo Runner is installed and configured - Set up action repository sources ### Benefits - **Dual CI/CD**: Can run alongside GitHub Actions - **Self-hosted**: Full control over CI/CD infrastructure - **Docker-native**: Optimized for containerized workflows - **Feature parity**: Maintains same functionality as GitHub Actions This enables Baktainer to run on Forgejo instances with full CI/CD capabilities while maintaining compatibility with existing GitHub Actions. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-07-15 11:02:58 -04:00
name: CI Pipeline
on:
push:
branches:
- main
tags:
- 'v*.*.*'
pull_request:
branches:
- main
jobs:
test:
runs-on: docker
container:
image: ruby:3.3-alpine
defaults:
run:
working-directory: ./app
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Install system dependencies
run: |
Fix Node.js executable error in Forgejo Actions ## Problem Forgejo Actions failed with error: ``` OCI runtime exec failed: exec failed: unable to start container process: exec: "node": executable file not found in $PATH: unknown ``` ## Root Cause GitHub Actions like checkout@v4, cache@v4, and upload-artifact@v4 require Node.js runtime, but Ruby Alpine containers don't include Node.js by default. ## Solutions Implemented ### 1. Updated Existing Workflows - **ci.yml**: Added Node.js installation (`apk add nodejs npm`) - **test.yml**: Added Node.js installation for GitHub Actions compatibility ### 2. New Alternative Workflows - **node-ruby.yml**: Uses Node.js 18 Alpine base with Ruby installed - **simple.yml**: Shell-based workflow avoiding Node.js actions - **minimal.yml**: Minimal test-only workflow with basic shell commands ### 3. Updated Documentation - Added troubleshooting section for Node.js issues - Documented all workflow options with their trade-offs - Provided clear solutions for different use cases ## Workflow Options ### For Full GitHub Actions Support - Use `node-ruby.yml` (Node.js base + Ruby) - Use `ci.yml` or `test.yml` (Ruby base + Node.js installed) ### For Minimal Dependencies - Use `simple.yml` (shell-based, manual git/docker) - Use `minimal.yml` (basic test execution only) ### For Production - Use `node-ruby.yml` for maximum compatibility - Use `simple.yml` for minimal resource usage ## Benefits - **Multiple Options**: Choose workflow based on needs - **Backward Compatibility**: Existing workflows still work - **Minimal Alternatives**: Avoid Node.js dependency if not needed - **Clear Documentation**: Troubleshooting guide for common issues This provides flexibility to use Forgejo Actions with or without Node.js dependencies based on specific requirements. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-07-15 11:18:12 -04:00
apk add --no-cache build-base libffi-dev linux-headers postgresql-dev git curl tzdata nodejs npm
Add Forgejo Actions workflows for CI/CD ## Forgejo Actions Setup ### Directory Structure - `.forgejo/workflows/` - Forgejo Actions workflows directory - `ci.yml` - Main CI pipeline (test + build + notify) - `test.yml` - Test-only workflow for development - `build.yml` - Build-only workflow for releases - `docker.yml` - Advanced Docker workflow with caching - `README.md` - Comprehensive documentation ### Key Features #### 1. Main CI Pipeline (ci.yml) - Runs RSpec tests in Ruby 3.3 Alpine container - Builds and pushes Docker images to Docker Hub - Supports version tagging and latest tags - Provides pipeline status notifications #### 2. Test Workflow (test.yml) - Dedicated testing workflow for PRs - Runs unit and integration tests separately - Generates coverage reports - Uploads test artifacts #### 3. Build Workflow (build.yml) - Standalone Docker build workflow - Triggers on main branch and version tags - Includes build status notifications #### 4. Advanced Docker Workflow (docker.yml) - Uses Docker Buildx for advanced builds - Implements Docker layer caching - Automatic metadata extraction and tagging ### Forgejo vs GitHub Actions Differences #### Technical Adaptations - **Directory**: `.forgejo/workflows/` vs `.github/workflows/` - **Runners**: `runs-on: docker` with container specification - **Dependencies**: Explicit Alpine package installation - **Caching**: Adapted for Forgejo environment - **Execution**: Optimized for Docker container runtime #### Compatibility - Uses same action references (`actions/checkout@v4`, etc.) - Same secret management (`${{ secrets.* }}`) - Same environment variables (`${{ github.* }}`) - Maintains workflow syntax compatibility ### Required Configuration - Enable Repository Actions in Forgejo settings - Configure Docker Hub secrets (DOCKER_USERNAME, DOCKER_PASSWORD, DOCKER_IMAGE_NAME) - Ensure Forgejo Runner is installed and configured - Set up action repository sources ### Benefits - **Dual CI/CD**: Can run alongside GitHub Actions - **Self-hosted**: Full control over CI/CD infrastructure - **Docker-native**: Optimized for containerized workflows - **Feature parity**: Maintains same functionality as GitHub Actions This enables Baktainer to run on Forgejo instances with full CI/CD capabilities while maintaining compatibility with existing GitHub Actions. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-07-15 11:02:58 -04:00
- name: Install bundler
run: gem install bundler -v 2.6.7
- name: Cache Ruby gems
uses: actions/cache@v4
with:
path: app/vendor/bundle
key: ${{ runner.os }}-gems-${{ hashFiles('app/Gemfile.lock') }}
restore-keys: |
${{ runner.os }}-gems-
- name: Install Ruby dependencies
run: |
bundle config path vendor/bundle
bundle install --jobs 4 --retry 3
- name: Run RSpec tests
run: |
mkdir -p tmp
bundle exec rspec \
--format progress \
--format RspecJunitFormatter \
--out tmp/rspec_results.xml
- name: Upload test results
uses: actions/upload-artifact@v4
if: always()
with:
name: rspec-results
path: app/tmp/rspec_results.xml
build:
needs: test
runs-on: docker
if: github.event_name == 'push' && (github.ref == 'refs/heads/main' || startsWith(github.ref, 'refs/tags/'))
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Log in to Docker Hub
uses: docker/login-action@v3
with:
username: ${{ secrets.DOCKER_USERNAME }}
password: ${{ secrets.DOCKER_PASSWORD }}
- name: Extract version tag
id: version
run: |
if [[ "${GITHUB_REF}" == refs/tags/v* ]]; then
echo "VERSION_TAG=${GITHUB_REF#refs/tags/}" >> $GITHUB_OUTPUT
fi
- name: Set image tags
id: tags
run: |
IMAGE_NAME=${{ secrets.DOCKER_IMAGE_NAME }}
TAGS="${IMAGE_NAME}:latest"
if [ -n "${{ steps.version.outputs.VERSION_TAG }}" ]; then
TAGS="$TAGS,${IMAGE_NAME}:${{ steps.version.outputs.VERSION_TAG }}"
fi
echo "tags=$TAGS" >> $GITHUB_OUTPUT
- name: Build and push Docker image
uses: docker/build-push-action@v5
with:
context: .
push: true
tags: ${{ steps.tags.outputs.tags }}
notify:
needs: [test, build]
runs-on: docker
if: always()
steps:
- name: Notify pipeline status
run: |
echo "📊 Pipeline Status Report:"
echo "🧪 Tests: ${{ needs.test.result }}"
if [ "${{ needs.build.result }}" != "skipped" ]; then
echo "🐳 Build: ${{ needs.build.result }}"
fi
if [ "${{ needs.test.result }}" == "success" ]; then
echo "✅ All tests passed!"
else
echo "❌ Tests failed"
fi