Job Management
Artifakt allows you to easily run jobs in your environments.
Once your environment is created and available online, you will be able to build your application and deliver your latest developments, bug fixes, new features or other improvements.
When creating an environment, you can define a specific branch to deploy from the Git repository associated with the project. Then, each time you run a Build & Deploy job, your application will be built using the last commit associated with that branch. You can change this at any time from Environment → Settings → General → Branch selection.
To trigger a new build go to Environment → Jobs and run the Build and Deploy job.
Please be aware that building jobs have a hard limit on storage, and the result Docker image cannot exceed 10GB. If you think you will need more storage per build, please contact our support team.
Sometimes you only need to change a few environment variables and redeploy your application. This is what the Deploy job is for.
To trigger a new deploy go to Environment → Jobs and run the Deploy job.
Deploy job is a destructive action, with potential data loss. If you need to keep files between deploys, we recommend storing them in a persistent folder such as /data
This ensures clean separation between code and data. As a consequence, anything written in non-persistent folders since last deployment is removed and replaced by latest build.
When maintenance is activated, a specific maintenance container will be started and all traffic will be redirected from the application container to the maintenance container. Conversely, when maintenance is deactivated, all traffic will be redirected from the maintenance container to the application container.
When maintenance is activated, a generic Artifakt maintenance page is displayed. For the moment, this page cannot be modified or customized.