The empty state reported that you didn't have any environments
regardless of scope, which was a bit misleading if you had many
available environments and no stopped environments.

I have refactored the component to allow the scope to be injected so the
text can change depending on what scope the user is looking at.

I've also refactored the rest of the translations to follow more
up-to-date patterns, and rewritten the tests to utilize the testing
library's queries for finding things by role.

Changelog: fixed

This is due to a Rails bug causing where FactoryBot thread, and Puma
thread are stuck with each other waiting for the
load_interlock_aware_monitor lock.

The fix is to ensure no Puma threads ocurr when FactoryBot factories are
being created. Here it is done by moving the visits to within the spec,
after the factory creation.

Previously the visits were in the before hook, which meant async
requests ran concurrently with factories.

Cleans up the feature tests for the environmetns page as well, making
sure they pass with the new table.

Changes are shockingly minimal, which is nice.

Changelog: changed

Changelog: changed

Shinya Maeda authored 3 years ago and Mikołaj Wawrzyniak committed 3 years ago

This commit drops the legacy finished at calculation
of deployments.

Changelog: fixed

Serhii Yarynovskyi authored 3 years ago and Nicolò Mezzopera committed 3 years ago

The delete_branch_confirmation_modals feature flag is removed per:
https://gitlab.com/gitlab-org/gitlab/-/issues/329052 Since it was introduced
to 100% of actors

Changelog: removed

Lukas Eipert authored 3 years ago and Peter Hegman committed 3 years ago

This overwrites `Rails.confirm` from `@rails/ujs` in order to show a
modal instead of a Browser `window.confirm`.

If manual deployments are deployed out of order, the ordering of the
table gets murky and it is hard to tell which deployment was most
recently deployed.

Instead we can update the deployment ordering so that deployments are
ordered by when they finished at, which forces the finished deployments
to be sorted by most recently finished (read: deployed). Postgres ORDER
BY pushes NULL to the top of the list, so created/running (upcoming)
deployments are first

Changelog: changed

As part of the ongoing revitalization of environment management, some
re-organization and clarification of the action buttons for environments
is needed.

Many non-well used actions have been moved to a kebab menu. For the time
being, the "Deploy to" dropdown is still external. Pending design work
from the Pajamas team on a nested dropdown or menu component, it will be
moved to extra actions in the future.

Changelog: changed

Disable all existing selector usages within spec and ee/spec

We are removing one-click applications from GitLab but leaving the
integrations for Prometheus and Elastic Stack.

We have code in place that keeps the integration in sync with the
corresponding cluster application, and have backfilled the
ingtegrations, so we can now use them as a source of truth.

See

- Backfill Prometheus: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/61502
- Backfill Elastic Stack: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/61521
- Deprecation Epic: https://gitlab.com/groups/gitlab-org/-/epics/4280

Replaces the bootstrap modal for the delete branch button and
confirmation.

Changelog: added

Update button variant and alignment in the
Projects::BranchesController#index and update tests to
follow current guides.

Changelog: added

Andrew Fontaine authored 4 years ago and Nicolò Mezzopera committed 4 years ago

This lets users set the canary ingress percentage via the UI when using
deploy boards.

Nathan Friend authored 4 years ago and Enrique Alcántara committed 4 years ago

This commit updates the Environments table with a new column: upcoming
deployment.

To comply with RSpec/TimecopFreeze cop

Also refactor tests and fix grammar in UI text

Ran another find + Replace on the specs

Lukas Eipert authored 4 years ago and Ho Tuan Duong committed 4 years ago

Fix all tests relating to GlIcon

Redirects from environment scoped metrics dashboard to project scoped
metrics dashboard

Custom metrics dashboards currently display the entire
file path in the URL. This MR supports a shorter path
for such dashboards

The plan for RSpec 4.0 is to disable monkey patching:
https://rspec.info/blog/2013/07/the-plan-for-rspec-3/#zero-monkey-patching-mode

This commit stops using RSpec monkey patching in some specs:
https://relishapp.com/rspec/rspec-core/docs/configuration/zero-monkey-patching-mode

This commit adds a feature spec

- Migrate components to new GlTable slot syntax
- Fix feature tests that made obsolete assertions on the
tooltip component
- Migrate components to new GlTabs slot syntax
- Fix bugs caused by the new Tooltip and Popover components
- Fix bugs introduced by the new modal component.

This is the commit for all changes, for merging

This change involves both HAML and Vue, plus refactoring

This prevents users from creating deployments using the API while
providing an invalid SHA or ref name. Providing invalid data for these
fields will break certain parts of GitLab, such as the UI used for
displaying the deployments of an environment.

These changes require that we correct a variety of tests that were using
deployments without a valid repository, or were even testing behaviour
that would never run due to the lack of a repository.

This fixes https://gitlab.com/gitlab-org/gitlab/issues/36967

- Dropped table pagination's custom implementation in favor of GitLab
UI's pagination component
- Added Number.isInteger polyfill for IE11 compatibility
- Updated RSpec, Karma and Jest specs as needed

This commit persists and controls auto stop date for environments

Auto-correct some references in RSpec as:
- expect_any_instance_of -> expect_next_instance_of
- allow_any_instance_of -> allow_next_instance_of

Related to https://gitlab.com/gitlab-org/gitlab/issues/34997

* We also use `needs` to speed it up
* To simplify the dependencies, we also pull cache on master