Nicolas Dular authored 5 years ago and Thong Kuah committed 5 years ago

Adds two different types of broadcast messages. Banner type is the
current design and will be kept shown on the top of the site, where
notification will be implemented in a separate frontend MR.

Allison Browne authored 5 years ago and Bob Van Landuyt :neckbeard: committed 5 years ago

Add table to store the sentry event and issue ids
that are related to a gitlab issue

This allows creating a `PoolRepository` for a source project for each
shard it resides on.

This will return data containing time tracked
for the group issues by group members and within
a time frame (limited to 60 days)

To get the collection of timelogs for a certain
group we include in Group a new concern
HasTimelogsReport that will use Timelog scopes
to filter results.

We use a TimelogPresenter to display additional
fields in TimelogType

Group timelogs is a premium feature so we added
group_timelogs feature to license

TimelogType is authorized with read_group_timelogs
permission that checks for a minimun access level of
reporter and group_timelogs feature being available
Refactor changes to improve code quality

- Include subgroups in Issue and Timelog scopes
- Field timelogs in GroupType is never null
- Add error to object validation in TimelogResolver
- Use fields UserType and IssueType  in TimelogType
- Improve rule in GroupPolicy
- Remove redundant TimelogPresenter
- Add missing specs for new scopes
- Extend specs for GroupType and  TimelogType
- Add new matcher fon non null graphql fields

Update GraphQL schema
Add index for spent_at in timelogs table

Fix Timelog scope to use group descendants

Sebastián Arcila Valenzuela authored 5 years ago and Imre (Admin) committed 5 years ago

It adds a worker (cron) that runs every day at 1AM that will notify the
user that some of its tokens are about to be expired.

Add `Packages::Dependency` and `Packages::DependencyLink`
  models
Add or update related services
Update `NpmPackagePresenter` to properly include dependencies

Co-Authored-By: Sara Ahbabou <sahbabou@gitlab.com>

This commit persists and controls auto stop date for environments

Charlie Ablett authored 5 years ago and Mayra Cabrera committed 5 years ago

- Non-unique

Sebastián Arcila Valenzuela authored 5 years ago and Mayra Cabrera committed 5 years ago

* Migration
* Application setting admin view
* license entry for ultimate

- Add tie-breaker `id desc` sorting to deployments API.
- Preload association to prevent n+1 queries.
- Turn `created_at` sorting to `id` sorting.
- Add index to speed up `updated_at` sorting.
- Add index to speed up `id` sorting.

* Remove duplicates
* Re-assign policies to oldest duplicate

mo khan authored 5 years ago and James Lopez committed 5 years ago

* Add a migration to rename the column
* Add a post migration to cleanup the migration
* Rename usages in backend code

https://docs.gitlab.com/ee/development/what_requires_downtime.html#renaming-columns

This commit preserves merge train rows after merge

Gitlab_subscriptions table currently doesn't keep history. That makes
blocks data team from measuring some growth KPIs. This MR adds a
history log table

Krasimir Angelov authored 5 years ago and Mayra Cabrera committed 5 years ago

Related to https://gitlab.com/gitlab-org/gitlab/issues/35697.

Adds partial indices to keys within `ci_variables` and
`ci_pipeline_variables` tables to track configuration of Web Application
Firewall for running environments

Diego Louzán authored 5 years ago and Bob Van Landuyt :neckbeard: committed 5 years ago

Make sure that the main admin mode controller path is added in the
default list of protected paths for Rack::Attack

This change adds `on_delete: :cascade`for the
foreign_key in `oauth_openid_requests` table.

This commit add a setting to snippets in order
to set a max limit to the content.

It can only be set through the Rails console
or the API.

The limit will affect to new snippets and existing
ones when the content is updated.

The default limit is 50MB.

This adds `target_path` to `BroadcastMessages` to allow to show
broadcast messages at certain URLs.
To match complex URLs, we allow to use `*` as wildcard characters for
the `target_url`. Since SQL is using `%` for wildcards, we need to
replace these characters in our query.

 - Add feature flag import_graceful_failures
 - Add feature flag to group instead of project
 - Add import_failures table
 - Gracefully fail, and log error
 - Send error to Sentry

Implementation idea for adding the artifacts keyword
into CI DAG needs.

Arturo Herrero authored 5 years ago and Alessio Caiazza committed 5 years ago

We had concerns about the cached values on Redis with the previous two
releases strategy:

First release (this commit):
  - Create new encrypted fields in the database.
  - Start populating new encrypted fields, read the encrypted fields or
    fallback to the plaintext fields.
  - Backfill the data removing the plaintext fields to the encrypted
    fields.
Second release:
  - Remove the virtual attribute (created in step 2).
  - Drop plaintext columns from the database (empty columns after
    step 3).

We end up with a better strategy only using migration scripts in one
release:
  - Pre-deployment migration: Add columns required for storing encrypted
    values.
  - Pre-deployment migration: Store the encrypted values in the new
    columns.
  - Post-deployment migration: Remove the old unencrypted columns

Arturo Herrero authored 5 years ago and Alessio Caiazza committed 5 years ago

This is the plan to encrypt the plaintext tokens:

First release (this commit):
  1. Create new encrypted fields in the database.
  2. Start populating new encrypted fields, read the encrypted fields or
     fallback to the plaintext fields.
  3. Backfill the data removing the plaintext fields to the encrypted fields.

Second release:
  4. Remove the virtual attribute (created in step 2).
  5. Drop plaintext columns from the database (empty columns after step 3).

Ho Tuan Duong authored 5 years ago and Bob Van Landuyt :neckbeard: committed 5 years ago

- Add column to store setting
- Update views, controller and params to handle updating the setting
- Add logic to jira_service to disable comments

- Implement query to join `resource_label_events` table.
- Extend the event serializer to show if an event is label based.
- Expose the label in a stage if the event is label based.
- Add missing event pairs for Issue events.

This change adds database changes required
for 'soft-delete for groups' feature

Extract a module MaxLimits for lists to make
limits behavior reusable.

Refactor existing logic a bit

Remove explicit namespaces and rubocop
disable comment in includes

Jan Beckmann authored 5 years ago and Mayra Cabrera committed 5 years ago

Closes #9898

Jason Goodman authored 5 years ago and Andreas Brandl committed 5 years ago

Replace index on environments project_id and state

Felipe Artur authored 5 years ago and Andreas Brandl committed 5 years ago

Let issue templates be applied on service desk issues

* Created DB tables for storing mentioned users, groups,
projects referenced in a note on issue, merge request, commit, epic
snippet or on issuable description. Mentioned users, groups, projects
will be stored as an array field in a corresponding table for: issues,
merge requests, commits, epics and snippets.

Francisco Javier López authored 5 years ago and Heinrich Lee Yu committed 5 years ago

For the new secret snippets feature we need to add a couple
of migrations and also a new index to include the new fields.