jenkinsOdooCICD — Project Overview

Automated Odoo module deployment + Jenkins pipeline monitoring. Pulls modules from git, deploys to Odoo, restarts services, validates results and emails on errors.

Quick Links

th

Replace placeholders with your real URLs

Open Jenkins Dashboard

Open Odoo App

Contact

Emails will be sent from the CI runner to configured recipients on failures.

Pipeline Features

  • Auto pull custom Odoo modules from git and install/update in Odoo.
  • Restart Odoo service (systemd / docker / k8s) after deployment.
  • Run validation checks and smoke tests; on failure, send detailed email with logs.
  • Stateful monitoring of multiple websites (port-aware and portless checks).
  • Jenkins job status, build history link, and one-click access to failed logs.

Project

Name: jenkinsOdooCICD
Repo: your-git-repo
Last pipeline:
Status: unknown

Monitored Sites & Modules

This table shows each monitored site (domain or IP), whether it uses a port check, status, last change and a quick action link.

SitePort-awareStatusLast changedActions
odoo.theamandairy.shop Yes (8069) UP 2025-11-06 09:40 Open
theamandairy.shop No DOWN 2025-11-06 08:55 Investigate

Custom Odoo Modules (example)

  • website_multi_monitor — monitors multiple websites & ports and reports state changes.
  • odoo_auto_deploy — git pull → install/update module → run migrations → restart service.
  • ci_notify — formats pipeline logs and sends templated emails on failure.

Email Notification

On failure, pipeline sends an email with subject, summary and an attachment (log snippet).

Subject: [jenkinsOdooCICD] Build #23 FAILED - Module: odoo_auto_deploy
To: ops@example.com

Summary:
- Git: repo/branch
- Module: odoo_auto_deploy
- Step: install
- Error: Traceback (most recent call last)...

Logs (tail):
...error stack...

Jenkins Dashboard & App

If your Jenkins instance allows embedding, insert its URL below. Otherwise link directly to it.

Note: some servers block iframe embedding (X-Frame-Options). If the frame is blank, click the Quick Links above.

Monitoring Behavior & Actions

  1. CI pulls modules -> runs install scripts -> runs smoke tests (health endpoint, db checks).
  2. If a smoke test fails: mark build as FAILED, attach logs, and send notification email with actionable steps and link to failed build.
  3. Monitor agent (script or k8s sidecar) pings sites. On state change (UP→DOWN or DOWN→UP), create event and send digest email (configurable frequency).
  4. Optional: auto-rollback on failures or open a Jira/ticket with diagnostics.