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
It would be useful, if the dbbot could save a table for continuous integration server information for each test run. Analysing the test results in context of CI server information would be a useful feature.
Some of the columns that could be saved
CI_REPO - repository name of the current build
CI_BRANCH - branch name for the current build
CI_COMMIT - git sha for the current build
CI_BUILD_NUMBER - build number for the current build
CI_PULL_REQUEST - pull request number of the current build
CI_BUILD_URL - url for the current build
CI_TAG - tag name for the current build
This is essentially more metadata for a test run and can be provided as a separate file or arguments to the command line.
The text was updated successfully, but these errors were encountered:
jakedsouza
changed the title
Allow continuous build informaiton and metadata to be serialized along with test runs
Allow continuous build information and metadata to be serialized along with test runs
Mar 6, 2017
It would be useful, if the dbbot could save a table for continuous integration server information for each test run. Analysing the test results in context of CI server information would be a useful feature.
Some of the columns that could be saved
This is essentially more metadata for a test run and can be provided as a separate file or arguments to the command line.
The text was updated successfully, but these errors were encountered: