Find out why your CI job fails
Give Gryphon the failed job log, pipeline configuration and project files. It can compare the error with your Dockerfile, YAML or shell script and suggest a change.
Example: dependency installation fails in CI
You have the error log, pipeline YAML, package.json, lockfile and Dockerfile.
- Find the failed command and compare runtime and package manager versions.
- Check the image, working directory and files included in the build.
- Prepare a patch, run checks and inspect the next CI run.
What you get
A configuration patch and a cause supported by a log or test. If the cause is still unknown, a list of remaining hypotheses.
Start with the failed command
Check the image version, runtime, package manager, working directory and lockfile. The cause often appears when the log is read alongside the configuration.
Provide the relevant files
Desktop can use local files and commands. Work with GitHub Actions, GitLab CI, Dockerfile or Terraform. Remove tokens and passwords from logs before sharing them.
Check the patch
Review the diff and run linters, tests or configuration validation. If a new CI run is needed, check that result too. You control infrastructure access and permitted actions.
Try it on your own task
Open Web and describe the task. Connect Desktop for files and commands on your computer.