Loading
Commits on Source 26
-
GitLab Renovate Bot authored
-
Matias Alvarez authored
-
Luke Hollinda authored
fix: Remove wrongly deprecated field See merge request !468 Merged-by:
Luke Hollinda <lhollinda@gitlab.com> Approved-by:
Luke Hollinda <lhollinda@gitlab.com> Co-authored-by:
Matias Alvarez <malvarez@gitlab.com>
-
Luke Hollinda authored
Adds a release-v1 and release-v2 job to run our release script automatically on changes to master. After this is validated in CI we can remove `--dry-run` and start creating tags and releases without human interaction.
-
Luke Hollinda authored
Per docs, the Release API accepts: - A personal access token using the PRIVATE-TOKEN header. - The GitLab CI/CD job token $CI_JOB_TOKEN using the JOB-TOKEN header. This commit adjusts the release script to use the appropriate authentication header.
-
Luke Hollinda authored
This commit removes the dry run flag from the release script jobs. After this is merged, we should be automatically filtering commits to master, creating tags and Gitlab releases when appropriate.
-
Matias Alvarez authored
ci: set up automatic release jobs in dry-run mode See merge request !470 Merged-by:
Matias Alvarez <malvarez@gitlab.com> Approved-by:
Matias Alvarez <malvarez@gitlab.com> Reviewed-by:
Matias Alvarez <malvarez@gitlab.com> Co-authored-by:
Luke Hollinda <lhollinda@gitlab.com>
-
Elliot Forbes authored
-
Elliot Forbes authored
Co-Authored-By:Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
-
Elliot Forbes authored
Co-Authored-By:Claude Sonnet 4.6 <noreply@anthropic.com>
-
Elliot Forbes authored
Avoids ambiguity with the log record's own timestamp field. Co-Authored-By:Claude Sonnet 4.6 <noreply@anthropic.com>
-
Elliot Forbes authored
feat(v2/app): add build metadata vars with automatic logger enrichment See merge request !472 Merged-by:
Elliot Forbes <eforbes@gitlab.com>
Approved-by: Alessio Caiazza <code.git@caiazza.info> Approved-by:
Peter Leitzen <pleitzen@gitlab.com> Reviewed-by:
GitLab Duo <gitlab-duo@gitlab.com>
-
Matias Alvarez authored
ci: fully enable release jobs See merge request !471 Merged-by:
Matias Alvarez <malvarez@gitlab.com> Approved-by:
Matias Alvarez <malvarez@gitlab.com> Reviewed-by:
GitLab Duo <gitlab-duo@gitlab.com> Co-authored-by:
Luke Hollinda <lhollinda@gitlab.com>
-
Steve Xuereb authored
chore(deps): update pre-commit hook gitlab-com/gl-infra/common-ci-tasks to v4 See merge request !460 Merged-by:
Steve Xuereb <sxuereb@gitlab.com>
Approved-by:
Steve Xuereb <sxuereb@gitlab.com>
Co-authored-by: GitLab Renovate Bot <ops-contact+gl-common-ci-tasks-self-renovate@gitlab.com>
-
Elliot Forbes authored
Co-Authored-By:Claude Sonnet 4.6 <noreply@anthropic.com>
-
Elliot Forbes authored
Co-Authored-By:Claude Sonnet 4.6 <noreply@anthropic.com>
-
Elliot Forbes authored
Co-Authored-By:Claude Sonnet 4.6 <noreply@anthropic.com>
-
Elliot Forbes authored
feat(v2/httpserver): include build info in health responses See merge request !473 Merged-by:
Elliot Forbes <eforbes@gitlab.com>
Approved-by: Alessio Caiazza <code.git@caiazza.info> Approved-by:
Peter Leitzen <pleitzen@gitlab.com>
-
GitLab Renovate Bot authored
-
Luke Hollinda authored
Grabbing the branch name directly leads to this error in CI: Error: current branch is HEAD. Releases should only be created from the 'master' branch. The CI git repo is in a detached state and we need to grab the branch name directly from CI_COMMIT_BRANCH
-
Matias Alvarez authored
ci(release): account for detached git repo in CI See merge request !476 Merged-by:
Matias Alvarez <malvarez@gitlab.com> Approved-by:
Matias Alvarez <malvarez@gitlab.com> Co-authored-by:
Luke Hollinda <lhollinda@gitlab.com>
-
Matias Alvarez authored
fix(deps): update module gitlab.com/gitlab-com/gl-infra/platform/runway/fairway to v1.15.2 See merge request !475 Merged-by:
Matias Alvarez <malvarez@gitlab.com> Approved-by:
Matias Alvarez <malvarez@gitlab.com> Co-authored-by:
GitLab Renovate Bot <ops-contact+gl-common-ci-tasks-self-renovate@gitlab.com>
-
Luke Hollinda authored
We're currently in a position where we incorrectly have `v2/X.X.X` tags. Our major version subdirectory set up requries us to use tags in the form `v2.X.X`. These tags previously existed and were deleted. While recreating these old tags, deleting incorrect formats, and fixing the release script; we should temporarily disable the release process by calling the script in dry-run mode.
-
Luke Hollinda authored
This release script was built out with the incorrect assumption that v2 module tags should be in the form `v2/v2.X.X`. This is incorrect and we should instead be using the format `v2.X.X`
-
Matias Alvarez authored
ci: set release jobs to dry run while fixing release tags See merge request !477 Merged-by:
Matias Alvarez <malvarez@gitlab.com> Approved-by:
Matias Alvarez <malvarez@gitlab.com> Co-authored-by:
Luke Hollinda <lhollinda@gitlab.com>
-
Luke Hollinda authored
ci: release script to use correct v2 tag format See merge request !478 Merged-by:
Luke Hollinda <lhollinda@gitlab.com> Approved-by:
Matias Alvarez <malvarez@gitlab.com>