Commit ed5dd976 authored by Amy Qualls's avatar Amy Qualls Committed by Evan Read

Restructure troubleshooting section

The troubleshooting section contained a nested bulleted list, and
would be better suited to subheadings instead.
parent f9ccf92b
...@@ -381,11 +381,10 @@ other environments. ...@@ -381,11 +381,10 @@ other environments.
## Currently supported languages ## Currently supported languages
Note that not all buildpacks support Auto Test yet, as it's a relatively new Note that not all buildpacks support Auto Test yet, as it's a relatively new
enhancement. All of Heroku's [officially supported enhancement. All of Heroku's
languages](https://devcenter.heroku.com/articles/heroku-ci#supported-languages) [officially supported languages](https://devcenter.heroku.com/articles/heroku-ci#supported-languages)
support buildpacks, and some third-party buildpacks as well (such as Go, Node, Java, PHP, support Auto Test. The languages supported by Heroku's Herokuish buildpacks all
Python, Ruby, Gradle, Scala, and Elixir) all support Auto Test, but notably the support Auto Test, but notably the multi-buildpack does not.
multi-buildpack does not.
As of GitLab 10.0, the supported buildpacks are: As of GitLab 10.0, the supported buildpacks are:
...@@ -438,28 +437,36 @@ spec: ...@@ -438,28 +437,36 @@ spec:
## Troubleshooting ## Troubleshooting
- Auto Build and Auto Test may fail to detect your language or framework with the ### Unable to select a buildpack
following error:
Auto Build and Auto Test may fail to detect your language or framework with the
```plaintext following error:
Step 5/11 : RUN /bin/herokuish buildpack build
---> Running in eb468cd46085 ```plaintext
-----> Unable to select a buildpack Step 5/11 : RUN /bin/herokuish buildpack build
The command '/bin/sh -c /bin/herokuish buildpack build' returned a non-zero code: 1 ---> Running in eb468cd46085
``` -----> Unable to select a buildpack
The command '/bin/sh -c /bin/herokuish buildpack build' returned a non-zero code: 1
The following are possible reasons: ```
- Your application may be missing the key files the buildpack is looking for. For The following are possible reasons:
example, for Ruby applications you must have a `Gemfile` to be properly detected,
even though it's possible to write a Ruby app without a `Gemfile`. - Your application may be missing the key files the buildpack is looking for.
- There may be no buildpack for your application. Try specifying a Ruby applications require a `Gemfile` to be properly detected,
[custom buildpack](customize.md#custom-buildpacks). even though it's possible to write a Ruby app without a `Gemfile`.
- Auto Test may fail because of a mismatch between testing frameworks. In this - No buildpack may exist for your application. Try specifying a
case, you may need to customize your `.gitlab-ci.yml` with your test commands. [custom buildpack](customize.md#custom-buildpacks).
- Auto Deploy will fail if GitLab can't create a Kubernetes namespace and
service account for your project. For help debugging this issue, see ### Mismatch between testing frameworks
[Troubleshooting failed deployment jobs](../../user/project/clusters/index.md#troubleshooting).
Auto Test may fail because of a mismatch between testing frameworks. In this
case, you may need to customize your `.gitlab-ci.yml` with your test commands.
### Failure to create a Kubernetes namespace
Auto Deploy will fail if GitLab can't create a Kubernetes namespace and
service account for your project. For help debugging this issue, see
[Troubleshooting failed deployment jobs](../../user/project/clusters/index.md#troubleshooting).
## Development guides ## Development guides
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment