actions-marketplace-validations/Teamscale Upload
Uploads external analysis results (coverage, findings, …) to Teamscale.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| server | The url under which the Teamscale server can be reached. | yes | — |
| project | The project ID (NOT the project name!) to which to upload the data. | yes | — |
| user | The username used to perform the upload. Must have the "Perform External Uploads" permission for the given Teamscale project. | yes | — |
| accesskey | The IDE access key of the given user. Can be retrieved in Teamscale under Admin > Users. | yes | — |
| partition | The partition into which the data is inserted in Teamscale. Successive uploads into the same partition will overwrite the data previously inserted there, so use different partitions if you would instead like to merge data from different sources (e.g. one for Findbugs findings and one for JaCoCo coverage). | yes | — |
| format | The file format of the reports which are specified as command line arguments. See http://cqse.eu/upload-formats for a full list of supported file formats. A report format must be supplied for each report file, either via --format or via --input. | no | — |
| revision | The version control commit for which you obtained the report files. E.g. if you obtained a test coverage report in your CI pipeline, then this is the commit the CI pipeline built before running the tests. Can be either a Git SHA1, a SVN revision number or an Team Foundation changeset ID. | no | — |
| repository | When using the revision parameter, this parameter allows to pass a repository name which is used to identify the correct commit in situations where the same revision exists in multiple repositories. | no | — |
| branch-and-timestamp | The branch and Unix Epoch timestamp for which you obtained the report files. E.g. if you obtained a test coverage report in your CI pipeline, then this is the branch and the commit timestamp of the commit that the CI pipeline built before running the tests. The timestamp must be milliseconds since 00:00:00 UTC Thursday, 1 January 1970 or the string HEAD to upload to the latest revision on that branch. Format: BRANCH:TIMESTAMP Example: master:1597845930000 Example: develop:HEAD | no | — |
| message | The message for the commit created in Teamscale for this upload. Will be visible in the Activity perspective. Defaults to a message containing useful meta-information about the upload and the machine performing it. | no | — |
| input | A file which contains additional report file patterns. A report format must be supplied for each report file, either via --format or via --input. | no | — |
| insecure | Causes SSL certificates to be accepted without validation, which makes using this tool with self-signed or invalid certificates easier. | no | false |
| trusted-keystore | A Java keystore file and its corresponding password. The keystore contains additional certificates that should be trusted when performing SSL requests. Separate the path from the password with a semicolon, e.g: /path/to/keystore.jks;PASSWORD The path to the keystore must not contain a semicolon. When this option is used, --validate-ssl will automatically be enabled as well. | no | — |
| append-to-message | Appends the given line to the message. Use this to augment the autogenerated message instead of replacing it. You may specify multiple lines separated by space to append several lines to the message (e.g., "1 3 10") | no | — |
| files | Path(s) or pattern(s) of the report files to upload. Alternatively, you may provide input files via the input parameter. | no | — |
| stacktrace | Enables printing stack traces in all cases where errors occur. Used for debugging. | no | false |
| timeout | Sets the timeout in seconds for TCP connect, read and write for HTTP requests. Defaults to 60 seconds. | no | — |
Outputs
no outputs