Skip to content
Snippets Groups Projects
Select Git revision
  • move-gl-dropdown
  • improve-table-pagination-spec
  • move-markdown-preview
  • winh-fix-merge-request-spec
  • master default
  • index-namespaces-lower-name
  • winh-single-karma-test
  • 10-3-stable
  • 36782-replace-team-user-role-with-add_role-user-in-specs
  • winh-modal-internal-state
  • tz-ide-file-icons
  • 38869-milestone-select
  • update-autodevops-template
  • jivl-activate-repo-cookie-preferences
  • qa-add-deploy-key
  • docs-move-article-ldap
  • 40780-choose-file
  • 22643-manual-job-page
  • refactor-cluster-show-page-conservative
  • dm-sidekiq-versioning
  • v10.4.0.pre
  • v10.3.0
  • v10.3.0-rc5
  • v10.3.0-rc4
  • v10.3.0-rc3
  • v10.3.0-rc2
  • v10.2.5
  • v10.3.0-rc1
  • v10.0.7
  • v10.1.5
  • v10.2.4
  • v10.2.3
  • v10.2.2
  • v10.2.1
  • v10.3.0.pre
  • v10.2.0
  • v10.2.0-rc4
  • v10.2.0-rc3
  • v10.1.4
  • v10.2.0-rc2
40 results

20170301205639_remove_unused_ci_tables_and_columns.rb

Forked from GitLab.org / GitLab FOSS
Source project has a limited visibility.
  • Lin Jen-Shin's avatar
    99294e09
    Do nothing if ci_builds.job_id isn't there · 99294e09
    Lin Jen-Shin authored
    This is really weird. I think we did get the same issue while
    migrating on GitLab.com. We fixed this by adding job_id to
    ci_builds table manually, and then run the migrations again.
    However I think we didn't hit into this on staging, which should
    somehow be a production clone.
    
    At any rate, I guess we could check if the column exists in the
    migration. If the column is not there, there's no point to remove
    that column anyway.
    
    Closes #29976
    99294e09
    History
    Do nothing if ci_builds.job_id isn't there
    Lin Jen-Shin authored
    This is really weird. I think we did get the same issue while
    migrating on GitLab.com. We fixed this by adding job_id to
    ci_builds table manually, and then run the migrations again.
    However I think we didn't hit into this on staging, which should
    somehow be a production clone.
    
    At any rate, I guess we could check if the column exists in the
    migration. If the column is not there, there's no point to remove
    that column anyway.
    
    Closes #29976