GH Actions + Buildkite release - #3137
Conversation
|
👋 @reakaleek Thanks a lot for your contribution! It may take some time before we review a PR, so even if you don’t see activity for some time, it does not mean that we have forgotten about it. Every once in a while we go through a process of prioritization, after which we are focussing on the tasks that were planned for the upcoming milestone. The prioritization status is typically reflected through the PR labels. It could be pending triage, a candidate for a future milestone, or have a target milestone set to it. |
33be408 to
a496660
Compare
a496660 to
95d27d9
Compare
Co-authored-by: Jonas Kunz <Jonas.Kunz@gmx.net>
This will be migrated to a updatecli job
ea674fb to
ffb0d16
Compare
|
FYI, while renaming the Does anyone know if they are used somewhere else? Is it safe to delete them? @elastic/observablt-ci @elastic/apm-agent-java |
| java .ci/ReleaseChangelog.java CHANGELOG.asciidoc ${{ inputs.version }} | ||
| git commit -m "Prepare changelog for release ${{ inputs.version }}" CHANGELOG.asciidoc | ||
| - name: Bump version and add git tag | ||
| run: ./mvnw release:prepare -B -DpushChanges=false "-Darguments=-DskipTests -Dmaven.javadoc.skip=true" -DreleaseVersion=${{ inputs.version }} |
There was a problem hiding this comment.
Commits to the main branch will not be allowed with the new changes in permissions, Would this code work?
There was a problem hiding this comment.
I assume it works because the job has
permissions:
contents: write
There was a problem hiding this comment.
So far the setup has been that the apmmachine-user has the permissions to directly push to the main branch. We implemented this by making apmmachine an admin, while we (the devs) do not have admin permissions.
Will this not work anymore with the permission changes?
There was a problem hiding this comment.
It should work, in the github workflow it's the github-action user who will do it and that bot user adheres to the set permissions in the workflow.
There was a problem hiding this comment.
On the APM Agent Android, the service account does not have permission to push the main branch. I assume all service accounts will have the same permissions at some point.
cc @cachedout
There was a problem hiding this comment.
I've been digging through SLSA requirements this morning and so far I haven't found any explicit provision which says that machine accounts can't commit code. So long as it's a part of a workflow that is initiated by a human, I think this should be OK.
Co-authored-by: Adrien Mannocci <adrien.mannocci@gmail.com>
| provider: "gcp" | ||
|
|
||
| steps: | ||
| - label: "Run the snapshot" |
There was a problem hiding this comment.
Run the snapshot - is this a copy-paste leftover?
What does this PR do?
Migrating release pipelines to GH Actions + Buildkite
Based on #3026