Skip to content
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

chore: consume CrashReporter v5.0.0 #5131

Merged
merged 1 commit into from
Sep 3, 2023

Conversation

jdrueckert
Copy link
Member

  • GDrive support was removed with CrashReporter v5

How to test

  1. Checkout this PR
  2. Start Terasology
  3. Observe in the logs that v5.0.0 can be properly fetched from artifactory
  4. Optional: provoke a crash and see that crash reporter comes up properly
    (I already tested that locally both when introducing the latest changes in crash reporter and for this PR, but feel free to reproduce)

- GDrive support was removed with CrashReporter v5
@jdrueckert jdrueckert added Category: Build/CI Requests, Issues and Changes targeting gradle, groovy, Jenkins, etc. Size: S Small effort likely only affecting a single area and requiring little to no research labels Aug 21, 2023
@jdrueckert jdrueckert added this to the 2023 Revive - Milestone 1 milestone Aug 21, 2023
@jdrueckert jdrueckert self-assigned this Aug 21, 2023
@github-actions github-actions bot added the Type: Chore Request for or implementation of maintenance changes label Aug 21, 2023
@jdrueckert jdrueckert merged commit e710b36 into develop Sep 3, 2023
19 of 21 checks passed
@jdrueckert jdrueckert deleted the chore/consume-cr-without-gdrive-support branch September 3, 2023 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Build/CI Requests, Issues and Changes targeting gradle, groovy, Jenkins, etc. Size: S Small effort likely only affecting a single area and requiring little to no research Type: Chore Request for or implementation of maintenance changes
Projects
Status: Done
Status: No status
Development

Successfully merging this pull request may close these issues.

2 participants