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
0
Merge Requests
0
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
Léo-Paul Géneau
gitlab-ce
Commits
0995d557
Commit
0995d557
authored
Oct 17, 2016
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Use better wording for test coverage parsing help text
parent
ea8b4edb
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
app/views/projects/pipelines_settings/show.html.haml
app/views/projects/pipelines_settings/show.html.haml
+2
-2
No files found.
app/views/projects/pipelines_settings/show.html.haml
View file @
0995d557
...
...
@@ -65,8 +65,8 @@
=
f
.
text_field
:build_coverage_regex
,
class:
'form-control'
,
placeholder:
'\(\d+.\d+\%\) covered'
%span
.input-group-addon
/
%p
.help-block
We will use this regular expression to find test coverage output in build trace.
Leave blank if you want to disable this featur
e
A regular expression that will be used to find the test coverage
output in the build trace. Leave blank to disabl
e
=
link_to
icon
(
'question-circle'
),
help_page_path
(
'user/project/pipelines/settings'
,
anchor:
'test-coverage-parsing'
)
.bs-callout.bs-callout-info
%p
Below are examples of regex for existing tools:
...
...
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