Conversation
The Azure DevOps organization ran out of free build minutes, so both Azure pipelines fail on every commit since #910. GitHub Actions now takes over their job: - windows.yml builds the solution on Windows and runs the tests, like azure-pipelines.yml did. - docker.yml verifies that the Docker image of src/Startup builds, like the "MUnique.OpenMU Docker" pipeline did. It doesn't push anything. The README build badges point to the new workflows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NzDFE3GAAd8LS25ibdKGbB
- Drop the separate Windows workflow and run the tests of the whole solution in the existing .NET Core workflow instead. - The Docker workflow now builds all images (the all-in-one image and the distributed ones). For a v* tag, it builds them for amd64, arm64 and arm/v7 and pushes them to Docker Hub as <version> and latest. This requires the DOCKERHUB_USERNAME and DOCKERHUB_TOKEN secrets. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NzDFE3GAAd8LS25ibdKGbB
sven-n
changed the title
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Both Azure pipelines (
MUnique.OpenMUandMUnique.OpenMU Docker) have failed on every master commit since #910. The code is fine; the Azure DevOps organization ran out of free build minutes:Changes
.github/workflows/dotnetcore.yml): after the existing publish of the Startup project, the workflow now builds the whole solution and runs its tests on Linux. This replaces the Windows build and test inazure-pipelines.yml. Windows-only tools such as the WinForms analyzer are no longer built on Windows..github/workflows/docker.yml): replaces theMUnique.OpenMU Dockerpipeline. It covers all 8 images, the all-in-onemunique/openmuand the distributedmunique/openmu-admin,-chat,-connect,-friend,-game,-guildand-login.masterand on pull requests, it only checks that each image builds (amd64).v*tag is pushed, it builds each image forlinux/amd64,linux/arm64andlinux/arm/v7and pushes it to Docker Hub as<version>(e.g.0.9.11forv0.9.11) andlatest. That's the same scheme as the existing images on Docker Hub.azure-pipelines.ymlis deleted, and its solution-items entry inMUnique.OpenMU.slnnow points todocker.yml.Needed before the next release
DOCKERHUB_USERNAMEandDOCKERHUB_TOKEN. The token is a Docker Hub access token with read/write access to themuniquerepositories.Notes
0.9.10,openmu-friend,-game,-guildand-loginwere never pushed to Docker Hub, only the other four images. The next release tag publishes all 8.🤖 Generated with Claude Code
https://claude.ai/code/session_01NzDFE3GAAd8LS25ibdKGbB