kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Add latest changes from gitlab-org/gitlab@master

Browse source
This commit is contained in:
GitLab Bot 2021-09-04 00:11:27 +00:00
parent aaa1062165
commit 2bd5bef0d1
6 changed files with 291 additions and 223 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
app/assets/javascripts/webpack_non_compiled_placeholder.js
View file

@ -8,7 +8,7 @@ Object.assign(div.style, {
left: 0,
'z-index': 100000,
background: 'rgba(0,0,0,0.9)',
'font-size': '25px',
'font-size': '20px',
'font-family': 'monospace',
color: 'white',
padding: '2.5em',
@ -16,9 +16,23 @@ Object.assign(div.style, {
});
div.innerHTML = `
<h1 style="color:white">🧙 Webpack is doing its magic 🧙</h1>
<p>If you use Hot Module reloading, the page will reload in a few seconds.</p>
<p>If you do not use Hot Module reloading, please <a href="">reload the page manually in a few seconds</a></p>
<!-- https://github.com/webpack/media/blob/master/logo/icon-square-big.svg -->
<svg height="50" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1200 1200">
<path fill="#FFF" d="M600 0l530.3 300v600L600 1200 69.7 900V300z"/>
<path fill="#8ED6FB" class="st1" d="M1035.6 879.3l-418.1 236.5V931.6L878 788.3l157.6 91zm28.6-25.9V358.8l-153 88.3V765l153 88.4zm-901.5 25.9l418.1 236.5V931.6L320.3 788.3l-157.6 91zm-28.6-25.9V358.8l153 88.3V765l-153 88.4zM152 326.8L580.8 84.2v178.1L306.1 413.4l-2.1 1.2-152-87.8zm894.3 0L617.5 84.2v178.1l274.7 151.1 2.1 1.2 152-87.8z"/>
<path fill="#1C78C0" d="M580.8 889.7l-257-141.3v-280l257 148.4v272.9zm36.7 0l257-141.3v-280l-257 148.4v272.9zm-18.3-283.6zM341.2 436l258-141.9 258 141.9-258 149-258-149z"/>
</svg>
<h1 style="color:white">✨ webpack is compiling frontend assets ✨</h1>
<p>
To reduce GDK memory consumption, incremental on-demand compiling is on by default.<br />
You can disable this within gdk.yml.
Learn more <a href="https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/configuration.md#webpack-settings">here</a>.
</p>
<p>
If you have live_reload enabled, the page will reload automatically when complete.<br />
Otherwise, please <a href="">reload the page manually in a few seconds</a>
</p>
`;
document.body.append(div);

45
db/migrate/20210903054158_recreate_stage_issue_events_table_with_bigints.rb Normal file
View file

@ -0,0 +1,45 @@
# frozen_string_literal: true
class RecreateStageIssueEventsTableWithBigints < Gitlab::Database::Migration[1.0]
include Gitlab::Database::PartitioningMigrationHelpers::TableManagementHelpers
def up
drop_table :analytics_cycle_analytics_issue_stage_events # rubocop:disable Migration/DropTable
execute <<~SQL
CREATE TABLE analytics_cycle_analytics_issue_stage_events (
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone,
PRIMARY KEY (stage_event_hash_id, issue_id)
) PARTITION BY HASH (stage_event_hash_id)
SQL
create_hash_partitions :analytics_cycle_analytics_issue_stage_events, 32
end
def down
drop_table :analytics_cycle_analytics_issue_stage_events
execute <<~SQL
CREATE TABLE analytics_cycle_analytics_issue_stage_events (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone,
PRIMARY KEY (stage_event_hash_id, issue_id)
) PARTITION BY HASH (stage_event_hash_id)
SQL
create_hash_partitions :analytics_cycle_analytics_issue_stage_events, 32
end
end

1
db/schema_migrations/20210903054158 Normal file
View file

@ -0,0 +1 @@
113d6bb813a89646d48c8ba6a86fc8e73f741d5c345f603bfe33939fb90f9428

396
db/structure.sql
View file

@ -222,396 +222,396 @@ CREATE TABLE web_hook_logs (
PARTITION BY RANGE (created_at);
CREATE TABLE analytics_cycle_analytics_issue_stage_events (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
)
PARTITION BY HASH (stage_event_hash_id);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_00 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_00 FOR VALUES WITH (modulus 32, remainder 0);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_01 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_01 FOR VALUES WITH (modulus 32, remainder 1);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_02 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_02 FOR VALUES WITH (modulus 32, remainder 2);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_03 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_03 FOR VALUES WITH (modulus 32, remainder 3);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_04 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_04 FOR VALUES WITH (modulus 32, remainder 4);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_05 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_05 FOR VALUES WITH (modulus 32, remainder 5);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_06 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_06 FOR VALUES WITH (modulus 32, remainder 6);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_07 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_07 FOR VALUES WITH (modulus 32, remainder 7);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_08 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_08 FOR VALUES WITH (modulus 32, remainder 8);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_09 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_09 FOR VALUES WITH (modulus 32, remainder 9);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_10 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_10 FOR VALUES WITH (modulus 32, remainder 10);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_11 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_11 FOR VALUES WITH (modulus 32, remainder 11);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_12 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_12 FOR VALUES WITH (modulus 32, remainder 12);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_13 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_13 FOR VALUES WITH (modulus 32, remainder 13);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_14 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_14 FOR VALUES WITH (modulus 32, remainder 14);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_15 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_15 FOR VALUES WITH (modulus 32, remainder 15);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_16 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_16 FOR VALUES WITH (modulus 32, remainder 16);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_17 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_17 FOR VALUES WITH (modulus 32, remainder 17);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_18 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_18 FOR VALUES WITH (modulus 32, remainder 18);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_19 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_19 FOR VALUES WITH (modulus 32, remainder 19);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_20 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_20 FOR VALUES WITH (modulus 32, remainder 20);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_21 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_21 FOR VALUES WITH (modulus 32, remainder 21);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_22 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_22 FOR VALUES WITH (modulus 32, remainder 22);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_23 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_23 FOR VALUES WITH (modulus 32, remainder 23);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_24 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_24 FOR VALUES WITH (modulus 32, remainder 24);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_25 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_25 FOR VALUES WITH (modulus 32, remainder 25);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_26 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_26 FOR VALUES WITH (modulus 32, remainder 26);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_27 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_27 FOR VALUES WITH (modulus 32, remainder 27);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_28 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_28 FOR VALUES WITH (modulus 32, remainder 28);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_29 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_29 FOR VALUES WITH (modulus 32, remainder 29);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_30 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);
ALTER TABLE ONLY analytics_cycle_analytics_issue_stage_events ATTACH PARTITION gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_30 FOR VALUES WITH (modulus 32, remainder 30);
CREATE TABLE gitlab_partitions_static.analytics_cycle_analytics_issue_stage_events_31 (
stage_event_hash_id integer NOT NULL,
issue_id integer NOT NULL,
group_id integer NOT NULL,
project_id integer NOT NULL,
milestone_id integer,
author_id integer,
stage_event_hash_id bigint NOT NULL,
issue_id bigint NOT NULL,
group_id bigint NOT NULL,
project_id bigint NOT NULL,
milestone_id bigint,
author_id bigint,
start_event_timestamp timestamp with time zone NOT NULL,
end_event_timestamp timestamp with time zone
);

48
doc/user/project/import/github.md
View file

@ -31,13 +31,18 @@ each imported repository maintains visibility level unless that [visibility
level is restricted](../../../public_access/public_access.md#restrict-use-of-public-or-internal-projects),
in which case it defaults to the default project visibility.
The namespace is a user or group in GitLab, such as `gitlab.com/janedoe` or `gitlab.com/customer-success`. You can do some bulk actions to move projects to different namespaces in the rails console.
The namespace is a user or group in GitLab, such as `gitlab.com/janedoe` or
`gitlab.com/customer-success`. You can do some bulk actions to move projects to
different namespaces in the rails console.
This process does not migrate or import any types of groups or organizations from GitHub to GitLab.
This process does not migrate or import any types of groups or organizations
from GitHub to GitLab.
## Use cases
The steps you take depend on whether you are importing from GitHub.com or GitHub Enterprise, as well as whether you are importing to GitLab.com or self-managed GitLab instance.
The steps you take depend on whether you are importing from GitHub.com or
GitHub Enterprise. The steps also depend on whether you are importing to GitLab.com or
self-managed GitLab instance.
- If you're importing to GitLab.com, you can alternatively import GitHub repositories
using a [personal access token](#use-a-github-token). We do not recommend
@ -49,12 +54,14 @@ The steps you take depend on whether you are importing from GitHub.com or GitHub
- If you're importing from GitHub Enterprise to your self-managed GitLab instance, you must first enable
[GitHub integration](../../../integration/github.md).
- To import projects from GitHub Enterprise to GitLab.com, use the [Import API](../../../api/import.md).
- If you're importing from GitHub.com to your self-managed GitLab instance, you do not need to set up GitHub integration. You can use the [Import API](../../../api/import.md).
- If you're importing from GitHub.com to your self-managed GitLab instance,
setting up GitHub integration is not required. You can use the [Import API](../../../api/import.md).
## How it works
When issues and pull requests are being imported, the importer attempts to find their GitHub authors and
assignees in the database of the GitLab instance (note that pull requests are called "merge requests" in GitLab).
When issues and pull requests are being imported, the importer attempts to find
their GitHub authors and assignees in the database of the GitLab instance (note
that pull requests are called "merge requests" in GitLab).
For this association to succeed, each GitHub author and assignee in the repository
must meet one of the following conditions prior to the import:
@ -64,12 +71,13 @@ must meet one of the following conditions prior to the import:
that matches their GitLab account's email address.
NOTE:
GitLab content imports that use GitHub accounts require that the GitHub public-facing
email address is populated so that all comments and contributions are properly mapped
to the same user in GitLab. GitHub Enterprise (on premise) does not require this field
to be populated to use the product, so you may need to add it on existing GitHub Enterprise
accounts for imported content to be properly mapped to the user in the new system.
Refer to GitHub documentation for instructions on how to add that address.
GitLab content imports that use GitHub accounts require that the GitHub
public-facing email address is populated so that all comments and
contributions are properly mapped to the same user in GitLab. GitHub
Enterprise (on premise) does not require this field to be populated to use the
product, so you may have to add it on existing accounts for the imported
content to be properly mapped to the user in the new system. Refer to GitHub
documentation for instructions on how to add this email address.
If a user referenced in the project is not found in the GitLab database, the project creator (typically the user
that initiated the import process) is set as the author/assignee, but a note on the issue mentioning the original
@ -132,7 +140,7 @@ If you are not using the GitHub integration, you can still perform an authorizat
1. Copy the token hash.
1. Go back to GitLab and provide the token to the GitHub importer.
1. Hit the **List Your GitHub Repositories** button and wait while GitLab reads your repositories' information.
Once done, you'll be taken to the importer page to select the repositories to import.
Once done, you are taken to the importer page to select the repositories to import.
To use a newer personal access token in imports after previously performing these steps, sign out of
your GitLab account and sign in again, or revoke the older personal access token in GitHub.
@ -152,7 +160,7 @@ your GitHub repositories are listed.
![GitHub importer page](img/import_projects_from_github_importer_v12_3.png)
## Mirroring and pipeline status sharing
## Mirror a repository and share pipeline status
Depending on your GitLab tier, [repository mirroring](../repository/repository_mirroring.md) can be set up to keep
your imported repository in sync with its GitHub copy.
@ -169,7 +177,7 @@ Mirroring does not sync any new or updated pull requests from your GitHub projec
## Improve the speed of imports on self-managed instances
NOTE:
Administrator access to the GitLab server is required.
An administrator role on the GitLab server is required for this process.
For large projects it may take a while to import all data. To reduce the time necessary, you can increase the number of
Sidekiq workers that process the following queues:
@ -183,19 +191,19 @@ servers. For 4 servers with 8 cores this means you can import up to 32 objects (
Reducing the time spent in cloning a repository can be done by increasing network throughput, CPU capacity, and disk
performance (by using high performance SSDs, for example) of the disks that store the Git repositories (for your GitLab instance).
Increasing the number of Sidekiq workers will *not* reduce the time spent cloning repositories.
Increasing the number of Sidekiq workers does *not* reduce the time spent cloning repositories.
## Alternative way to import notes and diff notes
When GitHub Importer runs on extremely large projects not all notes & diff notes can be imported due to GitHub API `issues_comments` & `pull_requests_comments` endpoints limitation.
Not all pages can be fetched due to the following error coming from GitHub API: `In order to keep the API fast for everyone, pagination is limited for this resource. Check the rel=last link relation in the Link response header to see how far back you can traverse.`.
Because of that, alternative approach for importing notes & diff notes is available that is behind a feature flag.
An alternative approach for importing notes and diff notes is available behind a feature flag.
Instead of using `issues_comments` & `pull_requests_comments`, use individual resources `issue_comments` & `pull_request_comments` instead in order to pull notes from 1 object at a time.
This allows us to carry over any missing comments, however it increases the number of network requests required to perform the import, which means its execution is going to be much longer.
Instead of using `issues_comments` and `pull_requests_comments`, use individual resources `issue_comments` and `pull_request_comments` instead to pull notes from one object at a time.
This allows us to carry over any missing comments, however it increases the number of network requests required to perform the import, which means its execution takes a longer time.
In order to use alternative way of importing notes `github_importer_single_endpoint_notes_import` feature flag needs to be enabled on the group project is being imported into.
To use the alternative way of importing notes, the `github_importer_single_endpoint_notes_import` feature flag must be enabled on the group project is being imported into.
Start a [Rails console](../../../administration/operations/rails_console.md#starting-a-rails-console-session).

2
doc/user/project/integrations/github.md
View file

@ -11,7 +11,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
GitLab provides an integration for updating the pipeline statuses on GitHub.
This is especially useful if using GitLab for CI/CD only.
This project integration is separate from the [instance wide GitHub integration](../import/github.md#mirroring-and-pipeline-status-sharing)
This project integration is separate from the [instance wide GitHub integration](../import/github.md#mirror-a-repository-and-share-pipeline-status)
and is automatically configured on [GitHub import](../../../integration/github.md).
![Pipeline status update on GitHub](img/github_status_check_pipeline_update.png)