Instances & Console

Deployments and the job queue

How CICDoo runs deployments and other actions as queued jobs, and how to check a job's status and log.

How work gets done in CICDoo

Every action on an instance runs as a job in a queue: deployments start automatically when you push code to the instance's branch, and actions you trigger from the Console (restart, backup, merge, and so on) are queued the same way. Each job has a status and a log you can read.

Job types

You will see these job types:

  • Deploy: builds and deploys the instance after a code push.
  • Upgrade: a Soft Restart, restarts Odoo and upgrades modules.
  • Restart: a Hard Restart of the Docker container.
  • Backup and Restore: instance backups and restores.
  • Merge: a branch merge between stages.
  • Stop: stops the instance.
  • Remove: deletes the instance.

Job statuses

  • Pending: waiting to start.
  • Processing (In Progress): being prepared.
  • Running: launched and executing on the server.
  • Completed: finished successfully.
  • Failed: something went wrong; the log tells you why.

The Queue tab in the instance console

Open an instance and click the Queue tab. It lists the recent jobs for that instance with type, status, who initiated it (your user, a teammate, or cicdoo for automatic jobs), and when it was created. The list refreshes automatically, and there is a Refresh link if you want to reload it manually.

The Queue page

The sidebar also has a Queue page that shows jobs across all your instances in one table: server, instance (repository and branch), type, status, initiated by, and creation time. Click the instance link to jump to its console.

Viewing a job log

Click View log (Queue tab) or Logs (Queue page) on any job. A dialog opens with the full job output. While a job is still active, the log shows a Live indicator and refreshes every few seconds, so you can watch a deployment as it runs. If a job failed, the log or its error message is shown in the same dialog.

Related articles

If you get stuck, open a support ticket from the Tickets page or the chat widget.

Still stuck? Open a ticket from the app or talk to an engineer.