GitHub Actions

The automatic evaluation of your submissions uses GitHub Actions. It is a CI/CD and workflow automation platform that enables us to execute and test your code in a virtual environment.

The evaluation will give you feedback on your pull request. In case you need more information or want to see the application logs, navigate to your GitHub repository in a web browser and click Actions.

The interface will list so-called Workflows. Every execution will be a new item in this list (thus, it also gives you access to past executions and their logs).

Selecting one of these (e.g., the topmost is always the last one) gives you the details. To get the logs, you need to click one more on the left, and then the logs will be on the right.

Every green checkmark is a successful step in the process. These steps do not correspond to your exercises; these are the evaluation process steps, such as the initialization of the environment.

Generally, each task shall succeed, even if there are errors in your submission. These errors should be expected and handled by the process. There is only one exception to this rule: if neptun.txt is missing, the evaluation will not proceed if this file is not correct.

There can be transient errors, though, such as a temporary network or git error. In such a case, you can re-run the evaluation. Naturally, re-running will only resolve transient errors. You can deduce the nature of the problem from the step name and the log itself.

You can also look at the execution log of the evaluation. This will provide you with the ETL execution log in the case of Microsoft SQL Server Integration Services. In other cases, the logs can be different.