* build: Update master for v19
Update the version in `master` to v19 now that the v18 branch has been
cut. This will cause all dev builds to be built with v19.0.0-dev version
prefix and use a teleport19 buildbox. The buildbox has been manually
built prior to this commit being merged to master.
Run `make update-version` to propagate the new version to required
files.
Remove no-longer-necessary steps in the preflight.md docs.
* fix: allow tests to use old client versions
---------
Co-authored-by: Tim Ross <tim.ross@goteleport.com>
* ci: Add preflight step for bumping use of buildbox in CI
Update the preflight docs for cutting a new release branch to bump the
version of the buildboxes on master. We keep forgetting to do this,
probably because it is not documented.
* ci: Update CI buildbox to teleport18
Update the buildbox used by the various CI jobs to `:teleport18` from
`:teleport17`. This should have been done when `branch/v17` was created,
but got missed.
The `unit-test-*` have been left out as there seems to be an issue with
some workflow runs erroring out with "The request could not be processed
because too many files changed". I'll raise a second PR for those.
Update the preflight docs to provide instructions for building the
buildboxes for the new version that master becomes. The buildboxes build
on a schedule and that can mean up to a week will need to pass before
the buildboxes are automatically built, given that the assets buildbox
is build only once a week (Sundays) and that is needed to build the
centos7 buildboxes. The updated instructions describe how to kick off
that build automatically.
Update the preflight and postrelease docs for starting a new release
branch and after publishing that release for the first time to update
the GitHub Action the scheduled building of the buildboxes.
Remove `.drone.yml` and `dronegen` which generates it from the repo,
disabling drone on master. Remove references to drone in docs.
The remaining piplines in `.drone.yml` were the tag build and promote
pipelines which now run on GitHub Actions, the push build pipelines that
are currently of limited value and will be re-done differently with a
little thought, and the `teleport-docker-cron-ecr` pipeline which no
longer works as of v15 due to the removal of the legacy OCI images (the
teleport-labs stuff that the pipeline builds is to be removed shortly
too).
From `docs/postrelease.md`:
- [x] Update `branchMajorVersion` const in Dronegen `/dronegen/container_images.go`, then run `make dronegen`
- [x] Update `CURRENT_VERSION_ROOT`, `PREVIOUS_VERSION_ONE_ROOT`, and `PREVIOUS_VERSION_TWO_ROOT` variables in `.drone.yml`, then run `make dronegen`
- Example: https://github.com/gravitational/teleport/pull/4602
- [x] Create PR to update default Teleport image referenced in docker/teleport-quickstart.yml
- Example: https://github.com/gravitational/teleport/pull/4655
- [x] Create PR to update default Teleport image referenced in docker/teleport-lab.yml
* Remove CodeQL Scanning for release branches
In RFD 114 (PR #32233) we setup mirroring for the Teleport release branches to the `teleport-sec-scan` repos. There are several advantages to moving the CodeQL scanning to these repos:
* It removes the manual process described in `preflight` to update the codeql scanning branch
* It solves the issue of alerts being repeatedly opened and closed as they are found on release branches and only fixed in master, for example: https://github.com/gravitational/teleport/security/code-scanning/560
As such CodeQL has already been configured on these repos and the initial findings triaged: https://github.com/gravitational/teleport-sec-scan-1/blob/master/.github/workflows/codeql-mirror.yml
* codeql: Comment relaese branch scanning
