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
1
Merge Requests
1
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
nexedi
gitlab-ce
Commits
78654a8c
Commit
78654a8c
authored
Apr 10, 2019
by
Rémy Coutable
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add missing team and stage labels in the workflow labels doc
Signed-off-by:
Rémy Coutable
<
remy@rymai.me
>
parent
6a2e10e3
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
6 additions
and
2 deletions
+6
-2
doc/development/contributing/issue_workflow.md
doc/development/contributing/issue_workflow.md
+4
-0
doc/development/testing_guide/flaky_tests.md
doc/development/testing_guide/flaky_tests.md
+2
-2
No files found.
doc/development/contributing/issue_workflow.md
View file @
78654a8c
...
...
@@ -62,10 +62,12 @@ The current team labels are:
-
~Configure
-
~Create
-
~Defend
-
~Distribution
-
~Documentation
-
~Geo
-
~Gitaly
-
~Growth
-
~Manage
-
~Monitor
-
~Plan
...
...
@@ -99,6 +101,8 @@ The current stage labels are:
-
~"devops:configure"
-
~"devops:monitor"
-
~"devops:secure"
-
~"devops:defend"
-
~"devops:enablement"
These labels should be mutually exclusive. If an issue belongs to multiple
stages, the most relevant should be used.
...
...
doc/development/testing_guide/flaky_tests.md
View file @
78654a8c
...
...
@@ -8,7 +8,7 @@ eventually.
## Quarantined tests
When a test frequently fails in
`master`
,
[
a ~"
broken master
" issue
](
https://about.gitlab.com/handbook/engineering/workflow/#broken-master
)
[
a ~"
master:broken
" issue
](
https://about.gitlab.com/handbook/engineering/workflow/#broken-master
)
should be created.
If the test cannot be fixed in a timely fashion, there is an impact on the
productivity of all the developers, so it should be placed in quarantine by
...
...
@@ -21,7 +21,7 @@ bin/rspec --tag quarantine
```
**
Before putting a test in quarantine, you should make sure that a
~"
broken master
" issue exists for it so it won't stay in quarantine forever.
**
~"
master:broken
" issue exists for it so it won't stay in quarantine forever.
**
Once a test is in quarantine, there are 3 choices:
...
...
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