Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Boxiang Sun
gitlab-ce
Commits
1a8dc206
Commit
1a8dc206
authored
May 04, 2017
by
Luke "Jared" Bennett
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Reset migration to head
parent
d34f6764
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
0 additions
and
98 deletions
+0
-98
db/migrate/20170428123910_add_clientside_sentry_to_application_settings.rb
...28123910_add_clientside_sentry_to_application_settings.rb
+0
-31
db/migrate/20170504094058_add_clientside_sentry_to_application_settings.rb
...04094058_add_clientside_sentry_to_application_settings.rb
+0
-65
db/schema.rb
db/schema.rb
+0
-2
No files found.
db/migrate/20170428123910_add_clientside_sentry_to_application_settings.rb
deleted
100644 → 0
View file @
d34f6764
class
AddClientsideSentryToApplicationSettings
<
ActiveRecord
::
Migration
include
Gitlab
::
Database
::
MigrationHelpers
# Set this constant to true if this migration requires downtime.
DOWNTIME
=
false
# When a migration requires downtime you **must** uncomment the following
# constant and define a short and easy to understand explanation as to why the
# migration requires downtime.
# DOWNTIME_REASON = ''
# When using the methods "add_concurrent_index" or "add_column_with_default"
# you must disable the use of transactions as these methods can not run in an
# existing transaction. When using "add_concurrent_index" make sure that this
# method is the _only_ method called in the migration, any other changes
# should go in a separate migration. This ensures that upon failure _only_ the
# index creation fails and can be retried or reverted easily.
#
# To disable transactions uncomment the following line and remove these
# comments:
disable_ddl_transaction!
def
up
add_column_with_default
:application_settings
,
:clientside_sentry_enabled
,
:boolean
,
default:
false
add_column
:application_settings
,
:clientside_sentry_dsn
,
:string
end
def
down
remove_columns
:application_settings
,
:clientside_sentry_enabled
,
:clientside_sentry_dsn
end
end
db/migrate/20170504094058_add_clientside_sentry_to_application_settings.rb
deleted
100644 → 0
View file @
d34f6764
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
# for more information on how to write migrations for GitLab.
class
AddClientsideSentryToApplicationSettings
<
ActiveRecord
::
Migration
include
Gitlab
::
Database
::
MigrationHelpers
# Set this constant to true if this migration requires downtime.
DOWNTIME
=
false
# When a migration requires downtime you **must** uncomment the following
# constant and define a short and easy to understand explanation as to why the
# migration requires downtime.
# DOWNTIME_REASON = ''
# When using the methods "add_concurrent_index", "remove_concurrent_index" or
# "add_column_with_default" you must disable the use of transactions
# as these methods can not run in an existing transaction.
# When using "add_concurrent_index" or "remove_concurrent_index" methods make sure
# that either of them is the _only_ method called in the migration,
# any other changes should go in a separate migration.
# This ensures that upon failure _only_ the index creation or removing fails
# and can be retried or reverted easily.
#
# To disable transactions uncomment the following line and remove these
# comments:
disable_ddl_transaction!
# Reversability was tested when I made an update the originally irreversible
# migration after I ran it, so I could test that the down method worked and then
# the up method worked.
def
up
add_column_with_default
:application_settings
,
:clientside_sentry_enabled
,
:boolean
,
default:
false
add_column
:application_settings
,
:clientside_sentry_dsn
,
:string
end
def
down
remove_columns
:application_settings
,
:clientside_sentry_enabled
,
:clientside_sentry_dsn
end
end
class
AddClientsideSentryToApplicationSettings
<
ActiveRecord
::
Migration
include
Gitlab
::
Database
::
MigrationHelpers
# Set this constant to true if this migration requires downtime.
DOWNTIME
=
false
# When a migration requires downtime you **must** uncomment the following
# constant and define a short and easy to understand explanation as to why the
# migration requires downtime.
# DOWNTIME_REASON = ''
# When using the methods "add_concurrent_index" or "add_column_with_default"
# you must disable the use of transactions as these methods can not run in an
# existing transaction. When using "add_concurrent_index" make sure that this
# method is the _only_ method called in the migration, any other changes
# should go in a separate migration. This ensures that upon failure _only_ the
# index creation fails and can be retried or reverted easily.
#
# To disable transactions uncomment the following line and remove these
# comments:
disable_ddl_transaction!
end
db/schema.rb
View file @
1a8dc206
...
@@ -121,8 +121,6 @@ ActiveRecord::Schema.define(version: 20170502091007) do
...
@@ -121,8 +121,6 @@ ActiveRecord::Schema.define(version: 20170502091007) do
t
.
integer
"cached_markdown_version"
t
.
integer
"cached_markdown_version"
t
.
boolean
"usage_ping_enabled"
,
default:
true
,
null:
false
t
.
boolean
"usage_ping_enabled"
,
default:
true
,
null:
false
t
.
string
"uuid"
t
.
string
"uuid"
t
.
boolean
"clientside_sentry_enabled"
,
default:
false
,
null:
false
t
.
string
"clientside_sentry_dsn"
end
end
create_table
"audit_events"
,
force: :cascade
do
|
t
|
create_table
"audit_events"
,
force: :cascade
do
|
t
|
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment