I'm not very experienced with spinning up servers. The CI server we are using
is effectively free, based on a generous donation from Microsoft of MSDN
accounts to ASF committers. So I leave it up 24/7, and share the RDP access on
private@. I think any other ASF committer could do the same. IIRC, if that
server actually is stopped, I have to use my personal (unshared) MSDN
credentials to start it again. AIUI, if I actually paid for the server, it
would cost me to leave it running even if it didn't run jobs between releases.
Is that what you are basically saying? I think it might be best if another
committer got a CI server going via the MS donation and could leave it up 24/7.
-Alex
On 4/12/20, 9:28 AM, "Harbs" <harbs.li...@gmail.com> wrote:
I’m willing to do this.
Considering that the release will be run infrequently, it should be doable
to have a relatively powerful server that could be spun up on demand. This is
something I have setup for my own releases.
The only complication would be that each RM would need valid credentials to
spin up the server.
Harbs
> On Apr 12, 2020, at 7:10 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
>
> A better solution, IMO, is for someone else to offer up a CI server only
for release jobs.
