** 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.
Redis streams are used to inform about update events, typically "create", "delete" and "update" for various resource types. The data itself should be stored within regular Redis keys and not included in the event, the event just details which resource has changed.
# Commands
Command streams instruct other services to perform a CRUD operation or issue an instruction of another kind. As an example, one service might wish to query a resource but finds that Redis does not contain that data yet (or it expired). To obtain the data it needs to send a query request and then respond to an update event.
