Add RWX as a build provider #4796
robinaugh
started this conversation in
Extension requests
Replies: 1 comment 3 replies
|
Seems like a reasonable addition, do they offer a OSS/Free/Self-hosted tier we can use for integration tests to verify? |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey team - Per the contributing guide, I'm seeking buyoff before opening a PR.
RWX is a cloud CI/CD platform with a growing .NET user base. I'd like to add it as a build provider under src/Cake.Common/Build/Rwx/, alongside the 14 already supported (GitHub Actions, GitLab CI, Azure Pipelines, etc.) so that Cake scripts running on RWX get the same
IsLocalBuild/IsRunningOnRwx/BuildSystem.Rwx.Environmentbehavior they get on every other supported CI.Detection contract
RWX exposes a documented env var contract: https://www.rwx.com/docs/environment-variables#meta-environment-variables
Proposed shape
Modeled on the existing TravisCI / GitLabCI providers — env/info only, no Commands surface for now:
Plus the usual additions to BuildProvider.cs, BuildSystem.cs, BuildSystemAliases.cs, DI registration, and unit tests modeled on the existing provider tests.
Worth flagging up front:
IsPullRequestaggregation. RWX's current envvar contract doesn't expose a PR identifier (many runs are kicked off from the CLI before PRing), so the initial provider would not contribute toBuildSystem.IsPullRequest.If approved, I'll open the accompanying issue linking back to this discussion and start the PR against develop. Once that's in, we'd also document the integration in our docs at rwx.com/docs.
I appreciate the time, and I'm happy to adjust scope or shape based on what you'd prefer to see!
All reactions