Releases: getsentry/gocd-jsonnet
v3.0.5
What's Changed
- feat(pipedream): allow rollback final_pipeline override by @joseph-sentry in #99
Full Changelog: v3.0.4...v3.0.5
v3.0.4
v3.0.3
fix(pipedream): no-op gate when SENTRY_REGION is unset
Jobs that didn't set their own SENTRY_REGION (e.g. global CI-check jobs that just hit GitHub) were tripping set -u on line 2 of the gate, before the actual script ran. The gate referenced ${SENTRY_REGION} without a default. Adds ${SENTRY_REGION:-} and an extra guard so the gate is a no-op when the region is unset rather than crashing.
Full changelog: v3.0.2...v3.0.3
v3.0.2
fix(pipedream): skip auto-suffix for single-region groups
When a group has only one region, pipedream now leaves job names alone instead of appending the region. v3.0.1's endsWith check covered the snuba/getsentry shape (jobs already keyed by region), but it didn't catch single-region groups whose libsonnet expands the one region into multiple cells with cell-keyed names (uptime-checker-k8s, vector-uc-k8s) — those broke with diff-us-east-sc becoming diff-us-east-sc-us and breaking downstream fetches.
Multi-region groups (the st shape) are unchanged. Single-region groups whose pipeline_fn produced a bare job name will now see that name un-suffixed (e.g. deploy-de -> deploy in deploy-foo-de); confirmed no v3 service in production references those post-aggregation names externally.
Full changelog: v3.0.1...v3.0.2
v3.0.1
What's Changed
- fix(pipedream): don't double-suffix region in already-suffixed job names by @mchen-sentry in #94: skip the region suffix when a job name already ends with
-{region}. Fixes GoCD validation failures on every k8s pipeline that usesops/k8s.libsonnethelpers (e.g.'diff-' + region) once it bumps to v3, where transform_stage was producing names likediff-customer-1-customer-1and breaking sibling fetch tasks.
Full Changelog: v3.0.0...v3.0.1
v3.0.0
This is a major release of gocd-jsonnet that adds region grouping to the pipedream library to support Sentry's cellularization effort. It's intended to be backwards compatible at the service-template level. This release also includes the replacement of s4s with s4s2.
What's Changed
- chore: pin GitHub Actions to full-length commit SHAs by @joshuarli in #90: pins workflow actions to commit SHAs (with version comments) so dependabot can manage upgrades safely.
- ref: remove s4s region by @dmajere in #91: drops the unused
s4stest region fromprod_regions. - ref(pipedream): group regions into parallel jobs per pipeline by @mchen-sentry in #92: cellularization. Pipedream now generates one pipeline per group instead of one per region; single-tenant customer regions (
customer-1/2/4/7) collapse into a singledeploy-{service}-stpipeline with parallel jobs per customer. Other groups (s4s2,de,us,control,prod-control,snty-tools) stay one-region-per-pipeline. Servicepipeline_fn(region)contract is unchanged. Also adds thePIPEDREAM_GROUP_REGIONSenv var on every group pipeline; override it on GoCD's "Trigger with options" Environment Variables tab to deploy to a subset of regions (e.g. justcustomer-1). Adds build-time assertions for stage-property and pipeline-attribute consistency across regions in a group, and a single-key stage assertion to catch missing-comma-in-jsonnet bugs. - ref(control): Create fake region for control in us by @dmajere in #93: adds a new
prod-controlregion (default-excluded, likecontrolandsnty-tools).
New Contributors
- @joshuarli made their first contribution in #90
- @dmajere made their first contribution in #91
Full Changelog: v2.19.0...v3.0.0
v3.0.0-rc.2
- s4s region removed
v3.0.0-rc.1
Pre-release for Pipedream cellularization (grouped pipedream).
Changes:
- Regions within a group now run as parallel jobs within a single pipeline
- Groups are chained sequentially (or fan out in parallel mode)
- Env var optimization: shared vars stay at stage level, region-specific cascade to jobs
- s4s group aligned to
['s4s2']only - Added rollback-final-stage-override test fixture
- All golden files regenerated
Breaking: Pipeline names change from deploy-{service}-{region} to deploy-{service}-{group}.
v2.19.0
What's Changed
- fix: disable unnecessary fetch_materials option for pipeline-complete branches by @mchen-sentry in #89: Disables the default (unnecessary) option of
fetch_materialsin thepipeline-completestage that was blocking deploys from completing; this should be a very marginal speedup for all pipelines.
Full Changelog: v2.18.0...v2.19.0