* Update active version list in .release/versions.hcl
* Remove nightly tests for 1.17.x
* Add nightly tests for 1.20.x
* Gate nightly tests for 1.19.x to Enterprise only
* Update CHANGELOG.md
ci: fix conditional skip and add safeguard
Adopt a third-party action to avoid script bugs, and to fix a current
issue where the script fails to detect all changes when processing push
events on PR branches.
Adapted from hashicorp/consul-dataplane#637. See that PR for testing
details and background context.
* Update test-integrations.yml
Update Vault/Nomad versions to ensure we're testing the latest versions .
* Update test to test latest available CE versions
* init release branch
* init 1.20 nightly tests
* drop 1.17 nightly tests for new release cycle
* drop 1.17 from test matrix
* Update nightly-test-integrations-1.20.x.yml
In some environments, the script will not fail despite SKIP_CHECK_BRANCH
being unset, leading to the script explicitly skipping CI when it should
fail fast.
Prevent this by explicitly checking for the env var.
Correctly set the the version of Consul built by the `dev-build` job,
which is then copied into the Consul dev image used in integration
tests.
This was causing failures starting sidecar proxies via `consul connect
envoy` due to a mismatch between the (incorrect) Consul binary's
supported Envoy versions and the (correct) Envoy version under test.
Also add debug log uploads to each int test so we can more easily
diagnose this sort of failure in the future, as it was entirely hidden
in test output.
* run integration tests on push in main and release/*
* Update .github/workflows/test-integrations.yml
Co-authored-by: Michael Zalimeni <michael.zalimeni@hashicorp.com>
---------
Co-authored-by: Michael Zalimeni <michael.zalimeni@hashicorp.com>
* Add checks to CI to ensure that generated golden files for xds tests are up to date
* fix file permissions
* debugging
* more debugging
* more debugging
* more debugging
* more debugging
* I can't type
* this might be correct
* removing debug prints
* build: consolidate Envoy version management
Simplify Envoy version management by consolidating all runtime, build,
and CI sources of Envoy versions into a single plaintext file.
The goal of this change is to avoid common mistakes missing an update of
some Envoy versions (both in general and due to release branch
inconsistency), and enable automated Envoy version updates in the
future.
* ci: add missing ref argument for get-go-version
Supports nightly tests.
Ensure files are split rather than compared as a single list for
accuracy and easier debugging.
Also adopt minor changes and file name from introduction of similar
check `consul-dataplane` and `consul-k8s` for clarity.
Several of our nightly cron jobs are actually running repeatedly
back-to-back during the designated hour. Change the cron to run them
once as intended.
Follow-up to #21094, which temporarily downgraded BPA to allow for old
CE backport labels to be used during Consul's most recent patch release.
Upgrading fully enforces the version manifest and prevents accidental
backports to no-longer-active CE versions.
To ease migration during this week's patch releases, temporarily use the
more permissive version of BPA to allow old + new backport labels to be
used simultaneously.
* Config changes to use backport-assistant with lts support
Co-authored-by: Michael Zalimeni <michael.zalimeni@hashicorp.com>
---------
Co-authored-by: claire labry <claire@hashicorp.com>
Co-authored-by: Michael Zalimeni <michael.zalimeni@hashicorp.com>
This adds a bunch of coverage of the topology.Compile method. It is not complete, but it is a start.
- A few panics and miscellany were fixed.
- The testing/deployer tests are now also run in CI.
sarahalsmiller
Nathan Coleman
Michael Zalimeni
NicoletaPopoviciu
Deniz Onur Duzgun
John Murret
John Maguire
Dan Stough
Jeanne Angeles Franco
wangxinyi7
R.B. Boyer