diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-18 09:06:43 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-18 09:06:43 +0000 |
commit | 5333cb6c7c960aac58af40c898c87d050d829383 (patch) | |
tree | 79cac8f3f0cf63340b3c0c305d2d1e9780f43ea6 /doc | |
parent | 44baf08d4ff4b0d32fecfded843257e2fc49a63c (diff) | |
download | gitlab-ce-5333cb6c7c960aac58af40c898c87d050d829383.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc')
-rw-r--r-- | doc/administration/geo/replication/troubleshooting.md | 13 | ||||
-rw-r--r-- | doc/api/graphql/reference/gitlab_schema.graphql | 9 | ||||
-rw-r--r-- | doc/api/graphql/reference/gitlab_schema.json | 22 | ||||
-rw-r--r-- | doc/ci/img/junit_test_report_ui.png | bin | 84300 -> 0 bytes | |||
-rw-r--r-- | doc/ci/img/pipelines_junit_test_report_ui_v12_5.png | bin | 0 -> 15957 bytes | |||
-rw-r--r-- | doc/ci/junit_test_reports.md | 2 | ||||
-rw-r--r-- | doc/development/api_graphql_styleguide.md | 26 |
7 files changed, 58 insertions, 14 deletions
diff --git a/doc/administration/geo/replication/troubleshooting.md b/doc/administration/geo/replication/troubleshooting.md index 5c40a4441b6..d2fe02abbab 100644 --- a/doc/administration/geo/replication/troubleshooting.md +++ b/doc/administration/geo/replication/troubleshooting.md @@ -366,7 +366,7 @@ to start again from scratch, there are a few steps that can help you: gitlab-ctl tail sidekiq ``` -1. Rename repository storage folders and create new ones +1. Rename repository storage folders and create new ones. If you are not concerned about possible orphaned directories and files, then you can simply skip this step. ```sh mv /var/opt/gitlab/git-data/repositories /var/opt/gitlab/git-data/repositories.old @@ -413,7 +413,9 @@ to start again from scratch, there are a few steps that can help you: 1. Reset the Tracking Database ```sh - gitlab-rake geo:db:reset + gitlab-rake geo:db:drop + gitlab-ctl reconfigure + gitlab-rake geo:db:setup ``` 1. Restart previously stopped services @@ -653,13 +655,6 @@ Geo cannot reuse an existing tracking database. It is safest to use a fresh secondary, or reset the whole secondary by following [Resetting Geo secondary node replication](#resetting-geo-secondary-node-replication). -If you are not concerned about possible orphaned directories and files, then you -can simply reset the existing tracking database with: - -```sh -sudo gitlab-rake geo:db:reset -``` - ### Geo node has a database that is writable which is an indication it is not configured for replication with the primary node This error refers to a problem with the database replica on a **secondary** node, diff --git a/doc/api/graphql/reference/gitlab_schema.graphql b/doc/api/graphql/reference/gitlab_schema.graphql index ecb7f04318a..f79122538a8 100644 --- a/doc/api/graphql/reference/gitlab_schema.graphql +++ b/doc/api/graphql/reference/gitlab_schema.graphql @@ -539,7 +539,7 @@ type DesignCollection { """ Filters designs to only those that existed at the version. If argument is - omitted or nil then all designs will reflect the latest version. + omitted or nil then all designs will reflect the latest version """ atVersion: ID @@ -549,12 +549,17 @@ type DesignCollection { before: String """ + Filters designs by their filename + """ + filenames: [String!] + + """ Returns the first _n_ elements from the list. """ first: Int """ - The list of IDs of designs. + Filters designs by their ID """ ids: [ID!] diff --git a/doc/api/graphql/reference/gitlab_schema.json b/doc/api/graphql/reference/gitlab_schema.json index b8d788fb6ec..eee98255367 100644 --- a/doc/api/graphql/reference/gitlab_schema.json +++ b/doc/api/graphql/reference/gitlab_schema.json @@ -7979,7 +7979,7 @@ "args": [ { "name": "ids", - "description": "The list of IDs of designs.", + "description": "Filters designs by their ID", "type": { "kind": "LIST", "name": null, @@ -7996,8 +7996,26 @@ "defaultValue": null }, { + "name": "filenames", + "description": "Filters designs by their filename", + "type": { + "kind": "LIST", + "name": null, + "ofType": { + "kind": "NON_NULL", + "name": null, + "ofType": { + "kind": "SCALAR", + "name": "String", + "ofType": null + } + } + }, + "defaultValue": null + }, + { "name": "atVersion", - "description": "Filters designs to only those that existed at the version. If argument is omitted or nil then all designs will reflect the latest version.", + "description": "Filters designs to only those that existed at the version. If argument is omitted or nil then all designs will reflect the latest version", "type": { "kind": "SCALAR", "name": "ID", diff --git a/doc/ci/img/junit_test_report_ui.png b/doc/ci/img/junit_test_report_ui.png Binary files differdeleted file mode 100644 index 380c6bbb89c..00000000000 --- a/doc/ci/img/junit_test_report_ui.png +++ /dev/null diff --git a/doc/ci/img/pipelines_junit_test_report_ui_v12_5.png b/doc/ci/img/pipelines_junit_test_report_ui_v12_5.png Binary files differnew file mode 100644 index 00000000000..5b1e3254f8b --- /dev/null +++ b/doc/ci/img/pipelines_junit_test_report_ui_v12_5.png diff --git a/doc/ci/junit_test_reports.md b/doc/ci/junit_test_reports.md index 3a94e9725e7..c03d1798ae1 100644 --- a/doc/ci/junit_test_reports.md +++ b/doc/ci/junit_test_reports.md @@ -187,7 +187,7 @@ If JUnit XML files are generated and uploaded as part of a pipeline, these repor can be viewed inside the pipelines details page. The **Tests** tab on this page will display a list of test suites and cases reported from the XML file. -![Test Reports Widget](img/junit_test_report_ui.png) +![Test Reports Widget](img/pipelines_junit_test_report_ui_v12_5.png) You can view all the known test suites and click on each of these to see further details, including the cases that makeup the suite. Cases are ordered by status, diff --git a/doc/development/api_graphql_styleguide.md b/doc/development/api_graphql_styleguide.md index 7161caf19ed..b0d94511c6e 100644 --- a/doc/development/api_graphql_styleguide.md +++ b/doc/development/api_graphql_styleguide.md @@ -548,6 +548,32 @@ found, we should raise a `Gitlab::Graphql::Errors::ResourceNotAvailable` error. Which will be correctly rendered to the clients. +## Gitlab's custom scalars + +### `Types::TimeType` + +[`Types::TimeType`](https://gitlab.com/gitlab-org/gitlab/blob/master/app%2Fgraphql%2Ftypes%2Ftime_type.rb) +must be used as the type for all fields and arguments that deal with Ruby +`Time` and `DateTime` objects. + +The type is +[a custom scalar](https://github.com/rmosolgo/graphql-ruby/blob/master/guides/type_definitions/scalars.md#custom-scalars) +that: + +- Converts Ruby's `Time` and `DateTime` objects into standardized + ISO-8601 formatted strings, when used as the type for our GraphQL fields. +- Converts ISO-8601 formatted time strings into Ruby `Time` objects, + when used as the type for our GraphQL arguments. + +This allows our GraphQL API to have a standardized way that it presents time +and handles time inputs. + +Example: + +```ruby +field :created_at, Types::TimeType, null: false, description: 'Timestamp of when the issue was created' +``` + ## Testing _full stack_ tests for a graphql query or mutation live in |