geerlingguy / geerlingguy/ansible-for-devops
Get three failing CI test playbooks to work again (after GH Actions Migration)
- Dominant language
- Python
- Stars
- 9.9k
- Forks
- 3.8k
- PR merge metrics
- No merged PRs in 30d
Description
In Issue #359, I migrated from Travis CI to GitHub Actions. Mostly that went okay, but there are three playbooks I've had to temporarily disable, all for what seem to be very minor issues:
| Playbook | Issue |
| --- | --- |
| `deployments-rolling.yml` | `npm test` results in `google.com is unreachable` (should be reachable) |
| `jenkins.yml` | `Install Jenkins plugins` task causes idempotence failure on `ansicolor` install |
| `includes.yml` | `Install Drupal dependencies with Composer` task fails with a cache permissions error. |
I would like to get these three CI playbooks running again, and at least the first two seem like they might be relatively quick fixes. Maybe the third too, but file permissions in CI environments can be... interesting.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with deployments-rolling.yml, jenkins.yml, and includes.yml, reviewing the disabled tasks and their reported CI failures. Run the affected npm test, Jenkins plugin installation, and Drupal Composer dependency steps in GitHub Actions. Done means all three playbooks run successfully and no longer fail their checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, drupal, github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100