Bogus pipeline failure notices on projects that don't have build pipeline enabled

Just received this email, which is surprising because I don't have auto devops enabled for this project (https://gitlab.com/chriscox/BenchmarkDevelopment ) And the failure appears to be an internal script update error.


GitLab
Auto DevOps pipeline was disabled for BenchmarkDevelopment
The Auto DevOps pipeline failed for pipeline #1 and has been disabled for BenchmarkDevelopment. In order to use the Auto DevOps pipeline with your project, please review the currently supported languages, adjust your project accordingly, and turn on the Auto DevOps pipeline within your CI/CD project settings.
 Learn more about Auto DevOps
Pipeline #33520203 triggered by		Chris Cox
had 1 failed build.
Logs may contain sensitive data. Please consider before forwarding this email.
✖	build	build
5ac34e15ac7b: Pull complete
7ff3cba3e710: Pull complete
8be7609fa05c: Pull complete
28b563a2d870: Pull complete
7d2ba817ef0b: Pull complete
Digest: sha256:d1581d20408be7a7366b6ea74dc5cddc866f4ad4c573a04251272471c0aa2e56
Status: Downloaded newer image for gliderlabs/herokuish:latest
       -----> Unable to select a buildpack
ERROR: Job failed: exit code 1
GitLab
You're receiving this email because of your account on gitlab.com. Manage all notifications · Help
Edited Oct 19, 2018 by Chris Cox
Assignee Loading
Time tracking Loading