wheels ci init
Initialize continuous integration configuration for your Wheels application.
Synopsis
Description
The wheels ci init
command sets up continuous integration (CI) configuration files for your Wheels application. It generates CI/CD pipeline configurations for popular CI providers like GitHub Actions, GitLab CI, Jenkins, and others.
Arguments
provider
CI provider to configure (github, gitlab, jenkins, travis, circle)
github
Options
--template
Use a specific template (basic, full, minimal)
--branch
Default branch name
--engines
CFML engines to test (lucee5, lucee6, adobe2018, adobe2021, adobe2023)
--databases
Databases to test against (h2, mysql, postgresql, sqlserver)
--force
Overwrite existing CI configuration
--help
Show help information
Examples
Initialize GitHub Actions
Initialize with specific engines
Initialize with multiple databases
Initialize GitLab CI
Use full template with force overwrite
What It Does
Creates CI configuration files in the appropriate location:
GitHub Actions:
.github/workflows/ci.yml
GitLab CI:
.gitlab-ci.yml
Jenkins:
Jenkinsfile
Travis CI:
.travis.yml
CircleCI:
.circleci/config.yml
Configures test matrix for:
Multiple CFML engines
Multiple database systems
Different operating systems (if supported)
Sets up common CI tasks:
Dependency installation
Database setup
Test execution
Code coverage reporting
Artifact generation
Generated Configuration
Example GitHub Actions configuration:
Templates
Basic Template
Single engine and database
Essential test execution
Minimal configuration
Full Template
Multiple engines and databases
Code coverage
Deployment steps
Notifications
Minimal Template
Bare minimum for CI
Quick setup
No extras
Use Cases
New Project Setup: Quickly add CI/CD to a new Wheels project
Migration: Move from one CI provider to another
Standardization: Apply consistent CI configuration across projects
Multi-Engine Testing: Ensure compatibility across CFML engines
Notes
Requires a valid Wheels application structure
Some providers may require additional authentication setup
Database services are configured as Docker containers where possible
The command respects existing
.gitignore
patterns
See Also
wheels test - Run tests locally
wheels docker init - Initialize Docker configuration
wheels deploy - Deployment commands
Last updated
Was this helpful?