Skip to content

doco-cd

v0.87.0 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 24d Deployment Automation
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ci-cd devops docker docker-swarm doco-cd gitops
+2 more
swarm-mode webhook

Summary

AI summary

Fixed bug causing jobs to always use UTC timezone instead of the configured local/set timezone.

Full changelog

What's Changed

Fixed a bug that caused jobs to always be scheduled with UTC timezone instead of the local/set timezone.

This release also adds two new API endpoints to list and trigger scheduled jobs (introduced in v0.86.0), see also the REST API documentation.

| Endpoint | Method | Description | Query Parameters |
|-----------------------------|--------|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| /v1/api/jobs | GET | List all discovered scheduled jobs. | - stack (string, optional): Return scheduled jobs only for one stack/project. |
| /v1/api/job/{jobName}/run | POST | Trigger a configured scheduled job immediately. | - stack (string, optional): Limit matching to a specific stack/project.
- wait (boolean, default: true): Wait for the triggered run to finish before responding. |

What is the jobName for a scheduled job?
jobName is the runtime name of the scheduled target:

  • Docker (standalone): the container name (for example my-stack-backup-1)
  • Docker Swarm: the service name (for example my-stack_backup)

How do I find the jobName for a scheduled job?
You can get the jobName from the scheduler logs ("job":"...") or from GET /v1/api/jobs.

  • If multiple jobs share the same jobName, provide stack to disambiguate for the run endpoint.
  • If the matched job is disabled, the run endpoint returns a conflict response.

Common run endpoint outcomes

  • 200 OK: run triggered and completed (wait=true).
  • 202 Accepted: run accepted and running in background (wait=false).
  • 404 Not Found: no scheduled job matched jobName (and optional stack).
  • 409 Conflict: matched job is disabled or the selection is ambiguous.

Example Request

Trigger a job by container name
curl --request POST \
  --url 'https://cd.example.com/v1/api/job/my-stack-backup-1/run?wait=true' \
  --header 'x-api-key: your-api-key'
Trigger a job by service name in a specific stack
curl --request POST \
  --url 'https://cd.example.com/v1/api/job/backup/run?stack=my-stack&wait=true' \
  --header 'x-api-key: your-api-key'
List all scheduled jobs for a specific stack
curl --request GET \
  --url 'https://cd.example.com/v1/api/jobs?stack=my-stack' \
  --header 'x-api-key: your-api-key'

✨ Features

  • feat(api): add API endpoints for managing scheduled jobs by @kimdre in https://github.com/kimdre/doco-cd/pull/1329

Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.86.0...v0.87.0

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track doco-cd

Get notified when new releases ship.

Sign up free

About doco-cd

Docker Compose Continuous Deployment

All releases →

Related context

Earlier breaking changes

  • v0.89.0 Deployment now requires a .doco-cd.yml config file.

Beta — feedback welcome: [email protected]