All articles

Getting Started

What is CICDoo Getting started: the onboarding wizard The Dashboard and Infrastructure Map

Concepts

Production, staging and development stages Domains, subdomains and SSL Odoo versions and editions (Community vs Enterprise) Workspaces and team collaboration

Servers

Adding a server Server domains and DNS Using a load balancer Server actions: deploy, logs and charts Deleting a server

Projects & Git

Creating a project Connecting GitHub Project GitHub settings and webhook Connecting GitLab Branches and instances Tagging and filtering projects High availability with app nodes Project environments, extensions and deletion

Instances & Console

Creating an instance Restarting, stopping and removing an instance Merging branches between stages Web IDE and remote access SSH access to instances Instance settings explained Deployments and the job queue

Agent Tasks

What agent tasks are Setting up agent tasks Running a task and reviewing the result Agent time and top-ups Agent insights and task filters

Monitoring & Backups

Monitoring your instance Backups and restore S3 storage, uploads and bulk backup actions Alert notifications (email and SMS)

Workspaces & Permissions

Inviting workspace members Member permissions and resource access A member cannot see or use a resource Audit log and server activity

Account & Security

Two-factor authentication (2FA) Profile and integrations settings Passwords and account recovery

Billing & Plans

Plans and pricing Upgrading and managing your subscription If a project subscription goes unpaid The channel partner program Onboarding a client as a partner

Support & Tickets

Opening a support ticket Getting help from the CICDoo team

Troubleshooting

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 problems

Instances & Console

Deployments and the job queue

How CICDoo runs deployments and other actions as queued jobs, the job types and statuses, and how to find, filter and read a job's live 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 (through your project's webhook), and the actions you trigger from the Console, such as a restart, a backup or a merge, are queued the same way. Each job has a status and a log you can read.

Only one action runs per instance at a time. While a job is pending or running, new actions on that instance are refused with a message until it finishes. Reconfigure jobs are the exception: they never block other actions.

Job types

  • Deploy: builds and deploys the instance, for example after a code push or when the instance is first created.
  • Upgrade: a Soft Restart, which restarts Odoo and upgrades modules.
  • Restart: a Hard Restart, which restarts the Docker container.
  • Reconfigure: applies saved Security or Nginx settings to the web server in a few seconds, without restarting the containers. It is queued automatically when you save those settings.
  • Backup and Restore: instance backups and restores.
  • Merge: a branch merge between stages.
  • Stop: stops the instance.
  • Remove: tears the instance down.

Job statuses

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

Checking jobs for one instance

  1. Open the instance in the Console.
  2. Click the Queue tab. The "Recent Jobs" list shows each job's type, status, who started it ("by" a user, or "by cicdoo" for automatic jobs) and how long ago it was created.
  3. Click View log on a job to read its output.

The list refreshes on its own every few seconds while the tab is open. Click Refresh to reload it immediately.

Checking jobs across all instances

  1. Click Queue in the main sidebar.
  2. Read the table: "Server", "Instance" (repository and branch), "Type", "Status", "By" and "Created".
  3. Click the instance name to jump to its console, or click Logs in the "Actions" column to read the job log.

Filtering the Queue page

  1. On the Queue page, click Filters.
  2. In the "Filter queue" dialog, choose any of:
    • Project: only jobs for one project.
    • Instance: only jobs for one instance.
    • Tags: only jobs on projects carrying any of the chosen tags.
  3. Click Apply. Reset clears the choices in the dialog and Cancel closes it without changes.

The number of active filters shows on the Filters button, and each filter appears as a chip under it. Click the x on a chip to remove that filter, or Clear all to remove them all. If nothing matches, the page shows "No jobs match these filters". For tags, see Tagging and filtering projects.

Reading a job log

  1. Click View log (Queue tab) or Logs (Queue page) on a job.
  2. The "Job Log" dialog opens with the job's status badge and full output.
  3. While the job is still pending or running, a Live indicator shows and the log refreshes every few seconds, so you can watch a deployment as it happens. The view keeps scrolling to the newest lines unless you scroll up.
  4. Click Close when done.

If a job failed, the log or its error message explains why. "No log available" means the job has not written any output yet.

Related: Restarting, stopping and removing an instance, Merging branches between stages, Backups and restore, Troubleshooting: a deployment failed.

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

Previous Instance settings explained Next What is CICDoo

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