Once logged in click the Submit button on the homepage. From here you will be able to submit your first build to Djinn CI.
Build's in Djinn CI are described using YAML manifests. These manifests describe how the build is executed, from the driver to use, the jobs to run, and the artifacts to collector. So let's write a simple manifest to demonstrate this,
driver: type: qemu image: debian/stable stages: - os jobs: - stage: os commands: - cat /etc/os-release artifacts: - /etc/os-release
From this same page we can also add a comment to the build, and some tags to help search for it later on. Tags are simple a comma separated list of strings.
Submitting the manifest will redirect you to the newly submitted build. From here you will be able to see the status of the build as it's processed by Djinn CI.
Once the build has finished processing its status will be updated to reflect so. If successful the build will be marked as
passed. From the "Artifacts" tab of the build page you will be able to see the
/etc/os-release artifact we collected from the build.
Now that we've submitted a simple build manifest let's submit another one, only this time let's actually build some source code, and collect the artifacts from it.
driver: type: qemu image: debian/stable sources: - https://github.com/andrewpillar/mdsrv stages: - packages - make jobs: - stage: packages commands: - apt install -y golang - stage: make commands: - cd mdsrv - ./make.sh artifacts: - mdsrv/bin/mdsrv
The above manifest will download the source for mdsrv build it, and collect the built binary.