Skip to content

GH Actions + Buildkite release - #3137

Merged
reakaleek merged 29 commits into
elastic:mainfrom
reakaleek:feature/release
Jun 12, 2023
Merged

GH Actions + Buildkite release#3137
reakaleek merged 29 commits into
elastic:mainfrom
reakaleek:feature/release

Conversation

@reakaleek

@reakaleek reakaleek commented May 8, 2023

Copy link
Copy Markdown
Member

What does this PR do?

Migrating release pipelines to GH Actions + Buildkite

Based on #3026

@github-actions github-actions Bot added agent-java community Issues and PRs created by the community triage labels May 8, 2023
@github-actions

github-actions Bot commented May 8, 2023

Copy link
Copy Markdown

👋 @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.

@reakaleek reakaleek self-assigned this May 8, 2023
Comment thread .github/workflows/release.yml Outdated
Comment thread .github/workflows/release.yml Outdated
Comment thread .github/workflows/release.yml
Comment thread .github/workflows/release.yml Outdated
Comment thread .github/workflows/release.yml Outdated
Comment thread .github/workflows/release.yml Outdated
Comment thread .github/workflows/release.yml Outdated
Comment thread .github/workflows/release.yml Outdated
Comment thread .github/workflows/release.yml Outdated
Comment thread .github/workflows/release.yml Outdated
@ghost

ghost commented May 15, 2023

Copy link
Copy Markdown

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview previewSnapshots

Expand to view the summary

Build stats

  • Start Time: 2023-06-12T11:45:29.835+0000

  • Duration: 13 min 7 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • run benchmark tests : Run the benchmark tests.

  • run jdk compatibility tests : Run the JDK Compatibility tests.

  • run integration tests : Run the Agent Integration tests.

  • run end-to-end tests : Run the APM-ITs.

  • run windows tests : Build & tests on windows.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Comment thread .github/workflows/release.yml Outdated
reakaleek and others added 4 commits May 31, 2023 15:13
Co-authored-by: Jonas Kunz <Jonas.Kunz@gmx.net>
This will be migrated to a updatecli job
@mergify mergify Bot mentioned this pull request May 31, 2023
Comment thread .github/workflows/release.yml Outdated
@reakaleek

reakaleek commented Jun 5, 2023

Copy link
Copy Markdown
Member Author

FYI, while renaming the scripts/jenkins folder to scripts/docker-release, I noticed that I was not able to find any usages of check_maven.sh andfetch_nexus_id.sh within the repository.

Does anyone know if they are used somewhere else? Is it safe to delete them?

@elastic/observablt-ci @elastic/apm-agent-java

@reakaleek
reakaleek requested review from a team June 5, 2023 15:54
@reakaleek
reakaleek marked this pull request as ready for review June 5, 2023 16:01
@reakaleek
reakaleek requested a review from JonasKunz June 5, 2023 16:01
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 }}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commits to the main branch will not be allowed with the new changes in permissions, Would this code work?

@reakaleek reakaleek Jun 6, 2023

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume it works because the job has

permissions:
      contents: write

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

@reakaleek reakaleek Jun 6, 2023

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@reakaleek
reakaleek requested a review from kuisathaverat June 6, 2023 07:45
Comment thread .github/workflows/release.yml Outdated
Comment thread .github/workflows/release.yml
Comment thread .github/workflows/release.yml Outdated
reakaleek and others added 2 commits June 7, 2023 11:20
Co-authored-by: Adrien Mannocci <adrien.mannocci@gmail.com>
@amannocci
amannocci self-requested a review June 7, 2023 10:08
Comment thread .buildkite/release.yml Outdated
provider: "gcp"

steps:
- label: "Run the snapshot"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Run the snapshot - is this a copy-paste leftover?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@reakaleek
reakaleek enabled auto-merge (squash) June 12, 2023 10:16
@reakaleek
reakaleek disabled auto-merge June 12, 2023 10:36
@reakaleek
reakaleek enabled auto-merge (squash) June 12, 2023 10:57
@reakaleek
reakaleek disabled auto-merge June 12, 2023 11:36
@reakaleek
reakaleek enabled auto-merge (squash) June 12, 2023 11:45
@reakaleek
reakaleek merged commit 0c2e1f9 into elastic:main Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agent-java community Issues and PRs created by the community triage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants