|
|
Build engines take source code submitted by entrants and compile it into a build artefact to be used in the competition. At present, most build engines are competition specific but in future, we aim to have some basic engines for common programming languages and build systems.
|
|
|
|
|
|
## Recommended steps
|
|
|
|
|
|
1. Query the API for new submissions to your track: eg, if the PK of your track is 1: `https://comp.fossgalaxy.com/api/track/1`
|
|
|
2. Find any submission with the status `BP` (build pending)
|
|
|
3. Download the upload referenced by `current_upload` from Comet
|
|
|
4. Run your build pipeline, storing any logs which you would like the entrant to have access to.
|
|
|
5. send a `HTTP PATCH` to https://comp.fossgalaxy.com/api/upload/5 (where 5 is the PK field of the `current_upload`) with the new `status` and `feedback` attributes set.
|
|
|
|
|
|
## Build Engines
|
|
|
Here is a list of public build engines:
|
|
|
|
|
|
### fireworks-builder
|
|
|
The fireworks build engine and evaluation server is Free Software and available on our [Gitlab server](https://git.fossgalaxy.com/hanabi/build-engine). It will compile submissions which use Maven as their build tool. At present, the fireworks builder does not have a validation step implemented. |