v1.3 is now released. This is a relatively small release compared to the last one. v1.3 introduces pinnable builds, whereby any build that is pinned will not have its artifacts deleted, even if they exceed the configured artifact limit on your account, useful if you want to mark a build as a release build.
The Djinn CI Blog
Djinn CI makes working with multiple repositories
in a build simple via the sources
parameter in the build manifest. This allows you to specify multiple Git
respositories to clone into your build environment. Each source would be a URL
that could be cloned via
git clone. With most CI platforms, a build's manifest
is typically tied to the source code repository itself. With Djinn CI, whilst
you can have a build manifest in a source code repository, the CI server itself
doesn't really have an understanding of that repository. Instead, it simply
looks at the sources in the manifest that is specified, and clones each of them
into the build environment.
Perhaps the one feature that sets Djinn CI out from other CI platforms is the fact that is has an offline runner. The offline runner allows for CI builds to be run without having to send them to the server. There are some limitations around this, of course, but it provides a useful mechanism for sanity checking build manifests, testing custom images, and for building software without the need for a CI server.
v1.2 has now been released. The major feature for this release is variable masking, whereby you can now have variables masked in build logs. Another feature is configurable artifact limits on a per user basis.
It's been relatively quiet here for some time since the first post was published announcing the initial launch of Djinn CI. Since then, work has been underway to expand the tests, fix bugs, and introduce new features. So, let's take a look at what is available with v1.1 of Djinn CI.
Djinn CI is a continuous integration platform, built with simplicity and flexibility in mind. It has been in development for some time, and has reached a stage where it is now ready to be debuted. Builds in Djinn CI are simple YAML manifest files. These can be either manually through the UI, via a push to a repository, or when a pull request is opened, or if you prefer you can have your builds run at a schedule.