-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
50 changed files
with
1,077 additions
and
538 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
|
||
| Allows to filter which steps to execute during launch. | ||
String value representing single filter or a set of filters separated by '**:**'. | ||
To define exclude pattern use '**!**' symbol at the beginning of the pattern. | ||
| | ||
| A Universum step match specified pattern when 'filter' is a substring of step 'name'. | ||
This functionality is similar to 'boosttest' and 'gtest' filtering, except special characters | ||
(like '*', '?', etc.) are ignored. | ||
| | ||
| Examples: | ||
| * -f='run test' - run only steps that contain 'run test' substring in their names | ||
| * -f='!run test' - run all steps except those containing 'run test' substring in their | ||
names | ||
| * -f='test 1:test 2' - run all steps with 'test 1' OR 'test 2' substring in their names | ||
| * -f='test 1:!unit test 1' - run all steps with 'test 1' substring in their names except those | ||
containing 'unit test 1' |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
Integration with GitHub Actions | ||
=============================== | ||
|
||
`Universum` requires no special integration with `GitHub Actions <https://docs.github.com/en/actions>`_. It is usually | ||
launched as one long step in a single build stage. | ||
|
||
.. warning:: | ||
|
||
'GitHub Actions' CI system is not compatible with ``report_artifacts`` :doc:`configuration Step key <configuration_support>`. | ||
If this key is set nevertheless, links to artifacts will be posted, but won't work. | ||
|
||
|
||
Command line | ||
------------ | ||
|
||
Here's an example of a command line to be used for running Universum in GitHub Actions:: | ||
|
||
python -m universum --vcs-type=git --git-repo "${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}" --git-refspec "${GITHUB_REF_NAME}" | ||
|
||
All environment variables mentioned in the example are `GitHub Environment variables | ||
<https://docs.github.com/en/actions/learn-github-actions/environment-variables>`_. | ||
|
||
`Universum` also supports reporting to code review systems ('--report-to-review' option) from 'GitHub Actions'. Link to | ||
build is created using environment variables and do not require any additional command line parameters. | ||
|
||
Logs | ||
---- | ||
|
||
GitHub Actions web interface currently supports single-level grouping of log lines | ||
(`without nesting <https://github.com/actions/runner/issues/802>`_). Because of that, Universum logs are printed | ||
as follows: an already opened group is closed if any other (including nested) group is opened. | ||
|
||
|
||
Artifacts | ||
--------- | ||
|
||
Artifacts can be stored in GitHub Actions with explicitly provided name via separate workflow step. | ||
It is possible to store multiple files in a single `artifact | ||
<https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts>`_, but it is not possible to | ||
retrieve only one file from such artifact. This leads to the following limitations: | ||
|
||
- links to GitHub Actions artifacts can only be retrieved after actual artifact creation | ||
(which happens after `Universum` run) | ||
- links to single artifact files cannot be provided at all | ||
|
||
This is the reason the ``report_artifacts`` key can not be processed correctly and shouldn't be set in configuration. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
Internal documentation | ||
---------------------- | ||
|
||
.. automodule:: universum.modules.output.base_output | ||
:members: | ||
:special-members: | ||
|
||
:mod:`universum.modules.output.base_output` | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.