** Notice: all internal pipelines have been restricted to 30 minute timeouts, if your CI/CD runs take longer, either use your own runners or read below **
We would remind everyone that the CI/CD services provided by the university Gitlab servers are intended for CI/CD use only (ie. delivering new versions of your software to your production servers, etc).They are not intended for data analysis or -production use, or creating, building and running servers to do heavy data calculation or visualization.
As a general guideline; if your jobs take more than 15 minutes, you might be running something that is better suited for a dedicated system or a virtual server - in this case, please contact the helpdesk for a solution to your needs.
Configuration files use JSON format. Each component `<name>` (for example `vision`) has its configuration in `root["<name>"]`. Other names than `<name>` are not used for that component.
Using multiple configuration files is supported. If two (or more) configuration files have same keys, last loaded file sets the final values (Q: Are both objects and arrays merged?). Configuration files are included in following order, later files replace values set earlier:
1.`/local/share/ftl/config.json`
2.`~/.config/ftl/config.json`
3.`./config.json`
4.`config.json` files found in path(s) in argument(s)
5. Config file path provided in `--config` argument
Configuration values set in command line parameters override configuration file values.
