To run analyses in TrustInSoft CI, a configuration is required for the GitHub repository to analyze. This configuration can:
either be written in the Project settings page (in the
Build configuration section) (and is called a Global configuration),
or be committed with files in the GitHub repository inside a
.trustinsoft/ directory at the root of the repository (and is called a Committed configuration).
This configuration includes:
the optional Build preparation stage, to prepare the repository to be analyzed,
and the required Analyses configuration, to describe the list of analyses.
While set-upping a project, you will have to chose between using a Global configuration (written in the Project settings page) or a Committed configuration (committed in the
.trustinsoft/directory of the GitHub repository), according to the following advantages and disadvantages:
➕ Easy set-up without updating your repository
➖ Requires to modify your repository by committing files
➕ Common to all branches, tags, and pull requests
➕ Each branch, tag or pull request can have its own unique configuration
➖ Replaying a build will use the current global configuration (and not the one used for the build)
➕ Replaying a build will use the same configuration of the associated commit