Skip to content
Snippets Groups Projects
Select Git revision
  • marioceli-master-patch-34687
  • mshaw1-master-patch-68287
  • andr3-master-patch-06736
  • 363356-positive-intent-first
  • russell/improve-app-security-tools-introduction
  • 361217-delete-streaming-header
  • 361641-comments-discussion-header
  • morefice/add-drop-sequence-helper
  • remove-modal-ok-and-modal-cancel-slots-usage
  • sy-do-not-set-unsupported-sort-order-from-user-preference
  • master default protected
  • pedropombeiro/363308/add-html-field
  • qa-shl-group-inheritance-auth-spec
  • nd/bulk-update-member-await-active-state
  • fix-multiple-stop-actions-n-plus-1-queries
  • 358987-cleanup-feature-flag
  • release-tools/update-gitaly
  • migrate-retry-migration-button
  • id-jwt-gitlab-shell
  • 334810-add-placeholder-assignees-query
  • v15.0.0-ee
  • v14.10.3-ee
  • v15.0.0-rc44-ee
  • v15.0.0-rc43-ee
  • v15.0.0-rc42-ee
  • v14.10.2-ee
  • v14.8.6-ee
  • v14.9.4-ee
  • v14.10.1-ee
  • v14.10.0-ee
  • v14.10.0-rc42-ee
  • v14.9.3-ee
  • v14.6.7-ee
  • v14.7.7-ee
  • v14.8.5-ee
  • v14.9.2-ee
  • v14.7.6-ee
  • v14.9.1-ee
  • v14.9.0-ee
  • v14.9.0-rc42-ee
40 results

environment_spec.rb

Forked from GitLab.org / GitLab
Source project has a limited visibility.
  • Andrew Fontaine's avatar
    75c9f7e3
    Order Deployments by Finish Time · 75c9f7e3
    Andrew Fontaine authored
    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
    75c9f7e3
    History
    Order Deployments by Finish Time
    Andrew Fontaine authored
    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