Description (Click to sort ascending) | Interval | Target (Click to sort ascending) | Last Pipeline | Next Run (Click to sort ascending) | Owner | |
|---|---|---|---|---|---|---|
No pipeline schedules | ||||||
** 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.
Description (Click to sort ascending)
↑
| Interval | Target (Click to sort ascending)
↑
| Last Pipeline | Next Run (Click to sort ascending)
↑
| Owner | |
|---|---|---|---|---|---|---|
No pipeline schedules | ||||||
Description (Click to sort ascending)
↑
| Interval | Target (Click to sort ascending)
↑
| Last Pipeline | Next Run (Click to sort ascending)
↑
| Owner | |
|---|---|---|---|---|---|---|
No pipeline schedules | ||||||
Description (Click to sort ascending)
↑
| Interval | Target (Click to sort ascending)
↑
| Last Pipeline | Next Run (Click to sort ascending)
↑
| Owner | |
|---|---|---|---|---|---|---|
No pipeline schedules | ||||||