Build Automation - RFC #11

Overview

Implement automated build, packaging, and publishing capabilities for OIE to streamline development workflows and improve distribution.

Requirements

Priority 1: Core Build Automation

• Configure GitHub Actions to execute the current Ant-based build system
• Handle code signing
• Support seamless transition to a future build system (implementation details TBD)
• Create installable packages for all supported platforms (Windows, macOS, Linux)
• Implement automated verification testing as part of the build pipeline - not full application, unit or integration testing

Priority 2: Artifact Publishing

• Publish library artifacts to GitHub Packages
  • Configure for future replication to additional repositories as needed
  • Include proper versioning and dependency management
  • Ensure appropriate documentation is generated and published

Priority 3: Container Support

• Create and publish Docker images to GitHub Container Registry
  • Design for future replication to additional container registries as needed
  • Include multiple tags for version tracking (latest, specific versions)
  • Optimize container size and security

Priority 3: Automated Testing & Releases (nice to have)

• Run automated tests as part of build process
• Automate the release process including Release, Release Notes

Success Criteria

• Fully automated builds triggered by pull requests and daily builds
• Installable packages generated for each supported platform
• Libraries and Docker images published to GitHub and accessible by users
• Complete documentation for accessing and using published artifacts

Supported Platforms

• Windows
  • 64-bit Installer (exe/msi)
  • 64-bit Zip
• Linux
  • Tar.gz
  • RPM
  • Installer (sh)
• macOS
  • Installer (dmg)
  • Tar.gz