Skip to content

Improve warning message when security feature is not supported

Our documentation explains the level of subscription necessary to use features:

Screenshot_2019-08-26_16.52.19

Yet, some users still confuse EE with Ultimate, and try to run our security features. As of today, all these security features are only available for Ultimate, and therefore will not run for lower plans. While the job will be skipped automatically, it's generally unclear for the user why. The job will just not run (it will not even be visible in the pipeline), without any explanation.

We should at least generate an error message, to let the user know they're doing something wrong. Some suggestions to improve this situation:

  • Add a "Troubleshooting" or "FAQ" section in our doc
  • Let the job start, but make it fail with an explicit message if GITLAB_FEATURES doesn't contain the right feature AND we're not using auto-devops (to avoid unwanted failures). It's fairly inefficient and will not work anymore once we remove the orchestrator layer in &971 (closed)
  • Maybe add a "Skipped" tab in the pipeline view (not sure it would really help)

It's a chicken and egg problem: We have an issue to help day-1 users, but these pages are only visible for Ultimate users. This issue is about users NOT having an ultimate license, and trying to figure out why the security features are not working.