-
Notifications
You must be signed in to change notification settings - Fork 568
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate CI release pipeline to GHA #10992
Labels
component/build-pipeline
kind/toil
Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc.
version:8.1.6
Marks an issue as being completely or in parts released in 8.1.6
version:8.2.0-alpha4
Marks an issue as being completely or in parts released in 8.2.0-alpha4
version:8.2.0
Marks an issue as being completely or in parts released in 8.2.0
Comments
This was referenced Nov 15, 2022
6 tasks
This was referenced Dec 13, 2022
zeebe-bors-camunda bot
added a commit
that referenced
this issue
Dec 20, 2022
11283: ci(release): nightly release dry run from stable branches r=megglos a=megglos ## Description Adds a nightly dry run referencing the release workflows from stable branches, to ensure they are functional, sends a [slack notification to #zeebe-ci else for the medic to check](https://camunda.slack.com/archives/C013MEVQ4M9/p1671183699739009). The dry run tests relevant inputs being latest:true for the most recent stable branch (8.1) as well as latest:false for previous stable branche(s). With every minor release the stable dry run workflow needs to be updated, release guide/process will get adjusted with a separate sub-task listed in #10992. Manual Tests: - [Run of the scheduled dry run for all stable branches](https://github.com/camunda/zeebe/actions/runs/3739887730) ## Related issues <!-- Which issues are closed by this PR or are related --> closes #11259 Co-authored-by: Meggle (Sebastian Bathke) <sebastian.bathke@camunda.com>
This was referenced Dec 20, 2022
zeebe-bors-camunda bot
added a commit
that referenced
this issue
Dec 21, 2022
11315: ci(release): github hosted runner for docker job r=megglos a=megglos ## Description I experienced some scheduling delays with the pool used for the docker job (the known hiccups that lead to the zeebe-io self-hosted runners and the new *-quick pool provided by infra). As the docker build is not that demanding I figured we can just make use of github hosted runners for it. Dry run: [here](https://github.com/camunda/zeebe/actions/runs/3748237847) ## Related issues <!-- Which issues are closed by this PR or are related --> relates to #10992 Co-authored-by: Meggle (Sebastian Bathke) <sebastian.bathke@camunda.com>
This was referenced Dec 21, 2022
zeebe-bors-camunda bot
added a commit
that referenced
this issue
Jan 20, 2023
11376: ci(jenkins): removal of Jenkins ci and jobs r=megglos a=megglos ## Description Removes all Jenkins related setup except the github repository scan of the zeebe-io org as there are projects that make use of Jenkins still. With the release job being migrated to GHA with #10992 and the 8.2.0-alpha3 as well as 8.0 and 8.1 patches being successfully published, this also removes the deprecated release job on Jenkins. I already seeded the jenkins ci from this branch the outcome is as expected: <img width="281" alt="image" src="https://user-images.githubusercontent.com/209518/211023700-319dd4a4-6424-484a-8455-05a230a2855f.png"> Given the [camunda org job setup is gone](https://github.com/camunda/zeebe/pull/11376/files#diff-0c2b5bccf4a2a4bc264fe1fae76a5b633068e747e59c90aa226c055dd473faba) by Jenkins seeding from main, I see no need for a backport, as Jenkins won't be building zeebe at all anymore. ## Related issues <!-- Which issues are closed by this PR or are related --> closes #9138 Co-authored-by: Meggle (Sebastian Bathke) <sebastian.bathke@camunda.com>
Would remove #11359 from the scope of this and follow-up on it separately. The migration is done and complete, using stable runners to reduce the risk of hiccups is something we indeed should do but is not a must have for the migration per se. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component/build-pipeline
kind/toil
Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc.
version:8.1.6
Marks an issue as being completely or in parts released in 8.1.6
version:8.2.0-alpha4
Marks an issue as being completely or in parts released in 8.2.0-alpha4
version:8.2.0
Marks an issue as being completely or in parts released in 8.2.0
Description
In order to conclude the migration from Jenkins to GHA one job left is the release job.
Breakdown
release-stable-dry-run.yml
workflows needs to get updated to reference the new stable branchAdditional Context:
Follow-ups:
The text was updated successfully, but these errors were encountered: