Using the skip-{XYZ}-deploy labels to control code deployment
When creating a PR, you're asked to add labels to it. Each label that you add tells our deployment pipeline not to re-deploy some part of our infrastructure. This is useful when you know your code doesn't change a part of the infra — don't deploy there.
There are a few skip-labels, so this page contains more detail on the type of pods affected by each skip-{type}-deploy label.
See the deployment code here
skip-web-deploy
Using this label will skip the update of cl-python pods. These contain the whole Django app that responds user's requests through the web, including API requests.
skip-celery-deploy
This label skips celery deployment, and skips the following pods:
- celery-default
- celery-feeds
- celery-batch0
- celery-batch1
- celery-batch2
- celery-batch3
- celery-etl
- celery-iquery
- celery-free-pacer-docs
- celery-inception
- celery-es-sweep
- celery-recap-fetch
skip-daemon-deploy
Daemon pods will be skipped. Among them, the following pods will not be updated:
- cl-scrape-rss
- cl-retry-webhooks
- cl-send-rt-percolator-alerts
- cl-es-sweep-indexer
- cl-iquery-probe
skip-cronjob-deploy
k8s cronjobs will not be updated. Among them:
- alert-dly
- alert-dly-es
- alert-mly
- alert-mly-es
- alert-recap
- alert-rt
- alert-wly
- alert-wly-es
- delete-stale-data
- handle-failing-email
- handle-old-docket-alerts
- make-bulk-data
- manage-accounts-notify-old
- monitor-replication-lag
- monthly-bulk-export
- scrape-free-opinions
- scrape-iquery
- scrape-opinions
- scrape-oral-arguments
- send-events-email
- task-welcome-new-users
- update-scraper-material-view
- upload-to-internet-archive
mike