Fix Failing CI Pipeline #5
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The deprecated actions/checkout@v2 was causing CI failures. Updated to v4 which is the current stable version and resolves compatibility issues with modern GitHub Actions runners.
Several draft files were missing the required YAML frontmatter, causing Jekyll to fail with exit code 5. Added proper frontmatter to: - !dogfight-milestone.md - !gunner-assist.md - !physics-engine.md - !pilot-assists.md All draft files now have the required layout, title, subtitle, and tags fields.
Added --verbose and --trace flags to see the actual build error in CI logs.
Replaced the Docker-based Jekyll build with the standard ruby/setup-ruby action. This provides: - Better error messages in CI logs - Faster builds with bundler caching - More reliable dependency management - Standard Jekyll CI approach recommended by GitHub
The old Ruby 2.7 image was incompatible with the latest bundler which requires Ruby >= 3.2.0. Updated to Ruby 3.1 to match the CI configuration and resolve the devcontainer build failure. This fixes the error: "bundler requires Ruby version >= 3.2.0. The current ruby version is 2.7.8.225."
The post-create script wasn't executable, preventing automatic gem installation on codespace creation. Changes: - Made script executable (chmod +x) - Switched from sh to bash with set -e for better error handling - Added verbose logging to show installation progress - This ensures gems are installed automatically when the codespace is created Fixes the "bundler: command not found: jekyll" error in codespace tasks.
The vscode user doesn't have write permissions to the RVM system gem directory. Configured bundler to install gems locally to vendor/bundle instead. Changes: - Updated post-create.sh to configure bundler with local path - Created .bundle/config to persist the setting - Added vendor/bundle to .gitignore - Added vendor/ to Jekyll's exclude list in _config.yml This fixes the "Bundler::PermissionError" when trying to install gems in codespaces.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The deprecated actions/checkout@v2 was causing CI failures. Updated to v4 which is the current stable version and resolves compatibility issues with modern GitHub Actions runners.
Please note that if you are trying to update your website, this is the wrong place to do so. Please carefully follow the Beautiful Jekyll instructions (found at https://github.com/daattali/beautiful-jekyll#readme) and make sure you submit changes to your version of the project.
If your intention is to submit a Pull Request, please describe what your pull request achieves.
Thank you!