All articles
Getting Started
What is CICDoo Getting started: the onboarding wizard The Dashboard and Infrastructure MapConcepts
Production, staging and development stages Domains, subdomains and SSL Odoo versions and editions (Community vs Enterprise) Workspaces and team collaborationServers
Adding a server Server domains and DNS Using a load balancer Server actions: deploy, logs and chartsProjects & Git
Creating a project Connecting GitHub Connecting GitLab Branches and instancesInstances & Console
Creating an instance Restarting, stopping and removing an instance Merging branches between stages Web IDE and remote access Instance settings explained Deployments and the job queueAgent Tasks
What agent tasks are Setting up agent tasks Running a task and reviewing the result Agent time and top-upsMonitoring & Backups
Monitoring your instance Backups and restore Alert notifications (email and SMS)Workspaces & Permissions
Inviting workspace members Member permissions and resource access A member cannot see or use a resourceAccount & Security
Two-factor authentication (2FA) Profile and integrations settings Passwords and account recoveryBilling & Plans
Plans and pricing Upgrading and managing your subscription If a project subscription goes unpaid The channel partner programSupport & Tickets
Opening a support ticket Getting help from the CICDoo teamTroubleshooting
Troubleshooting: cannot connect a server Troubleshooting: a deployment failed Troubleshooting: git push fails with 403 after moving a repository Troubleshooting: my instance is down or slow Troubleshooting: domain or SSL problemsInstances & 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
- Restart types are explained in Restarting, stopping and removing an instance.
- Merge jobs are covered in Merging branches between stages.
- Backup and restore jobs are covered in Backups and restore.
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.