Nextbuttons on a build's page (to go to the previous/next build of the same project) could lead to a build of another branch/tag. So comparing results for a same reference was not convenient.
tis.configfiles, so we will not have to change anything for projects you already set-up in TrustInSoft CI.
.jsonextension (that makes IDE/editors happy for syntax highlighting), and to allow the usage of a directory to gather any files related to TrustInSoft CI in a single place (see also the next new feature!).
.trustinsoft/prepare.shscript in your GitHub repository and write in
bashall the actions you need to do, such as:
.trustinsoft/prepare.shscript is run inside the
.trustinsoft/directory only once per build before reading the
.trustinsoft/config.json. Read more about the prepare.sh file in the documentation.
.trustinsoft/prepare.shfiles) directly in the Project settings page:
.trustinsoftdirectory exists among the committed files for the analyzed reference (in this case, committed files are taken into account and the global configuration is ignored).
Add referenceto many times, especially when Pull Requests are opened
"no-result": truefield. With this field, nothing relevant can be inspected within the
-U) or the whole compilation line. TrustInSoft CI will keep only the relevant options.
cxx-cpp-extra-argsfor respectively C and C++ source files. If your project contains source files in both languages, include both fields in the tis.config file.
"no-results": trueto your tis.config file. The tests will run faster and consume less memory.
0and it will return the Invalid property status otherwise: