Skip to content

"Buy additional minutes" button visible on self-managed instances

Summary

Self-Hosted/Self-Managed instances of GitLab versions 11.11 and newer have a visible "Buy more minutes" button. This button, when clicked takes the user to a page detailing paid GitLab plans, which only mentions CI minutes at the very bottom and clearly states its only for GitLab.com

Pipeline/runner minutes are a product only relevant to Gitlab.com . GitLab does not sell minutes for self-hosted installations.

Steps to reproduce

On a self-managed GitLab Omnibus instance running 11.11 or newer:

  • set a [Shared Runners pipeline minutes quota] at the group level
  • at the group page, navigate Group > Settings > Usage Quotas

"Buy additional minutes" button will now be visible at:
http(s)://<gitlab-URL>/groups/<group_name>/-/pipeline_quota OR http(s)://<gitlab-URL>/groups/<group_name>/-/usage_quotas#pipelines-quota-tab

buy-more-minutes

What is the current bug behavior?

"Buy additional minutes" button is visible on self-managed installations at:

http(s)://<gitlab-URL>/groups/<group_name>/-/pipeline_quota OR http(s)://<gitlab-URL>/groups/<group_name>/-/usage_quotas#pipelines-quota-tab

What is the expected correct behavior?

"Buy additional minutes" button ONLY visible for GitLab.com users, NEVER visible for self-managed installations

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info 


System information
System:		Ubuntu 16.04
Proxy:		no
Current User:	git
Using RVM:	no
Ruby Version:	2.6.3p62
Gem Version:	2.7.9
Bundler Version:1.17.3
Rake Version:	12.3.2
Redis Version:	3.2.12
Git Version:	2.21.0
Sidekiq Version:5.2.7
Go Version:	unknown

GitLab information
Version:	12.0.3-ee
Revision:	1b1872f9d93
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	PostgreSQL
DB Version:	10.7
URL:		https://example.com
HTTP Clone URL:	https://example.com/some-group/some-project.git
SSH Clone URL:	git@example.com:some-group/some-project.git
Elasticsearch:	no
Geo:		yes
Geo node:	Primary
Using LDAP:	no
Using Omniauth:	yes
Omniauth Providers: 

GitLab Shell
Version:	9.3.0
Repository storage paths:
- default: 	/var/opt/gitlab/git-data/repositories
GitLab Shell path:		/opt/gitlab/embedded/service/gitlab-shell
Git:		/opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 


Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 9.3.0 ? ... OK (9.3.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK

Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ... 
49/1 ... yes
49/2 ... yes
49/3 ... yes
49/4 ... yes
49/5 ... yes
49/6 ... yes
49/7 ... yes
49/8 ... yes
49/9 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.3)
Git version >= 2.21.0 ? ... yes (2.21.0)
Git user has default SSH configuration? ... yes
Active users: ... 52
Elasticsearch version 5.6 - 6.x? ... skipped (elasticsearch is disabled)

Checking GitLab App ... Finished

Checking Geo ...

GitLab Geo is available ... yes
GitLab Geo is enabled ... yes
GitLab Geo secondary database is correctly configured ... not a secondary node
Database replication enabled? ... not a secondary node
Database replication working? ... not a secondary node
GitLab Geo tracking database is configured to use Foreign Data Wrapper? ... not a secondary node
GitLab Geo tracking database Foreign Data Wrapper schema is up-to-date? ... not a secondary node
GitLab Geo HTTP(S) connectivity ... not a secondary node
HTTP/HTTPS repository cloning is enabled ... yes
Machine clock is synchronized ... yes
Git user has default SSH configuration? ... yes

Checking Geo ... Finished


Checking GitLab subtasks ... Finished

Possible fixes

Appears to have been introduced with this commit: https://gitlab.com/gitlab-org/gitlab-ee/commit/aa3951fe7820e333e7cc12472ef13d39292e1276 which was merged into master with https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/12486

Edited by Greg Myers