Well, the big hole in this plan is that I think we have to use someone's
personal VM account (in this case, mine). I can't think of a way we can run
interactive commands like git push on builds@. But that reminds me to go see
what are current options are for free/cheap compute servers.
On 2/5/19, 1:20 PM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> wrote:
Sounds like best plan ever. Using the same PC by everyone is awesome!
On Tue, Feb 5, 2019, 8:39 PM Harbs <harbs.li...@gmail.com wrote:
> A big +1 from me!
>
> Looking forward!
>
> > On Feb 5, 2019, at 9:34 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> >
> > Hi,
> >
> > We are coming up on 3 months since 0.9.4. I have finished the changes
> to get production Royale modules to work in Tour De Flex. Lots of other
> good changes have been contributed.
> >
> > There were emails around the 0.9.4 release about others stepping up to
> cut the next release, but that hasn't happened. I tried and failed to get
> Apache Infra to allow us to run our release packaging on the Jenkins
> servers. They felt there were too many security concerns with having the
> servers push changes to Git and PGP sign artifacts.
> >
> > However, we MUST find a way for other RMs to be successful. There is no
> way I should or want to be the only RM. But I have an idea that involves
> creating a long list of Jenkins jobs on my CI server that add up to the
> release. The RM would log into Jenkins and run some job titled "Apache
> Royale Release Step 1", then wait for an email indicating that it
completed
> and follow instructions in the email, such as logging into the CI server
> via Remote Desktop, opening a command prompt and running "git push" and
> entering his/her username and password. Then run the next job and so on.
> There will be a point where the RM has to download the build artifacts,
> verify them, then PGP sign them, and upload them. That will be a likely
> point of failure, but that step should be a single Maven command and thus
> can be restarted until it finally succeeds. Then more Jenkins jobs will
be
> run. But if this works then folks won't have to setup their computers to
> be an RM.
> >
> > So, prepare for lots of commits and reverts as I try to put this
> together. I'm guessing it won't actually work until the last week of
> February at the earliest so there is no big rush to get other stuff in for
> this release, and if we get it to work, hopefully we'll release more often
> with other folks being the RM.
> >
> > -Alex
> >
>
>
