| Age | Commit message (Collapse) | Author |
|---|
|
Gitaly's feature flags are much more limited compared to the feature
flags by Rails given that we do not support feature gates. As such, we
cannot ever use beta groups for a feature flag rollout.
Remove the section.
|
|
Add a `/title` command instead of documenting that the title should be
set.
|
|
|
|
|
|
Adjusts security merge request template to use the new changelog
workflow.
Related to gitlab-com/gl-infra/delivery#1767
|
|
This adds a configuration file for generating changelogs using the
GitLab API (done using Release Tools), as well as change Danger to
remind developers of these upcoming changes (similar to what we're doing
in gitlab-org/gitlab).
Omnibus, Pages and Helm are already using this new approach. Our current
plan is to also roll this out to remaining projects (GitLab Rails and
Gitaly) per May 22nd.
See https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/1564 for
more information.
|
|
After a couple of releases with enabled reads distribution
feature we are removing a feature flag completely.
The special test-cases deleted as now the feature is a default
and there is no way to change it.
The change also fixes some comments around reads distribution.
Closes: https://gitlab.com/gitlab-org/gitaly/-/issues/3383
|
|
|
|
It wasn't clear from the existing checklist item added in
2d9d7f9c9 (Add roll out issue template, 2019-06-11) what the removal
steps are, and what "remove feature flag" meant.
Split this up into steps where we discuss the removal from the
codebase, and what changelog entries we expect there, and then discuss
how to remove the feature via chatops.
|
|
I screwed this up in [1] and [2] and as a result the feature didn't
get enabled 100% on January 14th like I thought, but on January 27th
when the changes [3][4] to remove the feature flag itself went
live ([4] being the relevant change).
1. https://gitlab.com/gitlab-org/gitaly/-/issues/3412#note_485304117
2. https://gitlab.com/gitlab-org/gitaly/-/issues/3413#note_485303898
3. https://gitlab.com/gitlab-org/gitaly/-/merge_requests/3035
4. https://gitlab.com/gitlab-org/gitaly/-/merge_requests/3033
|
|
We don't need to do manual network configuration after
441ac39f2 (Demo: configuration of direct connection to
Postgres, 2020-12-30) is merged. We also don't need to
manually enable the feature flag as it is enabled by default
by 80b10d907 (Feature flag gitaly_distributed_reads enabled
by default, 2020-12-24).
|
|
|
|
Remove the "Ensure that the documentation has been updated" item. Yes,
docs are good, but this is not actionable. What docs are you going to
update between testing on staging and giving an ETA for production
rollout?
This was just copy/pasted from 2d9d7f9c9 (Add roll out issue template,
2019-06-11), presumably it meant some SRE rollout docs or something
they use. For gitaly the rollout is much simpler, and nobody's
updating any docs at this point in the process.
|
|
I added this because of a question @pks-t had in
https://gitlab.com/gitlab-org/gitaly/-/merge_requests/2995#note_484390302
It's easy to miss that we auto-add the featureflag::disabled flag
initially, let's cover that and provide handy links to the tracker to
see the status of each label.
|
|
Add more steps reflecting what we need to do after we have the feature
at 100%. Includes a paraphrased version of what I noted in my
a96949aef (Enable feature flag go_user_delete_{branch,tag} by default,
2021-01-12) as part of
https://gitlab.com/gitlab-org/gitaly/-/merge_requests/2994
|
|
Variable replication factor's demo script contains some incorrect
configuration lines. This commit corrects the situation.
|
|
Rather than duplicating things between the issue template and process
doc, let's cross link the two.
Also elaborate on a lot of things I encountered when enabling my first
features. This is the result of feedback on the initial version of
this [1] and a video chat with @zj-gitlab this morning.
1. https://gitlab.com/gitlab-org/gitaly/-/merge_requests/2910
|
|
The template said "Remove the...", but this is for creating
features. We've also changed the slack channel name.
|
|
Repository importer has been successfully demoed and has finished
in both production and staging. This commit removes the demo script
as it no longer is relevant.
|
|
|
|
Terraform configuration allows only PgBouncer connections to the Postrges database.
To demo reads distr caching we need to extend this set to include
IPs of the Praefect instances, so each Praefect can have direct
connection to Postgres to listen for notifications.
Once feature successfully demoed it would be automatically configured
by terraform setup as well.
|
|
Automatic reconciler has been successfully demoed on multiple
occasions. The only unfilled point is read-only metric missing from
the dashboards. This has an open issue already and is not strictly
related to the automatic reconciliation. This commit thus removes
the automatic reconciliation demo steps to make room for new features
on the demos.
|
|
Adds demo steps for performing a repository import to create missing
database records.
|
|
To understand the issue roll out status faster, and to make the roll out
issues appear on the issue board, the template was updated for new
issues.
|
|
The template included the wrong labels, this change updates the labels
in the template.
|
|
|
|
|
|
Prior to this change, the demo template didn't have any scripts. This
change adds two:
1. Test the ansible setup, to reduce the demo setup time
2. Verify the automatic repair of repositories
This allows a consistent test script throughout demos.
|
|
Demo issue template
Closes #2872
See merge request gitlab-org/gitaly!2486
|
|
|
|
|
|
|
|
Updates Security Release template
See merge request gitlab-org/gitaly!2311
|
|
Also adds a security merge request template
Related to https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/766
|
|
Introduces a process for introducing RFCs.
Closes https://gitlab.com/gitlab-org/gitaly/-/issues/2835
|
|
The "Security Release" issue template still mentions the old
"dev.gitlab.org" repositories, which have been replaced in favor of the
new "gitlab.org/security" ones.
Replace the old mentions to avoid any confusion.
|
|
|
|
Remove tag and stable branches syncing, it's automated in release-tools
|
|
Gitaly tagging is now automated by release-tools.
This MR update the development dovumentation.
https://gitlab.com/gitlab-org/gitaly/issues/2471
|
|
|
|
|
|
Last time the issue didn't include push mirroring, so tags didn't end up
on dev.gitlab.org. That means that builds were failing. Adding it to the
issue here should fix that for the next security release.
|
|
|
|
|
|
This one is copied from the GitLab-CE project, but seems applicible here
too.
|
|
|
|
|
|
|
|
These templates were in use, but given the project is nearing completion
on the migration phase and these templates won't be used anymore these
can be deleted.
|
|
It's been in the wrong order forever :)
|
