You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using self-hosted runners, but currently the build action is using an outdated runner label and so isn't being picked up. It is currently self-hosted and needs to be arc-runner-set-aissemble. Alternatively, this project just builds and publishes a single POM and so doesn't have the same issues as the aissemble build that forced our hand. We could just switch back to ubuntu-latest.
The text was updated successfully, but these errors were encountered:
Primarily this is to fix the build action never being picked up for
execution. But I also noticed that we were installing Java 11 during the
build and release actions, though 601cc17 just bumped the required Java
version to 17.
Primarily this is to fix the build action never being picked up for
execution. But I also noticed that we were installing Java 11 during the
build and release actions, though 601cc17 just bumped the required Java
version to 17.
Primarily this is to fix the build action never being picked up for
execution. But I also noticed that we were installing Java 11 during the
build and release actions, though 601cc17 just bumped the required Java
version to 17.
Also adds manual execution via `workflow_dispatch`.
We're using self-hosted runners, but currently the build action is using an outdated runner label and so isn't being picked up. It is currently
self-hosted
and needs to bearc-runner-set-aissemble
. Alternatively, this project just builds and publishes a single POM and so doesn't have the same issues as the aissemble build that forced our hand. We could just switch back toubuntu-latest
.The text was updated successfully, but these errors were encountered: