** 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.
@@ -11,6 +11,7 @@ The programming language was not restricted, but since all example materials wer
...
@@ -11,6 +11,7 @@ The programming language was not restricted, but since all example materials wer
## How to Use
## How to Use
The compiled versions of `init` and `scheduler` are included in this project. After cloning the repository, set the necessary permissions to run them using: `chmod u+x init scheduler`.
The compiled versions of `init` and `scheduler` are included in this project. After cloning the repository, set the necessary permissions to run them using: `chmod u+x init scheduler`.
To run the project:
To run the project:
- run `scheduler` with the following command: `./scheduler`.
- run `scheduler` with the following command: `./scheduler`.
- open a seperate terminal window and run `init` with four numbers like so `./init 1 3 5 7`.
- open a seperate terminal window and run `init` with four numbers like so `./init 1 3 5 7`.
