You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been getting a slew of cases where users are reporting requiring
different configurations -- especially Github Actions, where we seem to
need to set a different service name on a case-by-case basis.
Reordering our configuration precedence such that user-specified values
overwrite the CI defaults should allow users to fix these problems
without requiring a one-size-fits-all code change.
This is massively backwards incompatible for anyone with the same key
set to two different values in their configs.
Copy file name to clipboardExpand all lines: docs/usage/configuration.rst
+19-2Lines changed: 19 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,9 +3,22 @@
3
3
Configuration
4
4
=============
5
5
6
-
coveralls-python often works without any outside configuration by examining the environment it is being run in. Special handling has been added for AppVeyor, BuildKite, CircleCI, Github Actions, Jenkins, and TravisCI to make coveralls-python as close to "plug and play" as possible.
6
+
coveralls-python often works without any outside configuration by examining the
7
+
environment it is being run in. Special handling has been added for AppVeyor,
8
+
BuildKite, CircleCI, Github Actions, Jenkins, and TravisCI to make
9
+
coveralls-python as close to "plug and play" as possible.
7
10
8
-
Most often, you will simply need to run coveralls-python with no additional options after you have run your coverage suite::
11
+
In cases where you do need to modify the configuration, we obey a very strict
12
+
precedence order where the **latest value is used**:
13
+
14
+
* first, the CI environment will be loaded
15
+
* second, any environment variables will be loaded (eg. those which begin with
16
+
``COVERALLS_``
17
+
* third, the config file is loaded (eg. ``./..coveralls.yml``)
18
+
* finally, any command line flags are evaluated
19
+
20
+
Most often, you will simply need to run coveralls-python with no additional
21
+
options after you have run your coverage suite::
9
22
10
23
coveralls
11
24
@@ -68,6 +81,10 @@ Passing a coveralls.io token via the ``COVERALLS_REPO_TOKEN`` environment variab
68
81
(or via the ``repo_token`` parameter in the config file) is not needed for
69
82
Github Actions.
70
83
84
+
Sometimes Github Actions gets a little picky about the service name which needs to
85
+
be used in various cases. If you run into issues, try setting the ``COVERALLS_SERVICE_NAME``
86
+
explicitly to either ``github`` or ``github-actions``.
87
+
71
88
For parallel builds, you have to add a final step to let coveralls.io know the
0 commit comments