You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Alex Harui <ah...@adobe.com.INVALID> on 2019/02/05 19:34:22 UTC
0.9.6 Release
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
RE: 0.9.6 Release
Posted by Yishay Weiss <yi...@hotmail.com>.
I like this plan better. Seems it would require less changes to existing scripts and code base. Also, if the end result is that anyone with docker installed only needs to run a script the bar for becoming an RM should be lower.
________________________________
From: OmPrakash Muppirala <bi...@gmail.com>
Sent: Wednesday, February 6, 2019 12:07:55 AM
To: dev@royale.apache.org
Subject: Re: 0.9.6 Release
I was wondering if we can use docker images to setup and seal the RM
environment. Then other RMs simply need to run the image locally and run
the release scripts. Might be easier. If folks like this plan, I can try
to put something together.
Thanks,
Om
On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com> wrote:
> In a recent discussion, it looks like other projects have gotten resources
> from AWS.
>
> Whatever service we use, could setup a “shared” Royale account that all
> PMC members could have access to.
>
> I don’t know if there’s some way we could leverage Gitlab’s integration
> pipelines https://docs.gitlab.com/ee/ci/README.html <
> https://docs.gitlab.com/ee/ci/README.html>
>
> > On Feb 5, 2019, at 11:33 PM, Alex Harui <ah...@adobe.com.INVALID>
> wrote:
> >
> > 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" <pi...@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.lists@gmail.com wrote:
> >
> >> A big +1 from me!
> >>
> >> Looking forward!
> >>
> >>> On Feb 5, 2019, at 9:34 PM, Alex Harui <ah...@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
> >>>
> >>
> >>
> >
> >
>
>
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Looks like we can copy an "image" from Azure.
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/download-vhd
-Alex
On 2/6/19, 12:06 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
I don't anything about docker, but in 15 minutes of reading I ran into this:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C01d2594a5d1e4191a88d08d68c09f2ff%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850371723585790&sdata=8i73omHW3ocdJWUx1buo4GrHk9r3JFRystaMgJHfkdU%3D&reserved=0
Which says: Docker can't " Run applications with graphical interfaces". If you want Royale to use Docker for releases, show that it can run checkintests with Flash and the Browser. Then I will look into it more.
The highest level goal is to make it as easy as possible for someone to volunteer to be an RM. Any requirement of "install this (Docker, etc) on your computer" is, IMO, another barrier to entry. Yeah, RMs will have to have Maven installed and maybe Ant, but you should already have those installed to be a committer/PMC member.
That said, a good takeaway from the Docker idea is to try to find a way to make an "Image" of whatever we end up with on whatever server we end up using so if the image can be copied and used on other servers. I'm not exactly sure how to do that with Azure, which hosts my CI server. I will spend a few more minutes researching that.
I could not quickly find any way to get a free VM on Azure or AWS that isn't a free-trial-start-paying-after-a-year. So, unless someone comes up with a free server we can use "forever", I'm going to just start with my Azure VM.
-Alex
On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi.
the plan sounds very good to me. Just my 2 thoughts on this:
1.- As I was reading I was thinking as well on something like Docker and
see Om as well thinking on the same. Maybe is the way to this with the
actual technology. Seems VMs are stepping out a bit this days in favor of
things like Docker. Maybe the same did Git over Svn, and today Svn is an
old remembrance. I must say that I have no experience with Docker, so doing
that will require acquire that knowledge, but seems it could be worth it.
2.- Maybe is not possible, but I want to propose to do this work I a
separate branch, so it could be in parallel to other developments. I think
work over develop is practical if there's something tiny that could be done
in a commit. But as we need more than one, or is a long process (like
this), chances are to make develop branch unstable and even for some days.
I think we should try to avoid that scenario, and branches are the best
way. If we do this way, we'll benefit of more reliable develop branch.
Thanks and good to know of this plan :)
Carlos
El mar., 5 feb. 2019 a las 23:19, Harbs (<ha...@gmail.com>) escribió:
> I’ve never used Docker myself, but that might be a good plan.
>
> > On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <bi...@gmail.com>
> wrote:
> >
> > I was wondering if we can use docker images to setup and seal the RM
> > environment. Then other RMs simply need to run the image locally and run
> > the release scripts. Might be easier. If folks like this plan, I can
> try
> > to put something together.
> >
> > Thanks,
> > Om
> >
> > On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com> wrote:
> >
> >> In a recent discussion, it looks like other projects have gotten
> resources
> >> from AWS.
> >>
> >> Whatever service we use, could setup a “shared” Royale account that all
> >> PMC members could have access to.
> >>
> >> I don’t know if there’s some way we could leverage Gitlab’s integration
> >> pipelines https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C01d2594a5d1e4191a88d08d68c09f2ff%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850371723585790&sdata=7OZKq43ulwUOLvSabHnm%2FP9FBuMkqBrZABDLsP8IUwc%3D&reserved=0 <
> >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C01d2594a5d1e4191a88d08d68c09f2ff%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850371723585790&sdata=7OZKq43ulwUOLvSabHnm%2FP9FBuMkqBrZABDLsP8IUwc%3D&reserved=0>
> >>
> >>> On Feb 5, 2019, at 11:33 PM, Alex Harui <ah...@adobe.com.INVALID>
> >> wrote:
> >>>
> >>> 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" <pi...@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.lists@gmail.com wrote:
> >>>
> >>>> A big +1 from me!
> >>>>
> >>>> Looking forward!
> >>>>
> >>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui <ah...@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
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
>
>
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C01d2594a5d1e4191a88d08d68c09f2ff%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850371723585790&sdata=UOyIWRfILBpEBUsJNbzvjdv92ExGTXxIyRxQ9F0FWBw%3D&reserved=0
Re: 0.9.6 Release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
If you want to go down this path as far as the ASF is concerned you need to comply with [1] and [2]. There’s been some recent conversations on legal dicuss and the incubator list about making releases available on these platforms that you may also want to pay attention to.
Thanks,
Justin
1. http://www.apache.org/legal/release-policy.html#what
2. https://issues.apache.org/jira/browse/LEGAL-270
Re: 0.9.6 Release
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Fri, Mar 8, 2019, 9:17 AM Alex Harui <ah...@adobe.com.invalid> wrote:
> Om,
>
> Why is Linux required? I thought Docker worked on Windows. Or does it
> create a Linux VM in the Windows Docker container?
>
Almost all base docker images are based on some variant of Linux. There
are some windows images available but that requires host machine to be
windows. Which defeats the purpose of using docker.
> -Alex
>
> On 3/8/19, 8:41 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
> A quick update from my side regarding the docker experiments:
>
> The biggest block I have right now is to get the AIR runtime working
> inside
> a linux container.
>
> There are a few hacks available to try amd force it, but I could never
> get
> it to work unfortunately.
>
> Thanks,
> Om
>
> On Fri, Mar 8, 2019, 2:13 AM Carlos Rovira <ca...@apache.org>
> wrote:
>
> > Hi Alex,
> >
> > amazing work! congrats to reach to this point! :)
> >
> > I need to put my head on all of this, but count on me to be a RM. I
> think
> > the best thing should be that you be the first RM to try your own
> > development at least for the first time, and then the rest of us will
> > follow you on the next releases. With all this on place we maybe
> could
> > release once a month or every two months...
> >
> > Thanks for doing this :)
> >
> > Carlos
> >
> >
> > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> (<ah...@adobe.com.invalid>)
> > escribió:
> >
> > > OK, I've now seen Jenkins perform the steps to build the release
> > > artifacts. Folks interested in Docker-izing the steps are welcome
> to
> > look
> > > at the jobs on the "Royale Release" tab on the CI server.
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643816569&sdata=xhRB2A%2BHzgFpnk02yiEc71xLYO15yZU851nlN0mRBDQ%3D&reserved=0
> > >
> > > These steps assume that the RM can run the basic Maven and Ant
> build on
> > > the RM's computer. I think that's a fair requirement since all of
> us on
> > the
> > > PMC need to able to do that to build the RC in order to vote on it.
> > > Jenkins does other tasks like run the Maven release plugin steps.
> > >
> > > Currently that results in binaries on Jenkins that are downloaded
> to the
> > > RM's computer. These binaries need to be verified by the RM which
> is the
> > > next phase I will be starting on now. The RM verifies the bits
> and then
> > > PGP signs them. And then the bits are uploaded off the RM's
> computer to
> > > Maven Staging or dist.a.o/dev. If that uploading turns out to be
> a
> > point
> > > of failure, we have the option of having Jenkins upload the big
> files and
> > > have the RM only upload PGP signature files. Or finding a way for
> > Jenkins
> > > to get the signature files from the RM. The uploads worked fine
> for me,
> > > but then again, so did the old script's uploads.
> > >
> > > Therefore, once I get the binary verification phase completed, I
> think
> > > someone other than me should be the RM and try to use these steps
> to
> > > generate the release and help debug the process for the next RM.
> So,
> > > please try to carve out some time to be the RM. One advantage of
> doing
> > > most of the work on Jenkins is that it frees up my computer to do
> other
> > > things while Jenkins is cranking away.
> > >
> > > I think we're at least a week away from binary verification, maybe
> two,
> > so
> > > it is time to start thinking about what is going in this release.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 3/7/19, 4:15 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> > >
> > > In case you haven't guessed, I'm testing out Jenkins and its
> ability
> > > to create the artifacts and send emails. Please ignore any email
> that
> > > looks like a vote or discuss thread.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 2/10/19, 8:44 PM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> > >
> > > Om,
> > >
> > > Well, that's what I used for the last release. I'm sure
> there is
> > > probably some inaccuracy in it.
> > >
> > > That said, I'm abandoning that document and taking a new
> angle
> > > because that document presumed that the release manager was trying
> to
> > > create a release on his/her computer. I've given up on that and
> working
> > on
> > > making releases from a shared computer for the reasons I've stated
> > > upthread. I hope to make some progress on that this week.
> > >
> > > The key difference is that the new angle does not presume
> that
> > you
> > > have Git SSH and PGP signatures all set up on some computer. I
> have not
> > > looked into how Docker would handle that. You certainly wouldn't
> want
> > the
> > > Docker image to contain your SSH or PGP keys/creds. And if the
> Docker
> > > image doesn't, then that is another stumbling block for future RMs.
> > >
> > > The other key difference is that the old script presumed
> you
> > could
> > > create the 3 release in 3 huge "easy" steps. We've seen that is
> only
> > true
> > > for me. So the new angle creates many discrete steps managed by
> Jenkins.
> > >
> > > So, it is up to you to decide what you want to
> "Docker-ize". You
> > > can try to Docker-ize the current 3 big steps, so RMs can try to
> run it
> > on
> > > their systems, but I'd bet they will just faiI due to network
> issues. I
> > > would be interested in using Docker to make each of these many
> discrete
> > > steps portable to another server. I'm not going to involve
> Docker at
> > this
> > > point. My main goal is just to see if I can create a workflow of
> many
> > > discrete steps that isn't horribly painful. Once we see what
> these steps
> > > turn out to be, then we can worry about server portability of those
> > steps.
> > >
> > > Either way, we want to know about running Browser+Selenium
> for
> > > sure. And maybe FlashPlayerDebugger or AIR. I would want to
> know, for
> > > example, how you debug a failing checkintest in a Docker container.
> > >
> > > Thanks,
> > > -Alex
> > >
> > >
> > > On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <
> bigosmallm@gmail.com
> > >
> > > wrote:
> > >
> > > Alex,
> > >
> > > Just to be clear, I am following the steps from here
> to try
> > > and setup a
> > > docker container.
> > >
> > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643816569&sdata=DUN8gUQrTMxTs1xfNUHiJfPe%2BJi%2BKscM15tZmaHjsms%3D&reserved=0
> > >
> > > Is this doc up to date?
> > >
> > > Thanks,
> > > Om
> > >
> > > On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <
> > > bigosmallm@gmail.com>
> > > wrote:
> > >
> > > > One approach is to have each step in the process
> spin up a
> > > docker image.
> > > > And use docker-compose to run each step. All the
> images
> > can
> > > be made to
> > > > share a common volume where all the artifacts are
> stored
> > > across steps.
> > > >
> > > > You are right about the networking issue though. Any
> > > network related
> > > > failure that occurs on the host machine will most
> likely
> > > occur in the
> > > > docker container. Although, I am not clear how we
> can
> > > guarantee that the
> > > > same issues will not occur on the Jenkins server. I
> mean,
> > > what is special
> > > > about the Jenkins server that makes it immune to
> these
> > > networking issues?
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Wed, Feb 6, 2019 at 11:48 AM Alex Harui
> > > <ah...@adobe.com.invalid>
> > > > wrote:
> > > >
> > > >> Again, I don't know anything about Docker, but
> before we
> > > spend a lot of
> > > >> time on Docker, I also want to point out that the
> process
> > > to create a
> > > >> release cannot really be thought of as "one
> application".
> > > It will be a
> > > >> series of "steps" to run. How many steps depends
> on
> > > whether we think we
> > > >> can isolate enough stuff via Docker to be able to
> run
> > > Docker on the RM's
> > > >> computer instead of some shared computer. On a
> shared
> > > computer there will
> > > >> be dozens of steps because the RM will need to enter
> > > passwords to commit
> > > >> stuff. On a local computer I guess the RM can
> supply
> > > passwords but I think
> > > >> there will be stopping points where the Maven
> artifacts
> > are
> > > deployed and
> > > >> the staging repo is closed, and another stopping
> point for
> > > the vote. It
> > > >> seems like Docker works by downloading dependencies.
> > Given
> > > that the
> > > >> problem the RMs had last time involved downloads and
> > > uploads, why do we
> > > >> think Docker will really solve this for creating
> releases
> > > on local machines?
> > > >>
> > > >> The reason to do this on a shared machine is so
> that new
> > > RMs don't have
> > > >> to do as much setup. But then I wonder about the
> > > efficiency of kicking off
> > > >> that many Docker images. Jenkins can manage that
> already.
> > > Does Docker
> > > >> have some sort of similar Dashboard or would we use
> > Jenkins
> > > to kick off
> > > >> Docker steps? I can't quite picture what is the
> outermost
> > > >> control/dashboard.
> > > >>
> > > >> -Alex
> > > >>
> > > >> On 2/6/19, 11:03 AM, "Harbs" <harbs.lists@gmail.com
> >
> > wrote:
> > > >>
> > > >> A quick search turns up this:
> > > >>
> > > >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=mE1BTifHMPdTkfIKlBTOg4u9XztrJopi7YTMUegrY0k%3D&reserved=0
> > > >> <
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=mE1BTifHMPdTkfIKlBTOg4u9XztrJopi7YTMUegrY0k%3D&reserved=0
> > > >> >
> > > >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=MrfZhrrkYZSYJnYWXUwF44rBjptBkWgJNMuvdYyoJRQ%3D&reserved=0
> > > >> <
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=MrfZhrrkYZSYJnYWXUwF44rBjptBkWgJNMuvdYyoJRQ%3D&reserved=0
> > > >> >
> > > >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=eBdEmF%2F4zAEfw0rro0%2B5tfN5tC5aYgds0oeUXDyxSzk%3D&reserved=0
> > > >> <
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=eBdEmF%2F4zAEfw0rro0%2B5tfN5tC5aYgds0oeUXDyxSzk%3D&reserved=0
> > > >> >
> > > >>
> > > >> > On Feb 6, 2019, at 8:59 PM, Alex Harui
> > > <ah...@adobe.com.INVALID>
> > > >> wrote:
> > > >> >
> > > >> > Thanks for volunteering to try it Om. IMO,
> even
> > more
> > > important
> > > >> than Firefox+Flash is SomeBrowser+Selenium. We may
> also
> > > need to run Adobe
> > > >> AIR's adb. We could probably turn off the Flash
> tests or
> > > replace Flash
> > > >> with AIR.
> > > >> >
> > > >> > Thanks,
> > > >> > -Alex
> > > >> >
> > > >> > On 2/6/19, 10:54 AM, "Carlos Rovira" <
> > > carlosrovira@apache.org>
> > > >> wrote:
> > > >> >
> > > >> > Hi Om, that would be great! waiting for
> your
> > > experience with a
> > > >> that! :)
> > > >> >
> > > >> > El mié., 6 feb. 2019 a las 19:31, OmPrakash
> > > Muppirala (<
> > > >> bigosmallm@gmail.com>)
> > > >> > escribió:
> > > >> >
> > > >> >> Yes, I agree with Alex about not being able
> to run
> > > UI out of docker
> > > >> >> containers. I never thought of the
> checkintests
> > > when I made the
> > > >> >> suggestion.
> > > >> >>
> > > >> >> The firefox-flash image that Yishay pointed
> out
> > > looks promising.
> > > >> I will
> > > >> >> poke around with it and see if that works
> for us.
> > > >> >>
> > > >> >> Thanks,
> > > >> >> Om
> > > >> >>
> > > >> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss
> <
> > > >> yishayjobs@hotmail.com>
> > > >> >> wrote:
> > > >> >>
> > > >> >>> I’ll let Om or someone else with docker
> experience
> > > tell us if
> > > >> this [1] is
> > > >> >>> relevant.
> > > >> >>>
> > > >> >>>
> > > >> >>>
> > > >> >>> [1]
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=SLiE3Eo9Ts0wX1ZLIil4xp6rLMEdreBPKeTfg%2BOcFM0%3D&reserved=0
> > > >> >>>
> > > >> >>>
> > > >> >>>
> > > >> >>> ________________________________
> > > >> >>> From: Alex Harui <ah...@adobe.com.INVALID>
> > > >> >>> Sent: Wednesday, February 6, 2019 10:05:54
> AM
> > > >> >>> To: dev@royale.apache.org
> > > >> >>> Subject: Re: 0.9.6 Release
> > > >> >>>
> > > >> >>> I don't anything about docker, but in 15
> minutes
> > of
> > > reading I ran
> > > >> into
> > > >> >>> this:
> > > >> >>>
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=szljJ%2B%2F7a05Bjl2fuyAo2yC1%2FIKxaEpPakCpSvWKlQs%3D&reserved=0
> > > >> >>>
> > > >> >>> Which says: Docker can't " Run applications
> with
> > > graphical
> > > >> interfaces".
> > > >> >>> If you want Royale to use Docker for
> releases,
> > show
> > > that it can
> > > >> run
> > > >> >>> checkintests with Flash and the Browser.
> Then I
> > > will look into
> > > >> it more.
> > > >> >>>
> > > >> >>> The highest level goal is to make it as
> easy as
> > > possible for
> > > >> someone to
> > > >> >>> volunteer to be an RM. Any requirement of
> > "install
> > > this (Docker,
> > > >> etc) on
> > > >> >>> your computer" is, IMO, another barrier to
> entry.
> > > Yeah, RMs will
> > > >> have to
> > > >> >>> have Maven installed and maybe Ant, but you
> should
> > > already have
> > > >> those
> > > >> >>> installed to be a committer/PMC member.
> > > >> >>>
> > > >> >>> That said, a good takeaway from the Docker
> idea is
> > > to try to find
> > > >> a way
> > > >> >> to
> > > >> >>> make an "Image" of whatever we end up with
> on
> > > whatever server we
> > > >> end up
> > > >> >>> using so if the image can be copied and
> used on
> > > other servers.
> > > >> I'm not
> > > >> >>> exactly sure how to do that with Azure,
> which
> > hosts
> > > my CI
> > > >> server. I will
> > > >> >>> spend a few more minutes researching that.
> > > >> >>>
> > > >> >>> I could not quickly find any way to get a
> free VM
> > > on Azure or AWS
> > > >> that
> > > >> >>> isn't a
> free-trial-start-paying-after-a-year. So,
> > > unless someone
> > > >> comes
> > > >> >> up
> > > >> >>> with a free server we can use "forever",
> I'm going
> > > to just start
> > > >> with my
> > > >> >>> Azure VM.
> > > >> >>>
> > > >> >>> -Alex
> > > >> >>>
> > > >> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <
> > > carlosrovira@apache.org>
> > > >> wrote:
> > > >> >>>
> > > >> >>> Hi.
> > > >> >>>
> > > >> >>> the plan sounds very good to me. Just my
> 2
> > > thoughts on this:
> > > >> >>>
> > > >> >>> 1.- As I was reading I was thinking as
> well on
> > > something like
> > > >> Docker
> > > >> >>> and
> > > >> >>> see Om as well thinking on the same.
> Maybe is
> > > the way to this
> > > >> with
> > > >> >> the
> > > >> >>> actual technology. Seems VMs are
> stepping out a
> > > bit this days
> > > >> in
> > > >> >> favor
> > > >> >>> of
> > > >> >>> things like Docker. Maybe the same did
> Git over
> > > Svn, and today
> > > >> Svn is
> > > >> >>> an
> > > >> >>> old remembrance. I must say that I have
> no
> > > experience with
> > > >> Docker, so
> > > >> >>> doing
> > > >> >>> that will require acquire that
> knowledge, but
> > > seems it could
> > > >> be worth
> > > >> >>> it.
> > > >> >>>
> > > >> >>> 2.- Maybe is not possible, but I want to
> > propose
> > > to do this
> > > >> work I a
> > > >> >>> separate branch, so it could be in
> parallel to
> > > other
> > > >> developments. I
> > > >> >>> think
> > > >> >>> work over develop is practical if there's
> > > something tiny that
> > > >> could
> > > >> >> be
> > > >> >>> done
> > > >> >>> in a commit. But as we need more than
> one, or
> > is
> > > a long
> > > >> process (like
> > > >> >>> this), chances are to make develop branch
> > > unstable and even
> > > >> for some
> > > >> >>> days.
> > > >> >>> I think we should try to avoid that
> scenario,
> > > and branches are
> > > >> the
> > > >> >> best
> > > >> >>> way. If we do this way, we'll benefit of
> more
> > > reliable develop
> > > >> >> branch.
> > > >> >>>
> > > >> >>> Thanks and good to know of this plan :)
> > > >> >>>
> > > >> >>> Carlos
> > > >> >>>
> > > >> >>>
> > > >> >>> El mar., 5 feb. 2019 a las 23:19, Harbs
> (<
> > > >> harbs.lists@gmail.com>)
> > > >> >>> escribió:
> > > >> >>>
> > > >> >>>> I’ve never used Docker myself, but that
> might be
> > a
> > > good plan.
> > > >> >>>>
> > > >> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash
> > Muppirala <
> > > >> >>> bigosmallm@gmail.com>
> > > >> >>>> wrote:
> > > >> >>>>>
> > > >> >>>>> I was wondering if we can use docker
> images to
> > > setup and seal
> > > >> the
> > > >> >>> RM
> > > >> >>>>> environment. Then other RMs simply need
> to run
> > > the image
> > > >> locally
> > > >> >>> and run
> > > >> >>>>> the release scripts. Might be easier.
> If folks
> > > like this plan,
> > > >> >> I
> > > >> >>> can
> > > >> >>>> try
> > > >> >>>>> to put something together.
> > > >> >>>>>
> > > >> >>>>> Thanks,
> > > >> >>>>> Om
> > > >> >>>>>
> > > >> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <
> > > harbs.lists@gmail.com>
> > > >> >>> wrote:
> > > >> >>>>>
> > > >> >>>>>> In a recent discussion, it looks like
> other
> > > projects have
> > > >> gotten
> > > >> >>>> resources
> > > >> >>>>>> from AWS.
> > > >> >>>>>>
> > > >> >>>>>> Whatever service we use, could setup a
> “shared”
> > > Royale account
> > > >> >>> that all
> > > >> >>>>>> PMC members could have access to.
> > > >> >>>>>>
> > > >> >>>>>> I don’t know if there’s some way we could
> > > leverage Gitlab’s
> > > >> >>> integration
> > > >> >>>>>> pipelines
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=WzuomZ7NN31Pdmp0wHgmNj6OxuOgYAjUPGj1ENzKjPQ%3D&reserved=0
> > > >> >>> <
> > > >> >>>>>>
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643836589&sdata=zv79LGKuCsF5RdIX3XnoefxKz5xYuscoT6THUrr3Tcg%3D&reserved=0
> > > >> >>>>
> > > >> >>>>>>
> > > >> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
> > > >> >> <aharui@adobe.com.INVALID
> > > >> >>>>
> > > >> >>>>>> wrote:
> > > >> >>>>>>>
> > > >> >>>>>>> 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" <
> > > >> >> piotrzarzycki21@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.lists@gmail.com
> > > >> >>> wrote:
> > > >> >>>>>>>
> > > >> >>>>>>>> A big +1 from me!
> > > >> >>>>>>>>
> > > >> >>>>>>>> Looking forward!
> > > >> >>>>>>>>
> > > >> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
> > > >> >>> <ah...@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
> > > >> >>>>>>>>>
> > > >> >>>>>>>>
> > > >> >>>>>>>>
> > > >> >>>>>>>
> > > >> >>>>>>>
> > > >> >>>>>>
> > > >> >>>>>>
> > > >> >>>>
> > > >> >>>>
> > > >> >>>
> > > >> >>> --
> > > >> >>> Carlos Rovira
> > > >> >>>
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643836589&sdata=%2F4wc15Un0wZQ6g5b4RQYk2%2Bc%2BWHPUJmWzYLTRpIxCuA%3D&reserved=0
> > > >> >>>
> > > >> >>>
> > > >> >>>
> > > >> >>
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Carlos Rovira
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643836589&sdata=%2F4wc15Un0wZQ6g5b4RQYk2%2Bc%2BWHPUJmWzYLTRpIxCuA%3D&reserved=0
> > > >> >
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643836589&sdata=%2F4wc15Un0wZQ6g5b4RQYk2%2Bc%2BWHPUJmWzYLTRpIxCuA%3D&reserved=0
> >
>
>
>
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Om,
Why is Linux required? I thought Docker worked on Windows. Or does it create a Linux VM in the Windows Docker container?
-Alex
On 3/8/19, 8:41 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
A quick update from my side regarding the docker experiments:
The biggest block I have right now is to get the AIR runtime working inside
a linux container.
There are a few hacks available to try amd force it, but I could never get
it to work unfortunately.
Thanks,
Om
On Fri, Mar 8, 2019, 2:13 AM Carlos Rovira <ca...@apache.org> wrote:
> Hi Alex,
>
> amazing work! congrats to reach to this point! :)
>
> I need to put my head on all of this, but count on me to be a RM. I think
> the best thing should be that you be the first RM to try your own
> development at least for the first time, and then the rest of us will
> follow you on the next releases. With all this on place we maybe could
> release once a month or every two months...
>
> Thanks for doing this :)
>
> Carlos
>
>
> El vie., 8 mar. 2019 a las 1:55, Alex Harui (<ah...@adobe.com.invalid>)
> escribió:
>
> > OK, I've now seen Jenkins perform the steps to build the release
> > artifacts. Folks interested in Docker-izing the steps are welcome to
> look
> > at the jobs on the "Royale Release" tab on the CI server.
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643816569&sdata=xhRB2A%2BHzgFpnk02yiEc71xLYO15yZU851nlN0mRBDQ%3D&reserved=0
> >
> > These steps assume that the RM can run the basic Maven and Ant build on
> > the RM's computer. I think that's a fair requirement since all of us on
> the
> > PMC need to able to do that to build the RC in order to vote on it.
> > Jenkins does other tasks like run the Maven release plugin steps.
> >
> > Currently that results in binaries on Jenkins that are downloaded to the
> > RM's computer. These binaries need to be verified by the RM which is the
> > next phase I will be starting on now. The RM verifies the bits and then
> > PGP signs them. And then the bits are uploaded off the RM's computer to
> > Maven Staging or dist.a.o/dev. If that uploading turns out to be a
> point
> > of failure, we have the option of having Jenkins upload the big files and
> > have the RM only upload PGP signature files. Or finding a way for
> Jenkins
> > to get the signature files from the RM. The uploads worked fine for me,
> > but then again, so did the old script's uploads.
> >
> > Therefore, once I get the binary verification phase completed, I think
> > someone other than me should be the RM and try to use these steps to
> > generate the release and help debug the process for the next RM. So,
> > please try to carve out some time to be the RM. One advantage of doing
> > most of the work on Jenkins is that it frees up my computer to do other
> > things while Jenkins is cranking away.
> >
> > I think we're at least a week away from binary verification, maybe two,
> so
> > it is time to start thinking about what is going in this release.
> >
> > Thanks,
> > -Alex
> >
> > On 3/7/19, 4:15 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> >
> > In case you haven't guessed, I'm testing out Jenkins and its ability
> > to create the artifacts and send emails. Please ignore any email that
> > looks like a vote or discuss thread.
> >
> > Thanks,
> > -Alex
> >
> > On 2/10/19, 8:44 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> >
> > Om,
> >
> > Well, that's what I used for the last release. I'm sure there is
> > probably some inaccuracy in it.
> >
> > That said, I'm abandoning that document and taking a new angle
> > because that document presumed that the release manager was trying to
> > create a release on his/her computer. I've given up on that and working
> on
> > making releases from a shared computer for the reasons I've stated
> > upthread. I hope to make some progress on that this week.
> >
> > The key difference is that the new angle does not presume that
> you
> > have Git SSH and PGP signatures all set up on some computer. I have not
> > looked into how Docker would handle that. You certainly wouldn't want
> the
> > Docker image to contain your SSH or PGP keys/creds. And if the Docker
> > image doesn't, then that is another stumbling block for future RMs.
> >
> > The other key difference is that the old script presumed you
> could
> > create the 3 release in 3 huge "easy" steps. We've seen that is only
> true
> > for me. So the new angle creates many discrete steps managed by Jenkins.
> >
> > So, it is up to you to decide what you want to "Docker-ize". You
> > can try to Docker-ize the current 3 big steps, so RMs can try to run it
> on
> > their systems, but I'd bet they will just faiI due to network issues. I
> > would be interested in using Docker to make each of these many discrete
> > steps portable to another server. I'm not going to involve Docker at
> this
> > point. My main goal is just to see if I can create a workflow of many
> > discrete steps that isn't horribly painful. Once we see what these steps
> > turn out to be, then we can worry about server portability of those
> steps.
> >
> > Either way, we want to know about running Browser+Selenium for
> > sure. And maybe FlashPlayerDebugger or AIR. I would want to know, for
> > example, how you debug a failing checkintest in a Docker container.
> >
> > Thanks,
> > -Alex
> >
> >
> > On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <bigosmallm@gmail.com
> >
> > wrote:
> >
> > Alex,
> >
> > Just to be clear, I am following the steps from here to try
> > and setup a
> > docker container.
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643816569&sdata=DUN8gUQrTMxTs1xfNUHiJfPe%2BJi%2BKscM15tZmaHjsms%3D&reserved=0
> >
> > Is this doc up to date?
> >
> > Thanks,
> > Om
> >
> > On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <
> > bigosmallm@gmail.com>
> > wrote:
> >
> > > One approach is to have each step in the process spin up a
> > docker image.
> > > And use docker-compose to run each step. All the images
> can
> > be made to
> > > share a common volume where all the artifacts are stored
> > across steps.
> > >
> > > You are right about the networking issue though. Any
> > network related
> > > failure that occurs on the host machine will most likely
> > occur in the
> > > docker container. Although, I am not clear how we can
> > guarantee that the
> > > same issues will not occur on the Jenkins server. I mean,
> > what is special
> > > about the Jenkins server that makes it immune to these
> > networking issues?
> > >
> > > Thanks,
> > > Om
> > >
> > > On Wed, Feb 6, 2019 at 11:48 AM Alex Harui
> > <ah...@adobe.com.invalid>
> > > wrote:
> > >
> > >> Again, I don't know anything about Docker, but before we
> > spend a lot of
> > >> time on Docker, I also want to point out that the process
> > to create a
> > >> release cannot really be thought of as "one application".
> > It will be a
> > >> series of "steps" to run. How many steps depends on
> > whether we think we
> > >> can isolate enough stuff via Docker to be able to run
> > Docker on the RM's
> > >> computer instead of some shared computer. On a shared
> > computer there will
> > >> be dozens of steps because the RM will need to enter
> > passwords to commit
> > >> stuff. On a local computer I guess the RM can supply
> > passwords but I think
> > >> there will be stopping points where the Maven artifacts
> are
> > deployed and
> > >> the staging repo is closed, and another stopping point for
> > the vote. It
> > >> seems like Docker works by downloading dependencies.
> Given
> > that the
> > >> problem the RMs had last time involved downloads and
> > uploads, why do we
> > >> think Docker will really solve this for creating releases
> > on local machines?
> > >>
> > >> The reason to do this on a shared machine is so that new
> > RMs don't have
> > >> to do as much setup. But then I wonder about the
> > efficiency of kicking off
> > >> that many Docker images. Jenkins can manage that already.
> > Does Docker
> > >> have some sort of similar Dashboard or would we use
> Jenkins
> > to kick off
> > >> Docker steps? I can't quite picture what is the outermost
> > >> control/dashboard.
> > >>
> > >> -Alex
> > >>
> > >> On 2/6/19, 11:03 AM, "Harbs" <ha...@gmail.com>
> wrote:
> > >>
> > >> A quick search turns up this:
> > >>
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=mE1BTifHMPdTkfIKlBTOg4u9XztrJopi7YTMUegrY0k%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=mE1BTifHMPdTkfIKlBTOg4u9XztrJopi7YTMUegrY0k%3D&reserved=0
> > >> >
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=MrfZhrrkYZSYJnYWXUwF44rBjptBkWgJNMuvdYyoJRQ%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=MrfZhrrkYZSYJnYWXUwF44rBjptBkWgJNMuvdYyoJRQ%3D&reserved=0
> > >> >
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=eBdEmF%2F4zAEfw0rro0%2B5tfN5tC5aYgds0oeUXDyxSzk%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=eBdEmF%2F4zAEfw0rro0%2B5tfN5tC5aYgds0oeUXDyxSzk%3D&reserved=0
> > >> >
> > >>
> > >> > On Feb 6, 2019, at 8:59 PM, Alex Harui
> > <ah...@adobe.com.INVALID>
> > >> wrote:
> > >> >
> > >> > Thanks for volunteering to try it Om. IMO, even
> more
> > important
> > >> than Firefox+Flash is SomeBrowser+Selenium. We may also
> > need to run Adobe
> > >> AIR's adb. We could probably turn off the Flash tests or
> > replace Flash
> > >> with AIR.
> > >> >
> > >> > Thanks,
> > >> > -Alex
> > >> >
> > >> > On 2/6/19, 10:54 AM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > >> wrote:
> > >> >
> > >> > Hi Om, that would be great! waiting for your
> > experience with a
> > >> that! :)
> > >> >
> > >> > El mié., 6 feb. 2019 a las 19:31, OmPrakash
> > Muppirala (<
> > >> bigosmallm@gmail.com>)
> > >> > escribió:
> > >> >
> > >> >> Yes, I agree with Alex about not being able to run
> > UI out of docker
> > >> >> containers. I never thought of the checkintests
> > when I made the
> > >> >> suggestion.
> > >> >>
> > >> >> The firefox-flash image that Yishay pointed out
> > looks promising.
> > >> I will
> > >> >> poke around with it and see if that works for us.
> > >> >>
> > >> >> Thanks,
> > >> >> Om
> > >> >>
> > >> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <
> > >> yishayjobs@hotmail.com>
> > >> >> wrote:
> > >> >>
> > >> >>> I’ll let Om or someone else with docker experience
> > tell us if
> > >> this [1] is
> > >> >>> relevant.
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>> [1]
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=SLiE3Eo9Ts0wX1ZLIil4xp6rLMEdreBPKeTfg%2BOcFM0%3D&reserved=0
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>> ________________________________
> > >> >>> From: Alex Harui <ah...@adobe.com.INVALID>
> > >> >>> Sent: Wednesday, February 6, 2019 10:05:54 AM
> > >> >>> To: dev@royale.apache.org
> > >> >>> Subject: Re: 0.9.6 Release
> > >> >>>
> > >> >>> I don't anything about docker, but in 15 minutes
> of
> > reading I ran
> > >> into
> > >> >>> this:
> > >> >>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=szljJ%2B%2F7a05Bjl2fuyAo2yC1%2FIKxaEpPakCpSvWKlQs%3D&reserved=0
> > >> >>>
> > >> >>> Which says: Docker can't " Run applications with
> > graphical
> > >> interfaces".
> > >> >>> If you want Royale to use Docker for releases,
> show
> > that it can
> > >> run
> > >> >>> checkintests with Flash and the Browser. Then I
> > will look into
> > >> it more.
> > >> >>>
> > >> >>> The highest level goal is to make it as easy as
> > possible for
> > >> someone to
> > >> >>> volunteer to be an RM. Any requirement of
> "install
> > this (Docker,
> > >> etc) on
> > >> >>> your computer" is, IMO, another barrier to entry.
> > Yeah, RMs will
> > >> have to
> > >> >>> have Maven installed and maybe Ant, but you should
> > already have
> > >> those
> > >> >>> installed to be a committer/PMC member.
> > >> >>>
> > >> >>> That said, a good takeaway from the Docker idea is
> > to try to find
> > >> a way
> > >> >> to
> > >> >>> make an "Image" of whatever we end up with on
> > whatever server we
> > >> end up
> > >> >>> using so if the image can be copied and used on
> > other servers.
> > >> I'm not
> > >> >>> exactly sure how to do that with Azure, which
> hosts
> > my CI
> > >> server. I will
> > >> >>> spend a few more minutes researching that.
> > >> >>>
> > >> >>> I could not quickly find any way to get a free VM
> > on Azure or AWS
> > >> that
> > >> >>> isn't a free-trial-start-paying-after-a-year. So,
> > unless someone
> > >> comes
> > >> >> up
> > >> >>> with a free server we can use "forever", I'm going
> > to just start
> > >> with my
> > >> >>> Azure VM.
> > >> >>>
> > >> >>> -Alex
> > >> >>>
> > >> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > >> wrote:
> > >> >>>
> > >> >>> Hi.
> > >> >>>
> > >> >>> the plan sounds very good to me. Just my 2
> > thoughts on this:
> > >> >>>
> > >> >>> 1.- As I was reading I was thinking as well on
> > something like
> > >> Docker
> > >> >>> and
> > >> >>> see Om as well thinking on the same. Maybe is
> > the way to this
> > >> with
> > >> >> the
> > >> >>> actual technology. Seems VMs are stepping out a
> > bit this days
> > >> in
> > >> >> favor
> > >> >>> of
> > >> >>> things like Docker. Maybe the same did Git over
> > Svn, and today
> > >> Svn is
> > >> >>> an
> > >> >>> old remembrance. I must say that I have no
> > experience with
> > >> Docker, so
> > >> >>> doing
> > >> >>> that will require acquire that knowledge, but
> > seems it could
> > >> be worth
> > >> >>> it.
> > >> >>>
> > >> >>> 2.- Maybe is not possible, but I want to
> propose
> > to do this
> > >> work I a
> > >> >>> separate branch, so it could be in parallel to
> > other
> > >> developments. I
> > >> >>> think
> > >> >>> work over develop is practical if there's
> > something tiny that
> > >> could
> > >> >> be
> > >> >>> done
> > >> >>> in a commit. But as we need more than one, or
> is
> > a long
> > >> process (like
> > >> >>> this), chances are to make develop branch
> > unstable and even
> > >> for some
> > >> >>> days.
> > >> >>> I think we should try to avoid that scenario,
> > and branches are
> > >> the
> > >> >> best
> > >> >>> way. If we do this way, we'll benefit of more
> > reliable develop
> > >> >> branch.
> > >> >>>
> > >> >>> Thanks and good to know of this plan :)
> > >> >>>
> > >> >>> Carlos
> > >> >>>
> > >> >>>
> > >> >>> El mar., 5 feb. 2019 a las 23:19, Harbs (<
> > >> harbs.lists@gmail.com>)
> > >> >>> escribió:
> > >> >>>
> > >> >>>> I’ve never used Docker myself, but that might be
> a
> > good plan.
> > >> >>>>
> > >> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash
> Muppirala <
> > >> >>> bigosmallm@gmail.com>
> > >> >>>> wrote:
> > >> >>>>>
> > >> >>>>> I was wondering if we can use docker images to
> > setup and seal
> > >> the
> > >> >>> RM
> > >> >>>>> environment. Then other RMs simply need to run
> > the image
> > >> locally
> > >> >>> and run
> > >> >>>>> the release scripts. Might be easier. If folks
> > like this plan,
> > >> >> I
> > >> >>> can
> > >> >>>> try
> > >> >>>>> to put something together.
> > >> >>>>>
> > >> >>>>> Thanks,
> > >> >>>>> Om
> > >> >>>>>
> > >> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <
> > harbs.lists@gmail.com>
> > >> >>> wrote:
> > >> >>>>>
> > >> >>>>>> In a recent discussion, it looks like other
> > projects have
> > >> gotten
> > >> >>>> resources
> > >> >>>>>> from AWS.
> > >> >>>>>>
> > >> >>>>>> Whatever service we use, could setup a “shared”
> > Royale account
> > >> >>> that all
> > >> >>>>>> PMC members could have access to.
> > >> >>>>>>
> > >> >>>>>> I don’t know if there’s some way we could
> > leverage Gitlab’s
> > >> >>> integration
> > >> >>>>>> pipelines
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643826579&sdata=WzuomZ7NN31Pdmp0wHgmNj6OxuOgYAjUPGj1ENzKjPQ%3D&reserved=0
> > >> >>> <
> > >> >>>>>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643836589&sdata=zv79LGKuCsF5RdIX3XnoefxKz5xYuscoT6THUrr3Tcg%3D&reserved=0
> > >> >>>>
> > >> >>>>>>
> > >> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
> > >> >> <aharui@adobe.com.INVALID
> > >> >>>>
> > >> >>>>>> wrote:
> > >> >>>>>>>
> > >> >>>>>>> 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" <
> > >> >> piotrzarzycki21@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.lists@gmail.com
> > >> >>> wrote:
> > >> >>>>>>>
> > >> >>>>>>>> A big +1 from me!
> > >> >>>>>>>>
> > >> >>>>>>>> Looking forward!
> > >> >>>>>>>>
> > >> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
> > >> >>> <ah...@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
> > >> >>>>>>>>>
> > >> >>>>>>>>
> > >> >>>>>>>>
> > >> >>>>>>>
> > >> >>>>>>>
> > >> >>>>>>
> > >> >>>>>>
> > >> >>>>
> > >> >>>>
> > >> >>>
> > >> >>> --
> > >> >>> Carlos Rovira
> > >> >>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643836589&sdata=%2F4wc15Un0wZQ6g5b4RQYk2%2Bc%2BWHPUJmWzYLTRpIxCuA%3D&reserved=0
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>
> > >> >
> > >> >
> > >> > --
> > >> > Carlos Rovira
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643836589&sdata=%2F4wc15Un0wZQ6g5b4RQYk2%2Bc%2BWHPUJmWzYLTRpIxCuA%3D&reserved=0
> > >> >
> > >> >
> > >>
> > >>
> > >>
> > >>
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643836589&sdata=%2F4wc15Un0wZQ6g5b4RQYk2%2Bc%2BWHPUJmWzYLTRpIxCuA%3D&reserved=0
>
Re: 0.9.6 Release
Posted by OmPrakash Muppirala <bi...@gmail.com>.
A quick update from my side regarding the docker experiments:
The biggest block I have right now is to get the AIR runtime working inside
a linux container.
There are a few hacks available to try amd force it, but I could never get
it to work unfortunately.
Thanks,
Om
On Fri, Mar 8, 2019, 2:13 AM Carlos Rovira <ca...@apache.org> wrote:
> Hi Alex,
>
> amazing work! congrats to reach to this point! :)
>
> I need to put my head on all of this, but count on me to be a RM. I think
> the best thing should be that you be the first RM to try your own
> development at least for the first time, and then the rest of us will
> follow you on the next releases. With all this on place we maybe could
> release once a month or every two months...
>
> Thanks for doing this :)
>
> Carlos
>
>
> El vie., 8 mar. 2019 a las 1:55, Alex Harui (<ah...@adobe.com.invalid>)
> escribió:
>
> > OK, I've now seen Jenkins perform the steps to build the release
> > artifacts. Folks interested in Docker-izing the steps are welcome to
> look
> > at the jobs on the "Royale Release" tab on the CI server.
> >
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/
> >
> > These steps assume that the RM can run the basic Maven and Ant build on
> > the RM's computer. I think that's a fair requirement since all of us on
> the
> > PMC need to able to do that to build the RC in order to vote on it.
> > Jenkins does other tasks like run the Maven release plugin steps.
> >
> > Currently that results in binaries on Jenkins that are downloaded to the
> > RM's computer. These binaries need to be verified by the RM which is the
> > next phase I will be starting on now. The RM verifies the bits and then
> > PGP signs them. And then the bits are uploaded off the RM's computer to
> > Maven Staging or dist.a.o/dev. If that uploading turns out to be a
> point
> > of failure, we have the option of having Jenkins upload the big files and
> > have the RM only upload PGP signature files. Or finding a way for
> Jenkins
> > to get the signature files from the RM. The uploads worked fine for me,
> > but then again, so did the old script's uploads.
> >
> > Therefore, once I get the binary verification phase completed, I think
> > someone other than me should be the RM and try to use these steps to
> > generate the release and help debug the process for the next RM. So,
> > please try to carve out some time to be the RM. One advantage of doing
> > most of the work on Jenkins is that it frees up my computer to do other
> > things while Jenkins is cranking away.
> >
> > I think we're at least a week away from binary verification, maybe two,
> so
> > it is time to start thinking about what is going in this release.
> >
> > Thanks,
> > -Alex
> >
> > On 3/7/19, 4:15 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> >
> > In case you haven't guessed, I'm testing out Jenkins and its ability
> > to create the artifacts and send emails. Please ignore any email that
> > looks like a vote or discuss thread.
> >
> > Thanks,
> > -Alex
> >
> > On 2/10/19, 8:44 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> >
> > Om,
> >
> > Well, that's what I used for the last release. I'm sure there is
> > probably some inaccuracy in it.
> >
> > That said, I'm abandoning that document and taking a new angle
> > because that document presumed that the release manager was trying to
> > create a release on his/her computer. I've given up on that and working
> on
> > making releases from a shared computer for the reasons I've stated
> > upthread. I hope to make some progress on that this week.
> >
> > The key difference is that the new angle does not presume that
> you
> > have Git SSH and PGP signatures all set up on some computer. I have not
> > looked into how Docker would handle that. You certainly wouldn't want
> the
> > Docker image to contain your SSH or PGP keys/creds. And if the Docker
> > image doesn't, then that is another stumbling block for future RMs.
> >
> > The other key difference is that the old script presumed you
> could
> > create the 3 release in 3 huge "easy" steps. We've seen that is only
> true
> > for me. So the new angle creates many discrete steps managed by Jenkins.
> >
> > So, it is up to you to decide what you want to "Docker-ize". You
> > can try to Docker-ize the current 3 big steps, so RMs can try to run it
> on
> > their systems, but I'd bet they will just faiI due to network issues. I
> > would be interested in using Docker to make each of these many discrete
> > steps portable to another server. I'm not going to involve Docker at
> this
> > point. My main goal is just to see if I can create a workflow of many
> > discrete steps that isn't horribly painful. Once we see what these steps
> > turn out to be, then we can worry about server portability of those
> steps.
> >
> > Either way, we want to know about running Browser+Selenium for
> > sure. And maybe FlashPlayerDebugger or AIR. I would want to know, for
> > example, how you debug a failing checkintest in a Docker container.
> >
> > Thanks,
> > -Alex
> >
> >
> > On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <bigosmallm@gmail.com
> >
> > wrote:
> >
> > Alex,
> >
> > Just to be clear, I am following the steps from here to try
> > and setup a
> > docker container.
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=rJsHtgUQ%2BH5iQOXlZc%2FCEvtxH0Lm25fGn0wlAe6oqSs%3D&reserved=0
> >
> > Is this doc up to date?
> >
> > Thanks,
> > Om
> >
> > On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <
> > bigosmallm@gmail.com>
> > wrote:
> >
> > > One approach is to have each step in the process spin up a
> > docker image.
> > > And use docker-compose to run each step. All the images
> can
> > be made to
> > > share a common volume where all the artifacts are stored
> > across steps.
> > >
> > > You are right about the networking issue though. Any
> > network related
> > > failure that occurs on the host machine will most likely
> > occur in the
> > > docker container. Although, I am not clear how we can
> > guarantee that the
> > > same issues will not occur on the Jenkins server. I mean,
> > what is special
> > > about the Jenkins server that makes it immune to these
> > networking issues?
> > >
> > > Thanks,
> > > Om
> > >
> > > On Wed, Feb 6, 2019 at 11:48 AM Alex Harui
> > <ah...@adobe.com.invalid>
> > > wrote:
> > >
> > >> Again, I don't know anything about Docker, but before we
> > spend a lot of
> > >> time on Docker, I also want to point out that the process
> > to create a
> > >> release cannot really be thought of as "one application".
> > It will be a
> > >> series of "steps" to run. How many steps depends on
> > whether we think we
> > >> can isolate enough stuff via Docker to be able to run
> > Docker on the RM's
> > >> computer instead of some shared computer. On a shared
> > computer there will
> > >> be dozens of steps because the RM will need to enter
> > passwords to commit
> > >> stuff. On a local computer I guess the RM can supply
> > passwords but I think
> > >> there will be stopping points where the Maven artifacts
> are
> > deployed and
> > >> the staging repo is closed, and another stopping point for
> > the vote. It
> > >> seems like Docker works by downloading dependencies.
> Given
> > that the
> > >> problem the RMs had last time involved downloads and
> > uploads, why do we
> > >> think Docker will really solve this for creating releases
> > on local machines?
> > >>
> > >> The reason to do this on a shared machine is so that new
> > RMs don't have
> > >> to do as much setup. But then I wonder about the
> > efficiency of kicking off
> > >> that many Docker images. Jenkins can manage that already.
> > Does Docker
> > >> have some sort of similar Dashboard or would we use
> Jenkins
> > to kick off
> > >> Docker steps? I can't quite picture what is the outermost
> > >> control/dashboard.
> > >>
> > >> -Alex
> > >>
> > >> On 2/6/19, 11:03 AM, "Harbs" <ha...@gmail.com>
> wrote:
> > >>
> > >> A quick search turns up this:
> > >>
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=fA7bthRUAGXzqJdmK4raheZMEHQ4qyy3NHXjufAF6jc%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=fA7bthRUAGXzqJdmK4raheZMEHQ4qyy3NHXjufAF6jc%3D&reserved=0
> > >> >
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=QeJ5h98H2ghmY%2BMoGWKVgYaS6OKiv9BY7Cbu%2FRYh9K0%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=QeJ5h98H2ghmY%2BMoGWKVgYaS6OKiv9BY7Cbu%2FRYh9K0%3D&reserved=0
> > >> >
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=pvNt%2B4Spevu9uXaZeX1bV4AKi3p1KVnwND4XZvqlxt0%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=pvNt%2B4Spevu9uXaZeX1bV4AKi3p1KVnwND4XZvqlxt0%3D&reserved=0
> > >> >
> > >>
> > >> > On Feb 6, 2019, at 8:59 PM, Alex Harui
> > <ah...@adobe.com.INVALID>
> > >> wrote:
> > >> >
> > >> > Thanks for volunteering to try it Om. IMO, even
> more
> > important
> > >> than Firefox+Flash is SomeBrowser+Selenium. We may also
> > need to run Adobe
> > >> AIR's adb. We could probably turn off the Flash tests or
> > replace Flash
> > >> with AIR.
> > >> >
> > >> > Thanks,
> > >> > -Alex
> > >> >
> > >> > On 2/6/19, 10:54 AM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > >> wrote:
> > >> >
> > >> > Hi Om, that would be great! waiting for your
> > experience with a
> > >> that! :)
> > >> >
> > >> > El mié., 6 feb. 2019 a las 19:31, OmPrakash
> > Muppirala (<
> > >> bigosmallm@gmail.com>)
> > >> > escribió:
> > >> >
> > >> >> Yes, I agree with Alex about not being able to run
> > UI out of docker
> > >> >> containers. I never thought of the checkintests
> > when I made the
> > >> >> suggestion.
> > >> >>
> > >> >> The firefox-flash image that Yishay pointed out
> > looks promising.
> > >> I will
> > >> >> poke around with it and see if that works for us.
> > >> >>
> > >> >> Thanks,
> > >> >> Om
> > >> >>
> > >> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <
> > >> yishayjobs@hotmail.com>
> > >> >> wrote:
> > >> >>
> > >> >>> I’ll let Om or someone else with docker experience
> > tell us if
> > >> this [1] is
> > >> >>> relevant.
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>> [1]
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=O5WCCm7fcFGjaXpoDum5hMAJXl3JWscFMRMywpBAN1w%3D&reserved=0
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>> ________________________________
> > >> >>> From: Alex Harui <ah...@adobe.com.INVALID>
> > >> >>> Sent: Wednesday, February 6, 2019 10:05:54 AM
> > >> >>> To: dev@royale.apache.org
> > >> >>> Subject: Re: 0.9.6 Release
> > >> >>>
> > >> >>> I don't anything about docker, but in 15 minutes
> of
> > reading I ran
> > >> into
> > >> >>> this:
> > >> >>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=bjIQhi1pOBfBd8jQAc0XmbrsWzlDwSqieUiUoSovnIE%3D&reserved=0
> > >> >>>
> > >> >>> Which says: Docker can't " Run applications with
> > graphical
> > >> interfaces".
> > >> >>> If you want Royale to use Docker for releases,
> show
> > that it can
> > >> run
> > >> >>> checkintests with Flash and the Browser. Then I
> > will look into
> > >> it more.
> > >> >>>
> > >> >>> The highest level goal is to make it as easy as
> > possible for
> > >> someone to
> > >> >>> volunteer to be an RM. Any requirement of
> "install
> > this (Docker,
> > >> etc) on
> > >> >>> your computer" is, IMO, another barrier to entry.
> > Yeah, RMs will
> > >> have to
> > >> >>> have Maven installed and maybe Ant, but you should
> > already have
> > >> those
> > >> >>> installed to be a committer/PMC member.
> > >> >>>
> > >> >>> That said, a good takeaway from the Docker idea is
> > to try to find
> > >> a way
> > >> >> to
> > >> >>> make an "Image" of whatever we end up with on
> > whatever server we
> > >> end up
> > >> >>> using so if the image can be copied and used on
> > other servers.
> > >> I'm not
> > >> >>> exactly sure how to do that with Azure, which
> hosts
> > my CI
> > >> server. I will
> > >> >>> spend a few more minutes researching that.
> > >> >>>
> > >> >>> I could not quickly find any way to get a free VM
> > on Azure or AWS
> > >> that
> > >> >>> isn't a free-trial-start-paying-after-a-year. So,
> > unless someone
> > >> comes
> > >> >> up
> > >> >>> with a free server we can use "forever", I'm going
> > to just start
> > >> with my
> > >> >>> Azure VM.
> > >> >>>
> > >> >>> -Alex
> > >> >>>
> > >> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > >> wrote:
> > >> >>>
> > >> >>> Hi.
> > >> >>>
> > >> >>> the plan sounds very good to me. Just my 2
> > thoughts on this:
> > >> >>>
> > >> >>> 1.- As I was reading I was thinking as well on
> > something like
> > >> Docker
> > >> >>> and
> > >> >>> see Om as well thinking on the same. Maybe is
> > the way to this
> > >> with
> > >> >> the
> > >> >>> actual technology. Seems VMs are stepping out a
> > bit this days
> > >> in
> > >> >> favor
> > >> >>> of
> > >> >>> things like Docker. Maybe the same did Git over
> > Svn, and today
> > >> Svn is
> > >> >>> an
> > >> >>> old remembrance. I must say that I have no
> > experience with
> > >> Docker, so
> > >> >>> doing
> > >> >>> that will require acquire that knowledge, but
> > seems it could
> > >> be worth
> > >> >>> it.
> > >> >>>
> > >> >>> 2.- Maybe is not possible, but I want to
> propose
> > to do this
> > >> work I a
> > >> >>> separate branch, so it could be in parallel to
> > other
> > >> developments. I
> > >> >>> think
> > >> >>> work over develop is practical if there's
> > something tiny that
> > >> could
> > >> >> be
> > >> >>> done
> > >> >>> in a commit. But as we need more than one, or
> is
> > a long
> > >> process (like
> > >> >>> this), chances are to make develop branch
> > unstable and even
> > >> for some
> > >> >>> days.
> > >> >>> I think we should try to avoid that scenario,
> > and branches are
> > >> the
> > >> >> best
> > >> >>> way. If we do this way, we'll benefit of more
> > reliable develop
> > >> >> branch.
> > >> >>>
> > >> >>> Thanks and good to know of this plan :)
> > >> >>>
> > >> >>> Carlos
> > >> >>>
> > >> >>>
> > >> >>> El mar., 5 feb. 2019 a las 23:19, Harbs (<
> > >> harbs.lists@gmail.com>)
> > >> >>> escribió:
> > >> >>>
> > >> >>>> I’ve never used Docker myself, but that might be
> a
> > good plan.
> > >> >>>>
> > >> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash
> Muppirala <
> > >> >>> bigosmallm@gmail.com>
> > >> >>>> wrote:
> > >> >>>>>
> > >> >>>>> I was wondering if we can use docker images to
> > setup and seal
> > >> the
> > >> >>> RM
> > >> >>>>> environment. Then other RMs simply need to run
> > the image
> > >> locally
> > >> >>> and run
> > >> >>>>> the release scripts. Might be easier. If folks
> > like this plan,
> > >> >> I
> > >> >>> can
> > >> >>>> try
> > >> >>>>> to put something together.
> > >> >>>>>
> > >> >>>>> Thanks,
> > >> >>>>> Om
> > >> >>>>>
> > >> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <
> > harbs.lists@gmail.com>
> > >> >>> wrote:
> > >> >>>>>
> > >> >>>>>> In a recent discussion, it looks like other
> > projects have
> > >> gotten
> > >> >>>> resources
> > >> >>>>>> from AWS.
> > >> >>>>>>
> > >> >>>>>> Whatever service we use, could setup a “shared”
> > Royale account
> > >> >>> that all
> > >> >>>>>> PMC members could have access to.
> > >> >>>>>>
> > >> >>>>>> I don’t know if there’s some way we could
> > leverage Gitlab’s
> > >> >>> integration
> > >> >>>>>> pipelines
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=ZrqmL9%2B0oXasDm4aDW2q8K%2F%2BEkSc17zQerzJ4m%2BM7lU%3D&reserved=0
> > >> >>> <
> > >> >>>>>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=ZrqmL9%2B0oXasDm4aDW2q8K%2F%2BEkSc17zQerzJ4m%2BM7lU%3D&reserved=0
> > >> >>>>
> > >> >>>>>>
> > >> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
> > >> >> <aharui@adobe.com.INVALID
> > >> >>>>
> > >> >>>>>> wrote:
> > >> >>>>>>>
> > >> >>>>>>> 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" <
> > >> >> piotrzarzycki21@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.lists@gmail.com
> > >> >>> wrote:
> > >> >>>>>>>
> > >> >>>>>>>> A big +1 from me!
> > >> >>>>>>>>
> > >> >>>>>>>> Looking forward!
> > >> >>>>>>>>
> > >> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
> > >> >>> <ah...@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
> > >> >>>>>>>>>
> > >> >>>>>>>>
> > >> >>>>>>>>
> > >> >>>>>>>
> > >> >>>>>>>
> > >> >>>>>>
> > >> >>>>>>
> > >> >>>>
> > >> >>>>
> > >> >>>
> > >> >>> --
> > >> >>> Carlos Rovira
> > >> >>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=egeH1lqxrifO9sWYd0PO67pKuQP6Riv0N2tEDf9rriA%3D&reserved=0
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>
> > >> >
> > >> >
> > >> > --
> > >> > Carlos Rovira
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=egeH1lqxrifO9sWYd0PO67pKuQP6Riv0N2tEDf9rriA%3D&reserved=0
> > >> >
> > >> >
> > >>
> > >>
> > >>
> > >>
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
Re: 0.9.6 Release
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Alex,
What is happen with our Jenkins server - is it switched OFF for purpose ? I
see that it is happen every day. Today I'm not sure how it launch again.
Thanks,
Piotr
czw., 23 maj 2019 o 18:54 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> It has turned out to be harder than expected to get the same binaries on
> Mac and Win. I now have the identical binaries for royale-compiler and
> royale-typedefs Maven artifacts and am starting on royale-asjs. I might
> get lucky and the changes that fixed royale-typedefs SWCs will magically
> get the royale-asjs SWCs to match. Then we have to make the Ant artifacts
> match.
>
> There have been a lot of distractions in my non-work life which has also
> impeded progress. I hope to make much progress this coming week and if
> we're lucky, I will be asking for a volunteer (or volunteers) to test drive
> all of this stuff and be the RM for 0.9.6. I am not going to be the RM.
>
> -Alex
>
> On 5/23/19, 9:39 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> Hi Alex,
>
> It's been a while since you have started effort with automating build.
> Where are you with that ? Are we closer to started 0.9.6. Do you need
> any
> help with this ?
>
> Thanks,
> Piotr
>
> wt., 2 kwi 2019 o 19:30 Alex Harui <ah...@adobe.com.invalid>
> napisał(a):
>
> > Update:
> >
> > In order to make verification of binary release packages created on
> the
> > server easier, I have made changes to our build scripts and tools to
> try to
> > generate reproducible binaries. I've seen two different builds
> compare on
> > my Mac. The next challenge will be to see if the server can build a
> > package on Windows that will compare on Mac.
> >
> > One of the changes I needed to make is to JBurg. The version of
> JBurg we
> > use generates method names including a hash that doesn't reproduce
> the same
> > name each time. I have changes to JBurg ready, however JBurg is
> currently
> > under CPL which is category B. We only need one file, we don't need
> or
> > want all of JBurg at this time. The one JBurg file is jointly owned
> by
> > Adobe and Tom Harwood. I've contact Tom and he will be filing an
> ICLA and
> > has given me permission to commit the lines he owns in that one file.
> >
> > This is the revision of the file that will be donated by Tom/Adobe.
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095&sdata=1p0EhJm%2Be7CdkNlE5MHMEJ9EoPINgBGKVU6hlE8C0kQ%3D&reserved=0
> >
> > Once this file goes in with the changes to keep the method names the
> same,
> > there will be more tweaks to the release tasks and then we can try
> cutting
> > a release. I'm thinking we'll be at that point in early May, so now
> is the
> > time to get stuff in for the 0.9.6 release.
> >
> > Thanks,
> > -Alex
> >
> > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >
> > I would much rather have others find and fix issues themselves.
> That
> > way, more people than just me will know how to maintain the system.
> It
> > actually turns out that, IMO, a group of people can work on the
> release.
> > There are 14 steps. Literally, 14 different people could execute
> one step
> > each.
> >
> > My 2 cents,
> > -Alex
> >
> > On 3/8/19, 2:13 AM, "Carlos Rovira" <ca...@apache.org>
> wrote:
> >
> > Hi Alex,
> >
> > amazing work! congrats to reach to this point! :)
> >
> > I need to put my head on all of this, but count on me to be
> a RM.
> > I think
> > the best thing should be that you be the first RM to try
> your own
> > development at least for the first time, and then the rest
> of us
> > will
> > follow you on the next releases. With all this on place we
> maybe
> > could
> > release once a month or every two months...
> >
> > Thanks for doing this :)
> >
> > Carlos
> >
> >
> > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > (<ah...@adobe.com.invalid>)
> > escribió:
> >
> > > OK, I've now seen Jenkins perform the steps to build the
> release
> > > artifacts. Folks interested in Docker-izing the steps are
> > welcome to look
> > > at the jobs on the "Royale Release" tab on the CI server.
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095&sdata=OtDqx0O91trBGYlhEimqYdhTiJXhsCw1YRe6uaV9OF8%3D&reserved=0
> > >
> > > These steps assume that the RM can run the basic Maven and
> Ant
> > build on
> > > the RM's computer. I think that's a fair requirement since
> all
> > of us on the
> > > PMC need to able to do that to build the RC in order to
> vote on
> > it.
> > > Jenkins does other tasks like run the Maven release plugin
> > steps.
> > >
> > > Currently that results in binaries on Jenkins that are
> > downloaded to the
> > > RM's computer. These binaries need to be verified by the
> RM
> > which is the
> > > next phase I will be starting on now. The RM verifies the
> bits
> > and then
> > > PGP signs them. And then the bits are uploaded off the
> RM's
> > computer to
> > > Maven Staging or dist.a.o/dev. If that uploading turns
> out to
> > be a point
> > > of failure, we have the option of having Jenkins upload
> the big
> > files and
> > > have the RM only upload PGP signature files. Or finding a
> way
> > for Jenkins
> > > to get the signature files from the RM. The uploads
> worked fine
> > for me,
> > > but then again, so did the old script's uploads.
> > >
> > > Therefore, once I get the binary verification phase
> completed, I
> > think
> > > someone other than me should be the RM and try to use these
> > steps to
> > > generate the release and help debug the process for the
> next
> > RM. So,
> > > please try to carve out some time to be the RM. One
> advantage
> > of doing
> > > most of the work on Jenkins is that it frees up my
> computer to
> > do other
> > > things while Jenkins is cranking away.
> > >
> > > I think we're at least a week away from binary
> verification,
> > maybe two, so
> > > it is time to start thinking about what is going in this
> release.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 3/7/19, 4:15 PM, "Alex Harui" <aharui@adobe.com.INVALID
> >
> > wrote:
> > >
> > > In case you haven't guessed, I'm testing out Jenkins
> and its
> > ability
> > > to create the artifacts and send emails. Please ignore any
> > email that
> > > looks like a vote or discuss thread.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 2/10/19, 8:44 PM, "Alex Harui"
> <ah...@adobe.com.INVALID>
> > wrote:
> > >
> > > Om,
> > >
> > > Well, that's what I used for the last release.
> I'm sure
> > there is
> > > probably some inaccuracy in it.
> > >
> > > That said, I'm abandoning that document and taking
> a new
> > angle
> > > because that document presumed that the release manager was
> > trying to
> > > create a release on his/her computer. I've given up on
> that and
> > working on
> > > making releases from a shared computer for the reasons I've
> > stated
> > > upthread. I hope to make some progress on that this week.
> > >
> > > The key difference is that the new angle does not
> > presume that you
> > > have Git SSH and PGP signatures all set up on some
> computer. I
> > have not
> > > looked into how Docker would handle that. You certainly
> > wouldn't want the
> > > Docker image to contain your SSH or PGP keys/creds. And
> if the
> > Docker
> > > image doesn't, then that is another stumbling block for
> future
> > RMs.
> > >
> > > The other key difference is that the old script
> presumed
> > you could
> > > create the 3 release in 3 huge "easy" steps. We've seen
> that is
> > only true
> > > for me. So the new angle creates many discrete steps
> managed by
> > Jenkins.
> > >
> > > So, it is up to you to decide what you want to
> > "Docker-ize". You
> > > can try to Docker-ize the current 3 big steps, so RMs can
> try to
> > run it on
> > > their systems, but I'd bet they will just faiI due to
> network
> > issues. I
> > > would be interested in using Docker to make each of these
> many
> > discrete
> > > steps portable to another server. I'm not going to
> involve
> > Docker at this
> > > point. My main goal is just to see if I can create a
> workflow
> > of many
> > > discrete steps that isn't horribly painful. Once we see
> what
> > these steps
> > > turn out to be, then we can worry about server portability
> of
> > those steps.
> > >
> > > Either way, we want to know about running
> > Browser+Selenium for
> > > sure. And maybe FlashPlayerDebugger or AIR. I would want
> to
> > know, for
> > > example, how you debug a failing checkintest in a Docker
> > container.
> > >
> > > Thanks,
> > > -Alex
> > >
> > >
> > > On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <
> > bigosmallm@gmail.com>
> > > wrote:
> > >
> > > Alex,
> > >
> > > Just to be clear, I am following the steps
> from here
> > to try
> > > and setup a
> > > docker container.
> > >
> > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095&sdata=M3ckCTAILe%2FVyVIeMmV3tybH8JiVq6cy7PmvCSkH3Pk%3D&reserved=0
> > >
> > > Is this doc up to date?
> > >
> > > Thanks,
> > > Om
> > >
> > > On Wed, Feb 6, 2019 at 12:02 PM OmPrakash
> Muppirala <
> > > bigosmallm@gmail.com>
> > > wrote:
> > >
> > > > One approach is to have each step in the
> process
> > spin up a
> > > docker image.
> > > > And use docker-compose to run each step.
> All the
> > images can
> > > be made to
> > > > share a common volume where all the
> artifacts are
> > stored
> > > across steps.
> > > >
> > > > You are right about the networking issue
> though.
> > Any
> > > network related
> > > > failure that occurs on the host machine will
> most
> > likely
> > > occur in the
> > > > docker container. Although, I am not clear
> how we
> > can
> > > guarantee that the
> > > > same issues will not occur on the Jenkins
> server.
> > I mean,
> > > what is special
> > > > about the Jenkins server that makes it
> immune to
> > these
> > > networking issues?
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Wed, Feb 6, 2019 at 11:48 AM Alex Harui
> > > <ah...@adobe.com.invalid>
> > > > wrote:
> > > >
> > > >> Again, I don't know anything about Docker,
> but
> > before we
> > > spend a lot of
> > > >> time on Docker, I also want to point out
> that the
> > process
> > > to create a
> > > >> release cannot really be thought of as "one
> > application".
> > > It will be a
> > > >> series of "steps" to run. How many steps
> > depends on
> > > whether we think we
> > > >> can isolate enough stuff via Docker to be
> able to
> > run
> > > Docker on the RM's
> > > >> computer instead of some shared computer.
> On a
> > shared
> > > computer there will
> > > >> be dozens of steps because the RM will need
> to
> > enter
> > > passwords to commit
> > > >> stuff. On a local computer I guess the RM
> can
> > supply
> > > passwords but I think
> > > >> there will be stopping points where the
> Maven
> > artifacts are
> > > deployed and
> > > >> the staging repo is closed, and another
> stopping
> > point for
> > > the vote. It
> > > >> seems like Docker works by downloading
> > dependencies. Given
> > > that the
> > > >> problem the RMs had last time involved
> downloads
> > and
> > > uploads, why do we
> > > >> think Docker will really solve this for
> creating
> > releases
> > > on local machines?
> > > >>
> > > >> The reason to do this on a shared machine
> is so
> > that new
> > > RMs don't have
> > > >> to do as much setup. But then I wonder
> about the
> > > efficiency of kicking off
> > > >> that many Docker images. Jenkins can
> manage that
> > already.
> > > Does Docker
> > > >> have some sort of similar Dashboard or
> would we
> > use Jenkins
> > > to kick off
> > > >> Docker steps? I can't quite picture what
> is the
> > outermost
> > > >> control/dashboard.
> > > >>
> > > >> -Alex
> > > >>
> > > >> On 2/6/19, 11:03 AM, "Harbs" <
> > harbs.lists@gmail.com> wrote:
> > > >>
> > > >> A quick search turns up this:
> > > >>
> > > >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095&sdata=qxK2JWFPpxzEBAlERUEYahRC1sB02Nbo8YnNBEchWPk%3D&reserved=0
> > > >> <
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095&sdata=qxK2JWFPpxzEBAlERUEYahRC1sB02Nbo8YnNBEchWPk%3D&reserved=0
> > > >> >
> > > >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095&sdata=NplRCecGDitm7JlODUJPaNi294kXdr2UVVvhm%2BuPFQ0%3D&reserved=0
> > > >> <
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=d9WGdfMgG%2BeOXY18VGdFon39GxraphfngvhrbnsfwUQ%3D&reserved=0
> > > >> >
> > > >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=Rzs4ZWB8ZsALg%2FCjfyRXNtQqfgZcF70eGrnbZDQMkWo%3D&reserved=0
> > > >> <
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=Rzs4ZWB8ZsALg%2FCjfyRXNtQqfgZcF70eGrnbZDQMkWo%3D&reserved=0
> > > >> >
> > > >>
> > > >> > On Feb 6, 2019, at 8:59 PM, Alex Harui
> > > <ah...@adobe.com.INVALID>
> > > >> wrote:
> > > >> >
> > > >> > Thanks for volunteering to try it
> Om. IMO,
> > even more
> > > important
> > > >> than Firefox+Flash is
> SomeBrowser+Selenium. We
> > may also
> > > need to run Adobe
> > > >> AIR's adb. We could probably turn off the
> Flash
> > tests or
> > > replace Flash
> > > >> with AIR.
> > > >> >
> > > >> > Thanks,
> > > >> > -Alex
> > > >> >
> > > >> > On 2/6/19, 10:54 AM, "Carlos Rovira" <
> > > carlosrovira@apache.org>
> > > >> wrote:
> > > >> >
> > > >> > Hi Om, that would be great!
> waiting for
> > your
> > > experience with a
> > > >> that! :)
> > > >> >
> > > >> > El mié., 6 feb. 2019 a las 19:31,
> > OmPrakash
> > > Muppirala (<
> > > >> bigosmallm@gmail.com>)
> > > >> > escribió:
> > > >> >
> > > >> >> Yes, I agree with Alex about not
> being
> > able to run
> > > UI out of docker
> > > >> >> containers. I never thought of the
> > checkintests
> > > when I made the
> > > >> >> suggestion.
> > > >> >>
> > > >> >> The firefox-flash image that Yishay
> > pointed out
> > > looks promising.
> > > >> I will
> > > >> >> poke around with it and see if that
> works
> > for us.
> > > >> >>
> > > >> >> Thanks,
> > > >> >> Om
> > > >> >>
> > > >> >> On Wed, Feb 6, 2019 at 12:41 AM
> Yishay
> > Weiss <
> > > >> yishayjobs@hotmail.com>
> > > >> >> wrote:
> > > >> >>
> > > >> >>> I’ll let Om or someone else with
> docker
> > experience
> > > tell us if
> > > >> this [1] is
> > > >> >>> relevant.
> > > >> >>>
> > > >> >>>
> > > >> >>>
> > > >> >>> [1]
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=dxaDA7W1gty6zgFaB8HbmRFj5BW8v8JFH5icojRgQic%3D&reserved=0
> > > >> >>>
> > > >> >>>
> > > >> >>>
> > > >> >>> ________________________________
> > > >> >>> From: Alex Harui
> <aharui@adobe.com.INVALID
> > >
> > > >> >>> Sent: Wednesday, February 6, 2019
> > 10:05:54 AM
> > > >> >>> To: dev@royale.apache.org
> > > >> >>> Subject: Re: 0.9.6 Release
> > > >> >>>
> > > >> >>> I don't anything about docker, but
> in 15
> > minutes of
> > > reading I ran
> > > >> into
> > > >> >>> this:
> > > >> >>>
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=U1sknyW%2FIRwPeQperIpjyLOE%2B52%2FmTB2IDpNwyG6jz4%3D&reserved=0
> > > >> >>>
> > > >> >>> Which says: Docker can't " Run
> > applications with
> > > graphical
> > > >> interfaces".
> > > >> >>> If you want Royale to use Docker for
> > releases, show
> > > that it can
> > > >> run
> > > >> >>> checkintests with Flash and the
> Browser.
> > Then I
> > > will look into
> > > >> it more.
> > > >> >>>
> > > >> >>> The highest level goal is to make
> it as
> > easy as
> > > possible for
> > > >> someone to
> > > >> >>> volunteer to be an RM. Any
> requirement
> > of "install
> > > this (Docker,
> > > >> etc) on
> > > >> >>> your computer" is, IMO, another
> barrier
> > to entry.
> > > Yeah, RMs will
> > > >> have to
> > > >> >>> have Maven installed and maybe Ant,
> but
> > you should
> > > already have
> > > >> those
> > > >> >>> installed to be a committer/PMC
> member.
> > > >> >>>
> > > >> >>> That said, a good takeaway from the
> > Docker idea is
> > > to try to find
> > > >> a way
> > > >> >> to
> > > >> >>> make an "Image" of whatever we end
> up
> > with on
> > > whatever server we
> > > >> end up
> > > >> >>> using so if the image can be copied
> and
> > used on
> > > other servers.
> > > >> I'm not
> > > >> >>> exactly sure how to do that with
> Azure,
> > which hosts
> > > my CI
> > > >> server. I will
> > > >> >>> spend a few more minutes
> researching that.
> > > >> >>>
> > > >> >>> I could not quickly find any way to
> get a
> > free VM
> > > on Azure or AWS
> > > >> that
> > > >> >>> isn't a
> > free-trial-start-paying-after-a-year. So,
> > > unless someone
> > > >> comes
> > > >> >> up
> > > >> >>> with a free server we can use
> "forever",
> > I'm going
> > > to just start
> > > >> with my
> > > >> >>> Azure VM.
> > > >> >>>
> > > >> >>> -Alex
> > > >> >>>
> > > >> >>> On 2/5/19, 10:59 PM, "Carlos
> Rovira" <
> > > carlosrovira@apache.org>
> > > >> wrote:
> > > >> >>>
> > > >> >>> Hi.
> > > >> >>>
> > > >> >>> the plan sounds very good to me.
> Just
> > my 2
> > > thoughts on this:
> > > >> >>>
> > > >> >>> 1.- As I was reading I was
> thinking as
> > well on
> > > something like
> > > >> Docker
> > > >> >>> and
> > > >> >>> see Om as well thinking on the
> same.
> > Maybe is
> > > the way to this
> > > >> with
> > > >> >> the
> > > >> >>> actual technology. Seems VMs are
> > stepping out a
> > > bit this days
> > > >> in
> > > >> >> favor
> > > >> >>> of
> > > >> >>> things like Docker. Maybe the
> same did
> > Git over
> > > Svn, and today
> > > >> Svn is
> > > >> >>> an
> > > >> >>> old remembrance. I must say that
> I
> > have no
> > > experience with
> > > >> Docker, so
> > > >> >>> doing
> > > >> >>> that will require acquire that
> > knowledge, but
> > > seems it could
> > > >> be worth
> > > >> >>> it.
> > > >> >>>
> > > >> >>> 2.- Maybe is not possible, but I
> want
> > to propose
> > > to do this
> > > >> work I a
> > > >> >>> separate branch, so it could be
> in
> > parallel to
> > > other
> > > >> developments. I
> > > >> >>> think
> > > >> >>> work over develop is practical if
> > there's
> > > something tiny that
> > > >> could
> > > >> >> be
> > > >> >>> done
> > > >> >>> in a commit. But as we need more
> than
> > one, or is
> > > a long
> > > >> process (like
> > > >> >>> this), chances are to make
> develop
> > branch
> > > unstable and even
> > > >> for some
> > > >> >>> days.
> > > >> >>> I think we should try to avoid
> that
> > scenario,
> > > and branches are
> > > >> the
> > > >> >> best
> > > >> >>> way. If we do this way, we'll
> benefit
> > of more
> > > reliable develop
> > > >> >> branch.
> > > >> >>>
> > > >> >>> Thanks and good to know of this
> plan :)
> > > >> >>>
> > > >> >>> Carlos
> > > >> >>>
> > > >> >>>
> > > >> >>> El mar., 5 feb. 2019 a las 23:19,
> > Harbs (<
> > > >> harbs.lists@gmail.com>)
> > > >> >>> escribió:
> > > >> >>>
> > > >> >>>> I’ve never used Docker myself, but
> that
> > might be a
> > > good plan.
> > > >> >>>>
> > > >> >>>>> On Feb 6, 2019, at 12:07 AM,
> OmPrakash
> > Muppirala <
> > > >> >>> bigosmallm@gmail.com>
> > > >> >>>> wrote:
> > > >> >>>>>
> > > >> >>>>> I was wondering if we can use
> docker
> > images to
> > > setup and seal
> > > >> the
> > > >> >>> RM
> > > >> >>>>> environment. Then other RMs
> simply
> > need to run
> > > the image
> > > >> locally
> > > >> >>> and run
> > > >> >>>>> the release scripts. Might be
> easier.
> > If folks
> > > like this plan,
> > > >> >> I
> > > >> >>> can
> > > >> >>>> try
> > > >> >>>>> to put something together.
> > > >> >>>>>
> > > >> >>>>> Thanks,
> > > >> >>>>> Om
> > > >> >>>>>
> > > >> >>>>> On Tue, Feb 5, 2019 at 1:40 PM
> Harbs <
> > > harbs.lists@gmail.com>
> > > >> >>> wrote:
> > > >> >>>>>
> > > >> >>>>>> In a recent discussion, it looks
> like
> > other
> > > projects have
> > > >> gotten
> > > >> >>>> resources
> > > >> >>>>>> from AWS.
> > > >> >>>>>>
> > > >> >>>>>> Whatever service we use, could
> setup a
> > “shared”
> > > Royale account
> > > >> >>> that all
> > > >> >>>>>> PMC members could have access to.
> > > >> >>>>>>
> > > >> >>>>>> I don’t know if there’s some way
> we
> > could
> > > leverage Gitlab’s
> > > >> >>> integration
> > > >> >>>>>> pipelines
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=DPP6VhjSgo5mGugE1xxzMK7z3Q0aXz%2FSi4QJr3sO3z0%3D&reserved=0
> > > >> >>> <
> > > >> >>>>>>
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=DPP6VhjSgo5mGugE1xxzMK7z3Q0aXz%2FSi4QJr3sO3z0%3D&reserved=0
> > > >> >>>>
> > > >> >>>>>>
> > > >> >>>>>>> On Feb 5, 2019, at 11:33 PM,
> Alex
> > Harui
> > > >> >> <aharui@adobe.com.INVALID
> > > >> >>>>
> > > >> >>>>>> wrote:
> > > >> >>>>>>>
> > > >> >>>>>>> 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" <
> > > >> >> piotrzarzycki21@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.lists@gmail.com
> > > >> >>> wrote:
> > > >> >>>>>>>
> > > >> >>>>>>>> A big +1 from me!
> > > >> >>>>>>>>
> > > >> >>>>>>>> Looking forward!
> > > >> >>>>>>>>
> > > >> >>>>>>>>> On Feb 5, 2019, at 9:34 PM,
> Alex
> > Harui
> > > >> >>> <ah...@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
> > > >> >>>>>>>>>
> > > >> >>>>>>>>
> > > >> >>>>>>>>
> > > >> >>>>>>>
> > > >> >>>>>>>
> > > >> >>>>>>
> > > >> >>>>>>
> > > >> >>>>
> > > >> >>>>
> > > >> >>>
> > > >> >>> --
> > > >> >>> Carlos Rovira
> > > >> >>>
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=blcYO7%2F37ZW%2FEBFhqN7aIqnfGdDEz2idac%2BbrGa5cTE%3D&reserved=0
> > > >> >>>
> > > >> >>>
> > > >> >>>
> > > >> >>
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Carlos Rovira
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=blcYO7%2F37ZW%2FEBFhqN7aIqnfGdDEz2idac%2BbrGa5cTE%3D&reserved=0
> > > >> >
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907548084&sdata=H6LPsS7BpzoZiaRUEf4n3XdEpvTWQlzIUknJaXFZBGo%3D&reserved=0
> >
> >
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907548084&sdata=f4S4MDFSY1Y5%2Fstuucdc4KqI94YJWwmcNas%2F8GHevCA%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907548084&sdata=f4S4MDFSY1Y5%2Fstuucdc4KqI94YJWwmcNas%2F8GHevCA%3D&reserved=0
> >*
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: 0.9.6 Release
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex!
Congrats for this milestone! In doing we'll be doing an important step! :)
Now is time for the rest of us to don't stop on docs to make 1.0 be
available soon! :))
Thanks!
El mar., 11 jun. 2019 a las 8:35, Piotr Zarzycki (<pi...@gmail.com>)
escribió:
> Greg,
>
> It looks like Ant compiler build is working fine. I'm waiting now for JS
> only build of framework to be finished.
>
> Thanks,
> Piotr
>
> On Tue, Jun 11, 2019, 8:31 AM Greg Dove <gr...@gmail.com> wrote:
>
> > Thanks for clarifying Piotr. That one at least worked it seems.
> > I saw the problem elsewhere and first time it was because the compiler
> > build had required changes and did not complete before the framework.
> > The others have some issues, but I don't think it is related to my latest
> > changes , because it seems to be the same issue as previous fails. I will
> > try to figure those out tomorrow some time if I can.
> >
> > On Tue, Jun 11, 2019 at 5:08 PM Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> > wrote:
> >
> > > Greg,
> > >
> > > I was thinking about ant build on Jenkins [1]. I didn't check Maven
> build
> > > in a while.
> > >
> > > [1]
> > >
> > >
> >
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/changes
> > >
> > > Thanks,
> > > Piotr
> > >
> > >
> > > On Tue, Jun 11, 2019, 6:48 AM Greg Dove <gr...@gmail.com> wrote:
> > >
> > > > Piotr, I hope I addressed the issue, but waiting to see...
> > > > It looks like it has been unstable for last 7 days , am I reading
> that
> > > > right? https://builds.apache.org/job/Royale-asjs/
> > > >
> > > >
> > > > On Tue, Jun 11, 2019 at 4:30 PM Greg Dove <gr...@gmail.com>
> wrote:
> > > >
> > > > > Working on it!
> > > > >
> > > > >
> > > > > On Tue, Jun 11, 2019 at 4:29 PM Piotr Zarzycki <
> > > > piotrzarzycki21@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Hi Greg,
> > > > >>
> > > > >> After your merge the goal should be that build on Jenkins is
> working
> > > > fine.
> > > > >> Please make sure that is happen.
> > > > >>
> > > > >> Thanks,
> > > > >> Piotr
> > > > >>
> > > > >> On Tue, Jun 11, 2019, 5:32 AM Greg Dove <gr...@gmail.com>
> > wrote:
> > > > >>
> > > > >> > I will stick with the plan of single commit, I think it should
> be
> > > > easier
> > > > >> > for you if there are any conflicts.
> > > > >> > Last build testing is running now in local develop. I will push
> > > after
> > > > >> > that...
> > > > >> >
> > > > >> > On Tue, Jun 11, 2019 at 3:15 PM Greg Dove <gr...@gmail.com>
> > > > wrote:
> > > > >> >
> > > > >> > >
> > > > >> > > Thanks Alex, I was planning to merge this as a single squashed
> > > > commit,
> > > > >> > > because it isolates all the changes to a single commit (but
> this
> > > > will
> > > > >> > mean
> > > > >> > > there are many changes in one hit).
> > > > >> > > Do you have a preference in terms of how easy it will make
> > things
> > > > for
> > > > >> > you?
> > > > >> > >
> > > > >> > >
> > > > >> > > On Tue, Jun 11, 2019 at 3:07 PM Alex Harui
> > > <aharui@adobe.com.invalid
> > > > >
> > > > >> > > wrote:
> > > > >> > >
> > > > >> > >> OK, I will wait to see your commit emails. I will do some
> > other
> > > > >> things
> > > > >> > >> like the wiki doc.
> > > > >> > >>
> > > > >> > >> -Alex
> > > > >> > >>
> > > > >> > >> On 6/10/19, 8:06 PM, "Greg Dove" <gr...@gmail.com>
> wrote:
> > > > >> > >>
> > > > >> > >> Hi Alex, I guess you might be back on Royale about now.
> > Just
> > > a
> > > > >> heads
> > > > >> > >> up: I
> > > > >> > >> am about 20-30 mins max from merging in what I have. Hope
> > > > that's
> > > > >> > still
> > > > >> > >> ok... please let me know if not.
> > > > >> > >> Thanks,
> > > > >> > >> -Greg
> > > > >> > >>
> > > > >> > >>
> > > > >> > >> On Tue, Jun 11, 2019 at 7:51 AM Greg Dove <
> > > greg.dove@gmail.com
> > > > >
> > > > >> > >> wrote:
> > > > >> > >>
> > > > >> > >> >
> > > > >> > >> > Thanks Alex - I'll try to hit the window, much
> > appreciated!
> > > > >> > >> >
> > > > >> > >> >
> > > > >> > >> > On Tue, Jun 11, 2019 at 6:57 AM Alex Harui
> > > > >> > <aharui@adobe.com.invalid
> > > > >> > >> >
> > > > >> > >> > wrote:
> > > > >> > >> >
> > > > >> > >> >> Hi Greg,
> > > > >> > >> >>
> > > > >> > >> >> It turns out I have a "split shift" today. I'm
> stopping
> > > > work
> > > > >> for
> > > > >> > >> the
> > > > >> > >> >> next 7 or 8 hours then will get around to the merge.
> So
> > > if
> > > > >> you
> > > > >> > >> can get
> > > > >> > >> >> your changes merged in that amount of time, then I
> will
> > > wait
> > > > >> for
> > > > >> > >> you and
> > > > >> > >> >> deal with any merge conflicts (there are almost
> certain
> > to
> > > > be
> > > > >> > >> some).
> > > > >> > >> >>
> > > > >> > >> >> -Alex
> > > > >> > >> >>
> > > > >> > >> >> On 6/10/19, 11:46 AM, "Greg Dove" <
> greg.dove@gmail.com>
> > > > >> wrote:
> > > > >> > >> >>
> > > > >> > >> >> Alex, slightly OT, but in terms of coordination:
> > fyi I
> > > > am
> > > > >> > also
> > > > >> > >> very
> > > > >> > >> >> close
> > > > >> > >> >> to merging the language improvements branch into
> > > > develop.
> > > > >> As
> > > > >> > I
> > > > >> > >> already
> > > > >> > >> >> mentioned elsewhere, I was hoping to do that a
> > couple
> > > of
> > > > >> days
> > > > >> > >> back,
> > > > >> > >> >> but
> > > > >> > >> >> some recent things also took me a little longer
> than
> > > > >> expected
> > > > >> > >> (I have
> > > > >> > >> >> additional local changes/fixes not yet in remote
> > > branch)
> > > > >> . I
> > > > >> > >> was
> > > > >> > >> >> planning
> > > > >> > >> >> to merge that today also.
> > > > >> > >> >>
> > > > >> > >> >> However, I will wait until after your merge, so
> I'm
> > > > hoping
> > > > >> > you
> > > > >> > >> can get
> > > > >> > >> >> yours in today (if not, I will wait). I will
> > probably
> > > > put
> > > > >> > mine
> > > > >> > >> in as a
> > > > >> > >> >> squashed commit after yours.
> > > > >> > >> >>
> > > > >> > >> >>
> > > > >> > >> >> On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <
> > > > >> > >> >> piotrzarzycki21@gmail.com>
> > > > >> > >> >> wrote:
> > > > >> > >> >>
> > > > >> > >> >> > Hi Alex,
> > > > >> > >> >> >
> > > > >> > >> >> > Many thanks for that! I will try to be RM. I
> will
> > > have
> > > > >> some
> > > > >> > >> >> dedicated time
> > > > >> > >> >> > for that. I will wait for your instruction and
> > merge
> > > > to
> > > > >> > >> develop.
> > > > >> > >> >> >
> > > > >> > >> >> > Thanks,
> > > > >> > >> >> > Piotr
> > > > >> > >> >> >
> > > > >> > >> >> >
> > > > >> > >> >> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
> > > > >> > >> <ah...@adobe.com.invalid>
> > > > >> > >> >> wrote:
> > > > >> > >> >> >
> > > > >> > >> >> > > Well, that turned out to be much more
> > > time-consuming
> > > > >> > than I
> > > > >> > >> >> expected, but
> > > > >> > >> >> > > we can now create identical release artifacts
> on
> > > Mac
> > > > >> and
> > > > >> > >> Win. I
> > > > >> > >> >> am
> > > > >> > >> >> > hopeful
> > > > >> > >> >> > > this effort will pay off not only now in
> having
> > > > other
> > > > >> > folks
> > > > >> > >> >> generate
> > > > >> > >> >> > > releases, but also in the future if signed
> > > binaries
> > > > >> > become
> > > > >> > >> a
> > > > >> > >> >> requirement.
> > > > >> > >> >> > >
> > > > >> > >> >> > > There continues to be a lot of distractions in
> > my
> > > > life
> > > > >> > >> that can
> > > > >> > >> >> cause
> > > > >> > >> >> > > delays, but I hope to merge the
> release_practice
> > > > >> branches
> > > > >> > >> into
> > > > >> > >> >> develop
> > > > >> > >> >> > over
> > > > >> > >> >> > > the next day or two and figure out where in
> the
> > > wiki
> > > > >> to
> > > > >> > >> document
> > > > >> > >> >> the
> > > > >> > >> >> > > release process. So, now is the time for one
> or
> > > > more
> > > > >> > >> people to
> > > > >> > >> >> step up
> > > > >> > >> >> > to
> > > > >> > >> >> > > be the RMs for 0.9.6 and help debug and
> improve
> > > the
> > > > >> > >> process.
> > > > >> > >> >> > >
> > > > >> > >> >> > > I am going to try very hard not to "own" the
> > > > >> process. If
> > > > >> > >> >> something goes
> > > > >> > >> >> > > wrong, I am going to ask others to try to
> debug
> > > and
> > > > >> fix
> > > > >> > it
> > > > >> > >> first
> > > > >> > >> >> because
> > > > >> > >> >> > it
> > > > >> > >> >> > > is in the project's best interests for others
> to
> > > > truly
> > > > >> > >> understand
> > > > >> > >> >> how
> > > > >> > >> >> > this
> > > > >> > >> >> > > stuff works.
> > > > >> > >> >> > >
> > > > >> > >> >> > > Thanks,
> > > > >> > >> >> > > -Alex
> > > > >> > >> >> > >
> > > > >> > >> >> > > On 5/23/19, 9:54 AM, "Alex Harui"
> > > > >> > <aharui@adobe.com.INVALID
> > > > >> > >> >
> > > > >> > >> >> wrote:
> > > > >> > >> >> > >
> > > > >> > >> >> > > It has turned out to be harder than
> expected
> > > to
> > > > >> get
> > > > >> > >> the same
> > > > >> > >> >> binaries
> > > > >> > >> >> > > on Mac and Win. I now have the identical
> > binaries
> > > > for
> > > > >> > >> >> royale-compiler
> > > > >> > >> >> > and
> > > > >> > >> >> > > royale-typedefs Maven artifacts and am
> starting
> > on
> > > > >> > >> royale-asjs.
> > > > >> > >> >> I might
> > > > >> > >> >> > > get lucky and the changes that fixed
> > > royale-typedefs
> > > > >> SWCs
> > > > >> > >> will
> > > > >> > >> >> magically
> > > > >> > >> >> > > get the royale-asjs SWCs to match. Then we
> have
> > > to
> > > > >> make
> > > > >> > >> the Ant
> > > > >> > >> >> > artifacts
> > > > >> > >> >> > > match.
> > > > >> > >> >> > >
> > > > >> > >> >> > > There have been a lot of distractions in
> my
> > > > >> non-work
> > > > >> > >> life
> > > > >> > >> >> which has
> > > > >> > >> >> > > also impeded progress. I hope to make much
> > > progress
> > > > >> this
> > > > >> > >> coming
> > > > >> > >> >> week and
> > > > >> > >> >> > > if we're lucky, I will be asking for a
> volunteer
> > > (or
> > > > >> > >> volunteers)
> > > > >> > >> >> to test
> > > > >> > >> >> > > drive all of this stuff and be the RM for
> 0.9.6.
> > > I
> > > > am
> > > > >> > not
> > > > >> > >> going
> > > > >> > >> >> to be
> > > > >> > >> >> > the
> > > > >> > >> >> > > RM.
> > > > >> > >> >> > >
> > > > >> > >> >> > > -Alex
> > > > >> > >> >> > >
> > > > >> > >> >> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> > > > >> > >> >> piotrzarzycki21@gmail.com>
> > > > >> > >> >> > > wrote:
> > > > >> > >> >> > >
> > > > >> > >> >> > > Hi Alex,
> > > > >> > >> >> > >
> > > > >> > >> >> > > It's been a while since you have
> started
> > > > >> effort
> > > > >> > >> with
> > > > >> > >> >> automating
> > > > >> > >> >> > > build.
> > > > >> > >> >> > > Where are you with that ? Are we
> closer
> > to
> > > > >> > started
> > > > >> > >> 0.9.6.
> > > > >> > >> >> Do you
> > > > >> > >> >> > > need any
> > > > >> > >> >> > > help with this ?
> > > > >> > >> >> > >
> > > > >> > >> >> > > Thanks,
> > > > >> > >> >> > > Piotr
> > > > >> > >> >> > >
> > > > >> > >> >> > > wt., 2 kwi 2019 o 19:30 Alex Harui
> > > > >> > >> >> <ah...@adobe.com.invalid>
> > > > >> > >> >> > > napisał(a):
> > > > >> > >> >> > >
> > > > >> > >> >> > > > Update:
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > In order to make verification of
> > binary
> > > > >> release
> > > > >> > >> packages
> > > > >> > >> >> > created
> > > > >> > >> >> > > on the
> > > > >> > >> >> > > > server easier, I have made changes
> to
> > > our
> > > > >> build
> > > > >> > >> scripts
> > > > >> > >> >> and
> > > > >> > >> >> > > tools to try to
> > > > >> > >> >> > > > generate reproducible binaries.
> I've
> > > seen
> > > > >> two
> > > > >> > >> >> different builds
> > > > >> > >> >> > > compare on
> > > > >> > >> >> > > > my Mac. The next challenge will be
> > to
> > > > see
> > > > >> if
> > > > >> > >> the
> > > > >> > >> >> server can
> > > > >> > >> >> > > build a
> > > > >> > >> >> > > > package on Windows that will compare
> > on
> > > > Mac.
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > One of the changes I needed to make
> is
> > > to
> > > > >> > >> JBurg. The
> > > > >> > >> >> version
> > > > >> > >> >> > of
> > > > >> > >> >> > > JBurg we
> > > > >> > >> >> > > > use generates method names
> including a
> > > > hash
> > > > >> > that
> > > > >> > >> doesn't
> > > > >> > >> >> > > reproduce the same
> > > > >> > >> >> > > > name each time. I have changes to
> > JBurg
> > > > >> ready,
> > > > >> > >> however
> > > > >> > >> >> JBurg
> > > > >> > >> >> > is
> > > > >> > >> >> > > currently
> > > > >> > >> >> > > > under CPL which is category B. We
> > only
> > > > need
> > > > >> > one
> > > > >> > >> file,
> > > > >> > >> >> we don't
> > > > >> > >> >> > > need or
> > > > >> > >> >> > > > want all of JBurg at this time. The
> > one
> > > > >> JBurg
> > > > >> > >> file is
> > > > >> > >> >> jointly
> > > > >> > >> >> > > owned by
> > > > >> > >> >> > > > Adobe and Tom Harwood. I've contact
> > Tom
> > > > >> and he
> > > > >> > >> will be
> > > > >> > >> >> filing
> > > > >> > >> >> > > an ICLA and
> > > > >> > >> >> > > > has given me permission to commit
> the
> > > > lines
> > > > >> he
> > > > >> > >> owns in
> > > > >> > >> >> that one
> > > > >> > >> >> > > file.
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > This is the revision of the file
> that
> > > will
> > > > >> be
> > > > >> > >> donated by
> > > > >> > >> >> > > Tom/Adobe.
> > > > >> > >> >> > > >
> > > > >> > >> >> > > >
> > > > >> > >> >> > >
> > > > >> > >> >> >
> > > > >> > >> >>
> > > > >> > >>
> > > > >> >
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=VS1za1vOQhtlKlK4Tdgq3ej04OlhFoYfHziyNbgOIN4%3D&reserved=0
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > Once this file goes in with the
> > changes
> > > to
> > > > >> keep
> > > > >> > >> the
> > > > >> > >> >> method
> > > > >> > >> >> > names
> > > > >> > >> >> > > the same,
> > > > >> > >> >> > > > there will be more tweaks to the
> > release
> > > > >> tasks
> > > > >> > >> and then
> > > > >> > >> >> we can
> > > > >> > >> >> > > try cutting
> > > > >> > >> >> > > > a release. I'm thinking we'll be at
> > > that
> > > > >> point
> > > > >> > >> in
> > > > >> > >> >> early May,
> > > > >> > >> >> > so
> > > > >> > >> >> > > now is the
> > > > >> > >> >> > > > time to get stuff in for the 0.9.6
> > > > release.
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > Thanks,
> > > > >> > >> >> > > > -Alex
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > On 3/8/19, 9:27 AM, "Alex Harui" <
> > > > >> > >> aharui@adobe.com>
> > > > >> > >> >> wrote:
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > I would much rather have others
> > find
> > > > and
> > > > >> > fix
> > > > >> > >> issues
> > > > >> > >> >> > > themselves. That
> > > > >> > >> >> > > > way, more people than just me will
> > know
> > > > how
> > > > >> to
> > > > >> > >> maintain
> > > > >> > >> >> the
> > > > >> > >> >> > > system. It
> > > > >> > >> >> > > > actually turns out that, IMO, a
> group
> > of
> > > > >> people
> > > > >> > >> can
> > > > >> > >> >> work on the
> > > > >> > >> >> > > release.
> > > > >> > >> >> > > > There are 14 steps. Literally, 14
> > > > different
> > > > >> > >> people
> > > > >> > >> >> could
> > > > >> > >> >> > > execute one step
> > > > >> > >> >> > > > each.
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > My 2 cents,
> > > > >> > >> >> > > > -Alex
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > On 3/8/19, 2:13 AM, "Carlos
> > Rovira"
> > > <
> > > > >> > >> >> > carlosrovira@apache.org>
> > > > >> > >> >> > > wrote:
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > Hi Alex,
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > amazing work! congrats to
> > reach
> > > to
> > > > >> this
> > > > >> > >> point!
> > > > >> > >> >> :)
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > I need to put my head on all
> > of
> > > > >> this,
> > > > >> > >> but count
> > > > >> > >> >> on me
> > > > >> > >> >> > to
> > > > >> > >> >> > > be a RM.
> > > > >> > >> >> > > > I think
> > > > >> > >> >> > > > the best thing should be
> that
> > > you
> > > > be
> > > > >> > the
> > > > >> > >> first
> > > > >> > >> >> RM to
> > > > >> > >> >> > try
> > > > >> > >> >> > > your own
> > > > >> > >> >> > > > development at least for the
> > > first
> > > > >> > time,
> > > > >> > >> and
> > > > >> > >> >> then the
> > > > >> > >> >> > > rest of us
> > > > >> > >> >> > > > will
> > > > >> > >> >> > > > follow you on the next
> > releases.
> > > > >> With
> > > > >> > >> all this
> > > > >> > >> >> on place
> > > > >> > >> >> > > we maybe
> > > > >> > >> >> > > > could
> > > > >> > >> >> > > > release once a month or
> every
> > > two
> > > > >> > >> months...
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > Thanks for doing this :)
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > Carlos
> > > > >> > >> >> > > >
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > El vie., 8 mar. 2019 a las
> > 1:55,
> > > > >> Alex
> > > > >> > >> Harui
> > > > >> > >> >> > > > (<ah...@adobe.com.invalid>)
> > > > >> > >> >> > > > escribió:
> > > > >> > >> >> > > >
> > > > >> > >> >> > > > > OK, I've now seen Jenkins
> > > > perform
> > > > >> the
> > > > >> > >> steps
> > > > >> > >> >> to build
> > > > >> > >> >> > > the release
> > > > >> > >> >> > > > > artifacts. Folks
> interested
> > > in
> > > > >> > >> Docker-izing
> > > > >> > >> >> the
> > > > >> > >> >> > steps
> > > > >> > >> >> > > are
> > > > >> > >> >> > > > welcome to look
> > > > >> > >> >> > > > > at the jobs on the "Royale
> > > > >> Release"
> > > > >> > >> tab on
> > > > >> > >> >> the CI
> > > > >> > >> >> > > server.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > >
> > > > >> > >> >> > >
> > > > >> > >> >> >
> > > > >> > >> >>
> > > > >> > >>
> > > > >> >
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=LfWCyCaClCVgfeINn4%2B%2Bk%2FSVUFXvgyV7QxMtx4B%2B%2Fu0%3D&reserved=0
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > These steps assume that
> the
> > RM
> > > > can
> > > > >> > run
> > > > >> > >> the
> > > > >> > >> >> basic
> > > > >> > >> >> > Maven
> > > > >> > >> >> > > and Ant
> > > > >> > >> >> > > > build on
> > > > >> > >> >> > > > > the RM's computer. I think
> > > > that's
> > > > >> a
> > > > >> > >> fair
> > > > >> > >> >> requirement
> > > > >> > >> >> > > since all
> > > > >> > >> >> > > > of us on the
> > > > >> > >> >> > > > > PMC need to able to do
> that
> > to
> > > > >> build
> > > > >> > >> the RC
> > > > >> > >> >> in order
> > > > >> > >> >> > > to vote on
> > > > >> > >> >> > > > it.
> > > > >> > >> >> > > > > Jenkins does other tasks
> > like
> > > > run
> > > > >> > the
> > > > >> > >> Maven
> > > > >> > >> >> release
> > > > >> > >> >> > > plugin
> > > > >> > >> >> > > > steps.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > Currently that results in
> > > > >> binaries on
> > > > >> > >> Jenkins
> > > > >> > >> >> that
> > > > >> > >> >> > are
> > > > >> > >> >> > > > downloaded to the
> > > > >> > >> >> > > > > RM's computer. These
> > binaries
> > > > >> need
> > > > >> > to
> > > > >> > >> be
> > > > >> > >> >> verified by
> > > > >> > >> >> > > the RM
> > > > >> > >> >> > > > which is the
> > > > >> > >> >> > > > > next phase I will be
> > starting
> > > on
> > > > >> now.
> > > > >> > >> The RM
> > > > >> > >> >> > verifies
> > > > >> > >> >> > > the bits
> > > > >> > >> >> > > > and then
> > > > >> > >> >> > > > > PGP signs them. And then
> > the
> > > > bits
> > > > >> > are
> > > > >> > >> >> uploaded off
> > > > >> > >> >> > > the RM's
> > > > >> > >> >> > > > computer to
> > > > >> > >> >> > > > > Maven Staging or
> > dist.a.o/dev.
> > > > >> If
> > > > >> > >> that
> > > > >> > >> >> uploading
> > > > >> > >> >> > > turns out to
> > > > >> > >> >> > > > be a point
> > > > >> > >> >> > > > > of failure, we have the
> > option
> > > > of
> > > > >> > >> having
> > > > >> > >> >> Jenkins
> > > > >> > >> >> > > upload the big
> > > > >> > >> >> > > > files and
> > > > >> > >> >> > > > > have the RM only upload
> PGP
> > > > >> signature
> > > > >> > >> files.
> > > > >> > >> >> Or
> > > > >> > >> >> > > finding a way
> > > > >> > >> >> > > > for Jenkins
> > > > >> > >> >> > > > > to get the signature files
> > > from
> > > > >> the
> > > > >> > >> RM. The
> > > > >> > >> >> uploads
> > > > >> > >> >> > > worked fine
> > > > >> > >> >> > > > for me,
> > > > >> > >> >> > > > > but then again, so did the
> > old
> > > > >> > script's
> > > > >> > >> >> uploads.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > Therefore, once I get the
> > > binary
> > > > >> > >> verification
> > > > >> > >> >> phase
> > > > >> > >> >> > > completed, I
> > > > >> > >> >> > > > think
> > > > >> > >> >> > > > > someone other than me
> should
> > > be
> > > > >> the
> > > > >> > RM
> > > > >> > >> and
> > > > >> > >> >> try to use
> > > > >> > >> >> > > these
> > > > >> > >> >> > > > steps to
> > > > >> > >> >> > > > > generate the release and
> > help
> > > > >> debug
> > > > >> > the
> > > > >> > >> >> process for
> > > > >> > >> >> > > the next
> > > > >> > >> >> > > > RM. So,
> > > > >> > >> >> > > > > please try to carve out
> some
> > > > time
> > > > >> to
> > > > >> > >> be the
> > > > >> > >> >> RM. One
> > > > >> > >> >> > > advantage
> > > > >> > >> >> > > > of doing
> > > > >> > >> >> > > > > most of the work on
> Jenkins
> > is
> > > > >> that
> > > > >> > it
> > > > >> > >> frees
> > > > >> > >> >> up my
> > > > >> > >> >> > > computer to
> > > > >> > >> >> > > > do other
> > > > >> > >> >> > > > > things while Jenkins is
> > > cranking
> > > > >> > away.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > I think we're at least a
> > week
> > > > away
> > > > >> > >> from binary
> > > > >> > >> >> > > verification,
> > > > >> > >> >> > > > maybe two, so
> > > > >> > >> >> > > > > it is time to start
> thinking
> > > > about
> > > > >> > >> what is
> > > > >> > >> >> going in
> > > > >> > >> >> > > this release.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > Thanks,
> > > > >> > >> >> > > > > -Alex
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > On 3/7/19, 4:15 PM, "Alex
> > > Harui"
> > > > >> > >> >> > > <ah...@adobe.com.INVALID>
> > > > >> > >> >> > > > wrote:
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > In case you haven't
> > > guessed,
> > > > >> I'm
> > > > >> > >> testing
> > > > >> > >> >> out
> > > > >> > >> >> > > Jenkins and its
> > > > >> > >> >> > > > ability
> > > > >> > >> >> > > > > to create the artifacts
> and
> > > send
> > > > >> > >> emails.
> > > > >> > >> >> Please
> > > > >> > >> >> > > ignore any
> > > > >> > >> >> > > > email that
> > > > >> > >> >> > > > > looks like a vote or
> discuss
> > > > >> thread.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > Thanks,
> > > > >> > >> >> > > > > -Alex
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > On 2/10/19, 8:44 PM,
> > "Alex
> > > > >> Harui"
> > > > >> > >> >> > > <ah...@adobe.com.INVALID>
> > > > >> > >> >> > > > wrote:
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > Om,
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > Well, that's what
> I
> > > used
> > > > >> for
> > > > >> > >> the last
> > > > >> > >> >> > > release. I'm sure
> > > > >> > >> >> > > > there is
> > > > >> > >> >> > > > > probably some inaccuracy
> in
> > > it.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > That said, I'm
> > > > abandoning
> > > > >> > that
> > > > >> > >> >> document and
> > > > >> > >> >> > > taking a new
> > > > >> > >> >> > > > angle
> > > > >> > >> >> > > > > because that document
> > presumed
> > > > >> that
> > > > >> > the
> > > > >> > >> >> release
> > > > >> > >> >> > > manager was
> > > > >> > >> >> > > > trying to
> > > > >> > >> >> > > > > create a release on
> his/her
> > > > >> computer.
> > > > >> > >> I've
> > > > >> > >> >> given up
> > > > >> > >> >> > > on that and
> > > > >> > >> >> > > > working on
> > > > >> > >> >> > > > > making releases from a
> > shared
> > > > >> > computer
> > > > >> > >> for the
> > > > >> > >> >> > reasons
> > > > >> > >> >> > > I've
> > > > >> > >> >> > > > stated
> > > > >> > >> >> > > > > upthread. I hope to make
> > some
> > > > >> > >> progress on
> > > > >> > >> >> that this
> > > > >> > >> >> > > week.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > The key difference
> > is
> > > > that
> > > > >> > the
> > > > >> > >> new
> > > > >> > >> >> angle does
> > > > >> > >> >> > > not
> > > > >> > >> >> > > > presume that you
> > > > >> > >> >> > > > > have Git SSH and PGP
> > > signatures
> > > > >> all
> > > > >> > >> set up on
> > > > >> > >> >> some
> > > > >> > >> >> > > computer. I
> > > > >> > >> >> > > > have not
> > > > >> > >> >> > > > > looked into how Docker
> would
> > > > >> handle
> > > > >> > >> that. You
> > > > >> > >> >> > > certainly
> > > > >> > >> >> > > > wouldn't want the
> > > > >> > >> >> > > > > Docker image to contain
> your
> > > SSH
> > > > >> or
> > > > >> > PGP
> > > > >> > >> >> keys/creds.
> > > > >> > >> >> > > And if the
> > > > >> > >> >> > > > Docker
> > > > >> > >> >> > > > > image doesn't, then that
> is
> > > > >> another
> > > > >> > >> stumbling
> > > > >> > >> >> block
> > > > >> > >> >> > > for future
> > > > >> > >> >> > > > RMs.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > The other key
> > > difference
> > > > >> is
> > > > >> > >> that the
> > > > >> > >> >> old
> > > > >> > >> >> > > script presumed
> > > > >> > >> >> > > > you could
> > > > >> > >> >> > > > > create the 3 release in 3
> > huge
> > > > >> "easy"
> > > > >> > >> steps.
> > > > >> > >> >> We've
> > > > >> > >> >> > > seen that is
> > > > >> > >> >> > > > only true
> > > > >> > >> >> > > > > for me. So the new angle
> > > > creates
> > > > >> > many
> > > > >> > >> >> discrete steps
> > > > >> > >> >> > > managed by
> > > > >> > >> >> > > > Jenkins.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > So, it is up to
> you
> > to
> > > > >> decide
> > > > >> > >> what
> > > > >> > >> >> you want
> > > > >> > >> >> > to
> > > > >> > >> >> > > > "Docker-ize". You
> > > > >> > >> >> > > > > can try to Docker-ize the
> > > > current
> > > > >> 3
> > > > >> > big
> > > > >> > >> >> steps, so RMs
> > > > >> > >> >> > > can try to
> > > > >> > >> >> > > > run it on
> > > > >> > >> >> > > > > their systems, but I'd bet
> > > they
> > > > >> will
> > > > >> > >> just
> > > > >> > >> >> faiI due to
> > > > >> > >> >> > > network
> > > > >> > >> >> > > > issues. I
> > > > >> > >> >> > > > > would be interested in
> using
> > > > >> Docker
> > > > >> > to
> > > > >> > >> make
> > > > >> > >> >> each of
> > > > >> > >> >> > > these many
> > > > >> > >> >> > > > discrete
> > > > >> > >> >> > > > > steps portable to another
> > > > server.
> > > > >> > >> I'm not
> > > > >> > >> >> going to
> > > > >> > >> >> > > involve
> > > > >> > >> >> > > > Docker at this
> > > > >> > >> >> > > > > point. My main goal is
> just
> > > to
> > > > >> see
> > > > >> > if
> > > > >> > >> I can
> > > > >> > >> >> create a
> > > > >> > >> >> > > workflow
> > > > >> > >> >> > > > of many
> > > > >> > >> >> > > > > discrete steps that isn't
> > > > horribly
> > > > >> > >> painful.
> > > > >> > >> >> Once we
> > > > >> > >> >> > > see what
> > > > >> > >> >> > > > these steps
> > > > >> > >> >> > > > > turn out to be, then we
> can
> > > > worry
> > > > >> > >> about server
> > > > >> > >> >> > > portability of
> > > > >> > >> >> > > > those steps.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > Either way, we
> want
> > to
> > > > >> know
> > > > >> > >> about
> > > > >> > >> >> running
> > > > >> > >> >> > > > Browser+Selenium for
> > > > >> > >> >> > > > > sure. And maybe
> > > > >> FlashPlayerDebugger
> > > > >> > >> or AIR.
> > > > >> > >> >> I would
> > > > >> > >> >> > > want to
> > > > >> > >> >> > > > know, for
> > > > >> > >> >> > > > > example, how you debug a
> > > failing
> > > > >> > >> checkintest
> > > > >> > >> >> in a
> > > > >> > >> >> > > Docker
> > > > >> > >> >> > > > container.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > Thanks,
> > > > >> > >> >> > > > > -Alex
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > On 2/10/19, 5:18
> PM,
> > > > >> > "OmPrakash
> > > > >> > >> >> Muppirala" <
> > > > >> > >> >> > > > bigosmallm@gmail.com>
> > > > >> > >> >> > > > > wrote:
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > Alex,
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > Just to be
> > clear,
> > > I
> > > > am
> > > > >> > >> following
> > > > >> > >> >> the
> > > > >> > >> >> > steps
> > > > >> > >> >> > > from here
> > > > >> > >> >> > > > to try
> > > > >> > >> >> > > > > and setup a
> > > > >> > >> >> > > > > docker
> > container.
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > >
> > > > >> > >> >> > >
> > > > >> > >> >> >
> > > > >> > >>
> > > > >> >
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=Lhm0hudN8Nbx%2F6Lnmz0Wlus3EpV1o1h8XWBzBUoEWOA%3D&reserved=0
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > Is this doc up
> > to
> > > > >> date?
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > Thanks,
> > > > >> > >> >> > > > > Om
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > On Wed, Feb 6,
> > > 2019
> > > > at
> > > > >> > >> 12:02 PM
> > > > >> > >> >> OmPrakash
> > > > >> > >> >> > > Muppirala <
> > > > >> > >> >> > > > > bigosmallm@gmail.com>
> > > > >> > >> >> > > > > wrote:
> > > > >> > >> >> > > > >
> > > > >> > >> >> > > > > > One approach
> > is
> > > to
> > > > >> have
> > > > >> > >> each
> > > > >> > >> >> step in
> > > > >> > >> >> > the
> > > > >> > >> >> > > process
> > > > >> > >> >> > > > spin up a
> > > > >> > >> >> > > > > docker image.
> > > > >> > >> >> > > > > > And use
> > > > >> docker-compose
> > > > >> > >> to run
> > > > >> > >> >> each
> > > > >> > >> >> > > step. All the
> > > > >> > >> >> > > > images can
> > > > >> > >> >> > > > > be made to
> > > > >> > >> >> > > > > > share a
> common
> > > > >> volume
> > > > >> > >> where all
> > > > >> > >> >> the
> > > > >> > >> >> > > artifacts are
> > > > >> > >> >> > > > stored
> > > > >> > >> >> > > > > across steps.
> > > > >> > >> >> > > > > >
> > > > >> > >> >> > > > > > You are
> right
> > > > about
> > > > >> the
> > > > >> > >> >> networking
> > > > >> > >> >> > issue
> > > > >> > >> >> > > though.
> > > > >> > >> >> > > > Any
> > > > >> > >> >> > > > > network related
> > > > >> > >> >> > > > > > failure that
> > > > occurs
> > > > >> on
> > > > >> > >> the host
> > > > >> > >> >> machine
> > > > >> > >> >> > > will most
> > > > >> > >> >> > > > likely
> > > > >> > >> >> > > > > occur in the
> > > > >> > >> >> > > > > > docker
> > > container.
> > > > >> > >> Although, I
> > > > >> > >> >> am not
> > > > >> > >> >> > > clear how we
> > > > >> > >> >> > > > can
> > > > >> > >> >> > > > > guarantee that the
> > > > >> > >> >> > > > > > same issues
> > will
> > > > not
> > > > >> > >> occur on
> > > > >> > >> >> the
> > > > >> > >> >> > > Jenkins server.
> > > > >> > >> >> > > > I mean,
> > > > >> > >> >> > > > > what is special
> > > > >> > >> >> > > > > > about the
> > > Jenkins
> > > > >> > server
> > > > >> > >> that
> > > > >> > >> >> makes it
> > > > >> > >> >> > > immune to
> > > > >> > >> >> > > > these
> > > > >> > >> >> > > > > networking issues?
> > > > >> > >> >> > > > > >
> > > > >> > >> >> > > > > > Thanks,
> > > > >> > >> >> > > > > > Om
> > > > >> > >> >> > > > > >
> > > > >> > >> >> > > > > > On Wed, Feb
> 6,
> > > > 2019
> > > > >> at
> > > > >> > >> 11:48 AM
> > > > >> > >> >> Alex
> > > > >> > >> >> > > Harui
> > > > >> > >> >> > > > > <aharui@adobe.com.invalid
> >
> > > > >> > >> >> > > > > > wrote:
> > > > >> > >> >> > > > > >
> > > > >> > >> >> > > > > >> Again, I
> > don't
> > > > know
> > > > >> > >> anything
> > > > >> > >> >> about
> > > > >> > >> >> > > Docker, but
> > > > >> > >> >> > > > before we
> > > > >> > >> >> > > > > spend a lot of
> > > > >> > >> >> > > > > >> time on
> > > Docker, I
> > > > >> also
> > > > >> > >> want to
> > > > >> > >> >> point
> > > > >> > >> >> > > out that the
> > > > >> > >> >> > > > process
> > > > >> > >> >> > > > > to create a
> > > > >> > >> >> > > > > >> release
> > cannot
> > > > >> really
> > > > >> > be
> > > > >> > >> >> thought of as
> > > > >> > >> >> > > "one
> > > > >> > >> >> > > > application".
> > > > >> > >> >> > > > > It will be a
> > > > >> > >> >> > > > > >> series of
> > > "steps"
> > > > >> to
> > > > >> > >> run.
> > > > >> > >> >> How many
> > > > >> > >> >> > > steps
> > > > >> > >> >> > > > depends on
> > > > >> > >> >> > > > > whether we think we
> > > > >> > >> >> > > > > >> can isolate
> > > > enough
> > > > >> > >> stuff via
> > > > >> > >> >> Docker to
> > > > >> > >> >> > > be able to
> > > > >> > >> >> > > > run
> > > > >> > >> >> > > > > Docker on the RM's
> > > > >> > >> >> > > > > >> computer
> > > instead
> > > > of
> > > > >> > >> some shared
> > > > >> > >> >> > > computer. On a
> > > > >> > >> >> > > > shared
> > > > >> > >> >> > > > > computer there will
> > > > >> > >> >> > > > > >> be dozens
> of
> > > > steps
> > > > >> > >> because the
> > > > >> > >> >> RM will
> > > > >> > >> >> > > need to
> > > > >> > >> >> > > > enter
> > > > >> > >> >> > > > > passwords to commit
> > > > >> > >> >> > > > > >> stuff. On
> a
> > > > local
> > > > >> > >> computer I
> > > > >> > >> >> guess
> > > > >> > >> >> > the
> > > > >> > >> >> > > RM can
> > > > >> > >> >> > > > supply
> > > > >> > >> >> > > > > passwords but I think
> > > > >> > >> >> > > > > >> there will
> be
> > > > >> stopping
> > > > >> > >> points
> > > > >> > >> >> where
> > > > >> > >> >> > the
> > > > >> > >> >> > > Maven
> > > > >> > >> >> > > > artifacts are
> > > > >> > >> >> > > > > deployed and
> > > > >> > >> >> > >
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: 0.9.6 Release
Posted by Piotr Zarzycki <pi...@gmail.com>.
Greg,
It looks like Ant compiler build is working fine. I'm waiting now for JS
only build of framework to be finished.
Thanks,
Piotr
On Tue, Jun 11, 2019, 8:31 AM Greg Dove <gr...@gmail.com> wrote:
> Thanks for clarifying Piotr. That one at least worked it seems.
> I saw the problem elsewhere and first time it was because the compiler
> build had required changes and did not complete before the framework.
> The others have some issues, but I don't think it is related to my latest
> changes , because it seems to be the same issue as previous fails. I will
> try to figure those out tomorrow some time if I can.
>
> On Tue, Jun 11, 2019 at 5:08 PM Piotr Zarzycki <pi...@gmail.com>
> wrote:
>
> > Greg,
> >
> > I was thinking about ant build on Jenkins [1]. I didn't check Maven build
> > in a while.
> >
> > [1]
> >
> >
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/changes
> >
> > Thanks,
> > Piotr
> >
> >
> > On Tue, Jun 11, 2019, 6:48 AM Greg Dove <gr...@gmail.com> wrote:
> >
> > > Piotr, I hope I addressed the issue, but waiting to see...
> > > It looks like it has been unstable for last 7 days , am I reading that
> > > right? https://builds.apache.org/job/Royale-asjs/
> > >
> > >
> > > On Tue, Jun 11, 2019 at 4:30 PM Greg Dove <gr...@gmail.com> wrote:
> > >
> > > > Working on it!
> > > >
> > > >
> > > > On Tue, Jun 11, 2019 at 4:29 PM Piotr Zarzycki <
> > > piotrzarzycki21@gmail.com>
> > > > wrote:
> > > >
> > > >> Hi Greg,
> > > >>
> > > >> After your merge the goal should be that build on Jenkins is working
> > > fine.
> > > >> Please make sure that is happen.
> > > >>
> > > >> Thanks,
> > > >> Piotr
> > > >>
> > > >> On Tue, Jun 11, 2019, 5:32 AM Greg Dove <gr...@gmail.com>
> wrote:
> > > >>
> > > >> > I will stick with the plan of single commit, I think it should be
> > > easier
> > > >> > for you if there are any conflicts.
> > > >> > Last build testing is running now in local develop. I will push
> > after
> > > >> > that...
> > > >> >
> > > >> > On Tue, Jun 11, 2019 at 3:15 PM Greg Dove <gr...@gmail.com>
> > > wrote:
> > > >> >
> > > >> > >
> > > >> > > Thanks Alex, I was planning to merge this as a single squashed
> > > commit,
> > > >> > > because it isolates all the changes to a single commit (but this
> > > will
> > > >> > mean
> > > >> > > there are many changes in one hit).
> > > >> > > Do you have a preference in terms of how easy it will make
> things
> > > for
> > > >> > you?
> > > >> > >
> > > >> > >
> > > >> > > On Tue, Jun 11, 2019 at 3:07 PM Alex Harui
> > <aharui@adobe.com.invalid
> > > >
> > > >> > > wrote:
> > > >> > >
> > > >> > >> OK, I will wait to see your commit emails. I will do some
> other
> > > >> things
> > > >> > >> like the wiki doc.
> > > >> > >>
> > > >> > >> -Alex
> > > >> > >>
> > > >> > >> On 6/10/19, 8:06 PM, "Greg Dove" <gr...@gmail.com> wrote:
> > > >> > >>
> > > >> > >> Hi Alex, I guess you might be back on Royale about now.
> Just
> > a
> > > >> heads
> > > >> > >> up: I
> > > >> > >> am about 20-30 mins max from merging in what I have. Hope
> > > that's
> > > >> > still
> > > >> > >> ok... please let me know if not.
> > > >> > >> Thanks,
> > > >> > >> -Greg
> > > >> > >>
> > > >> > >>
> > > >> > >> On Tue, Jun 11, 2019 at 7:51 AM Greg Dove <
> > greg.dove@gmail.com
> > > >
> > > >> > >> wrote:
> > > >> > >>
> > > >> > >> >
> > > >> > >> > Thanks Alex - I'll try to hit the window, much
> appreciated!
> > > >> > >> >
> > > >> > >> >
> > > >> > >> > On Tue, Jun 11, 2019 at 6:57 AM Alex Harui
> > > >> > <aharui@adobe.com.invalid
> > > >> > >> >
> > > >> > >> > wrote:
> > > >> > >> >
> > > >> > >> >> Hi Greg,
> > > >> > >> >>
> > > >> > >> >> It turns out I have a "split shift" today. I'm stopping
> > > work
> > > >> for
> > > >> > >> the
> > > >> > >> >> next 7 or 8 hours then will get around to the merge. So
> > if
> > > >> you
> > > >> > >> can get
> > > >> > >> >> your changes merged in that amount of time, then I will
> > wait
> > > >> for
> > > >> > >> you and
> > > >> > >> >> deal with any merge conflicts (there are almost certain
> to
> > > be
> > > >> > >> some).
> > > >> > >> >>
> > > >> > >> >> -Alex
> > > >> > >> >>
> > > >> > >> >> On 6/10/19, 11:46 AM, "Greg Dove" <gr...@gmail.com>
> > > >> wrote:
> > > >> > >> >>
> > > >> > >> >> Alex, slightly OT, but in terms of coordination:
> fyi I
> > > am
> > > >> > also
> > > >> > >> very
> > > >> > >> >> close
> > > >> > >> >> to merging the language improvements branch into
> > > develop.
> > > >> As
> > > >> > I
> > > >> > >> already
> > > >> > >> >> mentioned elsewhere, I was hoping to do that a
> couple
> > of
> > > >> days
> > > >> > >> back,
> > > >> > >> >> but
> > > >> > >> >> some recent things also took me a little longer than
> > > >> expected
> > > >> > >> (I have
> > > >> > >> >> additional local changes/fixes not yet in remote
> > branch)
> > > >> . I
> > > >> > >> was
> > > >> > >> >> planning
> > > >> > >> >> to merge that today also.
> > > >> > >> >>
> > > >> > >> >> However, I will wait until after your merge, so I'm
> > > hoping
> > > >> > you
> > > >> > >> can get
> > > >> > >> >> yours in today (if not, I will wait). I will
> probably
> > > put
> > > >> > mine
> > > >> > >> in as a
> > > >> > >> >> squashed commit after yours.
> > > >> > >> >>
> > > >> > >> >>
> > > >> > >> >> On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <
> > > >> > >> >> piotrzarzycki21@gmail.com>
> > > >> > >> >> wrote:
> > > >> > >> >>
> > > >> > >> >> > Hi Alex,
> > > >> > >> >> >
> > > >> > >> >> > Many thanks for that! I will try to be RM. I will
> > have
> > > >> some
> > > >> > >> >> dedicated time
> > > >> > >> >> > for that. I will wait for your instruction and
> merge
> > > to
> > > >> > >> develop.
> > > >> > >> >> >
> > > >> > >> >> > Thanks,
> > > >> > >> >> > Piotr
> > > >> > >> >> >
> > > >> > >> >> >
> > > >> > >> >> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
> > > >> > >> <ah...@adobe.com.invalid>
> > > >> > >> >> wrote:
> > > >> > >> >> >
> > > >> > >> >> > > Well, that turned out to be much more
> > time-consuming
> > > >> > than I
> > > >> > >> >> expected, but
> > > >> > >> >> > > we can now create identical release artifacts on
> > Mac
> > > >> and
> > > >> > >> Win. I
> > > >> > >> >> am
> > > >> > >> >> > hopeful
> > > >> > >> >> > > this effort will pay off not only now in having
> > > other
> > > >> > folks
> > > >> > >> >> generate
> > > >> > >> >> > > releases, but also in the future if signed
> > binaries
> > > >> > become
> > > >> > >> a
> > > >> > >> >> requirement.
> > > >> > >> >> > >
> > > >> > >> >> > > There continues to be a lot of distractions in
> my
> > > life
> > > >> > >> that can
> > > >> > >> >> cause
> > > >> > >> >> > > delays, but I hope to merge the release_practice
> > > >> branches
> > > >> > >> into
> > > >> > >> >> develop
> > > >> > >> >> > over
> > > >> > >> >> > > the next day or two and figure out where in the
> > wiki
> > > >> to
> > > >> > >> document
> > > >> > >> >> the
> > > >> > >> >> > > release process. So, now is the time for one or
> > > more
> > > >> > >> people to
> > > >> > >> >> step up
> > > >> > >> >> > to
> > > >> > >> >> > > be the RMs for 0.9.6 and help debug and improve
> > the
> > > >> > >> process.
> > > >> > >> >> > >
> > > >> > >> >> > > I am going to try very hard not to "own" the
> > > >> process. If
> > > >> > >> >> something goes
> > > >> > >> >> > > wrong, I am going to ask others to try to debug
> > and
> > > >> fix
> > > >> > it
> > > >> > >> first
> > > >> > >> >> because
> > > >> > >> >> > it
> > > >> > >> >> > > is in the project's best interests for others to
> > > truly
> > > >> > >> understand
> > > >> > >> >> how
> > > >> > >> >> > this
> > > >> > >> >> > > stuff works.
> > > >> > >> >> > >
> > > >> > >> >> > > Thanks,
> > > >> > >> >> > > -Alex
> > > >> > >> >> > >
> > > >> > >> >> > > On 5/23/19, 9:54 AM, "Alex Harui"
> > > >> > <aharui@adobe.com.INVALID
> > > >> > >> >
> > > >> > >> >> wrote:
> > > >> > >> >> > >
> > > >> > >> >> > > It has turned out to be harder than expected
> > to
> > > >> get
> > > >> > >> the same
> > > >> > >> >> binaries
> > > >> > >> >> > > on Mac and Win. I now have the identical
> binaries
> > > for
> > > >> > >> >> royale-compiler
> > > >> > >> >> > and
> > > >> > >> >> > > royale-typedefs Maven artifacts and am starting
> on
> > > >> > >> royale-asjs.
> > > >> > >> >> I might
> > > >> > >> >> > > get lucky and the changes that fixed
> > royale-typedefs
> > > >> SWCs
> > > >> > >> will
> > > >> > >> >> magically
> > > >> > >> >> > > get the royale-asjs SWCs to match. Then we have
> > to
> > > >> make
> > > >> > >> the Ant
> > > >> > >> >> > artifacts
> > > >> > >> >> > > match.
> > > >> > >> >> > >
> > > >> > >> >> > > There have been a lot of distractions in my
> > > >> non-work
> > > >> > >> life
> > > >> > >> >> which has
> > > >> > >> >> > > also impeded progress. I hope to make much
> > progress
> > > >> this
> > > >> > >> coming
> > > >> > >> >> week and
> > > >> > >> >> > > if we're lucky, I will be asking for a volunteer
> > (or
> > > >> > >> volunteers)
> > > >> > >> >> to test
> > > >> > >> >> > > drive all of this stuff and be the RM for 0.9.6.
> > I
> > > am
> > > >> > not
> > > >> > >> going
> > > >> > >> >> to be
> > > >> > >> >> > the
> > > >> > >> >> > > RM.
> > > >> > >> >> > >
> > > >> > >> >> > > -Alex
> > > >> > >> >> > >
> > > >> > >> >> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> > > >> > >> >> piotrzarzycki21@gmail.com>
> > > >> > >> >> > > wrote:
> > > >> > >> >> > >
> > > >> > >> >> > > Hi Alex,
> > > >> > >> >> > >
> > > >> > >> >> > > It's been a while since you have started
> > > >> effort
> > > >> > >> with
> > > >> > >> >> automating
> > > >> > >> >> > > build.
> > > >> > >> >> > > Where are you with that ? Are we closer
> to
> > > >> > started
> > > >> > >> 0.9.6.
> > > >> > >> >> Do you
> > > >> > >> >> > > need any
> > > >> > >> >> > > help with this ?
> > > >> > >> >> > >
> > > >> > >> >> > > Thanks,
> > > >> > >> >> > > Piotr
> > > >> > >> >> > >
> > > >> > >> >> > > wt., 2 kwi 2019 o 19:30 Alex Harui
> > > >> > >> >> <ah...@adobe.com.invalid>
> > > >> > >> >> > > napisał(a):
> > > >> > >> >> > >
> > > >> > >> >> > > > Update:
> > > >> > >> >> > > >
> > > >> > >> >> > > > In order to make verification of
> binary
> > > >> release
> > > >> > >> packages
> > > >> > >> >> > created
> > > >> > >> >> > > on the
> > > >> > >> >> > > > server easier, I have made changes to
> > our
> > > >> build
> > > >> > >> scripts
> > > >> > >> >> and
> > > >> > >> >> > > tools to try to
> > > >> > >> >> > > > generate reproducible binaries. I've
> > seen
> > > >> two
> > > >> > >> >> different builds
> > > >> > >> >> > > compare on
> > > >> > >> >> > > > my Mac. The next challenge will be
> to
> > > see
> > > >> if
> > > >> > >> the
> > > >> > >> >> server can
> > > >> > >> >> > > build a
> > > >> > >> >> > > > package on Windows that will compare
> on
> > > Mac.
> > > >> > >> >> > > >
> > > >> > >> >> > > > One of the changes I needed to make is
> > to
> > > >> > >> JBurg. The
> > > >> > >> >> version
> > > >> > >> >> > of
> > > >> > >> >> > > JBurg we
> > > >> > >> >> > > > use generates method names including a
> > > hash
> > > >> > that
> > > >> > >> doesn't
> > > >> > >> >> > > reproduce the same
> > > >> > >> >> > > > name each time. I have changes to
> JBurg
> > > >> ready,
> > > >> > >> however
> > > >> > >> >> JBurg
> > > >> > >> >> > is
> > > >> > >> >> > > currently
> > > >> > >> >> > > > under CPL which is category B. We
> only
> > > need
> > > >> > one
> > > >> > >> file,
> > > >> > >> >> we don't
> > > >> > >> >> > > need or
> > > >> > >> >> > > > want all of JBurg at this time. The
> one
> > > >> JBurg
> > > >> > >> file is
> > > >> > >> >> jointly
> > > >> > >> >> > > owned by
> > > >> > >> >> > > > Adobe and Tom Harwood. I've contact
> Tom
> > > >> and he
> > > >> > >> will be
> > > >> > >> >> filing
> > > >> > >> >> > > an ICLA and
> > > >> > >> >> > > > has given me permission to commit the
> > > lines
> > > >> he
> > > >> > >> owns in
> > > >> > >> >> that one
> > > >> > >> >> > > file.
> > > >> > >> >> > > >
> > > >> > >> >> > > > This is the revision of the file that
> > will
> > > >> be
> > > >> > >> donated by
> > > >> > >> >> > > Tom/Adobe.
> > > >> > >> >> > > >
> > > >> > >> >> > > >
> > > >> > >> >> > >
> > > >> > >> >> >
> > > >> > >> >>
> > > >> > >>
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=VS1za1vOQhtlKlK4Tdgq3ej04OlhFoYfHziyNbgOIN4%3D&reserved=0
> > > >> > >> >> > > >
> > > >> > >> >> > > > Once this file goes in with the
> changes
> > to
> > > >> keep
> > > >> > >> the
> > > >> > >> >> method
> > > >> > >> >> > names
> > > >> > >> >> > > the same,
> > > >> > >> >> > > > there will be more tweaks to the
> release
> > > >> tasks
> > > >> > >> and then
> > > >> > >> >> we can
> > > >> > >> >> > > try cutting
> > > >> > >> >> > > > a release. I'm thinking we'll be at
> > that
> > > >> point
> > > >> > >> in
> > > >> > >> >> early May,
> > > >> > >> >> > so
> > > >> > >> >> > > now is the
> > > >> > >> >> > > > time to get stuff in for the 0.9.6
> > > release.
> > > >> > >> >> > > >
> > > >> > >> >> > > > Thanks,
> > > >> > >> >> > > > -Alex
> > > >> > >> >> > > >
> > > >> > >> >> > > > On 3/8/19, 9:27 AM, "Alex Harui" <
> > > >> > >> aharui@adobe.com>
> > > >> > >> >> wrote:
> > > >> > >> >> > > >
> > > >> > >> >> > > > I would much rather have others
> find
> > > and
> > > >> > fix
> > > >> > >> issues
> > > >> > >> >> > > themselves. That
> > > >> > >> >> > > > way, more people than just me will
> know
> > > how
> > > >> to
> > > >> > >> maintain
> > > >> > >> >> the
> > > >> > >> >> > > system. It
> > > >> > >> >> > > > actually turns out that, IMO, a group
> of
> > > >> people
> > > >> > >> can
> > > >> > >> >> work on the
> > > >> > >> >> > > release.
> > > >> > >> >> > > > There are 14 steps. Literally, 14
> > > different
> > > >> > >> people
> > > >> > >> >> could
> > > >> > >> >> > > execute one step
> > > >> > >> >> > > > each.
> > > >> > >> >> > > >
> > > >> > >> >> > > > My 2 cents,
> > > >> > >> >> > > > -Alex
> > > >> > >> >> > > >
> > > >> > >> >> > > > On 3/8/19, 2:13 AM, "Carlos
> Rovira"
> > <
> > > >> > >> >> > carlosrovira@apache.org>
> > > >> > >> >> > > wrote:
> > > >> > >> >> > > >
> > > >> > >> >> > > > Hi Alex,
> > > >> > >> >> > > >
> > > >> > >> >> > > > amazing work! congrats to
> reach
> > to
> > > >> this
> > > >> > >> point!
> > > >> > >> >> :)
> > > >> > >> >> > > >
> > > >> > >> >> > > > I need to put my head on all
> of
> > > >> this,
> > > >> > >> but count
> > > >> > >> >> on me
> > > >> > >> >> > to
> > > >> > >> >> > > be a RM.
> > > >> > >> >> > > > I think
> > > >> > >> >> > > > the best thing should be that
> > you
> > > be
> > > >> > the
> > > >> > >> first
> > > >> > >> >> RM to
> > > >> > >> >> > try
> > > >> > >> >> > > your own
> > > >> > >> >> > > > development at least for the
> > first
> > > >> > time,
> > > >> > >> and
> > > >> > >> >> then the
> > > >> > >> >> > > rest of us
> > > >> > >> >> > > > will
> > > >> > >> >> > > > follow you on the next
> releases.
> > > >> With
> > > >> > >> all this
> > > >> > >> >> on place
> > > >> > >> >> > > we maybe
> > > >> > >> >> > > > could
> > > >> > >> >> > > > release once a month or every
> > two
> > > >> > >> months...
> > > >> > >> >> > > >
> > > >> > >> >> > > > Thanks for doing this :)
> > > >> > >> >> > > >
> > > >> > >> >> > > > Carlos
> > > >> > >> >> > > >
> > > >> > >> >> > > >
> > > >> > >> >> > > > El vie., 8 mar. 2019 a las
> 1:55,
> > > >> Alex
> > > >> > >> Harui
> > > >> > >> >> > > > (<ah...@adobe.com.invalid>)
> > > >> > >> >> > > > escribió:
> > > >> > >> >> > > >
> > > >> > >> >> > > > > OK, I've now seen Jenkins
> > > perform
> > > >> the
> > > >> > >> steps
> > > >> > >> >> to build
> > > >> > >> >> > > the release
> > > >> > >> >> > > > > artifacts. Folks interested
> > in
> > > >> > >> Docker-izing
> > > >> > >> >> the
> > > >> > >> >> > steps
> > > >> > >> >> > > are
> > > >> > >> >> > > > welcome to look
> > > >> > >> >> > > > > at the jobs on the "Royale
> > > >> Release"
> > > >> > >> tab on
> > > >> > >> >> the CI
> > > >> > >> >> > > server.
> > > >> > >> >> > > > >
> > > >> > >> >> > > >
> > > >> > >> >> > >
> > > >> > >> >> >
> > > >> > >> >>
> > > >> > >>
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=LfWCyCaClCVgfeINn4%2B%2Bk%2FSVUFXvgyV7QxMtx4B%2B%2Fu0%3D&reserved=0
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > These steps assume that the
> RM
> > > can
> > > >> > run
> > > >> > >> the
> > > >> > >> >> basic
> > > >> > >> >> > Maven
> > > >> > >> >> > > and Ant
> > > >> > >> >> > > > build on
> > > >> > >> >> > > > > the RM's computer. I think
> > > that's
> > > >> a
> > > >> > >> fair
> > > >> > >> >> requirement
> > > >> > >> >> > > since all
> > > >> > >> >> > > > of us on the
> > > >> > >> >> > > > > PMC need to able to do that
> to
> > > >> build
> > > >> > >> the RC
> > > >> > >> >> in order
> > > >> > >> >> > > to vote on
> > > >> > >> >> > > > it.
> > > >> > >> >> > > > > Jenkins does other tasks
> like
> > > run
> > > >> > the
> > > >> > >> Maven
> > > >> > >> >> release
> > > >> > >> >> > > plugin
> > > >> > >> >> > > > steps.
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > Currently that results in
> > > >> binaries on
> > > >> > >> Jenkins
> > > >> > >> >> that
> > > >> > >> >> > are
> > > >> > >> >> > > > downloaded to the
> > > >> > >> >> > > > > RM's computer. These
> binaries
> > > >> need
> > > >> > to
> > > >> > >> be
> > > >> > >> >> verified by
> > > >> > >> >> > > the RM
> > > >> > >> >> > > > which is the
> > > >> > >> >> > > > > next phase I will be
> starting
> > on
> > > >> now.
> > > >> > >> The RM
> > > >> > >> >> > verifies
> > > >> > >> >> > > the bits
> > > >> > >> >> > > > and then
> > > >> > >> >> > > > > PGP signs them. And then
> the
> > > bits
> > > >> > are
> > > >> > >> >> uploaded off
> > > >> > >> >> > > the RM's
> > > >> > >> >> > > > computer to
> > > >> > >> >> > > > > Maven Staging or
> dist.a.o/dev.
> > > >> If
> > > >> > >> that
> > > >> > >> >> uploading
> > > >> > >> >> > > turns out to
> > > >> > >> >> > > > be a point
> > > >> > >> >> > > > > of failure, we have the
> option
> > > of
> > > >> > >> having
> > > >> > >> >> Jenkins
> > > >> > >> >> > > upload the big
> > > >> > >> >> > > > files and
> > > >> > >> >> > > > > have the RM only upload PGP
> > > >> signature
> > > >> > >> files.
> > > >> > >> >> Or
> > > >> > >> >> > > finding a way
> > > >> > >> >> > > > for Jenkins
> > > >> > >> >> > > > > to get the signature files
> > from
> > > >> the
> > > >> > >> RM. The
> > > >> > >> >> uploads
> > > >> > >> >> > > worked fine
> > > >> > >> >> > > > for me,
> > > >> > >> >> > > > > but then again, so did the
> old
> > > >> > script's
> > > >> > >> >> uploads.
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > Therefore, once I get the
> > binary
> > > >> > >> verification
> > > >> > >> >> phase
> > > >> > >> >> > > completed, I
> > > >> > >> >> > > > think
> > > >> > >> >> > > > > someone other than me should
> > be
> > > >> the
> > > >> > RM
> > > >> > >> and
> > > >> > >> >> try to use
> > > >> > >> >> > > these
> > > >> > >> >> > > > steps to
> > > >> > >> >> > > > > generate the release and
> help
> > > >> debug
> > > >> > the
> > > >> > >> >> process for
> > > >> > >> >> > > the next
> > > >> > >> >> > > > RM. So,
> > > >> > >> >> > > > > please try to carve out some
> > > time
> > > >> to
> > > >> > >> be the
> > > >> > >> >> RM. One
> > > >> > >> >> > > advantage
> > > >> > >> >> > > > of doing
> > > >> > >> >> > > > > most of the work on Jenkins
> is
> > > >> that
> > > >> > it
> > > >> > >> frees
> > > >> > >> >> up my
> > > >> > >> >> > > computer to
> > > >> > >> >> > > > do other
> > > >> > >> >> > > > > things while Jenkins is
> > cranking
> > > >> > away.
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > I think we're at least a
> week
> > > away
> > > >> > >> from binary
> > > >> > >> >> > > verification,
> > > >> > >> >> > > > maybe two, so
> > > >> > >> >> > > > > it is time to start thinking
> > > about
> > > >> > >> what is
> > > >> > >> >> going in
> > > >> > >> >> > > this release.
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > Thanks,
> > > >> > >> >> > > > > -Alex
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > On 3/7/19, 4:15 PM, "Alex
> > Harui"
> > > >> > >> >> > > <ah...@adobe.com.INVALID>
> > > >> > >> >> > > > wrote:
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > In case you haven't
> > guessed,
> > > >> I'm
> > > >> > >> testing
> > > >> > >> >> out
> > > >> > >> >> > > Jenkins and its
> > > >> > >> >> > > > ability
> > > >> > >> >> > > > > to create the artifacts and
> > send
> > > >> > >> emails.
> > > >> > >> >> Please
> > > >> > >> >> > > ignore any
> > > >> > >> >> > > > email that
> > > >> > >> >> > > > > looks like a vote or discuss
> > > >> thread.
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > Thanks,
> > > >> > >> >> > > > > -Alex
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > On 2/10/19, 8:44 PM,
> "Alex
> > > >> Harui"
> > > >> > >> >> > > <ah...@adobe.com.INVALID>
> > > >> > >> >> > > > wrote:
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > Om,
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > Well, that's what I
> > used
> > > >> for
> > > >> > >> the last
> > > >> > >> >> > > release. I'm sure
> > > >> > >> >> > > > there is
> > > >> > >> >> > > > > probably some inaccuracy in
> > it.
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > That said, I'm
> > > abandoning
> > > >> > that
> > > >> > >> >> document and
> > > >> > >> >> > > taking a new
> > > >> > >> >> > > > angle
> > > >> > >> >> > > > > because that document
> presumed
> > > >> that
> > > >> > the
> > > >> > >> >> release
> > > >> > >> >> > > manager was
> > > >> > >> >> > > > trying to
> > > >> > >> >> > > > > create a release on his/her
> > > >> computer.
> > > >> > >> I've
> > > >> > >> >> given up
> > > >> > >> >> > > on that and
> > > >> > >> >> > > > working on
> > > >> > >> >> > > > > making releases from a
> shared
> > > >> > computer
> > > >> > >> for the
> > > >> > >> >> > reasons
> > > >> > >> >> > > I've
> > > >> > >> >> > > > stated
> > > >> > >> >> > > > > upthread. I hope to make
> some
> > > >> > >> progress on
> > > >> > >> >> that this
> > > >> > >> >> > > week.
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > The key difference
> is
> > > that
> > > >> > the
> > > >> > >> new
> > > >> > >> >> angle does
> > > >> > >> >> > > not
> > > >> > >> >> > > > presume that you
> > > >> > >> >> > > > > have Git SSH and PGP
> > signatures
> > > >> all
> > > >> > >> set up on
> > > >> > >> >> some
> > > >> > >> >> > > computer. I
> > > >> > >> >> > > > have not
> > > >> > >> >> > > > > looked into how Docker would
> > > >> handle
> > > >> > >> that. You
> > > >> > >> >> > > certainly
> > > >> > >> >> > > > wouldn't want the
> > > >> > >> >> > > > > Docker image to contain your
> > SSH
> > > >> or
> > > >> > PGP
> > > >> > >> >> keys/creds.
> > > >> > >> >> > > And if the
> > > >> > >> >> > > > Docker
> > > >> > >> >> > > > > image doesn't, then that is
> > > >> another
> > > >> > >> stumbling
> > > >> > >> >> block
> > > >> > >> >> > > for future
> > > >> > >> >> > > > RMs.
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > The other key
> > difference
> > > >> is
> > > >> > >> that the
> > > >> > >> >> old
> > > >> > >> >> > > script presumed
> > > >> > >> >> > > > you could
> > > >> > >> >> > > > > create the 3 release in 3
> huge
> > > >> "easy"
> > > >> > >> steps.
> > > >> > >> >> We've
> > > >> > >> >> > > seen that is
> > > >> > >> >> > > > only true
> > > >> > >> >> > > > > for me. So the new angle
> > > creates
> > > >> > many
> > > >> > >> >> discrete steps
> > > >> > >> >> > > managed by
> > > >> > >> >> > > > Jenkins.
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > So, it is up to you
> to
> > > >> decide
> > > >> > >> what
> > > >> > >> >> you want
> > > >> > >> >> > to
> > > >> > >> >> > > > "Docker-ize". You
> > > >> > >> >> > > > > can try to Docker-ize the
> > > current
> > > >> 3
> > > >> > big
> > > >> > >> >> steps, so RMs
> > > >> > >> >> > > can try to
> > > >> > >> >> > > > run it on
> > > >> > >> >> > > > > their systems, but I'd bet
> > they
> > > >> will
> > > >> > >> just
> > > >> > >> >> faiI due to
> > > >> > >> >> > > network
> > > >> > >> >> > > > issues. I
> > > >> > >> >> > > > > would be interested in using
> > > >> Docker
> > > >> > to
> > > >> > >> make
> > > >> > >> >> each of
> > > >> > >> >> > > these many
> > > >> > >> >> > > > discrete
> > > >> > >> >> > > > > steps portable to another
> > > server.
> > > >> > >> I'm not
> > > >> > >> >> going to
> > > >> > >> >> > > involve
> > > >> > >> >> > > > Docker at this
> > > >> > >> >> > > > > point. My main goal is just
> > to
> > > >> see
> > > >> > if
> > > >> > >> I can
> > > >> > >> >> create a
> > > >> > >> >> > > workflow
> > > >> > >> >> > > > of many
> > > >> > >> >> > > > > discrete steps that isn't
> > > horribly
> > > >> > >> painful.
> > > >> > >> >> Once we
> > > >> > >> >> > > see what
> > > >> > >> >> > > > these steps
> > > >> > >> >> > > > > turn out to be, then we can
> > > worry
> > > >> > >> about server
> > > >> > >> >> > > portability of
> > > >> > >> >> > > > those steps.
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > Either way, we want
> to
> > > >> know
> > > >> > >> about
> > > >> > >> >> running
> > > >> > >> >> > > > Browser+Selenium for
> > > >> > >> >> > > > > sure. And maybe
> > > >> FlashPlayerDebugger
> > > >> > >> or AIR.
> > > >> > >> >> I would
> > > >> > >> >> > > want to
> > > >> > >> >> > > > know, for
> > > >> > >> >> > > > > example, how you debug a
> > failing
> > > >> > >> checkintest
> > > >> > >> >> in a
> > > >> > >> >> > > Docker
> > > >> > >> >> > > > container.
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > Thanks,
> > > >> > >> >> > > > > -Alex
> > > >> > >> >> > > > >
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > On 2/10/19, 5:18 PM,
> > > >> > "OmPrakash
> > > >> > >> >> Muppirala" <
> > > >> > >> >> > > > bigosmallm@gmail.com>
> > > >> > >> >> > > > > wrote:
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > Alex,
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > Just to be
> clear,
> > I
> > > am
> > > >> > >> following
> > > >> > >> >> the
> > > >> > >> >> > steps
> > > >> > >> >> > > from here
> > > >> > >> >> > > > to try
> > > >> > >> >> > > > > and setup a
> > > >> > >> >> > > > > docker
> container.
> > > >> > >> >> > > > >
> > > >> > >> >> > > > >
> > > >> > >> >> > > > >
> > > >> > >> >> > > >
> > > >> > >> >> > >
> > > >> > >> >> >
> > > >> > >>
> > > >> >
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=Lhm0hudN8Nbx%2F6Lnmz0Wlus3EpV1o1h8XWBzBUoEWOA%3D&reserved=0
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > Is this doc up
> to
> > > >> date?
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > Thanks,
> > > >> > >> >> > > > > Om
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > On Wed, Feb 6,
> > 2019
> > > at
> > > >> > >> 12:02 PM
> > > >> > >> >> OmPrakash
> > > >> > >> >> > > Muppirala <
> > > >> > >> >> > > > > bigosmallm@gmail.com>
> > > >> > >> >> > > > > wrote:
> > > >> > >> >> > > > >
> > > >> > >> >> > > > > > One approach
> is
> > to
> > > >> have
> > > >> > >> each
> > > >> > >> >> step in
> > > >> > >> >> > the
> > > >> > >> >> > > process
> > > >> > >> >> > > > spin up a
> > > >> > >> >> > > > > docker image.
> > > >> > >> >> > > > > > And use
> > > >> docker-compose
> > > >> > >> to run
> > > >> > >> >> each
> > > >> > >> >> > > step. All the
> > > >> > >> >> > > > images can
> > > >> > >> >> > > > > be made to
> > > >> > >> >> > > > > > share a common
> > > >> volume
> > > >> > >> where all
> > > >> > >> >> the
> > > >> > >> >> > > artifacts are
> > > >> > >> >> > > > stored
> > > >> > >> >> > > > > across steps.
> > > >> > >> >> > > > > >
> > > >> > >> >> > > > > > You are right
> > > about
> > > >> the
> > > >> > >> >> networking
> > > >> > >> >> > issue
> > > >> > >> >> > > though.
> > > >> > >> >> > > > Any
> > > >> > >> >> > > > > network related
> > > >> > >> >> > > > > > failure that
> > > occurs
> > > >> on
> > > >> > >> the host
> > > >> > >> >> machine
> > > >> > >> >> > > will most
> > > >> > >> >> > > > likely
> > > >> > >> >> > > > > occur in the
> > > >> > >> >> > > > > > docker
> > container.
> > > >> > >> Although, I
> > > >> > >> >> am not
> > > >> > >> >> > > clear how we
> > > >> > >> >> > > > can
> > > >> > >> >> > > > > guarantee that the
> > > >> > >> >> > > > > > same issues
> will
> > > not
> > > >> > >> occur on
> > > >> > >> >> the
> > > >> > >> >> > > Jenkins server.
> > > >> > >> >> > > > I mean,
> > > >> > >> >> > > > > what is special
> > > >> > >> >> > > > > > about the
> > Jenkins
> > > >> > server
> > > >> > >> that
> > > >> > >> >> makes it
> > > >> > >> >> > > immune to
> > > >> > >> >> > > > these
> > > >> > >> >> > > > > networking issues?
> > > >> > >> >> > > > > >
> > > >> > >> >> > > > > > Thanks,
> > > >> > >> >> > > > > > Om
> > > >> > >> >> > > > > >
> > > >> > >> >> > > > > > On Wed, Feb 6,
> > > 2019
> > > >> at
> > > >> > >> 11:48 AM
> > > >> > >> >> Alex
> > > >> > >> >> > > Harui
> > > >> > >> >> > > > > <ah...@adobe.com.invalid>
> > > >> > >> >> > > > > > wrote:
> > > >> > >> >> > > > > >
> > > >> > >> >> > > > > >> Again, I
> don't
> > > know
> > > >> > >> anything
> > > >> > >> >> about
> > > >> > >> >> > > Docker, but
> > > >> > >> >> > > > before we
> > > >> > >> >> > > > > spend a lot of
> > > >> > >> >> > > > > >> time on
> > Docker, I
> > > >> also
> > > >> > >> want to
> > > >> > >> >> point
> > > >> > >> >> > > out that the
> > > >> > >> >> > > > process
> > > >> > >> >> > > > > to create a
> > > >> > >> >> > > > > >> release
> cannot
> > > >> really
> > > >> > be
> > > >> > >> >> thought of as
> > > >> > >> >> > > "one
> > > >> > >> >> > > > application".
> > > >> > >> >> > > > > It will be a
> > > >> > >> >> > > > > >> series of
> > "steps"
> > > >> to
> > > >> > >> run.
> > > >> > >> >> How many
> > > >> > >> >> > > steps
> > > >> > >> >> > > > depends on
> > > >> > >> >> > > > > whether we think we
> > > >> > >> >> > > > > >> can isolate
> > > enough
> > > >> > >> stuff via
> > > >> > >> >> Docker to
> > > >> > >> >> > > be able to
> > > >> > >> >> > > > run
> > > >> > >> >> > > > > Docker on the RM's
> > > >> > >> >> > > > > >> computer
> > instead
> > > of
> > > >> > >> some shared
> > > >> > >> >> > > computer. On a
> > > >> > >> >> > > > shared
> > > >> > >> >> > > > > computer there will
> > > >> > >> >> > > > > >> be dozens of
> > > steps
> > > >> > >> because the
> > > >> > >> >> RM will
> > > >> > >> >> > > need to
> > > >> > >> >> > > > enter
> > > >> > >> >> > > > > passwords to commit
> > > >> > >> >> > > > > >> stuff. On a
> > > local
> > > >> > >> computer I
> > > >> > >> >> guess
> > > >> > >> >> > the
> > > >> > >> >> > > RM can
> > > >> > >> >> > > > supply
> > > >> > >> >> > > > > passwords but I think
> > > >> > >> >> > > > > >> there will be
> > > >> stopping
> > > >> > >> points
> > > >> > >> >> where
> > > >> > >> >> > the
> > > >> > >> >> > > Maven
> > > >> > >> >> > > > artifacts are
> > > >> > >> >> > > > > deployed and
> > > >> > >> >> > >
Re: 0.9.6 Release
Posted by Greg Dove <gr...@gmail.com>.
Thanks for clarifying Piotr. That one at least worked it seems.
I saw the problem elsewhere and first time it was because the compiler
build had required changes and did not complete before the framework.
The others have some issues, but I don't think it is related to my latest
changes , because it seems to be the same issue as previous fails. I will
try to figure those out tomorrow some time if I can.
On Tue, Jun 11, 2019 at 5:08 PM Piotr Zarzycki <pi...@gmail.com>
wrote:
> Greg,
>
> I was thinking about ant build on Jenkins [1]. I didn't check Maven build
> in a while.
>
> [1]
>
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/changes
>
> Thanks,
> Piotr
>
>
> On Tue, Jun 11, 2019, 6:48 AM Greg Dove <gr...@gmail.com> wrote:
>
> > Piotr, I hope I addressed the issue, but waiting to see...
> > It looks like it has been unstable for last 7 days , am I reading that
> > right? https://builds.apache.org/job/Royale-asjs/
> >
> >
> > On Tue, Jun 11, 2019 at 4:30 PM Greg Dove <gr...@gmail.com> wrote:
> >
> > > Working on it!
> > >
> > >
> > > On Tue, Jun 11, 2019 at 4:29 PM Piotr Zarzycki <
> > piotrzarzycki21@gmail.com>
> > > wrote:
> > >
> > >> Hi Greg,
> > >>
> > >> After your merge the goal should be that build on Jenkins is working
> > fine.
> > >> Please make sure that is happen.
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> On Tue, Jun 11, 2019, 5:32 AM Greg Dove <gr...@gmail.com> wrote:
> > >>
> > >> > I will stick with the plan of single commit, I think it should be
> > easier
> > >> > for you if there are any conflicts.
> > >> > Last build testing is running now in local develop. I will push
> after
> > >> > that...
> > >> >
> > >> > On Tue, Jun 11, 2019 at 3:15 PM Greg Dove <gr...@gmail.com>
> > wrote:
> > >> >
> > >> > >
> > >> > > Thanks Alex, I was planning to merge this as a single squashed
> > commit,
> > >> > > because it isolates all the changes to a single commit (but this
> > will
> > >> > mean
> > >> > > there are many changes in one hit).
> > >> > > Do you have a preference in terms of how easy it will make things
> > for
> > >> > you?
> > >> > >
> > >> > >
> > >> > > On Tue, Jun 11, 2019 at 3:07 PM Alex Harui
> <aharui@adobe.com.invalid
> > >
> > >> > > wrote:
> > >> > >
> > >> > >> OK, I will wait to see your commit emails. I will do some other
> > >> things
> > >> > >> like the wiki doc.
> > >> > >>
> > >> > >> -Alex
> > >> > >>
> > >> > >> On 6/10/19, 8:06 PM, "Greg Dove" <gr...@gmail.com> wrote:
> > >> > >>
> > >> > >> Hi Alex, I guess you might be back on Royale about now. Just
> a
> > >> heads
> > >> > >> up: I
> > >> > >> am about 20-30 mins max from merging in what I have. Hope
> > that's
> > >> > still
> > >> > >> ok... please let me know if not.
> > >> > >> Thanks,
> > >> > >> -Greg
> > >> > >>
> > >> > >>
> > >> > >> On Tue, Jun 11, 2019 at 7:51 AM Greg Dove <
> greg.dove@gmail.com
> > >
> > >> > >> wrote:
> > >> > >>
> > >> > >> >
> > >> > >> > Thanks Alex - I'll try to hit the window, much appreciated!
> > >> > >> >
> > >> > >> >
> > >> > >> > On Tue, Jun 11, 2019 at 6:57 AM Alex Harui
> > >> > <aharui@adobe.com.invalid
> > >> > >> >
> > >> > >> > wrote:
> > >> > >> >
> > >> > >> >> Hi Greg,
> > >> > >> >>
> > >> > >> >> It turns out I have a "split shift" today. I'm stopping
> > work
> > >> for
> > >> > >> the
> > >> > >> >> next 7 or 8 hours then will get around to the merge. So
> if
> > >> you
> > >> > >> can get
> > >> > >> >> your changes merged in that amount of time, then I will
> wait
> > >> for
> > >> > >> you and
> > >> > >> >> deal with any merge conflicts (there are almost certain to
> > be
> > >> > >> some).
> > >> > >> >>
> > >> > >> >> -Alex
> > >> > >> >>
> > >> > >> >> On 6/10/19, 11:46 AM, "Greg Dove" <gr...@gmail.com>
> > >> wrote:
> > >> > >> >>
> > >> > >> >> Alex, slightly OT, but in terms of coordination: fyi I
> > am
> > >> > also
> > >> > >> very
> > >> > >> >> close
> > >> > >> >> to merging the language improvements branch into
> > develop.
> > >> As
> > >> > I
> > >> > >> already
> > >> > >> >> mentioned elsewhere, I was hoping to do that a couple
> of
> > >> days
> > >> > >> back,
> > >> > >> >> but
> > >> > >> >> some recent things also took me a little longer than
> > >> expected
> > >> > >> (I have
> > >> > >> >> additional local changes/fixes not yet in remote
> branch)
> > >> . I
> > >> > >> was
> > >> > >> >> planning
> > >> > >> >> to merge that today also.
> > >> > >> >>
> > >> > >> >> However, I will wait until after your merge, so I'm
> > hoping
> > >> > you
> > >> > >> can get
> > >> > >> >> yours in today (if not, I will wait). I will probably
> > put
> > >> > mine
> > >> > >> in as a
> > >> > >> >> squashed commit after yours.
> > >> > >> >>
> > >> > >> >>
> > >> > >> >> On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <
> > >> > >> >> piotrzarzycki21@gmail.com>
> > >> > >> >> wrote:
> > >> > >> >>
> > >> > >> >> > Hi Alex,
> > >> > >> >> >
> > >> > >> >> > Many thanks for that! I will try to be RM. I will
> have
> > >> some
> > >> > >> >> dedicated time
> > >> > >> >> > for that. I will wait for your instruction and merge
> > to
> > >> > >> develop.
> > >> > >> >> >
> > >> > >> >> > Thanks,
> > >> > >> >> > Piotr
> > >> > >> >> >
> > >> > >> >> >
> > >> > >> >> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
> > >> > >> <ah...@adobe.com.invalid>
> > >> > >> >> wrote:
> > >> > >> >> >
> > >> > >> >> > > Well, that turned out to be much more
> time-consuming
> > >> > than I
> > >> > >> >> expected, but
> > >> > >> >> > > we can now create identical release artifacts on
> Mac
> > >> and
> > >> > >> Win. I
> > >> > >> >> am
> > >> > >> >> > hopeful
> > >> > >> >> > > this effort will pay off not only now in having
> > other
> > >> > folks
> > >> > >> >> generate
> > >> > >> >> > > releases, but also in the future if signed
> binaries
> > >> > become
> > >> > >> a
> > >> > >> >> requirement.
> > >> > >> >> > >
> > >> > >> >> > > There continues to be a lot of distractions in my
> > life
> > >> > >> that can
> > >> > >> >> cause
> > >> > >> >> > > delays, but I hope to merge the release_practice
> > >> branches
> > >> > >> into
> > >> > >> >> develop
> > >> > >> >> > over
> > >> > >> >> > > the next day or two and figure out where in the
> wiki
> > >> to
> > >> > >> document
> > >> > >> >> the
> > >> > >> >> > > release process. So, now is the time for one or
> > more
> > >> > >> people to
> > >> > >> >> step up
> > >> > >> >> > to
> > >> > >> >> > > be the RMs for 0.9.6 and help debug and improve
> the
> > >> > >> process.
> > >> > >> >> > >
> > >> > >> >> > > I am going to try very hard not to "own" the
> > >> process. If
> > >> > >> >> something goes
> > >> > >> >> > > wrong, I am going to ask others to try to debug
> and
> > >> fix
> > >> > it
> > >> > >> first
> > >> > >> >> because
> > >> > >> >> > it
> > >> > >> >> > > is in the project's best interests for others to
> > truly
> > >> > >> understand
> > >> > >> >> how
> > >> > >> >> > this
> > >> > >> >> > > stuff works.
> > >> > >> >> > >
> > >> > >> >> > > Thanks,
> > >> > >> >> > > -Alex
> > >> > >> >> > >
> > >> > >> >> > > On 5/23/19, 9:54 AM, "Alex Harui"
> > >> > <aharui@adobe.com.INVALID
> > >> > >> >
> > >> > >> >> wrote:
> > >> > >> >> > >
> > >> > >> >> > > It has turned out to be harder than expected
> to
> > >> get
> > >> > >> the same
> > >> > >> >> binaries
> > >> > >> >> > > on Mac and Win. I now have the identical binaries
> > for
> > >> > >> >> royale-compiler
> > >> > >> >> > and
> > >> > >> >> > > royale-typedefs Maven artifacts and am starting on
> > >> > >> royale-asjs.
> > >> > >> >> I might
> > >> > >> >> > > get lucky and the changes that fixed
> royale-typedefs
> > >> SWCs
> > >> > >> will
> > >> > >> >> magically
> > >> > >> >> > > get the royale-asjs SWCs to match. Then we have
> to
> > >> make
> > >> > >> the Ant
> > >> > >> >> > artifacts
> > >> > >> >> > > match.
> > >> > >> >> > >
> > >> > >> >> > > There have been a lot of distractions in my
> > >> non-work
> > >> > >> life
> > >> > >> >> which has
> > >> > >> >> > > also impeded progress. I hope to make much
> progress
> > >> this
> > >> > >> coming
> > >> > >> >> week and
> > >> > >> >> > > if we're lucky, I will be asking for a volunteer
> (or
> > >> > >> volunteers)
> > >> > >> >> to test
> > >> > >> >> > > drive all of this stuff and be the RM for 0.9.6.
> I
> > am
> > >> > not
> > >> > >> going
> > >> > >> >> to be
> > >> > >> >> > the
> > >> > >> >> > > RM.
> > >> > >> >> > >
> > >> > >> >> > > -Alex
> > >> > >> >> > >
> > >> > >> >> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> > >> > >> >> piotrzarzycki21@gmail.com>
> > >> > >> >> > > wrote:
> > >> > >> >> > >
> > >> > >> >> > > Hi Alex,
> > >> > >> >> > >
> > >> > >> >> > > It's been a while since you have started
> > >> effort
> > >> > >> with
> > >> > >> >> automating
> > >> > >> >> > > build.
> > >> > >> >> > > Where are you with that ? Are we closer to
> > >> > started
> > >> > >> 0.9.6.
> > >> > >> >> Do you
> > >> > >> >> > > need any
> > >> > >> >> > > help with this ?
> > >> > >> >> > >
> > >> > >> >> > > Thanks,
> > >> > >> >> > > Piotr
> > >> > >> >> > >
> > >> > >> >> > > wt., 2 kwi 2019 o 19:30 Alex Harui
> > >> > >> >> <ah...@adobe.com.invalid>
> > >> > >> >> > > napisał(a):
> > >> > >> >> > >
> > >> > >> >> > > > Update:
> > >> > >> >> > > >
> > >> > >> >> > > > In order to make verification of binary
> > >> release
> > >> > >> packages
> > >> > >> >> > created
> > >> > >> >> > > on the
> > >> > >> >> > > > server easier, I have made changes to
> our
> > >> build
> > >> > >> scripts
> > >> > >> >> and
> > >> > >> >> > > tools to try to
> > >> > >> >> > > > generate reproducible binaries. I've
> seen
> > >> two
> > >> > >> >> different builds
> > >> > >> >> > > compare on
> > >> > >> >> > > > my Mac. The next challenge will be to
> > see
> > >> if
> > >> > >> the
> > >> > >> >> server can
> > >> > >> >> > > build a
> > >> > >> >> > > > package on Windows that will compare on
> > Mac.
> > >> > >> >> > > >
> > >> > >> >> > > > One of the changes I needed to make is
> to
> > >> > >> JBurg. The
> > >> > >> >> version
> > >> > >> >> > of
> > >> > >> >> > > JBurg we
> > >> > >> >> > > > use generates method names including a
> > hash
> > >> > that
> > >> > >> doesn't
> > >> > >> >> > > reproduce the same
> > >> > >> >> > > > name each time. I have changes to JBurg
> > >> ready,
> > >> > >> however
> > >> > >> >> JBurg
> > >> > >> >> > is
> > >> > >> >> > > currently
> > >> > >> >> > > > under CPL which is category B. We only
> > need
> > >> > one
> > >> > >> file,
> > >> > >> >> we don't
> > >> > >> >> > > need or
> > >> > >> >> > > > want all of JBurg at this time. The one
> > >> JBurg
> > >> > >> file is
> > >> > >> >> jointly
> > >> > >> >> > > owned by
> > >> > >> >> > > > Adobe and Tom Harwood. I've contact Tom
> > >> and he
> > >> > >> will be
> > >> > >> >> filing
> > >> > >> >> > > an ICLA and
> > >> > >> >> > > > has given me permission to commit the
> > lines
> > >> he
> > >> > >> owns in
> > >> > >> >> that one
> > >> > >> >> > > file.
> > >> > >> >> > > >
> > >> > >> >> > > > This is the revision of the file that
> will
> > >> be
> > >> > >> donated by
> > >> > >> >> > > Tom/Adobe.
> > >> > >> >> > > >
> > >> > >> >> > > >
> > >> > >> >> > >
> > >> > >> >> >
> > >> > >> >>
> > >> > >>
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=VS1za1vOQhtlKlK4Tdgq3ej04OlhFoYfHziyNbgOIN4%3D&reserved=0
> > >> > >> >> > > >
> > >> > >> >> > > > Once this file goes in with the changes
> to
> > >> keep
> > >> > >> the
> > >> > >> >> method
> > >> > >> >> > names
> > >> > >> >> > > the same,
> > >> > >> >> > > > there will be more tweaks to the release
> > >> tasks
> > >> > >> and then
> > >> > >> >> we can
> > >> > >> >> > > try cutting
> > >> > >> >> > > > a release. I'm thinking we'll be at
> that
> > >> point
> > >> > >> in
> > >> > >> >> early May,
> > >> > >> >> > so
> > >> > >> >> > > now is the
> > >> > >> >> > > > time to get stuff in for the 0.9.6
> > release.
> > >> > >> >> > > >
> > >> > >> >> > > > Thanks,
> > >> > >> >> > > > -Alex
> > >> > >> >> > > >
> > >> > >> >> > > > On 3/8/19, 9:27 AM, "Alex Harui" <
> > >> > >> aharui@adobe.com>
> > >> > >> >> wrote:
> > >> > >> >> > > >
> > >> > >> >> > > > I would much rather have others find
> > and
> > >> > fix
> > >> > >> issues
> > >> > >> >> > > themselves. That
> > >> > >> >> > > > way, more people than just me will know
> > how
> > >> to
> > >> > >> maintain
> > >> > >> >> the
> > >> > >> >> > > system. It
> > >> > >> >> > > > actually turns out that, IMO, a group of
> > >> people
> > >> > >> can
> > >> > >> >> work on the
> > >> > >> >> > > release.
> > >> > >> >> > > > There are 14 steps. Literally, 14
> > different
> > >> > >> people
> > >> > >> >> could
> > >> > >> >> > > execute one step
> > >> > >> >> > > > each.
> > >> > >> >> > > >
> > >> > >> >> > > > My 2 cents,
> > >> > >> >> > > > -Alex
> > >> > >> >> > > >
> > >> > >> >> > > > On 3/8/19, 2:13 AM, "Carlos Rovira"
> <
> > >> > >> >> > carlosrovira@apache.org>
> > >> > >> >> > > wrote:
> > >> > >> >> > > >
> > >> > >> >> > > > Hi Alex,
> > >> > >> >> > > >
> > >> > >> >> > > > amazing work! congrats to reach
> to
> > >> this
> > >> > >> point!
> > >> > >> >> :)
> > >> > >> >> > > >
> > >> > >> >> > > > I need to put my head on all of
> > >> this,
> > >> > >> but count
> > >> > >> >> on me
> > >> > >> >> > to
> > >> > >> >> > > be a RM.
> > >> > >> >> > > > I think
> > >> > >> >> > > > the best thing should be that
> you
> > be
> > >> > the
> > >> > >> first
> > >> > >> >> RM to
> > >> > >> >> > try
> > >> > >> >> > > your own
> > >> > >> >> > > > development at least for the
> first
> > >> > time,
> > >> > >> and
> > >> > >> >> then the
> > >> > >> >> > > rest of us
> > >> > >> >> > > > will
> > >> > >> >> > > > follow you on the next releases.
> > >> With
> > >> > >> all this
> > >> > >> >> on place
> > >> > >> >> > > we maybe
> > >> > >> >> > > > could
> > >> > >> >> > > > release once a month or every
> two
> > >> > >> months...
> > >> > >> >> > > >
> > >> > >> >> > > > Thanks for doing this :)
> > >> > >> >> > > >
> > >> > >> >> > > > Carlos
> > >> > >> >> > > >
> > >> > >> >> > > >
> > >> > >> >> > > > El vie., 8 mar. 2019 a las 1:55,
> > >> Alex
> > >> > >> Harui
> > >> > >> >> > > > (<ah...@adobe.com.invalid>)
> > >> > >> >> > > > escribió:
> > >> > >> >> > > >
> > >> > >> >> > > > > OK, I've now seen Jenkins
> > perform
> > >> the
> > >> > >> steps
> > >> > >> >> to build
> > >> > >> >> > > the release
> > >> > >> >> > > > > artifacts. Folks interested
> in
> > >> > >> Docker-izing
> > >> > >> >> the
> > >> > >> >> > steps
> > >> > >> >> > > are
> > >> > >> >> > > > welcome to look
> > >> > >> >> > > > > at the jobs on the "Royale
> > >> Release"
> > >> > >> tab on
> > >> > >> >> the CI
> > >> > >> >> > > server.
> > >> > >> >> > > > >
> > >> > >> >> > > >
> > >> > >> >> > >
> > >> > >> >> >
> > >> > >> >>
> > >> > >>
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=LfWCyCaClCVgfeINn4%2B%2Bk%2FSVUFXvgyV7QxMtx4B%2B%2Fu0%3D&reserved=0
> > >> > >> >> > > > >
> > >> > >> >> > > > > These steps assume that the RM
> > can
> > >> > run
> > >> > >> the
> > >> > >> >> basic
> > >> > >> >> > Maven
> > >> > >> >> > > and Ant
> > >> > >> >> > > > build on
> > >> > >> >> > > > > the RM's computer. I think
> > that's
> > >> a
> > >> > >> fair
> > >> > >> >> requirement
> > >> > >> >> > > since all
> > >> > >> >> > > > of us on the
> > >> > >> >> > > > > PMC need to able to do that to
> > >> build
> > >> > >> the RC
> > >> > >> >> in order
> > >> > >> >> > > to vote on
> > >> > >> >> > > > it.
> > >> > >> >> > > > > Jenkins does other tasks like
> > run
> > >> > the
> > >> > >> Maven
> > >> > >> >> release
> > >> > >> >> > > plugin
> > >> > >> >> > > > steps.
> > >> > >> >> > > > >
> > >> > >> >> > > > > Currently that results in
> > >> binaries on
> > >> > >> Jenkins
> > >> > >> >> that
> > >> > >> >> > are
> > >> > >> >> > > > downloaded to the
> > >> > >> >> > > > > RM's computer. These binaries
> > >> need
> > >> > to
> > >> > >> be
> > >> > >> >> verified by
> > >> > >> >> > > the RM
> > >> > >> >> > > > which is the
> > >> > >> >> > > > > next phase I will be starting
> on
> > >> now.
> > >> > >> The RM
> > >> > >> >> > verifies
> > >> > >> >> > > the bits
> > >> > >> >> > > > and then
> > >> > >> >> > > > > PGP signs them. And then the
> > bits
> > >> > are
> > >> > >> >> uploaded off
> > >> > >> >> > > the RM's
> > >> > >> >> > > > computer to
> > >> > >> >> > > > > Maven Staging or dist.a.o/dev.
> > >> If
> > >> > >> that
> > >> > >> >> uploading
> > >> > >> >> > > turns out to
> > >> > >> >> > > > be a point
> > >> > >> >> > > > > of failure, we have the option
> > of
> > >> > >> having
> > >> > >> >> Jenkins
> > >> > >> >> > > upload the big
> > >> > >> >> > > > files and
> > >> > >> >> > > > > have the RM only upload PGP
> > >> signature
> > >> > >> files.
> > >> > >> >> Or
> > >> > >> >> > > finding a way
> > >> > >> >> > > > for Jenkins
> > >> > >> >> > > > > to get the signature files
> from
> > >> the
> > >> > >> RM. The
> > >> > >> >> uploads
> > >> > >> >> > > worked fine
> > >> > >> >> > > > for me,
> > >> > >> >> > > > > but then again, so did the old
> > >> > script's
> > >> > >> >> uploads.
> > >> > >> >> > > > >
> > >> > >> >> > > > > Therefore, once I get the
> binary
> > >> > >> verification
> > >> > >> >> phase
> > >> > >> >> > > completed, I
> > >> > >> >> > > > think
> > >> > >> >> > > > > someone other than me should
> be
> > >> the
> > >> > RM
> > >> > >> and
> > >> > >> >> try to use
> > >> > >> >> > > these
> > >> > >> >> > > > steps to
> > >> > >> >> > > > > generate the release and help
> > >> debug
> > >> > the
> > >> > >> >> process for
> > >> > >> >> > > the next
> > >> > >> >> > > > RM. So,
> > >> > >> >> > > > > please try to carve out some
> > time
> > >> to
> > >> > >> be the
> > >> > >> >> RM. One
> > >> > >> >> > > advantage
> > >> > >> >> > > > of doing
> > >> > >> >> > > > > most of the work on Jenkins is
> > >> that
> > >> > it
> > >> > >> frees
> > >> > >> >> up my
> > >> > >> >> > > computer to
> > >> > >> >> > > > do other
> > >> > >> >> > > > > things while Jenkins is
> cranking
> > >> > away.
> > >> > >> >> > > > >
> > >> > >> >> > > > > I think we're at least a week
> > away
> > >> > >> from binary
> > >> > >> >> > > verification,
> > >> > >> >> > > > maybe two, so
> > >> > >> >> > > > > it is time to start thinking
> > about
> > >> > >> what is
> > >> > >> >> going in
> > >> > >> >> > > this release.
> > >> > >> >> > > > >
> > >> > >> >> > > > > Thanks,
> > >> > >> >> > > > > -Alex
> > >> > >> >> > > > >
> > >> > >> >> > > > > On 3/7/19, 4:15 PM, "Alex
> Harui"
> > >> > >> >> > > <ah...@adobe.com.INVALID>
> > >> > >> >> > > > wrote:
> > >> > >> >> > > > >
> > >> > >> >> > > > > In case you haven't
> guessed,
> > >> I'm
> > >> > >> testing
> > >> > >> >> out
> > >> > >> >> > > Jenkins and its
> > >> > >> >> > > > ability
> > >> > >> >> > > > > to create the artifacts and
> send
> > >> > >> emails.
> > >> > >> >> Please
> > >> > >> >> > > ignore any
> > >> > >> >> > > > email that
> > >> > >> >> > > > > looks like a vote or discuss
> > >> thread.
> > >> > >> >> > > > >
> > >> > >> >> > > > > Thanks,
> > >> > >> >> > > > > -Alex
> > >> > >> >> > > > >
> > >> > >> >> > > > > On 2/10/19, 8:44 PM, "Alex
> > >> Harui"
> > >> > >> >> > > <ah...@adobe.com.INVALID>
> > >> > >> >> > > > wrote:
> > >> > >> >> > > > >
> > >> > >> >> > > > > Om,
> > >> > >> >> > > > >
> > >> > >> >> > > > > Well, that's what I
> used
> > >> for
> > >> > >> the last
> > >> > >> >> > > release. I'm sure
> > >> > >> >> > > > there is
> > >> > >> >> > > > > probably some inaccuracy in
> it.
> > >> > >> >> > > > >
> > >> > >> >> > > > > That said, I'm
> > abandoning
> > >> > that
> > >> > >> >> document and
> > >> > >> >> > > taking a new
> > >> > >> >> > > > angle
> > >> > >> >> > > > > because that document presumed
> > >> that
> > >> > the
> > >> > >> >> release
> > >> > >> >> > > manager was
> > >> > >> >> > > > trying to
> > >> > >> >> > > > > create a release on his/her
> > >> computer.
> > >> > >> I've
> > >> > >> >> given up
> > >> > >> >> > > on that and
> > >> > >> >> > > > working on
> > >> > >> >> > > > > making releases from a shared
> > >> > computer
> > >> > >> for the
> > >> > >> >> > reasons
> > >> > >> >> > > I've
> > >> > >> >> > > > stated
> > >> > >> >> > > > > upthread. I hope to make some
> > >> > >> progress on
> > >> > >> >> that this
> > >> > >> >> > > week.
> > >> > >> >> > > > >
> > >> > >> >> > > > > The key difference is
> > that
> > >> > the
> > >> > >> new
> > >> > >> >> angle does
> > >> > >> >> > > not
> > >> > >> >> > > > presume that you
> > >> > >> >> > > > > have Git SSH and PGP
> signatures
> > >> all
> > >> > >> set up on
> > >> > >> >> some
> > >> > >> >> > > computer. I
> > >> > >> >> > > > have not
> > >> > >> >> > > > > looked into how Docker would
> > >> handle
> > >> > >> that. You
> > >> > >> >> > > certainly
> > >> > >> >> > > > wouldn't want the
> > >> > >> >> > > > > Docker image to contain your
> SSH
> > >> or
> > >> > PGP
> > >> > >> >> keys/creds.
> > >> > >> >> > > And if the
> > >> > >> >> > > > Docker
> > >> > >> >> > > > > image doesn't, then that is
> > >> another
> > >> > >> stumbling
> > >> > >> >> block
> > >> > >> >> > > for future
> > >> > >> >> > > > RMs.
> > >> > >> >> > > > >
> > >> > >> >> > > > > The other key
> difference
> > >> is
> > >> > >> that the
> > >> > >> >> old
> > >> > >> >> > > script presumed
> > >> > >> >> > > > you could
> > >> > >> >> > > > > create the 3 release in 3 huge
> > >> "easy"
> > >> > >> steps.
> > >> > >> >> We've
> > >> > >> >> > > seen that is
> > >> > >> >> > > > only true
> > >> > >> >> > > > > for me. So the new angle
> > creates
> > >> > many
> > >> > >> >> discrete steps
> > >> > >> >> > > managed by
> > >> > >> >> > > > Jenkins.
> > >> > >> >> > > > >
> > >> > >> >> > > > > So, it is up to you to
> > >> decide
> > >> > >> what
> > >> > >> >> you want
> > >> > >> >> > to
> > >> > >> >> > > > "Docker-ize". You
> > >> > >> >> > > > > can try to Docker-ize the
> > current
> > >> 3
> > >> > big
> > >> > >> >> steps, so RMs
> > >> > >> >> > > can try to
> > >> > >> >> > > > run it on
> > >> > >> >> > > > > their systems, but I'd bet
> they
> > >> will
> > >> > >> just
> > >> > >> >> faiI due to
> > >> > >> >> > > network
> > >> > >> >> > > > issues. I
> > >> > >> >> > > > > would be interested in using
> > >> Docker
> > >> > to
> > >> > >> make
> > >> > >> >> each of
> > >> > >> >> > > these many
> > >> > >> >> > > > discrete
> > >> > >> >> > > > > steps portable to another
> > server.
> > >> > >> I'm not
> > >> > >> >> going to
> > >> > >> >> > > involve
> > >> > >> >> > > > Docker at this
> > >> > >> >> > > > > point. My main goal is just
> to
> > >> see
> > >> > if
> > >> > >> I can
> > >> > >> >> create a
> > >> > >> >> > > workflow
> > >> > >> >> > > > of many
> > >> > >> >> > > > > discrete steps that isn't
> > horribly
> > >> > >> painful.
> > >> > >> >> Once we
> > >> > >> >> > > see what
> > >> > >> >> > > > these steps
> > >> > >> >> > > > > turn out to be, then we can
> > worry
> > >> > >> about server
> > >> > >> >> > > portability of
> > >> > >> >> > > > those steps.
> > >> > >> >> > > > >
> > >> > >> >> > > > > Either way, we want to
> > >> know
> > >> > >> about
> > >> > >> >> running
> > >> > >> >> > > > Browser+Selenium for
> > >> > >> >> > > > > sure. And maybe
> > >> FlashPlayerDebugger
> > >> > >> or AIR.
> > >> > >> >> I would
> > >> > >> >> > > want to
> > >> > >> >> > > > know, for
> > >> > >> >> > > > > example, how you debug a
> failing
> > >> > >> checkintest
> > >> > >> >> in a
> > >> > >> >> > > Docker
> > >> > >> >> > > > container.
> > >> > >> >> > > > >
> > >> > >> >> > > > > Thanks,
> > >> > >> >> > > > > -Alex
> > >> > >> >> > > > >
> > >> > >> >> > > > >
> > >> > >> >> > > > > On 2/10/19, 5:18 PM,
> > >> > "OmPrakash
> > >> > >> >> Muppirala" <
> > >> > >> >> > > > bigosmallm@gmail.com>
> > >> > >> >> > > > > wrote:
> > >> > >> >> > > > >
> > >> > >> >> > > > > Alex,
> > >> > >> >> > > > >
> > >> > >> >> > > > > Just to be clear,
> I
> > am
> > >> > >> following
> > >> > >> >> the
> > >> > >> >> > steps
> > >> > >> >> > > from here
> > >> > >> >> > > > to try
> > >> > >> >> > > > > and setup a
> > >> > >> >> > > > > docker container.
> > >> > >> >> > > > >
> > >> > >> >> > > > >
> > >> > >> >> > > > >
> > >> > >> >> > > >
> > >> > >> >> > >
> > >> > >> >> >
> > >> > >>
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=Lhm0hudN8Nbx%2F6Lnmz0Wlus3EpV1o1h8XWBzBUoEWOA%3D&reserved=0
> > >> > >> >> > > > >
> > >> > >> >> > > > > Is this doc up to
> > >> date?
> > >> > >> >> > > > >
> > >> > >> >> > > > > Thanks,
> > >> > >> >> > > > > Om
> > >> > >> >> > > > >
> > >> > >> >> > > > > On Wed, Feb 6,
> 2019
> > at
> > >> > >> 12:02 PM
> > >> > >> >> OmPrakash
> > >> > >> >> > > Muppirala <
> > >> > >> >> > > > > bigosmallm@gmail.com>
> > >> > >> >> > > > > wrote:
> > >> > >> >> > > > >
> > >> > >> >> > > > > > One approach is
> to
> > >> have
> > >> > >> each
> > >> > >> >> step in
> > >> > >> >> > the
> > >> > >> >> > > process
> > >> > >> >> > > > spin up a
> > >> > >> >> > > > > docker image.
> > >> > >> >> > > > > > And use
> > >> docker-compose
> > >> > >> to run
> > >> > >> >> each
> > >> > >> >> > > step. All the
> > >> > >> >> > > > images can
> > >> > >> >> > > > > be made to
> > >> > >> >> > > > > > share a common
> > >> volume
> > >> > >> where all
> > >> > >> >> the
> > >> > >> >> > > artifacts are
> > >> > >> >> > > > stored
> > >> > >> >> > > > > across steps.
> > >> > >> >> > > > > >
> > >> > >> >> > > > > > You are right
> > about
> > >> the
> > >> > >> >> networking
> > >> > >> >> > issue
> > >> > >> >> > > though.
> > >> > >> >> > > > Any
> > >> > >> >> > > > > network related
> > >> > >> >> > > > > > failure that
> > occurs
> > >> on
> > >> > >> the host
> > >> > >> >> machine
> > >> > >> >> > > will most
> > >> > >> >> > > > likely
> > >> > >> >> > > > > occur in the
> > >> > >> >> > > > > > docker
> container.
> > >> > >> Although, I
> > >> > >> >> am not
> > >> > >> >> > > clear how we
> > >> > >> >> > > > can
> > >> > >> >> > > > > guarantee that the
> > >> > >> >> > > > > > same issues will
> > not
> > >> > >> occur on
> > >> > >> >> the
> > >> > >> >> > > Jenkins server.
> > >> > >> >> > > > I mean,
> > >> > >> >> > > > > what is special
> > >> > >> >> > > > > > about the
> Jenkins
> > >> > server
> > >> > >> that
> > >> > >> >> makes it
> > >> > >> >> > > immune to
> > >> > >> >> > > > these
> > >> > >> >> > > > > networking issues?
> > >> > >> >> > > > > >
> > >> > >> >> > > > > > Thanks,
> > >> > >> >> > > > > > Om
> > >> > >> >> > > > > >
> > >> > >> >> > > > > > On Wed, Feb 6,
> > 2019
> > >> at
> > >> > >> 11:48 AM
> > >> > >> >> Alex
> > >> > >> >> > > Harui
> > >> > >> >> > > > > <ah...@adobe.com.invalid>
> > >> > >> >> > > > > > wrote:
> > >> > >> >> > > > > >
> > >> > >> >> > > > > >> Again, I don't
> > know
> > >> > >> anything
> > >> > >> >> about
> > >> > >> >> > > Docker, but
> > >> > >> >> > > > before we
> > >> > >> >> > > > > spend a lot of
> > >> > >> >> > > > > >> time on
> Docker, I
> > >> also
> > >> > >> want to
> > >> > >> >> point
> > >> > >> >> > > out that the
> > >> > >> >> > > > process
> > >> > >> >> > > > > to create a
> > >> > >> >> > > > > >> release cannot
> > >> really
> > >> > be
> > >> > >> >> thought of as
> > >> > >> >> > > "one
> > >> > >> >> > > > application".
> > >> > >> >> > > > > It will be a
> > >> > >> >> > > > > >> series of
> "steps"
> > >> to
> > >> > >> run.
> > >> > >> >> How many
> > >> > >> >> > > steps
> > >> > >> >> > > > depends on
> > >> > >> >> > > > > whether we think we
> > >> > >> >> > > > > >> can isolate
> > enough
> > >> > >> stuff via
> > >> > >> >> Docker to
> > >> > >> >> > > be able to
> > >> > >> >> > > > run
> > >> > >> >> > > > > Docker on the RM's
> > >> > >> >> > > > > >> computer
> instead
> > of
> > >> > >> some shared
> > >> > >> >> > > computer. On a
> > >> > >> >> > > > shared
> > >> > >> >> > > > > computer there will
> > >> > >> >> > > > > >> be dozens of
> > steps
> > >> > >> because the
> > >> > >> >> RM will
> > >> > >> >> > > need to
> > >> > >> >> > > > enter
> > >> > >> >> > > > > passwords to commit
> > >> > >> >> > > > > >> stuff. On a
> > local
> > >> > >> computer I
> > >> > >> >> guess
> > >> > >> >> > the
> > >> > >> >> > > RM can
> > >> > >> >> > > > supply
> > >> > >> >> > > > > passwords but I think
> > >> > >> >> > > > > >> there will be
> > >> stopping
> > >> > >> points
> > >> > >> >> where
> > >> > >> >> > the
> > >> > >> >> > > Maven
> > >> > >> >> > > > artifacts are
> > >> > >> >> > > > > deployed and
> > >> > >> >> > > > > >> the staging
> repo
> > is
> > >> > >> closed, and
> > >> > >> >> > another
> > >> > >> >> > > stopping
> > >> > >> >> > > > point for
> > >> > >> >> > > > > the vote. It
> > >> > >> >> > > > > >> seems like
> Docker
> > >> > works
> > >> > >> by
> > >> > >> >> downloading
> > >> > >> >> > > > dependencies. Given
> > >> > >> >> > > > > that the
> > >> > >> >> > > > > >> problem the RMs
> > had
> > >> > >> last time
> > >> > >> >> involved
> > >> > >> >> > > downloads
> > >> > >> >> > > > and
> > >> > >> >> > > > > uploads, why do we
> > >> > >> >> > > > > >> think Docker
> will
> > >> > >> really solve
> > >> > >> >> this
> > >> > >> >> > for
> > >> > >> >> > > creating
> > >> > >> >> > > > releases
> > >> > >> >> > > > > on local machines?
> > >> > >> >> > > > > >>
> > >> > >> >> > > > > >> The reason to
> do
> > >> this
> > >> > >> on a
> > >> > >> >> shared
> > >> > >> >> > > machine is so
> > >> > >> >> > > > that new
> > >> > >> >> > > > > RMs don't have
> > >> > >> >> > > > > >> to do as much
> > >> setup.
> > >> > >> But then
> > >> > >> >> I
> > >> > >> >> > wonder
> > >> > >> >> > > about the
> > >> > >> >> > > > > efficiency of kicking off
> > >> > >> >> > > > > >> that many
> Docker
> > >> > images.
> > >> > >> >> Jenkins can
> > >> > >> >> > > manage that
> > >> > >> >> > > > already.
> > >> > >> >> > > > > Does Docker
> > >> > >> >> > > > > >> have some sort
> of
> > >> > >> similar
> > >> > >> >> Dashboard or
> > >> > >> >> > > would we
> > >> > >> >> > > > use Jenkins
> > >> > >> >> > > > > to kick off
> > >> > >> >> > > > > >> Docker steps?
> I
> > >> can't
> > >> > >> quite
> > >> > >> >> picture
> > >> > >> >> > > what is the
> > >> > >> >> > > > outermost
> > >> > >> >> > > > > >>
> > control/dashboard.
> > >> > >> >> > > > > >>
> > >> > >> >> > > > > >> -Alex
> > >> > >> >> > > > > >>
> > >> > >> >> > > > > >> On 2/6/19,
> 11:03
> > >> AM,
> > >> > >> "Harbs" <
> > >> > >> >> > > > harbs.lists@gmail.com> wrote:
> > >> > >> >> > > > > >>
> > >> > >> >> > > > > >> A quick
> > search
> > >> > >> turns up
> > >> > >> >> this:
> > >> > >> >> > > > > >>
> > >> > >> >> > > > > >>
> > >> > >> >> > > > > >>
> > >> > >> >> > > > >
> > >> > >> >> > > >
> > >> > >> >> > >
> > >> > >> >> >
> > >> > >>
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
> > >> > >> >> > > > > >> <
> > >> > >> >> > > > > >>
> > >> > >> >> > > > >
> > >> > >> >> > > >
> > >> > >> >> > >
> > >> > >> >> >
> > >> > >>
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
> >
>
0.9.6 Release
Posted by Piotr Zarzycki <pi...@gmail.com>.
Greg,
I was thinking about ant build on Jenkins [1]. I didn't check Maven build
in a while.
[1]
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/changes
Thanks,
Piotr
On Tue, Jun 11, 2019, 6:48 AM Greg Dove <gr...@gmail.com> wrote:
> Piotr, I hope I addressed the issue, but waiting to see...
> It looks like it has been unstable for last 7 days , am I reading that
> right? https://builds.apache.org/job/Royale-asjs/
>
>
> On Tue, Jun 11, 2019 at 4:30 PM Greg Dove <gr...@gmail.com> wrote:
>
> > Working on it!
> >
> >
> > On Tue, Jun 11, 2019 at 4:29 PM Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> > wrote:
> >
> >> Hi Greg,
> >>
> >> After your merge the goal should be that build on Jenkins is working
> fine.
> >> Please make sure that is happen.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> On Tue, Jun 11, 2019, 5:32 AM Greg Dove <gr...@gmail.com> wrote:
> >>
> >> > I will stick with the plan of single commit, I think it should be
> easier
> >> > for you if there are any conflicts.
> >> > Last build testing is running now in local develop. I will push after
> >> > that...
> >> >
> >> > On Tue, Jun 11, 2019 at 3:15 PM Greg Dove <gr...@gmail.com>
> wrote:
> >> >
> >> > >
> >> > > Thanks Alex, I was planning to merge this as a single squashed
> commit,
> >> > > because it isolates all the changes to a single commit (but this
> will
> >> > mean
> >> > > there are many changes in one hit).
> >> > > Do you have a preference in terms of how easy it will make things
> for
> >> > you?
> >> > >
> >> > >
> >> > > On Tue, Jun 11, 2019 at 3:07 PM Alex Harui <aharui@adobe.com.invalid
> >
> >> > > wrote:
> >> > >
> >> > >> OK, I will wait to see your commit emails. I will do some other
> >> things
> >> > >> like the wiki doc.
> >> > >>
> >> > >> -Alex
> >> > >>
> >> > >> On 6/10/19, 8:06 PM, "Greg Dove" <gr...@gmail.com> wrote:
> >> > >>
> >> > >> Hi Alex, I guess you might be back on Royale about now. Just a
> >> heads
> >> > >> up: I
> >> > >> am about 20-30 mins max from merging in what I have. Hope
> that's
> >> > still
> >> > >> ok... please let me know if not.
> >> > >> Thanks,
> >> > >> -Greg
> >> > >>
> >> > >>
> >> > >> On Tue, Jun 11, 2019 at 7:51 AM Greg Dove <greg.dove@gmail.com
> >
> >> > >> wrote:
> >> > >>
> >> > >> >
> >> > >> > Thanks Alex - I'll try to hit the window, much appreciated!
> >> > >> >
> >> > >> >
> >> > >> > On Tue, Jun 11, 2019 at 6:57 AM Alex Harui
> >> > <aharui@adobe.com.invalid
> >> > >> >
> >> > >> > wrote:
> >> > >> >
> >> > >> >> Hi Greg,
> >> > >> >>
> >> > >> >> It turns out I have a "split shift" today. I'm stopping
> work
> >> for
> >> > >> the
> >> > >> >> next 7 or 8 hours then will get around to the merge. So if
> >> you
> >> > >> can get
> >> > >> >> your changes merged in that amount of time, then I will wait
> >> for
> >> > >> you and
> >> > >> >> deal with any merge conflicts (there are almost certain to
> be
> >> > >> some).
> >> > >> >>
> >> > >> >> -Alex
> >> > >> >>
> >> > >> >> On 6/10/19, 11:46 AM, "Greg Dove" <gr...@gmail.com>
> >> wrote:
> >> > >> >>
> >> > >> >> Alex, slightly OT, but in terms of coordination: fyi I
> am
> >> > also
> >> > >> very
> >> > >> >> close
> >> > >> >> to merging the language improvements branch into
> develop.
> >> As
> >> > I
> >> > >> already
> >> > >> >> mentioned elsewhere, I was hoping to do that a couple of
> >> days
> >> > >> back,
> >> > >> >> but
> >> > >> >> some recent things also took me a little longer than
> >> expected
> >> > >> (I have
> >> > >> >> additional local changes/fixes not yet in remote branch)
> >> . I
> >> > >> was
> >> > >> >> planning
> >> > >> >> to merge that today also.
> >> > >> >>
> >> > >> >> However, I will wait until after your merge, so I'm
> hoping
> >> > you
> >> > >> can get
> >> > >> >> yours in today (if not, I will wait). I will probably
> put
> >> > mine
> >> > >> in as a
> >> > >> >> squashed commit after yours.
> >> > >> >>
> >> > >> >>
> >> > >> >> On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <
> >> > >> >> piotrzarzycki21@gmail.com>
> >> > >> >> wrote:
> >> > >> >>
> >> > >> >> > Hi Alex,
> >> > >> >> >
> >> > >> >> > Many thanks for that! I will try to be RM. I will have
> >> some
> >> > >> >> dedicated time
> >> > >> >> > for that. I will wait for your instruction and merge
> to
> >> > >> develop.
> >> > >> >> >
> >> > >> >> > Thanks,
> >> > >> >> > Piotr
> >> > >> >> >
> >> > >> >> >
> >> > >> >> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
> >> > >> <ah...@adobe.com.invalid>
> >> > >> >> wrote:
> >> > >> >> >
> >> > >> >> > > Well, that turned out to be much more time-consuming
> >> > than I
> >> > >> >> expected, but
> >> > >> >> > > we can now create identical release artifacts on Mac
> >> and
> >> > >> Win. I
> >> > >> >> am
> >> > >> >> > hopeful
> >> > >> >> > > this effort will pay off not only now in having
> other
> >> > folks
> >> > >> >> generate
> >> > >> >> > > releases, but also in the future if signed binaries
> >> > become
> >> > >> a
> >> > >> >> requirement.
> >> > >> >> > >
> >> > >> >> > > There continues to be a lot of distractions in my
> life
> >> > >> that can
> >> > >> >> cause
> >> > >> >> > > delays, but I hope to merge the release_practice
> >> branches
> >> > >> into
> >> > >> >> develop
> >> > >> >> > over
> >> > >> >> > > the next day or two and figure out where in the wiki
> >> to
> >> > >> document
> >> > >> >> the
> >> > >> >> > > release process. So, now is the time for one or
> more
> >> > >> people to
> >> > >> >> step up
> >> > >> >> > to
> >> > >> >> > > be the RMs for 0.9.6 and help debug and improve the
> >> > >> process.
> >> > >> >> > >
> >> > >> >> > > I am going to try very hard not to "own" the
> >> process. If
> >> > >> >> something goes
> >> > >> >> > > wrong, I am going to ask others to try to debug and
> >> fix
> >> > it
> >> > >> first
> >> > >> >> because
> >> > >> >> > it
> >> > >> >> > > is in the project's best interests for others to
> truly
> >> > >> understand
> >> > >> >> how
> >> > >> >> > this
> >> > >> >> > > stuff works.
> >> > >> >> > >
> >> > >> >> > > Thanks,
> >> > >> >> > > -Alex
> >> > >> >> > >
> >> > >> >> > > On 5/23/19, 9:54 AM, "Alex Harui"
> >> > <aharui@adobe.com.INVALID
> >> > >> >
> >> > >> >> wrote:
> >> > >> >> > >
> >> > >> >> > > It has turned out to be harder than expected to
> >> get
> >> > >> the same
> >> > >> >> binaries
> >> > >> >> > > on Mac and Win. I now have the identical binaries
> for
> >> > >> >> royale-compiler
> >> > >> >> > and
> >> > >> >> > > royale-typedefs Maven artifacts and am starting on
> >> > >> royale-asjs.
> >> > >> >> I might
> >> > >> >> > > get lucky and the changes that fixed royale-typedefs
> >> SWCs
> >> > >> will
> >> > >> >> magically
> >> > >> >> > > get the royale-asjs SWCs to match. Then we have to
> >> make
> >> > >> the Ant
> >> > >> >> > artifacts
> >> > >> >> > > match.
> >> > >> >> > >
> >> > >> >> > > There have been a lot of distractions in my
> >> non-work
> >> > >> life
> >> > >> >> which has
> >> > >> >> > > also impeded progress. I hope to make much progress
> >> this
> >> > >> coming
> >> > >> >> week and
> >> > >> >> > > if we're lucky, I will be asking for a volunteer (or
> >> > >> volunteers)
> >> > >> >> to test
> >> > >> >> > > drive all of this stuff and be the RM for 0.9.6. I
> am
> >> > not
> >> > >> going
> >> > >> >> to be
> >> > >> >> > the
> >> > >> >> > > RM.
> >> > >> >> > >
> >> > >> >> > > -Alex
> >> > >> >> > >
> >> > >> >> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> >> > >> >> piotrzarzycki21@gmail.com>
> >> > >> >> > > wrote:
> >> > >> >> > >
> >> > >> >> > > Hi Alex,
> >> > >> >> > >
> >> > >> >> > > It's been a while since you have started
> >> effort
> >> > >> with
> >> > >> >> automating
> >> > >> >> > > build.
> >> > >> >> > > Where are you with that ? Are we closer to
> >> > started
> >> > >> 0.9.6.
> >> > >> >> Do you
> >> > >> >> > > need any
> >> > >> >> > > help with this ?
> >> > >> >> > >
> >> > >> >> > > Thanks,
> >> > >> >> > > Piotr
> >> > >> >> > >
> >> > >> >> > > wt., 2 kwi 2019 o 19:30 Alex Harui
> >> > >> >> <ah...@adobe.com.invalid>
> >> > >> >> > > napisał(a):
> >> > >> >> > >
> >> > >> >> > > > Update:
> >> > >> >> > > >
> >> > >> >> > > > In order to make verification of binary
> >> release
> >> > >> packages
> >> > >> >> > created
> >> > >> >> > > on the
> >> > >> >> > > > server easier, I have made changes to our
> >> build
> >> > >> scripts
> >> > >> >> and
> >> > >> >> > > tools to try to
> >> > >> >> > > > generate reproducible binaries. I've seen
> >> two
> >> > >> >> different builds
> >> > >> >> > > compare on
> >> > >> >> > > > my Mac. The next challenge will be to
> see
> >> if
> >> > >> the
> >> > >> >> server can
> >> > >> >> > > build a
> >> > >> >> > > > package on Windows that will compare on
> Mac.
> >> > >> >> > > >
> >> > >> >> > > > One of the changes I needed to make is to
> >> > >> JBurg. The
> >> > >> >> version
> >> > >> >> > of
> >> > >> >> > > JBurg we
> >> > >> >> > > > use generates method names including a
> hash
> >> > that
> >> > >> doesn't
> >> > >> >> > > reproduce the same
> >> > >> >> > > > name each time. I have changes to JBurg
> >> ready,
> >> > >> however
> >> > >> >> JBurg
> >> > >> >> > is
> >> > >> >> > > currently
> >> > >> >> > > > under CPL which is category B. We only
> need
> >> > one
> >> > >> file,
> >> > >> >> we don't
> >> > >> >> > > need or
> >> > >> >> > > > want all of JBurg at this time. The one
> >> JBurg
> >> > >> file is
> >> > >> >> jointly
> >> > >> >> > > owned by
> >> > >> >> > > > Adobe and Tom Harwood. I've contact Tom
> >> and he
> >> > >> will be
> >> > >> >> filing
> >> > >> >> > > an ICLA and
> >> > >> >> > > > has given me permission to commit the
> lines
> >> he
> >> > >> owns in
> >> > >> >> that one
> >> > >> >> > > file.
> >> > >> >> > > >
> >> > >> >> > > > This is the revision of the file that will
> >> be
> >> > >> donated by
> >> > >> >> > > Tom/Adobe.
> >> > >> >> > > >
> >> > >> >> > > >
> >> > >> >> > >
> >> > >> >> >
> >> > >> >>
> >> > >>
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=VS1za1vOQhtlKlK4Tdgq3ej04OlhFoYfHziyNbgOIN4%3D&reserved=0
> >> > >> >> > > >
> >> > >> >> > > > Once this file goes in with the changes to
> >> keep
> >> > >> the
> >> > >> >> method
> >> > >> >> > names
> >> > >> >> > > the same,
> >> > >> >> > > > there will be more tweaks to the release
> >> tasks
> >> > >> and then
> >> > >> >> we can
> >> > >> >> > > try cutting
> >> > >> >> > > > a release. I'm thinking we'll be at that
> >> point
> >> > >> in
> >> > >> >> early May,
> >> > >> >> > so
> >> > >> >> > > now is the
> >> > >> >> > > > time to get stuff in for the 0.9.6
> release.
> >> > >> >> > > >
> >> > >> >> > > > Thanks,
> >> > >> >> > > > -Alex
> >> > >> >> > > >
> >> > >> >> > > > On 3/8/19, 9:27 AM, "Alex Harui" <
> >> > >> aharui@adobe.com>
> >> > >> >> wrote:
> >> > >> >> > > >
> >> > >> >> > > > I would much rather have others find
> and
> >> > fix
> >> > >> issues
> >> > >> >> > > themselves. That
> >> > >> >> > > > way, more people than just me will know
> how
> >> to
> >> > >> maintain
> >> > >> >> the
> >> > >> >> > > system. It
> >> > >> >> > > > actually turns out that, IMO, a group of
> >> people
> >> > >> can
> >> > >> >> work on the
> >> > >> >> > > release.
> >> > >> >> > > > There are 14 steps. Literally, 14
> different
> >> > >> people
> >> > >> >> could
> >> > >> >> > > execute one step
> >> > >> >> > > > each.
> >> > >> >> > > >
> >> > >> >> > > > My 2 cents,
> >> > >> >> > > > -Alex
> >> > >> >> > > >
> >> > >> >> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> >> > >> >> > carlosrovira@apache.org>
> >> > >> >> > > wrote:
> >> > >> >> > > >
> >> > >> >> > > > Hi Alex,
> >> > >> >> > > >
> >> > >> >> > > > amazing work! congrats to reach to
> >> this
> >> > >> point!
> >> > >> >> :)
> >> > >> >> > > >
> >> > >> >> > > > I need to put my head on all of
> >> this,
> >> > >> but count
> >> > >> >> on me
> >> > >> >> > to
> >> > >> >> > > be a RM.
> >> > >> >> > > > I think
> >> > >> >> > > > the best thing should be that you
> be
> >> > the
> >> > >> first
> >> > >> >> RM to
> >> > >> >> > try
> >> > >> >> > > your own
> >> > >> >> > > > development at least for the first
> >> > time,
> >> > >> and
> >> > >> >> then the
> >> > >> >> > > rest of us
> >> > >> >> > > > will
> >> > >> >> > > > follow you on the next releases.
> >> With
> >> > >> all this
> >> > >> >> on place
> >> > >> >> > > we maybe
> >> > >> >> > > > could
> >> > >> >> > > > release once a month or every two
> >> > >> months...
> >> > >> >> > > >
> >> > >> >> > > > Thanks for doing this :)
> >> > >> >> > > >
> >> > >> >> > > > Carlos
> >> > >> >> > > >
> >> > >> >> > > >
> >> > >> >> > > > El vie., 8 mar. 2019 a las 1:55,
> >> Alex
> >> > >> Harui
> >> > >> >> > > > (<ah...@adobe.com.invalid>)
> >> > >> >> > > > escribió:
> >> > >> >> > > >
> >> > >> >> > > > > OK, I've now seen Jenkins
> perform
> >> the
> >> > >> steps
> >> > >> >> to build
> >> > >> >> > > the release
> >> > >> >> > > > > artifacts. Folks interested in
> >> > >> Docker-izing
> >> > >> >> the
> >> > >> >> > steps
> >> > >> >> > > are
> >> > >> >> > > > welcome to look
> >> > >> >> > > > > at the jobs on the "Royale
> >> Release"
> >> > >> tab on
> >> > >> >> the CI
> >> > >> >> > > server.
> >> > >> >> > > > >
> >> > >> >> > > >
> >> > >> >> > >
> >> > >> >> >
> >> > >> >>
> >> > >>
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=LfWCyCaClCVgfeINn4%2B%2Bk%2FSVUFXvgyV7QxMtx4B%2B%2Fu0%3D&reserved=0
> >> > >> >> > > > >
> >> > >> >> > > > > These steps assume that the RM
> can
> >> > run
> >> > >> the
> >> > >> >> basic
> >> > >> >> > Maven
> >> > >> >> > > and Ant
> >> > >> >> > > > build on
> >> > >> >> > > > > the RM's computer. I think
> that's
> >> a
> >> > >> fair
> >> > >> >> requirement
> >> > >> >> > > since all
> >> > >> >> > > > of us on the
> >> > >> >> > > > > PMC need to able to do that to
> >> build
> >> > >> the RC
> >> > >> >> in order
> >> > >> >> > > to vote on
> >> > >> >> > > > it.
> >> > >> >> > > > > Jenkins does other tasks like
> run
> >> > the
> >> > >> Maven
> >> > >> >> release
> >> > >> >> > > plugin
> >> > >> >> > > > steps.
> >> > >> >> > > > >
> >> > >> >> > > > > Currently that results in
> >> binaries on
> >> > >> Jenkins
> >> > >> >> that
> >> > >> >> > are
> >> > >> >> > > > downloaded to the
> >> > >> >> > > > > RM's computer. These binaries
> >> need
> >> > to
> >> > >> be
> >> > >> >> verified by
> >> > >> >> > > the RM
> >> > >> >> > > > which is the
> >> > >> >> > > > > next phase I will be starting on
> >> now.
> >> > >> The RM
> >> > >> >> > verifies
> >> > >> >> > > the bits
> >> > >> >> > > > and then
> >> > >> >> > > > > PGP signs them. And then the
> bits
> >> > are
> >> > >> >> uploaded off
> >> > >> >> > > the RM's
> >> > >> >> > > > computer to
> >> > >> >> > > > > Maven Staging or dist.a.o/dev.
> >> If
> >> > >> that
> >> > >> >> uploading
> >> > >> >> > > turns out to
> >> > >> >> > > > be a point
> >> > >> >> > > > > of failure, we have the option
> of
> >> > >> having
> >> > >> >> Jenkins
> >> > >> >> > > upload the big
> >> > >> >> > > > files and
> >> > >> >> > > > > have the RM only upload PGP
> >> signature
> >> > >> files.
> >> > >> >> Or
> >> > >> >> > > finding a way
> >> > >> >> > > > for Jenkins
> >> > >> >> > > > > to get the signature files from
> >> the
> >> > >> RM. The
> >> > >> >> uploads
> >> > >> >> > > worked fine
> >> > >> >> > > > for me,
> >> > >> >> > > > > but then again, so did the old
> >> > script's
> >> > >> >> uploads.
> >> > >> >> > > > >
> >> > >> >> > > > > Therefore, once I get the binary
> >> > >> verification
> >> > >> >> phase
> >> > >> >> > > completed, I
> >> > >> >> > > > think
> >> > >> >> > > > > someone other than me should be
> >> the
> >> > RM
> >> > >> and
> >> > >> >> try to use
> >> > >> >> > > these
> >> > >> >> > > > steps to
> >> > >> >> > > > > generate the release and help
> >> debug
> >> > the
> >> > >> >> process for
> >> > >> >> > > the next
> >> > >> >> > > > RM. So,
> >> > >> >> > > > > please try to carve out some
> time
> >> to
> >> > >> be the
> >> > >> >> RM. One
> >> > >> >> > > advantage
> >> > >> >> > > > of doing
> >> > >> >> > > > > most of the work on Jenkins is
> >> that
> >> > it
> >> > >> frees
> >> > >> >> up my
> >> > >> >> > > computer to
> >> > >> >> > > > do other
> >> > >> >> > > > > things while Jenkins is cranking
> >> > away.
> >> > >> >> > > > >
> >> > >> >> > > > > I think we're at least a week
> away
> >> > >> from binary
> >> > >> >> > > verification,
> >> > >> >> > > > maybe two, so
> >> > >> >> > > > > it is time to start thinking
> about
> >> > >> what is
> >> > >> >> going in
> >> > >> >> > > this release.
> >> > >> >> > > > >
> >> > >> >> > > > > Thanks,
> >> > >> >> > > > > -Alex
> >> > >> >> > > > >
> >> > >> >> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
> >> > >> >> > > <ah...@adobe.com.INVALID>
> >> > >> >> > > > wrote:
> >> > >> >> > > > >
> >> > >> >> > > > > In case you haven't guessed,
> >> I'm
> >> > >> testing
> >> > >> >> out
> >> > >> >> > > Jenkins and its
> >> > >> >> > > > ability
> >> > >> >> > > > > to create the artifacts and send
> >> > >> emails.
> >> > >> >> Please
> >> > >> >> > > ignore any
> >> > >> >> > > > email that
> >> > >> >> > > > > looks like a vote or discuss
> >> thread.
> >> > >> >> > > > >
> >> > >> >> > > > > Thanks,
> >> > >> >> > > > > -Alex
> >> > >> >> > > > >
> >> > >> >> > > > > On 2/10/19, 8:44 PM, "Alex
> >> Harui"
> >> > >> >> > > <ah...@adobe.com.INVALID>
> >> > >> >> > > > wrote:
> >> > >> >> > > > >
> >> > >> >> > > > > Om,
> >> > >> >> > > > >
> >> > >> >> > > > > Well, that's what I used
> >> for
> >> > >> the last
> >> > >> >> > > release. I'm sure
> >> > >> >> > > > there is
> >> > >> >> > > > > probably some inaccuracy in it.
> >> > >> >> > > > >
> >> > >> >> > > > > That said, I'm
> abandoning
> >> > that
> >> > >> >> document and
> >> > >> >> > > taking a new
> >> > >> >> > > > angle
> >> > >> >> > > > > because that document presumed
> >> that
> >> > the
> >> > >> >> release
> >> > >> >> > > manager was
> >> > >> >> > > > trying to
> >> > >> >> > > > > create a release on his/her
> >> computer.
> >> > >> I've
> >> > >> >> given up
> >> > >> >> > > on that and
> >> > >> >> > > > working on
> >> > >> >> > > > > making releases from a shared
> >> > computer
> >> > >> for the
> >> > >> >> > reasons
> >> > >> >> > > I've
> >> > >> >> > > > stated
> >> > >> >> > > > > upthread. I hope to make some
> >> > >> progress on
> >> > >> >> that this
> >> > >> >> > > week.
> >> > >> >> > > > >
> >> > >> >> > > > > The key difference is
> that
> >> > the
> >> > >> new
> >> > >> >> angle does
> >> > >> >> > > not
> >> > >> >> > > > presume that you
> >> > >> >> > > > > have Git SSH and PGP signatures
> >> all
> >> > >> set up on
> >> > >> >> some
> >> > >> >> > > computer. I
> >> > >> >> > > > have not
> >> > >> >> > > > > looked into how Docker would
> >> handle
> >> > >> that. You
> >> > >> >> > > certainly
> >> > >> >> > > > wouldn't want the
> >> > >> >> > > > > Docker image to contain your SSH
> >> or
> >> > PGP
> >> > >> >> keys/creds.
> >> > >> >> > > And if the
> >> > >> >> > > > Docker
> >> > >> >> > > > > image doesn't, then that is
> >> another
> >> > >> stumbling
> >> > >> >> block
> >> > >> >> > > for future
> >> > >> >> > > > RMs.
> >> > >> >> > > > >
> >> > >> >> > > > > The other key difference
> >> is
> >> > >> that the
> >> > >> >> old
> >> > >> >> > > script presumed
> >> > >> >> > > > you could
> >> > >> >> > > > > create the 3 release in 3 huge
> >> "easy"
> >> > >> steps.
> >> > >> >> We've
> >> > >> >> > > seen that is
> >> > >> >> > > > only true
> >> > >> >> > > > > for me. So the new angle
> creates
> >> > many
> >> > >> >> discrete steps
> >> > >> >> > > managed by
> >> > >> >> > > > Jenkins.
> >> > >> >> > > > >
> >> > >> >> > > > > So, it is up to you to
> >> decide
> >> > >> what
> >> > >> >> you want
> >> > >> >> > to
> >> > >> >> > > > "Docker-ize". You
> >> > >> >> > > > > can try to Docker-ize the
> current
> >> 3
> >> > big
> >> > >> >> steps, so RMs
> >> > >> >> > > can try to
> >> > >> >> > > > run it on
> >> > >> >> > > > > their systems, but I'd bet they
> >> will
> >> > >> just
> >> > >> >> faiI due to
> >> > >> >> > > network
> >> > >> >> > > > issues. I
> >> > >> >> > > > > would be interested in using
> >> Docker
> >> > to
> >> > >> make
> >> > >> >> each of
> >> > >> >> > > these many
> >> > >> >> > > > discrete
> >> > >> >> > > > > steps portable to another
> server.
> >> > >> I'm not
> >> > >> >> going to
> >> > >> >> > > involve
> >> > >> >> > > > Docker at this
> >> > >> >> > > > > point. My main goal is just to
> >> see
> >> > if
> >> > >> I can
> >> > >> >> create a
> >> > >> >> > > workflow
> >> > >> >> > > > of many
> >> > >> >> > > > > discrete steps that isn't
> horribly
> >> > >> painful.
> >> > >> >> Once we
> >> > >> >> > > see what
> >> > >> >> > > > these steps
> >> > >> >> > > > > turn out to be, then we can
> worry
> >> > >> about server
> >> > >> >> > > portability of
> >> > >> >> > > > those steps.
> >> > >> >> > > > >
> >> > >> >> > > > > Either way, we want to
> >> know
> >> > >> about
> >> > >> >> running
> >> > >> >> > > > Browser+Selenium for
> >> > >> >> > > > > sure. And maybe
> >> FlashPlayerDebugger
> >> > >> or AIR.
> >> > >> >> I would
> >> > >> >> > > want to
> >> > >> >> > > > know, for
> >> > >> >> > > > > example, how you debug a failing
> >> > >> checkintest
> >> > >> >> in a
> >> > >> >> > > Docker
> >> > >> >> > > > container.
> >> > >> >> > > > >
> >> > >> >> > > > > Thanks,
> >> > >> >> > > > > -Alex
> >> > >> >> > > > >
> >> > >> >> > > > >
> >> > >> >> > > > > On 2/10/19, 5:18 PM,
> >> > "OmPrakash
> >> > >> >> Muppirala" <
> >> > >> >> > > > bigosmallm@gmail.com>
> >> > >> >> > > > > wrote:
> >> > >> >> > > > >
> >> > >> >> > > > > Alex,
> >> > >> >> > > > >
> >> > >> >> > > > > Just to be clear, I
> am
> >> > >> following
> >> > >> >> the
> >> > >> >> > steps
> >> > >> >> > > from here
> >> > >> >> > > > to try
> >> > >> >> > > > > and setup a
> >> > >> >> > > > > docker container.
> >> > >> >> > > > >
> >> > >> >> > > > >
> >> > >> >> > > > >
> >> > >> >> > > >
> >> > >> >> > >
> >> > >> >> >
> >> > >>
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=Lhm0hudN8Nbx%2F6Lnmz0Wlus3EpV1o1h8XWBzBUoEWOA%3D&reserved=0
> >> > >> >> > > > >
> >> > >> >> > > > > Is this doc up to
> >> date?
> >> > >> >> > > > >
> >> > >> >> > > > > Thanks,
> >> > >> >> > > > > Om
> >> > >> >> > > > >
> >> > >> >> > > > > On Wed, Feb 6, 2019
> at
> >> > >> 12:02 PM
> >> > >> >> OmPrakash
> >> > >> >> > > Muppirala <
> >> > >> >> > > > > bigosmallm@gmail.com>
> >> > >> >> > > > > wrote:
> >> > >> >> > > > >
> >> > >> >> > > > > > One approach is to
> >> have
> >> > >> each
> >> > >> >> step in
> >> > >> >> > the
> >> > >> >> > > process
> >> > >> >> > > > spin up a
> >> > >> >> > > > > docker image.
> >> > >> >> > > > > > And use
> >> docker-compose
> >> > >> to run
> >> > >> >> each
> >> > >> >> > > step. All the
> >> > >> >> > > > images can
> >> > >> >> > > > > be made to
> >> > >> >> > > > > > share a common
> >> volume
> >> > >> where all
> >> > >> >> the
> >> > >> >> > > artifacts are
> >> > >> >> > > > stored
> >> > >> >> > > > > across steps.
> >> > >> >> > > > > >
> >> > >> >> > > > > > You are right
> about
> >> the
> >> > >> >> networking
> >> > >> >> > issue
> >> > >> >> > > though.
> >> > >> >> > > > Any
> >> > >> >> > > > > network related
> >> > >> >> > > > > > failure that
> occurs
> >> on
> >> > >> the host
> >> > >> >> machine
> >> > >> >> > > will most
> >> > >> >> > > > likely
> >> > >> >> > > > > occur in the
> >> > >> >> > > > > > docker container.
> >> > >> Although, I
> >> > >> >> am not
> >> > >> >> > > clear how we
> >> > >> >> > > > can
> >> > >> >> > > > > guarantee that the
> >> > >> >> > > > > > same issues will
> not
> >> > >> occur on
> >> > >> >> the
> >> > >> >> > > Jenkins server.
> >> > >> >> > > > I mean,
> >> > >> >> > > > > what is special
> >> > >> >> > > > > > about the Jenkins
> >> > server
> >> > >> that
> >> > >> >> makes it
> >> > >> >> > > immune to
> >> > >> >> > > > these
> >> > >> >> > > > > networking issues?
> >> > >> >> > > > > >
> >> > >> >> > > > > > Thanks,
> >> > >> >> > > > > > Om
> >> > >> >> > > > > >
> >> > >> >> > > > > > On Wed, Feb 6,
> 2019
> >> at
> >> > >> 11:48 AM
> >> > >> >> Alex
> >> > >> >> > > Harui
> >> > >> >> > > > > <ah...@adobe.com.invalid>
> >> > >> >> > > > > > wrote:
> >> > >> >> > > > > >
> >> > >> >> > > > > >> Again, I don't
> know
> >> > >> anything
> >> > >> >> about
> >> > >> >> > > Docker, but
> >> > >> >> > > > before we
> >> > >> >> > > > > spend a lot of
> >> > >> >> > > > > >> time on Docker, I
> >> also
> >> > >> want to
> >> > >> >> point
> >> > >> >> > > out that the
> >> > >> >> > > > process
> >> > >> >> > > > > to create a
> >> > >> >> > > > > >> release cannot
> >> really
> >> > be
> >> > >> >> thought of as
> >> > >> >> > > "one
> >> > >> >> > > > application".
> >> > >> >> > > > > It will be a
> >> > >> >> > > > > >> series of "steps"
> >> to
> >> > >> run.
> >> > >> >> How many
> >> > >> >> > > steps
> >> > >> >> > > > depends on
> >> > >> >> > > > > whether we think we
> >> > >> >> > > > > >> can isolate
> enough
> >> > >> stuff via
> >> > >> >> Docker to
> >> > >> >> > > be able to
> >> > >> >> > > > run
> >> > >> >> > > > > Docker on the RM's
> >> > >> >> > > > > >> computer instead
> of
> >> > >> some shared
> >> > >> >> > > computer. On a
> >> > >> >> > > > shared
> >> > >> >> > > > > computer there will
> >> > >> >> > > > > >> be dozens of
> steps
> >> > >> because the
> >> > >> >> RM will
> >> > >> >> > > need to
> >> > >> >> > > > enter
> >> > >> >> > > > > passwords to commit
> >> > >> >> > > > > >> stuff. On a
> local
> >> > >> computer I
> >> > >> >> guess
> >> > >> >> > the
> >> > >> >> > > RM can
> >> > >> >> > > > supply
> >> > >> >> > > > > passwords but I think
> >> > >> >> > > > > >> there will be
> >> stopping
> >> > >> points
> >> > >> >> where
> >> > >> >> > the
> >> > >> >> > > Maven
> >> > >> >> > > > artifacts are
> >> > >> >> > > > > deployed and
> >> > >> >> > > > > >> the staging repo
> is
> >> > >> closed, and
> >> > >> >> > another
> >> > >> >> > > stopping
> >> > >> >> > > > point for
> >> > >> >> > > > > the vote. It
> >> > >> >> > > > > >> seems like Docker
> >> > works
> >> > >> by
> >> > >> >> downloading
> >> > >> >> > > > dependencies. Given
> >> > >> >> > > > > that the
> >> > >> >> > > > > >> problem the RMs
> had
> >> > >> last time
> >> > >> >> involved
> >> > >> >> > > downloads
> >> > >> >> > > > and
> >> > >> >> > > > > uploads, why do we
> >> > >> >> > > > > >> think Docker will
> >> > >> really solve
> >> > >> >> this
> >> > >> >> > for
> >> > >> >> > > creating
> >> > >> >> > > > releases
> >> > >> >> > > > > on local machines?
> >> > >> >> > > > > >>
> >> > >> >> > > > > >> The reason to do
> >> this
> >> > >> on a
> >> > >> >> shared
> >> > >> >> > > machine is so
> >> > >> >> > > > that new
> >> > >> >> > > > > RMs don't have
> >> > >> >> > > > > >> to do as much
> >> setup.
> >> > >> But then
> >> > >> >> I
> >> > >> >> > wonder
> >> > >> >> > > about the
> >> > >> >> > > > > efficiency of kicking off
> >> > >> >> > > > > >> that many Docker
> >> > images.
> >> > >> >> Jenkins can
> >> > >> >> > > manage that
> >> > >> >> > > > already.
> >> > >> >> > > > > Does Docker
> >> > >> >> > > > > >> have some sort of
> >> > >> similar
> >> > >> >> Dashboard or
> >> > >> >> > > would we
> >> > >> >> > > > use Jenkins
> >> > >> >> > > > > to kick off
> >> > >> >> > > > > >> Docker steps? I
> >> can't
> >> > >> quite
> >> > >> >> picture
> >> > >> >> > > what is the
> >> > >> >> > > > outermost
> >> > >> >> > > > > >>
> control/dashboard.
> >> > >> >> > > > > >>
> >> > >> >> > > > > >> -Alex
> >> > >> >> > > > > >>
> >> > >> >> > > > > >> On 2/6/19, 11:03
> >> AM,
> >> > >> "Harbs" <
> >> > >> >> > > > harbs.lists@gmail.com> wrote:
> >> > >> >> > > > > >>
> >> > >> >> > > > > >> A quick
> search
> >> > >> turns up
> >> > >> >> this:
> >> > >> >> > > > > >>
> >> > >> >> > > > > >>
> >> > >> >> > > > > >>
> >> > >> >> > > > >
> >> > >> >> > > >
> >> > >> >> > >
> >> > >> >> >
> >> > >>
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
> >> > >> >> > > > > >> <
> >> > >> >> > > > > >>
> >> > >> >> > > > >
> >> > >> >> > > >
> >> > >> >> > >
> >> > >> >> >
> >> > >>
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0>
Re: 0.9.6 Release
Posted by Greg Dove <gr...@gmail.com>.
Piotr, I hope I addressed the issue, but waiting to see...
It looks like it has been unstable for last 7 days , am I reading that
right? https://builds.apache.org/job/Royale-asjs/
On Tue, Jun 11, 2019 at 4:30 PM Greg Dove <gr...@gmail.com> wrote:
> Working on it!
>
>
> On Tue, Jun 11, 2019 at 4:29 PM Piotr Zarzycki <pi...@gmail.com>
> wrote:
>
>> Hi Greg,
>>
>> After your merge the goal should be that build on Jenkins is working fine.
>> Please make sure that is happen.
>>
>> Thanks,
>> Piotr
>>
>> On Tue, Jun 11, 2019, 5:32 AM Greg Dove <gr...@gmail.com> wrote:
>>
>> > I will stick with the plan of single commit, I think it should be easier
>> > for you if there are any conflicts.
>> > Last build testing is running now in local develop. I will push after
>> > that...
>> >
>> > On Tue, Jun 11, 2019 at 3:15 PM Greg Dove <gr...@gmail.com> wrote:
>> >
>> > >
>> > > Thanks Alex, I was planning to merge this as a single squashed commit,
>> > > because it isolates all the changes to a single commit (but this will
>> > mean
>> > > there are many changes in one hit).
>> > > Do you have a preference in terms of how easy it will make things for
>> > you?
>> > >
>> > >
>> > > On Tue, Jun 11, 2019 at 3:07 PM Alex Harui <ah...@adobe.com.invalid>
>> > > wrote:
>> > >
>> > >> OK, I will wait to see your commit emails. I will do some other
>> things
>> > >> like the wiki doc.
>> > >>
>> > >> -Alex
>> > >>
>> > >> On 6/10/19, 8:06 PM, "Greg Dove" <gr...@gmail.com> wrote:
>> > >>
>> > >> Hi Alex, I guess you might be back on Royale about now. Just a
>> heads
>> > >> up: I
>> > >> am about 20-30 mins max from merging in what I have. Hope that's
>> > still
>> > >> ok... please let me know if not.
>> > >> Thanks,
>> > >> -Greg
>> > >>
>> > >>
>> > >> On Tue, Jun 11, 2019 at 7:51 AM Greg Dove <gr...@gmail.com>
>> > >> wrote:
>> > >>
>> > >> >
>> > >> > Thanks Alex - I'll try to hit the window, much appreciated!
>> > >> >
>> > >> >
>> > >> > On Tue, Jun 11, 2019 at 6:57 AM Alex Harui
>> > <aharui@adobe.com.invalid
>> > >> >
>> > >> > wrote:
>> > >> >
>> > >> >> Hi Greg,
>> > >> >>
>> > >> >> It turns out I have a "split shift" today. I'm stopping work
>> for
>> > >> the
>> > >> >> next 7 or 8 hours then will get around to the merge. So if
>> you
>> > >> can get
>> > >> >> your changes merged in that amount of time, then I will wait
>> for
>> > >> you and
>> > >> >> deal with any merge conflicts (there are almost certain to be
>> > >> some).
>> > >> >>
>> > >> >> -Alex
>> > >> >>
>> > >> >> On 6/10/19, 11:46 AM, "Greg Dove" <gr...@gmail.com>
>> wrote:
>> > >> >>
>> > >> >> Alex, slightly OT, but in terms of coordination: fyi I am
>> > also
>> > >> very
>> > >> >> close
>> > >> >> to merging the language improvements branch into develop.
>> As
>> > I
>> > >> already
>> > >> >> mentioned elsewhere, I was hoping to do that a couple of
>> days
>> > >> back,
>> > >> >> but
>> > >> >> some recent things also took me a little longer than
>> expected
>> > >> (I have
>> > >> >> additional local changes/fixes not yet in remote branch)
>> . I
>> > >> was
>> > >> >> planning
>> > >> >> to merge that today also.
>> > >> >>
>> > >> >> However, I will wait until after your merge, so I'm hoping
>> > you
>> > >> can get
>> > >> >> yours in today (if not, I will wait). I will probably put
>> > mine
>> > >> in as a
>> > >> >> squashed commit after yours.
>> > >> >>
>> > >> >>
>> > >> >> On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <
>> > >> >> piotrzarzycki21@gmail.com>
>> > >> >> wrote:
>> > >> >>
>> > >> >> > Hi Alex,
>> > >> >> >
>> > >> >> > Many thanks for that! I will try to be RM. I will have
>> some
>> > >> >> dedicated time
>> > >> >> > for that. I will wait for your instruction and merge to
>> > >> develop.
>> > >> >> >
>> > >> >> > Thanks,
>> > >> >> > Piotr
>> > >> >> >
>> > >> >> >
>> > >> >> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
>> > >> <ah...@adobe.com.invalid>
>> > >> >> wrote:
>> > >> >> >
>> > >> >> > > Well, that turned out to be much more time-consuming
>> > than I
>> > >> >> expected, but
>> > >> >> > > we can now create identical release artifacts on Mac
>> and
>> > >> Win. I
>> > >> >> am
>> > >> >> > hopeful
>> > >> >> > > this effort will pay off not only now in having other
>> > folks
>> > >> >> generate
>> > >> >> > > releases, but also in the future if signed binaries
>> > become
>> > >> a
>> > >> >> requirement.
>> > >> >> > >
>> > >> >> > > There continues to be a lot of distractions in my life
>> > >> that can
>> > >> >> cause
>> > >> >> > > delays, but I hope to merge the release_practice
>> branches
>> > >> into
>> > >> >> develop
>> > >> >> > over
>> > >> >> > > the next day or two and figure out where in the wiki
>> to
>> > >> document
>> > >> >> the
>> > >> >> > > release process. So, now is the time for one or more
>> > >> people to
>> > >> >> step up
>> > >> >> > to
>> > >> >> > > be the RMs for 0.9.6 and help debug and improve the
>> > >> process.
>> > >> >> > >
>> > >> >> > > I am going to try very hard not to "own" the
>> process. If
>> > >> >> something goes
>> > >> >> > > wrong, I am going to ask others to try to debug and
>> fix
>> > it
>> > >> first
>> > >> >> because
>> > >> >> > it
>> > >> >> > > is in the project's best interests for others to truly
>> > >> understand
>> > >> >> how
>> > >> >> > this
>> > >> >> > > stuff works.
>> > >> >> > >
>> > >> >> > > Thanks,
>> > >> >> > > -Alex
>> > >> >> > >
>> > >> >> > > On 5/23/19, 9:54 AM, "Alex Harui"
>> > <aharui@adobe.com.INVALID
>> > >> >
>> > >> >> wrote:
>> > >> >> > >
>> > >> >> > > It has turned out to be harder than expected to
>> get
>> > >> the same
>> > >> >> binaries
>> > >> >> > > on Mac and Win. I now have the identical binaries for
>> > >> >> royale-compiler
>> > >> >> > and
>> > >> >> > > royale-typedefs Maven artifacts and am starting on
>> > >> royale-asjs.
>> > >> >> I might
>> > >> >> > > get lucky and the changes that fixed royale-typedefs
>> SWCs
>> > >> will
>> > >> >> magically
>> > >> >> > > get the royale-asjs SWCs to match. Then we have to
>> make
>> > >> the Ant
>> > >> >> > artifacts
>> > >> >> > > match.
>> > >> >> > >
>> > >> >> > > There have been a lot of distractions in my
>> non-work
>> > >> life
>> > >> >> which has
>> > >> >> > > also impeded progress. I hope to make much progress
>> this
>> > >> coming
>> > >> >> week and
>> > >> >> > > if we're lucky, I will be asking for a volunteer (or
>> > >> volunteers)
>> > >> >> to test
>> > >> >> > > drive all of this stuff and be the RM for 0.9.6. I am
>> > not
>> > >> going
>> > >> >> to be
>> > >> >> > the
>> > >> >> > > RM.
>> > >> >> > >
>> > >> >> > > -Alex
>> > >> >> > >
>> > >> >> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
>> > >> >> piotrzarzycki21@gmail.com>
>> > >> >> > > wrote:
>> > >> >> > >
>> > >> >> > > Hi Alex,
>> > >> >> > >
>> > >> >> > > It's been a while since you have started
>> effort
>> > >> with
>> > >> >> automating
>> > >> >> > > build.
>> > >> >> > > Where are you with that ? Are we closer to
>> > started
>> > >> 0.9.6.
>> > >> >> Do you
>> > >> >> > > need any
>> > >> >> > > help with this ?
>> > >> >> > >
>> > >> >> > > Thanks,
>> > >> >> > > Piotr
>> > >> >> > >
>> > >> >> > > wt., 2 kwi 2019 o 19:30 Alex Harui
>> > >> >> <ah...@adobe.com.invalid>
>> > >> >> > > napisał(a):
>> > >> >> > >
>> > >> >> > > > Update:
>> > >> >> > > >
>> > >> >> > > > In order to make verification of binary
>> release
>> > >> packages
>> > >> >> > created
>> > >> >> > > on the
>> > >> >> > > > server easier, I have made changes to our
>> build
>> > >> scripts
>> > >> >> and
>> > >> >> > > tools to try to
>> > >> >> > > > generate reproducible binaries. I've seen
>> two
>> > >> >> different builds
>> > >> >> > > compare on
>> > >> >> > > > my Mac. The next challenge will be to see
>> if
>> > >> the
>> > >> >> server can
>> > >> >> > > build a
>> > >> >> > > > package on Windows that will compare on Mac.
>> > >> >> > > >
>> > >> >> > > > One of the changes I needed to make is to
>> > >> JBurg. The
>> > >> >> version
>> > >> >> > of
>> > >> >> > > JBurg we
>> > >> >> > > > use generates method names including a hash
>> > that
>> > >> doesn't
>> > >> >> > > reproduce the same
>> > >> >> > > > name each time. I have changes to JBurg
>> ready,
>> > >> however
>> > >> >> JBurg
>> > >> >> > is
>> > >> >> > > currently
>> > >> >> > > > under CPL which is category B. We only need
>> > one
>> > >> file,
>> > >> >> we don't
>> > >> >> > > need or
>> > >> >> > > > want all of JBurg at this time. The one
>> JBurg
>> > >> file is
>> > >> >> jointly
>> > >> >> > > owned by
>> > >> >> > > > Adobe and Tom Harwood. I've contact Tom
>> and he
>> > >> will be
>> > >> >> filing
>> > >> >> > > an ICLA and
>> > >> >> > > > has given me permission to commit the lines
>> he
>> > >> owns in
>> > >> >> that one
>> > >> >> > > file.
>> > >> >> > > >
>> > >> >> > > > This is the revision of the file that will
>> be
>> > >> donated by
>> > >> >> > > Tom/Adobe.
>> > >> >> > > >
>> > >> >> > > >
>> > >> >> > >
>> > >> >> >
>> > >> >>
>> > >>
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=VS1za1vOQhtlKlK4Tdgq3ej04OlhFoYfHziyNbgOIN4%3D&reserved=0
>> > >> >> > > >
>> > >> >> > > > Once this file goes in with the changes to
>> keep
>> > >> the
>> > >> >> method
>> > >> >> > names
>> > >> >> > > the same,
>> > >> >> > > > there will be more tweaks to the release
>> tasks
>> > >> and then
>> > >> >> we can
>> > >> >> > > try cutting
>> > >> >> > > > a release. I'm thinking we'll be at that
>> point
>> > >> in
>> > >> >> early May,
>> > >> >> > so
>> > >> >> > > now is the
>> > >> >> > > > time to get stuff in for the 0.9.6 release.
>> > >> >> > > >
>> > >> >> > > > Thanks,
>> > >> >> > > > -Alex
>> > >> >> > > >
>> > >> >> > > > On 3/8/19, 9:27 AM, "Alex Harui" <
>> > >> aharui@adobe.com>
>> > >> >> wrote:
>> > >> >> > > >
>> > >> >> > > > I would much rather have others find and
>> > fix
>> > >> issues
>> > >> >> > > themselves. That
>> > >> >> > > > way, more people than just me will know how
>> to
>> > >> maintain
>> > >> >> the
>> > >> >> > > system. It
>> > >> >> > > > actually turns out that, IMO, a group of
>> people
>> > >> can
>> > >> >> work on the
>> > >> >> > > release.
>> > >> >> > > > There are 14 steps. Literally, 14 different
>> > >> people
>> > >> >> could
>> > >> >> > > execute one step
>> > >> >> > > > each.
>> > >> >> > > >
>> > >> >> > > > My 2 cents,
>> > >> >> > > > -Alex
>> > >> >> > > >
>> > >> >> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
>> > >> >> > carlosrovira@apache.org>
>> > >> >> > > wrote:
>> > >> >> > > >
>> > >> >> > > > Hi Alex,
>> > >> >> > > >
>> > >> >> > > > amazing work! congrats to reach to
>> this
>> > >> point!
>> > >> >> :)
>> > >> >> > > >
>> > >> >> > > > I need to put my head on all of
>> this,
>> > >> but count
>> > >> >> on me
>> > >> >> > to
>> > >> >> > > be a RM.
>> > >> >> > > > I think
>> > >> >> > > > the best thing should be that you be
>> > the
>> > >> first
>> > >> >> RM to
>> > >> >> > try
>> > >> >> > > your own
>> > >> >> > > > development at least for the first
>> > time,
>> > >> and
>> > >> >> then the
>> > >> >> > > rest of us
>> > >> >> > > > will
>> > >> >> > > > follow you on the next releases.
>> With
>> > >> all this
>> > >> >> on place
>> > >> >> > > we maybe
>> > >> >> > > > could
>> > >> >> > > > release once a month or every two
>> > >> months...
>> > >> >> > > >
>> > >> >> > > > Thanks for doing this :)
>> > >> >> > > >
>> > >> >> > > > Carlos
>> > >> >> > > >
>> > >> >> > > >
>> > >> >> > > > El vie., 8 mar. 2019 a las 1:55,
>> Alex
>> > >> Harui
>> > >> >> > > > (<ah...@adobe.com.invalid>)
>> > >> >> > > > escribió:
>> > >> >> > > >
>> > >> >> > > > > OK, I've now seen Jenkins perform
>> the
>> > >> steps
>> > >> >> to build
>> > >> >> > > the release
>> > >> >> > > > > artifacts. Folks interested in
>> > >> Docker-izing
>> > >> >> the
>> > >> >> > steps
>> > >> >> > > are
>> > >> >> > > > welcome to look
>> > >> >> > > > > at the jobs on the "Royale
>> Release"
>> > >> tab on
>> > >> >> the CI
>> > >> >> > > server.
>> > >> >> > > > >
>> > >> >> > > >
>> > >> >> > >
>> > >> >> >
>> > >> >>
>> > >>
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=LfWCyCaClCVgfeINn4%2B%2Bk%2FSVUFXvgyV7QxMtx4B%2B%2Fu0%3D&reserved=0
>> > >> >> > > > >
>> > >> >> > > > > These steps assume that the RM can
>> > run
>> > >> the
>> > >> >> basic
>> > >> >> > Maven
>> > >> >> > > and Ant
>> > >> >> > > > build on
>> > >> >> > > > > the RM's computer. I think that's
>> a
>> > >> fair
>> > >> >> requirement
>> > >> >> > > since all
>> > >> >> > > > of us on the
>> > >> >> > > > > PMC need to able to do that to
>> build
>> > >> the RC
>> > >> >> in order
>> > >> >> > > to vote on
>> > >> >> > > > it.
>> > >> >> > > > > Jenkins does other tasks like run
>> > the
>> > >> Maven
>> > >> >> release
>> > >> >> > > plugin
>> > >> >> > > > steps.
>> > >> >> > > > >
>> > >> >> > > > > Currently that results in
>> binaries on
>> > >> Jenkins
>> > >> >> that
>> > >> >> > are
>> > >> >> > > > downloaded to the
>> > >> >> > > > > RM's computer. These binaries
>> need
>> > to
>> > >> be
>> > >> >> verified by
>> > >> >> > > the RM
>> > >> >> > > > which is the
>> > >> >> > > > > next phase I will be starting on
>> now.
>> > >> The RM
>> > >> >> > verifies
>> > >> >> > > the bits
>> > >> >> > > > and then
>> > >> >> > > > > PGP signs them. And then the bits
>> > are
>> > >> >> uploaded off
>> > >> >> > > the RM's
>> > >> >> > > > computer to
>> > >> >> > > > > Maven Staging or dist.a.o/dev.
>> If
>> > >> that
>> > >> >> uploading
>> > >> >> > > turns out to
>> > >> >> > > > be a point
>> > >> >> > > > > of failure, we have the option of
>> > >> having
>> > >> >> Jenkins
>> > >> >> > > upload the big
>> > >> >> > > > files and
>> > >> >> > > > > have the RM only upload PGP
>> signature
>> > >> files.
>> > >> >> Or
>> > >> >> > > finding a way
>> > >> >> > > > for Jenkins
>> > >> >> > > > > to get the signature files from
>> the
>> > >> RM. The
>> > >> >> uploads
>> > >> >> > > worked fine
>> > >> >> > > > for me,
>> > >> >> > > > > but then again, so did the old
>> > script's
>> > >> >> uploads.
>> > >> >> > > > >
>> > >> >> > > > > Therefore, once I get the binary
>> > >> verification
>> > >> >> phase
>> > >> >> > > completed, I
>> > >> >> > > > think
>> > >> >> > > > > someone other than me should be
>> the
>> > RM
>> > >> and
>> > >> >> try to use
>> > >> >> > > these
>> > >> >> > > > steps to
>> > >> >> > > > > generate the release and help
>> debug
>> > the
>> > >> >> process for
>> > >> >> > > the next
>> > >> >> > > > RM. So,
>> > >> >> > > > > please try to carve out some time
>> to
>> > >> be the
>> > >> >> RM. One
>> > >> >> > > advantage
>> > >> >> > > > of doing
>> > >> >> > > > > most of the work on Jenkins is
>> that
>> > it
>> > >> frees
>> > >> >> up my
>> > >> >> > > computer to
>> > >> >> > > > do other
>> > >> >> > > > > things while Jenkins is cranking
>> > away.
>> > >> >> > > > >
>> > >> >> > > > > I think we're at least a week away
>> > >> from binary
>> > >> >> > > verification,
>> > >> >> > > > maybe two, so
>> > >> >> > > > > it is time to start thinking about
>> > >> what is
>> > >> >> going in
>> > >> >> > > this release.
>> > >> >> > > > >
>> > >> >> > > > > Thanks,
>> > >> >> > > > > -Alex
>> > >> >> > > > >
>> > >> >> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
>> > >> >> > > <ah...@adobe.com.INVALID>
>> > >> >> > > > wrote:
>> > >> >> > > > >
>> > >> >> > > > > In case you haven't guessed,
>> I'm
>> > >> testing
>> > >> >> out
>> > >> >> > > Jenkins and its
>> > >> >> > > > ability
>> > >> >> > > > > to create the artifacts and send
>> > >> emails.
>> > >> >> Please
>> > >> >> > > ignore any
>> > >> >> > > > email that
>> > >> >> > > > > looks like a vote or discuss
>> thread.
>> > >> >> > > > >
>> > >> >> > > > > Thanks,
>> > >> >> > > > > -Alex
>> > >> >> > > > >
>> > >> >> > > > > On 2/10/19, 8:44 PM, "Alex
>> Harui"
>> > >> >> > > <ah...@adobe.com.INVALID>
>> > >> >> > > > wrote:
>> > >> >> > > > >
>> > >> >> > > > > Om,
>> > >> >> > > > >
>> > >> >> > > > > Well, that's what I used
>> for
>> > >> the last
>> > >> >> > > release. I'm sure
>> > >> >> > > > there is
>> > >> >> > > > > probably some inaccuracy in it.
>> > >> >> > > > >
>> > >> >> > > > > That said, I'm abandoning
>> > that
>> > >> >> document and
>> > >> >> > > taking a new
>> > >> >> > > > angle
>> > >> >> > > > > because that document presumed
>> that
>> > the
>> > >> >> release
>> > >> >> > > manager was
>> > >> >> > > > trying to
>> > >> >> > > > > create a release on his/her
>> computer.
>> > >> I've
>> > >> >> given up
>> > >> >> > > on that and
>> > >> >> > > > working on
>> > >> >> > > > > making releases from a shared
>> > computer
>> > >> for the
>> > >> >> > reasons
>> > >> >> > > I've
>> > >> >> > > > stated
>> > >> >> > > > > upthread. I hope to make some
>> > >> progress on
>> > >> >> that this
>> > >> >> > > week.
>> > >> >> > > > >
>> > >> >> > > > > The key difference is that
>> > the
>> > >> new
>> > >> >> angle does
>> > >> >> > > not
>> > >> >> > > > presume that you
>> > >> >> > > > > have Git SSH and PGP signatures
>> all
>> > >> set up on
>> > >> >> some
>> > >> >> > > computer. I
>> > >> >> > > > have not
>> > >> >> > > > > looked into how Docker would
>> handle
>> > >> that. You
>> > >> >> > > certainly
>> > >> >> > > > wouldn't want the
>> > >> >> > > > > Docker image to contain your SSH
>> or
>> > PGP
>> > >> >> keys/creds.
>> > >> >> > > And if the
>> > >> >> > > > Docker
>> > >> >> > > > > image doesn't, then that is
>> another
>> > >> stumbling
>> > >> >> block
>> > >> >> > > for future
>> > >> >> > > > RMs.
>> > >> >> > > > >
>> > >> >> > > > > The other key difference
>> is
>> > >> that the
>> > >> >> old
>> > >> >> > > script presumed
>> > >> >> > > > you could
>> > >> >> > > > > create the 3 release in 3 huge
>> "easy"
>> > >> steps.
>> > >> >> We've
>> > >> >> > > seen that is
>> > >> >> > > > only true
>> > >> >> > > > > for me. So the new angle creates
>> > many
>> > >> >> discrete steps
>> > >> >> > > managed by
>> > >> >> > > > Jenkins.
>> > >> >> > > > >
>> > >> >> > > > > So, it is up to you to
>> decide
>> > >> what
>> > >> >> you want
>> > >> >> > to
>> > >> >> > > > "Docker-ize". You
>> > >> >> > > > > can try to Docker-ize the current
>> 3
>> > big
>> > >> >> steps, so RMs
>> > >> >> > > can try to
>> > >> >> > > > run it on
>> > >> >> > > > > their systems, but I'd bet they
>> will
>> > >> just
>> > >> >> faiI due to
>> > >> >> > > network
>> > >> >> > > > issues. I
>> > >> >> > > > > would be interested in using
>> Docker
>> > to
>> > >> make
>> > >> >> each of
>> > >> >> > > these many
>> > >> >> > > > discrete
>> > >> >> > > > > steps portable to another server.
>> > >> I'm not
>> > >> >> going to
>> > >> >> > > involve
>> > >> >> > > > Docker at this
>> > >> >> > > > > point. My main goal is just to
>> see
>> > if
>> > >> I can
>> > >> >> create a
>> > >> >> > > workflow
>> > >> >> > > > of many
>> > >> >> > > > > discrete steps that isn't horribly
>> > >> painful.
>> > >> >> Once we
>> > >> >> > > see what
>> > >> >> > > > these steps
>> > >> >> > > > > turn out to be, then we can worry
>> > >> about server
>> > >> >> > > portability of
>> > >> >> > > > those steps.
>> > >> >> > > > >
>> > >> >> > > > > Either way, we want to
>> know
>> > >> about
>> > >> >> running
>> > >> >> > > > Browser+Selenium for
>> > >> >> > > > > sure. And maybe
>> FlashPlayerDebugger
>> > >> or AIR.
>> > >> >> I would
>> > >> >> > > want to
>> > >> >> > > > know, for
>> > >> >> > > > > example, how you debug a failing
>> > >> checkintest
>> > >> >> in a
>> > >> >> > > Docker
>> > >> >> > > > container.
>> > >> >> > > > >
>> > >> >> > > > > Thanks,
>> > >> >> > > > > -Alex
>> > >> >> > > > >
>> > >> >> > > > >
>> > >> >> > > > > On 2/10/19, 5:18 PM,
>> > "OmPrakash
>> > >> >> Muppirala" <
>> > >> >> > > > bigosmallm@gmail.com>
>> > >> >> > > > > wrote:
>> > >> >> > > > >
>> > >> >> > > > > Alex,
>> > >> >> > > > >
>> > >> >> > > > > Just to be clear, I am
>> > >> following
>> > >> >> the
>> > >> >> > steps
>> > >> >> > > from here
>> > >> >> > > > to try
>> > >> >> > > > > and setup a
>> > >> >> > > > > docker container.
>> > >> >> > > > >
>> > >> >> > > > >
>> > >> >> > > > >
>> > >> >> > > >
>> > >> >> > >
>> > >> >> >
>> > >>
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=Lhm0hudN8Nbx%2F6Lnmz0Wlus3EpV1o1h8XWBzBUoEWOA%3D&reserved=0
>> > >> >> > > > >
>> > >> >> > > > > Is this doc up to
>> date?
>> > >> >> > > > >
>> > >> >> > > > > Thanks,
>> > >> >> > > > > Om
>> > >> >> > > > >
>> > >> >> > > > > On Wed, Feb 6, 2019 at
>> > >> 12:02 PM
>> > >> >> OmPrakash
>> > >> >> > > Muppirala <
>> > >> >> > > > > bigosmallm@gmail.com>
>> > >> >> > > > > wrote:
>> > >> >> > > > >
>> > >> >> > > > > > One approach is to
>> have
>> > >> each
>> > >> >> step in
>> > >> >> > the
>> > >> >> > > process
>> > >> >> > > > spin up a
>> > >> >> > > > > docker image.
>> > >> >> > > > > > And use
>> docker-compose
>> > >> to run
>> > >> >> each
>> > >> >> > > step. All the
>> > >> >> > > > images can
>> > >> >> > > > > be made to
>> > >> >> > > > > > share a common
>> volume
>> > >> where all
>> > >> >> the
>> > >> >> > > artifacts are
>> > >> >> > > > stored
>> > >> >> > > > > across steps.
>> > >> >> > > > > >
>> > >> >> > > > > > You are right about
>> the
>> > >> >> networking
>> > >> >> > issue
>> > >> >> > > though.
>> > >> >> > > > Any
>> > >> >> > > > > network related
>> > >> >> > > > > > failure that occurs
>> on
>> > >> the host
>> > >> >> machine
>> > >> >> > > will most
>> > >> >> > > > likely
>> > >> >> > > > > occur in the
>> > >> >> > > > > > docker container.
>> > >> Although, I
>> > >> >> am not
>> > >> >> > > clear how we
>> > >> >> > > > can
>> > >> >> > > > > guarantee that the
>> > >> >> > > > > > same issues will not
>> > >> occur on
>> > >> >> the
>> > >> >> > > Jenkins server.
>> > >> >> > > > I mean,
>> > >> >> > > > > what is special
>> > >> >> > > > > > about the Jenkins
>> > server
>> > >> that
>> > >> >> makes it
>> > >> >> > > immune to
>> > >> >> > > > these
>> > >> >> > > > > networking issues?
>> > >> >> > > > > >
>> > >> >> > > > > > Thanks,
>> > >> >> > > > > > Om
>> > >> >> > > > > >
>> > >> >> > > > > > On Wed, Feb 6, 2019
>> at
>> > >> 11:48 AM
>> > >> >> Alex
>> > >> >> > > Harui
>> > >> >> > > > > <ah...@adobe.com.invalid>
>> > >> >> > > > > > wrote:
>> > >> >> > > > > >
>> > >> >> > > > > >> Again, I don't know
>> > >> anything
>> > >> >> about
>> > >> >> > > Docker, but
>> > >> >> > > > before we
>> > >> >> > > > > spend a lot of
>> > >> >> > > > > >> time on Docker, I
>> also
>> > >> want to
>> > >> >> point
>> > >> >> > > out that the
>> > >> >> > > > process
>> > >> >> > > > > to create a
>> > >> >> > > > > >> release cannot
>> really
>> > be
>> > >> >> thought of as
>> > >> >> > > "one
>> > >> >> > > > application".
>> > >> >> > > > > It will be a
>> > >> >> > > > > >> series of "steps"
>> to
>> > >> run.
>> > >> >> How many
>> > >> >> > > steps
>> > >> >> > > > depends on
>> > >> >> > > > > whether we think we
>> > >> >> > > > > >> can isolate enough
>> > >> stuff via
>> > >> >> Docker to
>> > >> >> > > be able to
>> > >> >> > > > run
>> > >> >> > > > > Docker on the RM's
>> > >> >> > > > > >> computer instead of
>> > >> some shared
>> > >> >> > > computer. On a
>> > >> >> > > > shared
>> > >> >> > > > > computer there will
>> > >> >> > > > > >> be dozens of steps
>> > >> because the
>> > >> >> RM will
>> > >> >> > > need to
>> > >> >> > > > enter
>> > >> >> > > > > passwords to commit
>> > >> >> > > > > >> stuff. On a local
>> > >> computer I
>> > >> >> guess
>> > >> >> > the
>> > >> >> > > RM can
>> > >> >> > > > supply
>> > >> >> > > > > passwords but I think
>> > >> >> > > > > >> there will be
>> stopping
>> > >> points
>> > >> >> where
>> > >> >> > the
>> > >> >> > > Maven
>> > >> >> > > > artifacts are
>> > >> >> > > > > deployed and
>> > >> >> > > > > >> the staging repo is
>> > >> closed, and
>> > >> >> > another
>> > >> >> > > stopping
>> > >> >> > > > point for
>> > >> >> > > > > the vote. It
>> > >> >> > > > > >> seems like Docker
>> > works
>> > >> by
>> > >> >> downloading
>> > >> >> > > > dependencies. Given
>> > >> >> > > > > that the
>> > >> >> > > > > >> problem the RMs had
>> > >> last time
>> > >> >> involved
>> > >> >> > > downloads
>> > >> >> > > > and
>> > >> >> > > > > uploads, why do we
>> > >> >> > > > > >> think Docker will
>> > >> really solve
>> > >> >> this
>> > >> >> > for
>> > >> >> > > creating
>> > >> >> > > > releases
>> > >> >> > > > > on local machines?
>> > >> >> > > > > >>
>> > >> >> > > > > >> The reason to do
>> this
>> > >> on a
>> > >> >> shared
>> > >> >> > > machine is so
>> > >> >> > > > that new
>> > >> >> > > > > RMs don't have
>> > >> >> > > > > >> to do as much
>> setup.
>> > >> But then
>> > >> >> I
>> > >> >> > wonder
>> > >> >> > > about the
>> > >> >> > > > > efficiency of kicking off
>> > >> >> > > > > >> that many Docker
>> > images.
>> > >> >> Jenkins can
>> > >> >> > > manage that
>> > >> >> > > > already.
>> > >> >> > > > > Does Docker
>> > >> >> > > > > >> have some sort of
>> > >> similar
>> > >> >> Dashboard or
>> > >> >> > > would we
>> > >> >> > > > use Jenkins
>> > >> >> > > > > to kick off
>> > >> >> > > > > >> Docker steps? I
>> can't
>> > >> quite
>> > >> >> picture
>> > >> >> > > what is the
>> > >> >> > > > outermost
>> > >> >> > > > > >> control/dashboard.
>> > >> >> > > > > >>
>> > >> >> > > > > >> -Alex
>> > >> >> > > > > >>
>> > >> >> > > > > >> On 2/6/19, 11:03
>> AM,
>> > >> "Harbs" <
>> > >> >> > > > harbs.lists@gmail.com> wrote:
>> > >> >> > > > > >>
>> > >> >> > > > > >> A quick search
>> > >> turns up
>> > >> >> this:
>> > >> >> > > > > >>
>> > >> >> > > > > >>
>> > >> >> > > > > >>
>> > >> >> > > > >
>> > >> >> > > >
>> > >> >> > >
>> > >> >> >
>> > >>
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
>> > >> >> > > > > >> <
>> > >> >> > > > > >>
>> > >> >> > > > >
>> > >> >> > > >
>> > >> >> > >
>> > >> >> >
>> > >>
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
>> > >> >> > > > > >> >
>> > >> >> > > > > >>
>> > >> >> > > > > >>
>> > >> >> > > > >
>> > >> >> > > >
>> > >> >> > >
>> > >> >> >
>> > >>
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=YPCe61GnfpckdNdqMRCDAHXsd3dvMHT3BO157C%2Fufs4%3D&reserved=0
>> > >> >> > > > > >> <
>> > >> >> > > > > >>
>> > >> >> > > > >
>> > >> >> > > >
>> > >> >> > >
>> > >> >> >
>> > >>
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=YPCe61GnfpckdNdqMRCDAHXsd3dvMHT3BO157C%2Fufs4%3D&reserved=0
>> > >> >> > > > > >> >
>> > >> >> > > > > >>
>> > >> >> > > > > >>
>> > >> >> > > > >
>> > >> >> > > >
>> > >> >> > >
>> > >> >> >
>> > >>
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=lsUmIIjQQi5CZhXTvQgd7lPt%2BVL2ApXFbK7i0NbMk1k%3D&reserved=0
>> > >> >> > > > > >> <
>> > >> >> > > > > >>
>> > >> >> > > > >
>> > >> >> > > >
>> > >> >> > >
>> > >> >> >
>> > >>
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=lsUmIIjQQi5CZhXTvQgd7lPt%2BVL2ApXFbK7i0NbMk1k%3D&reserved=0
>> > >> >> > > > > >> >
>> > >> >> > > > > >>
>> > >> >> > > > > >> > On Feb 6,
>> 2019,
>> > >> at 8:59
>> > >> >> PM, Alex
>> > >> >> > > Harui
>> > >> >> > > > > <ah...@adobe.com.INVALID>
>> > >> >> > > > > >> wrote:
>> > >> >> > > > > >> >
>> > >> >> > > > > >> > Thanks for
>> > >> volunteering
>> > >> >> to try
>> > >> >> > it
>> > >> >> > > Om. IMO,
>> > >> >> > > > even more
>> > >> >> > > > > important
>> > >> >> > > > > >> than Firefox+Flash
>> is
>> > >> >> > > SomeBrowser+Selenium. We
>> > >> >> > > > may also
>> > >> >> > > > > need to run Adobe
>> > >> >> > > > > >> AIR's adb. We
>> could
>> > >> probably
>> > >> >> turn off
>> > >> >> > > the Flash
>> > >> >> > > > tests or
>> > >> >> > > > > replace Flash
>> > >> >> > > > > >> with AIR.
>> > >> >> > > > > >> >
>> > >> >> > > > > >> > Thanks,
>> > >> >> > > > > >> > -Alex
>> > >> >> > > > > >> >
>> > >> >> > > > > >> > On 2/6/19,
>> 10:54
>> > >> AM,
>> > >> >> "Carlos
>> > >> >> > > Rovira" <
>> > >> >> > > > > carlosrovira@apache.org>
>> > >> >> > > > > >> wrote:
>> > >> >> > > > > >> >
>> > >> >> > > > > >> > Hi Om,
>> that
>> > >> would be
>> > >> >> great!
>> > >> >> > > waiting for
>> > >> >> > > > your
>> > >> >> > > > > experience with a
>> > >> >> > > > > >> that! :)
>> > >> >> > > > > >> >
>> > >> >> > > > > >> > El mié., 6
>> > >> feb. 2019
>> > >> >> a las
>> > >> >> > > 19:31,
>> > >> >> > > > OmPrakash
>> > >> >> > > > > Muppirala (<
>> > >> >> > > > > >>
>> bigosmallm@gmail.com
>> > >)
>> > >> >> > > > > >> >
>>
>
Re: 0.9.6 Release
Posted by Greg Dove <gr...@gmail.com>.
Working on it!
On Tue, Jun 11, 2019 at 4:29 PM Piotr Zarzycki <pi...@gmail.com>
wrote:
> Hi Greg,
>
> After your merge the goal should be that build on Jenkins is working fine.
> Please make sure that is happen.
>
> Thanks,
> Piotr
>
> On Tue, Jun 11, 2019, 5:32 AM Greg Dove <gr...@gmail.com> wrote:
>
> > I will stick with the plan of single commit, I think it should be easier
> > for you if there are any conflicts.
> > Last build testing is running now in local develop. I will push after
> > that...
> >
> > On Tue, Jun 11, 2019 at 3:15 PM Greg Dove <gr...@gmail.com> wrote:
> >
> > >
> > > Thanks Alex, I was planning to merge this as a single squashed commit,
> > > because it isolates all the changes to a single commit (but this will
> > mean
> > > there are many changes in one hit).
> > > Do you have a preference in terms of how easy it will make things for
> > you?
> > >
> > >
> > > On Tue, Jun 11, 2019 at 3:07 PM Alex Harui <ah...@adobe.com.invalid>
> > > wrote:
> > >
> > >> OK, I will wait to see your commit emails. I will do some other
> things
> > >> like the wiki doc.
> > >>
> > >> -Alex
> > >>
> > >> On 6/10/19, 8:06 PM, "Greg Dove" <gr...@gmail.com> wrote:
> > >>
> > >> Hi Alex, I guess you might be back on Royale about now. Just a
> heads
> > >> up: I
> > >> am about 20-30 mins max from merging in what I have. Hope that's
> > still
> > >> ok... please let me know if not.
> > >> Thanks,
> > >> -Greg
> > >>
> > >>
> > >> On Tue, Jun 11, 2019 at 7:51 AM Greg Dove <gr...@gmail.com>
> > >> wrote:
> > >>
> > >> >
> > >> > Thanks Alex - I'll try to hit the window, much appreciated!
> > >> >
> > >> >
> > >> > On Tue, Jun 11, 2019 at 6:57 AM Alex Harui
> > <aharui@adobe.com.invalid
> > >> >
> > >> > wrote:
> > >> >
> > >> >> Hi Greg,
> > >> >>
> > >> >> It turns out I have a "split shift" today. I'm stopping work
> for
> > >> the
> > >> >> next 7 or 8 hours then will get around to the merge. So if you
> > >> can get
> > >> >> your changes merged in that amount of time, then I will wait
> for
> > >> you and
> > >> >> deal with any merge conflicts (there are almost certain to be
> > >> some).
> > >> >>
> > >> >> -Alex
> > >> >>
> > >> >> On 6/10/19, 11:46 AM, "Greg Dove" <gr...@gmail.com> wrote:
> > >> >>
> > >> >> Alex, slightly OT, but in terms of coordination: fyi I am
> > also
> > >> very
> > >> >> close
> > >> >> to merging the language improvements branch into develop.
> As
> > I
> > >> already
> > >> >> mentioned elsewhere, I was hoping to do that a couple of
> days
> > >> back,
> > >> >> but
> > >> >> some recent things also took me a little longer than
> expected
> > >> (I have
> > >> >> additional local changes/fixes not yet in remote branch) .
> I
> > >> was
> > >> >> planning
> > >> >> to merge that today also.
> > >> >>
> > >> >> However, I will wait until after your merge, so I'm hoping
> > you
> > >> can get
> > >> >> yours in today (if not, I will wait). I will probably put
> > mine
> > >> in as a
> > >> >> squashed commit after yours.
> > >> >>
> > >> >>
> > >> >> On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <
> > >> >> piotrzarzycki21@gmail.com>
> > >> >> wrote:
> > >> >>
> > >> >> > Hi Alex,
> > >> >> >
> > >> >> > Many thanks for that! I will try to be RM. I will have
> some
> > >> >> dedicated time
> > >> >> > for that. I will wait for your instruction and merge to
> > >> develop.
> > >> >> >
> > >> >> > Thanks,
> > >> >> > Piotr
> > >> >> >
> > >> >> >
> > >> >> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
> > >> <ah...@adobe.com.invalid>
> > >> >> wrote:
> > >> >> >
> > >> >> > > Well, that turned out to be much more time-consuming
> > than I
> > >> >> expected, but
> > >> >> > > we can now create identical release artifacts on Mac
> and
> > >> Win. I
> > >> >> am
> > >> >> > hopeful
> > >> >> > > this effort will pay off not only now in having other
> > folks
> > >> >> generate
> > >> >> > > releases, but also in the future if signed binaries
> > become
> > >> a
> > >> >> requirement.
> > >> >> > >
> > >> >> > > There continues to be a lot of distractions in my life
> > >> that can
> > >> >> cause
> > >> >> > > delays, but I hope to merge the release_practice
> branches
> > >> into
> > >> >> develop
> > >> >> > over
> > >> >> > > the next day or two and figure out where in the wiki to
> > >> document
> > >> >> the
> > >> >> > > release process. So, now is the time for one or more
> > >> people to
> > >> >> step up
> > >> >> > to
> > >> >> > > be the RMs for 0.9.6 and help debug and improve the
> > >> process.
> > >> >> > >
> > >> >> > > I am going to try very hard not to "own" the process.
> If
> > >> >> something goes
> > >> >> > > wrong, I am going to ask others to try to debug and fix
> > it
> > >> first
> > >> >> because
> > >> >> > it
> > >> >> > > is in the project's best interests for others to truly
> > >> understand
> > >> >> how
> > >> >> > this
> > >> >> > > stuff works.
> > >> >> > >
> > >> >> > > Thanks,
> > >> >> > > -Alex
> > >> >> > >
> > >> >> > > On 5/23/19, 9:54 AM, "Alex Harui"
> > <aharui@adobe.com.INVALID
> > >> >
> > >> >> wrote:
> > >> >> > >
> > >> >> > > It has turned out to be harder than expected to get
> > >> the same
> > >> >> binaries
> > >> >> > > on Mac and Win. I now have the identical binaries for
> > >> >> royale-compiler
> > >> >> > and
> > >> >> > > royale-typedefs Maven artifacts and am starting on
> > >> royale-asjs.
> > >> >> I might
> > >> >> > > get lucky and the changes that fixed royale-typedefs
> SWCs
> > >> will
> > >> >> magically
> > >> >> > > get the royale-asjs SWCs to match. Then we have to
> make
> > >> the Ant
> > >> >> > artifacts
> > >> >> > > match.
> > >> >> > >
> > >> >> > > There have been a lot of distractions in my
> non-work
> > >> life
> > >> >> which has
> > >> >> > > also impeded progress. I hope to make much progress
> this
> > >> coming
> > >> >> week and
> > >> >> > > if we're lucky, I will be asking for a volunteer (or
> > >> volunteers)
> > >> >> to test
> > >> >> > > drive all of this stuff and be the RM for 0.9.6. I am
> > not
> > >> going
> > >> >> to be
> > >> >> > the
> > >> >> > > RM.
> > >> >> > >
> > >> >> > > -Alex
> > >> >> > >
> > >> >> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> > >> >> piotrzarzycki21@gmail.com>
> > >> >> > > wrote:
> > >> >> > >
> > >> >> > > Hi Alex,
> > >> >> > >
> > >> >> > > It's been a while since you have started effort
> > >> with
> > >> >> automating
> > >> >> > > build.
> > >> >> > > Where are you with that ? Are we closer to
> > started
> > >> 0.9.6.
> > >> >> Do you
> > >> >> > > need any
> > >> >> > > help with this ?
> > >> >> > >
> > >> >> > > Thanks,
> > >> >> > > Piotr
> > >> >> > >
> > >> >> > > wt., 2 kwi 2019 o 19:30 Alex Harui
> > >> >> <ah...@adobe.com.invalid>
> > >> >> > > napisał(a):
> > >> >> > >
> > >> >> > > > Update:
> > >> >> > > >
> > >> >> > > > In order to make verification of binary
> release
> > >> packages
> > >> >> > created
> > >> >> > > on the
> > >> >> > > > server easier, I have made changes to our
> build
> > >> scripts
> > >> >> and
> > >> >> > > tools to try to
> > >> >> > > > generate reproducible binaries. I've seen
> two
> > >> >> different builds
> > >> >> > > compare on
> > >> >> > > > my Mac. The next challenge will be to see
> if
> > >> the
> > >> >> server can
> > >> >> > > build a
> > >> >> > > > package on Windows that will compare on Mac.
> > >> >> > > >
> > >> >> > > > One of the changes I needed to make is to
> > >> JBurg. The
> > >> >> version
> > >> >> > of
> > >> >> > > JBurg we
> > >> >> > > > use generates method names including a hash
> > that
> > >> doesn't
> > >> >> > > reproduce the same
> > >> >> > > > name each time. I have changes to JBurg
> ready,
> > >> however
> > >> >> JBurg
> > >> >> > is
> > >> >> > > currently
> > >> >> > > > under CPL which is category B. We only need
> > one
> > >> file,
> > >> >> we don't
> > >> >> > > need or
> > >> >> > > > want all of JBurg at this time. The one
> JBurg
> > >> file is
> > >> >> jointly
> > >> >> > > owned by
> > >> >> > > > Adobe and Tom Harwood. I've contact Tom and
> he
> > >> will be
> > >> >> filing
> > >> >> > > an ICLA and
> > >> >> > > > has given me permission to commit the lines
> he
> > >> owns in
> > >> >> that one
> > >> >> > > file.
> > >> >> > > >
> > >> >> > > > This is the revision of the file that will be
> > >> donated by
> > >> >> > > Tom/Adobe.
> > >> >> > > >
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=VS1za1vOQhtlKlK4Tdgq3ej04OlhFoYfHziyNbgOIN4%3D&reserved=0
> > >> >> > > >
> > >> >> > > > Once this file goes in with the changes to
> keep
> > >> the
> > >> >> method
> > >> >> > names
> > >> >> > > the same,
> > >> >> > > > there will be more tweaks to the release
> tasks
> > >> and then
> > >> >> we can
> > >> >> > > try cutting
> > >> >> > > > a release. I'm thinking we'll be at that
> point
> > >> in
> > >> >> early May,
> > >> >> > so
> > >> >> > > now is the
> > >> >> > > > time to get stuff in for the 0.9.6 release.
> > >> >> > > >
> > >> >> > > > Thanks,
> > >> >> > > > -Alex
> > >> >> > > >
> > >> >> > > > On 3/8/19, 9:27 AM, "Alex Harui" <
> > >> aharui@adobe.com>
> > >> >> wrote:
> > >> >> > > >
> > >> >> > > > I would much rather have others find and
> > fix
> > >> issues
> > >> >> > > themselves. That
> > >> >> > > > way, more people than just me will know how
> to
> > >> maintain
> > >> >> the
> > >> >> > > system. It
> > >> >> > > > actually turns out that, IMO, a group of
> people
> > >> can
> > >> >> work on the
> > >> >> > > release.
> > >> >> > > > There are 14 steps. Literally, 14 different
> > >> people
> > >> >> could
> > >> >> > > execute one step
> > >> >> > > > each.
> > >> >> > > >
> > >> >> > > > My 2 cents,
> > >> >> > > > -Alex
> > >> >> > > >
> > >> >> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> > >> >> > carlosrovira@apache.org>
> > >> >> > > wrote:
> > >> >> > > >
> > >> >> > > > Hi Alex,
> > >> >> > > >
> > >> >> > > > amazing work! congrats to reach to
> this
> > >> point!
> > >> >> :)
> > >> >> > > >
> > >> >> > > > I need to put my head on all of this,
> > >> but count
> > >> >> on me
> > >> >> > to
> > >> >> > > be a RM.
> > >> >> > > > I think
> > >> >> > > > the best thing should be that you be
> > the
> > >> first
> > >> >> RM to
> > >> >> > try
> > >> >> > > your own
> > >> >> > > > development at least for the first
> > time,
> > >> and
> > >> >> then the
> > >> >> > > rest of us
> > >> >> > > > will
> > >> >> > > > follow you on the next releases. With
> > >> all this
> > >> >> on place
> > >> >> > > we maybe
> > >> >> > > > could
> > >> >> > > > release once a month or every two
> > >> months...
> > >> >> > > >
> > >> >> > > > Thanks for doing this :)
> > >> >> > > >
> > >> >> > > > Carlos
> > >> >> > > >
> > >> >> > > >
> > >> >> > > > El vie., 8 mar. 2019 a las 1:55, Alex
> > >> Harui
> > >> >> > > > (<ah...@adobe.com.invalid>)
> > >> >> > > > escribió:
> > >> >> > > >
> > >> >> > > > > OK, I've now seen Jenkins perform
> the
> > >> steps
> > >> >> to build
> > >> >> > > the release
> > >> >> > > > > artifacts. Folks interested in
> > >> Docker-izing
> > >> >> the
> > >> >> > steps
> > >> >> > > are
> > >> >> > > > welcome to look
> > >> >> > > > > at the jobs on the "Royale Release"
> > >> tab on
> > >> >> the CI
> > >> >> > > server.
> > >> >> > > > >
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=LfWCyCaClCVgfeINn4%2B%2Bk%2FSVUFXvgyV7QxMtx4B%2B%2Fu0%3D&reserved=0
> > >> >> > > > >
> > >> >> > > > > These steps assume that the RM can
> > run
> > >> the
> > >> >> basic
> > >> >> > Maven
> > >> >> > > and Ant
> > >> >> > > > build on
> > >> >> > > > > the RM's computer. I think that's a
> > >> fair
> > >> >> requirement
> > >> >> > > since all
> > >> >> > > > of us on the
> > >> >> > > > > PMC need to able to do that to
> build
> > >> the RC
> > >> >> in order
> > >> >> > > to vote on
> > >> >> > > > it.
> > >> >> > > > > Jenkins does other tasks like run
> > the
> > >> Maven
> > >> >> release
> > >> >> > > plugin
> > >> >> > > > steps.
> > >> >> > > > >
> > >> >> > > > > Currently that results in binaries
> on
> > >> Jenkins
> > >> >> that
> > >> >> > are
> > >> >> > > > downloaded to the
> > >> >> > > > > RM's computer. These binaries need
> > to
> > >> be
> > >> >> verified by
> > >> >> > > the RM
> > >> >> > > > which is the
> > >> >> > > > > next phase I will be starting on
> now.
> > >> The RM
> > >> >> > verifies
> > >> >> > > the bits
> > >> >> > > > and then
> > >> >> > > > > PGP signs them. And then the bits
> > are
> > >> >> uploaded off
> > >> >> > > the RM's
> > >> >> > > > computer to
> > >> >> > > > > Maven Staging or dist.a.o/dev. If
> > >> that
> > >> >> uploading
> > >> >> > > turns out to
> > >> >> > > > be a point
> > >> >> > > > > of failure, we have the option of
> > >> having
> > >> >> Jenkins
> > >> >> > > upload the big
> > >> >> > > > files and
> > >> >> > > > > have the RM only upload PGP
> signature
> > >> files.
> > >> >> Or
> > >> >> > > finding a way
> > >> >> > > > for Jenkins
> > >> >> > > > > to get the signature files from the
> > >> RM. The
> > >> >> uploads
> > >> >> > > worked fine
> > >> >> > > > for me,
> > >> >> > > > > but then again, so did the old
> > script's
> > >> >> uploads.
> > >> >> > > > >
> > >> >> > > > > Therefore, once I get the binary
> > >> verification
> > >> >> phase
> > >> >> > > completed, I
> > >> >> > > > think
> > >> >> > > > > someone other than me should be the
> > RM
> > >> and
> > >> >> try to use
> > >> >> > > these
> > >> >> > > > steps to
> > >> >> > > > > generate the release and help debug
> > the
> > >> >> process for
> > >> >> > > the next
> > >> >> > > > RM. So,
> > >> >> > > > > please try to carve out some time
> to
> > >> be the
> > >> >> RM. One
> > >> >> > > advantage
> > >> >> > > > of doing
> > >> >> > > > > most of the work on Jenkins is that
> > it
> > >> frees
> > >> >> up my
> > >> >> > > computer to
> > >> >> > > > do other
> > >> >> > > > > things while Jenkins is cranking
> > away.
> > >> >> > > > >
> > >> >> > > > > I think we're at least a week away
> > >> from binary
> > >> >> > > verification,
> > >> >> > > > maybe two, so
> > >> >> > > > > it is time to start thinking about
> > >> what is
> > >> >> going in
> > >> >> > > this release.
> > >> >> > > > >
> > >> >> > > > > Thanks,
> > >> >> > > > > -Alex
> > >> >> > > > >
> > >> >> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
> > >> >> > > <ah...@adobe.com.INVALID>
> > >> >> > > > wrote:
> > >> >> > > > >
> > >> >> > > > > In case you haven't guessed,
> I'm
> > >> testing
> > >> >> out
> > >> >> > > Jenkins and its
> > >> >> > > > ability
> > >> >> > > > > to create the artifacts and send
> > >> emails.
> > >> >> Please
> > >> >> > > ignore any
> > >> >> > > > email that
> > >> >> > > > > looks like a vote or discuss
> thread.
> > >> >> > > > >
> > >> >> > > > > Thanks,
> > >> >> > > > > -Alex
> > >> >> > > > >
> > >> >> > > > > On 2/10/19, 8:44 PM, "Alex
> Harui"
> > >> >> > > <ah...@adobe.com.INVALID>
> > >> >> > > > wrote:
> > >> >> > > > >
> > >> >> > > > > Om,
> > >> >> > > > >
> > >> >> > > > > Well, that's what I used
> for
> > >> the last
> > >> >> > > release. I'm sure
> > >> >> > > > there is
> > >> >> > > > > probably some inaccuracy in it.
> > >> >> > > > >
> > >> >> > > > > That said, I'm abandoning
> > that
> > >> >> document and
> > >> >> > > taking a new
> > >> >> > > > angle
> > >> >> > > > > because that document presumed that
> > the
> > >> >> release
> > >> >> > > manager was
> > >> >> > > > trying to
> > >> >> > > > > create a release on his/her
> computer.
> > >> I've
> > >> >> given up
> > >> >> > > on that and
> > >> >> > > > working on
> > >> >> > > > > making releases from a shared
> > computer
> > >> for the
> > >> >> > reasons
> > >> >> > > I've
> > >> >> > > > stated
> > >> >> > > > > upthread. I hope to make some
> > >> progress on
> > >> >> that this
> > >> >> > > week.
> > >> >> > > > >
> > >> >> > > > > The key difference is that
> > the
> > >> new
> > >> >> angle does
> > >> >> > > not
> > >> >> > > > presume that you
> > >> >> > > > > have Git SSH and PGP signatures all
> > >> set up on
> > >> >> some
> > >> >> > > computer. I
> > >> >> > > > have not
> > >> >> > > > > looked into how Docker would handle
> > >> that. You
> > >> >> > > certainly
> > >> >> > > > wouldn't want the
> > >> >> > > > > Docker image to contain your SSH or
> > PGP
> > >> >> keys/creds.
> > >> >> > > And if the
> > >> >> > > > Docker
> > >> >> > > > > image doesn't, then that is another
> > >> stumbling
> > >> >> block
> > >> >> > > for future
> > >> >> > > > RMs.
> > >> >> > > > >
> > >> >> > > > > The other key difference is
> > >> that the
> > >> >> old
> > >> >> > > script presumed
> > >> >> > > > you could
> > >> >> > > > > create the 3 release in 3 huge
> "easy"
> > >> steps.
> > >> >> We've
> > >> >> > > seen that is
> > >> >> > > > only true
> > >> >> > > > > for me. So the new angle creates
> > many
> > >> >> discrete steps
> > >> >> > > managed by
> > >> >> > > > Jenkins.
> > >> >> > > > >
> > >> >> > > > > So, it is up to you to
> decide
> > >> what
> > >> >> you want
> > >> >> > to
> > >> >> > > > "Docker-ize". You
> > >> >> > > > > can try to Docker-ize the current 3
> > big
> > >> >> steps, so RMs
> > >> >> > > can try to
> > >> >> > > > run it on
> > >> >> > > > > their systems, but I'd bet they
> will
> > >> just
> > >> >> faiI due to
> > >> >> > > network
> > >> >> > > > issues. I
> > >> >> > > > > would be interested in using Docker
> > to
> > >> make
> > >> >> each of
> > >> >> > > these many
> > >> >> > > > discrete
> > >> >> > > > > steps portable to another server.
> > >> I'm not
> > >> >> going to
> > >> >> > > involve
> > >> >> > > > Docker at this
> > >> >> > > > > point. My main goal is just to see
> > if
> > >> I can
> > >> >> create a
> > >> >> > > workflow
> > >> >> > > > of many
> > >> >> > > > > discrete steps that isn't horribly
> > >> painful.
> > >> >> Once we
> > >> >> > > see what
> > >> >> > > > these steps
> > >> >> > > > > turn out to be, then we can worry
> > >> about server
> > >> >> > > portability of
> > >> >> > > > those steps.
> > >> >> > > > >
> > >> >> > > > > Either way, we want to know
> > >> about
> > >> >> running
> > >> >> > > > Browser+Selenium for
> > >> >> > > > > sure. And maybe
> FlashPlayerDebugger
> > >> or AIR.
> > >> >> I would
> > >> >> > > want to
> > >> >> > > > know, for
> > >> >> > > > > example, how you debug a failing
> > >> checkintest
> > >> >> in a
> > >> >> > > Docker
> > >> >> > > > container.
> > >> >> > > > >
> > >> >> > > > > Thanks,
> > >> >> > > > > -Alex
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > > > On 2/10/19, 5:18 PM,
> > "OmPrakash
> > >> >> Muppirala" <
> > >> >> > > > bigosmallm@gmail.com>
> > >> >> > > > > wrote:
> > >> >> > > > >
> > >> >> > > > > Alex,
> > >> >> > > > >
> > >> >> > > > > Just to be clear, I am
> > >> following
> > >> >> the
> > >> >> > steps
> > >> >> > > from here
> > >> >> > > > to try
> > >> >> > > > > and setup a
> > >> >> > > > > docker container.
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=Lhm0hudN8Nbx%2F6Lnmz0Wlus3EpV1o1h8XWBzBUoEWOA%3D&reserved=0
> > >> >> > > > >
> > >> >> > > > > Is this doc up to date?
> > >> >> > > > >
> > >> >> > > > > Thanks,
> > >> >> > > > > Om
> > >> >> > > > >
> > >> >> > > > > On Wed, Feb 6, 2019 at
> > >> 12:02 PM
> > >> >> OmPrakash
> > >> >> > > Muppirala <
> > >> >> > > > > bigosmallm@gmail.com>
> > >> >> > > > > wrote:
> > >> >> > > > >
> > >> >> > > > > > One approach is to
> have
> > >> each
> > >> >> step in
> > >> >> > the
> > >> >> > > process
> > >> >> > > > spin up a
> > >> >> > > > > docker image.
> > >> >> > > > > > And use
> docker-compose
> > >> to run
> > >> >> each
> > >> >> > > step. All the
> > >> >> > > > images can
> > >> >> > > > > be made to
> > >> >> > > > > > share a common volume
> > >> where all
> > >> >> the
> > >> >> > > artifacts are
> > >> >> > > > stored
> > >> >> > > > > across steps.
> > >> >> > > > > >
> > >> >> > > > > > You are right about
> the
> > >> >> networking
> > >> >> > issue
> > >> >> > > though.
> > >> >> > > > Any
> > >> >> > > > > network related
> > >> >> > > > > > failure that occurs
> on
> > >> the host
> > >> >> machine
> > >> >> > > will most
> > >> >> > > > likely
> > >> >> > > > > occur in the
> > >> >> > > > > > docker container.
> > >> Although, I
> > >> >> am not
> > >> >> > > clear how we
> > >> >> > > > can
> > >> >> > > > > guarantee that the
> > >> >> > > > > > same issues will not
> > >> occur on
> > >> >> the
> > >> >> > > Jenkins server.
> > >> >> > > > I mean,
> > >> >> > > > > what is special
> > >> >> > > > > > about the Jenkins
> > server
> > >> that
> > >> >> makes it
> > >> >> > > immune to
> > >> >> > > > these
> > >> >> > > > > networking issues?
> > >> >> > > > > >
> > >> >> > > > > > Thanks,
> > >> >> > > > > > Om
> > >> >> > > > > >
> > >> >> > > > > > On Wed, Feb 6, 2019
> at
> > >> 11:48 AM
> > >> >> Alex
> > >> >> > > Harui
> > >> >> > > > > <ah...@adobe.com.invalid>
> > >> >> > > > > > wrote:
> > >> >> > > > > >
> > >> >> > > > > >> Again, I don't know
> > >> anything
> > >> >> about
> > >> >> > > Docker, but
> > >> >> > > > before we
> > >> >> > > > > spend a lot of
> > >> >> > > > > >> time on Docker, I
> also
> > >> want to
> > >> >> point
> > >> >> > > out that the
> > >> >> > > > process
> > >> >> > > > > to create a
> > >> >> > > > > >> release cannot
> really
> > be
> > >> >> thought of as
> > >> >> > > "one
> > >> >> > > > application".
> > >> >> > > > > It will be a
> > >> >> > > > > >> series of "steps" to
> > >> run.
> > >> >> How many
> > >> >> > > steps
> > >> >> > > > depends on
> > >> >> > > > > whether we think we
> > >> >> > > > > >> can isolate enough
> > >> stuff via
> > >> >> Docker to
> > >> >> > > be able to
> > >> >> > > > run
> > >> >> > > > > Docker on the RM's
> > >> >> > > > > >> computer instead of
> > >> some shared
> > >> >> > > computer. On a
> > >> >> > > > shared
> > >> >> > > > > computer there will
> > >> >> > > > > >> be dozens of steps
> > >> because the
> > >> >> RM will
> > >> >> > > need to
> > >> >> > > > enter
> > >> >> > > > > passwords to commit
> > >> >> > > > > >> stuff. On a local
> > >> computer I
> > >> >> guess
> > >> >> > the
> > >> >> > > RM can
> > >> >> > > > supply
> > >> >> > > > > passwords but I think
> > >> >> > > > > >> there will be
> stopping
> > >> points
> > >> >> where
> > >> >> > the
> > >> >> > > Maven
> > >> >> > > > artifacts are
> > >> >> > > > > deployed and
> > >> >> > > > > >> the staging repo is
> > >> closed, and
> > >> >> > another
> > >> >> > > stopping
> > >> >> > > > point for
> > >> >> > > > > the vote. It
> > >> >> > > > > >> seems like Docker
> > works
> > >> by
> > >> >> downloading
> > >> >> > > > dependencies. Given
> > >> >> > > > > that the
> > >> >> > > > > >> problem the RMs had
> > >> last time
> > >> >> involved
> > >> >> > > downloads
> > >> >> > > > and
> > >> >> > > > > uploads, why do we
> > >> >> > > > > >> think Docker will
> > >> really solve
> > >> >> this
> > >> >> > for
> > >> >> > > creating
> > >> >> > > > releases
> > >> >> > > > > on local machines?
> > >> >> > > > > >>
> > >> >> > > > > >> The reason to do
> this
> > >> on a
> > >> >> shared
> > >> >> > > machine is so
> > >> >> > > > that new
> > >> >> > > > > RMs don't have
> > >> >> > > > > >> to do as much setup.
> > >> But then
> > >> >> I
> > >> >> > wonder
> > >> >> > > about the
> > >> >> > > > > efficiency of kicking off
> > >> >> > > > > >> that many Docker
> > images.
> > >> >> Jenkins can
> > >> >> > > manage that
> > >> >> > > > already.
> > >> >> > > > > Does Docker
> > >> >> > > > > >> have some sort of
> > >> similar
> > >> >> Dashboard or
> > >> >> > > would we
> > >> >> > > > use Jenkins
> > >> >> > > > > to kick off
> > >> >> > > > > >> Docker steps? I
> can't
> > >> quite
> > >> >> picture
> > >> >> > > what is the
> > >> >> > > > outermost
> > >> >> > > > > >> control/dashboard.
> > >> >> > > > > >>
> > >> >> > > > > >> -Alex
> > >> >> > > > > >>
> > >> >> > > > > >> On 2/6/19, 11:03 AM,
> > >> "Harbs" <
> > >> >> > > > harbs.lists@gmail.com> wrote:
> > >> >> > > > > >>
> > >> >> > > > > >> A quick search
> > >> turns up
> > >> >> this:
> > >> >> > > > > >>
> > >> >> > > > > >>
> > >> >> > > > > >>
> > >> >> > > > >
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
> > >> >> > > > > >> <
> > >> >> > > > > >>
> > >> >> > > > >
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
> > >> >> > > > > >> >
> > >> >> > > > > >>
> > >> >> > > > > >>
> > >> >> > > > >
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=YPCe61GnfpckdNdqMRCDAHXsd3dvMHT3BO157C%2Fufs4%3D&reserved=0
> > >> >> > > > > >> <
> > >> >> > > > > >>
> > >> >> > > > >
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=YPCe61GnfpckdNdqMRCDAHXsd3dvMHT3BO157C%2Fufs4%3D&reserved=0
> > >> >> > > > > >> >
> > >> >> > > > > >>
> > >> >> > > > > >>
> > >> >> > > > >
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=lsUmIIjQQi5CZhXTvQgd7lPt%2BVL2ApXFbK7i0NbMk1k%3D&reserved=0
> > >> >> > > > > >> <
> > >> >> > > > > >>
> > >> >> > > > >
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=lsUmIIjQQi5CZhXTvQgd7lPt%2BVL2ApXFbK7i0NbMk1k%3D&reserved=0
> > >> >> > > > > >> >
> > >> >> > > > > >>
> > >> >> > > > > >> > On Feb 6,
> 2019,
> > >> at 8:59
> > >> >> PM, Alex
> > >> >> > > Harui
> > >> >> > > > > <ah...@adobe.com.INVALID>
> > >> >> > > > > >> wrote:
> > >> >> > > > > >> >
> > >> >> > > > > >> > Thanks for
> > >> volunteering
> > >> >> to try
> > >> >> > it
> > >> >> > > Om. IMO,
> > >> >> > > > even more
> > >> >> > > > > important
> > >> >> > > > > >> than Firefox+Flash
> is
> > >> >> > > SomeBrowser+Selenium. We
> > >> >> > > > may also
> > >> >> > > > > need to run Adobe
> > >> >> > > > > >> AIR's adb. We could
> > >> probably
> > >> >> turn off
> > >> >> > > the Flash
> > >> >> > > > tests or
> > >> >> > > > > replace Flash
> > >> >> > > > > >> with AIR.
> > >> >> > > > > >> >
> > >> >> > > > > >> > Thanks,
> > >> >> > > > > >> > -Alex
> > >> >> > > > > >> >
> > >> >> > > > > >> > On 2/6/19,
> 10:54
> > >> AM,
> > >> >> "Carlos
> > >> >> > > Rovira" <
> > >> >> > > > > carlosrovira@apache.org>
> > >> >> > > > > >> wrote:
> > >> >> > > > > >> >
> > >> >> > > > > >> > Hi Om, that
> > >> would be
> > >> >> great!
> > >> >> > > waiting for
> > >> >> > > > your
> > >> >> > > > > experience with a
> > >> >> > > > > >> that! :)
> > >> >> > > > > >> >
> > >> >> > > > > >> > El mié., 6
> > >> feb. 2019
> > >> >> a las
> > >> >> > > 19:31,
> > >> >> > > > OmPrakash
> > >> >> > > > > Muppirala (<
> > >> >> > > > > >>
> bigosmallm@gmail.com
> > >)
> > >> >> > > > > >> >
>
0.9.6 Release
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Greg,
After your merge the goal should be that build on Jenkins is working fine.
Please make sure that is happen.
Thanks,
Piotr
On Tue, Jun 11, 2019, 5:32 AM Greg Dove <gr...@gmail.com> wrote:
> I will stick with the plan of single commit, I think it should be easier
> for you if there are any conflicts.
> Last build testing is running now in local develop. I will push after
> that...
>
> On Tue, Jun 11, 2019 at 3:15 PM Greg Dove <gr...@gmail.com> wrote:
>
> >
> > Thanks Alex, I was planning to merge this as a single squashed commit,
> > because it isolates all the changes to a single commit (but this will
> mean
> > there are many changes in one hit).
> > Do you have a preference in terms of how easy it will make things for
> you?
> >
> >
> > On Tue, Jun 11, 2019 at 3:07 PM Alex Harui <ah...@adobe.com.invalid>
> > wrote:
> >
> >> OK, I will wait to see your commit emails. I will do some other things
> >> like the wiki doc.
> >>
> >> -Alex
> >>
> >> On 6/10/19, 8:06 PM, "Greg Dove" <gr...@gmail.com> wrote:
> >>
> >> Hi Alex, I guess you might be back on Royale about now. Just a heads
> >> up: I
> >> am about 20-30 mins max from merging in what I have. Hope that's
> still
> >> ok... please let me know if not.
> >> Thanks,
> >> -Greg
> >>
> >>
> >> On Tue, Jun 11, 2019 at 7:51 AM Greg Dove <gr...@gmail.com>
> >> wrote:
> >>
> >> >
> >> > Thanks Alex - I'll try to hit the window, much appreciated!
> >> >
> >> >
> >> > On Tue, Jun 11, 2019 at 6:57 AM Alex Harui
> <aharui@adobe.com.invalid
> >> >
> >> > wrote:
> >> >
> >> >> Hi Greg,
> >> >>
> >> >> It turns out I have a "split shift" today. I'm stopping work for
> >> the
> >> >> next 7 or 8 hours then will get around to the merge. So if you
> >> can get
> >> >> your changes merged in that amount of time, then I will wait for
> >> you and
> >> >> deal with any merge conflicts (there are almost certain to be
> >> some).
> >> >>
> >> >> -Alex
> >> >>
> >> >> On 6/10/19, 11:46 AM, "Greg Dove" <gr...@gmail.com> wrote:
> >> >>
> >> >> Alex, slightly OT, but in terms of coordination: fyi I am
> also
> >> very
> >> >> close
> >> >> to merging the language improvements branch into develop. As
> I
> >> already
> >> >> mentioned elsewhere, I was hoping to do that a couple of days
> >> back,
> >> >> but
> >> >> some recent things also took me a little longer than expected
> >> (I have
> >> >> additional local changes/fixes not yet in remote branch) . I
> >> was
> >> >> planning
> >> >> to merge that today also.
> >> >>
> >> >> However, I will wait until after your merge, so I'm hoping
> you
> >> can get
> >> >> yours in today (if not, I will wait). I will probably put
> mine
> >> in as a
> >> >> squashed commit after yours.
> >> >>
> >> >>
> >> >> On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <
> >> >> piotrzarzycki21@gmail.com>
> >> >> wrote:
> >> >>
> >> >> > Hi Alex,
> >> >> >
> >> >> > Many thanks for that! I will try to be RM. I will have some
> >> >> dedicated time
> >> >> > for that. I will wait for your instruction and merge to
> >> develop.
> >> >> >
> >> >> > Thanks,
> >> >> > Piotr
> >> >> >
> >> >> >
> >> >> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
> >> <ah...@adobe.com.invalid>
> >> >> wrote:
> >> >> >
> >> >> > > Well, that turned out to be much more time-consuming
> than I
> >> >> expected, but
> >> >> > > we can now create identical release artifacts on Mac and
> >> Win. I
> >> >> am
> >> >> > hopeful
> >> >> > > this effort will pay off not only now in having other
> folks
> >> >> generate
> >> >> > > releases, but also in the future if signed binaries
> become
> >> a
> >> >> requirement.
> >> >> > >
> >> >> > > There continues to be a lot of distractions in my life
> >> that can
> >> >> cause
> >> >> > > delays, but I hope to merge the release_practice branches
> >> into
> >> >> develop
> >> >> > over
> >> >> > > the next day or two and figure out where in the wiki to
> >> document
> >> >> the
> >> >> > > release process. So, now is the time for one or more
> >> people to
> >> >> step up
> >> >> > to
> >> >> > > be the RMs for 0.9.6 and help debug and improve the
> >> process.
> >> >> > >
> >> >> > > I am going to try very hard not to "own" the process. If
> >> >> something goes
> >> >> > > wrong, I am going to ask others to try to debug and fix
> it
> >> first
> >> >> because
> >> >> > it
> >> >> > > is in the project's best interests for others to truly
> >> understand
> >> >> how
> >> >> > this
> >> >> > > stuff works.
> >> >> > >
> >> >> > > Thanks,
> >> >> > > -Alex
> >> >> > >
> >> >> > > On 5/23/19, 9:54 AM, "Alex Harui"
> <aharui@adobe.com.INVALID
> >> >
> >> >> wrote:
> >> >> > >
> >> >> > > It has turned out to be harder than expected to get
> >> the same
> >> >> binaries
> >> >> > > on Mac and Win. I now have the identical binaries for
> >> >> royale-compiler
> >> >> > and
> >> >> > > royale-typedefs Maven artifacts and am starting on
> >> royale-asjs.
> >> >> I might
> >> >> > > get lucky and the changes that fixed royale-typedefs SWCs
> >> will
> >> >> magically
> >> >> > > get the royale-asjs SWCs to match. Then we have to make
> >> the Ant
> >> >> > artifacts
> >> >> > > match.
> >> >> > >
> >> >> > > There have been a lot of distractions in my non-work
> >> life
> >> >> which has
> >> >> > > also impeded progress. I hope to make much progress this
> >> coming
> >> >> week and
> >> >> > > if we're lucky, I will be asking for a volunteer (or
> >> volunteers)
> >> >> to test
> >> >> > > drive all of this stuff and be the RM for 0.9.6. I am
> not
> >> going
> >> >> to be
> >> >> > the
> >> >> > > RM.
> >> >> > >
> >> >> > > -Alex
> >> >> > >
> >> >> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> >> >> piotrzarzycki21@gmail.com>
> >> >> > > wrote:
> >> >> > >
> >> >> > > Hi Alex,
> >> >> > >
> >> >> > > It's been a while since you have started effort
> >> with
> >> >> automating
> >> >> > > build.
> >> >> > > Where are you with that ? Are we closer to
> started
> >> 0.9.6.
> >> >> Do you
> >> >> > > need any
> >> >> > > help with this ?
> >> >> > >
> >> >> > > Thanks,
> >> >> > > Piotr
> >> >> > >
> >> >> > > wt., 2 kwi 2019 o 19:30 Alex Harui
> >> >> <ah...@adobe.com.invalid>
> >> >> > > napisał(a):
> >> >> > >
> >> >> > > > Update:
> >> >> > > >
> >> >> > > > In order to make verification of binary release
> >> packages
> >> >> > created
> >> >> > > on the
> >> >> > > > server easier, I have made changes to our build
> >> scripts
> >> >> and
> >> >> > > tools to try to
> >> >> > > > generate reproducible binaries. I've seen two
> >> >> different builds
> >> >> > > compare on
> >> >> > > > my Mac. The next challenge will be to see if
> >> the
> >> >> server can
> >> >> > > build a
> >> >> > > > package on Windows that will compare on Mac.
> >> >> > > >
> >> >> > > > One of the changes I needed to make is to
> >> JBurg. The
> >> >> version
> >> >> > of
> >> >> > > JBurg we
> >> >> > > > use generates method names including a hash
> that
> >> doesn't
> >> >> > > reproduce the same
> >> >> > > > name each time. I have changes to JBurg ready,
> >> however
> >> >> JBurg
> >> >> > is
> >> >> > > currently
> >> >> > > > under CPL which is category B. We only need
> one
> >> file,
> >> >> we don't
> >> >> > > need or
> >> >> > > > want all of JBurg at this time. The one JBurg
> >> file is
> >> >> jointly
> >> >> > > owned by
> >> >> > > > Adobe and Tom Harwood. I've contact Tom and he
> >> will be
> >> >> filing
> >> >> > > an ICLA and
> >> >> > > > has given me permission to commit the lines he
> >> owns in
> >> >> that one
> >> >> > > file.
> >> >> > > >
> >> >> > > > This is the revision of the file that will be
> >> donated by
> >> >> > > Tom/Adobe.
> >> >> > > >
> >> >> > > >
> >> >> > >
> >> >> >
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=VS1za1vOQhtlKlK4Tdgq3ej04OlhFoYfHziyNbgOIN4%3D&reserved=0
> >> >> > > >
> >> >> > > > Once this file goes in with the changes to keep
> >> the
> >> >> method
> >> >> > names
> >> >> > > the same,
> >> >> > > > there will be more tweaks to the release tasks
> >> and then
> >> >> we can
> >> >> > > try cutting
> >> >> > > > a release. I'm thinking we'll be at that point
> >> in
> >> >> early May,
> >> >> > so
> >> >> > > now is the
> >> >> > > > time to get stuff in for the 0.9.6 release.
> >> >> > > >
> >> >> > > > Thanks,
> >> >> > > > -Alex
> >> >> > > >
> >> >> > > > On 3/8/19, 9:27 AM, "Alex Harui" <
> >> aharui@adobe.com>
> >> >> wrote:
> >> >> > > >
> >> >> > > > I would much rather have others find and
> fix
> >> issues
> >> >> > > themselves. That
> >> >> > > > way, more people than just me will know how to
> >> maintain
> >> >> the
> >> >> > > system. It
> >> >> > > > actually turns out that, IMO, a group of people
> >> can
> >> >> work on the
> >> >> > > release.
> >> >> > > > There are 14 steps. Literally, 14 different
> >> people
> >> >> could
> >> >> > > execute one step
> >> >> > > > each.
> >> >> > > >
> >> >> > > > My 2 cents,
> >> >> > > > -Alex
> >> >> > > >
> >> >> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> >> >> > carlosrovira@apache.org>
> >> >> > > wrote:
> >> >> > > >
> >> >> > > > Hi Alex,
> >> >> > > >
> >> >> > > > amazing work! congrats to reach to this
> >> point!
> >> >> :)
> >> >> > > >
> >> >> > > > I need to put my head on all of this,
> >> but count
> >> >> on me
> >> >> > to
> >> >> > > be a RM.
> >> >> > > > I think
> >> >> > > > the best thing should be that you be
> the
> >> first
> >> >> RM to
> >> >> > try
> >> >> > > your own
> >> >> > > > development at least for the first
> time,
> >> and
> >> >> then the
> >> >> > > rest of us
> >> >> > > > will
> >> >> > > > follow you on the next releases. With
> >> all this
> >> >> on place
> >> >> > > we maybe
> >> >> > > > could
> >> >> > > > release once a month or every two
> >> months...
> >> >> > > >
> >> >> > > > Thanks for doing this :)
> >> >> > > >
> >> >> > > > Carlos
> >> >> > > >
> >> >> > > >
> >> >> > > > El vie., 8 mar. 2019 a las 1:55, Alex
> >> Harui
> >> >> > > > (<ah...@adobe.com.invalid>)
> >> >> > > > escribió:
> >> >> > > >
> >> >> > > > > OK, I've now seen Jenkins perform the
> >> steps
> >> >> to build
> >> >> > > the release
> >> >> > > > > artifacts. Folks interested in
> >> Docker-izing
> >> >> the
> >> >> > steps
> >> >> > > are
> >> >> > > > welcome to look
> >> >> > > > > at the jobs on the "Royale Release"
> >> tab on
> >> >> the CI
> >> >> > > server.
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> >
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=LfWCyCaClCVgfeINn4%2B%2Bk%2FSVUFXvgyV7QxMtx4B%2B%2Fu0%3D&reserved=0
> >> >> > > > >
> >> >> > > > > These steps assume that the RM can
> run
> >> the
> >> >> basic
> >> >> > Maven
> >> >> > > and Ant
> >> >> > > > build on
> >> >> > > > > the RM's computer. I think that's a
> >> fair
> >> >> requirement
> >> >> > > since all
> >> >> > > > of us on the
> >> >> > > > > PMC need to able to do that to build
> >> the RC
> >> >> in order
> >> >> > > to vote on
> >> >> > > > it.
> >> >> > > > > Jenkins does other tasks like run
> the
> >> Maven
> >> >> release
> >> >> > > plugin
> >> >> > > > steps.
> >> >> > > > >
> >> >> > > > > Currently that results in binaries on
> >> Jenkins
> >> >> that
> >> >> > are
> >> >> > > > downloaded to the
> >> >> > > > > RM's computer. These binaries need
> to
> >> be
> >> >> verified by
> >> >> > > the RM
> >> >> > > > which is the
> >> >> > > > > next phase I will be starting on now.
> >> The RM
> >> >> > verifies
> >> >> > > the bits
> >> >> > > > and then
> >> >> > > > > PGP signs them. And then the bits
> are
> >> >> uploaded off
> >> >> > > the RM's
> >> >> > > > computer to
> >> >> > > > > Maven Staging or dist.a.o/dev. If
> >> that
> >> >> uploading
> >> >> > > turns out to
> >> >> > > > be a point
> >> >> > > > > of failure, we have the option of
> >> having
> >> >> Jenkins
> >> >> > > upload the big
> >> >> > > > files and
> >> >> > > > > have the RM only upload PGP signature
> >> files.
> >> >> Or
> >> >> > > finding a way
> >> >> > > > for Jenkins
> >> >> > > > > to get the signature files from the
> >> RM. The
> >> >> uploads
> >> >> > > worked fine
> >> >> > > > for me,
> >> >> > > > > but then again, so did the old
> script's
> >> >> uploads.
> >> >> > > > >
> >> >> > > > > Therefore, once I get the binary
> >> verification
> >> >> phase
> >> >> > > completed, I
> >> >> > > > think
> >> >> > > > > someone other than me should be the
> RM
> >> and
> >> >> try to use
> >> >> > > these
> >> >> > > > steps to
> >> >> > > > > generate the release and help debug
> the
> >> >> process for
> >> >> > > the next
> >> >> > > > RM. So,
> >> >> > > > > please try to carve out some time to
> >> be the
> >> >> RM. One
> >> >> > > advantage
> >> >> > > > of doing
> >> >> > > > > most of the work on Jenkins is that
> it
> >> frees
> >> >> up my
> >> >> > > computer to
> >> >> > > > do other
> >> >> > > > > things while Jenkins is cranking
> away.
> >> >> > > > >
> >> >> > > > > I think we're at least a week away
> >> from binary
> >> >> > > verification,
> >> >> > > > maybe two, so
> >> >> > > > > it is time to start thinking about
> >> what is
> >> >> going in
> >> >> > > this release.
> >> >> > > > >
> >> >> > > > > Thanks,
> >> >> > > > > -Alex
> >> >> > > > >
> >> >> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
> >> >> > > <ah...@adobe.com.INVALID>
> >> >> > > > wrote:
> >> >> > > > >
> >> >> > > > > In case you haven't guessed, I'm
> >> testing
> >> >> out
> >> >> > > Jenkins and its
> >> >> > > > ability
> >> >> > > > > to create the artifacts and send
> >> emails.
> >> >> Please
> >> >> > > ignore any
> >> >> > > > email that
> >> >> > > > > looks like a vote or discuss thread.
> >> >> > > > >
> >> >> > > > > Thanks,
> >> >> > > > > -Alex
> >> >> > > > >
> >> >> > > > > On 2/10/19, 8:44 PM, "Alex Harui"
> >> >> > > <ah...@adobe.com.INVALID>
> >> >> > > > wrote:
> >> >> > > > >
> >> >> > > > > Om,
> >> >> > > > >
> >> >> > > > > Well, that's what I used for
> >> the last
> >> >> > > release. I'm sure
> >> >> > > > there is
> >> >> > > > > probably some inaccuracy in it.
> >> >> > > > >
> >> >> > > > > That said, I'm abandoning
> that
> >> >> document and
> >> >> > > taking a new
> >> >> > > > angle
> >> >> > > > > because that document presumed that
> the
> >> >> release
> >> >> > > manager was
> >> >> > > > trying to
> >> >> > > > > create a release on his/her computer.
> >> I've
> >> >> given up
> >> >> > > on that and
> >> >> > > > working on
> >> >> > > > > making releases from a shared
> computer
> >> for the
> >> >> > reasons
> >> >> > > I've
> >> >> > > > stated
> >> >> > > > > upthread. I hope to make some
> >> progress on
> >> >> that this
> >> >> > > week.
> >> >> > > > >
> >> >> > > > > The key difference is that
> the
> >> new
> >> >> angle does
> >> >> > > not
> >> >> > > > presume that you
> >> >> > > > > have Git SSH and PGP signatures all
> >> set up on
> >> >> some
> >> >> > > computer. I
> >> >> > > > have not
> >> >> > > > > looked into how Docker would handle
> >> that. You
> >> >> > > certainly
> >> >> > > > wouldn't want the
> >> >> > > > > Docker image to contain your SSH or
> PGP
> >> >> keys/creds.
> >> >> > > And if the
> >> >> > > > Docker
> >> >> > > > > image doesn't, then that is another
> >> stumbling
> >> >> block
> >> >> > > for future
> >> >> > > > RMs.
> >> >> > > > >
> >> >> > > > > The other key difference is
> >> that the
> >> >> old
> >> >> > > script presumed
> >> >> > > > you could
> >> >> > > > > create the 3 release in 3 huge "easy"
> >> steps.
> >> >> We've
> >> >> > > seen that is
> >> >> > > > only true
> >> >> > > > > for me. So the new angle creates
> many
> >> >> discrete steps
> >> >> > > managed by
> >> >> > > > Jenkins.
> >> >> > > > >
> >> >> > > > > So, it is up to you to decide
> >> what
> >> >> you want
> >> >> > to
> >> >> > > > "Docker-ize". You
> >> >> > > > > can try to Docker-ize the current 3
> big
> >> >> steps, so RMs
> >> >> > > can try to
> >> >> > > > run it on
> >> >> > > > > their systems, but I'd bet they will
> >> just
> >> >> faiI due to
> >> >> > > network
> >> >> > > > issues. I
> >> >> > > > > would be interested in using Docker
> to
> >> make
> >> >> each of
> >> >> > > these many
> >> >> > > > discrete
> >> >> > > > > steps portable to another server.
> >> I'm not
> >> >> going to
> >> >> > > involve
> >> >> > > > Docker at this
> >> >> > > > > point. My main goal is just to see
> if
> >> I can
> >> >> create a
> >> >> > > workflow
> >> >> > > > of many
> >> >> > > > > discrete steps that isn't horribly
> >> painful.
> >> >> Once we
> >> >> > > see what
> >> >> > > > these steps
> >> >> > > > > turn out to be, then we can worry
> >> about server
> >> >> > > portability of
> >> >> > > > those steps.
> >> >> > > > >
> >> >> > > > > Either way, we want to know
> >> about
> >> >> running
> >> >> > > > Browser+Selenium for
> >> >> > > > > sure. And maybe FlashPlayerDebugger
> >> or AIR.
> >> >> I would
> >> >> > > want to
> >> >> > > > know, for
> >> >> > > > > example, how you debug a failing
> >> checkintest
> >> >> in a
> >> >> > > Docker
> >> >> > > > container.
> >> >> > > > >
> >> >> > > > > Thanks,
> >> >> > > > > -Alex
> >> >> > > > >
> >> >> > > > >
> >> >> > > > > On 2/10/19, 5:18 PM,
> "OmPrakash
> >> >> Muppirala" <
> >> >> > > > bigosmallm@gmail.com>
> >> >> > > > > wrote:
> >> >> > > > >
> >> >> > > > > Alex,
> >> >> > > > >
> >> >> > > > > Just to be clear, I am
> >> following
> >> >> the
> >> >> > steps
> >> >> > > from here
> >> >> > > > to try
> >> >> > > > > and setup a
> >> >> > > > > docker container.
> >> >> > > > >
> >> >> > > > >
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=Lhm0hudN8Nbx%2F6Lnmz0Wlus3EpV1o1h8XWBzBUoEWOA%3D&reserved=0
> >> >> > > > >
> >> >> > > > > Is this doc up to date?
> >> >> > > > >
> >> >> > > > > Thanks,
> >> >> > > > > Om
> >> >> > > > >
> >> >> > > > > On Wed, Feb 6, 2019 at
> >> 12:02 PM
> >> >> OmPrakash
> >> >> > > Muppirala <
> >> >> > > > > bigosmallm@gmail.com>
> >> >> > > > > wrote:
> >> >> > > > >
> >> >> > > > > > One approach is to have
> >> each
> >> >> step in
> >> >> > the
> >> >> > > process
> >> >> > > > spin up a
> >> >> > > > > docker image.
> >> >> > > > > > And use docker-compose
> >> to run
> >> >> each
> >> >> > > step. All the
> >> >> > > > images can
> >> >> > > > > be made to
> >> >> > > > > > share a common volume
> >> where all
> >> >> the
> >> >> > > artifacts are
> >> >> > > > stored
> >> >> > > > > across steps.
> >> >> > > > > >
> >> >> > > > > > You are right about the
> >> >> networking
> >> >> > issue
> >> >> > > though.
> >> >> > > > Any
> >> >> > > > > network related
> >> >> > > > > > failure that occurs on
> >> the host
> >> >> machine
> >> >> > > will most
> >> >> > > > likely
> >> >> > > > > occur in the
> >> >> > > > > > docker container.
> >> Although, I
> >> >> am not
> >> >> > > clear how we
> >> >> > > > can
> >> >> > > > > guarantee that the
> >> >> > > > > > same issues will not
> >> occur on
> >> >> the
> >> >> > > Jenkins server.
> >> >> > > > I mean,
> >> >> > > > > what is special
> >> >> > > > > > about the Jenkins
> server
> >> that
> >> >> makes it
> >> >> > > immune to
> >> >> > > > these
> >> >> > > > > networking issues?
> >> >> > > > > >
> >> >> > > > > > Thanks,
> >> >> > > > > > Om
> >> >> > > > > >
> >> >> > > > > > On Wed, Feb 6, 2019 at
> >> 11:48 AM
> >> >> Alex
> >> >> > > Harui
> >> >> > > > > <ah...@adobe.com.invalid>
> >> >> > > > > > wrote:
> >> >> > > > > >
> >> >> > > > > >> Again, I don't know
> >> anything
> >> >> about
> >> >> > > Docker, but
> >> >> > > > before we
> >> >> > > > > spend a lot of
> >> >> > > > > >> time on Docker, I also
> >> want to
> >> >> point
> >> >> > > out that the
> >> >> > > > process
> >> >> > > > > to create a
> >> >> > > > > >> release cannot really
> be
> >> >> thought of as
> >> >> > > "one
> >> >> > > > application".
> >> >> > > > > It will be a
> >> >> > > > > >> series of "steps" to
> >> run.
> >> >> How many
> >> >> > > steps
> >> >> > > > depends on
> >> >> > > > > whether we think we
> >> >> > > > > >> can isolate enough
> >> stuff via
> >> >> Docker to
> >> >> > > be able to
> >> >> > > > run
> >> >> > > > > Docker on the RM's
> >> >> > > > > >> computer instead of
> >> some shared
> >> >> > > computer. On a
> >> >> > > > shared
> >> >> > > > > computer there will
> >> >> > > > > >> be dozens of steps
> >> because the
> >> >> RM will
> >> >> > > need to
> >> >> > > > enter
> >> >> > > > > passwords to commit
> >> >> > > > > >> stuff. On a local
> >> computer I
> >> >> guess
> >> >> > the
> >> >> > > RM can
> >> >> > > > supply
> >> >> > > > > passwords but I think
> >> >> > > > > >> there will be stopping
> >> points
> >> >> where
> >> >> > the
> >> >> > > Maven
> >> >> > > > artifacts are
> >> >> > > > > deployed and
> >> >> > > > > >> the staging repo is
> >> closed, and
> >> >> > another
> >> >> > > stopping
> >> >> > > > point for
> >> >> > > > > the vote. It
> >> >> > > > > >> seems like Docker
> works
> >> by
> >> >> downloading
> >> >> > > > dependencies. Given
> >> >> > > > > that the
> >> >> > > > > >> problem the RMs had
> >> last time
> >> >> involved
> >> >> > > downloads
> >> >> > > > and
> >> >> > > > > uploads, why do we
> >> >> > > > > >> think Docker will
> >> really solve
> >> >> this
> >> >> > for
> >> >> > > creating
> >> >> > > > releases
> >> >> > > > > on local machines?
> >> >> > > > > >>
> >> >> > > > > >> The reason to do this
> >> on a
> >> >> shared
> >> >> > > machine is so
> >> >> > > > that new
> >> >> > > > > RMs don't have
> >> >> > > > > >> to do as much setup.
> >> But then
> >> >> I
> >> >> > wonder
> >> >> > > about the
> >> >> > > > > efficiency of kicking off
> >> >> > > > > >> that many Docker
> images.
> >> >> Jenkins can
> >> >> > > manage that
> >> >> > > > already.
> >> >> > > > > Does Docker
> >> >> > > > > >> have some sort of
> >> similar
> >> >> Dashboard or
> >> >> > > would we
> >> >> > > > use Jenkins
> >> >> > > > > to kick off
> >> >> > > > > >> Docker steps? I can't
> >> quite
> >> >> picture
> >> >> > > what is the
> >> >> > > > outermost
> >> >> > > > > >> control/dashboard.
> >> >> > > > > >>
> >> >> > > > > >> -Alex
> >> >> > > > > >>
> >> >> > > > > >> On 2/6/19, 11:03 AM,
> >> "Harbs" <
> >> >> > > > harbs.lists@gmail.com> wrote:
> >> >> > > > > >>
> >> >> > > > > >> A quick search
> >> turns up
> >> >> this:
> >> >> > > > > >>
> >> >> > > > > >>
> >> >> > > > > >>
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
> >> >> > > > > >> <
> >> >> > > > > >>
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
> >> >> > > > > >> >
> >> >> > > > > >>
> >> >> > > > > >>
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=YPCe61GnfpckdNdqMRCDAHXsd3dvMHT3BO157C%2Fufs4%3D&reserved=0
> >> >> > > > > >> <
> >> >> > > > > >>
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=YPCe61GnfpckdNdqMRCDAHXsd3dvMHT3BO157C%2Fufs4%3D&reserved=0
> >> >> > > > > >> >
> >> >> > > > > >>
> >> >> > > > > >>
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=lsUmIIjQQi5CZhXTvQgd7lPt%2BVL2ApXFbK7i0NbMk1k%3D&reserved=0
> >> >> > > > > >> <
> >> >> > > > > >>
> >> >> > > > >
> >> >> > > >
> >> >> > >
> >> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=lsUmIIjQQi5CZhXTvQgd7lPt%2BVL2ApXFbK7i0NbMk1k%3D&reserved=0
> >> >> > > > > >> >
> >> >> > > > > >>
> >> >> > > > > >> > On Feb 6, 2019,
> >> at 8:59
> >> >> PM, Alex
> >> >> > > Harui
> >> >> > > > > <ah...@adobe.com.INVALID>
> >> >> > > > > >> wrote:
> >> >> > > > > >> >
> >> >> > > > > >> > Thanks for
> >> volunteering
> >> >> to try
> >> >> > it
> >> >> > > Om. IMO,
> >> >> > > > even more
> >> >> > > > > important
> >> >> > > > > >> than Firefox+Flash is
> >> >> > > SomeBrowser+Selenium. We
> >> >> > > > may also
> >> >> > > > > need to run Adobe
> >> >> > > > > >> AIR's adb. We could
> >> probably
> >> >> turn off
> >> >> > > the Flash
> >> >> > > > tests or
> >> >> > > > > replace Flash
> >> >> > > > > >> with AIR.
> >> >> > > > > >> >
> >> >> > > > > >> > Thanks,
> >> >> > > > > >> > -Alex
> >> >> > > > > >> >
> >> >> > > > > >> > On 2/6/19, 10:54
> >> AM,
> >> >> "Carlos
> >> >> > > Rovira" <
> >> >> > > > > carlosrovira@apache.org>
> >> >> > > > > >> wrote:
> >> >> > > > > >> >
> >> >> > > > > >> > Hi Om, that
> >> would be
> >> >> great!
> >> >> > > waiting for
> >> >> > > > your
> >> >> > > > > experience with a
> >> >> > > > > >> that! :)
> >> >> > > > > >> >
> >> >> > > > > >> > El mié., 6
> >> feb. 2019
> >> >> a las
> >> >> > > 19:31,
> >> >> > > > OmPrakash
> >> >> > > > > Muppirala (<
> >> >> > > > > >> bigosmallm@gmail.com
> >)
> >> >> > > > > >> >
Re: 0.9.6 Release
Posted by Greg Dove <gr...@gmail.com>.
I will stick with the plan of single commit, I think it should be easier
for you if there are any conflicts.
Last build testing is running now in local develop. I will push after
that...
On Tue, Jun 11, 2019 at 3:15 PM Greg Dove <gr...@gmail.com> wrote:
>
> Thanks Alex, I was planning to merge this as a single squashed commit,
> because it isolates all the changes to a single commit (but this will mean
> there are many changes in one hit).
> Do you have a preference in terms of how easy it will make things for you?
>
>
> On Tue, Jun 11, 2019 at 3:07 PM Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
>> OK, I will wait to see your commit emails. I will do some other things
>> like the wiki doc.
>>
>> -Alex
>>
>> On 6/10/19, 8:06 PM, "Greg Dove" <gr...@gmail.com> wrote:
>>
>> Hi Alex, I guess you might be back on Royale about now. Just a heads
>> up: I
>> am about 20-30 mins max from merging in what I have. Hope that's still
>> ok... please let me know if not.
>> Thanks,
>> -Greg
>>
>>
>> On Tue, Jun 11, 2019 at 7:51 AM Greg Dove <gr...@gmail.com>
>> wrote:
>>
>> >
>> > Thanks Alex - I'll try to hit the window, much appreciated!
>> >
>> >
>> > On Tue, Jun 11, 2019 at 6:57 AM Alex Harui <aharui@adobe.com.invalid
>> >
>> > wrote:
>> >
>> >> Hi Greg,
>> >>
>> >> It turns out I have a "split shift" today. I'm stopping work for
>> the
>> >> next 7 or 8 hours then will get around to the merge. So if you
>> can get
>> >> your changes merged in that amount of time, then I will wait for
>> you and
>> >> deal with any merge conflicts (there are almost certain to be
>> some).
>> >>
>> >> -Alex
>> >>
>> >> On 6/10/19, 11:46 AM, "Greg Dove" <gr...@gmail.com> wrote:
>> >>
>> >> Alex, slightly OT, but in terms of coordination: fyi I am also
>> very
>> >> close
>> >> to merging the language improvements branch into develop. As I
>> already
>> >> mentioned elsewhere, I was hoping to do that a couple of days
>> back,
>> >> but
>> >> some recent things also took me a little longer than expected
>> (I have
>> >> additional local changes/fixes not yet in remote branch) . I
>> was
>> >> planning
>> >> to merge that today also.
>> >>
>> >> However, I will wait until after your merge, so I'm hoping you
>> can get
>> >> yours in today (if not, I will wait). I will probably put mine
>> in as a
>> >> squashed commit after yours.
>> >>
>> >>
>> >> On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <
>> >> piotrzarzycki21@gmail.com>
>> >> wrote:
>> >>
>> >> > Hi Alex,
>> >> >
>> >> > Many thanks for that! I will try to be RM. I will have some
>> >> dedicated time
>> >> > for that. I will wait for your instruction and merge to
>> develop.
>> >> >
>> >> > Thanks,
>> >> > Piotr
>> >> >
>> >> >
>> >> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
>> <ah...@adobe.com.invalid>
>> >> wrote:
>> >> >
>> >> > > Well, that turned out to be much more time-consuming than I
>> >> expected, but
>> >> > > we can now create identical release artifacts on Mac and
>> Win. I
>> >> am
>> >> > hopeful
>> >> > > this effort will pay off not only now in having other folks
>> >> generate
>> >> > > releases, but also in the future if signed binaries become
>> a
>> >> requirement.
>> >> > >
>> >> > > There continues to be a lot of distractions in my life
>> that can
>> >> cause
>> >> > > delays, but I hope to merge the release_practice branches
>> into
>> >> develop
>> >> > over
>> >> > > the next day or two and figure out where in the wiki to
>> document
>> >> the
>> >> > > release process. So, now is the time for one or more
>> people to
>> >> step up
>> >> > to
>> >> > > be the RMs for 0.9.6 and help debug and improve the
>> process.
>> >> > >
>> >> > > I am going to try very hard not to "own" the process. If
>> >> something goes
>> >> > > wrong, I am going to ask others to try to debug and fix it
>> first
>> >> because
>> >> > it
>> >> > > is in the project's best interests for others to truly
>> understand
>> >> how
>> >> > this
>> >> > > stuff works.
>> >> > >
>> >> > > Thanks,
>> >> > > -Alex
>> >> > >
>> >> > > On 5/23/19, 9:54 AM, "Alex Harui" <aharui@adobe.com.INVALID
>> >
>> >> wrote:
>> >> > >
>> >> > > It has turned out to be harder than expected to get
>> the same
>> >> binaries
>> >> > > on Mac and Win. I now have the identical binaries for
>> >> royale-compiler
>> >> > and
>> >> > > royale-typedefs Maven artifacts and am starting on
>> royale-asjs.
>> >> I might
>> >> > > get lucky and the changes that fixed royale-typedefs SWCs
>> will
>> >> magically
>> >> > > get the royale-asjs SWCs to match. Then we have to make
>> the Ant
>> >> > artifacts
>> >> > > match.
>> >> > >
>> >> > > There have been a lot of distractions in my non-work
>> life
>> >> which has
>> >> > > also impeded progress. I hope to make much progress this
>> coming
>> >> week and
>> >> > > if we're lucky, I will be asking for a volunteer (or
>> volunteers)
>> >> to test
>> >> > > drive all of this stuff and be the RM for 0.9.6. I am not
>> going
>> >> to be
>> >> > the
>> >> > > RM.
>> >> > >
>> >> > > -Alex
>> >> > >
>> >> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
>> >> piotrzarzycki21@gmail.com>
>> >> > > wrote:
>> >> > >
>> >> > > Hi Alex,
>> >> > >
>> >> > > It's been a while since you have started effort
>> with
>> >> automating
>> >> > > build.
>> >> > > Where are you with that ? Are we closer to started
>> 0.9.6.
>> >> Do you
>> >> > > need any
>> >> > > help with this ?
>> >> > >
>> >> > > Thanks,
>> >> > > Piotr
>> >> > >
>> >> > > wt., 2 kwi 2019 o 19:30 Alex Harui
>> >> <ah...@adobe.com.invalid>
>> >> > > napisał(a):
>> >> > >
>> >> > > > Update:
>> >> > > >
>> >> > > > In order to make verification of binary release
>> packages
>> >> > created
>> >> > > on the
>> >> > > > server easier, I have made changes to our build
>> scripts
>> >> and
>> >> > > tools to try to
>> >> > > > generate reproducible binaries. I've seen two
>> >> different builds
>> >> > > compare on
>> >> > > > my Mac. The next challenge will be to see if
>> the
>> >> server can
>> >> > > build a
>> >> > > > package on Windows that will compare on Mac.
>> >> > > >
>> >> > > > One of the changes I needed to make is to
>> JBurg. The
>> >> version
>> >> > of
>> >> > > JBurg we
>> >> > > > use generates method names including a hash that
>> doesn't
>> >> > > reproduce the same
>> >> > > > name each time. I have changes to JBurg ready,
>> however
>> >> JBurg
>> >> > is
>> >> > > currently
>> >> > > > under CPL which is category B. We only need one
>> file,
>> >> we don't
>> >> > > need or
>> >> > > > want all of JBurg at this time. The one JBurg
>> file is
>> >> jointly
>> >> > > owned by
>> >> > > > Adobe and Tom Harwood. I've contact Tom and he
>> will be
>> >> filing
>> >> > > an ICLA and
>> >> > > > has given me permission to commit the lines he
>> owns in
>> >> that one
>> >> > > file.
>> >> > > >
>> >> > > > This is the revision of the file that will be
>> donated by
>> >> > > Tom/Adobe.
>> >> > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=VS1za1vOQhtlKlK4Tdgq3ej04OlhFoYfHziyNbgOIN4%3D&reserved=0
>> >> > > >
>> >> > > > Once this file goes in with the changes to keep
>> the
>> >> method
>> >> > names
>> >> > > the same,
>> >> > > > there will be more tweaks to the release tasks
>> and then
>> >> we can
>> >> > > try cutting
>> >> > > > a release. I'm thinking we'll be at that point
>> in
>> >> early May,
>> >> > so
>> >> > > now is the
>> >> > > > time to get stuff in for the 0.9.6 release.
>> >> > > >
>> >> > > > Thanks,
>> >> > > > -Alex
>> >> > > >
>> >> > > > On 3/8/19, 9:27 AM, "Alex Harui" <
>> aharui@adobe.com>
>> >> wrote:
>> >> > > >
>> >> > > > I would much rather have others find and fix
>> issues
>> >> > > themselves. That
>> >> > > > way, more people than just me will know how to
>> maintain
>> >> the
>> >> > > system. It
>> >> > > > actually turns out that, IMO, a group of people
>> can
>> >> work on the
>> >> > > release.
>> >> > > > There are 14 steps. Literally, 14 different
>> people
>> >> could
>> >> > > execute one step
>> >> > > > each.
>> >> > > >
>> >> > > > My 2 cents,
>> >> > > > -Alex
>> >> > > >
>> >> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
>> >> > carlosrovira@apache.org>
>> >> > > wrote:
>> >> > > >
>> >> > > > Hi Alex,
>> >> > > >
>> >> > > > amazing work! congrats to reach to this
>> point!
>> >> :)
>> >> > > >
>> >> > > > I need to put my head on all of this,
>> but count
>> >> on me
>> >> > to
>> >> > > be a RM.
>> >> > > > I think
>> >> > > > the best thing should be that you be the
>> first
>> >> RM to
>> >> > try
>> >> > > your own
>> >> > > > development at least for the first time,
>> and
>> >> then the
>> >> > > rest of us
>> >> > > > will
>> >> > > > follow you on the next releases. With
>> all this
>> >> on place
>> >> > > we maybe
>> >> > > > could
>> >> > > > release once a month or every two
>> months...
>> >> > > >
>> >> > > > Thanks for doing this :)
>> >> > > >
>> >> > > > Carlos
>> >> > > >
>> >> > > >
>> >> > > > El vie., 8 mar. 2019 a las 1:55, Alex
>> Harui
>> >> > > > (<ah...@adobe.com.invalid>)
>> >> > > > escribió:
>> >> > > >
>> >> > > > > OK, I've now seen Jenkins perform the
>> steps
>> >> to build
>> >> > > the release
>> >> > > > > artifacts. Folks interested in
>> Docker-izing
>> >> the
>> >> > steps
>> >> > > are
>> >> > > > welcome to look
>> >> > > > > at the jobs on the "Royale Release"
>> tab on
>> >> the CI
>> >> > > server.
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=LfWCyCaClCVgfeINn4%2B%2Bk%2FSVUFXvgyV7QxMtx4B%2B%2Fu0%3D&reserved=0
>> >> > > > >
>> >> > > > > These steps assume that the RM can run
>> the
>> >> basic
>> >> > Maven
>> >> > > and Ant
>> >> > > > build on
>> >> > > > > the RM's computer. I think that's a
>> fair
>> >> requirement
>> >> > > since all
>> >> > > > of us on the
>> >> > > > > PMC need to able to do that to build
>> the RC
>> >> in order
>> >> > > to vote on
>> >> > > > it.
>> >> > > > > Jenkins does other tasks like run the
>> Maven
>> >> release
>> >> > > plugin
>> >> > > > steps.
>> >> > > > >
>> >> > > > > Currently that results in binaries on
>> Jenkins
>> >> that
>> >> > are
>> >> > > > downloaded to the
>> >> > > > > RM's computer. These binaries need to
>> be
>> >> verified by
>> >> > > the RM
>> >> > > > which is the
>> >> > > > > next phase I will be starting on now.
>> The RM
>> >> > verifies
>> >> > > the bits
>> >> > > > and then
>> >> > > > > PGP signs them. And then the bits are
>> >> uploaded off
>> >> > > the RM's
>> >> > > > computer to
>> >> > > > > Maven Staging or dist.a.o/dev. If
>> that
>> >> uploading
>> >> > > turns out to
>> >> > > > be a point
>> >> > > > > of failure, we have the option of
>> having
>> >> Jenkins
>> >> > > upload the big
>> >> > > > files and
>> >> > > > > have the RM only upload PGP signature
>> files.
>> >> Or
>> >> > > finding a way
>> >> > > > for Jenkins
>> >> > > > > to get the signature files from the
>> RM. The
>> >> uploads
>> >> > > worked fine
>> >> > > > for me,
>> >> > > > > but then again, so did the old script's
>> >> uploads.
>> >> > > > >
>> >> > > > > Therefore, once I get the binary
>> verification
>> >> phase
>> >> > > completed, I
>> >> > > > think
>> >> > > > > someone other than me should be the RM
>> and
>> >> try to use
>> >> > > these
>> >> > > > steps to
>> >> > > > > generate the release and help debug the
>> >> process for
>> >> > > the next
>> >> > > > RM. So,
>> >> > > > > please try to carve out some time to
>> be the
>> >> RM. One
>> >> > > advantage
>> >> > > > of doing
>> >> > > > > most of the work on Jenkins is that it
>> frees
>> >> up my
>> >> > > computer to
>> >> > > > do other
>> >> > > > > things while Jenkins is cranking away.
>> >> > > > >
>> >> > > > > I think we're at least a week away
>> from binary
>> >> > > verification,
>> >> > > > maybe two, so
>> >> > > > > it is time to start thinking about
>> what is
>> >> going in
>> >> > > this release.
>> >> > > > >
>> >> > > > > Thanks,
>> >> > > > > -Alex
>> >> > > > >
>> >> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
>> >> > > <ah...@adobe.com.INVALID>
>> >> > > > wrote:
>> >> > > > >
>> >> > > > > In case you haven't guessed, I'm
>> testing
>> >> out
>> >> > > Jenkins and its
>> >> > > > ability
>> >> > > > > to create the artifacts and send
>> emails.
>> >> Please
>> >> > > ignore any
>> >> > > > email that
>> >> > > > > looks like a vote or discuss thread.
>> >> > > > >
>> >> > > > > Thanks,
>> >> > > > > -Alex
>> >> > > > >
>> >> > > > > On 2/10/19, 8:44 PM, "Alex Harui"
>> >> > > <ah...@adobe.com.INVALID>
>> >> > > > wrote:
>> >> > > > >
>> >> > > > > Om,
>> >> > > > >
>> >> > > > > Well, that's what I used for
>> the last
>> >> > > release. I'm sure
>> >> > > > there is
>> >> > > > > probably some inaccuracy in it.
>> >> > > > >
>> >> > > > > That said, I'm abandoning that
>> >> document and
>> >> > > taking a new
>> >> > > > angle
>> >> > > > > because that document presumed that the
>> >> release
>> >> > > manager was
>> >> > > > trying to
>> >> > > > > create a release on his/her computer.
>> I've
>> >> given up
>> >> > > on that and
>> >> > > > working on
>> >> > > > > making releases from a shared computer
>> for the
>> >> > reasons
>> >> > > I've
>> >> > > > stated
>> >> > > > > upthread. I hope to make some
>> progress on
>> >> that this
>> >> > > week.
>> >> > > > >
>> >> > > > > The key difference is that the
>> new
>> >> angle does
>> >> > > not
>> >> > > > presume that you
>> >> > > > > have Git SSH and PGP signatures all
>> set up on
>> >> some
>> >> > > computer. I
>> >> > > > have not
>> >> > > > > looked into how Docker would handle
>> that. You
>> >> > > certainly
>> >> > > > wouldn't want the
>> >> > > > > Docker image to contain your SSH or PGP
>> >> keys/creds.
>> >> > > And if the
>> >> > > > Docker
>> >> > > > > image doesn't, then that is another
>> stumbling
>> >> block
>> >> > > for future
>> >> > > > RMs.
>> >> > > > >
>> >> > > > > The other key difference is
>> that the
>> >> old
>> >> > > script presumed
>> >> > > > you could
>> >> > > > > create the 3 release in 3 huge "easy"
>> steps.
>> >> We've
>> >> > > seen that is
>> >> > > > only true
>> >> > > > > for me. So the new angle creates many
>> >> discrete steps
>> >> > > managed by
>> >> > > > Jenkins.
>> >> > > > >
>> >> > > > > So, it is up to you to decide
>> what
>> >> you want
>> >> > to
>> >> > > > "Docker-ize". You
>> >> > > > > can try to Docker-ize the current 3 big
>> >> steps, so RMs
>> >> > > can try to
>> >> > > > run it on
>> >> > > > > their systems, but I'd bet they will
>> just
>> >> faiI due to
>> >> > > network
>> >> > > > issues. I
>> >> > > > > would be interested in using Docker to
>> make
>> >> each of
>> >> > > these many
>> >> > > > discrete
>> >> > > > > steps portable to another server.
>> I'm not
>> >> going to
>> >> > > involve
>> >> > > > Docker at this
>> >> > > > > point. My main goal is just to see if
>> I can
>> >> create a
>> >> > > workflow
>> >> > > > of many
>> >> > > > > discrete steps that isn't horribly
>> painful.
>> >> Once we
>> >> > > see what
>> >> > > > these steps
>> >> > > > > turn out to be, then we can worry
>> about server
>> >> > > portability of
>> >> > > > those steps.
>> >> > > > >
>> >> > > > > Either way, we want to know
>> about
>> >> running
>> >> > > > Browser+Selenium for
>> >> > > > > sure. And maybe FlashPlayerDebugger
>> or AIR.
>> >> I would
>> >> > > want to
>> >> > > > know, for
>> >> > > > > example, how you debug a failing
>> checkintest
>> >> in a
>> >> > > Docker
>> >> > > > container.
>> >> > > > >
>> >> > > > > Thanks,
>> >> > > > > -Alex
>> >> > > > >
>> >> > > > >
>> >> > > > > On 2/10/19, 5:18 PM, "OmPrakash
>> >> Muppirala" <
>> >> > > > bigosmallm@gmail.com>
>> >> > > > > wrote:
>> >> > > > >
>> >> > > > > Alex,
>> >> > > > >
>> >> > > > > Just to be clear, I am
>> following
>> >> the
>> >> > steps
>> >> > > from here
>> >> > > > to try
>> >> > > > > and setup a
>> >> > > > > docker container.
>> >> > > > >
>> >> > > > >
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=Lhm0hudN8Nbx%2F6Lnmz0Wlus3EpV1o1h8XWBzBUoEWOA%3D&reserved=0
>> >> > > > >
>> >> > > > > Is this doc up to date?
>> >> > > > >
>> >> > > > > Thanks,
>> >> > > > > Om
>> >> > > > >
>> >> > > > > On Wed, Feb 6, 2019 at
>> 12:02 PM
>> >> OmPrakash
>> >> > > Muppirala <
>> >> > > > > bigosmallm@gmail.com>
>> >> > > > > wrote:
>> >> > > > >
>> >> > > > > > One approach is to have
>> each
>> >> step in
>> >> > the
>> >> > > process
>> >> > > > spin up a
>> >> > > > > docker image.
>> >> > > > > > And use docker-compose
>> to run
>> >> each
>> >> > > step. All the
>> >> > > > images can
>> >> > > > > be made to
>> >> > > > > > share a common volume
>> where all
>> >> the
>> >> > > artifacts are
>> >> > > > stored
>> >> > > > > across steps.
>> >> > > > > >
>> >> > > > > > You are right about the
>> >> networking
>> >> > issue
>> >> > > though.
>> >> > > > Any
>> >> > > > > network related
>> >> > > > > > failure that occurs on
>> the host
>> >> machine
>> >> > > will most
>> >> > > > likely
>> >> > > > > occur in the
>> >> > > > > > docker container.
>> Although, I
>> >> am not
>> >> > > clear how we
>> >> > > > can
>> >> > > > > guarantee that the
>> >> > > > > > same issues will not
>> occur on
>> >> the
>> >> > > Jenkins server.
>> >> > > > I mean,
>> >> > > > > what is special
>> >> > > > > > about the Jenkins server
>> that
>> >> makes it
>> >> > > immune to
>> >> > > > these
>> >> > > > > networking issues?
>> >> > > > > >
>> >> > > > > > Thanks,
>> >> > > > > > Om
>> >> > > > > >
>> >> > > > > > On Wed, Feb 6, 2019 at
>> 11:48 AM
>> >> Alex
>> >> > > Harui
>> >> > > > > <ah...@adobe.com.invalid>
>> >> > > > > > wrote:
>> >> > > > > >
>> >> > > > > >> Again, I don't know
>> anything
>> >> about
>> >> > > Docker, but
>> >> > > > before we
>> >> > > > > spend a lot of
>> >> > > > > >> time on Docker, I also
>> want to
>> >> point
>> >> > > out that the
>> >> > > > process
>> >> > > > > to create a
>> >> > > > > >> release cannot really be
>> >> thought of as
>> >> > > "one
>> >> > > > application".
>> >> > > > > It will be a
>> >> > > > > >> series of "steps" to
>> run.
>> >> How many
>> >> > > steps
>> >> > > > depends on
>> >> > > > > whether we think we
>> >> > > > > >> can isolate enough
>> stuff via
>> >> Docker to
>> >> > > be able to
>> >> > > > run
>> >> > > > > Docker on the RM's
>> >> > > > > >> computer instead of
>> some shared
>> >> > > computer. On a
>> >> > > > shared
>> >> > > > > computer there will
>> >> > > > > >> be dozens of steps
>> because the
>> >> RM will
>> >> > > need to
>> >> > > > enter
>> >> > > > > passwords to commit
>> >> > > > > >> stuff. On a local
>> computer I
>> >> guess
>> >> > the
>> >> > > RM can
>> >> > > > supply
>> >> > > > > passwords but I think
>> >> > > > > >> there will be stopping
>> points
>> >> where
>> >> > the
>> >> > > Maven
>> >> > > > artifacts are
>> >> > > > > deployed and
>> >> > > > > >> the staging repo is
>> closed, and
>> >> > another
>> >> > > stopping
>> >> > > > point for
>> >> > > > > the vote. It
>> >> > > > > >> seems like Docker works
>> by
>> >> downloading
>> >> > > > dependencies. Given
>> >> > > > > that the
>> >> > > > > >> problem the RMs had
>> last time
>> >> involved
>> >> > > downloads
>> >> > > > and
>> >> > > > > uploads, why do we
>> >> > > > > >> think Docker will
>> really solve
>> >> this
>> >> > for
>> >> > > creating
>> >> > > > releases
>> >> > > > > on local machines?
>> >> > > > > >>
>> >> > > > > >> The reason to do this
>> on a
>> >> shared
>> >> > > machine is so
>> >> > > > that new
>> >> > > > > RMs don't have
>> >> > > > > >> to do as much setup.
>> But then
>> >> I
>> >> > wonder
>> >> > > about the
>> >> > > > > efficiency of kicking off
>> >> > > > > >> that many Docker images.
>> >> Jenkins can
>> >> > > manage that
>> >> > > > already.
>> >> > > > > Does Docker
>> >> > > > > >> have some sort of
>> similar
>> >> Dashboard or
>> >> > > would we
>> >> > > > use Jenkins
>> >> > > > > to kick off
>> >> > > > > >> Docker steps? I can't
>> quite
>> >> picture
>> >> > > what is the
>> >> > > > outermost
>> >> > > > > >> control/dashboard.
>> >> > > > > >>
>> >> > > > > >> -Alex
>> >> > > > > >>
>> >> > > > > >> On 2/6/19, 11:03 AM,
>> "Harbs" <
>> >> > > > harbs.lists@gmail.com> wrote:
>> >> > > > > >>
>> >> > > > > >> A quick search
>> turns up
>> >> this:
>> >> > > > > >>
>> >> > > > > >>
>> >> > > > > >>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
>> >> > > > > >> <
>> >> > > > > >>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
>> >> > > > > >> >
>> >> > > > > >>
>> >> > > > > >>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=YPCe61GnfpckdNdqMRCDAHXsd3dvMHT3BO157C%2Fufs4%3D&reserved=0
>> >> > > > > >> <
>> >> > > > > >>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=YPCe61GnfpckdNdqMRCDAHXsd3dvMHT3BO157C%2Fufs4%3D&reserved=0
>> >> > > > > >> >
>> >> > > > > >>
>> >> > > > > >>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=lsUmIIjQQi5CZhXTvQgd7lPt%2BVL2ApXFbK7i0NbMk1k%3D&reserved=0
>> >> > > > > >> <
>> >> > > > > >>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=lsUmIIjQQi5CZhXTvQgd7lPt%2BVL2ApXFbK7i0NbMk1k%3D&reserved=0
>> >> > > > > >> >
>> >> > > > > >>
>> >> > > > > >> > On Feb 6, 2019,
>> at 8:59
>> >> PM, Alex
>> >> > > Harui
>> >> > > > > <ah...@adobe.com.INVALID>
>> >> > > > > >> wrote:
>> >> > > > > >> >
>> >> > > > > >> > Thanks for
>> volunteering
>> >> to try
>> >> > it
>> >> > > Om. IMO,
>> >> > > > even more
>> >> > > > > important
>> >> > > > > >> than Firefox+Flash is
>> >> > > SomeBrowser+Selenium. We
>> >> > > > may also
>> >> > > > > need to run Adobe
>> >> > > > > >> AIR's adb. We could
>> probably
>> >> turn off
>> >> > > the Flash
>> >> > > > tests or
>> >> > > > > replace Flash
>> >> > > > > >> with AIR.
>> >> > > > > >> >
>> >> > > > > >> > Thanks,
>> >> > > > > >> > -Alex
>> >> > > > > >> >
>> >> > > > > >> > On 2/6/19, 10:54
>> AM,
>> >> "Carlos
>> >> > > Rovira" <
>> >> > > > > carlosrovira@apache.org>
>> >> > > > > >> wrote:
>> >> > > > > >> >
>> >> > > > > >> > Hi Om, that
>> would be
>> >> great!
>> >> > > waiting for
>> >> > > > your
>> >> > > > > experience with a
>> >> > > > > >> that! :)
>> >> > > > > >> >
>> >> > > > > >> > El mié., 6
>> feb. 2019
>> >> a las
>> >> > > 19:31,
>> >> > > > OmPrakash
>> >> > > > > Muppirala (<
>> >> > > > > >> bigosmallm@gmail.com>)
>> >> > > > > >> > escribió:
>> >> > > > > >> >
>> >> > > > > >> >> Yes, I agree
>> with Alex
>> >> about
>> >> > not
>> >> > > being
>> >> > > > able to run
>> >> > > > > UI out of docker
>> >> > > > > >> >> containers. I
>> never
>> >> thought of
>> >> > > the
>> >> > > > checkintests
>> >> > > > > when I made the
>> >> > > > > >> >> suggestion.
>> >> > > > > >> >>
>> >> > > > > >> >> The
>> firefox-flash image
>> >> that
>> >> > > Yishay
>> >> > > > pointed out
>> >> > > > > looks promising.
>> >> > > > > >> I will
>> >> > > > > >> >> poke around with
>> it and
>> >> see if
>> >> > > that works
>> >> > > > for us.
>> >> > > > > >> >>
>> >> > > > > >> >> Thanks,
>> >> > > > > >> >> Om
>> >> > > > > >> >>
>> >> > > > > >> >> On Wed, Feb 6,
>> 2019 at
>> >> 12:41 AM
>> >> > > Yishay
>> >> > > > Weiss <
>> >> > > > > >> yishayjobs@hotmail.com>
>> >> > > > > >> >> wrote:
>> >> > > > > >> >>
>> >> > > > > >> >>> I’ll let Om or
>> someone
>> >> else
>> >> > > with docker
>> >> > > > experience
>> >> > > > > tell us if
>> >> > > > > >> this [1] is
>> >> > > > > >> >>> relevant.
>> >> > > > > >> >>>
>> >> > > > > >> >>>
>> >> > > > > >> >>>
>> >> > > > > >> >>> [1]
>> >> > > > > >>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=L6e5%2FCo%2BOzdzvR3QxWvKa7Yg%2BkTw00Afeq24%2B11PGeU%3D&reserved=0
>> >> > > > > >> >>>
>> >> > > > > >> >>>
>> >> > > > > >> >>>
>> >> > > > > >> >>>
>> >> > ________________________________
>> >> > > > > >> >>> From: Alex Harui
>> >> > > <aharui@adobe.com.INVALID
>> >> > > > >
>> >> > > > > >> >>> Sent: Wednesday,
>> >> February 6,
>> >> > > 2019
>> >> > > > 10:05:54 AM
>> >> > > > > >> >>> To:
>> >> dev@royale.apache.org
>> >> > > > > >> >>> Subject: Re:
>> 0.9.6
>> >> Release
>> >> > > > > >> >>>
>> >> > > > > >> >>> I don't
>> anything about
>> >> docker,
>> >> > > but in 15
>> >> > > > minutes of
>> >> > > > > reading I ran
>> >> > > > > >> into
>> >> > > > > >> >>> this:
>> >> > > > > >> >>>
>> >> > > > > >> >>>
>> >> > > > > >> >>
>> >> > > > > >>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=TLSgOkYEaTxxr%2B7TlB%2BOJVt68S2pOH%2FVOAUDtvFYWWE%3D&reserved=0
>> >> > > > > >> >>>
>> >> > > > > >> >>> Which says:
>> Docker
>> >> can't " Run
>> >> > > > applications with
>> >> > > > > graphical
>> >> > > > > >> interfaces".
>> >> > > > > >> >>> If you want
>> Royale to
>> >> use
>> >> > > Docker for
>> >> > > > releases, show
>> >> > > > > that it can
>> >> > > > > >> run
>> >> > > > > >> >>> checkintests
>> with
>> >> Flash and
>> >> > the
>> >> > > Browser.
>> >> > > > Then I
>> >> > > > > will look into
>> >> > > > > >> it more.
>> >> > > > > >> >>>
>> >> > > > > >> >>> The highest
>> level goal
>> >> is to
>> >> > > make it as
>> >> > > > easy as
>> >> > > > > possible for
>> >> > > > > >> someone to
>> >> > > > > >> >>> volunteer to be
>> an
>> >> RM. Any
>> >> > > requirement
>> >> > > > of "install
>> >> > > > > this (Docker,
>> >> > > > > >> etc) on
>> >> > > > > >> >>> your computer"
>> is, IMO,
>> >> > another
>> >> > > barrier
>> >> > > > to entry.
>> >> > > > > Yeah, RMs will
>> >> > > > > >> have to
>> >> > > > > >> >>> have Maven
>> installed
>> >> and maybe
>> >> > > Ant, but
>> >> > > > you should
>> >> > > > > already have
>> >> > > > > >> those
>> >> > > > > >> >>> installed to be
>> a
>> >> > committer/PMC
>> >> > > member.
>> >> > > > > >> >>>
>> >> > > > > >> >>> That said, a
>> good
>> >> takeaway
>> >> > from
>> >> > > the
>> >> > > > Docker idea is
>> >> > > > > to try to find
>> >> > > > > >> a way
>> >> > > > > >> >> to
>> >> > > > > >> >>> make an "Image"
>> of
>> >> whatever we
>> >> > > end up
>> >> > > > with on
>> >> > > > > whatever server we
>> >> > > > > >> end up
>> >> > > > > >> >>> using so if the
>> image
>> >> can be
>> >> > > copied and
>> >> > > > used on
>> >> > > > > other servers.
>> >> > > > > >> I'm not
>> >> > > > > >> >>> exactly sure
>> how to do
>> >> that
>> >> > > with Azure,
>> >> > > > which hosts
>> >> > > > > my CI
>> >> > > > > >> server. I will
>> >> > > > > >> >>> spend a few more
>> >> minutes
>> >> > > researching that.
>> >> > > > > >> >>>
>> >> > > > > >> >>> I could not
>> quickly
>> >> find any
>> >> > > way to get a
>> >> > > > free VM
>> >> > > > > on Azure or AWS
>> >> > > > > >> that
>> >> > > > > >> >>> isn't a
>> >> > > > free-trial-start-paying-after-a-year. So,
>> >> > > > > unless someone
>> >> > > > > >> comes
>> >> > > > > >> >> up
>> >> > > > > >> >>> with a free
>> server we
>> >> can use
>> >> > > "forever",
>> >> > > > I'm going
>> >> > > > > to just start
>> >> > > > > >> with my
>> >> > > > > >> >>> Azure VM.
>> >> > > > > >> >>>
>> >> > > > > >> >>> -Alex
>> >> > > > > >> >>>
>> >> > > > > >> >>> On 2/5/19,
>> 10:59 PM,
>> >> "Carlos
>> >> > > Rovira" <
>> >> > > > > carlosrovira@apache.org>
>> >> > > > > >> wrote:
>> >> > > > > >> >>>
>> >> > > > > >> >>> Hi.
>> >> > > > > >> >>>
>> >> > > > > >> >>> the plan
>> sounds
>> >> very good
>> >> > to
>> >> > > me. Just
>> >> > > > my 2
>> >> > > > > thoughts on this:
>> >> > > > > >> >>>
>> >> > > > > >> >>> 1.- As I was
>> >> reading I was
>> >> > > thinking as
>> >> > > > well on
>> >> > > > > something like
>> >> > > > > >> Docker
>> >> > > > > >> >>> and
>> >> > > > > >> >>> see Om as
>> well
>> >> thinking on
>> >> > > the same.
>> >> > > > Maybe is
>> >> > > > > the way to this
>> >> > > > > >> with
>> >> > > > > >> >> the
>> >> > > > > >> >>> actual
>> technology.
>> >> Seems
>> >> > VMs
>> >> > > are
>> >> > > > stepping out a
>> >> > > > > bit this days
>> >> > > > > >> in
>> >> > > > > >> >> favor
>> >> > > > > >> >>> of
>> >> > > > > >> >>> things like
>> Docker.
>> >> Maybe
>> >> > > the same did
>> >> > > > Git over
>> >> > > > > Svn, and today
>> >> > > > > >> Svn is
>> >> > > > > >> >>> an
>> >> > > > > >> >>> old
>> remembrance. I
>> >> must say
>> >> > > that I
>> >> > > > have no
>> >> > > > > experience with
>> >> > > > > >> Docker, so
>> >> > > > > >> >>> doing
>> >> > > > > >> >>> that will
>> require
>> >> acquire
>> >> > > that
>> >> > > > knowledge, but
>> >> > > > > seems it could
>> >> > > > > >> be worth
>> >> > > > > >> >>> it.
>> >> > > > > >> >>>
>> >> > > > > >> >>> 2.- Maybe is
>> not
>> >> possible,
>> >> > > but I want
>> >> > > > to propose
>> >> > > > > to do this
>> >> > > > > >> work I a
>> >> > > > > >> >>> separate
>> branch, so
>> >> it
>> >> > could
>> >> > > be in
>> >> > > > parallel to
>> >> > > > > other
>> >> > > > > >> developments. I
>> >> > > > > >> >>> think
>> >> > > > > >> >>> work over
>> develop is
>> >> > > practical if
>> >> > > > there's
>> >> > > > > something tiny that
>> >> > > > > >> could
>> >> > > > > >> >> be
>> >> > > > > >> >>> done
>> >> > > > > >> >>> in a commit.
>> But as
>> >> we need
>> >> > > more than
>> >> > > > one, or is
>> >> > > > > a long
>> >> > > > > >> process (like
>> >> > > > > >> >>> this),
>> chances are
>> >> to make
>> >> > > develop
>> >> > > > branch
>> >> > > > > unstable and even
>> >> > > > > >> for some
>> >> > > > > >> >>> days.
>> >> > > > > >> >>> I think we
>> should
>> >> try to
>> >> > > avoid that
>> >> > > > scenario,
>> >> > > > > and branches are
>> >> > > > > >> the
>> >> > > > > >> >> best
>> >> > > > > >> >>> way. If we
>> do this
>> >> way,
>> >> > > we'll benefit
>> >> > > > of more
>> >> > > > > reliable develop
>> >> > > > > >> >> branch.
>> >> > > > > >> >>>
>> >> > > > > >> >>> Thanks and
>> good to
>> >> know of
>> >> > > this plan :)
>> >> > > > > >> >>>
>> >> > > > > >> >>> Carlos
>> >> > > > > >> >>>
>> >> > > > > >> >>>
>> >> > > > > >> >>> El mar., 5
>> feb.
>> >> 2019 a las
>> >> > > 23:19,
>> >> > > > Harbs (<
>> >> > > > > >> harbs.lists@gmail.com>)
>> >> > > > > >> >>> escribió:
>> >> > > > > >> >>>
>> >> > > > > >> >>>> I’ve never
>> used Docker
>> >> > myself,
>> >> > > but that
>> >> > > > might be a
>> >> > > > > good plan.
>> >> > > > > >> >>>>
>> >> > > > > >> >>>>> On Feb 6,
>> 2019, at
>> >> 12:07 AM,
>> >> > > OmPrakash
>> >> > > > Muppirala <
>> >> > > > > >> >>>
>> bigosmallm@gmail.com>
>> >> > > > > >> >>>> wrote:
>> >> > > > > >> >>>>>
>> >> > > > > >> >>>>> I was
>> wondering if
>> >> we can
>> >> > use
>> >> > > docker
>> >> > > > images to
>> >> > > > > setup and seal
>> >> > > > > >> the
>> >> > > > > >> >>> RM
>> >> > > > > >> >>>>> environment.
>> Then
>> >> other RMs
>> >> > > simply
>> >> > > > need to run
>> >> > > > > the image
>> >> > > > > >> locally
>> >> > > > > >> >>> and run
>> >> > > > > >> >>>>> the release
>> >> scripts. Might
>> >> > > be easier.
>> >> > > > If folks
>> >> > > > > like this plan,
>> >> > > > > >> >> I
>> >> > > > > >> >>> can
>> >> > > > > >> >>>> try
>> >> > > > > >> >>>>> to put
>> something
>> >> together.
>> >> > > > > >> >>>>>
>> >> > > > > >> >>>>> Thanks,
>> >> > > > > >> >>>>> Om
>> >> > > > > >> >>>>>
>> >> > > > > >> >>>>> On Tue, Feb
>> 5, 2019
>> >> at 1:40
>> >> > > PM Harbs <
>> >> > > > > harbs.lists@gmail.com>
>> >> > > > > >> >>> wrote:
>> >> > > > > >> >>>>>
>> >> > > > > >> >>>>>> In a recent
>> >> discussion, it
>> >> > > looks like
>> >> > > > other
>> >> > > > > projects have
>> >> > > > > >> gotten
>> >> > > > > >> >>>> resources
>> >> > > > > >> >>>>>> from AWS.
>> >> > > > > >> >>>>>>
>> >> > > > > >> >>>>>> Whatever
>> service we
>> >> use,
>> >> > > could setup a
>> >> > > > “shared”
>> >> > > > > Royale account
>> >> > > > > >> >>> that all
>> >> > > > > >> >>>>>> PMC members
>> could
>> >> have
>> >> > > access to.
>> >> > > > > >> >>>>>>
>> >> > > > > >> >>>>>> I don’t know
>> if
>> >> there’s
>> >> > some
>> >> > > way we
>> >> > > > could
>> >> > > > > leverage Gitlab’s
>> >> > > > > >> >>> integration
>> >> > > > > >> >>>>>> pipelines
>> >> > > > > >> >>>
>> >> > > > > >> >>
>> >> > > > > >>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=rSudm9PhsVDHugk2T5zj%2BjDLlE8Ayx2tw3wLnpFnH0g%3D&reserved=0
>> >> > > > > >> >>> <
>> >> > > > > >> >>>>>>
>> >> > > > > >> >>>
>> >> > > > > >> >>
>> >> > > > > >>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=rSudm9PhsVDHugk2T5zj%2BjDLlE8Ayx2tw3wLnpFnH0g%3D&reserved=0
>> >> > > > > >> >>>>
>> >> > > > > >> >>>>>>
>> >> > > > > >> >>>>>>> On Feb 5,
>> 2019, at
>> >> 11:33
>> >> > > PM, Alex
>> >> > > > Harui
>> >> > > > > >> >>
>> >> <aharui@adobe.com.INVALID
>> >> > > > > >> >>>>
>> >> > > > > >> >>>>>> wrote:
>> >> > > > > >> >>>>>>>
>> >> > > > > >> >>>>>>> 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" <
>> >> > > > > >> >>
>> >> piotrzarzycki21@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.lists@gmail.com
>> >> > > > > >> >>> wrote:
>> >> > > > > >> >>>>>>>
>> >> > > > > >> >>>>>>>> A big +1
>> from me!
>> >> > > > > >> >>>>>>>>
>> >> > > > > >> >>>>>>>> Looking
>> forward!
>> >> > > > > >> >>>>>>>>
>> >> > > > > >> >>>>>>>>> On Feb 5,
>> 2019,
>> >> at 9:34
>> >> > > PM, Alex
>> >> > > > Harui
>> >> > > > > >> >>>
>> >> <ah...@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
>> >> > > > >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>
Re: 0.9.6 Release
Posted by Greg Dove <gr...@gmail.com>.
Thanks Alex, I was planning to merge this as a single squashed commit,
because it isolates all the changes to a single commit (but this will mean
there are many changes in one hit).
Do you have a preference in terms of how easy it will make things for you?
On Tue, Jun 11, 2019 at 3:07 PM Alex Harui <ah...@adobe.com.invalid> wrote:
> OK, I will wait to see your commit emails. I will do some other things
> like the wiki doc.
>
> -Alex
>
> On 6/10/19, 8:06 PM, "Greg Dove" <gr...@gmail.com> wrote:
>
> Hi Alex, I guess you might be back on Royale about now. Just a heads
> up: I
> am about 20-30 mins max from merging in what I have. Hope that's still
> ok... please let me know if not.
> Thanks,
> -Greg
>
>
> On Tue, Jun 11, 2019 at 7:51 AM Greg Dove <gr...@gmail.com> wrote:
>
> >
> > Thanks Alex - I'll try to hit the window, much appreciated!
> >
> >
> > On Tue, Jun 11, 2019 at 6:57 AM Alex Harui <aharui@adobe.com.invalid
> >
> > wrote:
> >
> >> Hi Greg,
> >>
> >> It turns out I have a "split shift" today. I'm stopping work for
> the
> >> next 7 or 8 hours then will get around to the merge. So if you can
> get
> >> your changes merged in that amount of time, then I will wait for
> you and
> >> deal with any merge conflicts (there are almost certain to be some).
> >>
> >> -Alex
> >>
> >> On 6/10/19, 11:46 AM, "Greg Dove" <gr...@gmail.com> wrote:
> >>
> >> Alex, slightly OT, but in terms of coordination: fyi I am also
> very
> >> close
> >> to merging the language improvements branch into develop. As I
> already
> >> mentioned elsewhere, I was hoping to do that a couple of days
> back,
> >> but
> >> some recent things also took me a little longer than expected
> (I have
> >> additional local changes/fixes not yet in remote branch) . I was
> >> planning
> >> to merge that today also.
> >>
> >> However, I will wait until after your merge, so I'm hoping you
> can get
> >> yours in today (if not, I will wait). I will probably put mine
> in as a
> >> squashed commit after yours.
> >>
> >>
> >> On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <
> >> piotrzarzycki21@gmail.com>
> >> wrote:
> >>
> >> > Hi Alex,
> >> >
> >> > Many thanks for that! I will try to be RM. I will have some
> >> dedicated time
> >> > for that. I will wait for your instruction and merge to
> develop.
> >> >
> >> > Thanks,
> >> > Piotr
> >> >
> >> >
> >> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
> <ah...@adobe.com.invalid>
> >> wrote:
> >> >
> >> > > Well, that turned out to be much more time-consuming than I
> >> expected, but
> >> > > we can now create identical release artifacts on Mac and
> Win. I
> >> am
> >> > hopeful
> >> > > this effort will pay off not only now in having other folks
> >> generate
> >> > > releases, but also in the future if signed binaries become a
> >> requirement.
> >> > >
> >> > > There continues to be a lot of distractions in my life that
> can
> >> cause
> >> > > delays, but I hope to merge the release_practice branches
> into
> >> develop
> >> > over
> >> > > the next day or two and figure out where in the wiki to
> document
> >> the
> >> > > release process. So, now is the time for one or more
> people to
> >> step up
> >> > to
> >> > > be the RMs for 0.9.6 and help debug and improve the process.
> >> > >
> >> > > I am going to try very hard not to "own" the process. If
> >> something goes
> >> > > wrong, I am going to ask others to try to debug and fix it
> first
> >> because
> >> > it
> >> > > is in the project's best interests for others to truly
> understand
> >> how
> >> > this
> >> > > stuff works.
> >> > >
> >> > > Thanks,
> >> > > -Alex
> >> > >
> >> > > On 5/23/19, 9:54 AM, "Alex Harui" <aharui@adobe.com.INVALID
> >
> >> wrote:
> >> > >
> >> > > It has turned out to be harder than expected to get the
> same
> >> binaries
> >> > > on Mac and Win. I now have the identical binaries for
> >> royale-compiler
> >> > and
> >> > > royale-typedefs Maven artifacts and am starting on
> royale-asjs.
> >> I might
> >> > > get lucky and the changes that fixed royale-typedefs SWCs
> will
> >> magically
> >> > > get the royale-asjs SWCs to match. Then we have to make
> the Ant
> >> > artifacts
> >> > > match.
> >> > >
> >> > > There have been a lot of distractions in my non-work
> life
> >> which has
> >> > > also impeded progress. I hope to make much progress this
> coming
> >> week and
> >> > > if we're lucky, I will be asking for a volunteer (or
> volunteers)
> >> to test
> >> > > drive all of this stuff and be the RM for 0.9.6. I am not
> going
> >> to be
> >> > the
> >> > > RM.
> >> > >
> >> > > -Alex
> >> > >
> >> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> >> piotrzarzycki21@gmail.com>
> >> > > wrote:
> >> > >
> >> > > Hi Alex,
> >> > >
> >> > > It's been a while since you have started effort with
> >> automating
> >> > > build.
> >> > > Where are you with that ? Are we closer to started
> 0.9.6.
> >> Do you
> >> > > need any
> >> > > help with this ?
> >> > >
> >> > > Thanks,
> >> > > Piotr
> >> > >
> >> > > wt., 2 kwi 2019 o 19:30 Alex Harui
> >> <ah...@adobe.com.invalid>
> >> > > napisał(a):
> >> > >
> >> > > > Update:
> >> > > >
> >> > > > In order to make verification of binary release
> packages
> >> > created
> >> > > on the
> >> > > > server easier, I have made changes to our build
> scripts
> >> and
> >> > > tools to try to
> >> > > > generate reproducible binaries. I've seen two
> >> different builds
> >> > > compare on
> >> > > > my Mac. The next challenge will be to see if the
> >> server can
> >> > > build a
> >> > > > package on Windows that will compare on Mac.
> >> > > >
> >> > > > One of the changes I needed to make is to JBurg.
> The
> >> version
> >> > of
> >> > > JBurg we
> >> > > > use generates method names including a hash that
> doesn't
> >> > > reproduce the same
> >> > > > name each time. I have changes to JBurg ready,
> however
> >> JBurg
> >> > is
> >> > > currently
> >> > > > under CPL which is category B. We only need one
> file,
> >> we don't
> >> > > need or
> >> > > > want all of JBurg at this time. The one JBurg
> file is
> >> jointly
> >> > > owned by
> >> > > > Adobe and Tom Harwood. I've contact Tom and he
> will be
> >> filing
> >> > > an ICLA and
> >> > > > has given me permission to commit the lines he
> owns in
> >> that one
> >> > > file.
> >> > > >
> >> > > > This is the revision of the file that will be
> donated by
> >> > > Tom/Adobe.
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=VS1za1vOQhtlKlK4Tdgq3ej04OlhFoYfHziyNbgOIN4%3D&reserved=0
> >> > > >
> >> > > > Once this file goes in with the changes to keep
> the
> >> method
> >> > names
> >> > > the same,
> >> > > > there will be more tweaks to the release tasks
> and then
> >> we can
> >> > > try cutting
> >> > > > a release. I'm thinking we'll be at that point in
> >> early May,
> >> > so
> >> > > now is the
> >> > > > time to get stuff in for the 0.9.6 release.
> >> > > >
> >> > > > Thanks,
> >> > > > -Alex
> >> > > >
> >> > > > On 3/8/19, 9:27 AM, "Alex Harui" <
> aharui@adobe.com>
> >> wrote:
> >> > > >
> >> > > > I would much rather have others find and fix
> issues
> >> > > themselves. That
> >> > > > way, more people than just me will know how to
> maintain
> >> the
> >> > > system. It
> >> > > > actually turns out that, IMO, a group of people
> can
> >> work on the
> >> > > release.
> >> > > > There are 14 steps. Literally, 14 different
> people
> >> could
> >> > > execute one step
> >> > > > each.
> >> > > >
> >> > > > My 2 cents,
> >> > > > -Alex
> >> > > >
> >> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> >> > carlosrovira@apache.org>
> >> > > wrote:
> >> > > >
> >> > > > Hi Alex,
> >> > > >
> >> > > > amazing work! congrats to reach to this
> point!
> >> :)
> >> > > >
> >> > > > I need to put my head on all of this, but
> count
> >> on me
> >> > to
> >> > > be a RM.
> >> > > > I think
> >> > > > the best thing should be that you be the
> first
> >> RM to
> >> > try
> >> > > your own
> >> > > > development at least for the first time,
> and
> >> then the
> >> > > rest of us
> >> > > > will
> >> > > > follow you on the next releases. With all
> this
> >> on place
> >> > > we maybe
> >> > > > could
> >> > > > release once a month or every two
> months...
> >> > > >
> >> > > > Thanks for doing this :)
> >> > > >
> >> > > > Carlos
> >> > > >
> >> > > >
> >> > > > El vie., 8 mar. 2019 a las 1:55, Alex
> Harui
> >> > > > (<ah...@adobe.com.invalid>)
> >> > > > escribió:
> >> > > >
> >> > > > > OK, I've now seen Jenkins perform the
> steps
> >> to build
> >> > > the release
> >> > > > > artifacts. Folks interested in
> Docker-izing
> >> the
> >> > steps
> >> > > are
> >> > > > welcome to look
> >> > > > > at the jobs on the "Royale Release" tab
> on
> >> the CI
> >> > > server.
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=LfWCyCaClCVgfeINn4%2B%2Bk%2FSVUFXvgyV7QxMtx4B%2B%2Fu0%3D&reserved=0
> >> > > > >
> >> > > > > These steps assume that the RM can run
> the
> >> basic
> >> > Maven
> >> > > and Ant
> >> > > > build on
> >> > > > > the RM's computer. I think that's a fair
> >> requirement
> >> > > since all
> >> > > > of us on the
> >> > > > > PMC need to able to do that to build
> the RC
> >> in order
> >> > > to vote on
> >> > > > it.
> >> > > > > Jenkins does other tasks like run the
> Maven
> >> release
> >> > > plugin
> >> > > > steps.
> >> > > > >
> >> > > > > Currently that results in binaries on
> Jenkins
> >> that
> >> > are
> >> > > > downloaded to the
> >> > > > > RM's computer. These binaries need to
> be
> >> verified by
> >> > > the RM
> >> > > > which is the
> >> > > > > next phase I will be starting on now.
> The RM
> >> > verifies
> >> > > the bits
> >> > > > and then
> >> > > > > PGP signs them. And then the bits are
> >> uploaded off
> >> > > the RM's
> >> > > > computer to
> >> > > > > Maven Staging or dist.a.o/dev. If that
> >> uploading
> >> > > turns out to
> >> > > > be a point
> >> > > > > of failure, we have the option of having
> >> Jenkins
> >> > > upload the big
> >> > > > files and
> >> > > > > have the RM only upload PGP signature
> files.
> >> Or
> >> > > finding a way
> >> > > > for Jenkins
> >> > > > > to get the signature files from the
> RM. The
> >> uploads
> >> > > worked fine
> >> > > > for me,
> >> > > > > but then again, so did the old script's
> >> uploads.
> >> > > > >
> >> > > > > Therefore, once I get the binary
> verification
> >> phase
> >> > > completed, I
> >> > > > think
> >> > > > > someone other than me should be the RM
> and
> >> try to use
> >> > > these
> >> > > > steps to
> >> > > > > generate the release and help debug the
> >> process for
> >> > > the next
> >> > > > RM. So,
> >> > > > > please try to carve out some time to be
> the
> >> RM. One
> >> > > advantage
> >> > > > of doing
> >> > > > > most of the work on Jenkins is that it
> frees
> >> up my
> >> > > computer to
> >> > > > do other
> >> > > > > things while Jenkins is cranking away.
> >> > > > >
> >> > > > > I think we're at least a week away from
> binary
> >> > > verification,
> >> > > > maybe two, so
> >> > > > > it is time to start thinking about what
> is
> >> going in
> >> > > this release.
> >> > > > >
> >> > > > > Thanks,
> >> > > > > -Alex
> >> > > > >
> >> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
> >> > > <ah...@adobe.com.INVALID>
> >> > > > wrote:
> >> > > > >
> >> > > > > In case you haven't guessed, I'm
> testing
> >> out
> >> > > Jenkins and its
> >> > > > ability
> >> > > > > to create the artifacts and send emails.
> >> Please
> >> > > ignore any
> >> > > > email that
> >> > > > > looks like a vote or discuss thread.
> >> > > > >
> >> > > > > Thanks,
> >> > > > > -Alex
> >> > > > >
> >> > > > > On 2/10/19, 8:44 PM, "Alex Harui"
> >> > > <ah...@adobe.com.INVALID>
> >> > > > wrote:
> >> > > > >
> >> > > > > Om,
> >> > > > >
> >> > > > > Well, that's what I used for
> the last
> >> > > release. I'm sure
> >> > > > there is
> >> > > > > probably some inaccuracy in it.
> >> > > > >
> >> > > > > That said, I'm abandoning that
> >> document and
> >> > > taking a new
> >> > > > angle
> >> > > > > because that document presumed that the
> >> release
> >> > > manager was
> >> > > > trying to
> >> > > > > create a release on his/her computer.
> I've
> >> given up
> >> > > on that and
> >> > > > working on
> >> > > > > making releases from a shared computer
> for the
> >> > reasons
> >> > > I've
> >> > > > stated
> >> > > > > upthread. I hope to make some progress
> on
> >> that this
> >> > > week.
> >> > > > >
> >> > > > > The key difference is that the
> new
> >> angle does
> >> > > not
> >> > > > presume that you
> >> > > > > have Git SSH and PGP signatures all set
> up on
> >> some
> >> > > computer. I
> >> > > > have not
> >> > > > > looked into how Docker would handle
> that. You
> >> > > certainly
> >> > > > wouldn't want the
> >> > > > > Docker image to contain your SSH or PGP
> >> keys/creds.
> >> > > And if the
> >> > > > Docker
> >> > > > > image doesn't, then that is another
> stumbling
> >> block
> >> > > for future
> >> > > > RMs.
> >> > > > >
> >> > > > > The other key difference is
> that the
> >> old
> >> > > script presumed
> >> > > > you could
> >> > > > > create the 3 release in 3 huge "easy"
> steps.
> >> We've
> >> > > seen that is
> >> > > > only true
> >> > > > > for me. So the new angle creates many
> >> discrete steps
> >> > > managed by
> >> > > > Jenkins.
> >> > > > >
> >> > > > > So, it is up to you to decide
> what
> >> you want
> >> > to
> >> > > > "Docker-ize". You
> >> > > > > can try to Docker-ize the current 3 big
> >> steps, so RMs
> >> > > can try to
> >> > > > run it on
> >> > > > > their systems, but I'd bet they will
> just
> >> faiI due to
> >> > > network
> >> > > > issues. I
> >> > > > > would be interested in using Docker to
> make
> >> each of
> >> > > these many
> >> > > > discrete
> >> > > > > steps portable to another server. I'm
> not
> >> going to
> >> > > involve
> >> > > > Docker at this
> >> > > > > point. My main goal is just to see if
> I can
> >> create a
> >> > > workflow
> >> > > > of many
> >> > > > > discrete steps that isn't horribly
> painful.
> >> Once we
> >> > > see what
> >> > > > these steps
> >> > > > > turn out to be, then we can worry about
> server
> >> > > portability of
> >> > > > those steps.
> >> > > > >
> >> > > > > Either way, we want to know
> about
> >> running
> >> > > > Browser+Selenium for
> >> > > > > sure. And maybe FlashPlayerDebugger or
> AIR.
> >> I would
> >> > > want to
> >> > > > know, for
> >> > > > > example, how you debug a failing
> checkintest
> >> in a
> >> > > Docker
> >> > > > container.
> >> > > > >
> >> > > > > Thanks,
> >> > > > > -Alex
> >> > > > >
> >> > > > >
> >> > > > > On 2/10/19, 5:18 PM, "OmPrakash
> >> Muppirala" <
> >> > > > bigosmallm@gmail.com>
> >> > > > > wrote:
> >> > > > >
> >> > > > > Alex,
> >> > > > >
> >> > > > > Just to be clear, I am
> following
> >> the
> >> > steps
> >> > > from here
> >> > > > to try
> >> > > > > and setup a
> >> > > > > docker container.
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=Lhm0hudN8Nbx%2F6Lnmz0Wlus3EpV1o1h8XWBzBUoEWOA%3D&reserved=0
> >> > > > >
> >> > > > > Is this doc up to date?
> >> > > > >
> >> > > > > Thanks,
> >> > > > > Om
> >> > > > >
> >> > > > > On Wed, Feb 6, 2019 at
> 12:02 PM
> >> OmPrakash
> >> > > Muppirala <
> >> > > > > bigosmallm@gmail.com>
> >> > > > > wrote:
> >> > > > >
> >> > > > > > One approach is to have
> each
> >> step in
> >> > the
> >> > > process
> >> > > > spin up a
> >> > > > > docker image.
> >> > > > > > And use docker-compose to
> run
> >> each
> >> > > step. All the
> >> > > > images can
> >> > > > > be made to
> >> > > > > > share a common volume
> where all
> >> the
> >> > > artifacts are
> >> > > > stored
> >> > > > > across steps.
> >> > > > > >
> >> > > > > > You are right about the
> >> networking
> >> > issue
> >> > > though.
> >> > > > Any
> >> > > > > network related
> >> > > > > > failure that occurs on
> the host
> >> machine
> >> > > will most
> >> > > > likely
> >> > > > > occur in the
> >> > > > > > docker container.
> Although, I
> >> am not
> >> > > clear how we
> >> > > > can
> >> > > > > guarantee that the
> >> > > > > > same issues will not
> occur on
> >> the
> >> > > Jenkins server.
> >> > > > I mean,
> >> > > > > what is special
> >> > > > > > about the Jenkins server
> that
> >> makes it
> >> > > immune to
> >> > > > these
> >> > > > > networking issues?
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > Om
> >> > > > > >
> >> > > > > > On Wed, Feb 6, 2019 at
> 11:48 AM
> >> Alex
> >> > > Harui
> >> > > > > <ah...@adobe.com.invalid>
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > >> Again, I don't know
> anything
> >> about
> >> > > Docker, but
> >> > > > before we
> >> > > > > spend a lot of
> >> > > > > >> time on Docker, I also
> want to
> >> point
> >> > > out that the
> >> > > > process
> >> > > > > to create a
> >> > > > > >> release cannot really be
> >> thought of as
> >> > > "one
> >> > > > application".
> >> > > > > It will be a
> >> > > > > >> series of "steps" to run.
> >> How many
> >> > > steps
> >> > > > depends on
> >> > > > > whether we think we
> >> > > > > >> can isolate enough stuff
> via
> >> Docker to
> >> > > be able to
> >> > > > run
> >> > > > > Docker on the RM's
> >> > > > > >> computer instead of some
> shared
> >> > > computer. On a
> >> > > > shared
> >> > > > > computer there will
> >> > > > > >> be dozens of steps
> because the
> >> RM will
> >> > > need to
> >> > > > enter
> >> > > > > passwords to commit
> >> > > > > >> stuff. On a local
> computer I
> >> guess
> >> > the
> >> > > RM can
> >> > > > supply
> >> > > > > passwords but I think
> >> > > > > >> there will be stopping
> points
> >> where
> >> > the
> >> > > Maven
> >> > > > artifacts are
> >> > > > > deployed and
> >> > > > > >> the staging repo is
> closed, and
> >> > another
> >> > > stopping
> >> > > > point for
> >> > > > > the vote. It
> >> > > > > >> seems like Docker works
> by
> >> downloading
> >> > > > dependencies. Given
> >> > > > > that the
> >> > > > > >> problem the RMs had last
> time
> >> involved
> >> > > downloads
> >> > > > and
> >> > > > > uploads, why do we
> >> > > > > >> think Docker will really
> solve
> >> this
> >> > for
> >> > > creating
> >> > > > releases
> >> > > > > on local machines?
> >> > > > > >>
> >> > > > > >> The reason to do this on
> a
> >> shared
> >> > > machine is so
> >> > > > that new
> >> > > > > RMs don't have
> >> > > > > >> to do as much setup.
> But then
> >> I
> >> > wonder
> >> > > about the
> >> > > > > efficiency of kicking off
> >> > > > > >> that many Docker images.
> >> Jenkins can
> >> > > manage that
> >> > > > already.
> >> > > > > Does Docker
> >> > > > > >> have some sort of similar
> >> Dashboard or
> >> > > would we
> >> > > > use Jenkins
> >> > > > > to kick off
> >> > > > > >> Docker steps? I can't
> quite
> >> picture
> >> > > what is the
> >> > > > outermost
> >> > > > > >> control/dashboard.
> >> > > > > >>
> >> > > > > >> -Alex
> >> > > > > >>
> >> > > > > >> On 2/6/19, 11:03 AM,
> "Harbs" <
> >> > > > harbs.lists@gmail.com> wrote:
> >> > > > > >>
> >> > > > > >> A quick search turns
> up
> >> this:
> >> > > > > >>
> >> > > > > >>
> >> > > > > >>
> >> > > > >
> >> > > >
> >> > >
> >> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
> >> > > > > >> <
> >> > > > > >>
> >> > > > >
> >> > > >
> >> > >
> >> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
> >> > > > > >> >
> >> > > > > >>
> >> > > > > >>
> >> > > > >
> >> > > >
> >> > >
> >> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=YPCe61GnfpckdNdqMRCDAHXsd3dvMHT3BO157C%2Fufs4%3D&reserved=0
> >> > > > > >> <
> >> > > > > >>
> >> > > > >
> >> > > >
> >> > >
> >> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=YPCe61GnfpckdNdqMRCDAHXsd3dvMHT3BO157C%2Fufs4%3D&reserved=0
> >> > > > > >> >
> >> > > > > >>
> >> > > > > >>
> >> > > > >
> >> > > >
> >> > >
> >> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=lsUmIIjQQi5CZhXTvQgd7lPt%2BVL2ApXFbK7i0NbMk1k%3D&reserved=0
> >> > > > > >> <
> >> > > > > >>
> >> > > > >
> >> > > >
> >> > >
> >> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=lsUmIIjQQi5CZhXTvQgd7lPt%2BVL2ApXFbK7i0NbMk1k%3D&reserved=0
> >> > > > > >> >
> >> > > > > >>
> >> > > > > >> > On Feb 6, 2019, at
> 8:59
> >> PM, Alex
> >> > > Harui
> >> > > > > <ah...@adobe.com.INVALID>
> >> > > > > >> wrote:
> >> > > > > >> >
> >> > > > > >> > Thanks for
> volunteering
> >> to try
> >> > it
> >> > > Om. IMO,
> >> > > > even more
> >> > > > > important
> >> > > > > >> than Firefox+Flash is
> >> > > SomeBrowser+Selenium. We
> >> > > > may also
> >> > > > > need to run Adobe
> >> > > > > >> AIR's adb. We could
> probably
> >> turn off
> >> > > the Flash
> >> > > > tests or
> >> > > > > replace Flash
> >> > > > > >> with AIR.
> >> > > > > >> >
> >> > > > > >> > Thanks,
> >> > > > > >> > -Alex
> >> > > > > >> >
> >> > > > > >> > On 2/6/19, 10:54
> AM,
> >> "Carlos
> >> > > Rovira" <
> >> > > > > carlosrovira@apache.org>
> >> > > > > >> wrote:
> >> > > > > >> >
> >> > > > > >> > Hi Om, that
> would be
> >> great!
> >> > > waiting for
> >> > > > your
> >> > > > > experience with a
> >> > > > > >> that! :)
> >> > > > > >> >
> >> > > > > >> > El mié., 6 feb.
> 2019
> >> a las
> >> > > 19:31,
> >> > > > OmPrakash
> >> > > > > Muppirala (<
> >> > > > > >> bigosmallm@gmail.com>)
> >> > > > > >> > escribió:
> >> > > > > >> >
> >> > > > > >> >> Yes, I agree with
> Alex
> >> about
> >> > not
> >> > > being
> >> > > > able to run
> >> > > > > UI out of docker
> >> > > > > >> >> containers. I
> never
> >> thought of
> >> > > the
> >> > > > checkintests
> >> > > > > when I made the
> >> > > > > >> >> suggestion.
> >> > > > > >> >>
> >> > > > > >> >> The firefox-flash
> image
> >> that
> >> > > Yishay
> >> > > > pointed out
> >> > > > > looks promising.
> >> > > > > >> I will
> >> > > > > >> >> poke around with
> it and
> >> see if
> >> > > that works
> >> > > > for us.
> >> > > > > >> >>
> >> > > > > >> >> Thanks,
> >> > > > > >> >> Om
> >> > > > > >> >>
> >> > > > > >> >> On Wed, Feb 6,
> 2019 at
> >> 12:41 AM
> >> > > Yishay
> >> > > > Weiss <
> >> > > > > >> yishayjobs@hotmail.com>
> >> > > > > >> >> wrote:
> >> > > > > >> >>
> >> > > > > >> >>> I’ll let Om or
> someone
> >> else
> >> > > with docker
> >> > > > experience
> >> > > > > tell us if
> >> > > > > >> this [1] is
> >> > > > > >> >>> relevant.
> >> > > > > >> >>>
> >> > > > > >> >>>
> >> > > > > >> >>>
> >> > > > > >> >>> [1]
> >> > > > > >>
> >> > > > >
> >> > > >
> >> > >
> >> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=L6e5%2FCo%2BOzdzvR3QxWvKa7Yg%2BkTw00Afeq24%2B11PGeU%3D&reserved=0
> >> > > > > >> >>>
> >> > > > > >> >>>
> >> > > > > >> >>>
> >> > > > > >> >>>
> >> > ________________________________
> >> > > > > >> >>> From: Alex Harui
> >> > > <aharui@adobe.com.INVALID
> >> > > > >
> >> > > > > >> >>> Sent: Wednesday,
> >> February 6,
> >> > > 2019
> >> > > > 10:05:54 AM
> >> > > > > >> >>> To:
> >> dev@royale.apache.org
> >> > > > > >> >>> Subject: Re:
> 0.9.6
> >> Release
> >> > > > > >> >>>
> >> > > > > >> >>> I don't anything
> about
> >> docker,
> >> > > but in 15
> >> > > > minutes of
> >> > > > > reading I ran
> >> > > > > >> into
> >> > > > > >> >>> this:
> >> > > > > >> >>>
> >> > > > > >> >>>
> >> > > > > >> >>
> >> > > > > >>
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=TLSgOkYEaTxxr%2B7TlB%2BOJVt68S2pOH%2FVOAUDtvFYWWE%3D&reserved=0
> >> > > > > >> >>>
> >> > > > > >> >>> Which says:
> Docker
> >> can't " Run
> >> > > > applications with
> >> > > > > graphical
> >> > > > > >> interfaces".
> >> > > > > >> >>> If you want
> Royale to
> >> use
> >> > > Docker for
> >> > > > releases, show
> >> > > > > that it can
> >> > > > > >> run
> >> > > > > >> >>> checkintests with
> >> Flash and
> >> > the
> >> > > Browser.
> >> > > > Then I
> >> > > > > will look into
> >> > > > > >> it more.
> >> > > > > >> >>>
> >> > > > > >> >>> The highest
> level goal
> >> is to
> >> > > make it as
> >> > > > easy as
> >> > > > > possible for
> >> > > > > >> someone to
> >> > > > > >> >>> volunteer to be
> an
> >> RM. Any
> >> > > requirement
> >> > > > of "install
> >> > > > > this (Docker,
> >> > > > > >> etc) on
> >> > > > > >> >>> your computer"
> is, IMO,
> >> > another
> >> > > barrier
> >> > > > to entry.
> >> > > > > Yeah, RMs will
> >> > > > > >> have to
> >> > > > > >> >>> have Maven
> installed
> >> and maybe
> >> > > Ant, but
> >> > > > you should
> >> > > > > already have
> >> > > > > >> those
> >> > > > > >> >>> installed to be a
> >> > committer/PMC
> >> > > member.
> >> > > > > >> >>>
> >> > > > > >> >>> That said, a good
> >> takeaway
> >> > from
> >> > > the
> >> > > > Docker idea is
> >> > > > > to try to find
> >> > > > > >> a way
> >> > > > > >> >> to
> >> > > > > >> >>> make an "Image"
> of
> >> whatever we
> >> > > end up
> >> > > > with on
> >> > > > > whatever server we
> >> > > > > >> end up
> >> > > > > >> >>> using so if the
> image
> >> can be
> >> > > copied and
> >> > > > used on
> >> > > > > other servers.
> >> > > > > >> I'm not
> >> > > > > >> >>> exactly sure how
> to do
> >> that
> >> > > with Azure,
> >> > > > which hosts
> >> > > > > my CI
> >> > > > > >> server. I will
> >> > > > > >> >>> spend a few more
> >> minutes
> >> > > researching that.
> >> > > > > >> >>>
> >> > > > > >> >>> I could not
> quickly
> >> find any
> >> > > way to get a
> >> > > > free VM
> >> > > > > on Azure or AWS
> >> > > > > >> that
> >> > > > > >> >>> isn't a
> >> > > > free-trial-start-paying-after-a-year. So,
> >> > > > > unless someone
> >> > > > > >> comes
> >> > > > > >> >> up
> >> > > > > >> >>> with a free
> server we
> >> can use
> >> > > "forever",
> >> > > > I'm going
> >> > > > > to just start
> >> > > > > >> with my
> >> > > > > >> >>> Azure VM.
> >> > > > > >> >>>
> >> > > > > >> >>> -Alex
> >> > > > > >> >>>
> >> > > > > >> >>> On 2/5/19, 10:59
> PM,
> >> "Carlos
> >> > > Rovira" <
> >> > > > > carlosrovira@apache.org>
> >> > > > > >> wrote:
> >> > > > > >> >>>
> >> > > > > >> >>> Hi.
> >> > > > > >> >>>
> >> > > > > >> >>> the plan
> sounds
> >> very good
> >> > to
> >> > > me. Just
> >> > > > my 2
> >> > > > > thoughts on this:
> >> > > > > >> >>>
> >> > > > > >> >>> 1.- As I was
> >> reading I was
> >> > > thinking as
> >> > > > well on
> >> > > > > something like
> >> > > > > >> Docker
> >> > > > > >> >>> and
> >> > > > > >> >>> see Om as well
> >> thinking on
> >> > > the same.
> >> > > > Maybe is
> >> > > > > the way to this
> >> > > > > >> with
> >> > > > > >> >> the
> >> > > > > >> >>> actual
> technology.
> >> Seems
> >> > VMs
> >> > > are
> >> > > > stepping out a
> >> > > > > bit this days
> >> > > > > >> in
> >> > > > > >> >> favor
> >> > > > > >> >>> of
> >> > > > > >> >>> things like
> Docker.
> >> Maybe
> >> > > the same did
> >> > > > Git over
> >> > > > > Svn, and today
> >> > > > > >> Svn is
> >> > > > > >> >>> an
> >> > > > > >> >>> old
> remembrance. I
> >> must say
> >> > > that I
> >> > > > have no
> >> > > > > experience with
> >> > > > > >> Docker, so
> >> > > > > >> >>> doing
> >> > > > > >> >>> that will
> require
> >> acquire
> >> > > that
> >> > > > knowledge, but
> >> > > > > seems it could
> >> > > > > >> be worth
> >> > > > > >> >>> it.
> >> > > > > >> >>>
> >> > > > > >> >>> 2.- Maybe is
> not
> >> possible,
> >> > > but I want
> >> > > > to propose
> >> > > > > to do this
> >> > > > > >> work I a
> >> > > > > >> >>> separate
> branch, so
> >> it
> >> > could
> >> > > be in
> >> > > > parallel to
> >> > > > > other
> >> > > > > >> developments. I
> >> > > > > >> >>> think
> >> > > > > >> >>> work over
> develop is
> >> > > practical if
> >> > > > there's
> >> > > > > something tiny that
> >> > > > > >> could
> >> > > > > >> >> be
> >> > > > > >> >>> done
> >> > > > > >> >>> in a commit.
> But as
> >> we need
> >> > > more than
> >> > > > one, or is
> >> > > > > a long
> >> > > > > >> process (like
> >> > > > > >> >>> this),
> chances are
> >> to make
> >> > > develop
> >> > > > branch
> >> > > > > unstable and even
> >> > > > > >> for some
> >> > > > > >> >>> days.
> >> > > > > >> >>> I think we
> should
> >> try to
> >> > > avoid that
> >> > > > scenario,
> >> > > > > and branches are
> >> > > > > >> the
> >> > > > > >> >> best
> >> > > > > >> >>> way. If we do
> this
> >> way,
> >> > > we'll benefit
> >> > > > of more
> >> > > > > reliable develop
> >> > > > > >> >> branch.
> >> > > > > >> >>>
> >> > > > > >> >>> Thanks and
> good to
> >> know of
> >> > > this plan :)
> >> > > > > >> >>>
> >> > > > > >> >>> Carlos
> >> > > > > >> >>>
> >> > > > > >> >>>
> >> > > > > >> >>> El mar., 5
> feb.
> >> 2019 a las
> >> > > 23:19,
> >> > > > Harbs (<
> >> > > > > >> harbs.lists@gmail.com>)
> >> > > > > >> >>> escribió:
> >> > > > > >> >>>
> >> > > > > >> >>>> I’ve never used
> Docker
> >> > myself,
> >> > > but that
> >> > > > might be a
> >> > > > > good plan.
> >> > > > > >> >>>>
> >> > > > > >> >>>>> On Feb 6,
> 2019, at
> >> 12:07 AM,
> >> > > OmPrakash
> >> > > > Muppirala <
> >> > > > > >> >>>
> bigosmallm@gmail.com>
> >> > > > > >> >>>> wrote:
> >> > > > > >> >>>>>
> >> > > > > >> >>>>> I was
> wondering if
> >> we can
> >> > use
> >> > > docker
> >> > > > images to
> >> > > > > setup and seal
> >> > > > > >> the
> >> > > > > >> >>> RM
> >> > > > > >> >>>>> environment.
> Then
> >> other RMs
> >> > > simply
> >> > > > need to run
> >> > > > > the image
> >> > > > > >> locally
> >> > > > > >> >>> and run
> >> > > > > >> >>>>> the release
> >> scripts. Might
> >> > > be easier.
> >> > > > If folks
> >> > > > > like this plan,
> >> > > > > >> >> I
> >> > > > > >> >>> can
> >> > > > > >> >>>> try
> >> > > > > >> >>>>> to put
> something
> >> together.
> >> > > > > >> >>>>>
> >> > > > > >> >>>>> Thanks,
> >> > > > > >> >>>>> Om
> >> > > > > >> >>>>>
> >> > > > > >> >>>>> On Tue, Feb 5,
> 2019
> >> at 1:40
> >> > > PM Harbs <
> >> > > > > harbs.lists@gmail.com>
> >> > > > > >> >>> wrote:
> >> > > > > >> >>>>>
> >> > > > > >> >>>>>> In a recent
> >> discussion, it
> >> > > looks like
> >> > > > other
> >> > > > > projects have
> >> > > > > >> gotten
> >> > > > > >> >>>> resources
> >> > > > > >> >>>>>> from AWS.
> >> > > > > >> >>>>>>
> >> > > > > >> >>>>>> Whatever
> service we
> >> use,
> >> > > could setup a
> >> > > > “shared”
> >> > > > > Royale account
> >> > > > > >> >>> that all
> >> > > > > >> >>>>>> PMC members
> could
> >> have
> >> > > access to.
> >> > > > > >> >>>>>>
> >> > > > > >> >>>>>> I don’t know
> if
> >> there’s
> >> > some
> >> > > way we
> >> > > > could
> >> > > > > leverage Gitlab’s
> >> > > > > >> >>> integration
> >> > > > > >> >>>>>> pipelines
> >> > > > > >> >>>
> >> > > > > >> >>
> >> > > > > >>
> >> > > > >
> >> > > >
> >> > >
> >> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=rSudm9PhsVDHugk2T5zj%2BjDLlE8Ayx2tw3wLnpFnH0g%3D&reserved=0
> >> > > > > >> >>> <
> >> > > > > >> >>>>>>
> >> > > > > >> >>>
> >> > > > > >> >>
> >> > > > > >>
> >> > > > >
> >> > > >
> >> > >
> >> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=rSudm9PhsVDHugk2T5zj%2BjDLlE8Ayx2tw3wLnpFnH0g%3D&reserved=0
> >> > > > > >> >>>>
> >> > > > > >> >>>>>>
> >> > > > > >> >>>>>>> On Feb 5,
> 2019, at
> >> 11:33
> >> > > PM, Alex
> >> > > > Harui
> >> > > > > >> >>
> >> <aharui@adobe.com.INVALID
> >> > > > > >> >>>>
> >> > > > > >> >>>>>> wrote:
> >> > > > > >> >>>>>>>
> >> > > > > >> >>>>>>> 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" <
> >> > > > > >> >>
> >> piotrzarzycki21@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.lists@gmail.com
> >> > > > > >> >>> wrote:
> >> > > > > >> >>>>>>>
> >> > > > > >> >>>>>>>> A big +1
> from me!
> >> > > > > >> >>>>>>>>
> >> > > > > >> >>>>>>>> Looking
> forward!
> >> > > > > >> >>>>>>>>
> >> > > > > >> >>>>>>>>> On Feb 5,
> 2019,
> >> at 9:34
> >> > > PM, Alex
> >> > > > Harui
> >> > > > > >> >>>
> >> <ah...@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
> >> > > > >
> >> >
> >>
> >>
> >>
>
>
>
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
OK, I will wait to see your commit emails. I will do some other things like the wiki doc.
-Alex
On 6/10/19, 8:06 PM, "Greg Dove" <gr...@gmail.com> wrote:
Hi Alex, I guess you might be back on Royale about now. Just a heads up: I
am about 20-30 mins max from merging in what I have. Hope that's still
ok... please let me know if not.
Thanks,
-Greg
On Tue, Jun 11, 2019 at 7:51 AM Greg Dove <gr...@gmail.com> wrote:
>
> Thanks Alex - I'll try to hit the window, much appreciated!
>
>
> On Tue, Jun 11, 2019 at 6:57 AM Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
>> Hi Greg,
>>
>> It turns out I have a "split shift" today. I'm stopping work for the
>> next 7 or 8 hours then will get around to the merge. So if you can get
>> your changes merged in that amount of time, then I will wait for you and
>> deal with any merge conflicts (there are almost certain to be some).
>>
>> -Alex
>>
>> On 6/10/19, 11:46 AM, "Greg Dove" <gr...@gmail.com> wrote:
>>
>> Alex, slightly OT, but in terms of coordination: fyi I am also very
>> close
>> to merging the language improvements branch into develop. As I already
>> mentioned elsewhere, I was hoping to do that a couple of days back,
>> but
>> some recent things also took me a little longer than expected (I have
>> additional local changes/fixes not yet in remote branch) . I was
>> planning
>> to merge that today also.
>>
>> However, I will wait until after your merge, so I'm hoping you can get
>> yours in today (if not, I will wait). I will probably put mine in as a
>> squashed commit after yours.
>>
>>
>> On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <
>> piotrzarzycki21@gmail.com>
>> wrote:
>>
>> > Hi Alex,
>> >
>> > Many thanks for that! I will try to be RM. I will have some
>> dedicated time
>> > for that. I will wait for your instruction and merge to develop.
>> >
>> > Thanks,
>> > Piotr
>> >
>> >
>> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui <ah...@adobe.com.invalid>
>> wrote:
>> >
>> > > Well, that turned out to be much more time-consuming than I
>> expected, but
>> > > we can now create identical release artifacts on Mac and Win. I
>> am
>> > hopeful
>> > > this effort will pay off not only now in having other folks
>> generate
>> > > releases, but also in the future if signed binaries become a
>> requirement.
>> > >
>> > > There continues to be a lot of distractions in my life that can
>> cause
>> > > delays, but I hope to merge the release_practice branches into
>> develop
>> > over
>> > > the next day or two and figure out where in the wiki to document
>> the
>> > > release process. So, now is the time for one or more people to
>> step up
>> > to
>> > > be the RMs for 0.9.6 and help debug and improve the process.
>> > >
>> > > I am going to try very hard not to "own" the process. If
>> something goes
>> > > wrong, I am going to ask others to try to debug and fix it first
>> because
>> > it
>> > > is in the project's best interests for others to truly understand
>> how
>> > this
>> > > stuff works.
>> > >
>> > > Thanks,
>> > > -Alex
>> > >
>> > > On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID>
>> wrote:
>> > >
>> > > It has turned out to be harder than expected to get the same
>> binaries
>> > > on Mac and Win. I now have the identical binaries for
>> royale-compiler
>> > and
>> > > royale-typedefs Maven artifacts and am starting on royale-asjs.
>> I might
>> > > get lucky and the changes that fixed royale-typedefs SWCs will
>> magically
>> > > get the royale-asjs SWCs to match. Then we have to make the Ant
>> > artifacts
>> > > match.
>> > >
>> > > There have been a lot of distractions in my non-work life
>> which has
>> > > also impeded progress. I hope to make much progress this coming
>> week and
>> > > if we're lucky, I will be asking for a volunteer (or volunteers)
>> to test
>> > > drive all of this stuff and be the RM for 0.9.6. I am not going
>> to be
>> > the
>> > > RM.
>> > >
>> > > -Alex
>> > >
>> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
>> piotrzarzycki21@gmail.com>
>> > > wrote:
>> > >
>> > > Hi Alex,
>> > >
>> > > It's been a while since you have started effort with
>> automating
>> > > build.
>> > > Where are you with that ? Are we closer to started 0.9.6.
>> Do you
>> > > need any
>> > > help with this ?
>> > >
>> > > Thanks,
>> > > Piotr
>> > >
>> > > wt., 2 kwi 2019 o 19:30 Alex Harui
>> <ah...@adobe.com.invalid>
>> > > napisał(a):
>> > >
>> > > > Update:
>> > > >
>> > > > In order to make verification of binary release packages
>> > created
>> > > on the
>> > > > server easier, I have made changes to our build scripts
>> and
>> > > tools to try to
>> > > > generate reproducible binaries. I've seen two
>> different builds
>> > > compare on
>> > > > my Mac. The next challenge will be to see if the
>> server can
>> > > build a
>> > > > package on Windows that will compare on Mac.
>> > > >
>> > > > One of the changes I needed to make is to JBurg. The
>> version
>> > of
>> > > JBurg we
>> > > > use generates method names including a hash that doesn't
>> > > reproduce the same
>> > > > name each time. I have changes to JBurg ready, however
>> JBurg
>> > is
>> > > currently
>> > > > under CPL which is category B. We only need one file,
>> we don't
>> > > need or
>> > > > want all of JBurg at this time. The one JBurg file is
>> jointly
>> > > owned by
>> > > > Adobe and Tom Harwood. I've contact Tom and he will be
>> filing
>> > > an ICLA and
>> > > > has given me permission to commit the lines he owns in
>> that one
>> > > file.
>> > > >
>> > > > This is the revision of the file that will be donated by
>> > > Tom/Adobe.
>> > > >
>> > > >
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=VS1za1vOQhtlKlK4Tdgq3ej04OlhFoYfHziyNbgOIN4%3D&reserved=0
>> > > >
>> > > > Once this file goes in with the changes to keep the
>> method
>> > names
>> > > the same,
>> > > > there will be more tweaks to the release tasks and then
>> we can
>> > > try cutting
>> > > > a release. I'm thinking we'll be at that point in
>> early May,
>> > so
>> > > now is the
>> > > > time to get stuff in for the 0.9.6 release.
>> > > >
>> > > > Thanks,
>> > > > -Alex
>> > > >
>> > > > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com>
>> wrote:
>> > > >
>> > > > I would much rather have others find and fix issues
>> > > themselves. That
>> > > > way, more people than just me will know how to maintain
>> the
>> > > system. It
>> > > > actually turns out that, IMO, a group of people can
>> work on the
>> > > release.
>> > > > There are 14 steps. Literally, 14 different people
>> could
>> > > execute one step
>> > > > each.
>> > > >
>> > > > My 2 cents,
>> > > > -Alex
>> > > >
>> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
>> > carlosrovira@apache.org>
>> > > wrote:
>> > > >
>> > > > Hi Alex,
>> > > >
>> > > > amazing work! congrats to reach to this point!
>> :)
>> > > >
>> > > > I need to put my head on all of this, but count
>> on me
>> > to
>> > > be a RM.
>> > > > I think
>> > > > the best thing should be that you be the first
>> RM to
>> > try
>> > > your own
>> > > > development at least for the first time, and
>> then the
>> > > rest of us
>> > > > will
>> > > > follow you on the next releases. With all this
>> on place
>> > > we maybe
>> > > > could
>> > > > release once a month or every two months...
>> > > >
>> > > > Thanks for doing this :)
>> > > >
>> > > > Carlos
>> > > >
>> > > >
>> > > > El vie., 8 mar. 2019 a las 1:55, Alex Harui
>> > > > (<ah...@adobe.com.invalid>)
>> > > > escribió:
>> > > >
>> > > > > OK, I've now seen Jenkins perform the steps
>> to build
>> > > the release
>> > > > > artifacts. Folks interested in Docker-izing
>> the
>> > steps
>> > > are
>> > > > welcome to look
>> > > > > at the jobs on the "Royale Release" tab on
>> the CI
>> > > server.
>> > > > >
>> > > >
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=LfWCyCaClCVgfeINn4%2B%2Bk%2FSVUFXvgyV7QxMtx4B%2B%2Fu0%3D&reserved=0
>> > > > >
>> > > > > These steps assume that the RM can run the
>> basic
>> > Maven
>> > > and Ant
>> > > > build on
>> > > > > the RM's computer. I think that's a fair
>> requirement
>> > > since all
>> > > > of us on the
>> > > > > PMC need to able to do that to build the RC
>> in order
>> > > to vote on
>> > > > it.
>> > > > > Jenkins does other tasks like run the Maven
>> release
>> > > plugin
>> > > > steps.
>> > > > >
>> > > > > Currently that results in binaries on Jenkins
>> that
>> > are
>> > > > downloaded to the
>> > > > > RM's computer. These binaries need to be
>> verified by
>> > > the RM
>> > > > which is the
>> > > > > next phase I will be starting on now. The RM
>> > verifies
>> > > the bits
>> > > > and then
>> > > > > PGP signs them. And then the bits are
>> uploaded off
>> > > the RM's
>> > > > computer to
>> > > > > Maven Staging or dist.a.o/dev. If that
>> uploading
>> > > turns out to
>> > > > be a point
>> > > > > of failure, we have the option of having
>> Jenkins
>> > > upload the big
>> > > > files and
>> > > > > have the RM only upload PGP signature files.
>> Or
>> > > finding a way
>> > > > for Jenkins
>> > > > > to get the signature files from the RM. The
>> uploads
>> > > worked fine
>> > > > for me,
>> > > > > but then again, so did the old script's
>> uploads.
>> > > > >
>> > > > > Therefore, once I get the binary verification
>> phase
>> > > completed, I
>> > > > think
>> > > > > someone other than me should be the RM and
>> try to use
>> > > these
>> > > > steps to
>> > > > > generate the release and help debug the
>> process for
>> > > the next
>> > > > RM. So,
>> > > > > please try to carve out some time to be the
>> RM. One
>> > > advantage
>> > > > of doing
>> > > > > most of the work on Jenkins is that it frees
>> up my
>> > > computer to
>> > > > do other
>> > > > > things while Jenkins is cranking away.
>> > > > >
>> > > > > I think we're at least a week away from binary
>> > > verification,
>> > > > maybe two, so
>> > > > > it is time to start thinking about what is
>> going in
>> > > this release.
>> > > > >
>> > > > > Thanks,
>> > > > > -Alex
>> > > > >
>> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
>> > > <ah...@adobe.com.INVALID>
>> > > > wrote:
>> > > > >
>> > > > > In case you haven't guessed, I'm testing
>> out
>> > > Jenkins and its
>> > > > ability
>> > > > > to create the artifacts and send emails.
>> Please
>> > > ignore any
>> > > > email that
>> > > > > looks like a vote or discuss thread.
>> > > > >
>> > > > > Thanks,
>> > > > > -Alex
>> > > > >
>> > > > > On 2/10/19, 8:44 PM, "Alex Harui"
>> > > <ah...@adobe.com.INVALID>
>> > > > wrote:
>> > > > >
>> > > > > Om,
>> > > > >
>> > > > > Well, that's what I used for the last
>> > > release. I'm sure
>> > > > there is
>> > > > > probably some inaccuracy in it.
>> > > > >
>> > > > > That said, I'm abandoning that
>> document and
>> > > taking a new
>> > > > angle
>> > > > > because that document presumed that the
>> release
>> > > manager was
>> > > > trying to
>> > > > > create a release on his/her computer. I've
>> given up
>> > > on that and
>> > > > working on
>> > > > > making releases from a shared computer for the
>> > reasons
>> > > I've
>> > > > stated
>> > > > > upthread. I hope to make some progress on
>> that this
>> > > week.
>> > > > >
>> > > > > The key difference is that the new
>> angle does
>> > > not
>> > > > presume that you
>> > > > > have Git SSH and PGP signatures all set up on
>> some
>> > > computer. I
>> > > > have not
>> > > > > looked into how Docker would handle that. You
>> > > certainly
>> > > > wouldn't want the
>> > > > > Docker image to contain your SSH or PGP
>> keys/creds.
>> > > And if the
>> > > > Docker
>> > > > > image doesn't, then that is another stumbling
>> block
>> > > for future
>> > > > RMs.
>> > > > >
>> > > > > The other key difference is that the
>> old
>> > > script presumed
>> > > > you could
>> > > > > create the 3 release in 3 huge "easy" steps.
>> We've
>> > > seen that is
>> > > > only true
>> > > > > for me. So the new angle creates many
>> discrete steps
>> > > managed by
>> > > > Jenkins.
>> > > > >
>> > > > > So, it is up to you to decide what
>> you want
>> > to
>> > > > "Docker-ize". You
>> > > > > can try to Docker-ize the current 3 big
>> steps, so RMs
>> > > can try to
>> > > > run it on
>> > > > > their systems, but I'd bet they will just
>> faiI due to
>> > > network
>> > > > issues. I
>> > > > > would be interested in using Docker to make
>> each of
>> > > these many
>> > > > discrete
>> > > > > steps portable to another server. I'm not
>> going to
>> > > involve
>> > > > Docker at this
>> > > > > point. My main goal is just to see if I can
>> create a
>> > > workflow
>> > > > of many
>> > > > > discrete steps that isn't horribly painful.
>> Once we
>> > > see what
>> > > > these steps
>> > > > > turn out to be, then we can worry about server
>> > > portability of
>> > > > those steps.
>> > > > >
>> > > > > Either way, we want to know about
>> running
>> > > > Browser+Selenium for
>> > > > > sure. And maybe FlashPlayerDebugger or AIR.
>> I would
>> > > want to
>> > > > know, for
>> > > > > example, how you debug a failing checkintest
>> in a
>> > > Docker
>> > > > container.
>> > > > >
>> > > > > Thanks,
>> > > > > -Alex
>> > > > >
>> > > > >
>> > > > > On 2/10/19, 5:18 PM, "OmPrakash
>> Muppirala" <
>> > > > bigosmallm@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > Alex,
>> > > > >
>> > > > > Just to be clear, I am following
>> the
>> > steps
>> > > from here
>> > > > to try
>> > > > > and setup a
>> > > > > docker container.
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=Lhm0hudN8Nbx%2F6Lnmz0Wlus3EpV1o1h8XWBzBUoEWOA%3D&reserved=0
>> > > > >
>> > > > > Is this doc up to date?
>> > > > >
>> > > > > Thanks,
>> > > > > Om
>> > > > >
>> > > > > On Wed, Feb 6, 2019 at 12:02 PM
>> OmPrakash
>> > > Muppirala <
>> > > > > bigosmallm@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > > One approach is to have each
>> step in
>> > the
>> > > process
>> > > > spin up a
>> > > > > docker image.
>> > > > > > And use docker-compose to run
>> each
>> > > step. All the
>> > > > images can
>> > > > > be made to
>> > > > > > share a common volume where all
>> the
>> > > artifacts are
>> > > > stored
>> > > > > across steps.
>> > > > > >
>> > > > > > You are right about the
>> networking
>> > issue
>> > > though.
>> > > > Any
>> > > > > network related
>> > > > > > failure that occurs on the host
>> machine
>> > > will most
>> > > > likely
>> > > > > occur in the
>> > > > > > docker container. Although, I
>> am not
>> > > clear how we
>> > > > can
>> > > > > guarantee that the
>> > > > > > same issues will not occur on
>> the
>> > > Jenkins server.
>> > > > I mean,
>> > > > > what is special
>> > > > > > about the Jenkins server that
>> makes it
>> > > immune to
>> > > > these
>> > > > > networking issues?
>> > > > > >
>> > > > > > Thanks,
>> > > > > > Om
>> > > > > >
>> > > > > > On Wed, Feb 6, 2019 at 11:48 AM
>> Alex
>> > > Harui
>> > > > > <ah...@adobe.com.invalid>
>> > > > > > wrote:
>> > > > > >
>> > > > > >> Again, I don't know anything
>> about
>> > > Docker, but
>> > > > before we
>> > > > > spend a lot of
>> > > > > >> time on Docker, I also want to
>> point
>> > > out that the
>> > > > process
>> > > > > to create a
>> > > > > >> release cannot really be
>> thought of as
>> > > "one
>> > > > application".
>> > > > > It will be a
>> > > > > >> series of "steps" to run.
>> How many
>> > > steps
>> > > > depends on
>> > > > > whether we think we
>> > > > > >> can isolate enough stuff via
>> Docker to
>> > > be able to
>> > > > run
>> > > > > Docker on the RM's
>> > > > > >> computer instead of some shared
>> > > computer. On a
>> > > > shared
>> > > > > computer there will
>> > > > > >> be dozens of steps because the
>> RM will
>> > > need to
>> > > > enter
>> > > > > passwords to commit
>> > > > > >> stuff. On a local computer I
>> guess
>> > the
>> > > RM can
>> > > > supply
>> > > > > passwords but I think
>> > > > > >> there will be stopping points
>> where
>> > the
>> > > Maven
>> > > > artifacts are
>> > > > > deployed and
>> > > > > >> the staging repo is closed, and
>> > another
>> > > stopping
>> > > > point for
>> > > > > the vote. It
>> > > > > >> seems like Docker works by
>> downloading
>> > > > dependencies. Given
>> > > > > that the
>> > > > > >> problem the RMs had last time
>> involved
>> > > downloads
>> > > > and
>> > > > > uploads, why do we
>> > > > > >> think Docker will really solve
>> this
>> > for
>> > > creating
>> > > > releases
>> > > > > on local machines?
>> > > > > >>
>> > > > > >> The reason to do this on a
>> shared
>> > > machine is so
>> > > > that new
>> > > > > RMs don't have
>> > > > > >> to do as much setup. But then
>> I
>> > wonder
>> > > about the
>> > > > > efficiency of kicking off
>> > > > > >> that many Docker images.
>> Jenkins can
>> > > manage that
>> > > > already.
>> > > > > Does Docker
>> > > > > >> have some sort of similar
>> Dashboard or
>> > > would we
>> > > > use Jenkins
>> > > > > to kick off
>> > > > > >> Docker steps? I can't quite
>> picture
>> > > what is the
>> > > > outermost
>> > > > > >> control/dashboard.
>> > > > > >>
>> > > > > >> -Alex
>> > > > > >>
>> > > > > >> On 2/6/19, 11:03 AM, "Harbs" <
>> > > > harbs.lists@gmail.com> wrote:
>> > > > > >>
>> > > > > >> A quick search turns up
>> this:
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
>> > > > > >> <
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704021103&sdata=J8IhmEsIBh3BwFjBwwd1ePrO3UryuC6gNaZuz3apY7w%3D&reserved=0
>> > > > > >> >
>> > > > > >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=YPCe61GnfpckdNdqMRCDAHXsd3dvMHT3BO157C%2Fufs4%3D&reserved=0
>> > > > > >> <
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=YPCe61GnfpckdNdqMRCDAHXsd3dvMHT3BO157C%2Fufs4%3D&reserved=0
>> > > > > >> >
>> > > > > >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=lsUmIIjQQi5CZhXTvQgd7lPt%2BVL2ApXFbK7i0NbMk1k%3D&reserved=0
>> > > > > >> <
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=lsUmIIjQQi5CZhXTvQgd7lPt%2BVL2ApXFbK7i0NbMk1k%3D&reserved=0
>> > > > > >> >
>> > > > > >>
>> > > > > >> > On Feb 6, 2019, at 8:59
>> PM, Alex
>> > > Harui
>> > > > > <ah...@adobe.com.INVALID>
>> > > > > >> wrote:
>> > > > > >> >
>> > > > > >> > Thanks for volunteering
>> to try
>> > it
>> > > Om. IMO,
>> > > > even more
>> > > > > important
>> > > > > >> than Firefox+Flash is
>> > > SomeBrowser+Selenium. We
>> > > > may also
>> > > > > need to run Adobe
>> > > > > >> AIR's adb. We could probably
>> turn off
>> > > the Flash
>> > > > tests or
>> > > > > replace Flash
>> > > > > >> with AIR.
>> > > > > >> >
>> > > > > >> > Thanks,
>> > > > > >> > -Alex
>> > > > > >> >
>> > > > > >> > On 2/6/19, 10:54 AM,
>> "Carlos
>> > > Rovira" <
>> > > > > carlosrovira@apache.org>
>> > > > > >> wrote:
>> > > > > >> >
>> > > > > >> > Hi Om, that would be
>> great!
>> > > waiting for
>> > > > your
>> > > > > experience with a
>> > > > > >> that! :)
>> > > > > >> >
>> > > > > >> > El mié., 6 feb. 2019
>> a las
>> > > 19:31,
>> > > > OmPrakash
>> > > > > Muppirala (<
>> > > > > >> bigosmallm@gmail.com>)
>> > > > > >> > escribió:
>> > > > > >> >
>> > > > > >> >> Yes, I agree with Alex
>> about
>> > not
>> > > being
>> > > > able to run
>> > > > > UI out of docker
>> > > > > >> >> containers. I never
>> thought of
>> > > the
>> > > > checkintests
>> > > > > when I made the
>> > > > > >> >> suggestion.
>> > > > > >> >>
>> > > > > >> >> The firefox-flash image
>> that
>> > > Yishay
>> > > > pointed out
>> > > > > looks promising.
>> > > > > >> I will
>> > > > > >> >> poke around with it and
>> see if
>> > > that works
>> > > > for us.
>> > > > > >> >>
>> > > > > >> >> Thanks,
>> > > > > >> >> Om
>> > > > > >> >>
>> > > > > >> >> On Wed, Feb 6, 2019 at
>> 12:41 AM
>> > > Yishay
>> > > > Weiss <
>> > > > > >> yishayjobs@hotmail.com>
>> > > > > >> >> wrote:
>> > > > > >> >>
>> > > > > >> >>> I’ll let Om or someone
>> else
>> > > with docker
>> > > > experience
>> > > > > tell us if
>> > > > > >> this [1] is
>> > > > > >> >>> relevant.
>> > > > > >> >>>
>> > > > > >> >>>
>> > > > > >> >>>
>> > > > > >> >>> [1]
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=L6e5%2FCo%2BOzdzvR3QxWvKa7Yg%2BkTw00Afeq24%2B11PGeU%3D&reserved=0
>> > > > > >> >>>
>> > > > > >> >>>
>> > > > > >> >>>
>> > > > > >> >>>
>> > ________________________________
>> > > > > >> >>> From: Alex Harui
>> > > <aharui@adobe.com.INVALID
>> > > > >
>> > > > > >> >>> Sent: Wednesday,
>> February 6,
>> > > 2019
>> > > > 10:05:54 AM
>> > > > > >> >>> To:
>> dev@royale.apache.org
>> > > > > >> >>> Subject: Re: 0.9.6
>> Release
>> > > > > >> >>>
>> > > > > >> >>> I don't anything about
>> docker,
>> > > but in 15
>> > > > minutes of
>> > > > > reading I ran
>> > > > > >> into
>> > > > > >> >>> this:
>> > > > > >> >>>
>> > > > > >> >>>
>> > > > > >> >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=TLSgOkYEaTxxr%2B7TlB%2BOJVt68S2pOH%2FVOAUDtvFYWWE%3D&reserved=0
>> > > > > >> >>>
>> > > > > >> >>> Which says: Docker
>> can't " Run
>> > > > applications with
>> > > > > graphical
>> > > > > >> interfaces".
>> > > > > >> >>> If you want Royale to
>> use
>> > > Docker for
>> > > > releases, show
>> > > > > that it can
>> > > > > >> run
>> > > > > >> >>> checkintests with
>> Flash and
>> > the
>> > > Browser.
>> > > > Then I
>> > > > > will look into
>> > > > > >> it more.
>> > > > > >> >>>
>> > > > > >> >>> The highest level goal
>> is to
>> > > make it as
>> > > > easy as
>> > > > > possible for
>> > > > > >> someone to
>> > > > > >> >>> volunteer to be an
>> RM. Any
>> > > requirement
>> > > > of "install
>> > > > > this (Docker,
>> > > > > >> etc) on
>> > > > > >> >>> your computer" is, IMO,
>> > another
>> > > barrier
>> > > > to entry.
>> > > > > Yeah, RMs will
>> > > > > >> have to
>> > > > > >> >>> have Maven installed
>> and maybe
>> > > Ant, but
>> > > > you should
>> > > > > already have
>> > > > > >> those
>> > > > > >> >>> installed to be a
>> > committer/PMC
>> > > member.
>> > > > > >> >>>
>> > > > > >> >>> That said, a good
>> takeaway
>> > from
>> > > the
>> > > > Docker idea is
>> > > > > to try to find
>> > > > > >> a way
>> > > > > >> >> to
>> > > > > >> >>> make an "Image" of
>> whatever we
>> > > end up
>> > > > with on
>> > > > > whatever server we
>> > > > > >> end up
>> > > > > >> >>> using so if the image
>> can be
>> > > copied and
>> > > > used on
>> > > > > other servers.
>> > > > > >> I'm not
>> > > > > >> >>> exactly sure how to do
>> that
>> > > with Azure,
>> > > > which hosts
>> > > > > my CI
>> > > > > >> server. I will
>> > > > > >> >>> spend a few more
>> minutes
>> > > researching that.
>> > > > > >> >>>
>> > > > > >> >>> I could not quickly
>> find any
>> > > way to get a
>> > > > free VM
>> > > > > on Azure or AWS
>> > > > > >> that
>> > > > > >> >>> isn't a
>> > > > free-trial-start-paying-after-a-year. So,
>> > > > > unless someone
>> > > > > >> comes
>> > > > > >> >> up
>> > > > > >> >>> with a free server we
>> can use
>> > > "forever",
>> > > > I'm going
>> > > > > to just start
>> > > > > >> with my
>> > > > > >> >>> Azure VM.
>> > > > > >> >>>
>> > > > > >> >>> -Alex
>> > > > > >> >>>
>> > > > > >> >>> On 2/5/19, 10:59 PM,
>> "Carlos
>> > > Rovira" <
>> > > > > carlosrovira@apache.org>
>> > > > > >> wrote:
>> > > > > >> >>>
>> > > > > >> >>> Hi.
>> > > > > >> >>>
>> > > > > >> >>> the plan sounds
>> very good
>> > to
>> > > me. Just
>> > > > my 2
>> > > > > thoughts on this:
>> > > > > >> >>>
>> > > > > >> >>> 1.- As I was
>> reading I was
>> > > thinking as
>> > > > well on
>> > > > > something like
>> > > > > >> Docker
>> > > > > >> >>> and
>> > > > > >> >>> see Om as well
>> thinking on
>> > > the same.
>> > > > Maybe is
>> > > > > the way to this
>> > > > > >> with
>> > > > > >> >> the
>> > > > > >> >>> actual technology.
>> Seems
>> > VMs
>> > > are
>> > > > stepping out a
>> > > > > bit this days
>> > > > > >> in
>> > > > > >> >> favor
>> > > > > >> >>> of
>> > > > > >> >>> things like Docker.
>> Maybe
>> > > the same did
>> > > > Git over
>> > > > > Svn, and today
>> > > > > >> Svn is
>> > > > > >> >>> an
>> > > > > >> >>> old remembrance. I
>> must say
>> > > that I
>> > > > have no
>> > > > > experience with
>> > > > > >> Docker, so
>> > > > > >> >>> doing
>> > > > > >> >>> that will require
>> acquire
>> > > that
>> > > > knowledge, but
>> > > > > seems it could
>> > > > > >> be worth
>> > > > > >> >>> it.
>> > > > > >> >>>
>> > > > > >> >>> 2.- Maybe is not
>> possible,
>> > > but I want
>> > > > to propose
>> > > > > to do this
>> > > > > >> work I a
>> > > > > >> >>> separate branch, so
>> it
>> > could
>> > > be in
>> > > > parallel to
>> > > > > other
>> > > > > >> developments. I
>> > > > > >> >>> think
>> > > > > >> >>> work over develop is
>> > > practical if
>> > > > there's
>> > > > > something tiny that
>> > > > > >> could
>> > > > > >> >> be
>> > > > > >> >>> done
>> > > > > >> >>> in a commit. But as
>> we need
>> > > more than
>> > > > one, or is
>> > > > > a long
>> > > > > >> process (like
>> > > > > >> >>> this), chances are
>> to make
>> > > develop
>> > > > branch
>> > > > > unstable and even
>> > > > > >> for some
>> > > > > >> >>> days.
>> > > > > >> >>> I think we should
>> try to
>> > > avoid that
>> > > > scenario,
>> > > > > and branches are
>> > > > > >> the
>> > > > > >> >> best
>> > > > > >> >>> way. If we do this
>> way,
>> > > we'll benefit
>> > > > of more
>> > > > > reliable develop
>> > > > > >> >> branch.
>> > > > > >> >>>
>> > > > > >> >>> Thanks and good to
>> know of
>> > > this plan :)
>> > > > > >> >>>
>> > > > > >> >>> Carlos
>> > > > > >> >>>
>> > > > > >> >>>
>> > > > > >> >>> El mar., 5 feb.
>> 2019 a las
>> > > 23:19,
>> > > > Harbs (<
>> > > > > >> harbs.lists@gmail.com>)
>> > > > > >> >>> escribió:
>> > > > > >> >>>
>> > > > > >> >>>> I’ve never used Docker
>> > myself,
>> > > but that
>> > > > might be a
>> > > > > good plan.
>> > > > > >> >>>>
>> > > > > >> >>>>> On Feb 6, 2019, at
>> 12:07 AM,
>> > > OmPrakash
>> > > > Muppirala <
>> > > > > >> >>> bigosmallm@gmail.com>
>> > > > > >> >>>> wrote:
>> > > > > >> >>>>>
>> > > > > >> >>>>> I was wondering if
>> we can
>> > use
>> > > docker
>> > > > images to
>> > > > > setup and seal
>> > > > > >> the
>> > > > > >> >>> RM
>> > > > > >> >>>>> environment. Then
>> other RMs
>> > > simply
>> > > > need to run
>> > > > > the image
>> > > > > >> locally
>> > > > > >> >>> and run
>> > > > > >> >>>>> the release
>> scripts. Might
>> > > be easier.
>> > > > If folks
>> > > > > like this plan,
>> > > > > >> >> I
>> > > > > >> >>> can
>> > > > > >> >>>> try
>> > > > > >> >>>>> to put something
>> together.
>> > > > > >> >>>>>
>> > > > > >> >>>>> Thanks,
>> > > > > >> >>>>> Om
>> > > > > >> >>>>>
>> > > > > >> >>>>> On Tue, Feb 5, 2019
>> at 1:40
>> > > PM Harbs <
>> > > > > harbs.lists@gmail.com>
>> > > > > >> >>> wrote:
>> > > > > >> >>>>>
>> > > > > >> >>>>>> In a recent
>> discussion, it
>> > > looks like
>> > > > other
>> > > > > projects have
>> > > > > >> gotten
>> > > > > >> >>>> resources
>> > > > > >> >>>>>> from AWS.
>> > > > > >> >>>>>>
>> > > > > >> >>>>>> Whatever service we
>> use,
>> > > could setup a
>> > > > “shared”
>> > > > > Royale account
>> > > > > >> >>> that all
>> > > > > >> >>>>>> PMC members could
>> have
>> > > access to.
>> > > > > >> >>>>>>
>> > > > > >> >>>>>> I don’t know if
>> there’s
>> > some
>> > > way we
>> > > > could
>> > > > > leverage Gitlab’s
>> > > > > >> >>> integration
>> > > > > >> >>>>>> pipelines
>> > > > > >> >>>
>> > > > > >> >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=rSudm9PhsVDHugk2T5zj%2BjDLlE8Ayx2tw3wLnpFnH0g%3D&reserved=0
>> > > > > >> >>> <
>> > > > > >> >>>>>>
>> > > > > >> >>>
>> > > > > >> >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C5b308b70316a40dd04cd08d6ee19bec0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636958191704031094&sdata=rSudm9PhsVDHugk2T5zj%2BjDLlE8Ayx2tw3wLnpFnH0g%3D&reserved=0
>> > > > > >> >>>>
>> > > > > >> >>>>>>
>> > > > > >> >>>>>>> On Feb 5, 2019, at
>> 11:33
>> > > PM, Alex
>> > > > Harui
>> > > > > >> >>
>> <aharui@adobe.com.INVALID
>> > > > > >> >>>>
>> > > > > >> >>>>>> wrote:
>> > > > > >> >>>>>>>
>> > > > > >> >>>>>>> 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" <
>> > > > > >> >>
>> piotrzarzycki21@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.lists@gmail.com
>> > > > > >> >>> wrote:
>> > > > > >> >>>>>>>
>> > > > > >> >>>>>>>> A big +1 from me!
>> > > > > >> >>>>>>>>
>> > > > > >> >>>>>>>> Looking forward!
>> > > > > >> >>>>>>>>
>> > > > > >> >>>>>>>>> On Feb 5, 2019,
>> at 9:34
>> > > PM, Alex
>> > > > Harui
>> > > > > >> >>>
>> <ah...@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
>> > > > >
>> >
>>
>>
>>
Re: 0.9.6 Release
Posted by Greg Dove <gr...@gmail.com>.
Hi Alex, I guess you might be back on Royale about now. Just a heads up: I
am about 20-30 mins max from merging in what I have. Hope that's still
ok... please let me know if not.
Thanks,
-Greg
On Tue, Jun 11, 2019 at 7:51 AM Greg Dove <gr...@gmail.com> wrote:
>
> Thanks Alex - I'll try to hit the window, much appreciated!
>
>
> On Tue, Jun 11, 2019 at 6:57 AM Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
>> Hi Greg,
>>
>> It turns out I have a "split shift" today. I'm stopping work for the
>> next 7 or 8 hours then will get around to the merge. So if you can get
>> your changes merged in that amount of time, then I will wait for you and
>> deal with any merge conflicts (there are almost certain to be some).
>>
>> -Alex
>>
>> On 6/10/19, 11:46 AM, "Greg Dove" <gr...@gmail.com> wrote:
>>
>> Alex, slightly OT, but in terms of coordination: fyi I am also very
>> close
>> to merging the language improvements branch into develop. As I already
>> mentioned elsewhere, I was hoping to do that a couple of days back,
>> but
>> some recent things also took me a little longer than expected (I have
>> additional local changes/fixes not yet in remote branch) . I was
>> planning
>> to merge that today also.
>>
>> However, I will wait until after your merge, so I'm hoping you can get
>> yours in today (if not, I will wait). I will probably put mine in as a
>> squashed commit after yours.
>>
>>
>> On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <
>> piotrzarzycki21@gmail.com>
>> wrote:
>>
>> > Hi Alex,
>> >
>> > Many thanks for that! I will try to be RM. I will have some
>> dedicated time
>> > for that. I will wait for your instruction and merge to develop.
>> >
>> > Thanks,
>> > Piotr
>> >
>> >
>> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui <ah...@adobe.com.invalid>
>> wrote:
>> >
>> > > Well, that turned out to be much more time-consuming than I
>> expected, but
>> > > we can now create identical release artifacts on Mac and Win. I
>> am
>> > hopeful
>> > > this effort will pay off not only now in having other folks
>> generate
>> > > releases, but also in the future if signed binaries become a
>> requirement.
>> > >
>> > > There continues to be a lot of distractions in my life that can
>> cause
>> > > delays, but I hope to merge the release_practice branches into
>> develop
>> > over
>> > > the next day or two and figure out where in the wiki to document
>> the
>> > > release process. So, now is the time for one or more people to
>> step up
>> > to
>> > > be the RMs for 0.9.6 and help debug and improve the process.
>> > >
>> > > I am going to try very hard not to "own" the process. If
>> something goes
>> > > wrong, I am going to ask others to try to debug and fix it first
>> because
>> > it
>> > > is in the project's best interests for others to truly understand
>> how
>> > this
>> > > stuff works.
>> > >
>> > > Thanks,
>> > > -Alex
>> > >
>> > > On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID>
>> wrote:
>> > >
>> > > It has turned out to be harder than expected to get the same
>> binaries
>> > > on Mac and Win. I now have the identical binaries for
>> royale-compiler
>> > and
>> > > royale-typedefs Maven artifacts and am starting on royale-asjs.
>> I might
>> > > get lucky and the changes that fixed royale-typedefs SWCs will
>> magically
>> > > get the royale-asjs SWCs to match. Then we have to make the Ant
>> > artifacts
>> > > match.
>> > >
>> > > There have been a lot of distractions in my non-work life
>> which has
>> > > also impeded progress. I hope to make much progress this coming
>> week and
>> > > if we're lucky, I will be asking for a volunteer (or volunteers)
>> to test
>> > > drive all of this stuff and be the RM for 0.9.6. I am not going
>> to be
>> > the
>> > > RM.
>> > >
>> > > -Alex
>> > >
>> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
>> piotrzarzycki21@gmail.com>
>> > > wrote:
>> > >
>> > > Hi Alex,
>> > >
>> > > It's been a while since you have started effort with
>> automating
>> > > build.
>> > > Where are you with that ? Are we closer to started 0.9.6.
>> Do you
>> > > need any
>> > > help with this ?
>> > >
>> > > Thanks,
>> > > Piotr
>> > >
>> > > wt., 2 kwi 2019 o 19:30 Alex Harui
>> <ah...@adobe.com.invalid>
>> > > napisał(a):
>> > >
>> > > > Update:
>> > > >
>> > > > In order to make verification of binary release packages
>> > created
>> > > on the
>> > > > server easier, I have made changes to our build scripts
>> and
>> > > tools to try to
>> > > > generate reproducible binaries. I've seen two
>> different builds
>> > > compare on
>> > > > my Mac. The next challenge will be to see if the
>> server can
>> > > build a
>> > > > package on Windows that will compare on Mac.
>> > > >
>> > > > One of the changes I needed to make is to JBurg. The
>> version
>> > of
>> > > JBurg we
>> > > > use generates method names including a hash that doesn't
>> > > reproduce the same
>> > > > name each time. I have changes to JBurg ready, however
>> JBurg
>> > is
>> > > currently
>> > > > under CPL which is category B. We only need one file,
>> we don't
>> > > need or
>> > > > want all of JBurg at this time. The one JBurg file is
>> jointly
>> > > owned by
>> > > > Adobe and Tom Harwood. I've contact Tom and he will be
>> filing
>> > > an ICLA and
>> > > > has given me permission to commit the lines he owns in
>> that one
>> > > file.
>> > > >
>> > > > This is the revision of the file that will be donated by
>> > > Tom/Adobe.
>> > > >
>> > > >
>> > >
>> >
>> https://sourceforge.net/p/jburg/code/ci/66c287943376a74ac791f3d3bf969ab160bf80ff/tree/src/generator/jburg/burg/JBurgGenerator.java
>> > > >
>> > > > Once this file goes in with the changes to keep the
>> method
>> > names
>> > > the same,
>> > > > there will be more tweaks to the release tasks and then
>> we can
>> > > try cutting
>> > > > a release. I'm thinking we'll be at that point in
>> early May,
>> > so
>> > > now is the
>> > > > time to get stuff in for the 0.9.6 release.
>> > > >
>> > > > Thanks,
>> > > > -Alex
>> > > >
>> > > > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com>
>> wrote:
>> > > >
>> > > > I would much rather have others find and fix issues
>> > > themselves. That
>> > > > way, more people than just me will know how to maintain
>> the
>> > > system. It
>> > > > actually turns out that, IMO, a group of people can
>> work on the
>> > > release.
>> > > > There are 14 steps. Literally, 14 different people
>> could
>> > > execute one step
>> > > > each.
>> > > >
>> > > > My 2 cents,
>> > > > -Alex
>> > > >
>> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
>> > carlosrovira@apache.org>
>> > > wrote:
>> > > >
>> > > > Hi Alex,
>> > > >
>> > > > amazing work! congrats to reach to this point!
>> :)
>> > > >
>> > > > I need to put my head on all of this, but count
>> on me
>> > to
>> > > be a RM.
>> > > > I think
>> > > > the best thing should be that you be the first
>> RM to
>> > try
>> > > your own
>> > > > development at least for the first time, and
>> then the
>> > > rest of us
>> > > > will
>> > > > follow you on the next releases. With all this
>> on place
>> > > we maybe
>> > > > could
>> > > > release once a month or every two months...
>> > > >
>> > > > Thanks for doing this :)
>> > > >
>> > > > Carlos
>> > > >
>> > > >
>> > > > El vie., 8 mar. 2019 a las 1:55, Alex Harui
>> > > > (<ah...@adobe.com.invalid>)
>> > > > escribió:
>> > > >
>> > > > > OK, I've now seen Jenkins perform the steps
>> to build
>> > > the release
>> > > > > artifacts. Folks interested in Docker-izing
>> the
>> > steps
>> > > are
>> > > > welcome to look
>> > > > > at the jobs on the "Royale Release" tab on
>> the CI
>> > > server.
>> > > > >
>> > > >
>> > >
>> >
>> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/
>> > > > >
>> > > > > These steps assume that the RM can run the
>> basic
>> > Maven
>> > > and Ant
>> > > > build on
>> > > > > the RM's computer. I think that's a fair
>> requirement
>> > > since all
>> > > > of us on the
>> > > > > PMC need to able to do that to build the RC
>> in order
>> > > to vote on
>> > > > it.
>> > > > > Jenkins does other tasks like run the Maven
>> release
>> > > plugin
>> > > > steps.
>> > > > >
>> > > > > Currently that results in binaries on Jenkins
>> that
>> > are
>> > > > downloaded to the
>> > > > > RM's computer. These binaries need to be
>> verified by
>> > > the RM
>> > > > which is the
>> > > > > next phase I will be starting on now. The RM
>> > verifies
>> > > the bits
>> > > > and then
>> > > > > PGP signs them. And then the bits are
>> uploaded off
>> > > the RM's
>> > > > computer to
>> > > > > Maven Staging or dist.a.o/dev. If that
>> uploading
>> > > turns out to
>> > > > be a point
>> > > > > of failure, we have the option of having
>> Jenkins
>> > > upload the big
>> > > > files and
>> > > > > have the RM only upload PGP signature files.
>> Or
>> > > finding a way
>> > > > for Jenkins
>> > > > > to get the signature files from the RM. The
>> uploads
>> > > worked fine
>> > > > for me,
>> > > > > but then again, so did the old script's
>> uploads.
>> > > > >
>> > > > > Therefore, once I get the binary verification
>> phase
>> > > completed, I
>> > > > think
>> > > > > someone other than me should be the RM and
>> try to use
>> > > these
>> > > > steps to
>> > > > > generate the release and help debug the
>> process for
>> > > the next
>> > > > RM. So,
>> > > > > please try to carve out some time to be the
>> RM. One
>> > > advantage
>> > > > of doing
>> > > > > most of the work on Jenkins is that it frees
>> up my
>> > > computer to
>> > > > do other
>> > > > > things while Jenkins is cranking away.
>> > > > >
>> > > > > I think we're at least a week away from binary
>> > > verification,
>> > > > maybe two, so
>> > > > > it is time to start thinking about what is
>> going in
>> > > this release.
>> > > > >
>> > > > > Thanks,
>> > > > > -Alex
>> > > > >
>> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
>> > > <ah...@adobe.com.INVALID>
>> > > > wrote:
>> > > > >
>> > > > > In case you haven't guessed, I'm testing
>> out
>> > > Jenkins and its
>> > > > ability
>> > > > > to create the artifacts and send emails.
>> Please
>> > > ignore any
>> > > > email that
>> > > > > looks like a vote or discuss thread.
>> > > > >
>> > > > > Thanks,
>> > > > > -Alex
>> > > > >
>> > > > > On 2/10/19, 8:44 PM, "Alex Harui"
>> > > <ah...@adobe.com.INVALID>
>> > > > wrote:
>> > > > >
>> > > > > Om,
>> > > > >
>> > > > > Well, that's what I used for the last
>> > > release. I'm sure
>> > > > there is
>> > > > > probably some inaccuracy in it.
>> > > > >
>> > > > > That said, I'm abandoning that
>> document and
>> > > taking a new
>> > > > angle
>> > > > > because that document presumed that the
>> release
>> > > manager was
>> > > > trying to
>> > > > > create a release on his/her computer. I've
>> given up
>> > > on that and
>> > > > working on
>> > > > > making releases from a shared computer for the
>> > reasons
>> > > I've
>> > > > stated
>> > > > > upthread. I hope to make some progress on
>> that this
>> > > week.
>> > > > >
>> > > > > The key difference is that the new
>> angle does
>> > > not
>> > > > presume that you
>> > > > > have Git SSH and PGP signatures all set up on
>> some
>> > > computer. I
>> > > > have not
>> > > > > looked into how Docker would handle that. You
>> > > certainly
>> > > > wouldn't want the
>> > > > > Docker image to contain your SSH or PGP
>> keys/creds.
>> > > And if the
>> > > > Docker
>> > > > > image doesn't, then that is another stumbling
>> block
>> > > for future
>> > > > RMs.
>> > > > >
>> > > > > The other key difference is that the
>> old
>> > > script presumed
>> > > > you could
>> > > > > create the 3 release in 3 huge "easy" steps.
>> We've
>> > > seen that is
>> > > > only true
>> > > > > for me. So the new angle creates many
>> discrete steps
>> > > managed by
>> > > > Jenkins.
>> > > > >
>> > > > > So, it is up to you to decide what
>> you want
>> > to
>> > > > "Docker-ize". You
>> > > > > can try to Docker-ize the current 3 big
>> steps, so RMs
>> > > can try to
>> > > > run it on
>> > > > > their systems, but I'd bet they will just
>> faiI due to
>> > > network
>> > > > issues. I
>> > > > > would be interested in using Docker to make
>> each of
>> > > these many
>> > > > discrete
>> > > > > steps portable to another server. I'm not
>> going to
>> > > involve
>> > > > Docker at this
>> > > > > point. My main goal is just to see if I can
>> create a
>> > > workflow
>> > > > of many
>> > > > > discrete steps that isn't horribly painful.
>> Once we
>> > > see what
>> > > > these steps
>> > > > > turn out to be, then we can worry about server
>> > > portability of
>> > > > those steps.
>> > > > >
>> > > > > Either way, we want to know about
>> running
>> > > > Browser+Selenium for
>> > > > > sure. And maybe FlashPlayerDebugger or AIR.
>> I would
>> > > want to
>> > > > know, for
>> > > > > example, how you debug a failing checkintest
>> in a
>> > > Docker
>> > > > container.
>> > > > >
>> > > > > Thanks,
>> > > > > -Alex
>> > > > >
>> > > > >
>> > > > > On 2/10/19, 5:18 PM, "OmPrakash
>> Muppirala" <
>> > > > bigosmallm@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > Alex,
>> > > > >
>> > > > > Just to be clear, I am following
>> the
>> > steps
>> > > from here
>> > > > to try
>> > > > > and setup a
>> > > > > docker container.
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> > https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
>> > > > >
>> > > > > Is this doc up to date?
>> > > > >
>> > > > > Thanks,
>> > > > > Om
>> > > > >
>> > > > > On Wed, Feb 6, 2019 at 12:02 PM
>> OmPrakash
>> > > Muppirala <
>> > > > > bigosmallm@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > > One approach is to have each
>> step in
>> > the
>> > > process
>> > > > spin up a
>> > > > > docker image.
>> > > > > > And use docker-compose to run
>> each
>> > > step. All the
>> > > > images can
>> > > > > be made to
>> > > > > > share a common volume where all
>> the
>> > > artifacts are
>> > > > stored
>> > > > > across steps.
>> > > > > >
>> > > > > > You are right about the
>> networking
>> > issue
>> > > though.
>> > > > Any
>> > > > > network related
>> > > > > > failure that occurs on the host
>> machine
>> > > will most
>> > > > likely
>> > > > > occur in the
>> > > > > > docker container. Although, I
>> am not
>> > > clear how we
>> > > > can
>> > > > > guarantee that the
>> > > > > > same issues will not occur on
>> the
>> > > Jenkins server.
>> > > > I mean,
>> > > > > what is special
>> > > > > > about the Jenkins server that
>> makes it
>> > > immune to
>> > > > these
>> > > > > networking issues?
>> > > > > >
>> > > > > > Thanks,
>> > > > > > Om
>> > > > > >
>> > > > > > On Wed, Feb 6, 2019 at 11:48 AM
>> Alex
>> > > Harui
>> > > > > <ah...@adobe.com.invalid>
>> > > > > > wrote:
>> > > > > >
>> > > > > >> Again, I don't know anything
>> about
>> > > Docker, but
>> > > > before we
>> > > > > spend a lot of
>> > > > > >> time on Docker, I also want to
>> point
>> > > out that the
>> > > > process
>> > > > > to create a
>> > > > > >> release cannot really be
>> thought of as
>> > > "one
>> > > > application".
>> > > > > It will be a
>> > > > > >> series of "steps" to run.
>> How many
>> > > steps
>> > > > depends on
>> > > > > whether we think we
>> > > > > >> can isolate enough stuff via
>> Docker to
>> > > be able to
>> > > > run
>> > > > > Docker on the RM's
>> > > > > >> computer instead of some shared
>> > > computer. On a
>> > > > shared
>> > > > > computer there will
>> > > > > >> be dozens of steps because the
>> RM will
>> > > need to
>> > > > enter
>> > > > > passwords to commit
>> > > > > >> stuff. On a local computer I
>> guess
>> > the
>> > > RM can
>> > > > supply
>> > > > > passwords but I think
>> > > > > >> there will be stopping points
>> where
>> > the
>> > > Maven
>> > > > artifacts are
>> > > > > deployed and
>> > > > > >> the staging repo is closed, and
>> > another
>> > > stopping
>> > > > point for
>> > > > > the vote. It
>> > > > > >> seems like Docker works by
>> downloading
>> > > > dependencies. Given
>> > > > > that the
>> > > > > >> problem the RMs had last time
>> involved
>> > > downloads
>> > > > and
>> > > > > uploads, why do we
>> > > > > >> think Docker will really solve
>> this
>> > for
>> > > creating
>> > > > releases
>> > > > > on local machines?
>> > > > > >>
>> > > > > >> The reason to do this on a
>> shared
>> > > machine is so
>> > > > that new
>> > > > > RMs don't have
>> > > > > >> to do as much setup. But then
>> I
>> > wonder
>> > > about the
>> > > > > efficiency of kicking off
>> > > > > >> that many Docker images.
>> Jenkins can
>> > > manage that
>> > > > already.
>> > > > > Does Docker
>> > > > > >> have some sort of similar
>> Dashboard or
>> > > would we
>> > > > use Jenkins
>> > > > > to kick off
>> > > > > >> Docker steps? I can't quite
>> picture
>> > > what is the
>> > > > outermost
>> > > > > >> control/dashboard.
>> > > > > >>
>> > > > > >> -Alex
>> > > > > >>
>> > > > > >> On 2/6/19, 11:03 AM, "Harbs" <
>> > > > harbs.lists@gmail.com> wrote:
>> > > > > >>
>> > > > > >> A quick search turns up
>> this:
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://codingsans.com/blog/selenium-with-docker-testing
>> > > > > >> <
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://codingsans.com/blog/selenium-with-docker-testing
>> > > > > >> >
>> > > > > >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker
>> > > > > >> <
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker
>> > > > > >> >
>> > > > > >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://github.com/SeleniumHQ/docker-selenium
>> > > > > >> <
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://github.com/SeleniumHQ/docker-selenium
>> > > > > >> >
>> > > > > >>
>> > > > > >> > On Feb 6, 2019, at 8:59
>> PM, Alex
>> > > Harui
>> > > > > <ah...@adobe.com.INVALID>
>> > > > > >> wrote:
>> > > > > >> >
>> > > > > >> > Thanks for volunteering
>> to try
>> > it
>> > > Om. IMO,
>> > > > even more
>> > > > > important
>> > > > > >> than Firefox+Flash is
>> > > SomeBrowser+Selenium. We
>> > > > may also
>> > > > > need to run Adobe
>> > > > > >> AIR's adb. We could probably
>> turn off
>> > > the Flash
>> > > > tests or
>> > > > > replace Flash
>> > > > > >> with AIR.
>> > > > > >> >
>> > > > > >> > Thanks,
>> > > > > >> > -Alex
>> > > > > >> >
>> > > > > >> > On 2/6/19, 10:54 AM,
>> "Carlos
>> > > Rovira" <
>> > > > > carlosrovira@apache.org>
>> > > > > >> wrote:
>> > > > > >> >
>> > > > > >> > Hi Om, that would be
>> great!
>> > > waiting for
>> > > > your
>> > > > > experience with a
>> > > > > >> that! :)
>> > > > > >> >
>> > > > > >> > El mié., 6 feb. 2019
>> a las
>> > > 19:31,
>> > > > OmPrakash
>> > > > > Muppirala (<
>> > > > > >> bigosmallm@gmail.com>)
>> > > > > >> > escribió:
>> > > > > >> >
>> > > > > >> >> Yes, I agree with Alex
>> about
>> > not
>> > > being
>> > > > able to run
>> > > > > UI out of docker
>> > > > > >> >> containers. I never
>> thought of
>> > > the
>> > > > checkintests
>> > > > > when I made the
>> > > > > >> >> suggestion.
>> > > > > >> >>
>> > > > > >> >> The firefox-flash image
>> that
>> > > Yishay
>> > > > pointed out
>> > > > > looks promising.
>> > > > > >> I will
>> > > > > >> >> poke around with it and
>> see if
>> > > that works
>> > > > for us.
>> > > > > >> >>
>> > > > > >> >> Thanks,
>> > > > > >> >> Om
>> > > > > >> >>
>> > > > > >> >> On Wed, Feb 6, 2019 at
>> 12:41 AM
>> > > Yishay
>> > > > Weiss <
>> > > > > >> yishayjobs@hotmail.com>
>> > > > > >> >> wrote:
>> > > > > >> >>
>> > > > > >> >>> I’ll let Om or someone
>> else
>> > > with docker
>> > > > experience
>> > > > > tell us if
>> > > > > >> this [1] is
>> > > > > >> >>> relevant.
>> > > > > >> >>>
>> > > > > >> >>>
>> > > > > >> >>>
>> > > > > >> >>> [1]
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://hub.docker.com/r/beli/firefox-flash/
>> > > > > >> >>>
>> > > > > >> >>>
>> > > > > >> >>>
>> > > > > >> >>>
>> > ________________________________
>> > > > > >> >>> From: Alex Harui
>> > > <aharui@adobe.com.INVALID
>> > > > >
>> > > > > >> >>> Sent: Wednesday,
>> February 6,
>> > > 2019
>> > > > 10:05:54 AM
>> > > > > >> >>> To:
>> dev@royale.apache.org
>> > > > > >> >>> Subject: Re: 0.9.6
>> Release
>> > > > > >> >>>
>> > > > > >> >>> I don't anything about
>> docker,
>> > > but in 15
>> > > > minutes of
>> > > > > reading I ran
>> > > > > >> into
>> > > > > >> >>> this:
>> > > > > >> >>>
>> > > > > >> >>>
>> > > > > >> >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> >
>> https://www.channelfutures.com/open-source/when-not-to-use-docker-understanding-the-limitations-of-containers
>> > > > > >> >>>
>> > > > > >> >>> Which says: Docker
>> can't " Run
>> > > > applications with
>> > > > > graphical
>> > > > > >> interfaces".
>> > > > > >> >>> If you want Royale to
>> use
>> > > Docker for
>> > > > releases, show
>> > > > > that it can
>> > > > > >> run
>> > > > > >> >>> checkintests with
>> Flash and
>> > the
>> > > Browser.
>> > > > Then I
>> > > > > will look into
>> > > > > >> it more.
>> > > > > >> >>>
>> > > > > >> >>> The highest level goal
>> is to
>> > > make it as
>> > > > easy as
>> > > > > possible for
>> > > > > >> someone to
>> > > > > >> >>> volunteer to be an
>> RM. Any
>> > > requirement
>> > > > of "install
>> > > > > this (Docker,
>> > > > > >> etc) on
>> > > > > >> >>> your computer" is, IMO,
>> > another
>> > > barrier
>> > > > to entry.
>> > > > > Yeah, RMs will
>> > > > > >> have to
>> > > > > >> >>> have Maven installed
>> and maybe
>> > > Ant, but
>> > > > you should
>> > > > > already have
>> > > > > >> those
>> > > > > >> >>> installed to be a
>> > committer/PMC
>> > > member.
>> > > > > >> >>>
>> > > > > >> >>> That said, a good
>> takeaway
>> > from
>> > > the
>> > > > Docker idea is
>> > > > > to try to find
>> > > > > >> a way
>> > > > > >> >> to
>> > > > > >> >>> make an "Image" of
>> whatever we
>> > > end up
>> > > > with on
>> > > > > whatever server we
>> > > > > >> end up
>> > > > > >> >>> using so if the image
>> can be
>> > > copied and
>> > > > used on
>> > > > > other servers.
>> > > > > >> I'm not
>> > > > > >> >>> exactly sure how to do
>> that
>> > > with Azure,
>> > > > which hosts
>> > > > > my CI
>> > > > > >> server. I will
>> > > > > >> >>> spend a few more
>> minutes
>> > > researching that.
>> > > > > >> >>>
>> > > > > >> >>> I could not quickly
>> find any
>> > > way to get a
>> > > > free VM
>> > > > > on Azure or AWS
>> > > > > >> that
>> > > > > >> >>> isn't a
>> > > > free-trial-start-paying-after-a-year. So,
>> > > > > unless someone
>> > > > > >> comes
>> > > > > >> >> up
>> > > > > >> >>> with a free server we
>> can use
>> > > "forever",
>> > > > I'm going
>> > > > > to just start
>> > > > > >> with my
>> > > > > >> >>> Azure VM.
>> > > > > >> >>>
>> > > > > >> >>> -Alex
>> > > > > >> >>>
>> > > > > >> >>> On 2/5/19, 10:59 PM,
>> "Carlos
>> > > Rovira" <
>> > > > > carlosrovira@apache.org>
>> > > > > >> wrote:
>> > > > > >> >>>
>> > > > > >> >>> Hi.
>> > > > > >> >>>
>> > > > > >> >>> the plan sounds
>> very good
>> > to
>> > > me. Just
>> > > > my 2
>> > > > > thoughts on this:
>> > > > > >> >>>
>> > > > > >> >>> 1.- As I was
>> reading I was
>> > > thinking as
>> > > > well on
>> > > > > something like
>> > > > > >> Docker
>> > > > > >> >>> and
>> > > > > >> >>> see Om as well
>> thinking on
>> > > the same.
>> > > > Maybe is
>> > > > > the way to this
>> > > > > >> with
>> > > > > >> >> the
>> > > > > >> >>> actual technology.
>> Seems
>> > VMs
>> > > are
>> > > > stepping out a
>> > > > > bit this days
>> > > > > >> in
>> > > > > >> >> favor
>> > > > > >> >>> of
>> > > > > >> >>> things like Docker.
>> Maybe
>> > > the same did
>> > > > Git over
>> > > > > Svn, and today
>> > > > > >> Svn is
>> > > > > >> >>> an
>> > > > > >> >>> old remembrance. I
>> must say
>> > > that I
>> > > > have no
>> > > > > experience with
>> > > > > >> Docker, so
>> > > > > >> >>> doing
>> > > > > >> >>> that will require
>> acquire
>> > > that
>> > > > knowledge, but
>> > > > > seems it could
>> > > > > >> be worth
>> > > > > >> >>> it.
>> > > > > >> >>>
>> > > > > >> >>> 2.- Maybe is not
>> possible,
>> > > but I want
>> > > > to propose
>> > > > > to do this
>> > > > > >> work I a
>> > > > > >> >>> separate branch, so
>> it
>> > could
>> > > be in
>> > > > parallel to
>> > > > > other
>> > > > > >> developments. I
>> > > > > >> >>> think
>> > > > > >> >>> work over develop is
>> > > practical if
>> > > > there's
>> > > > > something tiny that
>> > > > > >> could
>> > > > > >> >> be
>> > > > > >> >>> done
>> > > > > >> >>> in a commit. But as
>> we need
>> > > more than
>> > > > one, or is
>> > > > > a long
>> > > > > >> process (like
>> > > > > >> >>> this), chances are
>> to make
>> > > develop
>> > > > branch
>> > > > > unstable and even
>> > > > > >> for some
>> > > > > >> >>> days.
>> > > > > >> >>> I think we should
>> try to
>> > > avoid that
>> > > > scenario,
>> > > > > and branches are
>> > > > > >> the
>> > > > > >> >> best
>> > > > > >> >>> way. If we do this
>> way,
>> > > we'll benefit
>> > > > of more
>> > > > > reliable develop
>> > > > > >> >> branch.
>> > > > > >> >>>
>> > > > > >> >>> Thanks and good to
>> know of
>> > > this plan :)
>> > > > > >> >>>
>> > > > > >> >>> Carlos
>> > > > > >> >>>
>> > > > > >> >>>
>> > > > > >> >>> El mar., 5 feb.
>> 2019 a las
>> > > 23:19,
>> > > > Harbs (<
>> > > > > >> harbs.lists@gmail.com>)
>> > > > > >> >>> escribió:
>> > > > > >> >>>
>> > > > > >> >>>> I’ve never used Docker
>> > myself,
>> > > but that
>> > > > might be a
>> > > > > good plan.
>> > > > > >> >>>>
>> > > > > >> >>>>> On Feb 6, 2019, at
>> 12:07 AM,
>> > > OmPrakash
>> > > > Muppirala <
>> > > > > >> >>> bigosmallm@gmail.com>
>> > > > > >> >>>> wrote:
>> > > > > >> >>>>>
>> > > > > >> >>>>> I was wondering if
>> we can
>> > use
>> > > docker
>> > > > images to
>> > > > > setup and seal
>> > > > > >> the
>> > > > > >> >>> RM
>> > > > > >> >>>>> environment. Then
>> other RMs
>> > > simply
>> > > > need to run
>> > > > > the image
>> > > > > >> locally
>> > > > > >> >>> and run
>> > > > > >> >>>>> the release
>> scripts. Might
>> > > be easier.
>> > > > If folks
>> > > > > like this plan,
>> > > > > >> >> I
>> > > > > >> >>> can
>> > > > > >> >>>> try
>> > > > > >> >>>>> to put something
>> together.
>> > > > > >> >>>>>
>> > > > > >> >>>>> Thanks,
>> > > > > >> >>>>> Om
>> > > > > >> >>>>>
>> > > > > >> >>>>> On Tue, Feb 5, 2019
>> at 1:40
>> > > PM Harbs <
>> > > > > harbs.lists@gmail.com>
>> > > > > >> >>> wrote:
>> > > > > >> >>>>>
>> > > > > >> >>>>>> In a recent
>> discussion, it
>> > > looks like
>> > > > other
>> > > > > projects have
>> > > > > >> gotten
>> > > > > >> >>>> resources
>> > > > > >> >>>>>> from AWS.
>> > > > > >> >>>>>>
>> > > > > >> >>>>>> Whatever service we
>> use,
>> > > could setup a
>> > > > “shared”
>> > > > > Royale account
>> > > > > >> >>> that all
>> > > > > >> >>>>>> PMC members could
>> have
>> > > access to.
>> > > > > >> >>>>>>
>> > > > > >> >>>>>> I don’t know if
>> there’s
>> > some
>> > > way we
>> > > > could
>> > > > > leverage Gitlab’s
>> > > > > >> >>> integration
>> > > > > >> >>>>>> pipelines
>> > > > > >> >>>
>> > > > > >> >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://docs.gitlab.com/ee/ci/README.html
>> > > > > >> >>> <
>> > > > > >> >>>>>>
>> > > > > >> >>>
>> > > > > >> >>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> > https://docs.gitlab.com/ee/ci/README.html
>> > > > > >> >>>>
>> > > > > >> >>>>>>
>> > > > > >> >>>>>>> On Feb 5, 2019, at
>> 11:33
>> > > PM, Alex
>> > > > Harui
>> > > > > >> >>
>> <aharui@adobe.com.INVALID
>> > > > > >> >>>>
>> > > > > >> >>>>>> wrote:
>> > > > > >> >>>>>>>
>> > > > > >> >>>>>>> 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" <
>> > > > > >> >>
>> piotrzarzycki21@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.lists@gmail.com
>> > > > > >> >>> wrote:
>> > > > > >> >>>>>>>
>> > > > > >> >>>>>>>> A big +1 from me!
>> > > > > >> >>>>>>>>
>> > > > > >> >>>>>>>> Looking forward!
>> > > > > >> >>>>>>>>
>> > > > > >> >>>>>>>>> On Feb 5, 2019,
>> at 9:34
>> > > PM, Alex
>> > > > Harui
>> > > > > >> >>>
>> <ah...@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
>> > > > >
>> >
>>
>>
>>
Re: 0.9.6 Release
Posted by Greg Dove <gr...@gmail.com>.
Thanks Alex - I'll try to hit the window, much appreciated!
On Tue, Jun 11, 2019 at 6:57 AM Alex Harui <ah...@adobe.com.invalid> wrote:
> Hi Greg,
>
> It turns out I have a "split shift" today. I'm stopping work for the next
> 7 or 8 hours then will get around to the merge. So if you can get your
> changes merged in that amount of time, then I will wait for you and deal
> with any merge conflicts (there are almost certain to be some).
>
> -Alex
>
> On 6/10/19, 11:46 AM, "Greg Dove" <gr...@gmail.com> wrote:
>
> Alex, slightly OT, but in terms of coordination: fyi I am also very
> close
> to merging the language improvements branch into develop. As I already
> mentioned elsewhere, I was hoping to do that a couple of days back, but
> some recent things also took me a little longer than expected (I have
> additional local changes/fixes not yet in remote branch) . I was
> planning
> to merge that today also.
>
> However, I will wait until after your merge, so I'm hoping you can get
> yours in today (if not, I will wait). I will probably put mine in as a
> squashed commit after yours.
>
>
> On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> wrote:
>
> > Hi Alex,
> >
> > Many thanks for that! I will try to be RM. I will have some
> dedicated time
> > for that. I will wait for your instruction and merge to develop.
> >
> > Thanks,
> > Piotr
> >
> >
> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui <ah...@adobe.com.invalid>
> wrote:
> >
> > > Well, that turned out to be much more time-consuming than I
> expected, but
> > > we can now create identical release artifacts on Mac and Win. I am
> > hopeful
> > > this effort will pay off not only now in having other folks
> generate
> > > releases, but also in the future if signed binaries become a
> requirement.
> > >
> > > There continues to be a lot of distractions in my life that can
> cause
> > > delays, but I hope to merge the release_practice branches into
> develop
> > over
> > > the next day or two and figure out where in the wiki to document
> the
> > > release process. So, now is the time for one or more people to
> step up
> > to
> > > be the RMs for 0.9.6 and help debug and improve the process.
> > >
> > > I am going to try very hard not to "own" the process. If
> something goes
> > > wrong, I am going to ask others to try to debug and fix it first
> because
> > it
> > > is in the project's best interests for others to truly understand
> how
> > this
> > > stuff works.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> > >
> > > It has turned out to be harder than expected to get the same
> binaries
> > > on Mac and Win. I now have the identical binaries for
> royale-compiler
> > and
> > > royale-typedefs Maven artifacts and am starting on royale-asjs. I
> might
> > > get lucky and the changes that fixed royale-typedefs SWCs will
> magically
> > > get the royale-asjs SWCs to match. Then we have to make the Ant
> > artifacts
> > > match.
> > >
> > > There have been a lot of distractions in my non-work life
> which has
> > > also impeded progress. I hope to make much progress this coming
> week and
> > > if we're lucky, I will be asking for a volunteer (or volunteers)
> to test
> > > drive all of this stuff and be the RM for 0.9.6. I am not going
> to be
> > the
> > > RM.
> > >
> > > -Alex
> > >
> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com>
> > > wrote:
> > >
> > > Hi Alex,
> > >
> > > It's been a while since you have started effort with
> automating
> > > build.
> > > Where are you with that ? Are we closer to started 0.9.6.
> Do you
> > > need any
> > > help with this ?
> > >
> > > Thanks,
> > > Piotr
> > >
> > > wt., 2 kwi 2019 o 19:30 Alex Harui
> <ah...@adobe.com.invalid>
> > > napisał(a):
> > >
> > > > Update:
> > > >
> > > > In order to make verification of binary release packages
> > created
> > > on the
> > > > server easier, I have made changes to our build scripts
> and
> > > tools to try to
> > > > generate reproducible binaries. I've seen two different
> builds
> > > compare on
> > > > my Mac. The next challenge will be to see if the
> server can
> > > build a
> > > > package on Windows that will compare on Mac.
> > > >
> > > > One of the changes I needed to make is to JBurg. The
> version
> > of
> > > JBurg we
> > > > use generates method names including a hash that doesn't
> > > reproduce the same
> > > > name each time. I have changes to JBurg ready, however
> JBurg
> > is
> > > currently
> > > > under CPL which is category B. We only need one file,
> we don't
> > > need or
> > > > want all of JBurg at this time. The one JBurg file is
> jointly
> > > owned by
> > > > Adobe and Tom Harwood. I've contact Tom and he will be
> filing
> > > an ICLA and
> > > > has given me permission to commit the lines he owns in
> that one
> > > file.
> > > >
> > > > This is the revision of the file that will be donated by
> > > Tom/Adobe.
> > > >
> > > >
> > >
> >
> https://sourceforge.net/p/jburg/code/ci/66c287943376a74ac791f3d3bf969ab160bf80ff/tree/src/generator/jburg/burg/JBurgGenerator.java
> > > >
> > > > Once this file goes in with the changes to keep the
> method
> > names
> > > the same,
> > > > there will be more tweaks to the release tasks and then
> we can
> > > try cutting
> > > > a release. I'm thinking we'll be at that point in early
> May,
> > so
> > > now is the
> > > > time to get stuff in for the 0.9.6 release.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com>
> wrote:
> > > >
> > > > I would much rather have others find and fix issues
> > > themselves. That
> > > > way, more people than just me will know how to maintain
> the
> > > system. It
> > > > actually turns out that, IMO, a group of people can work
> on the
> > > release.
> > > > There are 14 steps. Literally, 14 different people could
> > > execute one step
> > > > each.
> > > >
> > > > My 2 cents,
> > > > -Alex
> > > >
> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > > wrote:
> > > >
> > > > Hi Alex,
> > > >
> > > > amazing work! congrats to reach to this point! :)
> > > >
> > > > I need to put my head on all of this, but count
> on me
> > to
> > > be a RM.
> > > > I think
> > > > the best thing should be that you be the first
> RM to
> > try
> > > your own
> > > > development at least for the first time, and
> then the
> > > rest of us
> > > > will
> > > > follow you on the next releases. With all this
> on place
> > > we maybe
> > > > could
> > > > release once a month or every two months...
> > > >
> > > > Thanks for doing this :)
> > > >
> > > > Carlos
> > > >
> > > >
> > > > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > > > (<ah...@adobe.com.invalid>)
> > > > escribió:
> > > >
> > > > > OK, I've now seen Jenkins perform the steps to
> build
> > > the release
> > > > > artifacts. Folks interested in Docker-izing
> the
> > steps
> > > are
> > > > welcome to look
> > > > > at the jobs on the "Royale Release" tab on the
> CI
> > > server.
> > > > >
> > > >
> > >
> >
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/
> > > > >
> > > > > These steps assume that the RM can run the
> basic
> > Maven
> > > and Ant
> > > > build on
> > > > > the RM's computer. I think that's a fair
> requirement
> > > since all
> > > > of us on the
> > > > > PMC need to able to do that to build the RC in
> order
> > > to vote on
> > > > it.
> > > > > Jenkins does other tasks like run the Maven
> release
> > > plugin
> > > > steps.
> > > > >
> > > > > Currently that results in binaries on Jenkins
> that
> > are
> > > > downloaded to the
> > > > > RM's computer. These binaries need to be
> verified by
> > > the RM
> > > > which is the
> > > > > next phase I will be starting on now. The RM
> > verifies
> > > the bits
> > > > and then
> > > > > PGP signs them. And then the bits are
> uploaded off
> > > the RM's
> > > > computer to
> > > > > Maven Staging or dist.a.o/dev. If that
> uploading
> > > turns out to
> > > > be a point
> > > > > of failure, we have the option of having
> Jenkins
> > > upload the big
> > > > files and
> > > > > have the RM only upload PGP signature files.
> Or
> > > finding a way
> > > > for Jenkins
> > > > > to get the signature files from the RM. The
> uploads
> > > worked fine
> > > > for me,
> > > > > but then again, so did the old script's
> uploads.
> > > > >
> > > > > Therefore, once I get the binary verification
> phase
> > > completed, I
> > > > think
> > > > > someone other than me should be the RM and try
> to use
> > > these
> > > > steps to
> > > > > generate the release and help debug the
> process for
> > > the next
> > > > RM. So,
> > > > > please try to carve out some time to be the
> RM. One
> > > advantage
> > > > of doing
> > > > > most of the work on Jenkins is that it frees
> up my
> > > computer to
> > > > do other
> > > > > things while Jenkins is cranking away.
> > > > >
> > > > > I think we're at least a week away from binary
> > > verification,
> > > > maybe two, so
> > > > > it is time to start thinking about what is
> going in
> > > this release.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
> > > <ah...@adobe.com.INVALID>
> > > > wrote:
> > > > >
> > > > > In case you haven't guessed, I'm testing
> out
> > > Jenkins and its
> > > > ability
> > > > > to create the artifacts and send emails.
> Please
> > > ignore any
> > > > email that
> > > > > looks like a vote or discuss thread.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 2/10/19, 8:44 PM, "Alex Harui"
> > > <ah...@adobe.com.INVALID>
> > > > wrote:
> > > > >
> > > > > Om,
> > > > >
> > > > > Well, that's what I used for the last
> > > release. I'm sure
> > > > there is
> > > > > probably some inaccuracy in it.
> > > > >
> > > > > That said, I'm abandoning that
> document and
> > > taking a new
> > > > angle
> > > > > because that document presumed that the release
> > > manager was
> > > > trying to
> > > > > create a release on his/her computer. I've
> given up
> > > on that and
> > > > working on
> > > > > making releases from a shared computer for the
> > reasons
> > > I've
> > > > stated
> > > > > upthread. I hope to make some progress on
> that this
> > > week.
> > > > >
> > > > > The key difference is that the new
> angle does
> > > not
> > > > presume that you
> > > > > have Git SSH and PGP signatures all set up on
> some
> > > computer. I
> > > > have not
> > > > > looked into how Docker would handle that. You
> > > certainly
> > > > wouldn't want the
> > > > > Docker image to contain your SSH or PGP
> keys/creds.
> > > And if the
> > > > Docker
> > > > > image doesn't, then that is another stumbling
> block
> > > for future
> > > > RMs.
> > > > >
> > > > > The other key difference is that the
> old
> > > script presumed
> > > > you could
> > > > > create the 3 release in 3 huge "easy" steps.
> We've
> > > seen that is
> > > > only true
> > > > > for me. So the new angle creates many
> discrete steps
> > > managed by
> > > > Jenkins.
> > > > >
> > > > > So, it is up to you to decide what you
> want
> > to
> > > > "Docker-ize". You
> > > > > can try to Docker-ize the current 3 big steps,
> so RMs
> > > can try to
> > > > run it on
> > > > > their systems, but I'd bet they will just faiI
> due to
> > > network
> > > > issues. I
> > > > > would be interested in using Docker to make
> each of
> > > these many
> > > > discrete
> > > > > steps portable to another server. I'm not
> going to
> > > involve
> > > > Docker at this
> > > > > point. My main goal is just to see if I can
> create a
> > > workflow
> > > > of many
> > > > > discrete steps that isn't horribly painful.
> Once we
> > > see what
> > > > these steps
> > > > > turn out to be, then we can worry about server
> > > portability of
> > > > those steps.
> > > > >
> > > > > Either way, we want to know about
> running
> > > > Browser+Selenium for
> > > > > sure. And maybe FlashPlayerDebugger or AIR.
> I would
> > > want to
> > > > know, for
> > > > > example, how you debug a failing checkintest
> in a
> > > Docker
> > > > container.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > >
> > > > > On 2/10/19, 5:18 PM, "OmPrakash
> Muppirala" <
> > > > bigosmallm@gmail.com>
> > > > > wrote:
> > > > >
> > > > > Alex,
> > > > >
> > > > > Just to be clear, I am following
> the
> > steps
> > > from here
> > > > to try
> > > > > and setup a
> > > > > docker container.
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
> > > > >
> > > > > Is this doc up to date?
> > > > >
> > > > > Thanks,
> > > > > Om
> > > > >
> > > > > On Wed, Feb 6, 2019 at 12:02 PM
> OmPrakash
> > > Muppirala <
> > > > > bigosmallm@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > One approach is to have each
> step in
> > the
> > > process
> > > > spin up a
> > > > > docker image.
> > > > > > And use docker-compose to run
> each
> > > step. All the
> > > > images can
> > > > > be made to
> > > > > > share a common volume where all
> the
> > > artifacts are
> > > > stored
> > > > > across steps.
> > > > > >
> > > > > > You are right about the
> networking
> > issue
> > > though.
> > > > Any
> > > > > network related
> > > > > > failure that occurs on the host
> machine
> > > will most
> > > > likely
> > > > > occur in the
> > > > > > docker container. Although, I
> am not
> > > clear how we
> > > > can
> > > > > guarantee that the
> > > > > > same issues will not occur on the
> > > Jenkins server.
> > > > I mean,
> > > > > what is special
> > > > > > about the Jenkins server that
> makes it
> > > immune to
> > > > these
> > > > > networking issues?
> > > > > >
> > > > > > Thanks,
> > > > > > Om
> > > > > >
> > > > > > On Wed, Feb 6, 2019 at 11:48 AM
> Alex
> > > Harui
> > > > > <ah...@adobe.com.invalid>
> > > > > > wrote:
> > > > > >
> > > > > >> Again, I don't know anything
> about
> > > Docker, but
> > > > before we
> > > > > spend a lot of
> > > > > >> time on Docker, I also want to
> point
> > > out that the
> > > > process
> > > > > to create a
> > > > > >> release cannot really be
> thought of as
> > > "one
> > > > application".
> > > > > It will be a
> > > > > >> series of "steps" to run.
> How many
> > > steps
> > > > depends on
> > > > > whether we think we
> > > > > >> can isolate enough stuff via
> Docker to
> > > be able to
> > > > run
> > > > > Docker on the RM's
> > > > > >> computer instead of some shared
> > > computer. On a
> > > > shared
> > > > > computer there will
> > > > > >> be dozens of steps because the
> RM will
> > > need to
> > > > enter
> > > > > passwords to commit
> > > > > >> stuff. On a local computer I
> guess
> > the
> > > RM can
> > > > supply
> > > > > passwords but I think
> > > > > >> there will be stopping points
> where
> > the
> > > Maven
> > > > artifacts are
> > > > > deployed and
> > > > > >> the staging repo is closed, and
> > another
> > > stopping
> > > > point for
> > > > > the vote. It
> > > > > >> seems like Docker works by
> downloading
> > > > dependencies. Given
> > > > > that the
> > > > > >> problem the RMs had last time
> involved
> > > downloads
> > > > and
> > > > > uploads, why do we
> > > > > >> think Docker will really solve
> this
> > for
> > > creating
> > > > releases
> > > > > on local machines?
> > > > > >>
> > > > > >> The reason to do this on a
> shared
> > > machine is so
> > > > that new
> > > > > RMs don't have
> > > > > >> to do as much setup. But then I
> > wonder
> > > about the
> > > > > efficiency of kicking off
> > > > > >> that many Docker images.
> Jenkins can
> > > manage that
> > > > already.
> > > > > Does Docker
> > > > > >> have some sort of similar
> Dashboard or
> > > would we
> > > > use Jenkins
> > > > > to kick off
> > > > > >> Docker steps? I can't quite
> picture
> > > what is the
> > > > outermost
> > > > > >> control/dashboard.
> > > > > >>
> > > > > >> -Alex
> > > > > >>
> > > > > >> On 2/6/19, 11:03 AM, "Harbs" <
> > > > harbs.lists@gmail.com> wrote:
> > > > > >>
> > > > > >> A quick search turns up
> this:
> > > > > >>
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> > https://codingsans.com/blog/selenium-with-docker-testing
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > >
> > https://codingsans.com/blog/selenium-with-docker-testing
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> > https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > >
> > https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> > https://github.com/SeleniumHQ/docker-selenium
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > >
> > https://github.com/SeleniumHQ/docker-selenium
> > > > > >> >
> > > > > >>
> > > > > >> > On Feb 6, 2019, at 8:59
> PM, Alex
> > > Harui
> > > > > <ah...@adobe.com.INVALID>
> > > > > >> wrote:
> > > > > >> >
> > > > > >> > Thanks for volunteering
> to try
> > it
> > > Om. IMO,
> > > > even more
> > > > > important
> > > > > >> than Firefox+Flash is
> > > SomeBrowser+Selenium. We
> > > > may also
> > > > > need to run Adobe
> > > > > >> AIR's adb. We could probably
> turn off
> > > the Flash
> > > > tests or
> > > > > replace Flash
> > > > > >> with AIR.
> > > > > >> >
> > > > > >> > Thanks,
> > > > > >> > -Alex
> > > > > >> >
> > > > > >> > On 2/6/19, 10:54 AM,
> "Carlos
> > > Rovira" <
> > > > > carlosrovira@apache.org>
> > > > > >> wrote:
> > > > > >> >
> > > > > >> > Hi Om, that would be
> great!
> > > waiting for
> > > > your
> > > > > experience with a
> > > > > >> that! :)
> > > > > >> >
> > > > > >> > El mié., 6 feb. 2019 a
> las
> > > 19:31,
> > > > OmPrakash
> > > > > Muppirala (<
> > > > > >> bigosmallm@gmail.com>)
> > > > > >> > escribió:
> > > > > >> >
> > > > > >> >> Yes, I agree with Alex
> about
> > not
> > > being
> > > > able to run
> > > > > UI out of docker
> > > > > >> >> containers. I never
> thought of
> > > the
> > > > checkintests
> > > > > when I made the
> > > > > >> >> suggestion.
> > > > > >> >>
> > > > > >> >> The firefox-flash image
> that
> > > Yishay
> > > > pointed out
> > > > > looks promising.
> > > > > >> I will
> > > > > >> >> poke around with it and
> see if
> > > that works
> > > > for us.
> > > > > >> >>
> > > > > >> >> Thanks,
> > > > > >> >> Om
> > > > > >> >>
> > > > > >> >> On Wed, Feb 6, 2019 at
> 12:41 AM
> > > Yishay
> > > > Weiss <
> > > > > >> yishayjobs@hotmail.com>
> > > > > >> >> wrote:
> > > > > >> >>
> > > > > >> >>> I’ll let Om or someone
> else
> > > with docker
> > > > experience
> > > > > tell us if
> > > > > >> this [1] is
> > > > > >> >>> relevant.
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>> [1]
> > > > > >>
> > > > >
> > > >
> > >
> > https://hub.docker.com/r/beli/firefox-flash/
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > ________________________________
> > > > > >> >>> From: Alex Harui
> > > <aharui@adobe.com.INVALID
> > > > >
> > > > > >> >>> Sent: Wednesday,
> February 6,
> > > 2019
> > > > 10:05:54 AM
> > > > > >> >>> To:
> dev@royale.apache.org
> > > > > >> >>> Subject: Re: 0.9.6
> Release
> > > > > >> >>>
> > > > > >> >>> I don't anything about
> docker,
> > > but in 15
> > > > minutes of
> > > > > reading I ran
> > > > > >> into
> > > > > >> >>> this:
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://www.channelfutures.com/open-source/when-not-to-use-docker-understanding-the-limitations-of-containers
> > > > > >> >>>
> > > > > >> >>> Which says: Docker
> can't " Run
> > > > applications with
> > > > > graphical
> > > > > >> interfaces".
> > > > > >> >>> If you want Royale to
> use
> > > Docker for
> > > > releases, show
> > > > > that it can
> > > > > >> run
> > > > > >> >>> checkintests with Flash
> and
> > the
> > > Browser.
> > > > Then I
> > > > > will look into
> > > > > >> it more.
> > > > > >> >>>
> > > > > >> >>> The highest level goal
> is to
> > > make it as
> > > > easy as
> > > > > possible for
> > > > > >> someone to
> > > > > >> >>> volunteer to be an RM.
> Any
> > > requirement
> > > > of "install
> > > > > this (Docker,
> > > > > >> etc) on
> > > > > >> >>> your computer" is, IMO,
> > another
> > > barrier
> > > > to entry.
> > > > > Yeah, RMs will
> > > > > >> have to
> > > > > >> >>> have Maven installed
> and maybe
> > > Ant, but
> > > > you should
> > > > > already have
> > > > > >> those
> > > > > >> >>> installed to be a
> > committer/PMC
> > > member.
> > > > > >> >>>
> > > > > >> >>> That said, a good
> takeaway
> > from
> > > the
> > > > Docker idea is
> > > > > to try to find
> > > > > >> a way
> > > > > >> >> to
> > > > > >> >>> make an "Image" of
> whatever we
> > > end up
> > > > with on
> > > > > whatever server we
> > > > > >> end up
> > > > > >> >>> using so if the image
> can be
> > > copied and
> > > > used on
> > > > > other servers.
> > > > > >> I'm not
> > > > > >> >>> exactly sure how to do
> that
> > > with Azure,
> > > > which hosts
> > > > > my CI
> > > > > >> server. I will
> > > > > >> >>> spend a few more minutes
> > > researching that.
> > > > > >> >>>
> > > > > >> >>> I could not quickly
> find any
> > > way to get a
> > > > free VM
> > > > > on Azure or AWS
> > > > > >> that
> > > > > >> >>> isn't a
> > > > free-trial-start-paying-after-a-year. So,
> > > > > unless someone
> > > > > >> comes
> > > > > >> >> up
> > > > > >> >>> with a free server we
> can use
> > > "forever",
> > > > I'm going
> > > > > to just start
> > > > > >> with my
> > > > > >> >>> Azure VM.
> > > > > >> >>>
> > > > > >> >>> -Alex
> > > > > >> >>>
> > > > > >> >>> On 2/5/19, 10:59 PM,
> "Carlos
> > > Rovira" <
> > > > > carlosrovira@apache.org>
> > > > > >> wrote:
> > > > > >> >>>
> > > > > >> >>> Hi.
> > > > > >> >>>
> > > > > >> >>> the plan sounds very
> good
> > to
> > > me. Just
> > > > my 2
> > > > > thoughts on this:
> > > > > >> >>>
> > > > > >> >>> 1.- As I was reading
> I was
> > > thinking as
> > > > well on
> > > > > something like
> > > > > >> Docker
> > > > > >> >>> and
> > > > > >> >>> see Om as well
> thinking on
> > > the same.
> > > > Maybe is
> > > > > the way to this
> > > > > >> with
> > > > > >> >> the
> > > > > >> >>> actual technology.
> Seems
> > VMs
> > > are
> > > > stepping out a
> > > > > bit this days
> > > > > >> in
> > > > > >> >> favor
> > > > > >> >>> of
> > > > > >> >>> things like Docker.
> Maybe
> > > the same did
> > > > Git over
> > > > > Svn, and today
> > > > > >> Svn is
> > > > > >> >>> an
> > > > > >> >>> old remembrance. I
> must say
> > > that I
> > > > have no
> > > > > experience with
> > > > > >> Docker, so
> > > > > >> >>> doing
> > > > > >> >>> that will require
> acquire
> > > that
> > > > knowledge, but
> > > > > seems it could
> > > > > >> be worth
> > > > > >> >>> it.
> > > > > >> >>>
> > > > > >> >>> 2.- Maybe is not
> possible,
> > > but I want
> > > > to propose
> > > > > to do this
> > > > > >> work I a
> > > > > >> >>> separate branch, so
> it
> > could
> > > be in
> > > > parallel to
> > > > > other
> > > > > >> developments. I
> > > > > >> >>> think
> > > > > >> >>> work over develop is
> > > practical if
> > > > there's
> > > > > something tiny that
> > > > > >> could
> > > > > >> >> be
> > > > > >> >>> done
> > > > > >> >>> in a commit. But as
> we need
> > > more than
> > > > one, or is
> > > > > a long
> > > > > >> process (like
> > > > > >> >>> this), chances are
> to make
> > > develop
> > > > branch
> > > > > unstable and even
> > > > > >> for some
> > > > > >> >>> days.
> > > > > >> >>> I think we should
> try to
> > > avoid that
> > > > scenario,
> > > > > and branches are
> > > > > >> the
> > > > > >> >> best
> > > > > >> >>> way. If we do this
> way,
> > > we'll benefit
> > > > of more
> > > > > reliable develop
> > > > > >> >> branch.
> > > > > >> >>>
> > > > > >> >>> Thanks and good to
> know of
> > > this plan :)
> > > > > >> >>>
> > > > > >> >>> Carlos
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>> El mar., 5 feb. 2019
> a las
> > > 23:19,
> > > > Harbs (<
> > > > > >> harbs.lists@gmail.com>)
> > > > > >> >>> escribió:
> > > > > >> >>>
> > > > > >> >>>> I’ve never used Docker
> > myself,
> > > but that
> > > > might be a
> > > > > good plan.
> > > > > >> >>>>
> > > > > >> >>>>> On Feb 6, 2019, at
> 12:07 AM,
> > > OmPrakash
> > > > Muppirala <
> > > > > >> >>> bigosmallm@gmail.com>
> > > > > >> >>>> wrote:
> > > > > >> >>>>>
> > > > > >> >>>>> I was wondering if we
> can
> > use
> > > docker
> > > > images to
> > > > > setup and seal
> > > > > >> the
> > > > > >> >>> RM
> > > > > >> >>>>> environment. Then
> other RMs
> > > simply
> > > > need to run
> > > > > the image
> > > > > >> locally
> > > > > >> >>> and run
> > > > > >> >>>>> the release scripts.
> Might
> > > be easier.
> > > > If folks
> > > > > like this plan,
> > > > > >> >> I
> > > > > >> >>> can
> > > > > >> >>>> try
> > > > > >> >>>>> to put something
> together.
> > > > > >> >>>>>
> > > > > >> >>>>> Thanks,
> > > > > >> >>>>> Om
> > > > > >> >>>>>
> > > > > >> >>>>> On Tue, Feb 5, 2019
> at 1:40
> > > PM Harbs <
> > > > > harbs.lists@gmail.com>
> > > > > >> >>> wrote:
> > > > > >> >>>>>
> > > > > >> >>>>>> In a recent
> discussion, it
> > > looks like
> > > > other
> > > > > projects have
> > > > > >> gotten
> > > > > >> >>>> resources
> > > > > >> >>>>>> from AWS.
> > > > > >> >>>>>>
> > > > > >> >>>>>> Whatever service we
> use,
> > > could setup a
> > > > “shared”
> > > > > Royale account
> > > > > >> >>> that all
> > > > > >> >>>>>> PMC members could
> have
> > > access to.
> > > > > >> >>>>>>
> > > > > >> >>>>>> I don’t know if
> there’s
> > some
> > > way we
> > > > could
> > > > > leverage Gitlab’s
> > > > > >> >>> integration
> > > > > >> >>>>>> pipelines
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > >
> > https://docs.gitlab.com/ee/ci/README.html
> > > > > >> >>> <
> > > > > >> >>>>>>
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > >
> > https://docs.gitlab.com/ee/ci/README.html
> > > > > >> >>>>
> > > > > >> >>>>>>
> > > > > >> >>>>>>> On Feb 5, 2019, at
> 11:33
> > > PM, Alex
> > > > Harui
> > > > > >> >> <aharui@adobe.com.INVALID
> > > > > >> >>>>
> > > > > >> >>>>>> wrote:
> > > > > >> >>>>>>>
> > > > > >> >>>>>>> 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" <
> > > > > >> >>
> piotrzarzycki21@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.lists@gmail.com
> > > > > >> >>> wrote:
> > > > > >> >>>>>>>
> > > > > >> >>>>>>>> A big +1 from me!
> > > > > >> >>>>>>>>
> > > > > >> >>>>>>>> Looking forward!
> > > > > >> >>>>>>>>
> > > > > >> >>>>>>>>> On Feb 5, 2019,
> at 9:34
> > > PM, Alex
> > > > Harui
> > > > > >> >>>
> <ah...@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
> > > > >
> >
>
>
>
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Hi Greg,
It turns out I have a "split shift" today. I'm stopping work for the next 7 or 8 hours then will get around to the merge. So if you can get your changes merged in that amount of time, then I will wait for you and deal with any merge conflicts (there are almost certain to be some).
-Alex
On 6/10/19, 11:46 AM, "Greg Dove" <gr...@gmail.com> wrote:
Alex, slightly OT, but in terms of coordination: fyi I am also very close
to merging the language improvements branch into develop. As I already
mentioned elsewhere, I was hoping to do that a couple of days back, but
some recent things also took me a little longer than expected (I have
additional local changes/fixes not yet in remote branch) . I was planning
to merge that today also.
However, I will wait until after your merge, so I'm hoping you can get
yours in today (if not, I will wait). I will probably put mine in as a
squashed commit after yours.
On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <pi...@gmail.com>
wrote:
> Hi Alex,
>
> Many thanks for that! I will try to be RM. I will have some dedicated time
> for that. I will wait for your instruction and merge to develop.
>
> Thanks,
> Piotr
>
>
> On Mon, Jun 10, 2019, 7:31 PM Alex Harui <ah...@adobe.com.invalid> wrote:
>
> > Well, that turned out to be much more time-consuming than I expected, but
> > we can now create identical release artifacts on Mac and Win. I am
> hopeful
> > this effort will pay off not only now in having other folks generate
> > releases, but also in the future if signed binaries become a requirement.
> >
> > There continues to be a lot of distractions in my life that can cause
> > delays, but I hope to merge the release_practice branches into develop
> over
> > the next day or two and figure out where in the wiki to document the
> > release process. So, now is the time for one or more people to step up
> to
> > be the RMs for 0.9.6 and help debug and improve the process.
> >
> > I am going to try very hard not to "own" the process. If something goes
> > wrong, I am going to ask others to try to debug and fix it first because
> it
> > is in the project's best interests for others to truly understand how
> this
> > stuff works.
> >
> > Thanks,
> > -Alex
> >
> > On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> >
> > It has turned out to be harder than expected to get the same binaries
> > on Mac and Win. I now have the identical binaries for royale-compiler
> and
> > royale-typedefs Maven artifacts and am starting on royale-asjs. I might
> > get lucky and the changes that fixed royale-typedefs SWCs will magically
> > get the royale-asjs SWCs to match. Then we have to make the Ant
> artifacts
> > match.
> >
> > There have been a lot of distractions in my non-work life which has
> > also impeded progress. I hope to make much progress this coming week and
> > if we're lucky, I will be asking for a volunteer (or volunteers) to test
> > drive all of this stuff and be the RM for 0.9.6. I am not going to be
> the
> > RM.
> >
> > -Alex
> >
> > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <pi...@gmail.com>
> > wrote:
> >
> > Hi Alex,
> >
> > It's been a while since you have started effort with automating
> > build.
> > Where are you with that ? Are we closer to started 0.9.6. Do you
> > need any
> > help with this ?
> >
> > Thanks,
> > Piotr
> >
> > wt., 2 kwi 2019 o 19:30 Alex Harui <ah...@adobe.com.invalid>
> > napisał(a):
> >
> > > Update:
> > >
> > > In order to make verification of binary release packages
> created
> > on the
> > > server easier, I have made changes to our build scripts and
> > tools to try to
> > > generate reproducible binaries. I've seen two different builds
> > compare on
> > > my Mac. The next challenge will be to see if the server can
> > build a
> > > package on Windows that will compare on Mac.
> > >
> > > One of the changes I needed to make is to JBurg. The version
> of
> > JBurg we
> > > use generates method names including a hash that doesn't
> > reproduce the same
> > > name each time. I have changes to JBurg ready, however JBurg
> is
> > currently
> > > under CPL which is category B. We only need one file, we don't
> > need or
> > > want all of JBurg at this time. The one JBurg file is jointly
> > owned by
> > > Adobe and Tom Harwood. I've contact Tom and he will be filing
> > an ICLA and
> > > has given me permission to commit the lines he owns in that one
> > file.
> > >
> > > This is the revision of the file that will be donated by
> > Tom/Adobe.
> > >
> > >
> >
> https://sourceforge.net/p/jburg/code/ci/66c287943376a74ac791f3d3bf969ab160bf80ff/tree/src/generator/jburg/burg/JBurgGenerator.java
> > >
> > > Once this file goes in with the changes to keep the method
> names
> > the same,
> > > there will be more tweaks to the release tasks and then we can
> > try cutting
> > > a release. I'm thinking we'll be at that point in early May,
> so
> > now is the
> > > time to get stuff in for the 0.9.6 release.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com> wrote:
> > >
> > > I would much rather have others find and fix issues
> > themselves. That
> > > way, more people than just me will know how to maintain the
> > system. It
> > > actually turns out that, IMO, a group of people can work on the
> > release.
> > > There are 14 steps. Literally, 14 different people could
> > execute one step
> > > each.
> > >
> > > My 2 cents,
> > > -Alex
> > >
> > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> carlosrovira@apache.org>
> > wrote:
> > >
> > > Hi Alex,
> > >
> > > amazing work! congrats to reach to this point! :)
> > >
> > > I need to put my head on all of this, but count on me
> to
> > be a RM.
> > > I think
> > > the best thing should be that you be the first RM to
> try
> > your own
> > > development at least for the first time, and then the
> > rest of us
> > > will
> > > follow you on the next releases. With all this on place
> > we maybe
> > > could
> > > release once a month or every two months...
> > >
> > > Thanks for doing this :)
> > >
> > > Carlos
> > >
> > >
> > > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > > (<ah...@adobe.com.invalid>)
> > > escribió:
> > >
> > > > OK, I've now seen Jenkins perform the steps to build
> > the release
> > > > artifacts. Folks interested in Docker-izing the
> steps
> > are
> > > welcome to look
> > > > at the jobs on the "Royale Release" tab on the CI
> > server.
> > > >
> > >
> >
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/
> > > >
> > > > These steps assume that the RM can run the basic
> Maven
> > and Ant
> > > build on
> > > > the RM's computer. I think that's a fair requirement
> > since all
> > > of us on the
> > > > PMC need to able to do that to build the RC in order
> > to vote on
> > > it.
> > > > Jenkins does other tasks like run the Maven release
> > plugin
> > > steps.
> > > >
> > > > Currently that results in binaries on Jenkins that
> are
> > > downloaded to the
> > > > RM's computer. These binaries need to be verified by
> > the RM
> > > which is the
> > > > next phase I will be starting on now. The RM
> verifies
> > the bits
> > > and then
> > > > PGP signs them. And then the bits are uploaded off
> > the RM's
> > > computer to
> > > > Maven Staging or dist.a.o/dev. If that uploading
> > turns out to
> > > be a point
> > > > of failure, we have the option of having Jenkins
> > upload the big
> > > files and
> > > > have the RM only upload PGP signature files. Or
> > finding a way
> > > for Jenkins
> > > > to get the signature files from the RM. The uploads
> > worked fine
> > > for me,
> > > > but then again, so did the old script's uploads.
> > > >
> > > > Therefore, once I get the binary verification phase
> > completed, I
> > > think
> > > > someone other than me should be the RM and try to use
> > these
> > > steps to
> > > > generate the release and help debug the process for
> > the next
> > > RM. So,
> > > > please try to carve out some time to be the RM. One
> > advantage
> > > of doing
> > > > most of the work on Jenkins is that it frees up my
> > computer to
> > > do other
> > > > things while Jenkins is cranking away.
> > > >
> > > > I think we're at least a week away from binary
> > verification,
> > > maybe two, so
> > > > it is time to start thinking about what is going in
> > this release.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 3/7/19, 4:15 PM, "Alex Harui"
> > <ah...@adobe.com.INVALID>
> > > wrote:
> > > >
> > > > In case you haven't guessed, I'm testing out
> > Jenkins and its
> > > ability
> > > > to create the artifacts and send emails. Please
> > ignore any
> > > email that
> > > > looks like a vote or discuss thread.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 2/10/19, 8:44 PM, "Alex Harui"
> > <ah...@adobe.com.INVALID>
> > > wrote:
> > > >
> > > > Om,
> > > >
> > > > Well, that's what I used for the last
> > release. I'm sure
> > > there is
> > > > probably some inaccuracy in it.
> > > >
> > > > That said, I'm abandoning that document and
> > taking a new
> > > angle
> > > > because that document presumed that the release
> > manager was
> > > trying to
> > > > create a release on his/her computer. I've given up
> > on that and
> > > working on
> > > > making releases from a shared computer for the
> reasons
> > I've
> > > stated
> > > > upthread. I hope to make some progress on that this
> > week.
> > > >
> > > > The key difference is that the new angle does
> > not
> > > presume that you
> > > > have Git SSH and PGP signatures all set up on some
> > computer. I
> > > have not
> > > > looked into how Docker would handle that. You
> > certainly
> > > wouldn't want the
> > > > Docker image to contain your SSH or PGP keys/creds.
> > And if the
> > > Docker
> > > > image doesn't, then that is another stumbling block
> > for future
> > > RMs.
> > > >
> > > > The other key difference is that the old
> > script presumed
> > > you could
> > > > create the 3 release in 3 huge "easy" steps. We've
> > seen that is
> > > only true
> > > > for me. So the new angle creates many discrete steps
> > managed by
> > > Jenkins.
> > > >
> > > > So, it is up to you to decide what you want
> to
> > > "Docker-ize". You
> > > > can try to Docker-ize the current 3 big steps, so RMs
> > can try to
> > > run it on
> > > > their systems, but I'd bet they will just faiI due to
> > network
> > > issues. I
> > > > would be interested in using Docker to make each of
> > these many
> > > discrete
> > > > steps portable to another server. I'm not going to
> > involve
> > > Docker at this
> > > > point. My main goal is just to see if I can create a
> > workflow
> > > of many
> > > > discrete steps that isn't horribly painful. Once we
> > see what
> > > these steps
> > > > turn out to be, then we can worry about server
> > portability of
> > > those steps.
> > > >
> > > > Either way, we want to know about running
> > > Browser+Selenium for
> > > > sure. And maybe FlashPlayerDebugger or AIR. I would
> > want to
> > > know, for
> > > > example, how you debug a failing checkintest in a
> > Docker
> > > container.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > >
> > > > On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <
> > > bigosmallm@gmail.com>
> > > > wrote:
> > > >
> > > > Alex,
> > > >
> > > > Just to be clear, I am following the
> steps
> > from here
> > > to try
> > > > and setup a
> > > > docker container.
> > > >
> > > >
> > > >
> > >
> >
> https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
> > > >
> > > > Is this doc up to date?
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Wed, Feb 6, 2019 at 12:02 PM OmPrakash
> > Muppirala <
> > > > bigosmallm@gmail.com>
> > > > wrote:
> > > >
> > > > > One approach is to have each step in
> the
> > process
> > > spin up a
> > > > docker image.
> > > > > And use docker-compose to run each
> > step. All the
> > > images can
> > > > be made to
> > > > > share a common volume where all the
> > artifacts are
> > > stored
> > > > across steps.
> > > > >
> > > > > You are right about the networking
> issue
> > though.
> > > Any
> > > > network related
> > > > > failure that occurs on the host machine
> > will most
> > > likely
> > > > occur in the
> > > > > docker container. Although, I am not
> > clear how we
> > > can
> > > > guarantee that the
> > > > > same issues will not occur on the
> > Jenkins server.
> > > I mean,
> > > > what is special
> > > > > about the Jenkins server that makes it
> > immune to
> > > these
> > > > networking issues?
> > > > >
> > > > > Thanks,
> > > > > Om
> > > > >
> > > > > On Wed, Feb 6, 2019 at 11:48 AM Alex
> > Harui
> > > > <ah...@adobe.com.invalid>
> > > > > wrote:
> > > > >
> > > > >> Again, I don't know anything about
> > Docker, but
> > > before we
> > > > spend a lot of
> > > > >> time on Docker, I also want to point
> > out that the
> > > process
> > > > to create a
> > > > >> release cannot really be thought of as
> > "one
> > > application".
> > > > It will be a
> > > > >> series of "steps" to run. How many
> > steps
> > > depends on
> > > > whether we think we
> > > > >> can isolate enough stuff via Docker to
> > be able to
> > > run
> > > > Docker on the RM's
> > > > >> computer instead of some shared
> > computer. On a
> > > shared
> > > > computer there will
> > > > >> be dozens of steps because the RM will
> > need to
> > > enter
> > > > passwords to commit
> > > > >> stuff. On a local computer I guess
> the
> > RM can
> > > supply
> > > > passwords but I think
> > > > >> there will be stopping points where
> the
> > Maven
> > > artifacts are
> > > > deployed and
> > > > >> the staging repo is closed, and
> another
> > stopping
> > > point for
> > > > the vote. It
> > > > >> seems like Docker works by downloading
> > > dependencies. Given
> > > > that the
> > > > >> problem the RMs had last time involved
> > downloads
> > > and
> > > > uploads, why do we
> > > > >> think Docker will really solve this
> for
> > creating
> > > releases
> > > > on local machines?
> > > > >>
> > > > >> The reason to do this on a shared
> > machine is so
> > > that new
> > > > RMs don't have
> > > > >> to do as much setup. But then I
> wonder
> > about the
> > > > efficiency of kicking off
> > > > >> that many Docker images. Jenkins can
> > manage that
> > > already.
> > > > Does Docker
> > > > >> have some sort of similar Dashboard or
> > would we
> > > use Jenkins
> > > > to kick off
> > > > >> Docker steps? I can't quite picture
> > what is the
> > > outermost
> > > > >> control/dashboard.
> > > > >>
> > > > >> -Alex
> > > > >>
> > > > >> On 2/6/19, 11:03 AM, "Harbs" <
> > > harbs.lists@gmail.com> wrote:
> > > > >>
> > > > >> A quick search turns up this:
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://codingsans.com/blog/selenium-with-docker-testing
> > > > >> <
> > > > >>
> > > >
> > >
> >
> https://codingsans.com/blog/selenium-with-docker-testing
> > > > >> >
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker
> > > > >> <
> > > > >>
> > > >
> > >
> >
> https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker
> > > > >> >
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://github.com/SeleniumHQ/docker-selenium
> > > > >> <
> > > > >>
> > > >
> > >
> >
> https://github.com/SeleniumHQ/docker-selenium
> > > > >> >
> > > > >>
> > > > >> > On Feb 6, 2019, at 8:59 PM, Alex
> > Harui
> > > > <ah...@adobe.com.INVALID>
> > > > >> wrote:
> > > > >> >
> > > > >> > Thanks for volunteering to try
> it
> > Om. IMO,
> > > even more
> > > > important
> > > > >> than Firefox+Flash is
> > SomeBrowser+Selenium. We
> > > may also
> > > > need to run Adobe
> > > > >> AIR's adb. We could probably turn off
> > the Flash
> > > tests or
> > > > replace Flash
> > > > >> with AIR.
> > > > >> >
> > > > >> > Thanks,
> > > > >> > -Alex
> > > > >> >
> > > > >> > On 2/6/19, 10:54 AM, "Carlos
> > Rovira" <
> > > > carlosrovira@apache.org>
> > > > >> wrote:
> > > > >> >
> > > > >> > Hi Om, that would be great!
> > waiting for
> > > your
> > > > experience with a
> > > > >> that! :)
> > > > >> >
> > > > >> > El mié., 6 feb. 2019 a las
> > 19:31,
> > > OmPrakash
> > > > Muppirala (<
> > > > >> bigosmallm@gmail.com>)
> > > > >> > escribió:
> > > > >> >
> > > > >> >> Yes, I agree with Alex about
> not
> > being
> > > able to run
> > > > UI out of docker
> > > > >> >> containers. I never thought of
> > the
> > > checkintests
> > > > when I made the
> > > > >> >> suggestion.
> > > > >> >>
> > > > >> >> The firefox-flash image that
> > Yishay
> > > pointed out
> > > > looks promising.
> > > > >> I will
> > > > >> >> poke around with it and see if
> > that works
> > > for us.
> > > > >> >>
> > > > >> >> Thanks,
> > > > >> >> Om
> > > > >> >>
> > > > >> >> On Wed, Feb 6, 2019 at 12:41 AM
> > Yishay
> > > Weiss <
> > > > >> yishayjobs@hotmail.com>
> > > > >> >> wrote:
> > > > >> >>
> > > > >> >>> I’ll let Om or someone else
> > with docker
> > > experience
> > > > tell us if
> > > > >> this [1] is
> > > > >> >>> relevant.
> > > > >> >>>
> > > > >> >>>
> > > > >> >>>
> > > > >> >>> [1]
> > > > >>
> > > >
> > >
> >
> https://hub.docker.com/r/beli/firefox-flash/
> > > > >> >>>
> > > > >> >>>
> > > > >> >>>
> > > > >> >>>
> ________________________________
> > > > >> >>> From: Alex Harui
> > <aharui@adobe.com.INVALID
> > > >
> > > > >> >>> Sent: Wednesday, February 6,
> > 2019
> > > 10:05:54 AM
> > > > >> >>> To: dev@royale.apache.org
> > > > >> >>> Subject: Re: 0.9.6 Release
> > > > >> >>>
> > > > >> >>> I don't anything about docker,
> > but in 15
> > > minutes of
> > > > reading I ran
> > > > >> into
> > > > >> >>> this:
> > > > >> >>>
> > > > >> >>>
> > > > >> >>
> > > > >>
> > > >
> > >
> >
> https://www.channelfutures.com/open-source/when-not-to-use-docker-understanding-the-limitations-of-containers
> > > > >> >>>
> > > > >> >>> Which says: Docker can't " Run
> > > applications with
> > > > graphical
> > > > >> interfaces".
> > > > >> >>> If you want Royale to use
> > Docker for
> > > releases, show
> > > > that it can
> > > > >> run
> > > > >> >>> checkintests with Flash and
> the
> > Browser.
> > > Then I
> > > > will look into
> > > > >> it more.
> > > > >> >>>
> > > > >> >>> The highest level goal is to
> > make it as
> > > easy as
> > > > possible for
> > > > >> someone to
> > > > >> >>> volunteer to be an RM. Any
> > requirement
> > > of "install
> > > > this (Docker,
> > > > >> etc) on
> > > > >> >>> your computer" is, IMO,
> another
> > barrier
> > > to entry.
> > > > Yeah, RMs will
> > > > >> have to
> > > > >> >>> have Maven installed and maybe
> > Ant, but
> > > you should
> > > > already have
> > > > >> those
> > > > >> >>> installed to be a
> committer/PMC
> > member.
> > > > >> >>>
> > > > >> >>> That said, a good takeaway
> from
> > the
> > > Docker idea is
> > > > to try to find
> > > > >> a way
> > > > >> >> to
> > > > >> >>> make an "Image" of whatever we
> > end up
> > > with on
> > > > whatever server we
> > > > >> end up
> > > > >> >>> using so if the image can be
> > copied and
> > > used on
> > > > other servers.
> > > > >> I'm not
> > > > >> >>> exactly sure how to do that
> > with Azure,
> > > which hosts
> > > > my CI
> > > > >> server. I will
> > > > >> >>> spend a few more minutes
> > researching that.
> > > > >> >>>
> > > > >> >>> I could not quickly find any
> > way to get a
> > > free VM
> > > > on Azure or AWS
> > > > >> that
> > > > >> >>> isn't a
> > > free-trial-start-paying-after-a-year. So,
> > > > unless someone
> > > > >> comes
> > > > >> >> up
> > > > >> >>> with a free server we can use
> > "forever",
> > > I'm going
> > > > to just start
> > > > >> with my
> > > > >> >>> Azure VM.
> > > > >> >>>
> > > > >> >>> -Alex
> > > > >> >>>
> > > > >> >>> On 2/5/19, 10:59 PM, "Carlos
> > Rovira" <
> > > > carlosrovira@apache.org>
> > > > >> wrote:
> > > > >> >>>
> > > > >> >>> Hi.
> > > > >> >>>
> > > > >> >>> the plan sounds very good
> to
> > me. Just
> > > my 2
> > > > thoughts on this:
> > > > >> >>>
> > > > >> >>> 1.- As I was reading I was
> > thinking as
> > > well on
> > > > something like
> > > > >> Docker
> > > > >> >>> and
> > > > >> >>> see Om as well thinking on
> > the same.
> > > Maybe is
> > > > the way to this
> > > > >> with
> > > > >> >> the
> > > > >> >>> actual technology. Seems
> VMs
> > are
> > > stepping out a
> > > > bit this days
> > > > >> in
> > > > >> >> favor
> > > > >> >>> of
> > > > >> >>> things like Docker. Maybe
> > the same did
> > > Git over
> > > > Svn, and today
> > > > >> Svn is
> > > > >> >>> an
> > > > >> >>> old remembrance. I must say
> > that I
> > > have no
> > > > experience with
> > > > >> Docker, so
> > > > >> >>> doing
> > > > >> >>> that will require acquire
> > that
> > > knowledge, but
> > > > seems it could
> > > > >> be worth
> > > > >> >>> it.
> > > > >> >>>
> > > > >> >>> 2.- Maybe is not possible,
> > but I want
> > > to propose
> > > > to do this
> > > > >> work I a
> > > > >> >>> separate branch, so it
> could
> > be in
> > > parallel to
> > > > other
> > > > >> developments. I
> > > > >> >>> think
> > > > >> >>> work over develop is
> > practical if
> > > there's
> > > > something tiny that
> > > > >> could
> > > > >> >> be
> > > > >> >>> done
> > > > >> >>> in a commit. But as we need
> > more than
> > > one, or is
> > > > a long
> > > > >> process (like
> > > > >> >>> this), chances are to make
> > develop
> > > branch
> > > > unstable and even
> > > > >> for some
> > > > >> >>> days.
> > > > >> >>> I think we should try to
> > avoid that
> > > scenario,
> > > > and branches are
> > > > >> the
> > > > >> >> best
> > > > >> >>> way. If we do this way,
> > we'll benefit
> > > of more
> > > > reliable develop
> > > > >> >> branch.
> > > > >> >>>
> > > > >> >>> Thanks and good to know of
> > this plan :)
> > > > >> >>>
> > > > >> >>> Carlos
> > > > >> >>>
> > > > >> >>>
> > > > >> >>> El mar., 5 feb. 2019 a las
> > 23:19,
> > > Harbs (<
> > > > >> harbs.lists@gmail.com>)
> > > > >> >>> escribió:
> > > > >> >>>
> > > > >> >>>> I’ve never used Docker
> myself,
> > but that
> > > might be a
> > > > good plan.
> > > > >> >>>>
> > > > >> >>>>> On Feb 6, 2019, at 12:07 AM,
> > OmPrakash
> > > Muppirala <
> > > > >> >>> bigosmallm@gmail.com>
> > > > >> >>>> wrote:
> > > > >> >>>>>
> > > > >> >>>>> I was wondering if we can
> use
> > docker
> > > images to
> > > > setup and seal
> > > > >> the
> > > > >> >>> RM
> > > > >> >>>>> environment. Then other RMs
> > simply
> > > need to run
> > > > the image
> > > > >> locally
> > > > >> >>> and run
> > > > >> >>>>> the release scripts. Might
> > be easier.
> > > If folks
> > > > like this plan,
> > > > >> >> I
> > > > >> >>> can
> > > > >> >>>> try
> > > > >> >>>>> to put something together.
> > > > >> >>>>>
> > > > >> >>>>> Thanks,
> > > > >> >>>>> Om
> > > > >> >>>>>
> > > > >> >>>>> On Tue, Feb 5, 2019 at 1:40
> > PM Harbs <
> > > > harbs.lists@gmail.com>
> > > > >> >>> wrote:
> > > > >> >>>>>
> > > > >> >>>>>> In a recent discussion, it
> > looks like
> > > other
> > > > projects have
> > > > >> gotten
> > > > >> >>>> resources
> > > > >> >>>>>> from AWS.
> > > > >> >>>>>>
> > > > >> >>>>>> Whatever service we use,
> > could setup a
> > > “shared”
> > > > Royale account
> > > > >> >>> that all
> > > > >> >>>>>> PMC members could have
> > access to.
> > > > >> >>>>>>
> > > > >> >>>>>> I don’t know if there’s
> some
> > way we
> > > could
> > > > leverage Gitlab’s
> > > > >> >>> integration
> > > > >> >>>>>> pipelines
> > > > >> >>>
> > > > >> >>
> > > > >>
> > > >
> > >
> >
> https://docs.gitlab.com/ee/ci/README.html
> > > > >> >>> <
> > > > >> >>>>>>
> > > > >> >>>
> > > > >> >>
> > > > >>
> > > >
> > >
> >
> https://docs.gitlab.com/ee/ci/README.html
> > > > >> >>>>
> > > > >> >>>>>>
> > > > >> >>>>>>> On Feb 5, 2019, at 11:33
> > PM, Alex
> > > Harui
> > > > >> >> <aharui@adobe.com.INVALID
> > > > >> >>>>
> > > > >> >>>>>> wrote:
> > > > >> >>>>>>>
> > > > >> >>>>>>> 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" <
> > > > >> >> piotrzarzycki21@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.lists@gmail.com
> > > > >> >>> wrote:
> > > > >> >>>>>>>
> > > > >> >>>>>>>> A big +1 from me!
> > > > >> >>>>>>>>
> > > > >> >>>>>>>> Looking forward!
> > > > >> >>>>>>>>
> > > > >> >>>>>>>>> On Feb 5, 2019, at 9:34
> > PM, Alex
> > > Harui
> > > > >> >>> <ah...@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
> > > >
>
Re: 0.9.6 Release
Posted by Greg Dove <gr...@gmail.com>.
Alex, slightly OT, but in terms of coordination: fyi I am also very close
to merging the language improvements branch into develop. As I already
mentioned elsewhere, I was hoping to do that a couple of days back, but
some recent things also took me a little longer than expected (I have
additional local changes/fixes not yet in remote branch) . I was planning
to merge that today also.
However, I will wait until after your merge, so I'm hoping you can get
yours in today (if not, I will wait). I will probably put mine in as a
squashed commit after yours.
On Tue, Jun 11, 2019 at 6:05 AM Piotr Zarzycki <pi...@gmail.com>
wrote:
> Hi Alex,
>
> Many thanks for that! I will try to be RM. I will have some dedicated time
> for that. I will wait for your instruction and merge to develop.
>
> Thanks,
> Piotr
>
>
> On Mon, Jun 10, 2019, 7:31 PM Alex Harui <ah...@adobe.com.invalid> wrote:
>
> > Well, that turned out to be much more time-consuming than I expected, but
> > we can now create identical release artifacts on Mac and Win. I am
> hopeful
> > this effort will pay off not only now in having other folks generate
> > releases, but also in the future if signed binaries become a requirement.
> >
> > There continues to be a lot of distractions in my life that can cause
> > delays, but I hope to merge the release_practice branches into develop
> over
> > the next day or two and figure out where in the wiki to document the
> > release process. So, now is the time for one or more people to step up
> to
> > be the RMs for 0.9.6 and help debug and improve the process.
> >
> > I am going to try very hard not to "own" the process. If something goes
> > wrong, I am going to ask others to try to debug and fix it first because
> it
> > is in the project's best interests for others to truly understand how
> this
> > stuff works.
> >
> > Thanks,
> > -Alex
> >
> > On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> >
> > It has turned out to be harder than expected to get the same binaries
> > on Mac and Win. I now have the identical binaries for royale-compiler
> and
> > royale-typedefs Maven artifacts and am starting on royale-asjs. I might
> > get lucky and the changes that fixed royale-typedefs SWCs will magically
> > get the royale-asjs SWCs to match. Then we have to make the Ant
> artifacts
> > match.
> >
> > There have been a lot of distractions in my non-work life which has
> > also impeded progress. I hope to make much progress this coming week and
> > if we're lucky, I will be asking for a volunteer (or volunteers) to test
> > drive all of this stuff and be the RM for 0.9.6. I am not going to be
> the
> > RM.
> >
> > -Alex
> >
> > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <pi...@gmail.com>
> > wrote:
> >
> > Hi Alex,
> >
> > It's been a while since you have started effort with automating
> > build.
> > Where are you with that ? Are we closer to started 0.9.6. Do you
> > need any
> > help with this ?
> >
> > Thanks,
> > Piotr
> >
> > wt., 2 kwi 2019 o 19:30 Alex Harui <ah...@adobe.com.invalid>
> > napisał(a):
> >
> > > Update:
> > >
> > > In order to make verification of binary release packages
> created
> > on the
> > > server easier, I have made changes to our build scripts and
> > tools to try to
> > > generate reproducible binaries. I've seen two different builds
> > compare on
> > > my Mac. The next challenge will be to see if the server can
> > build a
> > > package on Windows that will compare on Mac.
> > >
> > > One of the changes I needed to make is to JBurg. The version
> of
> > JBurg we
> > > use generates method names including a hash that doesn't
> > reproduce the same
> > > name each time. I have changes to JBurg ready, however JBurg
> is
> > currently
> > > under CPL which is category B. We only need one file, we don't
> > need or
> > > want all of JBurg at this time. The one JBurg file is jointly
> > owned by
> > > Adobe and Tom Harwood. I've contact Tom and he will be filing
> > an ICLA and
> > > has given me permission to commit the lines he owns in that one
> > file.
> > >
> > > This is the revision of the file that will be donated by
> > Tom/Adobe.
> > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=XMDpGg0yPP530enC02eH8CQXf66Lsn97FFaqHxJaaio%3D&reserved=0
> > >
> > > Once this file goes in with the changes to keep the method
> names
> > the same,
> > > there will be more tweaks to the release tasks and then we can
> > try cutting
> > > a release. I'm thinking we'll be at that point in early May,
> so
> > now is the
> > > time to get stuff in for the 0.9.6 release.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com> wrote:
> > >
> > > I would much rather have others find and fix issues
> > themselves. That
> > > way, more people than just me will know how to maintain the
> > system. It
> > > actually turns out that, IMO, a group of people can work on the
> > release.
> > > There are 14 steps. Literally, 14 different people could
> > execute one step
> > > each.
> > >
> > > My 2 cents,
> > > -Alex
> > >
> > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> carlosrovira@apache.org>
> > wrote:
> > >
> > > Hi Alex,
> > >
> > > amazing work! congrats to reach to this point! :)
> > >
> > > I need to put my head on all of this, but count on me
> to
> > be a RM.
> > > I think
> > > the best thing should be that you be the first RM to
> try
> > your own
> > > development at least for the first time, and then the
> > rest of us
> > > will
> > > follow you on the next releases. With all this on place
> > we maybe
> > > could
> > > release once a month or every two months...
> > >
> > > Thanks for doing this :)
> > >
> > > Carlos
> > >
> > >
> > > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > > (<ah...@adobe.com.invalid>)
> > > escribió:
> > >
> > > > OK, I've now seen Jenkins perform the steps to build
> > the release
> > > > artifacts. Folks interested in Docker-izing the
> steps
> > are
> > > welcome to look
> > > > at the jobs on the "Royale Release" tab on the CI
> > server.
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=ag8xFP8FhC0ndIumEhlwAKTNImbUy3vLwVGYWiK0a68%3D&reserved=0
> > > >
> > > > These steps assume that the RM can run the basic
> Maven
> > and Ant
> > > build on
> > > > the RM's computer. I think that's a fair requirement
> > since all
> > > of us on the
> > > > PMC need to able to do that to build the RC in order
> > to vote on
> > > it.
> > > > Jenkins does other tasks like run the Maven release
> > plugin
> > > steps.
> > > >
> > > > Currently that results in binaries on Jenkins that
> are
> > > downloaded to the
> > > > RM's computer. These binaries need to be verified by
> > the RM
> > > which is the
> > > > next phase I will be starting on now. The RM
> verifies
> > the bits
> > > and then
> > > > PGP signs them. And then the bits are uploaded off
> > the RM's
> > > computer to
> > > > Maven Staging or dist.a.o/dev. If that uploading
> > turns out to
> > > be a point
> > > > of failure, we have the option of having Jenkins
> > upload the big
> > > files and
> > > > have the RM only upload PGP signature files. Or
> > finding a way
> > > for Jenkins
> > > > to get the signature files from the RM. The uploads
> > worked fine
> > > for me,
> > > > but then again, so did the old script's uploads.
> > > >
> > > > Therefore, once I get the binary verification phase
> > completed, I
> > > think
> > > > someone other than me should be the RM and try to use
> > these
> > > steps to
> > > > generate the release and help debug the process for
> > the next
> > > RM. So,
> > > > please try to carve out some time to be the RM. One
> > advantage
> > > of doing
> > > > most of the work on Jenkins is that it frees up my
> > computer to
> > > do other
> > > > things while Jenkins is cranking away.
> > > >
> > > > I think we're at least a week away from binary
> > verification,
> > > maybe two, so
> > > > it is time to start thinking about what is going in
> > this release.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 3/7/19, 4:15 PM, "Alex Harui"
> > <ah...@adobe.com.INVALID>
> > > wrote:
> > > >
> > > > In case you haven't guessed, I'm testing out
> > Jenkins and its
> > > ability
> > > > to create the artifacts and send emails. Please
> > ignore any
> > > email that
> > > > looks like a vote or discuss thread.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 2/10/19, 8:44 PM, "Alex Harui"
> > <ah...@adobe.com.INVALID>
> > > wrote:
> > > >
> > > > Om,
> > > >
> > > > Well, that's what I used for the last
> > release. I'm sure
> > > there is
> > > > probably some inaccuracy in it.
> > > >
> > > > That said, I'm abandoning that document and
> > taking a new
> > > angle
> > > > because that document presumed that the release
> > manager was
> > > trying to
> > > > create a release on his/her computer. I've given up
> > on that and
> > > working on
> > > > making releases from a shared computer for the
> reasons
> > I've
> > > stated
> > > > upthread. I hope to make some progress on that this
> > week.
> > > >
> > > > The key difference is that the new angle does
> > not
> > > presume that you
> > > > have Git SSH and PGP signatures all set up on some
> > computer. I
> > > have not
> > > > looked into how Docker would handle that. You
> > certainly
> > > wouldn't want the
> > > > Docker image to contain your SSH or PGP keys/creds.
> > And if the
> > > Docker
> > > > image doesn't, then that is another stumbling block
> > for future
> > > RMs.
> > > >
> > > > The other key difference is that the old
> > script presumed
> > > you could
> > > > create the 3 release in 3 huge "easy" steps. We've
> > seen that is
> > > only true
> > > > for me. So the new angle creates many discrete steps
> > managed by
> > > Jenkins.
> > > >
> > > > So, it is up to you to decide what you want
> to
> > > "Docker-ize". You
> > > > can try to Docker-ize the current 3 big steps, so RMs
> > can try to
> > > run it on
> > > > their systems, but I'd bet they will just faiI due to
> > network
> > > issues. I
> > > > would be interested in using Docker to make each of
> > these many
> > > discrete
> > > > steps portable to another server. I'm not going to
> > involve
> > > Docker at this
> > > > point. My main goal is just to see if I can create a
> > workflow
> > > of many
> > > > discrete steps that isn't horribly painful. Once we
> > see what
> > > these steps
> > > > turn out to be, then we can worry about server
> > portability of
> > > those steps.
> > > >
> > > > Either way, we want to know about running
> > > Browser+Selenium for
> > > > sure. And maybe FlashPlayerDebugger or AIR. I would
> > want to
> > > know, for
> > > > example, how you debug a failing checkintest in a
> > Docker
> > > container.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > >
> > > > On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <
> > > bigosmallm@gmail.com>
> > > > wrote:
> > > >
> > > > Alex,
> > > >
> > > > Just to be clear, I am following the
> steps
> > from here
> > > to try
> > > > and setup a
> > > > docker container.
> > > >
> > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=JfJSK%2B4xchkDWpv78GpWtFlVMQ%2BoUAE10rv7HdeCZck%3D&reserved=0
> > > >
> > > > Is this doc up to date?
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Wed, Feb 6, 2019 at 12:02 PM OmPrakash
> > Muppirala <
> > > > bigosmallm@gmail.com>
> > > > wrote:
> > > >
> > > > > One approach is to have each step in
> the
> > process
> > > spin up a
> > > > docker image.
> > > > > And use docker-compose to run each
> > step. All the
> > > images can
> > > > be made to
> > > > > share a common volume where all the
> > artifacts are
> > > stored
> > > > across steps.
> > > > >
> > > > > You are right about the networking
> issue
> > though.
> > > Any
> > > > network related
> > > > > failure that occurs on the host machine
> > will most
> > > likely
> > > > occur in the
> > > > > docker container. Although, I am not
> > clear how we
> > > can
> > > > guarantee that the
> > > > > same issues will not occur on the
> > Jenkins server.
> > > I mean,
> > > > what is special
> > > > > about the Jenkins server that makes it
> > immune to
> > > these
> > > > networking issues?
> > > > >
> > > > > Thanks,
> > > > > Om
> > > > >
> > > > > On Wed, Feb 6, 2019 at 11:48 AM Alex
> > Harui
> > > > <ah...@adobe.com.invalid>
> > > > > wrote:
> > > > >
> > > > >> Again, I don't know anything about
> > Docker, but
> > > before we
> > > > spend a lot of
> > > > >> time on Docker, I also want to point
> > out that the
> > > process
> > > > to create a
> > > > >> release cannot really be thought of as
> > "one
> > > application".
> > > > It will be a
> > > > >> series of "steps" to run. How many
> > steps
> > > depends on
> > > > whether we think we
> > > > >> can isolate enough stuff via Docker to
> > be able to
> > > run
> > > > Docker on the RM's
> > > > >> computer instead of some shared
> > computer. On a
> > > shared
> > > > computer there will
> > > > >> be dozens of steps because the RM will
> > need to
> > > enter
> > > > passwords to commit
> > > > >> stuff. On a local computer I guess
> the
> > RM can
> > > supply
> > > > passwords but I think
> > > > >> there will be stopping points where
> the
> > Maven
> > > artifacts are
> > > > deployed and
> > > > >> the staging repo is closed, and
> another
> > stopping
> > > point for
> > > > the vote. It
> > > > >> seems like Docker works by downloading
> > > dependencies. Given
> > > > that the
> > > > >> problem the RMs had last time involved
> > downloads
> > > and
> > > > uploads, why do we
> > > > >> think Docker will really solve this
> for
> > creating
> > > releases
> > > > on local machines?
> > > > >>
> > > > >> The reason to do this on a shared
> > machine is so
> > > that new
> > > > RMs don't have
> > > > >> to do as much setup. But then I
> wonder
> > about the
> > > > efficiency of kicking off
> > > > >> that many Docker images. Jenkins can
> > manage that
> > > already.
> > > > Does Docker
> > > > >> have some sort of similar Dashboard or
> > would we
> > > use Jenkins
> > > > to kick off
> > > > >> Docker steps? I can't quite picture
> > what is the
> > > outermost
> > > > >> control/dashboard.
> > > > >>
> > > > >> -Alex
> > > > >>
> > > > >> On 2/6/19, 11:03 AM, "Harbs" <
> > > harbs.lists@gmail.com> wrote:
> > > > >>
> > > > >> A quick search turns up this:
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=FUYuwlg6rT8EgffgT3QoP8YWcyzjXxNdrT8aN0jq1H4%3D&reserved=0
> > > > >> <
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=FUYuwlg6rT8EgffgT3QoP8YWcyzjXxNdrT8aN0jq1H4%3D&reserved=0
> > > > >> >
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=T4QPL4Hh552jE67uYLU1Xu2hDv61NLfuk4u2V6GS%2Bek%3D&reserved=0
> > > > >> <
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=T4QPL4Hh552jE67uYLU1Xu2hDv61NLfuk4u2V6GS%2Bek%3D&reserved=0
> > > > >> >
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=3r1pbB7qdx%2FQUpas%2FyQFs4ICsZUF7vBemIOm%2FArz6ZM%3D&reserved=0
> > > > >> <
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=3r1pbB7qdx%2FQUpas%2FyQFs4ICsZUF7vBemIOm%2FArz6ZM%3D&reserved=0
> > > > >> >
> > > > >>
> > > > >> > On Feb 6, 2019, at 8:59 PM, Alex
> > Harui
> > > > <ah...@adobe.com.INVALID>
> > > > >> wrote:
> > > > >> >
> > > > >> > Thanks for volunteering to try
> it
> > Om. IMO,
> > > even more
> > > > important
> > > > >> than Firefox+Flash is
> > SomeBrowser+Selenium. We
> > > may also
> > > > need to run Adobe
> > > > >> AIR's adb. We could probably turn off
> > the Flash
> > > tests or
> > > > replace Flash
> > > > >> with AIR.
> > > > >> >
> > > > >> > Thanks,
> > > > >> > -Alex
> > > > >> >
> > > > >> > On 2/6/19, 10:54 AM, "Carlos
> > Rovira" <
> > > > carlosrovira@apache.org>
> > > > >> wrote:
> > > > >> >
> > > > >> > Hi Om, that would be great!
> > waiting for
> > > your
> > > > experience with a
> > > > >> that! :)
> > > > >> >
> > > > >> > El mié., 6 feb. 2019 a las
> > 19:31,
> > > OmPrakash
> > > > Muppirala (<
> > > > >> bigosmallm@gmail.com>)
> > > > >> > escribió:
> > > > >> >
> > > > >> >> Yes, I agree with Alex about
> not
> > being
> > > able to run
> > > > UI out of docker
> > > > >> >> containers. I never thought of
> > the
> > > checkintests
> > > > when I made the
> > > > >> >> suggestion.
> > > > >> >>
> > > > >> >> The firefox-flash image that
> > Yishay
> > > pointed out
> > > > looks promising.
> > > > >> I will
> > > > >> >> poke around with it and see if
> > that works
> > > for us.
> > > > >> >>
> > > > >> >> Thanks,
> > > > >> >> Om
> > > > >> >>
> > > > >> >> On Wed, Feb 6, 2019 at 12:41 AM
> > Yishay
> > > Weiss <
> > > > >> yishayjobs@hotmail.com>
> > > > >> >> wrote:
> > > > >> >>
> > > > >> >>> I’ll let Om or someone else
> > with docker
> > > experience
> > > > tell us if
> > > > >> this [1] is
> > > > >> >>> relevant.
> > > > >> >>>
> > > > >> >>>
> > > > >> >>>
> > > > >> >>> [1]
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=t1ZG3j7i5LnUTpdSEW78jLfn4K3gIDLnhpJNeaonTjg%3D&reserved=0
> > > > >> >>>
> > > > >> >>>
> > > > >> >>>
> > > > >> >>>
> ________________________________
> > > > >> >>> From: Alex Harui
> > <aharui@adobe.com.INVALID
> > > >
> > > > >> >>> Sent: Wednesday, February 6,
> > 2019
> > > 10:05:54 AM
> > > > >> >>> To: dev@royale.apache.org
> > > > >> >>> Subject: Re: 0.9.6 Release
> > > > >> >>>
> > > > >> >>> I don't anything about docker,
> > but in 15
> > > minutes of
> > > > reading I ran
> > > > >> into
> > > > >> >>> this:
> > > > >> >>>
> > > > >> >>>
> > > > >> >>
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=ZOuiuLuyYx1I5w2expOtx1tGxDXIQqnKcSoFYUNkZeA%3D&reserved=0
> > > > >> >>>
> > > > >> >>> Which says: Docker can't " Run
> > > applications with
> > > > graphical
> > > > >> interfaces".
> > > > >> >>> If you want Royale to use
> > Docker for
> > > releases, show
> > > > that it can
> > > > >> run
> > > > >> >>> checkintests with Flash and
> the
> > Browser.
> > > Then I
> > > > will look into
> > > > >> it more.
> > > > >> >>>
> > > > >> >>> The highest level goal is to
> > make it as
> > > easy as
> > > > possible for
> > > > >> someone to
> > > > >> >>> volunteer to be an RM. Any
> > requirement
> > > of "install
> > > > this (Docker,
> > > > >> etc) on
> > > > >> >>> your computer" is, IMO,
> another
> > barrier
> > > to entry.
> > > > Yeah, RMs will
> > > > >> have to
> > > > >> >>> have Maven installed and maybe
> > Ant, but
> > > you should
> > > > already have
> > > > >> those
> > > > >> >>> installed to be a
> committer/PMC
> > member.
> > > > >> >>>
> > > > >> >>> That said, a good takeaway
> from
> > the
> > > Docker idea is
> > > > to try to find
> > > > >> a way
> > > > >> >> to
> > > > >> >>> make an "Image" of whatever we
> > end up
> > > with on
> > > > whatever server we
> > > > >> end up
> > > > >> >>> using so if the image can be
> > copied and
> > > used on
> > > > other servers.
> > > > >> I'm not
> > > > >> >>> exactly sure how to do that
> > with Azure,
> > > which hosts
> > > > my CI
> > > > >> server. I will
> > > > >> >>> spend a few more minutes
> > researching that.
> > > > >> >>>
> > > > >> >>> I could not quickly find any
> > way to get a
> > > free VM
> > > > on Azure or AWS
> > > > >> that
> > > > >> >>> isn't a
> > > free-trial-start-paying-after-a-year. So,
> > > > unless someone
> > > > >> comes
> > > > >> >> up
> > > > >> >>> with a free server we can use
> > "forever",
> > > I'm going
> > > > to just start
> > > > >> with my
> > > > >> >>> Azure VM.
> > > > >> >>>
> > > > >> >>> -Alex
> > > > >> >>>
> > > > >> >>> On 2/5/19, 10:59 PM, "Carlos
> > Rovira" <
> > > > carlosrovira@apache.org>
> > > > >> wrote:
> > > > >> >>>
> > > > >> >>> Hi.
> > > > >> >>>
> > > > >> >>> the plan sounds very good
> to
> > me. Just
> > > my 2
> > > > thoughts on this:
> > > > >> >>>
> > > > >> >>> 1.- As I was reading I was
> > thinking as
> > > well on
> > > > something like
> > > > >> Docker
> > > > >> >>> and
> > > > >> >>> see Om as well thinking on
> > the same.
> > > Maybe is
> > > > the way to this
> > > > >> with
> > > > >> >> the
> > > > >> >>> actual technology. Seems
> VMs
> > are
> > > stepping out a
> > > > bit this days
> > > > >> in
> > > > >> >> favor
> > > > >> >>> of
> > > > >> >>> things like Docker. Maybe
> > the same did
> > > Git over
> > > > Svn, and today
> > > > >> Svn is
> > > > >> >>> an
> > > > >> >>> old remembrance. I must say
> > that I
> > > have no
> > > > experience with
> > > > >> Docker, so
> > > > >> >>> doing
> > > > >> >>> that will require acquire
> > that
> > > knowledge, but
> > > > seems it could
> > > > >> be worth
> > > > >> >>> it.
> > > > >> >>>
> > > > >> >>> 2.- Maybe is not possible,
> > but I want
> > > to propose
> > > > to do this
> > > > >> work I a
> > > > >> >>> separate branch, so it
> could
> > be in
> > > parallel to
> > > > other
> > > > >> developments. I
> > > > >> >>> think
> > > > >> >>> work over develop is
> > practical if
> > > there's
> > > > something tiny that
> > > > >> could
> > > > >> >> be
> > > > >> >>> done
> > > > >> >>> in a commit. But as we need
> > more than
> > > one, or is
> > > > a long
> > > > >> process (like
> > > > >> >>> this), chances are to make
> > develop
> > > branch
> > > > unstable and even
> > > > >> for some
> > > > >> >>> days.
> > > > >> >>> I think we should try to
> > avoid that
> > > scenario,
> > > > and branches are
> > > > >> the
> > > > >> >> best
> > > > >> >>> way. If we do this way,
> > we'll benefit
> > > of more
> > > > reliable develop
> > > > >> >> branch.
> > > > >> >>>
> > > > >> >>> Thanks and good to know of
> > this plan :)
> > > > >> >>>
> > > > >> >>> Carlos
> > > > >> >>>
> > > > >> >>>
> > > > >> >>> El mar., 5 feb. 2019 a las
> > 23:19,
> > > Harbs (<
> > > > >> harbs.lists@gmail.com>)
> > > > >> >>> escribió:
> > > > >> >>>
> > > > >> >>>> I’ve never used Docker
> myself,
> > but that
> > > might be a
> > > > good plan.
> > > > >> >>>>
> > > > >> >>>>> On Feb 6, 2019, at 12:07 AM,
> > OmPrakash
> > > Muppirala <
> > > > >> >>> bigosmallm@gmail.com>
> > > > >> >>>> wrote:
> > > > >> >>>>>
> > > > >> >>>>> I was wondering if we can
> use
> > docker
> > > images to
> > > > setup and seal
> > > > >> the
> > > > >> >>> RM
> > > > >> >>>>> environment. Then other RMs
> > simply
> > > need to run
> > > > the image
> > > > >> locally
> > > > >> >>> and run
> > > > >> >>>>> the release scripts. Might
> > be easier.
> > > If folks
> > > > like this plan,
> > > > >> >> I
> > > > >> >>> can
> > > > >> >>>> try
> > > > >> >>>>> to put something together.
> > > > >> >>>>>
> > > > >> >>>>> Thanks,
> > > > >> >>>>> Om
> > > > >> >>>>>
> > > > >> >>>>> On Tue, Feb 5, 2019 at 1:40
> > PM Harbs <
> > > > harbs.lists@gmail.com>
> > > > >> >>> wrote:
> > > > >> >>>>>
> > > > >> >>>>>> In a recent discussion, it
> > looks like
> > > other
> > > > projects have
> > > > >> gotten
> > > > >> >>>> resources
> > > > >> >>>>>> from AWS.
> > > > >> >>>>>>
> > > > >> >>>>>> Whatever service we use,
> > could setup a
> > > “shared”
> > > > Royale account
> > > > >> >>> that all
> > > > >> >>>>>> PMC members could have
> > access to.
> > > > >> >>>>>>
> > > > >> >>>>>> I don’t know if there’s
> some
> > way we
> > > could
> > > > leverage Gitlab’s
> > > > >> >>> integration
> > > > >> >>>>>> pipelines
> > > > >> >>>
> > > > >> >>
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=nfhbWtXmtxNEITbNNH4pvU37rQo6glA2VUBJFPC1Flg%3D&reserved=0
> > > > >> >>> <
> > > > >> >>>>>>
> > > > >> >>>
> > > > >> >>
> > > > >>
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=nfhbWtXmtxNEITbNNH4pvU37rQo6glA2VUBJFPC1Flg%3D&reserved=0
> > > > >> >>>>
> > > > >> >>>>>>
> > > > >> >>>>>>> On Feb 5, 2019, at 11:33
> > PM, Alex
> > > Harui
> > > > >> >> <aharui@adobe.com.INVALID
> > > > >> >>>>
> > > > >> >>>>>> wrote:
> > > > >> >>>>>>>
> > > > >> >>>>>>> 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" <
> > > > >> >> piotrzarzycki21@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.lists@gmail.com
> > > > >> >>> wrote:
> > > > >> >>>>>>>
> > > > >> >>>>>>>> A big +1 from me!
> > > > >> >>>>>>>>
> > > > >> >>>>>>>> Looking forward!
> > > > >> >>>>>>>>
> > > > >> >>>>>>>>> On Feb 5, 2019, at 9:34
> > PM, Alex
> > > Harui
> > > > >> >>> <ah...@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
> > > >
>
Re: 0.9.6 Release
Posted by Carlos Rovira <ca...@apache.org>.
Hi,
I think both ASDocs and MX are important. The first since is part of the
docs. In fact I switched focus to Modules since I was having problems with
ASDocs as I'm referring to each permalink from Royale Docs, that is one of
the main things we put in priority in our way to 1.0. MX in the other hand
is something others are waiting for so I think is expected in 0.9.6
My next actions will be to end Module example (although I'm still solving
some technical issues) and then go back to royale docs
El lun., 17 jun. 2019 a las 17:12, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> I will try to run MX Tests locally and see what is happening.
>
> pon., 17 cze 2019 o 17:08 Alex Harui <ah...@adobe.com.invalid>
> napisał(a):
>
> > ASDoc is not fully working for me. I've been working on that the past
> > several days. It took quite a while to fix the JSON output from new and
> > interesting ASDoc patterns. I'm now looking into failures due to changes
> > in coercion rules in the JS output. ASDoc was trying to save time by
> using
> > plain objects that were isomorphic to a class instead of actual class
> > instances.
> >
> > MXTests are failing on the CI server and probably locally but I haven't
> > gotten that far.
> >
> > I would think we want these things to work, but you are the RM so it is
> up
> > to you. Volunteers are welcome to help with these and other tasks.
> >
> > -Alex
> >
> > On 6/17/19, 12:44 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
> >
> > Hi Alex,
> >
> > I don't see any answer here - can I start with trying your
> instruction
> > and
> > start release ?
> >
> > Thanks,
> > Piotr
> >
> > śr., 12 cze 2019 o 10:12 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> > > Hi Alex,
> > > just build from scratch right now and seems maven and ant was ok
> > >
> > > El mié., 12 jun. 2019 a las 10:02, Alex Harui
> > (<ah...@adobe.com.invalid>)
> > > escribió:
> > >
> > > > The merge is complete, and the main builds seem to be successful,
> > except
> > > > for Maven on royale-asjs which was failing before the merge.
> > > >
> > > > I'm still catching up on other things, but I think there are some
> > bugs we
> > > > need to fix before cutting the release? I think ASDoc may not be
> > fully
> > > > working? What else?
> > > >
> > > > -Alex
> > > >
> > > > On 6/10/19, 11:05 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com>
> > > wrote:
> > > >
> > > > Hi Alex,
> > > >
> > > > Many thanks for that! I will try to be RM. I will have some
> > dedicated
> > > > time
> > > > for that. I will wait for your instruction and merge to
> > develop.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > >
> > > > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
> > <ah...@adobe.com.invalid>
> > > > wrote:
> > > >
> > > > > Well, that turned out to be much more time-consuming than I
> > > > expected, but
> > > > > we can now create identical release artifacts on Mac and
> > Win. I am
> > > > hopeful
> > > > > this effort will pay off not only now in having other folks
> > > generate
> > > > > releases, but also in the future if signed binaries become
> a
> > > > requirement.
> > > > >
> > > > > There continues to be a lot of distractions in my life that
> > can
> > > cause
> > > > > delays, but I hope to merge the release_practice branches
> > into
> > > > develop over
> > > > > the next day or two and figure out where in the wiki to
> > document
> > > the
> > > > > release process. So, now is the time for one or more
> people
> > to
> > > step
> > > > up to
> > > > > be the RMs for 0.9.6 and help debug and improve the
> process.
> > > > >
> > > > > I am going to try very hard not to "own" the process. If
> > something
> > > > goes
> > > > > wrong, I am going to ask others to try to debug and fix it
> > first
> > > > because it
> > > > > is in the project's best interests for others to truly
> > understand
> > > > how this
> > > > > stuff works.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 5/23/19, 9:54 AM, "Alex Harui" <aharui@adobe.com.INVALID
> >
> > > wrote:
> > > > >
> > > > > It has turned out to be harder than expected to get the
> > same
> > > > binaries
> > > > > on Mac and Win. I now have the identical binaries for
> > > > royale-compiler and
> > > > > royale-typedefs Maven artifacts and am starting on
> > royale-asjs. I
> > > > might
> > > > > get lucky and the changes that fixed royale-typedefs SWCs
> > will
> > > > magically
> > > > > get the royale-asjs SWCs to match. Then we have to make
> the
> > Ant
> > > > artifacts
> > > > > match.
> > > > >
> > > > > There have been a lot of distractions in my non-work
> > life which
> > > > has
> > > > > also impeded progress. I hope to make much progress this
> > coming
> > > > week and
> > > > > if we're lucky, I will be asking for a volunteer (or
> > volunteers) to
> > > > test
> > > > > drive all of this stuff and be the RM for 0.9.6. I am not
> > going to
> > > > be the
> > > > > RM.
> > > > >
> > > > > -Alex
> > > > >
> > > > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> > > piotrzarzycki21@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > Hi Alex,
> > > > >
> > > > > It's been a while since you have started effort
> with
> > > > automating
> > > > > build.
> > > > > Where are you with that ? Are we closer to started
> > 0.9.6.
> > > Do
> > > > you
> > > > > need any
> > > > > help with this ?
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > wt., 2 kwi 2019 o 19:30 Alex Harui
> > > <aharui@adobe.com.invalid
> > > > >
> > > > > napisał(a):
> > > > >
> > > > > > Update:
> > > > > >
> > > > > > In order to make verification of binary release
> > packages
> > > > created
> > > > > on the
> > > > > > server easier, I have made changes to our build
> > scripts
> > > and
> > > > > tools to try to
> > > > > > generate reproducible binaries. I've seen two
> > different
> > > > builds
> > > > > compare on
> > > > > > my Mac. The next challenge will be to see if
> the
> > server
> > > > can
> > > > > build a
> > > > > > package on Windows that will compare on Mac.
> > > > > >
> > > > > > One of the changes I needed to make is to JBurg.
> > The
> > > > version of
> > > > > JBurg we
> > > > > > use generates method names including a hash that
> > doesn't
> > > > > reproduce the same
> > > > > > name each time. I have changes to JBurg ready,
> > however
> > > > JBurg is
> > > > > currently
> > > > > > under CPL which is category B. We only need one
> > file, we
> > > > don't
> > > > > need or
> > > > > > want all of JBurg at this time. The one JBurg
> > file is
> > > > jointly
> > > > > owned by
> > > > > > Adobe and Tom Harwood. I've contact Tom and he
> > will be
> > > > filing
> > > > > an ICLA and
> > > > > > has given me permission to commit the lines he
> > owns in
> > > > that one
> > > > > file.
> > > > > >
> > > > > > This is the revision of the file that will be
> > donated by
> > > > > Tom/Adobe.
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=b70CftgUQmkNU%2BaLs8hw4ZcSCxhpoh4oZ%2FhJ9BCFjUQ%3D&reserved=0
> > > > > >
> > > > > > Once this file goes in with the changes to keep
> the
> > > method
> > > > names
> > > > > the same,
> > > > > > there will be more tweaks to the release tasks
> and
> > then
> > > we
> > > > can
> > > > > try cutting
> > > > > > a release. I'm thinking we'll be at that point
> in
> > early
> > > > May, so
> > > > > now is the
> > > > > > time to get stuff in for the 0.9.6 release.
> > > > > >
> > > > > > Thanks,
> > > > > > -Alex
> > > > > >
> > > > > > On 3/8/19, 9:27 AM, "Alex Harui" <
> aharui@adobe.com
> > >
> > > wrote:
> > > > > >
> > > > > > I would much rather have others find and fix
> > issues
> > > > > themselves. That
> > > > > > way, more people than just me will know how to
> > maintain
> > > the
> > > > > system. It
> > > > > > actually turns out that, IMO, a group of people
> > can work
> > > > on the
> > > > > release.
> > > > > > There are 14 steps. Literally, 14 different
> > people could
> > > > > execute one step
> > > > > > each.
> > > > > >
> > > > > > My 2 cents,
> > > > > > -Alex
> > > > > >
> > > > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> > > > carlosrovira@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > Hi Alex,
> > > > > >
> > > > > > amazing work! congrats to reach to this
> > point! :)
> > > > > >
> > > > > > I need to put my head on all of this, but
> > count
> > > on
> > > > me to
> > > > > be a RM.
> > > > > > I think
> > > > > > the best thing should be that you be the
> > first RM
> > > > to try
> > > > > your own
> > > > > > development at least for the first time,
> > and then
> > > > the
> > > > > rest of us
> > > > > > will
> > > > > > follow you on the next releases. With all
> > this on
> > > > place
> > > > > we maybe
> > > > > > could
> > > > > > release once a month or every two
> months...
> > > > > >
> > > > > > Thanks for doing this :)
> > > > > >
> > > > > > Carlos
> > > > > >
> > > > > >
> > > > > > El vie., 8 mar. 2019 a las 1:55, Alex
> Harui
> > > > > > (<ah...@adobe.com.invalid>)
> > > > > > escribió:
> > > > > >
> > > > > > > OK, I've now seen Jenkins perform the
> > steps to
> > > > build
> > > > > the release
> > > > > > > artifacts. Folks interested in
> > Docker-izing
> > > the
> > > > steps
> > > > > are
> > > > > > welcome to look
> > > > > > > at the jobs on the "Royale Release" tab
> > on the
> > > CI
> > > > > server.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GZZ35qSSBDcI24AgDEdV6o9ujYAT%2BB11a4%2FHeXiVnCY%3D&reserved=0
> > > > > > >
> > > > > > > These steps assume that the RM can run
> > the
> > > basic
> > > > Maven
> > > > > and Ant
> > > > > > build on
> > > > > > > the RM's computer. I think that's a
> fair
> > > > requirement
> > > > > since all
> > > > > > of us on the
> > > > > > > PMC need to able to do that to build
> the
> > RC in
> > > > order
> > > > > to vote on
> > > > > > it.
> > > > > > > Jenkins does other tasks like run the
> > Maven
> > > > release
> > > > > plugin
> > > > > > steps.
> > > > > > >
> > > > > > > Currently that results in binaries on
> > Jenkins
> > > > that are
> > > > > > downloaded to the
> > > > > > > RM's computer. These binaries need to
> be
> > > > verified by
> > > > > the RM
> > > > > > which is the
> > > > > > > next phase I will be starting on now.
> > The RM
> > > > verifies
> > > > > the bits
> > > > > > and then
> > > > > > > PGP signs them. And then the bits are
> > uploaded
> > > > off
> > > > > the RM's
> > > > > > computer to
> > > > > > > Maven Staging or dist.a.o/dev. If
> that
> > > > uploading
> > > > > turns out to
> > > > > > be a point
> > > > > > > of failure, we have the option of
> having
> > > Jenkins
> > > > > upload the big
> > > > > > files and
> > > > > > > have the RM only upload PGP signature
> > files.
> > > Or
> > > > > finding a way
> > > > > > for Jenkins
> > > > > > > to get the signature files from the RM.
> > The
> > > > uploads
> > > > > worked fine
> > > > > > for me,
> > > > > > > but then again, so did the old script's
> > > uploads.
> > > > > > >
> > > > > > > Therefore, once I get the binary
> > verification
> > > > phase
> > > > > completed, I
> > > > > > think
> > > > > > > someone other than me should be the RM
> > and try
> > > > to use
> > > > > these
> > > > > > steps to
> > > > > > > generate the release and help debug the
> > process
> > > > for
> > > > > the next
> > > > > > RM. So,
> > > > > > > please try to carve out some time to be
> > the RM.
> > > > One
> > > > > advantage
> > > > > > of doing
> > > > > > > most of the work on Jenkins is that it
> > frees up
> > > > my
> > > > > computer to
> > > > > > do other
> > > > > > > things while Jenkins is cranking away.
> > > > > > >
> > > > > > > I think we're at least a week away from
> > binary
> > > > > verification,
> > > > > > maybe two, so
> > > > > > > it is time to start thinking about what
> > is
> > > going
> > > > in
> > > > > this release.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > -Alex
> > > > > > >
> > > > > > > On 3/7/19, 4:15 PM, "Alex Harui"
> > > > > <ah...@adobe.com.INVALID>
> > > > > > wrote:
> > > > > > >
> > > > > > > In case you haven't guessed, I'm
> > testing
> > > out
> > > > > Jenkins and its
> > > > > > ability
> > > > > > > to create the artifacts and send
> emails.
> > > Please
> > > > > ignore any
> > > > > > email that
> > > > > > > looks like a vote or discuss thread.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > -Alex
> > > > > > >
> > > > > > > On 2/10/19, 8:44 PM, "Alex Harui"
> > > > > <ah...@adobe.com.INVALID>
> > > > > > wrote:
> > > > > > >
> > > > > > > Om,
> > > > > > >
> > > > > > > Well, that's what I used for
> the
> > last
> > > > > release. I'm sure
> > > > > > there is
> > > > > > > probably some inaccuracy in it.
> > > > > > >
> > > > > > > That said, I'm abandoning that
> > document
> > > > and
> > > > > taking a new
> > > > > > angle
> > > > > > > because that document presumed that the
> > release
> > > > > manager was
> > > > > > trying to
> > > > > > > create a release on his/her computer.
> > I've
> > > > given up
> > > > > on that and
> > > > > > working on
> > > > > > > making releases from a shared computer
> > for the
> > > > reasons
> > > > > I've
> > > > > > stated
> > > > > > > upthread. I hope to make some progress
> > on that
> > > > this
> > > > > week.
> > > > > > >
> > > > > > > The key difference is that the
> > new
> > > angle
> > > > does
> > > > > not
> > > > > > presume that you
> > > > > > > have Git SSH and PGP signatures all set
> > up on
> > > > some
> > > > > computer. I
> > > > > > have not
> > > > > > > looked into how Docker would handle
> > that. You
> > > > > certainly
> > > > > > wouldn't want the
> > > > > > > Docker image to contain your SSH or PGP
> > > > keys/creds.
> > > > > And if the
> > > > > > Docker
> > > > > > > image doesn't, then that is another
> > stumbling
> > > > block
> > > > > for future
> > > > > > RMs.
> > > > > > >
> > > > > > > The other key difference is
> that
> > the
> > > old
> > > > > script presumed
> > > > > > you could
> > > > > > > create the 3 release in 3 huge "easy"
> > steps.
> > > > We've
> > > > > seen that is
> > > > > > only true
> > > > > > > for me. So the new angle creates many
> > discrete
> > > > steps
> > > > > managed by
> > > > > > Jenkins.
> > > > > > >
> > > > > > > So, it is up to you to decide
> > what you
> > > > want to
> > > > > > "Docker-ize". You
> > > > > > > can try to Docker-ize the current 3 big
> > steps,
> > > > so RMs
> > > > > can try to
> > > > > > run it on
> > > > > > > their systems, but I'd bet they will
> > just faiI
> > > > due to
> > > > > network
> > > > > > issues. I
> > > > > > > would be interested in using Docker to
> > make
> > > each
> > > > of
> > > > > these many
> > > > > > discrete
> > > > > > > steps portable to another server. I'm
> > not
> > > > going to
> > > > > involve
> > > > > > Docker at this
> > > > > > > point. My main goal is just to see if
> I
> > can
> > > > create a
> > > > > workflow
> > > > > > of many
> > > > > > > discrete steps that isn't horribly
> > painful.
> > > > Once we
> > > > > see what
> > > > > > these steps
> > > > > > > turn out to be, then we can worry about
> > server
> > > > > portability of
> > > > > > those steps.
> > > > > > >
> > > > > > > Either way, we want to know
> about
> > > running
> > > > > > Browser+Selenium for
> > > > > > > sure. And maybe FlashPlayerDebugger or
> > AIR. I
> > > > would
> > > > > want to
> > > > > > know, for
> > > > > > > example, how you debug a failing
> > checkintest
> > > in a
> > > > > Docker
> > > > > > container.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > -Alex
> > > > > > >
> > > > > > >
> > > > > > > On 2/10/19, 5:18 PM, "OmPrakash
> > > > Muppirala" <
> > > > > > bigosmallm@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > Alex,
> > > > > > >
> > > > > > > Just to be clear, I am
> > following
> > > the
> > > > steps
> > > > > from here
> > > > > > to try
> > > > > > > and setup a
> > > > > > > docker container.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=%2F9mdYnvJTSx1BVR6I0FyoH%2BbKSbiCET7hCoO1y%2FvgrQ%3D&reserved=0
> > > > > > >
> > > > > > > Is this doc up to date?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Om
> > > > > > >
> > > > > > > On Wed, Feb 6, 2019 at
> 12:02
> > PM
> > > > OmPrakash
> > > > > Muppirala <
> > > > > > > bigosmallm@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > One approach is to have
> > each step
> > > > in the
> > > > > process
> > > > > > spin up a
> > > > > > > docker image.
> > > > > > > > And use docker-compose to
> > run
> > > each
> > > > > step. All the
> > > > > > images can
> > > > > > > be made to
> > > > > > > > share a common volume
> > where all
> > > the
> > > > > artifacts are
> > > > > > stored
> > > > > > > across steps.
> > > > > > > >
> > > > > > > > You are right about the
> > > networking
> > > > issue
> > > > > though.
> > > > > > Any
> > > > > > > network related
> > > > > > > > failure that occurs on
> the
> > host
> > > > machine
> > > > > will most
> > > > > > likely
> > > > > > > occur in the
> > > > > > > > docker container.
> > Although, I am
> > > > not
> > > > > clear how we
> > > > > > can
> > > > > > > guarantee that the
> > > > > > > > same issues will not
> occur
> > on the
> > > > > Jenkins server.
> > > > > > I mean,
> > > > > > > what is special
> > > > > > > > about the Jenkins server
> > that
> > > > makes it
> > > > > immune to
> > > > > > these
> > > > > > > networking issues?
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Om
> > > > > > > >
> > > > > > > > On Wed, Feb 6, 2019 at
> > 11:48 AM
> > > > Alex
> > > > > Harui
> > > > > > > <ah...@adobe.com.invalid>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Again, I don't know
> > anything
> > > about
> > > > > Docker, but
> > > > > > before we
> > > > > > > spend a lot of
> > > > > > > >> time on Docker, I also
> > want to
> > > > point
> > > > > out that the
> > > > > > process
> > > > > > > to create a
> > > > > > > >> release cannot really be
> > thought
> > > > of as
> > > > > "one
> > > > > > application".
> > > > > > > It will be a
> > > > > > > >> series of "steps" to
> > run. How
> > > > many
> > > > > steps
> > > > > > depends on
> > > > > > > whether we think we
> > > > > > > >> can isolate enough stuff
> > via
> > > > Docker to
> > > > > be able to
> > > > > > run
> > > > > > > Docker on the RM's
> > > > > > > >> computer instead of some
> > shared
> > > > > computer. On a
> > > > > > shared
> > > > > > > computer there will
> > > > > > > >> be dozens of steps
> > because the
> > > RM
> > > > will
> > > > > need to
> > > > > > enter
> > > > > > > passwords to commit
> > > > > > > >> stuff. On a local
> > computer I
> > > > guess the
> > > > > RM can
> > > > > > supply
> > > > > > > passwords but I think
> > > > > > > >> there will be stopping
> > points
> > > > where the
> > > > > Maven
> > > > > > artifacts are
> > > > > > > deployed and
> > > > > > > >> the staging repo is
> > closed, and
> > > > another
> > > > > stopping
> > > > > > point for
> > > > > > > the vote. It
> > > > > > > >> seems like Docker works
> by
> > > > downloading
> > > > > > dependencies. Given
> > > > > > > that the
> > > > > > > >> problem the RMs had last
> > time
> > > > involved
> > > > > downloads
> > > > > > and
> > > > > > > uploads, why do we
> > > > > > > >> think Docker will really
> > solve
> > > > this for
> > > > > creating
> > > > > > releases
> > > > > > > on local machines?
> > > > > > > >>
> > > > > > > >> The reason to do this
> on a
> > > shared
> > > > > machine is so
> > > > > > that new
> > > > > > > RMs don't have
> > > > > > > >> to do as much setup.
> But
> > then I
> > > > wonder
> > > > > about the
> > > > > > > efficiency of kicking off
> > > > > > > >> that many Docker images.
> > > Jenkins
> > > > can
> > > > > manage that
> > > > > > already.
> > > > > > > Does Docker
> > > > > > > >> have some sort of
> similar
> > > > Dashboard or
> > > > > would we
> > > > > > use Jenkins
> > > > > > > to kick off
> > > > > > > >> Docker steps? I can't
> > quite
> > > > picture
> > > > > what is the
> > > > > > outermost
> > > > > > > >> control/dashboard.
> > > > > > > >>
> > > > > > > >> -Alex
> > > > > > > >>
> > > > > > > >> On 2/6/19, 11:03 AM,
> > "Harbs" <
> > > > > > harbs.lists@gmail.com> wrote:
> > > > > > > >>
> > > > > > > >> A quick search turns
> > up
> > > this:
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=L%2FSQRtItveWwGWXpiz5ImQHJ%2BD0kyqIWy9%2BN8KFpfGg%3D&reserved=0
> > > > > > > >> <
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=L%2FSQRtItveWwGWXpiz5ImQHJ%2BD0kyqIWy9%2BN8KFpfGg%3D&reserved=0
> > > > > > > >> >
> > > > > > > >>
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GgxPOsJMU7xnieSkFk%2FF5Ntp75tvg4y8VVOJitIEEYI%3D&reserved=0
> > > > > > > >> <
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GgxPOsJMU7xnieSkFk%2FF5Ntp75tvg4y8VVOJitIEEYI%3D&reserved=0
> > > > > > > >> >
> > > > > > > >>
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=oAwxtBcYuuB73255nFD40k2NqnLKIJWo92htZkychLc%3D&reserved=0
> > > > > > > >> <
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=oAwxtBcYuuB73255nFD40k2NqnLKIJWo92htZkychLc%3D&reserved=0
> > > > > > > >> >
> > > > > > > >>
> > > > > > > >> > On Feb 6, 2019, at
> > 8:59
> > > PM,
> > > > Alex
> > > > > Harui
> > > > > > > <ah...@adobe.com.INVALID>
> > > > > > > >> wrote:
> > > > > > > >> >
> > > > > > > >> > Thanks for
> > volunteering to
> > > > try it
> > > > > Om. IMO,
> > > > > > even more
> > > > > > > important
> > > > > > > >> than Firefox+Flash is
> > > > > SomeBrowser+Selenium. We
> > > > > > may also
> > > > > > > need to run Adobe
> > > > > > > >> AIR's adb. We could
> > probably
> > > > turn off
> > > > > the Flash
> > > > > > tests or
> > > > > > > replace Flash
> > > > > > > >> with AIR.
> > > > > > > >> >
> > > > > > > >> > Thanks,
> > > > > > > >> > -Alex
> > > > > > > >> >
> > > > > > > >> > On 2/6/19, 10:54
> AM,
> > > "Carlos
> > > > > Rovira" <
> > > > > > > carlosrovira@apache.org>
> > > > > > > >> wrote:
> > > > > > > >> >
> > > > > > > >> > Hi Om, that
> > would be
> > > > great!
> > > > > waiting for
> > > > > > your
> > > > > > > experience with a
> > > > > > > >> that! :)
> > > > > > > >> >
> > > > > > > >> > El mié., 6 feb.
> > 2019 a
> > > > las
> > > > > 19:31,
> > > > > > OmPrakash
> > > > > > > Muppirala (<
> > > > > > > >> bigosmallm@gmail.com>)
> > > > > > > >> > escribió:
> > > > > > > >> >
> > > > > > > >> >> Yes, I agree with
> > Alex
> > > > about not
> > > > > being
> > > > > > able to run
> > > > > > > UI out of docker
> > > > > > > >> >> containers. I
> > never
> > > > thought of
> > > > > the
> > > > > > checkintests
> > > > > > > when I made the
> > > > > > > >> >> suggestion.
> > > > > > > >> >>
> > > > > > > >> >> The firefox-flash
> > image
> > > > that
> > > > > Yishay
> > > > > > pointed out
> > > > > > > looks promising.
> > > > > > > >> I will
> > > > > > > >> >> poke around with
> > it and
> > > > see if
> > > > > that works
> > > > > > for us.
> > > > > > > >> >>
> > > > > > > >> >> Thanks,
> > > > > > > >> >> Om
> > > > > > > >> >>
> > > > > > > >> >> On Wed, Feb 6,
> > 2019 at
> > > > 12:41 AM
> > > > > Yishay
> > > > > > Weiss <
> > > > > > > >> yishayjobs@hotmail.com>
> > > > > > > >> >> wrote:
> > > > > > > >> >>
> > > > > > > >> >>> I’ll let Om or
> > someone
> > > > else
> > > > > with docker
> > > > > > experience
> > > > > > > tell us if
> > > > > > > >> this [1] is
> > > > > > > >> >>> relevant.
> > > > > > > >> >>>
> > > > > > > >> >>>
> > > > > > > >> >>>
> > > > > > > >> >>> [1]
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=oE4%2F%2FqGiaVmCU3VShIMUbUMJc%2BiwF%2F07dkEgYhcgQJA%3D&reserved=0
> > > > > > > >> >>>
> > > > > > > >> >>>
> > > > > > > >> >>>
> > > > > > > >> >>>
> > > > ________________________________
> > > > > > > >> >>> From: Alex Harui
> > > > > <aharui@adobe.com.INVALID
> > > > > > >
> > > > > > > >> >>> Sent: Wednesday,
> > > February
> > > > 6,
> > > > > 2019
> > > > > > 10:05:54 AM
> > > > > > > >> >>> To:
> > > dev@royale.apache.org
> > > > > > > >> >>> Subject: Re:
> 0.9.6
> > > Release
> > > > > > > >> >>>
> > > > > > > >> >>> I don't anything
> > about
> > > > docker,
> > > > > but in 15
> > > > > > minutes of
> > > > > > > reading I ran
> > > > > > > >> into
> > > > > > > >> >>> this:
> > > > > > > >> >>>
> > > > > > > >> >>>
> > > > > > > >> >>
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=iyP6ZrHSV24Ykd5zjCPwrQYD%2F378Ek9pHNj4n2mTIp8%3D&reserved=0
> > > > > > > >> >>>
> > > > > > > >> >>> Which says:
> > Docker can't
> > > > " Run
> > > > > > applications with
> > > > > > > graphical
> > > > > > > >> interfaces".
> > > > > > > >> >>> If you want
> > Royale to
> > > use
> > > > > Docker for
> > > > > > releases, show
> > > > > > > that it can
> > > > > > > >> run
> > > > > > > >> >>> checkintests
> with
> > Flash
> > > > and the
> > > > > Browser.
> > > > > > Then I
> > > > > > > will look into
> > > > > > > >> it more.
> > > > > > > >> >>>
> > > > > > > >> >>> The highest
> level
> > goal
> > > is
> > > > to
> > > > > make it as
> > > > > > easy as
> > > > > > > possible for
> > > > > > > >> someone to
> > > > > > > >> >>> volunteer to be
> > an RM.
> > > > Any
> > > > > requirement
> > > > > > of "install
> > > > > > > this (Docker,
> > > > > > > >> etc) on
> > > > > > > >> >>> your computer"
> > is, IMO,
> > > > another
> > > > > barrier
> > > > > > to entry.
> > > > > > > Yeah, RMs will
> > > > > > > >> have to
> > > > > > > >> >>> have Maven
> > installed and
> > > > maybe
> > > > > Ant, but
> > > > > > you should
> > > > > > > already have
> > > > > > > >> those
> > > > > > > >> >>> installed to be
> a
> > > > committer/PMC
> > > > > member.
> > > > > > > >> >>>
> > > > > > > >> >>> That said, a
> good
> > > > takeaway from
> > > > > the
> > > > > > Docker idea is
> > > > > > > to try to find
> > > > > > > >> a way
> > > > > > > >> >> to
> > > > > > > >> >>> make an "Image"
> of
> > > > whatever we
> > > > > end up
> > > > > > with on
> > > > > > > whatever server we
> > > > > > > >> end up
> > > > > > > >> >>> using so if the
> > image
> > > can
> > > > be
> > > > > copied and
> > > > > > used on
> > > > > > > other servers.
> > > > > > > >> I'm not
> > > > > > > >> >>> exactly sure how
> > to do
> > > > that
> > > > > with Azure,
> > > > > > which hosts
> > > > > > > my CI
> > > > > > > >> server. I will
> > > > > > > >> >>> spend a few more
> > minutes
> > > > > researching that.
> > > > > > > >> >>>
> > > > > > > >> >>> I could not
> > quickly find
> > > > any
> > > > > way to get a
> > > > > > free VM
> > > > > > > on Azure or AWS
> > > > > > > >> that
> > > > > > > >> >>> isn't a
> > > > > > free-trial-start-paying-after-a-year. So,
> > > > > > > unless someone
> > > > > > > >> comes
> > > > > > > >> >> up
> > > > > > > >> >>> with a free
> > server we
> > > can
> > > > use
> > > > > "forever",
> > > > > > I'm going
> > > > > > > to just start
> > > > > > > >> with my
> > > > > > > >> >>> Azure VM.
> > > > > > > >> >>>
> > > > > > > >> >>> -Alex
> > > > > > > >> >>>
> > > > > > > >> >>> On 2/5/19, 10:59
> > PM,
> > > > "Carlos
> > > > > Rovira" <
> > > > > > > carlosrovira@apache.org>
> > > > > > > >> wrote:
> > > > > > > >> >>>
> > > > > > > >> >>> Hi.
> > > > > > > >> >>>
> > > > > > > >> >>> the plan
> > sounds very
> > > > good to
> > > > > me. Just
> > > > > > my 2
> > > > > > > thoughts on this:
> > > > > > > >> >>>
> > > > > > > >> >>> 1.- As I was
> > reading
> > > I
> > > > was
> > > > > thinking as
> > > > > > well on
> > > > > > > something like
> > > > > > > >> Docker
> > > > > > > >> >>> and
> > > > > > > >> >>> see Om as
> well
> > > > thinking on
> > > > > the same.
> > > > > > Maybe is
> > > > > > > the way to this
> > > > > > > >> with
> > > > > > > >> >> the
> > > > > > > >> >>> actual
> > technology.
> > > > Seems VMs
> > > > > are
> > > > > > stepping out a
> > > > > > > bit this days
> > > > > > > >> in
> > > > > > > >> >> favor
> > > > > > > >> >>> of
> > > > > > > >> >>> things like
> > Docker.
> > > > Maybe
> > > > > the same did
> > > > > > Git over
> > > > > > > Svn, and today
> > > > > > > >> Svn is
> > > > > > > >> >>> an
> > > > > > > >> >>> old
> > remembrance. I
> > > > must say
> > > > > that I
> > > > > > have no
> > > > > > > experience with
> > > > > > > >> Docker, so
> > > > > > > >> >>> doing
> > > > > > > >> >>> that will
> > require
> > > > acquire
> > > > > that
> > > > > > knowledge, but
> > > > > > > seems it could
> > > > > > > >> be worth
> > > > > > > >> >>> it.
> > > > > > > >> >>>
> > > > > > > >> >>> 2.- Maybe is
> > not
> > > > possible,
> > > > > but I want
> > > > > > to propose
> > > > > > > to do this
> > > > > > > >> work I a
> > > > > > > >> >>> separate
> > branch, so
> > > it
> > > > could
> > > > > be in
> > > > > > parallel to
> > > > > > > other
> > > > > > > >> developments. I
> > > > > > > >> >>> think
> > > > > > > >> >>> work over
> > develop is
> > > > > practical if
> > > > > > there's
> > > > > > > something tiny that
> > > > > > > >> could
> > > > > > > >> >> be
> > > > > > > >> >>> done
> > > > > > > >> >>> in a commit.
> > But as
> > > we
> > > > need
> > > > > more than
> > > > > > one, or is
> > > > > > > a long
> > > > > > > >> process (like
> > > > > > > >> >>> this),
> chances
> > are to
> > > > make
> > > > > develop
> > > > > > branch
> > > > > > > unstable and even
> > > > > > > >> for some
> > > > > > > >> >>> days.
> > > > > > > >> >>> I think we
> > should try
> > > > to
> > > > > avoid that
> > > > > > scenario,
> > > > > > > and branches are
> > > > > > > >> the
> > > > > > > >> >> best
> > > > > > > >> >>> way. If we do
> > this
> > > way,
> > > > > we'll benefit
> > > > > > of more
> > > > > > > reliable develop
> > > > > > > >> >> branch.
> > > > > > > >> >>>
> > > > > > > >> >>> Thanks and
> > good to
> > > > know of
> > > > > this plan :)
> > > > > > > >> >>>
> > > > > > > >> >>> Carlos
> > > > > > > >> >>>
> > > > > > > >> >>>
> > > > > > > >> >>> El mar., 5
> > feb. 2019
> > > a
> > > > las
> > > > > 23:19,
> > > > > > Harbs (<
> > > > > > > >> harbs.lists@gmail.com>)
> > > > > > > >> >>> escribió:
> > > > > > > >> >>>
> > > > > > > >> >>>> I’ve never used
> > Docker
> > > > myself,
> > > > > but that
> > > > > > might be a
> > > > > > > good plan.
> > > > > > > >> >>>>
> > > > > > > >> >>>>> On Feb 6,
> 2019,
> > at
> > > > 12:07 AM,
> > > > > OmPrakash
> > > > > > Muppirala <
> > > > > > > >> >>>
> > bigosmallm@gmail.com>
> > > > > > > >> >>>> wrote:
> > > > > > > >> >>>>>
> > > > > > > >> >>>>> I was
> wondering
> > if we
> > > > can use
> > > > > docker
> > > > > > images to
> > > > > > > setup and seal
> > > > > > > >> the
> > > > > > > >> >>> RM
> > > > > > > >> >>>>> environment.
> > Then
> > > > other RMs
> > > > > simply
> > > > > > need to run
> > > > > > > the image
> > > > > > > >> locally
> > > > > > > >> >>> and run
> > > > > > > >> >>>>> the release
> > scripts.
> > > > Might
> > > > > be easier.
> > > > > > If folks
> > > > > > > like this plan,
> > > > > > > >> >> I
> > > > > > > >> >>> can
> > > > > > > >> >>>> try
> > > > > > > >> >>>>> to put
> something
> > > > together.
> > > > > > > >> >>>>>
> > > > > > > >> >>>>> Thanks,
> > > > > > > >> >>>>> Om
> > > > > > > >> >>>>>
> > > > > > > >> >>>>> On Tue, Feb 5,
> > 2019 at
> > > > 1:40
> > > > > PM Harbs <
> > > > > > > harbs.lists@gmail.com>
> > > > > > > >> >>> wrote:
> > > > > > > >> >>>>>
> > > > > > > >> >>>>>> In a recent
> > > > discussion, it
> > > > > looks like
> > > > > > other
> > > > > > > projects have
> > > > > > > >> gotten
> > > > > > > >> >>>> resources
> > > > > > > >> >>>>>> from AWS.
> > > > > > > >> >>>>>>
> > > > > > > >> >>>>>> Whatever
> > service we
> > > > use,
> > > > > could setup a
> > > > > > “shared”
> > > > > > > Royale account
> > > > > > > >> >>> that all
> > > > > > > >> >>>>>> PMC members
> > could
> > > have
> > > > > access to.
> > > > > > > >> >>>>>>
> > > > > > > >> >>>>>> I don’t know
> if
> > > > there’s some
> > > > > way we
> > > > > > could
> > > > > > > leverage Gitlab’s
> > > > > > > >> >>> integration
> > > > > > > >> >>>>>> pipelines
> > > > > > > >> >>>
> > > > > > > >> >>
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GSexC31IRXLohkmy%2F1kx1PrVgcu0Ixu1%2BtQNMaCOUr4%3D&reserved=0
> > > > > > > >> >>> <
> > > > > > > >> >>>>>>
> > > > > > > >> >>>
> > > > > > > >> >>
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GSexC31IRXLohkmy%2F1kx1PrVgcu0Ixu1%2BtQNMaCOUr4%3D&reserved=0
> > > > > > > >> >>>>
> > > > > > > >> >>>>>>
> > > > > > > >> >>>>>>> On Feb 5,
> > 2019, at
> > > > 11:33
> > > > > PM, Alex
> > > > > > Harui
> > > > > > > >> >>
> > <aharui@adobe.com.INVALID
> > > > > > > >> >>>>
> > > > > > > >> >>>>>> wrote:
> > > > > > > >> >>>>>>>
> > > > > > > >> >>>>>>> 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" <
> > > > > > > >> >>
> > > piotrzarzycki21@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.lists@gmail.com
> > > > > > > >> >>> wrote:
> > > > > > > >> >>>>>>>
> > > > > > > >> >>>>>>>> A big +1
> > from me!
> > > > > > > >> >>>>>>>>
> > > > > > > >> >>>>>>>> Looking
> > forward!
> > > > > > > >> >>>>>>>>
> > > > > > > >> >>>>>>>>> On Feb 5,
> > 2019, at
> > > > 9:34
> > > > > PM, Alex
> > > > > > Harui
> > > > > > > >> >>>
> > > <aharui@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
> > > > > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > Carlos Rovira
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542823006545&sdata=IqYeRFQyKmIse1xD5qA8MUPMadljfjLBbzYayWw6AtQ%3D&reserved=0
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542823006545&sdata=5VexoocnThIqHb1XE5tl%2BFl6awXBdtxBIPVrXX9r5LI%3D&reserved=0
> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542823006545&sdata=5VexoocnThIqHb1XE5tl%2BFl6awXBdtxBIPVrXX9r5LI%3D&reserved=0
> > >*
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: 0.9.6 Release
Posted by Piotr Zarzycki <pi...@gmail.com>.
I will try to run MX Tests locally and see what is happening.
pon., 17 cze 2019 o 17:08 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> ASDoc is not fully working for me. I've been working on that the past
> several days. It took quite a while to fix the JSON output from new and
> interesting ASDoc patterns. I'm now looking into failures due to changes
> in coercion rules in the JS output. ASDoc was trying to save time by using
> plain objects that were isomorphic to a class instead of actual class
> instances.
>
> MXTests are failing on the CI server and probably locally but I haven't
> gotten that far.
>
> I would think we want these things to work, but you are the RM so it is up
> to you. Volunteers are welcome to help with these and other tasks.
>
> -Alex
>
> On 6/17/19, 12:44 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> Hi Alex,
>
> I don't see any answer here - can I start with trying your instruction
> and
> start release ?
>
> Thanks,
> Piotr
>
> śr., 12 cze 2019 o 10:12 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Hi Alex,
> > just build from scratch right now and seems maven and ant was ok
> >
> > El mié., 12 jun. 2019 a las 10:02, Alex Harui
> (<ah...@adobe.com.invalid>)
> > escribió:
> >
> > > The merge is complete, and the main builds seem to be successful,
> except
> > > for Maven on royale-asjs which was failing before the merge.
> > >
> > > I'm still catching up on other things, but I think there are some
> bugs we
> > > need to fix before cutting the release? I think ASDoc may not be
> fully
> > > working? What else?
> > >
> > > -Alex
> > >
> > > On 6/10/19, 11:05 AM, "Piotr Zarzycki" <pi...@gmail.com>
> > wrote:
> > >
> > > Hi Alex,
> > >
> > > Many thanks for that! I will try to be RM. I will have some
> dedicated
> > > time
> > > for that. I will wait for your instruction and merge to
> develop.
> > >
> > > Thanks,
> > > Piotr
> > >
> > >
> > > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
> <ah...@adobe.com.invalid>
> > > wrote:
> > >
> > > > Well, that turned out to be much more time-consuming than I
> > > expected, but
> > > > we can now create identical release artifacts on Mac and
> Win. I am
> > > hopeful
> > > > this effort will pay off not only now in having other folks
> > generate
> > > > releases, but also in the future if signed binaries become a
> > > requirement.
> > > >
> > > > There continues to be a lot of distractions in my life that
> can
> > cause
> > > > delays, but I hope to merge the release_practice branches
> into
> > > develop over
> > > > the next day or two and figure out where in the wiki to
> document
> > the
> > > > release process. So, now is the time for one or more people
> to
> > step
> > > up to
> > > > be the RMs for 0.9.6 and help debug and improve the process.
> > > >
> > > > I am going to try very hard not to "own" the process. If
> something
> > > goes
> > > > wrong, I am going to ask others to try to debug and fix it
> first
> > > because it
> > > > is in the project's best interests for others to truly
> understand
> > > how this
> > > > stuff works.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID>
> > wrote:
> > > >
> > > > It has turned out to be harder than expected to get the
> same
> > > binaries
> > > > on Mac and Win. I now have the identical binaries for
> > > royale-compiler and
> > > > royale-typedefs Maven artifacts and am starting on
> royale-asjs. I
> > > might
> > > > get lucky and the changes that fixed royale-typedefs SWCs
> will
> > > magically
> > > > get the royale-asjs SWCs to match. Then we have to make the
> Ant
> > > artifacts
> > > > match.
> > > >
> > > > There have been a lot of distractions in my non-work
> life which
> > > has
> > > > also impeded progress. I hope to make much progress this
> coming
> > > week and
> > > > if we're lucky, I will be asking for a volunteer (or
> volunteers) to
> > > test
> > > > drive all of this stuff and be the RM for 0.9.6. I am not
> going to
> > > be the
> > > > RM.
> > > >
> > > > -Alex
> > > >
> > > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> > piotrzarzycki21@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > Hi Alex,
> > > >
> > > > It's been a while since you have started effort with
> > > automating
> > > > build.
> > > > Where are you with that ? Are we closer to started
> 0.9.6.
> > Do
> > > you
> > > > need any
> > > > help with this ?
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > wt., 2 kwi 2019 o 19:30 Alex Harui
> > <aharui@adobe.com.invalid
> > > >
> > > > napisał(a):
> > > >
> > > > > Update:
> > > > >
> > > > > In order to make verification of binary release
> packages
> > > created
> > > > on the
> > > > > server easier, I have made changes to our build
> scripts
> > and
> > > > tools to try to
> > > > > generate reproducible binaries. I've seen two
> different
> > > builds
> > > > compare on
> > > > > my Mac. The next challenge will be to see if the
> server
> > > can
> > > > build a
> > > > > package on Windows that will compare on Mac.
> > > > >
> > > > > One of the changes I needed to make is to JBurg.
> The
> > > version of
> > > > JBurg we
> > > > > use generates method names including a hash that
> doesn't
> > > > reproduce the same
> > > > > name each time. I have changes to JBurg ready,
> however
> > > JBurg is
> > > > currently
> > > > > under CPL which is category B. We only need one
> file, we
> > > don't
> > > > need or
> > > > > want all of JBurg at this time. The one JBurg
> file is
> > > jointly
> > > > owned by
> > > > > Adobe and Tom Harwood. I've contact Tom and he
> will be
> > > filing
> > > > an ICLA and
> > > > > has given me permission to commit the lines he
> owns in
> > > that one
> > > > file.
> > > > >
> > > > > This is the revision of the file that will be
> donated by
> > > > Tom/Adobe.
> > > > >
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=b70CftgUQmkNU%2BaLs8hw4ZcSCxhpoh4oZ%2FhJ9BCFjUQ%3D&reserved=0
> > > > >
> > > > > Once this file goes in with the changes to keep the
> > method
> > > names
> > > > the same,
> > > > > there will be more tweaks to the release tasks and
> then
> > we
> > > can
> > > > try cutting
> > > > > a release. I'm thinking we'll be at that point in
> early
> > > May, so
> > > > now is the
> > > > > time to get stuff in for the 0.9.6 release.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 3/8/19, 9:27 AM, "Alex Harui" <aharui@adobe.com
> >
> > wrote:
> > > > >
> > > > > I would much rather have others find and fix
> issues
> > > > themselves. That
> > > > > way, more people than just me will know how to
> maintain
> > the
> > > > system. It
> > > > > actually turns out that, IMO, a group of people
> can work
> > > on the
> > > > release.
> > > > > There are 14 steps. Literally, 14 different
> people could
> > > > execute one step
> > > > > each.
> > > > >
> > > > > My 2 cents,
> > > > > -Alex
> > > > >
> > > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> > > carlosrovira@apache.org>
> > > > wrote:
> > > > >
> > > > > Hi Alex,
> > > > >
> > > > > amazing work! congrats to reach to this
> point! :)
> > > > >
> > > > > I need to put my head on all of this, but
> count
> > on
> > > me to
> > > > be a RM.
> > > > > I think
> > > > > the best thing should be that you be the
> first RM
> > > to try
> > > > your own
> > > > > development at least for the first time,
> and then
> > > the
> > > > rest of us
> > > > > will
> > > > > follow you on the next releases. With all
> this on
> > > place
> > > > we maybe
> > > > > could
> > > > > release once a month or every two months...
> > > > >
> > > > > Thanks for doing this :)
> > > > >
> > > > > Carlos
> > > > >
> > > > >
> > > > > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > > > > (<ah...@adobe.com.invalid>)
> > > > > escribió:
> > > > >
> > > > > > OK, I've now seen Jenkins perform the
> steps to
> > > build
> > > > the release
> > > > > > artifacts. Folks interested in
> Docker-izing
> > the
> > > steps
> > > > are
> > > > > welcome to look
> > > > > > at the jobs on the "Royale Release" tab
> on the
> > CI
> > > > server.
> > > > > >
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GZZ35qSSBDcI24AgDEdV6o9ujYAT%2BB11a4%2FHeXiVnCY%3D&reserved=0
> > > > > >
> > > > > > These steps assume that the RM can run
> the
> > basic
> > > Maven
> > > > and Ant
> > > > > build on
> > > > > > the RM's computer. I think that's a fair
> > > requirement
> > > > since all
> > > > > of us on the
> > > > > > PMC need to able to do that to build the
> RC in
> > > order
> > > > to vote on
> > > > > it.
> > > > > > Jenkins does other tasks like run the
> Maven
> > > release
> > > > plugin
> > > > > steps.
> > > > > >
> > > > > > Currently that results in binaries on
> Jenkins
> > > that are
> > > > > downloaded to the
> > > > > > RM's computer. These binaries need to be
> > > verified by
> > > > the RM
> > > > > which is the
> > > > > > next phase I will be starting on now.
> The RM
> > > verifies
> > > > the bits
> > > > > and then
> > > > > > PGP signs them. And then the bits are
> uploaded
> > > off
> > > > the RM's
> > > > > computer to
> > > > > > Maven Staging or dist.a.o/dev. If that
> > > uploading
> > > > turns out to
> > > > > be a point
> > > > > > of failure, we have the option of having
> > Jenkins
> > > > upload the big
> > > > > files and
> > > > > > have the RM only upload PGP signature
> files.
> > Or
> > > > finding a way
> > > > > for Jenkins
> > > > > > to get the signature files from the RM.
> The
> > > uploads
> > > > worked fine
> > > > > for me,
> > > > > > but then again, so did the old script's
> > uploads.
> > > > > >
> > > > > > Therefore, once I get the binary
> verification
> > > phase
> > > > completed, I
> > > > > think
> > > > > > someone other than me should be the RM
> and try
> > > to use
> > > > these
> > > > > steps to
> > > > > > generate the release and help debug the
> process
> > > for
> > > > the next
> > > > > RM. So,
> > > > > > please try to carve out some time to be
> the RM.
> > > One
> > > > advantage
> > > > > of doing
> > > > > > most of the work on Jenkins is that it
> frees up
> > > my
> > > > computer to
> > > > > do other
> > > > > > things while Jenkins is cranking away.
> > > > > >
> > > > > > I think we're at least a week away from
> binary
> > > > verification,
> > > > > maybe two, so
> > > > > > it is time to start thinking about what
> is
> > going
> > > in
> > > > this release.
> > > > > >
> > > > > > Thanks,
> > > > > > -Alex
> > > > > >
> > > > > > On 3/7/19, 4:15 PM, "Alex Harui"
> > > > <ah...@adobe.com.INVALID>
> > > > > wrote:
> > > > > >
> > > > > > In case you haven't guessed, I'm
> testing
> > out
> > > > Jenkins and its
> > > > > ability
> > > > > > to create the artifacts and send emails.
> > Please
> > > > ignore any
> > > > > email that
> > > > > > looks like a vote or discuss thread.
> > > > > >
> > > > > > Thanks,
> > > > > > -Alex
> > > > > >
> > > > > > On 2/10/19, 8:44 PM, "Alex Harui"
> > > > <ah...@adobe.com.INVALID>
> > > > > wrote:
> > > > > >
> > > > > > Om,
> > > > > >
> > > > > > Well, that's what I used for the
> last
> > > > release. I'm sure
> > > > > there is
> > > > > > probably some inaccuracy in it.
> > > > > >
> > > > > > That said, I'm abandoning that
> document
> > > and
> > > > taking a new
> > > > > angle
> > > > > > because that document presumed that the
> release
> > > > manager was
> > > > > trying to
> > > > > > create a release on his/her computer.
> I've
> > > given up
> > > > on that and
> > > > > working on
> > > > > > making releases from a shared computer
> for the
> > > reasons
> > > > I've
> > > > > stated
> > > > > > upthread. I hope to make some progress
> on that
> > > this
> > > > week.
> > > > > >
> > > > > > The key difference is that the
> new
> > angle
> > > does
> > > > not
> > > > > presume that you
> > > > > > have Git SSH and PGP signatures all set
> up on
> > > some
> > > > computer. I
> > > > > have not
> > > > > > looked into how Docker would handle
> that. You
> > > > certainly
> > > > > wouldn't want the
> > > > > > Docker image to contain your SSH or PGP
> > > keys/creds.
> > > > And if the
> > > > > Docker
> > > > > > image doesn't, then that is another
> stumbling
> > > block
> > > > for future
> > > > > RMs.
> > > > > >
> > > > > > The other key difference is that
> the
> > old
> > > > script presumed
> > > > > you could
> > > > > > create the 3 release in 3 huge "easy"
> steps.
> > > We've
> > > > seen that is
> > > > > only true
> > > > > > for me. So the new angle creates many
> discrete
> > > steps
> > > > managed by
> > > > > Jenkins.
> > > > > >
> > > > > > So, it is up to you to decide
> what you
> > > want to
> > > > > "Docker-ize". You
> > > > > > can try to Docker-ize the current 3 big
> steps,
> > > so RMs
> > > > can try to
> > > > > run it on
> > > > > > their systems, but I'd bet they will
> just faiI
> > > due to
> > > > network
> > > > > issues. I
> > > > > > would be interested in using Docker to
> make
> > each
> > > of
> > > > these many
> > > > > discrete
> > > > > > steps portable to another server. I'm
> not
> > > going to
> > > > involve
> > > > > Docker at this
> > > > > > point. My main goal is just to see if I
> can
> > > create a
> > > > workflow
> > > > > of many
> > > > > > discrete steps that isn't horribly
> painful.
> > > Once we
> > > > see what
> > > > > these steps
> > > > > > turn out to be, then we can worry about
> server
> > > > portability of
> > > > > those steps.
> > > > > >
> > > > > > Either way, we want to know about
> > running
> > > > > Browser+Selenium for
> > > > > > sure. And maybe FlashPlayerDebugger or
> AIR. I
> > > would
> > > > want to
> > > > > know, for
> > > > > > example, how you debug a failing
> checkintest
> > in a
> > > > Docker
> > > > > container.
> > > > > >
> > > > > > Thanks,
> > > > > > -Alex
> > > > > >
> > > > > >
> > > > > > On 2/10/19, 5:18 PM, "OmPrakash
> > > Muppirala" <
> > > > > bigosmallm@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > Alex,
> > > > > >
> > > > > > Just to be clear, I am
> following
> > the
> > > steps
> > > > from here
> > > > > to try
> > > > > > and setup a
> > > > > > docker container.
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=%2F9mdYnvJTSx1BVR6I0FyoH%2BbKSbiCET7hCoO1y%2FvgrQ%3D&reserved=0
> > > > > >
> > > > > > Is this doc up to date?
> > > > > >
> > > > > > Thanks,
> > > > > > Om
> > > > > >
> > > > > > On Wed, Feb 6, 2019 at 12:02
> PM
> > > OmPrakash
> > > > Muppirala <
> > > > > > bigosmallm@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > One approach is to have
> each step
> > > in the
> > > > process
> > > > > spin up a
> > > > > > docker image.
> > > > > > > And use docker-compose to
> run
> > each
> > > > step. All the
> > > > > images can
> > > > > > be made to
> > > > > > > share a common volume
> where all
> > the
> > > > artifacts are
> > > > > stored
> > > > > > across steps.
> > > > > > >
> > > > > > > You are right about the
> > networking
> > > issue
> > > > though.
> > > > > Any
> > > > > > network related
> > > > > > > failure that occurs on the
> host
> > > machine
> > > > will most
> > > > > likely
> > > > > > occur in the
> > > > > > > docker container.
> Although, I am
> > > not
> > > > clear how we
> > > > > can
> > > > > > guarantee that the
> > > > > > > same issues will not occur
> on the
> > > > Jenkins server.
> > > > > I mean,
> > > > > > what is special
> > > > > > > about the Jenkins server
> that
> > > makes it
> > > > immune to
> > > > > these
> > > > > > networking issues?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Om
> > > > > > >
> > > > > > > On Wed, Feb 6, 2019 at
> 11:48 AM
> > > Alex
> > > > Harui
> > > > > > <ah...@adobe.com.invalid>
> > > > > > > wrote:
> > > > > > >
> > > > > > >> Again, I don't know
> anything
> > about
> > > > Docker, but
> > > > > before we
> > > > > > spend a lot of
> > > > > > >> time on Docker, I also
> want to
> > > point
> > > > out that the
> > > > > process
> > > > > > to create a
> > > > > > >> release cannot really be
> thought
> > > of as
> > > > "one
> > > > > application".
> > > > > > It will be a
> > > > > > >> series of "steps" to
> run. How
> > > many
> > > > steps
> > > > > depends on
> > > > > > whether we think we
> > > > > > >> can isolate enough stuff
> via
> > > Docker to
> > > > be able to
> > > > > run
> > > > > > Docker on the RM's
> > > > > > >> computer instead of some
> shared
> > > > computer. On a
> > > > > shared
> > > > > > computer there will
> > > > > > >> be dozens of steps
> because the
> > RM
> > > will
> > > > need to
> > > > > enter
> > > > > > passwords to commit
> > > > > > >> stuff. On a local
> computer I
> > > guess the
> > > > RM can
> > > > > supply
> > > > > > passwords but I think
> > > > > > >> there will be stopping
> points
> > > where the
> > > > Maven
> > > > > artifacts are
> > > > > > deployed and
> > > > > > >> the staging repo is
> closed, and
> > > another
> > > > stopping
> > > > > point for
> > > > > > the vote. It
> > > > > > >> seems like Docker works by
> > > downloading
> > > > > dependencies. Given
> > > > > > that the
> > > > > > >> problem the RMs had last
> time
> > > involved
> > > > downloads
> > > > > and
> > > > > > uploads, why do we
> > > > > > >> think Docker will really
> solve
> > > this for
> > > > creating
> > > > > releases
> > > > > > on local machines?
> > > > > > >>
> > > > > > >> The reason to do this on a
> > shared
> > > > machine is so
> > > > > that new
> > > > > > RMs don't have
> > > > > > >> to do as much setup. But
> then I
> > > wonder
> > > > about the
> > > > > > efficiency of kicking off
> > > > > > >> that many Docker images.
> > Jenkins
> > > can
> > > > manage that
> > > > > already.
> > > > > > Does Docker
> > > > > > >> have some sort of similar
> > > Dashboard or
> > > > would we
> > > > > use Jenkins
> > > > > > to kick off
> > > > > > >> Docker steps? I can't
> quite
> > > picture
> > > > what is the
> > > > > outermost
> > > > > > >> control/dashboard.
> > > > > > >>
> > > > > > >> -Alex
> > > > > > >>
> > > > > > >> On 2/6/19, 11:03 AM,
> "Harbs" <
> > > > > harbs.lists@gmail.com> wrote:
> > > > > > >>
> > > > > > >> A quick search turns
> up
> > this:
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=L%2FSQRtItveWwGWXpiz5ImQHJ%2BD0kyqIWy9%2BN8KFpfGg%3D&reserved=0
> > > > > > >> <
> > > > > > >>
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=L%2FSQRtItveWwGWXpiz5ImQHJ%2BD0kyqIWy9%2BN8KFpfGg%3D&reserved=0
> > > > > > >> >
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GgxPOsJMU7xnieSkFk%2FF5Ntp75tvg4y8VVOJitIEEYI%3D&reserved=0
> > > > > > >> <
> > > > > > >>
> > > > > >
> > > > >
> > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GgxPOsJMU7xnieSkFk%2FF5Ntp75tvg4y8VVOJitIEEYI%3D&reserved=0
> > > > > > >> >
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=oAwxtBcYuuB73255nFD40k2NqnLKIJWo92htZkychLc%3D&reserved=0
> > > > > > >> <
> > > > > > >>
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=oAwxtBcYuuB73255nFD40k2NqnLKIJWo92htZkychLc%3D&reserved=0
> > > > > > >> >
> > > > > > >>
> > > > > > >> > On Feb 6, 2019, at
> 8:59
> > PM,
> > > Alex
> > > > Harui
> > > > > > <ah...@adobe.com.INVALID>
> > > > > > >> wrote:
> > > > > > >> >
> > > > > > >> > Thanks for
> volunteering to
> > > try it
> > > > Om. IMO,
> > > > > even more
> > > > > > important
> > > > > > >> than Firefox+Flash is
> > > > SomeBrowser+Selenium. We
> > > > > may also
> > > > > > need to run Adobe
> > > > > > >> AIR's adb. We could
> probably
> > > turn off
> > > > the Flash
> > > > > tests or
> > > > > > replace Flash
> > > > > > >> with AIR.
> > > > > > >> >
> > > > > > >> > Thanks,
> > > > > > >> > -Alex
> > > > > > >> >
> > > > > > >> > On 2/6/19, 10:54 AM,
> > "Carlos
> > > > Rovira" <
> > > > > > carlosrovira@apache.org>
> > > > > > >> wrote:
> > > > > > >> >
> > > > > > >> > Hi Om, that
> would be
> > > great!
> > > > waiting for
> > > > > your
> > > > > > experience with a
> > > > > > >> that! :)
> > > > > > >> >
> > > > > > >> > El mié., 6 feb.
> 2019 a
> > > las
> > > > 19:31,
> > > > > OmPrakash
> > > > > > Muppirala (<
> > > > > > >> bigosmallm@gmail.com>)
> > > > > > >> > escribió:
> > > > > > >> >
> > > > > > >> >> Yes, I agree with
> Alex
> > > about not
> > > > being
> > > > > able to run
> > > > > > UI out of docker
> > > > > > >> >> containers. I
> never
> > > thought of
> > > > the
> > > > > checkintests
> > > > > > when I made the
> > > > > > >> >> suggestion.
> > > > > > >> >>
> > > > > > >> >> The firefox-flash
> image
> > > that
> > > > Yishay
> > > > > pointed out
> > > > > > looks promising.
> > > > > > >> I will
> > > > > > >> >> poke around with
> it and
> > > see if
> > > > that works
> > > > > for us.
> > > > > > >> >>
> > > > > > >> >> Thanks,
> > > > > > >> >> Om
> > > > > > >> >>
> > > > > > >> >> On Wed, Feb 6,
> 2019 at
> > > 12:41 AM
> > > > Yishay
> > > > > Weiss <
> > > > > > >> yishayjobs@hotmail.com>
> > > > > > >> >> wrote:
> > > > > > >> >>
> > > > > > >> >>> I’ll let Om or
> someone
> > > else
> > > > with docker
> > > > > experience
> > > > > > tell us if
> > > > > > >> this [1] is
> > > > > > >> >>> relevant.
> > > > > > >> >>>
> > > > > > >> >>>
> > > > > > >> >>>
> > > > > > >> >>> [1]
> > > > > > >>
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=oE4%2F%2FqGiaVmCU3VShIMUbUMJc%2BiwF%2F07dkEgYhcgQJA%3D&reserved=0
> > > > > > >> >>>
> > > > > > >> >>>
> > > > > > >> >>>
> > > > > > >> >>>
> > > ________________________________
> > > > > > >> >>> From: Alex Harui
> > > > <aharui@adobe.com.INVALID
> > > > > >
> > > > > > >> >>> Sent: Wednesday,
> > February
> > > 6,
> > > > 2019
> > > > > 10:05:54 AM
> > > > > > >> >>> To:
> > dev@royale.apache.org
> > > > > > >> >>> Subject: Re: 0.9.6
> > Release
> > > > > > >> >>>
> > > > > > >> >>> I don't anything
> about
> > > docker,
> > > > but in 15
> > > > > minutes of
> > > > > > reading I ran
> > > > > > >> into
> > > > > > >> >>> this:
> > > > > > >> >>>
> > > > > > >> >>>
> > > > > > >> >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=iyP6ZrHSV24Ykd5zjCPwrQYD%2F378Ek9pHNj4n2mTIp8%3D&reserved=0
> > > > > > >> >>>
> > > > > > >> >>> Which says:
> Docker can't
> > > " Run
> > > > > applications with
> > > > > > graphical
> > > > > > >> interfaces".
> > > > > > >> >>> If you want
> Royale to
> > use
> > > > Docker for
> > > > > releases, show
> > > > > > that it can
> > > > > > >> run
> > > > > > >> >>> checkintests with
> Flash
> > > and the
> > > > Browser.
> > > > > Then I
> > > > > > will look into
> > > > > > >> it more.
> > > > > > >> >>>
> > > > > > >> >>> The highest level
> goal
> > is
> > > to
> > > > make it as
> > > > > easy as
> > > > > > possible for
> > > > > > >> someone to
> > > > > > >> >>> volunteer to be
> an RM.
> > > Any
> > > > requirement
> > > > > of "install
> > > > > > this (Docker,
> > > > > > >> etc) on
> > > > > > >> >>> your computer"
> is, IMO,
> > > another
> > > > barrier
> > > > > to entry.
> > > > > > Yeah, RMs will
> > > > > > >> have to
> > > > > > >> >>> have Maven
> installed and
> > > maybe
> > > > Ant, but
> > > > > you should
> > > > > > already have
> > > > > > >> those
> > > > > > >> >>> installed to be a
> > > committer/PMC
> > > > member.
> > > > > > >> >>>
> > > > > > >> >>> That said, a good
> > > takeaway from
> > > > the
> > > > > Docker idea is
> > > > > > to try to find
> > > > > > >> a way
> > > > > > >> >> to
> > > > > > >> >>> make an "Image" of
> > > whatever we
> > > > end up
> > > > > with on
> > > > > > whatever server we
> > > > > > >> end up
> > > > > > >> >>> using so if the
> image
> > can
> > > be
> > > > copied and
> > > > > used on
> > > > > > other servers.
> > > > > > >> I'm not
> > > > > > >> >>> exactly sure how
> to do
> > > that
> > > > with Azure,
> > > > > which hosts
> > > > > > my CI
> > > > > > >> server. I will
> > > > > > >> >>> spend a few more
> minutes
> > > > researching that.
> > > > > > >> >>>
> > > > > > >> >>> I could not
> quickly find
> > > any
> > > > way to get a
> > > > > free VM
> > > > > > on Azure or AWS
> > > > > > >> that
> > > > > > >> >>> isn't a
> > > > > free-trial-start-paying-after-a-year. So,
> > > > > > unless someone
> > > > > > >> comes
> > > > > > >> >> up
> > > > > > >> >>> with a free
> server we
> > can
> > > use
> > > > "forever",
> > > > > I'm going
> > > > > > to just start
> > > > > > >> with my
> > > > > > >> >>> Azure VM.
> > > > > > >> >>>
> > > > > > >> >>> -Alex
> > > > > > >> >>>
> > > > > > >> >>> On 2/5/19, 10:59
> PM,
> > > "Carlos
> > > > Rovira" <
> > > > > > carlosrovira@apache.org>
> > > > > > >> wrote:
> > > > > > >> >>>
> > > > > > >> >>> Hi.
> > > > > > >> >>>
> > > > > > >> >>> the plan
> sounds very
> > > good to
> > > > me. Just
> > > > > my 2
> > > > > > thoughts on this:
> > > > > > >> >>>
> > > > > > >> >>> 1.- As I was
> reading
> > I
> > > was
> > > > thinking as
> > > > > well on
> > > > > > something like
> > > > > > >> Docker
> > > > > > >> >>> and
> > > > > > >> >>> see Om as well
> > > thinking on
> > > > the same.
> > > > > Maybe is
> > > > > > the way to this
> > > > > > >> with
> > > > > > >> >> the
> > > > > > >> >>> actual
> technology.
> > > Seems VMs
> > > > are
> > > > > stepping out a
> > > > > > bit this days
> > > > > > >> in
> > > > > > >> >> favor
> > > > > > >> >>> of
> > > > > > >> >>> things like
> Docker.
> > > Maybe
> > > > the same did
> > > > > Git over
> > > > > > Svn, and today
> > > > > > >> Svn is
> > > > > > >> >>> an
> > > > > > >> >>> old
> remembrance. I
> > > must say
> > > > that I
> > > > > have no
> > > > > > experience with
> > > > > > >> Docker, so
> > > > > > >> >>> doing
> > > > > > >> >>> that will
> require
> > > acquire
> > > > that
> > > > > knowledge, but
> > > > > > seems it could
> > > > > > >> be worth
> > > > > > >> >>> it.
> > > > > > >> >>>
> > > > > > >> >>> 2.- Maybe is
> not
> > > possible,
> > > > but I want
> > > > > to propose
> > > > > > to do this
> > > > > > >> work I a
> > > > > > >> >>> separate
> branch, so
> > it
> > > could
> > > > be in
> > > > > parallel to
> > > > > > other
> > > > > > >> developments. I
> > > > > > >> >>> think
> > > > > > >> >>> work over
> develop is
> > > > practical if
> > > > > there's
> > > > > > something tiny that
> > > > > > >> could
> > > > > > >> >> be
> > > > > > >> >>> done
> > > > > > >> >>> in a commit.
> But as
> > we
> > > need
> > > > more than
> > > > > one, or is
> > > > > > a long
> > > > > > >> process (like
> > > > > > >> >>> this), chances
> are to
> > > make
> > > > develop
> > > > > branch
> > > > > > unstable and even
> > > > > > >> for some
> > > > > > >> >>> days.
> > > > > > >> >>> I think we
> should try
> > > to
> > > > avoid that
> > > > > scenario,
> > > > > > and branches are
> > > > > > >> the
> > > > > > >> >> best
> > > > > > >> >>> way. If we do
> this
> > way,
> > > > we'll benefit
> > > > > of more
> > > > > > reliable develop
> > > > > > >> >> branch.
> > > > > > >> >>>
> > > > > > >> >>> Thanks and
> good to
> > > know of
> > > > this plan :)
> > > > > > >> >>>
> > > > > > >> >>> Carlos
> > > > > > >> >>>
> > > > > > >> >>>
> > > > > > >> >>> El mar., 5
> feb. 2019
> > a
> > > las
> > > > 23:19,
> > > > > Harbs (<
> > > > > > >> harbs.lists@gmail.com>)
> > > > > > >> >>> escribió:
> > > > > > >> >>>
> > > > > > >> >>>> I’ve never used
> Docker
> > > myself,
> > > > but that
> > > > > might be a
> > > > > > good plan.
> > > > > > >> >>>>
> > > > > > >> >>>>> On Feb 6, 2019,
> at
> > > 12:07 AM,
> > > > OmPrakash
> > > > > Muppirala <
> > > > > > >> >>>
> bigosmallm@gmail.com>
> > > > > > >> >>>> wrote:
> > > > > > >> >>>>>
> > > > > > >> >>>>> I was wondering
> if we
> > > can use
> > > > docker
> > > > > images to
> > > > > > setup and seal
> > > > > > >> the
> > > > > > >> >>> RM
> > > > > > >> >>>>> environment.
> Then
> > > other RMs
> > > > simply
> > > > > need to run
> > > > > > the image
> > > > > > >> locally
> > > > > > >> >>> and run
> > > > > > >> >>>>> the release
> scripts.
> > > Might
> > > > be easier.
> > > > > If folks
> > > > > > like this plan,
> > > > > > >> >> I
> > > > > > >> >>> can
> > > > > > >> >>>> try
> > > > > > >> >>>>> to put something
> > > together.
> > > > > > >> >>>>>
> > > > > > >> >>>>> Thanks,
> > > > > > >> >>>>> Om
> > > > > > >> >>>>>
> > > > > > >> >>>>> On Tue, Feb 5,
> 2019 at
> > > 1:40
> > > > PM Harbs <
> > > > > > harbs.lists@gmail.com>
> > > > > > >> >>> wrote:
> > > > > > >> >>>>>
> > > > > > >> >>>>>> In a recent
> > > discussion, it
> > > > looks like
> > > > > other
> > > > > > projects have
> > > > > > >> gotten
> > > > > > >> >>>> resources
> > > > > > >> >>>>>> from AWS.
> > > > > > >> >>>>>>
> > > > > > >> >>>>>> Whatever
> service we
> > > use,
> > > > could setup a
> > > > > “shared”
> > > > > > Royale account
> > > > > > >> >>> that all
> > > > > > >> >>>>>> PMC members
> could
> > have
> > > > access to.
> > > > > > >> >>>>>>
> > > > > > >> >>>>>> I don’t know if
> > > there’s some
> > > > way we
> > > > > could
> > > > > > leverage Gitlab’s
> > > > > > >> >>> integration
> > > > > > >> >>>>>> pipelines
> > > > > > >> >>>
> > > > > > >> >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GSexC31IRXLohkmy%2F1kx1PrVgcu0Ixu1%2BtQNMaCOUr4%3D&reserved=0
> > > > > > >> >>> <
> > > > > > >> >>>>>>
> > > > > > >> >>>
> > > > > > >> >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GSexC31IRXLohkmy%2F1kx1PrVgcu0Ixu1%2BtQNMaCOUr4%3D&reserved=0
> > > > > > >> >>>>
> > > > > > >> >>>>>>
> > > > > > >> >>>>>>> On Feb 5,
> 2019, at
> > > 11:33
> > > > PM, Alex
> > > > > Harui
> > > > > > >> >>
> <aharui@adobe.com.INVALID
> > > > > > >> >>>>
> > > > > > >> >>>>>> wrote:
> > > > > > >> >>>>>>>
> > > > > > >> >>>>>>> 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" <
> > > > > > >> >>
> > piotrzarzycki21@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.lists@gmail.com
> > > > > > >> >>> wrote:
> > > > > > >> >>>>>>>
> > > > > > >> >>>>>>>> A big +1
> from me!
> > > > > > >> >>>>>>>>
> > > > > > >> >>>>>>>> Looking
> forward!
> > > > > > >> >>>>>>>>
> > > > > > >> >>>>>>>>> On Feb 5,
> 2019, at
> > > 9:34
> > > > PM, Alex
> > > > > Harui
> > > > > > >> >>>
> > <aharui@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
> > > > > >
> > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542823006545&sdata=IqYeRFQyKmIse1xD5qA8MUPMadljfjLBbzYayWw6AtQ%3D&reserved=0
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542823006545&sdata=5VexoocnThIqHb1XE5tl%2BFl6awXBdtxBIPVrXX9r5LI%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542823006545&sdata=5VexoocnThIqHb1XE5tl%2BFl6awXBdtxBIPVrXX9r5LI%3D&reserved=0
> >*
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: 0.9.6 Release
Posted by Piotr Zarzycki <pi...@gmail.com>.
Great! Let me study this tomorrow and see how far I can go.
Thank you!
niedz., 23 cze 2019 o 18:22 Alex Harui <ah...@adobe.com.invalid>
napisał(a):
> Hi Piotr,
>
> I'm sure it doesn't contain everything. That's part of this exercise: to
> see what else needs to be modified in that wiki page or in the scripts and
> Jenkins jobs so it works for you as well as me and thus, hopefully others.
>
> Thanks for trying it out,
> -Alex
>
> On 6/23/19, 6:54 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> Hi Alex,
>
> Instruction here [1] contains everything what I need to know in order
> to
> make RC1 ? I'm going to start trying tomorrow my time.
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736458102&sdata=j8LpE1uMhgEvjsA5CviAGVhve9VZHuZmZGcBt0fQ0JY%3D&reserved=0
>
> Thanks,
> Piotr
>
> wt., 18 cze 2019 o 07:51 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Hi Alex,
> >
> > Thank you! I will be working in release next week, so if anyone have
> > anything to add there is some time.
> >
> > Thanks,
> > Piotr
> >
> > On Tue, Jun 18, 2019, 7:28 AM Alex Harui <ah...@adobe.com.invalid>
> wrote:
> >
> >> Mx tests are working locally for me with this last change to
> >> ListItemRenderer.
> >>
> >> So, the question for everyone is: is there anything else we want
> to put
> >> in before trying to cut a release?
> >>
> >> We might need to change the ASDoc app after Greg's last change. We
> might
> >> want to bang on ASDoc for a bit and see if anything major needs
> fixing
> >> before cutting a release.
> >>
> >> The only other thing I thought of was trying to upgrade Selenium so
> we
> >> can use a recent FireFox version. Right now we are stuck way back
> on FF47,
> >> but I've also heard that more recent FF versions are less friendly
> to
> >> Flash, so you have to use some other browser to test Flash. That's
> ok for
> >> building the Royale SDK since the Flash tests are run in
> >> FlashPlayerDebugger and the JS tests are run in a browser like FF.
> >>
> >> I'm tempted to say we should punt the inject_html in modules
> problem to
> >> the next release.
> >>
> >> I will be adding more details to
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736458102&sdata=j8LpE1uMhgEvjsA5CviAGVhve9VZHuZmZGcBt0fQ0JY%3D&reserved=0
> >> But there should be enough there to get an RC out for vote.
> >>
> >> Thanks,
> >> -Alex
> >>
> >> On 6/17/19, 11:06 AM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> >>
> >> I just saw ASDoc work well enough for me to start with
> >> mx.binding.BindabilityInfo and switch to mx.charts.AxisRenderer.
> >>
> >> There might be JSON parsing issues with other classes. Run the
> >> bin/js-debug version, check the console if things don't load and
> see what
> >> file failed to load and why.
> >>
> >> I will take a look at MXTests next.
> >>
> >> -Alex
> >>
> >> On 6/17/19, 8:08 AM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> >>
> >> ASDoc is not fully working for me. I've been working on
> that the
> >> past several days. It took quite a while to fix the JSON output
> from new
> >> and interesting ASDoc patterns. I'm now looking into failures due
> to
> >> changes in coercion rules in the JS output. ASDoc was trying to
> save time
> >> by using plain objects that were isomorphic to a class instead of
> actual
> >> class instances.
> >>
> >> MXTests are failing on the CI server and probably locally
> but I
> >> haven't gotten that far.
> >>
> >> I would think we want these things to work, but you are the
> RM so
> >> it is up to you. Volunteers are welcome to help with these and
> other tasks.
> >>
> >> -Alex
> >>
> >> On 6/17/19, 12:44 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com>
> >> wrote:
> >>
> >> Hi Alex,
> >>
> >> I don't see any answer here - can I start with trying
> your
> >> instruction and
> >> start release ?
> >>
> >> Thanks,
> >> Piotr
> >>
> >> śr., 12 cze 2019 o 10:12 Carlos Rovira <
> >> carlosrovira@apache.org> napisał(a):
> >>
> >> > Hi Alex,
> >> > just build from scratch right now and seems maven and
> ant
> >> was ok
> >> >
> >> > El mié., 12 jun. 2019 a las 10:02, Alex Harui
> >> (<ah...@adobe.com.invalid>)
> >> > escribió:
> >> >
> >> > > The merge is complete, and the main builds seem to
> be
> >> successful, except
> >> > > for Maven on royale-asjs which was failing before
> the
> >> merge.
> >> > >
> >> > > I'm still catching up on other things, but I think
> there
> >> are some bugs we
> >> > > need to fix before cutting the release? I think
> ASDoc
> >> may not be fully
> >> > > working? What else?
> >> > >
> >> > > -Alex
> >> > >
> >> > > On 6/10/19, 11:05 AM, "Piotr Zarzycki" <
> >> piotrzarzycki21@gmail.com>
> >> > wrote:
> >> > >
> >> > > Hi Alex,
> >> > >
> >> > > Many thanks for that! I will try to be RM. I
> will
> >> have some dedicated
> >> > > time
> >> > > for that. I will wait for your instruction and
> merge
> >> to develop.
> >> > >
> >> > > Thanks,
> >> > > Piotr
> >> > >
> >> > >
> >> > > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
> >> <ah...@adobe.com.invalid>
> >> > > wrote:
> >> > >
> >> > > > Well, that turned out to be much more
> >> time-consuming than I
> >> > > expected, but
> >> > > > we can now create identical release artifacts
> on
> >> Mac and Win. I am
> >> > > hopeful
> >> > > > this effort will pay off not only now in
> having
> >> other folks
> >> > generate
> >> > > > releases, but also in the future if signed
> binaries
> >> become a
> >> > > requirement.
> >> > > >
> >> > > > There continues to be a lot of distractions
> in my
> >> life that can
> >> > cause
> >> > > > delays, but I hope to merge the
> release_practice
> >> branches into
> >> > > develop over
> >> > > > the next day or two and figure out where in
> the
> >> wiki to document
> >> > the
> >> > > > release process. So, now is the time for one
> or
> >> more people to
> >> > step
> >> > > up to
> >> > > > be the RMs for 0.9.6 and help debug and
> improve the
> >> process.
> >> > > >
> >> > > > I am going to try very hard not to "own" the
> >> process. If something
> >> > > goes
> >> > > > wrong, I am going to ask others to try to
> debug and
> >> fix it first
> >> > > because it
> >> > > > is in the project's best interests for others
> to
> >> truly understand
> >> > > how this
> >> > > > stuff works.
> >> > > >
> >> > > > Thanks,
> >> > > > -Alex
> >> > > >
> >> > > > On 5/23/19, 9:54 AM, "Alex Harui"
> >> <ah...@adobe.com.INVALID>
> >> > wrote:
> >> > > >
> >> > > > It has turned out to be harder than
> expected to
> >> get the same
> >> > > binaries
> >> > > > on Mac and Win. I now have the identical
> binaries
> >> for
> >> > > royale-compiler and
> >> > > > royale-typedefs Maven artifacts and am
> starting on
> >> royale-asjs. I
> >> > > might
> >> > > > get lucky and the changes that fixed
> >> royale-typedefs SWCs will
> >> > > magically
> >> > > > get the royale-asjs SWCs to match. Then we
> have to
> >> make the Ant
> >> > > artifacts
> >> > > > match.
> >> > > >
> >> > > > There have been a lot of distractions in
> my
> >> non-work life which
> >> > > has
> >> > > > also impeded progress. I hope to make much
> >> progress this coming
> >> > > week and
> >> > > > if we're lucky, I will be asking for a
> volunteer
> >> (or volunteers) to
> >> > > test
> >> > > > drive all of this stuff and be the RM for
> 0.9.6. I
> >> am not going to
> >> > > be the
> >> > > > RM.
> >> > > >
> >> > > > -Alex
> >> > > >
> >> > > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> >> > piotrzarzycki21@gmail.com
> >> > > >
> >> > > > wrote:
> >> > > >
> >> > > > Hi Alex,
> >> > > >
> >> > > > It's been a while since you have
> started
> >> effort with
> >> > > automating
> >> > > > build.
> >> > > > Where are you with that ? Are we
> closer to
> >> started 0.9.6.
> >> > Do
> >> > > you
> >> > > > need any
> >> > > > help with this ?
> >> > > >
> >> > > > Thanks,
> >> > > > Piotr
> >> > > >
> >> > > > wt., 2 kwi 2019 o 19:30 Alex Harui
> >> > <aharui@adobe.com.invalid
> >> > > >
> >> > > > napisał(a):
> >> > > >
> >> > > > > Update:
> >> > > > >
> >> > > > > In order to make verification of
> binary
> >> release packages
> >> > > created
> >> > > > on the
> >> > > > > server easier, I have made changes
> to our
> >> build scripts
> >> > and
> >> > > > tools to try to
> >> > > > > generate reproducible binaries.
> I've
> >> seen two different
> >> > > builds
> >> > > > compare on
> >> > > > > my Mac. The next challenge will
> be to
> >> see if the server
> >> > > can
> >> > > > build a
> >> > > > > package on Windows that will
> compare on
> >> Mac.
> >> > > > >
> >> > > > > One of the changes I needed to make
> is to
> >> JBurg. The
> >> > > version of
> >> > > > JBurg we
> >> > > > > use generates method names
> including a
> >> hash that doesn't
> >> > > > reproduce the same
> >> > > > > name each time. I have changes to
> JBurg
> >> ready, however
> >> > > JBurg is
> >> > > > currently
> >> > > > > under CPL which is category B. We
> only
> >> need one file, we
> >> > > don't
> >> > > > need or
> >> > > > > want all of JBurg at this time.
> The one
> >> JBurg file is
> >> > > jointly
> >> > > > owned by
> >> > > > > Adobe and Tom Harwood. I've
> contact Tom
> >> and he will be
> >> > > filing
> >> > > > an ICLA and
> >> > > > > has given me permission to commit
> the
> >> lines he owns in
> >> > > that one
> >> > > > file.
> >> > > > >
> >> > > > > This is the revision of the file
> that
> >> will be donated by
> >> > > > Tom/Adobe.
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736458102&sdata=qgLFtK8dC1zMxpPmqqyYCybCIV2EWlT4UUeWypNw%2FnY%3D&reserved=0
> >> > > > >
> >> > > > > Once this file goes in with the
> changes
> >> to keep the
> >> > method
> >> > > names
> >> > > > the same,
> >> > > > > there will be more tweaks to the
> release
> >> tasks and then
> >> > we
> >> > > can
> >> > > > try cutting
> >> > > > > a release. I'm thinking we'll be
> at that
> >> point in early
> >> > > May, so
> >> > > > now is the
> >> > > > > time to get stuff in for the 0.9.6
> >> release.
> >> > > > >
> >> > > > > Thanks,
> >> > > > > -Alex
> >> > > > >
> >> > > > > On 3/8/19, 9:27 AM, "Alex Harui" <
> >> aharui@adobe.com>
> >> > wrote:
> >> > > > >
> >> > > > > I would much rather have others
> find
> >> and fix issues
> >> > > > themselves. That
> >> > > > > way, more people than just me will
> know
> >> how to maintain
> >> > the
> >> > > > system. It
> >> > > > > actually turns out that, IMO, a
> group of
> >> people can work
> >> > > on the
> >> > > > release.
> >> > > > > There are 14 steps. Literally, 14
> >> different people could
> >> > > > execute one step
> >> > > > > each.
> >> > > > >
> >> > > > > My 2 cents,
> >> > > > > -Alex
> >> > > > >
> >> > > > > On 3/8/19, 2:13 AM, "Carlos
> Rovira" <
> >> > > carlosrovira@apache.org>
> >> > > > wrote:
> >> > > > >
> >> > > > > Hi Alex,
> >> > > > >
> >> > > > > amazing work! congrats to
> reach
> >> to this point! :)
> >> > > > >
> >> > > > > I need to put my head on
> all of
> >> this, but count
> >> > on
> >> > > me to
> >> > > > be a RM.
> >> > > > > I think
> >> > > > > the best thing should be
> that you
> >> be the first RM
> >> > > to try
> >> > > > your own
> >> > > > > development at least for the
> >> first time, and then
> >> > > the
> >> > > > rest of us
> >> > > > > will
> >> > > > > follow you on the next
> releases.
> >> With all this on
> >> > > place
> >> > > > we maybe
> >> > > > > could
> >> > > > > release once a month or
> every two
> >> months...
> >> > > > >
> >> > > > > Thanks for doing this :)
> >> > > > >
> >> > > > > Carlos
> >> > > > >
> >> > > > >
> >> > > > > El vie., 8 mar. 2019 a las
> 1:55,
> >> Alex Harui
> >> > > > > (<ah...@adobe.com.invalid>)
> >> > > > > escribió:
> >> > > > >
> >> > > > > > OK, I've now seen Jenkins
> >> perform the steps to
> >> > > build
> >> > > > the release
> >> > > > > > artifacts. Folks
> interested in
> >> Docker-izing
> >> > the
> >> > > steps
> >> > > > are
> >> > > > > welcome to look
> >> > > > > > at the jobs on the "Royale
> >> Release" tab on the
> >> > CI
> >> > > > server.
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736458102&sdata=YjKx%2B8dlWH%2B0u72mZCfvDQ9T5nZfmeS2tzW17xBQO%2FU%3D&reserved=0
> >> > > > > >
> >> > > > > > These steps assume that
> the RM
> >> can run the
> >> > basic
> >> > > Maven
> >> > > > and Ant
> >> > > > > build on
> >> > > > > > the RM's computer. I think
> >> that's a fair
> >> > > requirement
> >> > > > since all
> >> > > > > of us on the
> >> > > > > > PMC need to able to do
> that to
> >> build the RC in
> >> > > order
> >> > > > to vote on
> >> > > > > it.
> >> > > > > > Jenkins does other tasks
> like
> >> run the Maven
> >> > > release
> >> > > > plugin
> >> > > > > steps.
> >> > > > > >
> >> > > > > > Currently that results in
> >> binaries on Jenkins
> >> > > that are
> >> > > > > downloaded to the
> >> > > > > > RM's computer. These
> binaries
> >> need to be
> >> > > verified by
> >> > > > the RM
> >> > > > > which is the
> >> > > > > > next phase I will be
> starting
> >> on now. The RM
> >> > > verifies
> >> > > > the bits
> >> > > > > and then
> >> > > > > > PGP signs them. And then
> the
> >> bits are uploaded
> >> > > off
> >> > > > the RM's
> >> > > > > computer to
> >> > > > > > Maven Staging or
> dist.a.o/dev.
> >> If that
> >> > > uploading
> >> > > > turns out to
> >> > > > > be a point
> >> > > > > > of failure, we have the
> option
> >> of having
> >> > Jenkins
> >> > > > upload the big
> >> > > > > files and
> >> > > > > > have the RM only upload
> PGP
> >> signature files.
> >> > Or
> >> > > > finding a way
> >> > > > > for Jenkins
> >> > > > > > to get the signature
> files from
> >> the RM. The
> >> > > uploads
> >> > > > worked fine
> >> > > > > for me,
> >> > > > > > but then again, so did
> the old
> >> script's
> >> > uploads.
> >> > > > > >
> >> > > > > > Therefore, once I get the
> >> binary verification
> >> > > phase
> >> > > > completed, I
> >> > > > > think
> >> > > > > > someone other than me
> should be
> >> the RM and try
> >> > > to use
> >> > > > these
> >> > > > > steps to
> >> > > > > > generate the release and
> help
> >> debug the process
> >> > > for
> >> > > > the next
> >> > > > > RM. So,
> >> > > > > > please try to carve out
> some
> >> time to be the RM.
> >> > > One
> >> > > > advantage
> >> > > > > of doing
> >> > > > > > most of the work on
> Jenkins is
> >> that it frees up
> >> > > my
> >> > > > computer to
> >> > > > > do other
> >> > > > > > things while Jenkins is
> >> cranking away.
> >> > > > > >
> >> > > > > > I think we're at least a
> week
> >> away from binary
> >> > > > verification,
> >> > > > > maybe two, so
> >> > > > > > it is time to start
> thinking
> >> about what is
> >> > going
> >> > > in
> >> > > > this release.
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > -Alex
> >> > > > > >
> >> > > > > > On 3/7/19, 4:15 PM, "Alex
> Harui"
> >> > > > <ah...@adobe.com.INVALID>
> >> > > > > wrote:
> >> > > > > >
> >> > > > > > In case you haven't
> >> guessed, I'm testing
> >> > out
> >> > > > Jenkins and its
> >> > > > > ability
> >> > > > > > to create the artifacts
> and
> >> send emails.
> >> > Please
> >> > > > ignore any
> >> > > > > email that
> >> > > > > > looks like a vote or
> discuss
> >> thread.
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > -Alex
> >> > > > > >
> >> > > > > > On 2/10/19, 8:44 PM,
> "Alex
> >> Harui"
> >> > > > <ah...@adobe.com.INVALID>
> >> > > > > wrote:
> >> > > > > >
> >> > > > > > Om,
> >> > > > > >
> >> > > > > > Well, that's what
> I
> >> used for the last
> >> > > > release. I'm sure
> >> > > > > there is
> >> > > > > > probably some inaccuracy
> in it.
> >> > > > > >
> >> > > > > > That said, I'm
> >> abandoning that document
> >> > > and
> >> > > > taking a new
> >> > > > > angle
> >> > > > > > because that document
> presumed
> >> that the release
> >> > > > manager was
> >> > > > > trying to
> >> > > > > > create a release on
> his/her
> >> computer. I've
> >> > > given up
> >> > > > on that and
> >> > > > > working on
> >> > > > > > making releases from a
> shared
> >> computer for the
> >> > > reasons
> >> > > > I've
> >> > > > > stated
> >> > > > > > upthread. I hope to make
> some
> >> progress on that
> >> > > this
> >> > > > week.
> >> > > > > >
> >> > > > > > The key
> difference is
> >> that the new
> >> > angle
> >> > > does
> >> > > > not
> >> > > > > presume that you
> >> > > > > > have Git SSH and PGP
> signatures
> >> all set up on
> >> > > some
> >> > > > computer. I
> >> > > > > have not
> >> > > > > > looked into how Docker
> would
> >> handle that. You
> >> > > > certainly
> >> > > > > wouldn't want the
> >> > > > > > Docker image to contain
> your
> >> SSH or PGP
> >> > > keys/creds.
> >> > > > And if the
> >> > > > > Docker
> >> > > > > > image doesn't, then that
> is
> >> another stumbling
> >> > > block
> >> > > > for future
> >> > > > > RMs.
> >> > > > > >
> >> > > > > > The other key
> >> difference is that the
> >> > old
> >> > > > script presumed
> >> > > > > you could
> >> > > > > > create the 3 release in 3
> huge
> >> "easy" steps.
> >> > > We've
> >> > > > seen that is
> >> > > > > only true
> >> > > > > > for me. So the new angle
> >> creates many discrete
> >> > > steps
> >> > > > managed by
> >> > > > > Jenkins.
> >> > > > > >
> >> > > > > > So, it is up to
> you to
> >> decide what you
> >> > > want to
> >> > > > > "Docker-ize". You
> >> > > > > > can try to Docker-ize the
> >> current 3 big steps,
> >> > > so RMs
> >> > > > can try to
> >> > > > > run it on
> >> > > > > > their systems, but I'd
> bet they
> >> will just faiI
> >> > > due to
> >> > > > network
> >> > > > > issues. I
> >> > > > > > would be interested in
> using
> >> Docker to make
> >> > each
> >> > > of
> >> > > > these many
> >> > > > > discrete
> >> > > > > > steps portable to another
> >> server. I'm not
> >> > > going to
> >> > > > involve
> >> > > > > Docker at this
> >> > > > > > point. My main goal is
> just to
> >> see if I can
> >> > > create a
> >> > > > workflow
> >> > > > > of many
> >> > > > > > discrete steps that isn't
> >> horribly painful.
> >> > > Once we
> >> > > > see what
> >> > > > > these steps
> >> > > > > > turn out to be, then we
> can
> >> worry about server
> >> > > > portability of
> >> > > > > those steps.
> >> > > > > >
> >> > > > > > Either way, we
> want to
> >> know about
> >> > running
> >> > > > > Browser+Selenium for
> >> > > > > > sure. And maybe
> >> FlashPlayerDebugger or AIR. I
> >> > > would
> >> > > > want to
> >> > > > > know, for
> >> > > > > > example, how you debug a
> >> failing checkintest
> >> > in a
> >> > > > Docker
> >> > > > > container.
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > -Alex
> >> > > > > >
> >> > > > > >
> >> > > > > > On 2/10/19, 5:18
> PM,
> >> "OmPrakash
> >> > > Muppirala" <
> >> > > > > bigosmallm@gmail.com>
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > Alex,
> >> > > > > >
> >> > > > > > Just to be
> clear, I
> >> am following
> >> > the
> >> > > steps
> >> > > > from here
> >> > > > > to try
> >> > > > > > and setup a
> >> > > > > > docker
> container.
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736458102&sdata=j8LpE1uMhgEvjsA5CviAGVhve9VZHuZmZGcBt0fQ0JY%3D&reserved=0
> >> > > > > >
> >> > > > > > Is this doc
> up to
> >> date?
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > Om
> >> > > > > >
> >> > > > > > On Wed, Feb
> 6, 2019
> >> at 12:02 PM
> >> > > OmPrakash
> >> > > > Muppirala <
> >> > > > > > bigosmallm@gmail.com>
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > > One
> approach is
> >> to have each step
> >> > > in the
> >> > > > process
> >> > > > > spin up a
> >> > > > > > docker image.
> >> > > > > > > And use
> >> docker-compose to run
> >> > each
> >> > > > step. All the
> >> > > > > images can
> >> > > > > > be made to
> >> > > > > > > share a
> common
> >> volume where all
> >> > the
> >> > > > artifacts are
> >> > > > > stored
> >> > > > > > across steps.
> >> > > > > > >
> >> > > > > > > You are
> right
> >> about the
> >> > networking
> >> > > issue
> >> > > > though.
> >> > > > > Any
> >> > > > > > network related
> >> > > > > > > failure that
> >> occurs on the host
> >> > > machine
> >> > > > will most
> >> > > > > likely
> >> > > > > > occur in the
> >> > > > > > > docker
> >> container. Although, I am
> >> > > not
> >> > > > clear how we
> >> > > > > can
> >> > > > > > guarantee that the
> >> > > > > > > same issues
> will
> >> not occur on the
> >> > > > Jenkins server.
> >> > > > > I mean,
> >> > > > > > what is special
> >> > > > > > > about the
> Jenkins
> >> server that
> >> > > makes it
> >> > > > immune to
> >> > > > > these
> >> > > > > > networking issues?
> >> > > > > > >
> >> > > > > > > Thanks,
> >> > > > > > > Om
> >> > > > > > >
> >> > > > > > > On Wed, Feb
> 6,
> >> 2019 at 11:48 AM
> >> > > Alex
> >> > > > Harui
> >> > > > > > <aharui@adobe.com.invalid
> >
> >> > > > > > > wrote:
> >> > > > > > >
> >> > > > > > >> Again, I
> don't
> >> know anything
> >> > about
> >> > > > Docker, but
> >> > > > > before we
> >> > > > > > spend a lot of
> >> > > > > > >> time on
> Docker,
> >> I also want to
> >> > > point
> >> > > > out that the
> >> > > > > process
> >> > > > > > to create a
> >> > > > > > >> release
> cannot
> >> really be thought
> >> > > of as
> >> > > > "one
> >> > > > > application".
> >> > > > > > It will be a
> >> > > > > > >> series of
> >> "steps" to run. How
> >> > > many
> >> > > > steps
> >> > > > > depends on
> >> > > > > > whether we think we
> >> > > > > > >> can isolate
> >> enough stuff via
> >> > > Docker to
> >> > > > be able to
> >> > > > > run
> >> > > > > > Docker on the RM's
> >> > > > > > >> computer
> instead
> >> of some shared
> >> > > > computer. On a
> >> > > > > shared
> >> > > > > > computer there will
> >> > > > > > >> be dozens
> of
> >> steps because the
> >> > RM
> >> > > will
> >> > > > need to
> >> > > > > enter
> >> > > > > > passwords to commit
> >> > > > > > >> stuff. On
> a
> >> local computer I
> >> > > guess the
> >> > > > RM can
> >> > > > > supply
> >> > > > > > passwords but I think
> >> > > > > > >> there will
> be
> >> stopping points
> >> > > where the
> >> > > > Maven
> >> > > > > artifacts are
> >> > > > > > deployed and
> >> > > > > > >> the
> staging repo
> >> is closed, and
> >> > > another
> >> > > > stopping
> >> > > > > point for
> >> > > > > > the vote. It
> >> > > > > > >> seems like
> >> Docker works by
> >> > > downloading
> >> > > > > dependencies. Given
> >> > > > > > that the
> >> > > > > > >> problem
> the RMs
> >> had last time
> >> > > involved
> >> > > > downloads
> >> > > > > and
> >> > > > > > uploads, why do we
> >> > > > > > >> think
> Docker
> >> will really solve
> >> > > this for
> >> > > > creating
> >> > > > > releases
> >> > > > > > on local machines?
> >> > > > > > >>
> >> > > > > > >> The reason
> to do
> >> this on a
> >> > shared
> >> > > > machine is so
> >> > > > > that new
> >> > > > > > RMs don't have
> >> > > > > > >> to do as
> much
> >> setup. But then I
> >> > > wonder
> >> > > > about the
> >> > > > > > efficiency of kicking off
> >> > > > > > >> that many
> Docker
> >> images.
> >> > Jenkins
> >> > > can
> >> > > > manage that
> >> > > > > already.
> >> > > > > > Does Docker
> >> > > > > > >> have some
> sort
> >> of similar
> >> > > Dashboard or
> >> > > > would we
> >> > > > > use Jenkins
> >> > > > > > to kick off
> >> > > > > > >> Docker
> steps? I
> >> can't quite
> >> > > picture
> >> > > > what is the
> >> > > > > outermost
> >> > > > > > >>
> >> control/dashboard.
> >> > > > > > >>
> >> > > > > > >> -Alex
> >> > > > > > >>
> >> > > > > > >> On 2/6/19,
> 11:03
> >> AM, "Harbs" <
> >> > > > > harbs.lists@gmail.com> wrote:
> >> > > > > > >>
> >> > > > > > >> A quick
> >> search turns up
> >> > this:
> >> > > > > > >>
> >> > > > > > >>
> >> > > > > > >>
> >> > > > > >
> >> > > > >
> >> > > >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736458102&sdata=fdTpHtWcIqSV6hP407YixKFl5gK2K177Xr3NSWpjvtU%3D&reserved=0
> >> > > > > > >> <
> >> > > > > > >>
> >> > > > > >
> >> > > > >
> >> > > >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736468096&sdata=7ps%2Bc%2B5bm58wvVRynAID2WPXscuSPHcvRfdJ1QQdSck%3D&reserved=0
> >> > > > > > >> >
> >> > > > > > >>
> >> > > > > > >>
> >> > > > > >
> >> > > > >
> >> > > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736468096&sdata=2A63VFpxJjxK9AhvjE5uAzYPTG5X57IlB1MJ11iQNWA%3D&reserved=0
> >> > > > > > >> <
> >> > > > > > >>
> >> > > > > >
> >> > > > >
> >> > > >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736468096&sdata=2A63VFpxJjxK9AhvjE5uAzYPTG5X57IlB1MJ11iQNWA%3D&reserved=0
> >> > > > > > >> >
> >> > > > > > >>
> >> > > > > > >>
> >> > > > > >
> >> > > > >
> >> > > >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736468096&sdata=gQvz2x7044ZxqHsGW%2FUxZWcAKke%2B0aZ9oAdjPb0G%2FMw%3D&reserved=0
> >> > > > > > >> <
> >> > > > > > >>
> >> > > > > >
> >> > > > >
> >> > > >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736468096&sdata=gQvz2x7044ZxqHsGW%2FUxZWcAKke%2B0aZ9oAdjPb0G%2FMw%3D&reserved=0
> >> > > > > > >> >
> >> > > > > > >>
> >> > > > > > >> > On
> Feb 6,
> >> 2019, at 8:59
> >> > PM,
> >> > > Alex
> >> > > > Harui
> >> > > > > > <aharui@adobe.com.INVALID
> >
> >> > > > > > >> wrote:
> >> > > > > > >> >
> >> > > > > > >> >
> Thanks for
> >> volunteering to
> >> > > try it
> >> > > > Om. IMO,
> >> > > > > even more
> >> > > > > > important
> >> > > > > > >> than
> >> Firefox+Flash is
> >> > > > SomeBrowser+Selenium. We
> >> > > > > may also
> >> > > > > > need to run Adobe
> >> > > > > > >> AIR's
> adb. We
> >> could probably
> >> > > turn off
> >> > > > the Flash
> >> > > > > tests or
> >> > > > > > replace Flash
> >> > > > > > >> with AIR.
> >> > > > > > >> >
> >> > > > > > >> >
> Thanks,
> >>
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736468096&sdata=5%2FWpXG4swZR7rh0XS6DcPW5zi%2FizWpkEWZg0l9zF5Q4%3D&reserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736468096&sdata=5%2FWpXG4swZR7rh0XS6DcPW5zi%2FizWpkEWZg0l9zF5Q4%3D&reserved=0
> >*
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: 0.9.6 Release
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Alex,
Instruction here [1] contains everything what I need to know in order to
make RC1 ? I'm going to start trying tomorrow my time.
[1] https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
Thanks,
Piotr
wt., 18 cze 2019 o 07:51 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Hi Alex,
>
> Thank you! I will be working in release next week, so if anyone have
> anything to add there is some time.
>
> Thanks,
> Piotr
>
> On Tue, Jun 18, 2019, 7:28 AM Alex Harui <ah...@adobe.com.invalid> wrote:
>
>> Mx tests are working locally for me with this last change to
>> ListItemRenderer.
>>
>> So, the question for everyone is: is there anything else we want to put
>> in before trying to cut a release?
>>
>> We might need to change the ASDoc app after Greg's last change. We might
>> want to bang on ASDoc for a bit and see if anything major needs fixing
>> before cutting a release.
>>
>> The only other thing I thought of was trying to upgrade Selenium so we
>> can use a recent FireFox version. Right now we are stuck way back on FF47,
>> but I've also heard that more recent FF versions are less friendly to
>> Flash, so you have to use some other browser to test Flash. That's ok for
>> building the Royale SDK since the Flash tests are run in
>> FlashPlayerDebugger and the JS tests are run in a browser like FF.
>>
>> I'm tempted to say we should punt the inject_html in modules problem to
>> the next release.
>>
>> I will be adding more details to
>> https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
>> But there should be enough there to get an RC out for vote.
>>
>> Thanks,
>> -Alex
>>
>> On 6/17/19, 11:06 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>>
>> I just saw ASDoc work well enough for me to start with
>> mx.binding.BindabilityInfo and switch to mx.charts.AxisRenderer.
>>
>> There might be JSON parsing issues with other classes. Run the
>> bin/js-debug version, check the console if things don't load and see what
>> file failed to load and why.
>>
>> I will take a look at MXTests next.
>>
>> -Alex
>>
>> On 6/17/19, 8:08 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>>
>> ASDoc is not fully working for me. I've been working on that the
>> past several days. It took quite a while to fix the JSON output from new
>> and interesting ASDoc patterns. I'm now looking into failures due to
>> changes in coercion rules in the JS output. ASDoc was trying to save time
>> by using plain objects that were isomorphic to a class instead of actual
>> class instances.
>>
>> MXTests are failing on the CI server and probably locally but I
>> haven't gotten that far.
>>
>> I would think we want these things to work, but you are the RM so
>> it is up to you. Volunteers are welcome to help with these and other tasks.
>>
>> -Alex
>>
>> On 6/17/19, 12:44 AM, "Piotr Zarzycki" <pi...@gmail.com>
>> wrote:
>>
>> Hi Alex,
>>
>> I don't see any answer here - can I start with trying your
>> instruction and
>> start release ?
>>
>> Thanks,
>> Piotr
>>
>> śr., 12 cze 2019 o 10:12 Carlos Rovira <
>> carlosrovira@apache.org> napisał(a):
>>
>> > Hi Alex,
>> > just build from scratch right now and seems maven and ant
>> was ok
>> >
>> > El mié., 12 jun. 2019 a las 10:02, Alex Harui
>> (<ah...@adobe.com.invalid>)
>> > escribió:
>> >
>> > > The merge is complete, and the main builds seem to be
>> successful, except
>> > > for Maven on royale-asjs which was failing before the
>> merge.
>> > >
>> > > I'm still catching up on other things, but I think there
>> are some bugs we
>> > > need to fix before cutting the release? I think ASDoc
>> may not be fully
>> > > working? What else?
>> > >
>> > > -Alex
>> > >
>> > > On 6/10/19, 11:05 AM, "Piotr Zarzycki" <
>> piotrzarzycki21@gmail.com>
>> > wrote:
>> > >
>> > > Hi Alex,
>> > >
>> > > Many thanks for that! I will try to be RM. I will
>> have some dedicated
>> > > time
>> > > for that. I will wait for your instruction and merge
>> to develop.
>> > >
>> > > Thanks,
>> > > Piotr
>> > >
>> > >
>> > > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
>> <ah...@adobe.com.invalid>
>> > > wrote:
>> > >
>> > > > Well, that turned out to be much more
>> time-consuming than I
>> > > expected, but
>> > > > we can now create identical release artifacts on
>> Mac and Win. I am
>> > > hopeful
>> > > > this effort will pay off not only now in having
>> other folks
>> > generate
>> > > > releases, but also in the future if signed binaries
>> become a
>> > > requirement.
>> > > >
>> > > > There continues to be a lot of distractions in my
>> life that can
>> > cause
>> > > > delays, but I hope to merge the release_practice
>> branches into
>> > > develop over
>> > > > the next day or two and figure out where in the
>> wiki to document
>> > the
>> > > > release process. So, now is the time for one or
>> more people to
>> > step
>> > > up to
>> > > > be the RMs for 0.9.6 and help debug and improve the
>> process.
>> > > >
>> > > > I am going to try very hard not to "own" the
>> process. If something
>> > > goes
>> > > > wrong, I am going to ask others to try to debug and
>> fix it first
>> > > because it
>> > > > is in the project's best interests for others to
>> truly understand
>> > > how this
>> > > > stuff works.
>> > > >
>> > > > Thanks,
>> > > > -Alex
>> > > >
>> > > > On 5/23/19, 9:54 AM, "Alex Harui"
>> <ah...@adobe.com.INVALID>
>> > wrote:
>> > > >
>> > > > It has turned out to be harder than expected to
>> get the same
>> > > binaries
>> > > > on Mac and Win. I now have the identical binaries
>> for
>> > > royale-compiler and
>> > > > royale-typedefs Maven artifacts and am starting on
>> royale-asjs. I
>> > > might
>> > > > get lucky and the changes that fixed
>> royale-typedefs SWCs will
>> > > magically
>> > > > get the royale-asjs SWCs to match. Then we have to
>> make the Ant
>> > > artifacts
>> > > > match.
>> > > >
>> > > > There have been a lot of distractions in my
>> non-work life which
>> > > has
>> > > > also impeded progress. I hope to make much
>> progress this coming
>> > > week and
>> > > > if we're lucky, I will be asking for a volunteer
>> (or volunteers) to
>> > > test
>> > > > drive all of this stuff and be the RM for 0.9.6. I
>> am not going to
>> > > be the
>> > > > RM.
>> > > >
>> > > > -Alex
>> > > >
>> > > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
>> > piotrzarzycki21@gmail.com
>> > > >
>> > > > wrote:
>> > > >
>> > > > Hi Alex,
>> > > >
>> > > > It's been a while since you have started
>> effort with
>> > > automating
>> > > > build.
>> > > > Where are you with that ? Are we closer to
>> started 0.9.6.
>> > Do
>> > > you
>> > > > need any
>> > > > help with this ?
>> > > >
>> > > > Thanks,
>> > > > Piotr
>> > > >
>> > > > wt., 2 kwi 2019 o 19:30 Alex Harui
>> > <aharui@adobe.com.invalid
>> > > >
>> > > > napisał(a):
>> > > >
>> > > > > Update:
>> > > > >
>> > > > > In order to make verification of binary
>> release packages
>> > > created
>> > > > on the
>> > > > > server easier, I have made changes to our
>> build scripts
>> > and
>> > > > tools to try to
>> > > > > generate reproducible binaries. I've
>> seen two different
>> > > builds
>> > > > compare on
>> > > > > my Mac. The next challenge will be to
>> see if the server
>> > > can
>> > > > build a
>> > > > > package on Windows that will compare on
>> Mac.
>> > > > >
>> > > > > One of the changes I needed to make is to
>> JBurg. The
>> > > version of
>> > > > JBurg we
>> > > > > use generates method names including a
>> hash that doesn't
>> > > > reproduce the same
>> > > > > name each time. I have changes to JBurg
>> ready, however
>> > > JBurg is
>> > > > currently
>> > > > > under CPL which is category B. We only
>> need one file, we
>> > > don't
>> > > > need or
>> > > > > want all of JBurg at this time. The one
>> JBurg file is
>> > > jointly
>> > > > owned by
>> > > > > Adobe and Tom Harwood. I've contact Tom
>> and he will be
>> > > filing
>> > > > an ICLA and
>> > > > > has given me permission to commit the
>> lines he owns in
>> > > that one
>> > > > file.
>> > > > >
>> > > > > This is the revision of the file that
>> will be donated by
>> > > > Tom/Adobe.
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959643335&sdata=ZYf5QUAPr%2BNKndH9vr8pI7TeTAWX1hxLMV%2FyKb1U0g4%3D&reserved=0
>> > > > >
>> > > > > Once this file goes in with the changes
>> to keep the
>> > method
>> > > names
>> > > > the same,
>> > > > > there will be more tweaks to the release
>> tasks and then
>> > we
>> > > can
>> > > > try cutting
>> > > > > a release. I'm thinking we'll be at that
>> point in early
>> > > May, so
>> > > > now is the
>> > > > > time to get stuff in for the 0.9.6
>> release.
>> > > > >
>> > > > > Thanks,
>> > > > > -Alex
>> > > > >
>> > > > > On 3/8/19, 9:27 AM, "Alex Harui" <
>> aharui@adobe.com>
>> > wrote:
>> > > > >
>> > > > > I would much rather have others find
>> and fix issues
>> > > > themselves. That
>> > > > > way, more people than just me will know
>> how to maintain
>> > the
>> > > > system. It
>> > > > > actually turns out that, IMO, a group of
>> people can work
>> > > on the
>> > > > release.
>> > > > > There are 14 steps. Literally, 14
>> different people could
>> > > > execute one step
>> > > > > each.
>> > > > >
>> > > > > My 2 cents,
>> > > > > -Alex
>> > > > >
>> > > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
>> > > carlosrovira@apache.org>
>> > > > wrote:
>> > > > >
>> > > > > Hi Alex,
>> > > > >
>> > > > > amazing work! congrats to reach
>> to this point! :)
>> > > > >
>> > > > > I need to put my head on all of
>> this, but count
>> > on
>> > > me to
>> > > > be a RM.
>> > > > > I think
>> > > > > the best thing should be that you
>> be the first RM
>> > > to try
>> > > > your own
>> > > > > development at least for the
>> first time, and then
>> > > the
>> > > > rest of us
>> > > > > will
>> > > > > follow you on the next releases.
>> With all this on
>> > > place
>> > > > we maybe
>> > > > > could
>> > > > > release once a month or every two
>> months...
>> > > > >
>> > > > > Thanks for doing this :)
>> > > > >
>> > > > > Carlos
>> > > > >
>> > > > >
>> > > > > El vie., 8 mar. 2019 a las 1:55,
>> Alex Harui
>> > > > > (<ah...@adobe.com.invalid>)
>> > > > > escribió:
>> > > > >
>> > > > > > OK, I've now seen Jenkins
>> perform the steps to
>> > > build
>> > > > the release
>> > > > > > artifacts. Folks interested in
>> Docker-izing
>> > the
>> > > steps
>> > > > are
>> > > > > welcome to look
>> > > > > > at the jobs on the "Royale
>> Release" tab on the
>> > CI
>> > > > server.
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959643335&sdata=tCcelcUXdJFddO5EtAM3or35OvY1W55uN0axY%2FJRIcI%3D&reserved=0
>> > > > > >
>> > > > > > These steps assume that the RM
>> can run the
>> > basic
>> > > Maven
>> > > > and Ant
>> > > > > build on
>> > > > > > the RM's computer. I think
>> that's a fair
>> > > requirement
>> > > > since all
>> > > > > of us on the
>> > > > > > PMC need to able to do that to
>> build the RC in
>> > > order
>> > > > to vote on
>> > > > > it.
>> > > > > > Jenkins does other tasks like
>> run the Maven
>> > > release
>> > > > plugin
>> > > > > steps.
>> > > > > >
>> > > > > > Currently that results in
>> binaries on Jenkins
>> > > that are
>> > > > > downloaded to the
>> > > > > > RM's computer. These binaries
>> need to be
>> > > verified by
>> > > > the RM
>> > > > > which is the
>> > > > > > next phase I will be starting
>> on now. The RM
>> > > verifies
>> > > > the bits
>> > > > > and then
>> > > > > > PGP signs them. And then the
>> bits are uploaded
>> > > off
>> > > > the RM's
>> > > > > computer to
>> > > > > > Maven Staging or dist.a.o/dev.
>> If that
>> > > uploading
>> > > > turns out to
>> > > > > be a point
>> > > > > > of failure, we have the option
>> of having
>> > Jenkins
>> > > > upload the big
>> > > > > files and
>> > > > > > have the RM only upload PGP
>> signature files.
>> > Or
>> > > > finding a way
>> > > > > for Jenkins
>> > > > > > to get the signature files from
>> the RM. The
>> > > uploads
>> > > > worked fine
>> > > > > for me,
>> > > > > > but then again, so did the old
>> script's
>> > uploads.
>> > > > > >
>> > > > > > Therefore, once I get the
>> binary verification
>> > > phase
>> > > > completed, I
>> > > > > think
>> > > > > > someone other than me should be
>> the RM and try
>> > > to use
>> > > > these
>> > > > > steps to
>> > > > > > generate the release and help
>> debug the process
>> > > for
>> > > > the next
>> > > > > RM. So,
>> > > > > > please try to carve out some
>> time to be the RM.
>> > > One
>> > > > advantage
>> > > > > of doing
>> > > > > > most of the work on Jenkins is
>> that it frees up
>> > > my
>> > > > computer to
>> > > > > do other
>> > > > > > things while Jenkins is
>> cranking away.
>> > > > > >
>> > > > > > I think we're at least a week
>> away from binary
>> > > > verification,
>> > > > > maybe two, so
>> > > > > > it is time to start thinking
>> about what is
>> > going
>> > > in
>> > > > this release.
>> > > > > >
>> > > > > > Thanks,
>> > > > > > -Alex
>> > > > > >
>> > > > > > On 3/7/19, 4:15 PM, "Alex Harui"
>> > > > <ah...@adobe.com.INVALID>
>> > > > > wrote:
>> > > > > >
>> > > > > > In case you haven't
>> guessed, I'm testing
>> > out
>> > > > Jenkins and its
>> > > > > ability
>> > > > > > to create the artifacts and
>> send emails.
>> > Please
>> > > > ignore any
>> > > > > email that
>> > > > > > looks like a vote or discuss
>> thread.
>> > > > > >
>> > > > > > Thanks,
>> > > > > > -Alex
>> > > > > >
>> > > > > > On 2/10/19, 8:44 PM, "Alex
>> Harui"
>> > > > <ah...@adobe.com.INVALID>
>> > > > > wrote:
>> > > > > >
>> > > > > > Om,
>> > > > > >
>> > > > > > Well, that's what I
>> used for the last
>> > > > release. I'm sure
>> > > > > there is
>> > > > > > probably some inaccuracy in it.
>> > > > > >
>> > > > > > That said, I'm
>> abandoning that document
>> > > and
>> > > > taking a new
>> > > > > angle
>> > > > > > because that document presumed
>> that the release
>> > > > manager was
>> > > > > trying to
>> > > > > > create a release on his/her
>> computer. I've
>> > > given up
>> > > > on that and
>> > > > > working on
>> > > > > > making releases from a shared
>> computer for the
>> > > reasons
>> > > > I've
>> > > > > stated
>> > > > > > upthread. I hope to make some
>> progress on that
>> > > this
>> > > > week.
>> > > > > >
>> > > > > > The key difference is
>> that the new
>> > angle
>> > > does
>> > > > not
>> > > > > presume that you
>> > > > > > have Git SSH and PGP signatures
>> all set up on
>> > > some
>> > > > computer. I
>> > > > > have not
>> > > > > > looked into how Docker would
>> handle that. You
>> > > > certainly
>> > > > > wouldn't want the
>> > > > > > Docker image to contain your
>> SSH or PGP
>> > > keys/creds.
>> > > > And if the
>> > > > > Docker
>> > > > > > image doesn't, then that is
>> another stumbling
>> > > block
>> > > > for future
>> > > > > RMs.
>> > > > > >
>> > > > > > The other key
>> difference is that the
>> > old
>> > > > script presumed
>> > > > > you could
>> > > > > > create the 3 release in 3 huge
>> "easy" steps.
>> > > We've
>> > > > seen that is
>> > > > > only true
>> > > > > > for me. So the new angle
>> creates many discrete
>> > > steps
>> > > > managed by
>> > > > > Jenkins.
>> > > > > >
>> > > > > > So, it is up to you to
>> decide what you
>> > > want to
>> > > > > "Docker-ize". You
>> > > > > > can try to Docker-ize the
>> current 3 big steps,
>> > > so RMs
>> > > > can try to
>> > > > > run it on
>> > > > > > their systems, but I'd bet they
>> will just faiI
>> > > due to
>> > > > network
>> > > > > issues. I
>> > > > > > would be interested in using
>> Docker to make
>> > each
>> > > of
>> > > > these many
>> > > > > discrete
>> > > > > > steps portable to another
>> server. I'm not
>> > > going to
>> > > > involve
>> > > > > Docker at this
>> > > > > > point. My main goal is just to
>> see if I can
>> > > create a
>> > > > workflow
>> > > > > of many
>> > > > > > discrete steps that isn't
>> horribly painful.
>> > > Once we
>> > > > see what
>> > > > > these steps
>> > > > > > turn out to be, then we can
>> worry about server
>> > > > portability of
>> > > > > those steps.
>> > > > > >
>> > > > > > Either way, we want to
>> know about
>> > running
>> > > > > Browser+Selenium for
>> > > > > > sure. And maybe
>> FlashPlayerDebugger or AIR. I
>> > > would
>> > > > want to
>> > > > > know, for
>> > > > > > example, how you debug a
>> failing checkintest
>> > in a
>> > > > Docker
>> > > > > container.
>> > > > > >
>> > > > > > Thanks,
>> > > > > > -Alex
>> > > > > >
>> > > > > >
>> > > > > > On 2/10/19, 5:18 PM,
>> "OmPrakash
>> > > Muppirala" <
>> > > > > bigosmallm@gmail.com>
>> > > > > > wrote:
>> > > > > >
>> > > > > > Alex,
>> > > > > >
>> > > > > > Just to be clear, I
>> am following
>> > the
>> > > steps
>> > > > from here
>> > > > > to try
>> > > > > > and setup a
>> > > > > > docker container.
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959648328&sdata=W9%2B3T2XDDiDXUDWXYBWV4DYLYZlsJGcfhnhD2hXzTh0%3D&reserved=0
>> > > > > >
>> > > > > > Is this doc up to
>> date?
>> > > > > >
>> > > > > > Thanks,
>> > > > > > Om
>> > > > > >
>> > > > > > On Wed, Feb 6, 2019
>> at 12:02 PM
>> > > OmPrakash
>> > > > Muppirala <
>> > > > > > bigosmallm@gmail.com>
>> > > > > > wrote:
>> > > > > >
>> > > > > > > One approach is
>> to have each step
>> > > in the
>> > > > process
>> > > > > spin up a
>> > > > > > docker image.
>> > > > > > > And use
>> docker-compose to run
>> > each
>> > > > step. All the
>> > > > > images can
>> > > > > > be made to
>> > > > > > > share a common
>> volume where all
>> > the
>> > > > artifacts are
>> > > > > stored
>> > > > > > across steps.
>> > > > > > >
>> > > > > > > You are right
>> about the
>> > networking
>> > > issue
>> > > > though.
>> > > > > Any
>> > > > > > network related
>> > > > > > > failure that
>> occurs on the host
>> > > machine
>> > > > will most
>> > > > > likely
>> > > > > > occur in the
>> > > > > > > docker
>> container. Although, I am
>> > > not
>> > > > clear how we
>> > > > > can
>> > > > > > guarantee that the
>> > > > > > > same issues will
>> not occur on the
>> > > > Jenkins server.
>> > > > > I mean,
>> > > > > > what is special
>> > > > > > > about the Jenkins
>> server that
>> > > makes it
>> > > > immune to
>> > > > > these
>> > > > > > networking issues?
>> > > > > > >
>> > > > > > > Thanks,
>> > > > > > > Om
>> > > > > > >
>> > > > > > > On Wed, Feb 6,
>> 2019 at 11:48 AM
>> > > Alex
>> > > > Harui
>> > > > > > <ah...@adobe.com.invalid>
>> > > > > > > wrote:
>> > > > > > >
>> > > > > > >> Again, I don't
>> know anything
>> > about
>> > > > Docker, but
>> > > > > before we
>> > > > > > spend a lot of
>> > > > > > >> time on Docker,
>> I also want to
>> > > point
>> > > > out that the
>> > > > > process
>> > > > > > to create a
>> > > > > > >> release cannot
>> really be thought
>> > > of as
>> > > > "one
>> > > > > application".
>> > > > > > It will be a
>> > > > > > >> series of
>> "steps" to run. How
>> > > many
>> > > > steps
>> > > > > depends on
>> > > > > > whether we think we
>> > > > > > >> can isolate
>> enough stuff via
>> > > Docker to
>> > > > be able to
>> > > > > run
>> > > > > > Docker on the RM's
>> > > > > > >> computer instead
>> of some shared
>> > > > computer. On a
>> > > > > shared
>> > > > > > computer there will
>> > > > > > >> be dozens of
>> steps because the
>> > RM
>> > > will
>> > > > need to
>> > > > > enter
>> > > > > > passwords to commit
>> > > > > > >> stuff. On a
>> local computer I
>> > > guess the
>> > > > RM can
>> > > > > supply
>> > > > > > passwords but I think
>> > > > > > >> there will be
>> stopping points
>> > > where the
>> > > > Maven
>> > > > > artifacts are
>> > > > > > deployed and
>> > > > > > >> the staging repo
>> is closed, and
>> > > another
>> > > > stopping
>> > > > > point for
>> > > > > > the vote. It
>> > > > > > >> seems like
>> Docker works by
>> > > downloading
>> > > > > dependencies. Given
>> > > > > > that the
>> > > > > > >> problem the RMs
>> had last time
>> > > involved
>> > > > downloads
>> > > > > and
>> > > > > > uploads, why do we
>> > > > > > >> think Docker
>> will really solve
>> > > this for
>> > > > creating
>> > > > > releases
>> > > > > > on local machines?
>> > > > > > >>
>> > > > > > >> The reason to do
>> this on a
>> > shared
>> > > > machine is so
>> > > > > that new
>> > > > > > RMs don't have
>> > > > > > >> to do as much
>> setup. But then I
>> > > wonder
>> > > > about the
>> > > > > > efficiency of kicking off
>> > > > > > >> that many Docker
>> images.
>> > Jenkins
>> > > can
>> > > > manage that
>> > > > > already.
>> > > > > > Does Docker
>> > > > > > >> have some sort
>> of similar
>> > > Dashboard or
>> > > > would we
>> > > > > use Jenkins
>> > > > > > to kick off
>> > > > > > >> Docker steps? I
>> can't quite
>> > > picture
>> > > > what is the
>> > > > > outermost
>> > > > > > >>
>> control/dashboard.
>> > > > > > >>
>> > > > > > >> -Alex
>> > > > > > >>
>> > > > > > >> On 2/6/19, 11:03
>> AM, "Harbs" <
>> > > > > harbs.lists@gmail.com> wrote:
>> > > > > > >>
>> > > > > > >> A quick
>> search turns up
>> > this:
>> > > > > > >>
>> > > > > > >>
>> > > > > > >>
>> > > > > >
>> > > > >
>> > > >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959648328&sdata=cg4RjT3Tb9nBspx0dWR1ENPGiSrOk4ooKpQK8vmatLs%3D&reserved=0
>> > > > > > >> <
>> > > > > > >>
>> > > > > >
>> > > > >
>> > > >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959648328&sdata=cg4RjT3Tb9nBspx0dWR1ENPGiSrOk4ooKpQK8vmatLs%3D&reserved=0
>> > > > > > >> >
>> > > > > > >>
>> > > > > > >>
>> > > > > >
>> > > > >
>> > > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959648328&sdata=9UnncgpaERA7ATYkT8zcyEzqgmV4%2FqxzpFXcXZVY%2BhE%3D&reserved=0
>> > > > > > >> <
>> > > > > > >>
>> > > > > >
>> > > > >
>> > > >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959653317&sdata=Ta36Y8PPxHJauVKuQui74a0Mm5WyfGSTKZeK2g09gHI%3D&reserved=0
>> > > > > > >> >
>> > > > > > >>
>> > > > > > >>
>> > > > > >
>> > > > >
>> > > >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959653317&sdata=4bvIekmv9Gv%2Fim0qWdiPNJpSm5r3Tb3H6dlX%2Buassuc%3D&reserved=0
>> > > > > > >> <
>> > > > > > >>
>> > > > > >
>> > > > >
>> > > >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959653317&sdata=4bvIekmv9Gv%2Fim0qWdiPNJpSm5r3Tb3H6dlX%2Buassuc%3D&reserved=0
>> > > > > > >> >
>> > > > > > >>
>> > > > > > >> > On Feb 6,
>> 2019, at 8:59
>> > PM,
>> > > Alex
>> > > > Harui
>> > > > > > <ah...@adobe.com.INVALID>
>> > > > > > >> wrote:
>> > > > > > >> >
>> > > > > > >> > Thanks for
>> volunteering to
>> > > try it
>> > > > Om. IMO,
>> > > > > even more
>> > > > > > important
>> > > > > > >> than
>> Firefox+Flash is
>> > > > SomeBrowser+Selenium. We
>> > > > > may also
>> > > > > > need to run Adobe
>> > > > > > >> AIR's adb. We
>> could probably
>> > > turn off
>> > > > the Flash
>> > > > > tests or
>> > > > > > replace Flash
>> > > > > > >> with AIR.
>> > > > > > >> >
>> > > > > > >> > Thanks,
>>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: 0.9.6 Release
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Alex,
Thank you! I will be working in release next week, so if anyone have
anything to add there is some time.
Thanks,
Piotr
On Tue, Jun 18, 2019, 7:28 AM Alex Harui <ah...@adobe.com.invalid> wrote:
> Mx tests are working locally for me with this last change to
> ListItemRenderer.
>
> So, the question for everyone is: is there anything else we want to put
> in before trying to cut a release?
>
> We might need to change the ASDoc app after Greg's last change. We might
> want to bang on ASDoc for a bit and see if anything major needs fixing
> before cutting a release.
>
> The only other thing I thought of was trying to upgrade Selenium so we can
> use a recent FireFox version. Right now we are stuck way back on FF47, but
> I've also heard that more recent FF versions are less friendly to Flash, so
> you have to use some other browser to test Flash. That's ok for building
> the Royale SDK since the Flash tests are run in FlashPlayerDebugger and the
> JS tests are run in a browser like FF.
>
> I'm tempted to say we should punt the inject_html in modules problem to
> the next release.
>
> I will be adding more details to
> https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
> But there should be enough there to get an RC out for vote.
>
> Thanks,
> -Alex
>
> On 6/17/19, 11:06 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> I just saw ASDoc work well enough for me to start with
> mx.binding.BindabilityInfo and switch to mx.charts.AxisRenderer.
>
> There might be JSON parsing issues with other classes. Run the
> bin/js-debug version, check the console if things don't load and see what
> file failed to load and why.
>
> I will take a look at MXTests next.
>
> -Alex
>
> On 6/17/19, 8:08 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> ASDoc is not fully working for me. I've been working on that the
> past several days. It took quite a while to fix the JSON output from new
> and interesting ASDoc patterns. I'm now looking into failures due to
> changes in coercion rules in the JS output. ASDoc was trying to save time
> by using plain objects that were isomorphic to a class instead of actual
> class instances.
>
> MXTests are failing on the CI server and probably locally but I
> haven't gotten that far.
>
> I would think we want these things to work, but you are the RM so
> it is up to you. Volunteers are welcome to help with these and other tasks.
>
> -Alex
>
> On 6/17/19, 12:44 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
>
> Hi Alex,
>
> I don't see any answer here - can I start with trying your
> instruction and
> start release ?
>
> Thanks,
> Piotr
>
> śr., 12 cze 2019 o 10:12 Carlos Rovira <
> carlosrovira@apache.org> napisał(a):
>
> > Hi Alex,
> > just build from scratch right now and seems maven and ant
> was ok
> >
> > El mié., 12 jun. 2019 a las 10:02, Alex Harui
> (<ah...@adobe.com.invalid>)
> > escribió:
> >
> > > The merge is complete, and the main builds seem to be
> successful, except
> > > for Maven on royale-asjs which was failing before the
> merge.
> > >
> > > I'm still catching up on other things, but I think there
> are some bugs we
> > > need to fix before cutting the release? I think ASDoc may
> not be fully
> > > working? What else?
> > >
> > > -Alex
> > >
> > > On 6/10/19, 11:05 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com>
> > wrote:
> > >
> > > Hi Alex,
> > >
> > > Many thanks for that! I will try to be RM. I will have
> some dedicated
> > > time
> > > for that. I will wait for your instruction and merge
> to develop.
> > >
> > > Thanks,
> > > Piotr
> > >
> > >
> > > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
> <ah...@adobe.com.invalid>
> > > wrote:
> > >
> > > > Well, that turned out to be much more time-consuming
> than I
> > > expected, but
> > > > we can now create identical release artifacts on Mac
> and Win. I am
> > > hopeful
> > > > this effort will pay off not only now in having
> other folks
> > generate
> > > > releases, but also in the future if signed binaries
> become a
> > > requirement.
> > > >
> > > > There continues to be a lot of distractions in my
> life that can
> > cause
> > > > delays, but I hope to merge the release_practice
> branches into
> > > develop over
> > > > the next day or two and figure out where in the wiki
> to document
> > the
> > > > release process. So, now is the time for one or
> more people to
> > step
> > > up to
> > > > be the RMs for 0.9.6 and help debug and improve the
> process.
> > > >
> > > > I am going to try very hard not to "own" the
> process. If something
> > > goes
> > > > wrong, I am going to ask others to try to debug and
> fix it first
> > > because it
> > > > is in the project's best interests for others to
> truly understand
> > > how this
> > > > stuff works.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 5/23/19, 9:54 AM, "Alex Harui"
> <ah...@adobe.com.INVALID>
> > wrote:
> > > >
> > > > It has turned out to be harder than expected to
> get the same
> > > binaries
> > > > on Mac and Win. I now have the identical binaries
> for
> > > royale-compiler and
> > > > royale-typedefs Maven artifacts and am starting on
> royale-asjs. I
> > > might
> > > > get lucky and the changes that fixed royale-typedefs
> SWCs will
> > > magically
> > > > get the royale-asjs SWCs to match. Then we have to
> make the Ant
> > > artifacts
> > > > match.
> > > >
> > > > There have been a lot of distractions in my
> non-work life which
> > > has
> > > > also impeded progress. I hope to make much progress
> this coming
> > > week and
> > > > if we're lucky, I will be asking for a volunteer (or
> volunteers) to
> > > test
> > > > drive all of this stuff and be the RM for 0.9.6. I
> am not going to
> > > be the
> > > > RM.
> > > >
> > > > -Alex
> > > >
> > > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> > piotrzarzycki21@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > Hi Alex,
> > > >
> > > > It's been a while since you have started
> effort with
> > > automating
> > > > build.
> > > > Where are you with that ? Are we closer to
> started 0.9.6.
> > Do
> > > you
> > > > need any
> > > > help with this ?
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > wt., 2 kwi 2019 o 19:30 Alex Harui
> > <aharui@adobe.com.invalid
> > > >
> > > > napisał(a):
> > > >
> > > > > Update:
> > > > >
> > > > > In order to make verification of binary
> release packages
> > > created
> > > > on the
> > > > > server easier, I have made changes to our
> build scripts
> > and
> > > > tools to try to
> > > > > generate reproducible binaries. I've seen
> two different
> > > builds
> > > > compare on
> > > > > my Mac. The next challenge will be to
> see if the server
> > > can
> > > > build a
> > > > > package on Windows that will compare on
> Mac.
> > > > >
> > > > > One of the changes I needed to make is to
> JBurg. The
> > > version of
> > > > JBurg we
> > > > > use generates method names including a
> hash that doesn't
> > > > reproduce the same
> > > > > name each time. I have changes to JBurg
> ready, however
> > > JBurg is
> > > > currently
> > > > > under CPL which is category B. We only
> need one file, we
> > > don't
> > > > need or
> > > > > want all of JBurg at this time. The one
> JBurg file is
> > > jointly
> > > > owned by
> > > > > Adobe and Tom Harwood. I've contact Tom
> and he will be
> > > filing
> > > > an ICLA and
> > > > > has given me permission to commit the
> lines he owns in
> > > that one
> > > > file.
> > > > >
> > > > > This is the revision of the file that will
> be donated by
> > > > Tom/Adobe.
> > > > >
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959643335&sdata=ZYf5QUAPr%2BNKndH9vr8pI7TeTAWX1hxLMV%2FyKb1U0g4%3D&reserved=0
> > > > >
> > > > > Once this file goes in with the changes to
> keep the
> > method
> > > names
> > > > the same,
> > > > > there will be more tweaks to the release
> tasks and then
> > we
> > > can
> > > > try cutting
> > > > > a release. I'm thinking we'll be at that
> point in early
> > > May, so
> > > > now is the
> > > > > time to get stuff in for the 0.9.6 release.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 3/8/19, 9:27 AM, "Alex Harui" <
> aharui@adobe.com>
> > wrote:
> > > > >
> > > > > I would much rather have others find
> and fix issues
> > > > themselves. That
> > > > > way, more people than just me will know
> how to maintain
> > the
> > > > system. It
> > > > > actually turns out that, IMO, a group of
> people can work
> > > on the
> > > > release.
> > > > > There are 14 steps. Literally, 14
> different people could
> > > > execute one step
> > > > > each.
> > > > >
> > > > > My 2 cents,
> > > > > -Alex
> > > > >
> > > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> > > carlosrovira@apache.org>
> > > > wrote:
> > > > >
> > > > > Hi Alex,
> > > > >
> > > > > amazing work! congrats to reach to
> this point! :)
> > > > >
> > > > > I need to put my head on all of
> this, but count
> > on
> > > me to
> > > > be a RM.
> > > > > I think
> > > > > the best thing should be that you
> be the first RM
> > > to try
> > > > your own
> > > > > development at least for the first
> time, and then
> > > the
> > > > rest of us
> > > > > will
> > > > > follow you on the next releases.
> With all this on
> > > place
> > > > we maybe
> > > > > could
> > > > > release once a month or every two
> months...
> > > > >
> > > > > Thanks for doing this :)
> > > > >
> > > > > Carlos
> > > > >
> > > > >
> > > > > El vie., 8 mar. 2019 a las 1:55,
> Alex Harui
> > > > > (<ah...@adobe.com.invalid>)
> > > > > escribió:
> > > > >
> > > > > > OK, I've now seen Jenkins
> perform the steps to
> > > build
> > > > the release
> > > > > > artifacts. Folks interested in
> Docker-izing
> > the
> > > steps
> > > > are
> > > > > welcome to look
> > > > > > at the jobs on the "Royale
> Release" tab on the
> > CI
> > > > server.
> > > > > >
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959643335&sdata=tCcelcUXdJFddO5EtAM3or35OvY1W55uN0axY%2FJRIcI%3D&reserved=0
> > > > > >
> > > > > > These steps assume that the RM
> can run the
> > basic
> > > Maven
> > > > and Ant
> > > > > build on
> > > > > > the RM's computer. I think
> that's a fair
> > > requirement
> > > > since all
> > > > > of us on the
> > > > > > PMC need to able to do that to
> build the RC in
> > > order
> > > > to vote on
> > > > > it.
> > > > > > Jenkins does other tasks like
> run the Maven
> > > release
> > > > plugin
> > > > > steps.
> > > > > >
> > > > > > Currently that results in
> binaries on Jenkins
> > > that are
> > > > > downloaded to the
> > > > > > RM's computer. These binaries
> need to be
> > > verified by
> > > > the RM
> > > > > which is the
> > > > > > next phase I will be starting on
> now. The RM
> > > verifies
> > > > the bits
> > > > > and then
> > > > > > PGP signs them. And then the
> bits are uploaded
> > > off
> > > > the RM's
> > > > > computer to
> > > > > > Maven Staging or dist.a.o/dev.
> If that
> > > uploading
> > > > turns out to
> > > > > be a point
> > > > > > of failure, we have the option
> of having
> > Jenkins
> > > > upload the big
> > > > > files and
> > > > > > have the RM only upload PGP
> signature files.
> > Or
> > > > finding a way
> > > > > for Jenkins
> > > > > > to get the signature files from
> the RM. The
> > > uploads
> > > > worked fine
> > > > > for me,
> > > > > > but then again, so did the old
> script's
> > uploads.
> > > > > >
> > > > > > Therefore, once I get the binary
> verification
> > > phase
> > > > completed, I
> > > > > think
> > > > > > someone other than me should be
> the RM and try
> > > to use
> > > > these
> > > > > steps to
> > > > > > generate the release and help
> debug the process
> > > for
> > > > the next
> > > > > RM. So,
> > > > > > please try to carve out some
> time to be the RM.
> > > One
> > > > advantage
> > > > > of doing
> > > > > > most of the work on Jenkins is
> that it frees up
> > > my
> > > > computer to
> > > > > do other
> > > > > > things while Jenkins is cranking
> away.
> > > > > >
> > > > > > I think we're at least a week
> away from binary
> > > > verification,
> > > > > maybe two, so
> > > > > > it is time to start thinking
> about what is
> > going
> > > in
> > > > this release.
> > > > > >
> > > > > > Thanks,
> > > > > > -Alex
> > > > > >
> > > > > > On 3/7/19, 4:15 PM, "Alex Harui"
> > > > <ah...@adobe.com.INVALID>
> > > > > wrote:
> > > > > >
> > > > > > In case you haven't guessed,
> I'm testing
> > out
> > > > Jenkins and its
> > > > > ability
> > > > > > to create the artifacts and send
> emails.
> > Please
> > > > ignore any
> > > > > email that
> > > > > > looks like a vote or discuss
> thread.
> > > > > >
> > > > > > Thanks,
> > > > > > -Alex
> > > > > >
> > > > > > On 2/10/19, 8:44 PM, "Alex
> Harui"
> > > > <ah...@adobe.com.INVALID>
> > > > > wrote:
> > > > > >
> > > > > > Om,
> > > > > >
> > > > > > Well, that's what I used
> for the last
> > > > release. I'm sure
> > > > > there is
> > > > > > probably some inaccuracy in it.
> > > > > >
> > > > > > That said, I'm
> abandoning that document
> > > and
> > > > taking a new
> > > > > angle
> > > > > > because that document presumed
> that the release
> > > > manager was
> > > > > trying to
> > > > > > create a release on his/her
> computer. I've
> > > given up
> > > > on that and
> > > > > working on
> > > > > > making releases from a shared
> computer for the
> > > reasons
> > > > I've
> > > > > stated
> > > > > > upthread. I hope to make some
> progress on that
> > > this
> > > > week.
> > > > > >
> > > > > > The key difference is
> that the new
> > angle
> > > does
> > > > not
> > > > > presume that you
> > > > > > have Git SSH and PGP signatures
> all set up on
> > > some
> > > > computer. I
> > > > > have not
> > > > > > looked into how Docker would
> handle that. You
> > > > certainly
> > > > > wouldn't want the
> > > > > > Docker image to contain your SSH
> or PGP
> > > keys/creds.
> > > > And if the
> > > > > Docker
> > > > > > image doesn't, then that is
> another stumbling
> > > block
> > > > for future
> > > > > RMs.
> > > > > >
> > > > > > The other key difference
> is that the
> > old
> > > > script presumed
> > > > > you could
> > > > > > create the 3 release in 3 huge
> "easy" steps.
> > > We've
> > > > seen that is
> > > > > only true
> > > > > > for me. So the new angle
> creates many discrete
> > > steps
> > > > managed by
> > > > > Jenkins.
> > > > > >
> > > > > > So, it is up to you to
> decide what you
> > > want to
> > > > > "Docker-ize". You
> > > > > > can try to Docker-ize the
> current 3 big steps,
> > > so RMs
> > > > can try to
> > > > > run it on
> > > > > > their systems, but I'd bet they
> will just faiI
> > > due to
> > > > network
> > > > > issues. I
> > > > > > would be interested in using
> Docker to make
> > each
> > > of
> > > > these many
> > > > > discrete
> > > > > > steps portable to another
> server. I'm not
> > > going to
> > > > involve
> > > > > Docker at this
> > > > > > point. My main goal is just to
> see if I can
> > > create a
> > > > workflow
> > > > > of many
> > > > > > discrete steps that isn't
> horribly painful.
> > > Once we
> > > > see what
> > > > > these steps
> > > > > > turn out to be, then we can
> worry about server
> > > > portability of
> > > > > those steps.
> > > > > >
> > > > > > Either way, we want to
> know about
> > running
> > > > > Browser+Selenium for
> > > > > > sure. And maybe
> FlashPlayerDebugger or AIR. I
> > > would
> > > > want to
> > > > > know, for
> > > > > > example, how you debug a failing
> checkintest
> > in a
> > > > Docker
> > > > > container.
> > > > > >
> > > > > > Thanks,
> > > > > > -Alex
> > > > > >
> > > > > >
> > > > > > On 2/10/19, 5:18 PM,
> "OmPrakash
> > > Muppirala" <
> > > > > bigosmallm@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > Alex,
> > > > > >
> > > > > > Just to be clear, I
> am following
> > the
> > > steps
> > > > from here
> > > > > to try
> > > > > > and setup a
> > > > > > docker container.
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959648328&sdata=W9%2B3T2XDDiDXUDWXYBWV4DYLYZlsJGcfhnhD2hXzTh0%3D&reserved=0
> > > > > >
> > > > > > Is this doc up to
> date?
> > > > > >
> > > > > > Thanks,
> > > > > > Om
> > > > > >
> > > > > > On Wed, Feb 6, 2019
> at 12:02 PM
> > > OmPrakash
> > > > Muppirala <
> > > > > > bigosmallm@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > One approach is to
> have each step
> > > in the
> > > > process
> > > > > spin up a
> > > > > > docker image.
> > > > > > > And use
> docker-compose to run
> > each
> > > > step. All the
> > > > > images can
> > > > > > be made to
> > > > > > > share a common
> volume where all
> > the
> > > > artifacts are
> > > > > stored
> > > > > > across steps.
> > > > > > >
> > > > > > > You are right
> about the
> > networking
> > > issue
> > > > though.
> > > > > Any
> > > > > > network related
> > > > > > > failure that
> occurs on the host
> > > machine
> > > > will most
> > > > > likely
> > > > > > occur in the
> > > > > > > docker container.
> Although, I am
> > > not
> > > > clear how we
> > > > > can
> > > > > > guarantee that the
> > > > > > > same issues will
> not occur on the
> > > > Jenkins server.
> > > > > I mean,
> > > > > > what is special
> > > > > > > about the Jenkins
> server that
> > > makes it
> > > > immune to
> > > > > these
> > > > > > networking issues?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Om
> > > > > > >
> > > > > > > On Wed, Feb 6,
> 2019 at 11:48 AM
> > > Alex
> > > > Harui
> > > > > > <ah...@adobe.com.invalid>
> > > > > > > wrote:
> > > > > > >
> > > > > > >> Again, I don't
> know anything
> > about
> > > > Docker, but
> > > > > before we
> > > > > > spend a lot of
> > > > > > >> time on Docker, I
> also want to
> > > point
> > > > out that the
> > > > > process
> > > > > > to create a
> > > > > > >> release cannot
> really be thought
> > > of as
> > > > "one
> > > > > application".
> > > > > > It will be a
> > > > > > >> series of "steps"
> to run. How
> > > many
> > > > steps
> > > > > depends on
> > > > > > whether we think we
> > > > > > >> can isolate
> enough stuff via
> > > Docker to
> > > > be able to
> > > > > run
> > > > > > Docker on the RM's
> > > > > > >> computer instead
> of some shared
> > > > computer. On a
> > > > > shared
> > > > > > computer there will
> > > > > > >> be dozens of
> steps because the
> > RM
> > > will
> > > > need to
> > > > > enter
> > > > > > passwords to commit
> > > > > > >> stuff. On a
> local computer I
> > > guess the
> > > > RM can
> > > > > supply
> > > > > > passwords but I think
> > > > > > >> there will be
> stopping points
> > > where the
> > > > Maven
> > > > > artifacts are
> > > > > > deployed and
> > > > > > >> the staging repo
> is closed, and
> > > another
> > > > stopping
> > > > > point for
> > > > > > the vote. It
> > > > > > >> seems like Docker
> works by
> > > downloading
> > > > > dependencies. Given
> > > > > > that the
> > > > > > >> problem the RMs
> had last time
> > > involved
> > > > downloads
> > > > > and
> > > > > > uploads, why do we
> > > > > > >> think Docker will
> really solve
> > > this for
> > > > creating
> > > > > releases
> > > > > > on local machines?
> > > > > > >>
> > > > > > >> The reason to do
> this on a
> > shared
> > > > machine is so
> > > > > that new
> > > > > > RMs don't have
> > > > > > >> to do as much
> setup. But then I
> > > wonder
> > > > about the
> > > > > > efficiency of kicking off
> > > > > > >> that many Docker
> images.
> > Jenkins
> > > can
> > > > manage that
> > > > > already.
> > > > > > Does Docker
> > > > > > >> have some sort of
> similar
> > > Dashboard or
> > > > would we
> > > > > use Jenkins
> > > > > > to kick off
> > > > > > >> Docker steps? I
> can't quite
> > > picture
> > > > what is the
> > > > > outermost
> > > > > > >> control/dashboard.
> > > > > > >>
> > > > > > >> -Alex
> > > > > > >>
> > > > > > >> On 2/6/19, 11:03
> AM, "Harbs" <
> > > > > harbs.lists@gmail.com> wrote:
> > > > > > >>
> > > > > > >> A quick
> search turns up
> > this:
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959648328&sdata=cg4RjT3Tb9nBspx0dWR1ENPGiSrOk4ooKpQK8vmatLs%3D&reserved=0
> > > > > > >> <
> > > > > > >>
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959648328&sdata=cg4RjT3Tb9nBspx0dWR1ENPGiSrOk4ooKpQK8vmatLs%3D&reserved=0
> > > > > > >> >
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959648328&sdata=9UnncgpaERA7ATYkT8zcyEzqgmV4%2FqxzpFXcXZVY%2BhE%3D&reserved=0
> > > > > > >> <
> > > > > > >>
> > > > > >
> > > > >
> > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959653317&sdata=Ta36Y8PPxHJauVKuQui74a0Mm5WyfGSTKZeK2g09gHI%3D&reserved=0
> > > > > > >> >
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959653317&sdata=4bvIekmv9Gv%2Fim0qWdiPNJpSm5r3Tb3H6dlX%2Buassuc%3D&reserved=0
> > > > > > >> <
> > > > > > >>
> > > > > >
> > > > >
> > > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959653317&sdata=4bvIekmv9Gv%2Fim0qWdiPNJpSm5r3Tb3H6dlX%2Buassuc%3D&reserved=0
> > > > > > >> >
> > > > > > >>
> > > > > > >> > On Feb 6,
> 2019, at 8:59
> > PM,
> > > Alex
> > > > Harui
> > > > > > <ah...@adobe.com.INVALID>
> > > > > > >> wrote:
> > > > > > >> >
> > > > > > >> > Thanks for
> volunteering to
> > > try it
> > > > Om. IMO,
> > > > > even more
> > > > > > important
> > > > > > >> than
> Firefox+Flash is
> > > > SomeBrowser+Selenium. We
> > > > > may also
> > > > > > need to run Adobe
> > > > > > >> AIR's adb. We
> could probably
> > > turn off
> > > > the Flash
> > > > > tests or
> > > > > > replace Flash
> > > > > > >> with AIR.
> > > > > > >> >
> > > > > > >> > Thanks,
>
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Mx tests are working locally for me with this last change to ListItemRenderer.
So, the question for everyone is: is there anything else we want to put in before trying to cut a release?
We might need to change the ASDoc app after Greg's last change. We might want to bang on ASDoc for a bit and see if anything major needs fixing before cutting a release.
The only other thing I thought of was trying to upgrade Selenium so we can use a recent FireFox version. Right now we are stuck way back on FF47, but I've also heard that more recent FF versions are less friendly to Flash, so you have to use some other browser to test Flash. That's ok for building the Royale SDK since the Flash tests are run in FlashPlayerDebugger and the JS tests are run in a browser like FF.
I'm tempted to say we should punt the inject_html in modules problem to the next release.
I will be adding more details to https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
But there should be enough there to get an RC out for vote.
Thanks,
-Alex
On 6/17/19, 11:06 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
I just saw ASDoc work well enough for me to start with mx.binding.BindabilityInfo and switch to mx.charts.AxisRenderer.
There might be JSON parsing issues with other classes. Run the bin/js-debug version, check the console if things don't load and see what file failed to load and why.
I will take a look at MXTests next.
-Alex
On 6/17/19, 8:08 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
ASDoc is not fully working for me. I've been working on that the past several days. It took quite a while to fix the JSON output from new and interesting ASDoc patterns. I'm now looking into failures due to changes in coercion rules in the JS output. ASDoc was trying to save time by using plain objects that were isomorphic to a class instead of actual class instances.
MXTests are failing on the CI server and probably locally but I haven't gotten that far.
I would think we want these things to work, but you are the RM so it is up to you. Volunteers are welcome to help with these and other tasks.
-Alex
On 6/17/19, 12:44 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Hi Alex,
I don't see any answer here - can I start with trying your instruction and
start release ?
Thanks,
Piotr
śr., 12 cze 2019 o 10:12 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Alex,
> just build from scratch right now and seems maven and ant was ok
>
> El mié., 12 jun. 2019 a las 10:02, Alex Harui (<ah...@adobe.com.invalid>)
> escribió:
>
> > The merge is complete, and the main builds seem to be successful, except
> > for Maven on royale-asjs which was failing before the merge.
> >
> > I'm still catching up on other things, but I think there are some bugs we
> > need to fix before cutting the release? I think ASDoc may not be fully
> > working? What else?
> >
> > -Alex
> >
> > On 6/10/19, 11:05 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
> >
> > Hi Alex,
> >
> > Many thanks for that! I will try to be RM. I will have some dedicated
> > time
> > for that. I will wait for your instruction and merge to develop.
> >
> > Thanks,
> > Piotr
> >
> >
> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui <ah...@adobe.com.invalid>
> > wrote:
> >
> > > Well, that turned out to be much more time-consuming than I
> > expected, but
> > > we can now create identical release artifacts on Mac and Win. I am
> > hopeful
> > > this effort will pay off not only now in having other folks
> generate
> > > releases, but also in the future if signed binaries become a
> > requirement.
> > >
> > > There continues to be a lot of distractions in my life that can
> cause
> > > delays, but I hope to merge the release_practice branches into
> > develop over
> > > the next day or two and figure out where in the wiki to document
> the
> > > release process. So, now is the time for one or more people to
> step
> > up to
> > > be the RMs for 0.9.6 and help debug and improve the process.
> > >
> > > I am going to try very hard not to "own" the process. If something
> > goes
> > > wrong, I am going to ask others to try to debug and fix it first
> > because it
> > > is in the project's best interests for others to truly understand
> > how this
> > > stuff works.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> > >
> > > It has turned out to be harder than expected to get the same
> > binaries
> > > on Mac and Win. I now have the identical binaries for
> > royale-compiler and
> > > royale-typedefs Maven artifacts and am starting on royale-asjs. I
> > might
> > > get lucky and the changes that fixed royale-typedefs SWCs will
> > magically
> > > get the royale-asjs SWCs to match. Then we have to make the Ant
> > artifacts
> > > match.
> > >
> > > There have been a lot of distractions in my non-work life which
> > has
> > > also impeded progress. I hope to make much progress this coming
> > week and
> > > if we're lucky, I will be asking for a volunteer (or volunteers) to
> > test
> > > drive all of this stuff and be the RM for 0.9.6. I am not going to
> > be the
> > > RM.
> > >
> > > -Alex
> > >
> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com
> > >
> > > wrote:
> > >
> > > Hi Alex,
> > >
> > > It's been a while since you have started effort with
> > automating
> > > build.
> > > Where are you with that ? Are we closer to started 0.9.6.
> Do
> > you
> > > need any
> > > help with this ?
> > >
> > > Thanks,
> > > Piotr
> > >
> > > wt., 2 kwi 2019 o 19:30 Alex Harui
> <aharui@adobe.com.invalid
> > >
> > > napisał(a):
> > >
> > > > Update:
> > > >
> > > > In order to make verification of binary release packages
> > created
> > > on the
> > > > server easier, I have made changes to our build scripts
> and
> > > tools to try to
> > > > generate reproducible binaries. I've seen two different
> > builds
> > > compare on
> > > > my Mac. The next challenge will be to see if the server
> > can
> > > build a
> > > > package on Windows that will compare on Mac.
> > > >
> > > > One of the changes I needed to make is to JBurg. The
> > version of
> > > JBurg we
> > > > use generates method names including a hash that doesn't
> > > reproduce the same
> > > > name each time. I have changes to JBurg ready, however
> > JBurg is
> > > currently
> > > > under CPL which is category B. We only need one file, we
> > don't
> > > need or
> > > > want all of JBurg at this time. The one JBurg file is
> > jointly
> > > owned by
> > > > Adobe and Tom Harwood. I've contact Tom and he will be
> > filing
> > > an ICLA and
> > > > has given me permission to commit the lines he owns in
> > that one
> > > file.
> > > >
> > > > This is the revision of the file that will be donated by
> > > Tom/Adobe.
> > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959643335&sdata=ZYf5QUAPr%2BNKndH9vr8pI7TeTAWX1hxLMV%2FyKb1U0g4%3D&reserved=0
> > > >
> > > > Once this file goes in with the changes to keep the
> method
> > names
> > > the same,
> > > > there will be more tweaks to the release tasks and then
> we
> > can
> > > try cutting
> > > > a release. I'm thinking we'll be at that point in early
> > May, so
> > > now is the
> > > > time to get stuff in for the 0.9.6 release.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com>
> wrote:
> > > >
> > > > I would much rather have others find and fix issues
> > > themselves. That
> > > > way, more people than just me will know how to maintain
> the
> > > system. It
> > > > actually turns out that, IMO, a group of people can work
> > on the
> > > release.
> > > > There are 14 steps. Literally, 14 different people could
> > > execute one step
> > > > each.
> > > >
> > > > My 2 cents,
> > > > -Alex
> > > >
> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > > wrote:
> > > >
> > > > Hi Alex,
> > > >
> > > > amazing work! congrats to reach to this point! :)
> > > >
> > > > I need to put my head on all of this, but count
> on
> > me to
> > > be a RM.
> > > > I think
> > > > the best thing should be that you be the first RM
> > to try
> > > your own
> > > > development at least for the first time, and then
> > the
> > > rest of us
> > > > will
> > > > follow you on the next releases. With all this on
> > place
> > > we maybe
> > > > could
> > > > release once a month or every two months...
> > > >
> > > > Thanks for doing this :)
> > > >
> > > > Carlos
> > > >
> > > >
> > > > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > > > (<ah...@adobe.com.invalid>)
> > > > escribió:
> > > >
> > > > > OK, I've now seen Jenkins perform the steps to
> > build
> > > the release
> > > > > artifacts. Folks interested in Docker-izing
> the
> > steps
> > > are
> > > > welcome to look
> > > > > at the jobs on the "Royale Release" tab on the
> CI
> > > server.
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959643335&sdata=tCcelcUXdJFddO5EtAM3or35OvY1W55uN0axY%2FJRIcI%3D&reserved=0
> > > > >
> > > > > These steps assume that the RM can run the
> basic
> > Maven
> > > and Ant
> > > > build on
> > > > > the RM's computer. I think that's a fair
> > requirement
> > > since all
> > > > of us on the
> > > > > PMC need to able to do that to build the RC in
> > order
> > > to vote on
> > > > it.
> > > > > Jenkins does other tasks like run the Maven
> > release
> > > plugin
> > > > steps.
> > > > >
> > > > > Currently that results in binaries on Jenkins
> > that are
> > > > downloaded to the
> > > > > RM's computer. These binaries need to be
> > verified by
> > > the RM
> > > > which is the
> > > > > next phase I will be starting on now. The RM
> > verifies
> > > the bits
> > > > and then
> > > > > PGP signs them. And then the bits are uploaded
> > off
> > > the RM's
> > > > computer to
> > > > > Maven Staging or dist.a.o/dev. If that
> > uploading
> > > turns out to
> > > > be a point
> > > > > of failure, we have the option of having
> Jenkins
> > > upload the big
> > > > files and
> > > > > have the RM only upload PGP signature files.
> Or
> > > finding a way
> > > > for Jenkins
> > > > > to get the signature files from the RM. The
> > uploads
> > > worked fine
> > > > for me,
> > > > > but then again, so did the old script's
> uploads.
> > > > >
> > > > > Therefore, once I get the binary verification
> > phase
> > > completed, I
> > > > think
> > > > > someone other than me should be the RM and try
> > to use
> > > these
> > > > steps to
> > > > > generate the release and help debug the process
> > for
> > > the next
> > > > RM. So,
> > > > > please try to carve out some time to be the RM.
> > One
> > > advantage
> > > > of doing
> > > > > most of the work on Jenkins is that it frees up
> > my
> > > computer to
> > > > do other
> > > > > things while Jenkins is cranking away.
> > > > >
> > > > > I think we're at least a week away from binary
> > > verification,
> > > > maybe two, so
> > > > > it is time to start thinking about what is
> going
> > in
> > > this release.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
> > > <ah...@adobe.com.INVALID>
> > > > wrote:
> > > > >
> > > > > In case you haven't guessed, I'm testing
> out
> > > Jenkins and its
> > > > ability
> > > > > to create the artifacts and send emails.
> Please
> > > ignore any
> > > > email that
> > > > > looks like a vote or discuss thread.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 2/10/19, 8:44 PM, "Alex Harui"
> > > <ah...@adobe.com.INVALID>
> > > > wrote:
> > > > >
> > > > > Om,
> > > > >
> > > > > Well, that's what I used for the last
> > > release. I'm sure
> > > > there is
> > > > > probably some inaccuracy in it.
> > > > >
> > > > > That said, I'm abandoning that document
> > and
> > > taking a new
> > > > angle
> > > > > because that document presumed that the release
> > > manager was
> > > > trying to
> > > > > create a release on his/her computer. I've
> > given up
> > > on that and
> > > > working on
> > > > > making releases from a shared computer for the
> > reasons
> > > I've
> > > > stated
> > > > > upthread. I hope to make some progress on that
> > this
> > > week.
> > > > >
> > > > > The key difference is that the new
> angle
> > does
> > > not
> > > > presume that you
> > > > > have Git SSH and PGP signatures all set up on
> > some
> > > computer. I
> > > > have not
> > > > > looked into how Docker would handle that. You
> > > certainly
> > > > wouldn't want the
> > > > > Docker image to contain your SSH or PGP
> > keys/creds.
> > > And if the
> > > > Docker
> > > > > image doesn't, then that is another stumbling
> > block
> > > for future
> > > > RMs.
> > > > >
> > > > > The other key difference is that the
> old
> > > script presumed
> > > > you could
> > > > > create the 3 release in 3 huge "easy" steps.
> > We've
> > > seen that is
> > > > only true
> > > > > for me. So the new angle creates many discrete
> > steps
> > > managed by
> > > > Jenkins.
> > > > >
> > > > > So, it is up to you to decide what you
> > want to
> > > > "Docker-ize". You
> > > > > can try to Docker-ize the current 3 big steps,
> > so RMs
> > > can try to
> > > > run it on
> > > > > their systems, but I'd bet they will just faiI
> > due to
> > > network
> > > > issues. I
> > > > > would be interested in using Docker to make
> each
> > of
> > > these many
> > > > discrete
> > > > > steps portable to another server. I'm not
> > going to
> > > involve
> > > > Docker at this
> > > > > point. My main goal is just to see if I can
> > create a
> > > workflow
> > > > of many
> > > > > discrete steps that isn't horribly painful.
> > Once we
> > > see what
> > > > these steps
> > > > > turn out to be, then we can worry about server
> > > portability of
> > > > those steps.
> > > > >
> > > > > Either way, we want to know about
> running
> > > > Browser+Selenium for
> > > > > sure. And maybe FlashPlayerDebugger or AIR. I
> > would
> > > want to
> > > > know, for
> > > > > example, how you debug a failing checkintest
> in a
> > > Docker
> > > > container.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > >
> > > > > On 2/10/19, 5:18 PM, "OmPrakash
> > Muppirala" <
> > > > bigosmallm@gmail.com>
> > > > > wrote:
> > > > >
> > > > > Alex,
> > > > >
> > > > > Just to be clear, I am following
> the
> > steps
> > > from here
> > > > to try
> > > > > and setup a
> > > > > docker container.
> > > > >
> > > > >
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959648328&sdata=W9%2B3T2XDDiDXUDWXYBWV4DYLYZlsJGcfhnhD2hXzTh0%3D&reserved=0
> > > > >
> > > > > Is this doc up to date?
> > > > >
> > > > > Thanks,
> > > > > Om
> > > > >
> > > > > On Wed, Feb 6, 2019 at 12:02 PM
> > OmPrakash
> > > Muppirala <
> > > > > bigosmallm@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > One approach is to have each step
> > in the
> > > process
> > > > spin up a
> > > > > docker image.
> > > > > > And use docker-compose to run
> each
> > > step. All the
> > > > images can
> > > > > be made to
> > > > > > share a common volume where all
> the
> > > artifacts are
> > > > stored
> > > > > across steps.
> > > > > >
> > > > > > You are right about the
> networking
> > issue
> > > though.
> > > > Any
> > > > > network related
> > > > > > failure that occurs on the host
> > machine
> > > will most
> > > > likely
> > > > > occur in the
> > > > > > docker container. Although, I am
> > not
> > > clear how we
> > > > can
> > > > > guarantee that the
> > > > > > same issues will not occur on the
> > > Jenkins server.
> > > > I mean,
> > > > > what is special
> > > > > > about the Jenkins server that
> > makes it
> > > immune to
> > > > these
> > > > > networking issues?
> > > > > >
> > > > > > Thanks,
> > > > > > Om
> > > > > >
> > > > > > On Wed, Feb 6, 2019 at 11:48 AM
> > Alex
> > > Harui
> > > > > <ah...@adobe.com.invalid>
> > > > > > wrote:
> > > > > >
> > > > > >> Again, I don't know anything
> about
> > > Docker, but
> > > > before we
> > > > > spend a lot of
> > > > > >> time on Docker, I also want to
> > point
> > > out that the
> > > > process
> > > > > to create a
> > > > > >> release cannot really be thought
> > of as
> > > "one
> > > > application".
> > > > > It will be a
> > > > > >> series of "steps" to run. How
> > many
> > > steps
> > > > depends on
> > > > > whether we think we
> > > > > >> can isolate enough stuff via
> > Docker to
> > > be able to
> > > > run
> > > > > Docker on the RM's
> > > > > >> computer instead of some shared
> > > computer. On a
> > > > shared
> > > > > computer there will
> > > > > >> be dozens of steps because the
> RM
> > will
> > > need to
> > > > enter
> > > > > passwords to commit
> > > > > >> stuff. On a local computer I
> > guess the
> > > RM can
> > > > supply
> > > > > passwords but I think
> > > > > >> there will be stopping points
> > where the
> > > Maven
> > > > artifacts are
> > > > > deployed and
> > > > > >> the staging repo is closed, and
> > another
> > > stopping
> > > > point for
> > > > > the vote. It
> > > > > >> seems like Docker works by
> > downloading
> > > > dependencies. Given
> > > > > that the
> > > > > >> problem the RMs had last time
> > involved
> > > downloads
> > > > and
> > > > > uploads, why do we
> > > > > >> think Docker will really solve
> > this for
> > > creating
> > > > releases
> > > > > on local machines?
> > > > > >>
> > > > > >> The reason to do this on a
> shared
> > > machine is so
> > > > that new
> > > > > RMs don't have
> > > > > >> to do as much setup. But then I
> > wonder
> > > about the
> > > > > efficiency of kicking off
> > > > > >> that many Docker images.
> Jenkins
> > can
> > > manage that
> > > > already.
> > > > > Does Docker
> > > > > >> have some sort of similar
> > Dashboard or
> > > would we
> > > > use Jenkins
> > > > > to kick off
> > > > > >> Docker steps? I can't quite
> > picture
> > > what is the
> > > > outermost
> > > > > >> control/dashboard.
> > > > > >>
> > > > > >> -Alex
> > > > > >>
> > > > > >> On 2/6/19, 11:03 AM, "Harbs" <
> > > > harbs.lists@gmail.com> wrote:
> > > > > >>
> > > > > >> A quick search turns up
> this:
> > > > > >>
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959648328&sdata=cg4RjT3Tb9nBspx0dWR1ENPGiSrOk4ooKpQK8vmatLs%3D&reserved=0
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959648328&sdata=cg4RjT3Tb9nBspx0dWR1ENPGiSrOk4ooKpQK8vmatLs%3D&reserved=0
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959648328&sdata=9UnncgpaERA7ATYkT8zcyEzqgmV4%2FqxzpFXcXZVY%2BhE%3D&reserved=0
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959653317&sdata=Ta36Y8PPxHJauVKuQui74a0Mm5WyfGSTKZeK2g09gHI%3D&reserved=0
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959653317&sdata=4bvIekmv9Gv%2Fim0qWdiPNJpSm5r3Tb3H6dlX%2Buassuc%3D&reserved=0
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959653317&sdata=4bvIekmv9Gv%2Fim0qWdiPNJpSm5r3Tb3H6dlX%2Buassuc%3D&reserved=0
> > > > > >> >
> > > > > >>
> > > > > >> > On Feb 6, 2019, at 8:59
> PM,
> > Alex
> > > Harui
> > > > > <ah...@adobe.com.INVALID>
> > > > > >> wrote:
> > > > > >> >
> > > > > >> > Thanks for volunteering to
> > try it
> > > Om. IMO,
> > > > even more
> > > > > important
> > > > > >> than Firefox+Flash is
> > > SomeBrowser+Selenium. We
> > > > may also
> > > > > need to run Adobe
> > > > > >> AIR's adb. We could probably
> > turn off
> > > the Flash
> > > > tests or
> > > > > replace Flash
> > > > > >> with AIR.
> > > > > >> >
> > > > > >> > Thanks,
> > > > > >> > -Alex
> > > > > >> >
> > > > > >> > On 2/6/19, 10:54 AM,
> "Carlos
> > > Rovira" <
> > > > > carlosrovira@apache.org>
> > > > > >> wrote:
> > > > > >> >
> > > > > >> > Hi Om, that would be
> > great!
> > > waiting for
> > > > your
> > > > > experience with a
> > > > > >> that! :)
> > > > > >> >
> > > > > >> > El mié., 6 feb. 2019 a
> > las
> > > 19:31,
> > > > OmPrakash
> > > > > Muppirala (<
> > > > > >> bigosmallm@gmail.com>)
> > > > > >> > escribió:
> > > > > >> >
> > > > > >> >> Yes, I agree with Alex
> > about not
> > > being
> > > > able to run
> > > > > UI out of docker
> > > > > >> >> containers. I never
> > thought of
> > > the
> > > > checkintests
> > > > > when I made the
> > > > > >> >> suggestion.
> > > > > >> >>
> > > > > >> >> The firefox-flash image
> > that
> > > Yishay
> > > > pointed out
> > > > > looks promising.
> > > > > >> I will
> > > > > >> >> poke around with it and
> > see if
> > > that works
> > > > for us.
> > > > > >> >>
> > > > > >> >> Thanks,
> > > > > >> >> Om
> > > > > >> >>
> > > > > >> >> On Wed, Feb 6, 2019 at
> > 12:41 AM
> > > Yishay
> > > > Weiss <
> > > > > >> yishayjobs@hotmail.com>
> > > > > >> >> wrote:
> > > > > >> >>
> > > > > >> >>> I’ll let Om or someone
> > else
> > > with docker
> > > > experience
> > > > > tell us if
> > > > > >> this [1] is
> > > > > >> >>> relevant.
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>> [1]
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959653317&sdata=HTKG6mLMu8t2zQ29Tq5N70SJbMop%2BudxX6m0SuHJ2Fo%3D&reserved=0
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > ________________________________
> > > > > >> >>> From: Alex Harui
> > > <aharui@adobe.com.INVALID
> > > > >
> > > > > >> >>> Sent: Wednesday,
> February
> > 6,
> > > 2019
> > > > 10:05:54 AM
> > > > > >> >>> To:
> dev@royale.apache.org
> > > > > >> >>> Subject: Re: 0.9.6
> Release
> > > > > >> >>>
> > > > > >> >>> I don't anything about
> > docker,
> > > but in 15
> > > > minutes of
> > > > > reading I ran
> > > > > >> into
> > > > > >> >>> this:
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959653317&sdata=SNgNYUt8byTT2HDDLSkHqZ5%2BLzlc7s648%2BH3tmh4rJo%3D&reserved=0
> > > > > >> >>>
> > > > > >> >>> Which says: Docker can't
> > " Run
> > > > applications with
> > > > > graphical
> > > > > >> interfaces".
> > > > > >> >>> If you want Royale to
> use
> > > Docker for
> > > > releases, show
> > > > > that it can
> > > > > >> run
> > > > > >> >>> checkintests with Flash
> > and the
> > > Browser.
> > > > Then I
> > > > > will look into
> > > > > >> it more.
> > > > > >> >>>
> > > > > >> >>> The highest level goal
> is
> > to
> > > make it as
> > > > easy as
> > > > > possible for
> > > > > >> someone to
> > > > > >> >>> volunteer to be an RM.
> > Any
> > > requirement
> > > > of "install
> > > > > this (Docker,
> > > > > >> etc) on
> > > > > >> >>> your computer" is, IMO,
> > another
> > > barrier
> > > > to entry.
> > > > > Yeah, RMs will
> > > > > >> have to
> > > > > >> >>> have Maven installed and
> > maybe
> > > Ant, but
> > > > you should
> > > > > already have
> > > > > >> those
> > > > > >> >>> installed to be a
> > committer/PMC
> > > member.
> > > > > >> >>>
> > > > > >> >>> That said, a good
> > takeaway from
> > > the
> > > > Docker idea is
> > > > > to try to find
> > > > > >> a way
> > > > > >> >> to
> > > > > >> >>> make an "Image" of
> > whatever we
> > > end up
> > > > with on
> > > > > whatever server we
> > > > > >> end up
> > > > > >> >>> using so if the image
> can
> > be
> > > copied and
> > > > used on
> > > > > other servers.
> > > > > >> I'm not
> > > > > >> >>> exactly sure how to do
> > that
> > > with Azure,
> > > > which hosts
> > > > > my CI
> > > > > >> server. I will
> > > > > >> >>> spend a few more minutes
> > > researching that.
> > > > > >> >>>
> > > > > >> >>> I could not quickly find
> > any
> > > way to get a
> > > > free VM
> > > > > on Azure or AWS
> > > > > >> that
> > > > > >> >>> isn't a
> > > > free-trial-start-paying-after-a-year. So,
> > > > > unless someone
> > > > > >> comes
> > > > > >> >> up
> > > > > >> >>> with a free server we
> can
> > use
> > > "forever",
> > > > I'm going
> > > > > to just start
> > > > > >> with my
> > > > > >> >>> Azure VM.
> > > > > >> >>>
> > > > > >> >>> -Alex
> > > > > >> >>>
> > > > > >> >>> On 2/5/19, 10:59 PM,
> > "Carlos
> > > Rovira" <
> > > > > carlosrovira@apache.org>
> > > > > >> wrote:
> > > > > >> >>>
> > > > > >> >>> Hi.
> > > > > >> >>>
> > > > > >> >>> the plan sounds very
> > good to
> > > me. Just
> > > > my 2
> > > > > thoughts on this:
> > > > > >> >>>
> > > > > >> >>> 1.- As I was reading
> I
> > was
> > > thinking as
> > > > well on
> > > > > something like
> > > > > >> Docker
> > > > > >> >>> and
> > > > > >> >>> see Om as well
> > thinking on
> > > the same.
> > > > Maybe is
> > > > > the way to this
> > > > > >> with
> > > > > >> >> the
> > > > > >> >>> actual technology.
> > Seems VMs
> > > are
> > > > stepping out a
> > > > > bit this days
> > > > > >> in
> > > > > >> >> favor
> > > > > >> >>> of
> > > > > >> >>> things like Docker.
> > Maybe
> > > the same did
> > > > Git over
> > > > > Svn, and today
> > > > > >> Svn is
> > > > > >> >>> an
> > > > > >> >>> old remembrance. I
> > must say
> > > that I
> > > > have no
> > > > > experience with
> > > > > >> Docker, so
> > > > > >> >>> doing
> > > > > >> >>> that will require
> > acquire
> > > that
> > > > knowledge, but
> > > > > seems it could
> > > > > >> be worth
> > > > > >> >>> it.
> > > > > >> >>>
> > > > > >> >>> 2.- Maybe is not
> > possible,
> > > but I want
> > > > to propose
> > > > > to do this
> > > > > >> work I a
> > > > > >> >>> separate branch, so
> it
> > could
> > > be in
> > > > parallel to
> > > > > other
> > > > > >> developments. I
> > > > > >> >>> think
> > > > > >> >>> work over develop is
> > > practical if
> > > > there's
> > > > > something tiny that
> > > > > >> could
> > > > > >> >> be
> > > > > >> >>> done
> > > > > >> >>> in a commit. But as
> we
> > need
> > > more than
> > > > one, or is
> > > > > a long
> > > > > >> process (like
> > > > > >> >>> this), chances are to
> > make
> > > develop
> > > > branch
> > > > > unstable and even
> > > > > >> for some
> > > > > >> >>> days.
> > > > > >> >>> I think we should try
> > to
> > > avoid that
> > > > scenario,
> > > > > and branches are
> > > > > >> the
> > > > > >> >> best
> > > > > >> >>> way. If we do this
> way,
> > > we'll benefit
> > > > of more
> > > > > reliable develop
> > > > > >> >> branch.
> > > > > >> >>>
> > > > > >> >>> Thanks and good to
> > know of
> > > this plan :)
> > > > > >> >>>
> > > > > >> >>> Carlos
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>> El mar., 5 feb. 2019
> a
> > las
> > > 23:19,
> > > > Harbs (<
> > > > > >> harbs.lists@gmail.com>)
> > > > > >> >>> escribió:
> > > > > >> >>>
> > > > > >> >>>> I’ve never used Docker
> > myself,
> > > but that
> > > > might be a
> > > > > good plan.
> > > > > >> >>>>
> > > > > >> >>>>> On Feb 6, 2019, at
> > 12:07 AM,
> > > OmPrakash
> > > > Muppirala <
> > > > > >> >>> bigosmallm@gmail.com>
> > > > > >> >>>> wrote:
> > > > > >> >>>>>
> > > > > >> >>>>> I was wondering if we
> > can use
> > > docker
> > > > images to
> > > > > setup and seal
> > > > > >> the
> > > > > >> >>> RM
> > > > > >> >>>>> environment. Then
> > other RMs
> > > simply
> > > > need to run
> > > > > the image
> > > > > >> locally
> > > > > >> >>> and run
> > > > > >> >>>>> the release scripts.
> > Might
> > > be easier.
> > > > If folks
> > > > > like this plan,
> > > > > >> >> I
> > > > > >> >>> can
> > > > > >> >>>> try
> > > > > >> >>>>> to put something
> > together.
> > > > > >> >>>>>
> > > > > >> >>>>> Thanks,
> > > > > >> >>>>> Om
> > > > > >> >>>>>
> > > > > >> >>>>> On Tue, Feb 5, 2019 at
> > 1:40
> > > PM Harbs <
> > > > > harbs.lists@gmail.com>
> > > > > >> >>> wrote:
> > > > > >> >>>>>
> > > > > >> >>>>>> In a recent
> > discussion, it
> > > looks like
> > > > other
> > > > > projects have
> > > > > >> gotten
> > > > > >> >>>> resources
> > > > > >> >>>>>> from AWS.
> > > > > >> >>>>>>
> > > > > >> >>>>>> Whatever service we
> > use,
> > > could setup a
> > > > “shared”
> > > > > Royale account
> > > > > >> >>> that all
> > > > > >> >>>>>> PMC members could
> have
> > > access to.
> > > > > >> >>>>>>
> > > > > >> >>>>>> I don’t know if
> > there’s some
> > > way we
> > > > could
> > > > > leverage Gitlab’s
> > > > > >> >>> integration
> > > > > >> >>>>>> pipelines
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959658308&sdata=KUaBhPrja6mINJQE%2BEWBUR12uX2dYWmWh2X%2FEoGyqgo%3D&reserved=0
> > > > > >> >>> <
> > > > > >> >>>>>>
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959658308&sdata=KUaBhPrja6mINJQE%2BEWBUR12uX2dYWmWh2X%2FEoGyqgo%3D&reserved=0
> > > > > >> >>>>
> > > > > >> >>>>>>
> > > > > >> >>>>>>> On Feb 5, 2019, at
> > 11:33
> > > PM, Alex
> > > > Harui
> > > > > >> >> <aharui@adobe.com.INVALID
> > > > > >> >>>>
> > > > > >> >>>>>> wrote:
> > > > > >> >>>>>>>
> > > > > >> >>>>>>> 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" <
> > > > > >> >>
> piotrzarzycki21@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.lists@gmail.com
> > > > > >> >>> wrote:
> > > > > >> >>>>>>>
> > > > > >> >>>>>>>> A big +1 from me!
> > > > > >> >>>>>>>>
> > > > > >> >>>>>>>> Looking forward!
> > > > > >> >>>>>>>>
> > > > > >> >>>>>>>>> On Feb 5, 2019, at
> > 9:34
> > > PM, Alex
> > > > Harui
> > > > > >> >>>
> <aharui@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
> > > > >
> >
> >
> >
>
> --
> Carlos Rovira
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959658308&sdata=7tpQiMiwqrQbklQfVIJMytD9eUuHzJuGbGUC9PfdA1U%3D&reserved=0
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959658308&sdata=pQ%2BXkY1758p%2BRc3kL2ojQzfmhk1Gbvsfn%2B8Dr%2BUQ1jo%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C2e85c48a75964c54aadd08d6f34e8829%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963915959663298&sdata=eEkKEchptyOdNR2UvNtCnAoZEpA0WWyYCP3BYLg%2FTeQ%3D&reserved=0>*
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I just saw ASDoc work well enough for me to start with mx.binding.BindabilityInfo and switch to mx.charts.AxisRenderer.
There might be JSON parsing issues with other classes. Run the bin/js-debug version, check the console if things don't load and see what file failed to load and why.
I will take a look at MXTests next.
-Alex
On 6/17/19, 8:08 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
ASDoc is not fully working for me. I've been working on that the past several days. It took quite a while to fix the JSON output from new and interesting ASDoc patterns. I'm now looking into failures due to changes in coercion rules in the JS output. ASDoc was trying to save time by using plain objects that were isomorphic to a class instead of actual class instances.
MXTests are failing on the CI server and probably locally but I haven't gotten that far.
I would think we want these things to work, but you are the RM so it is up to you. Volunteers are welcome to help with these and other tasks.
-Alex
On 6/17/19, 12:44 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Hi Alex,
I don't see any answer here - can I start with trying your instruction and
start release ?
Thanks,
Piotr
śr., 12 cze 2019 o 10:12 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Alex,
> just build from scratch right now and seems maven and ant was ok
>
> El mié., 12 jun. 2019 a las 10:02, Alex Harui (<ah...@adobe.com.invalid>)
> escribió:
>
> > The merge is complete, and the main builds seem to be successful, except
> > for Maven on royale-asjs which was failing before the merge.
> >
> > I'm still catching up on other things, but I think there are some bugs we
> > need to fix before cutting the release? I think ASDoc may not be fully
> > working? What else?
> >
> > -Alex
> >
> > On 6/10/19, 11:05 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
> >
> > Hi Alex,
> >
> > Many thanks for that! I will try to be RM. I will have some dedicated
> > time
> > for that. I will wait for your instruction and merge to develop.
> >
> > Thanks,
> > Piotr
> >
> >
> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui <ah...@adobe.com.invalid>
> > wrote:
> >
> > > Well, that turned out to be much more time-consuming than I
> > expected, but
> > > we can now create identical release artifacts on Mac and Win. I am
> > hopeful
> > > this effort will pay off not only now in having other folks
> generate
> > > releases, but also in the future if signed binaries become a
> > requirement.
> > >
> > > There continues to be a lot of distractions in my life that can
> cause
> > > delays, but I hope to merge the release_practice branches into
> > develop over
> > > the next day or two and figure out where in the wiki to document
> the
> > > release process. So, now is the time for one or more people to
> step
> > up to
> > > be the RMs for 0.9.6 and help debug and improve the process.
> > >
> > > I am going to try very hard not to "own" the process. If something
> > goes
> > > wrong, I am going to ask others to try to debug and fix it first
> > because it
> > > is in the project's best interests for others to truly understand
> > how this
> > > stuff works.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> > >
> > > It has turned out to be harder than expected to get the same
> > binaries
> > > on Mac and Win. I now have the identical binaries for
> > royale-compiler and
> > > royale-typedefs Maven artifacts and am starting on royale-asjs. I
> > might
> > > get lucky and the changes that fixed royale-typedefs SWCs will
> > magically
> > > get the royale-asjs SWCs to match. Then we have to make the Ant
> > artifacts
> > > match.
> > >
> > > There have been a lot of distractions in my non-work life which
> > has
> > > also impeded progress. I hope to make much progress this coming
> > week and
> > > if we're lucky, I will be asking for a volunteer (or volunteers) to
> > test
> > > drive all of this stuff and be the RM for 0.9.6. I am not going to
> > be the
> > > RM.
> > >
> > > -Alex
> > >
> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com
> > >
> > > wrote:
> > >
> > > Hi Alex,
> > >
> > > It's been a while since you have started effort with
> > automating
> > > build.
> > > Where are you with that ? Are we closer to started 0.9.6.
> Do
> > you
> > > need any
> > > help with this ?
> > >
> > > Thanks,
> > > Piotr
> > >
> > > wt., 2 kwi 2019 o 19:30 Alex Harui
> <aharui@adobe.com.invalid
> > >
> > > napisał(a):
> > >
> > > > Update:
> > > >
> > > > In order to make verification of binary release packages
> > created
> > > on the
> > > > server easier, I have made changes to our build scripts
> and
> > > tools to try to
> > > > generate reproducible binaries. I've seen two different
> > builds
> > > compare on
> > > > my Mac. The next challenge will be to see if the server
> > can
> > > build a
> > > > package on Windows that will compare on Mac.
> > > >
> > > > One of the changes I needed to make is to JBurg. The
> > version of
> > > JBurg we
> > > > use generates method names including a hash that doesn't
> > > reproduce the same
> > > > name each time. I have changes to JBurg ready, however
> > JBurg is
> > > currently
> > > > under CPL which is category B. We only need one file, we
> > don't
> > > need or
> > > > want all of JBurg at this time. The one JBurg file is
> > jointly
> > > owned by
> > > > Adobe and Tom Harwood. I've contact Tom and he will be
> > filing
> > > an ICLA and
> > > > has given me permission to commit the lines he owns in
> > that one
> > > file.
> > > >
> > > > This is the revision of the file that will be donated by
> > > Tom/Adobe.
> > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809362999395&sdata=se%2FwjB7phtYMds4U5ouI4muRMf8eBGxaH0GXcda1r70%3D&reserved=0
> > > >
> > > > Once this file goes in with the changes to keep the
> method
> > names
> > > the same,
> > > > there will be more tweaks to the release tasks and then
> we
> > can
> > > try cutting
> > > > a release. I'm thinking we'll be at that point in early
> > May, so
> > > now is the
> > > > time to get stuff in for the 0.9.6 release.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com>
> wrote:
> > > >
> > > > I would much rather have others find and fix issues
> > > themselves. That
> > > > way, more people than just me will know how to maintain
> the
> > > system. It
> > > > actually turns out that, IMO, a group of people can work
> > on the
> > > release.
> > > > There are 14 steps. Literally, 14 different people could
> > > execute one step
> > > > each.
> > > >
> > > > My 2 cents,
> > > > -Alex
> > > >
> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > > wrote:
> > > >
> > > > Hi Alex,
> > > >
> > > > amazing work! congrats to reach to this point! :)
> > > >
> > > > I need to put my head on all of this, but count
> on
> > me to
> > > be a RM.
> > > > I think
> > > > the best thing should be that you be the first RM
> > to try
> > > your own
> > > > development at least for the first time, and then
> > the
> > > rest of us
> > > > will
> > > > follow you on the next releases. With all this on
> > place
> > > we maybe
> > > > could
> > > > release once a month or every two months...
> > > >
> > > > Thanks for doing this :)
> > > >
> > > > Carlos
> > > >
> > > >
> > > > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > > > (<ah...@adobe.com.invalid>)
> > > > escribió:
> > > >
> > > > > OK, I've now seen Jenkins perform the steps to
> > build
> > > the release
> > > > > artifacts. Folks interested in Docker-izing
> the
> > steps
> > > are
> > > > welcome to look
> > > > > at the jobs on the "Royale Release" tab on the
> CI
> > > server.
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363009383&sdata=tml8lYUJKtXtkDOh0SZQQY2x8EyiGSNTCFYjYrVei4M%3D&reserved=0
> > > > >
> > > > > These steps assume that the RM can run the
> basic
> > Maven
> > > and Ant
> > > > build on
> > > > > the RM's computer. I think that's a fair
> > requirement
> > > since all
> > > > of us on the
> > > > > PMC need to able to do that to build the RC in
> > order
> > > to vote on
> > > > it.
> > > > > Jenkins does other tasks like run the Maven
> > release
> > > plugin
> > > > steps.
> > > > >
> > > > > Currently that results in binaries on Jenkins
> > that are
> > > > downloaded to the
> > > > > RM's computer. These binaries need to be
> > verified by
> > > the RM
> > > > which is the
> > > > > next phase I will be starting on now. The RM
> > verifies
> > > the bits
> > > > and then
> > > > > PGP signs them. And then the bits are uploaded
> > off
> > > the RM's
> > > > computer to
> > > > > Maven Staging or dist.a.o/dev. If that
> > uploading
> > > turns out to
> > > > be a point
> > > > > of failure, we have the option of having
> Jenkins
> > > upload the big
> > > > files and
> > > > > have the RM only upload PGP signature files.
> Or
> > > finding a way
> > > > for Jenkins
> > > > > to get the signature files from the RM. The
> > uploads
> > > worked fine
> > > > for me,
> > > > > but then again, so did the old script's
> uploads.
> > > > >
> > > > > Therefore, once I get the binary verification
> > phase
> > > completed, I
> > > > think
> > > > > someone other than me should be the RM and try
> > to use
> > > these
> > > > steps to
> > > > > generate the release and help debug the process
> > for
> > > the next
> > > > RM. So,
> > > > > please try to carve out some time to be the RM.
> > One
> > > advantage
> > > > of doing
> > > > > most of the work on Jenkins is that it frees up
> > my
> > > computer to
> > > > do other
> > > > > things while Jenkins is cranking away.
> > > > >
> > > > > I think we're at least a week away from binary
> > > verification,
> > > > maybe two, so
> > > > > it is time to start thinking about what is
> going
> > in
> > > this release.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
> > > <ah...@adobe.com.INVALID>
> > > > wrote:
> > > > >
> > > > > In case you haven't guessed, I'm testing
> out
> > > Jenkins and its
> > > > ability
> > > > > to create the artifacts and send emails.
> Please
> > > ignore any
> > > > email that
> > > > > looks like a vote or discuss thread.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 2/10/19, 8:44 PM, "Alex Harui"
> > > <ah...@adobe.com.INVALID>
> > > > wrote:
> > > > >
> > > > > Om,
> > > > >
> > > > > Well, that's what I used for the last
> > > release. I'm sure
> > > > there is
> > > > > probably some inaccuracy in it.
> > > > >
> > > > > That said, I'm abandoning that document
> > and
> > > taking a new
> > > > angle
> > > > > because that document presumed that the release
> > > manager was
> > > > trying to
> > > > > create a release on his/her computer. I've
> > given up
> > > on that and
> > > > working on
> > > > > making releases from a shared computer for the
> > reasons
> > > I've
> > > > stated
> > > > > upthread. I hope to make some progress on that
> > this
> > > week.
> > > > >
> > > > > The key difference is that the new
> angle
> > does
> > > not
> > > > presume that you
> > > > > have Git SSH and PGP signatures all set up on
> > some
> > > computer. I
> > > > have not
> > > > > looked into how Docker would handle that. You
> > > certainly
> > > > wouldn't want the
> > > > > Docker image to contain your SSH or PGP
> > keys/creds.
> > > And if the
> > > > Docker
> > > > > image doesn't, then that is another stumbling
> > block
> > > for future
> > > > RMs.
> > > > >
> > > > > The other key difference is that the
> old
> > > script presumed
> > > > you could
> > > > > create the 3 release in 3 huge "easy" steps.
> > We've
> > > seen that is
> > > > only true
> > > > > for me. So the new angle creates many discrete
> > steps
> > > managed by
> > > > Jenkins.
> > > > >
> > > > > So, it is up to you to decide what you
> > want to
> > > > "Docker-ize". You
> > > > > can try to Docker-ize the current 3 big steps,
> > so RMs
> > > can try to
> > > > run it on
> > > > > their systems, but I'd bet they will just faiI
> > due to
> > > network
> > > > issues. I
> > > > > would be interested in using Docker to make
> each
> > of
> > > these many
> > > > discrete
> > > > > steps portable to another server. I'm not
> > going to
> > > involve
> > > > Docker at this
> > > > > point. My main goal is just to see if I can
> > create a
> > > workflow
> > > > of many
> > > > > discrete steps that isn't horribly painful.
> > Once we
> > > see what
> > > > these steps
> > > > > turn out to be, then we can worry about server
> > > portability of
> > > > those steps.
> > > > >
> > > > > Either way, we want to know about
> running
> > > > Browser+Selenium for
> > > > > sure. And maybe FlashPlayerDebugger or AIR. I
> > would
> > > want to
> > > > know, for
> > > > > example, how you debug a failing checkintest
> in a
> > > Docker
> > > > container.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > >
> > > > > On 2/10/19, 5:18 PM, "OmPrakash
> > Muppirala" <
> > > > bigosmallm@gmail.com>
> > > > > wrote:
> > > > >
> > > > > Alex,
> > > > >
> > > > > Just to be clear, I am following
> the
> > steps
> > > from here
> > > > to try
> > > > > and setup a
> > > > > docker container.
> > > > >
> > > > >
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363009383&sdata=5J7SKN8bRH8oeAzuLfHjT4gQ6UEYbSt46XoaOT%2FqDic%3D&reserved=0
> > > > >
> > > > > Is this doc up to date?
> > > > >
> > > > > Thanks,
> > > > > Om
> > > > >
> > > > > On Wed, Feb 6, 2019 at 12:02 PM
> > OmPrakash
> > > Muppirala <
> > > > > bigosmallm@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > One approach is to have each step
> > in the
> > > process
> > > > spin up a
> > > > > docker image.
> > > > > > And use docker-compose to run
> each
> > > step. All the
> > > > images can
> > > > > be made to
> > > > > > share a common volume where all
> the
> > > artifacts are
> > > > stored
> > > > > across steps.
> > > > > >
> > > > > > You are right about the
> networking
> > issue
> > > though.
> > > > Any
> > > > > network related
> > > > > > failure that occurs on the host
> > machine
> > > will most
> > > > likely
> > > > > occur in the
> > > > > > docker container. Although, I am
> > not
> > > clear how we
> > > > can
> > > > > guarantee that the
> > > > > > same issues will not occur on the
> > > Jenkins server.
> > > > I mean,
> > > > > what is special
> > > > > > about the Jenkins server that
> > makes it
> > > immune to
> > > > these
> > > > > networking issues?
> > > > > >
> > > > > > Thanks,
> > > > > > Om
> > > > > >
> > > > > > On Wed, Feb 6, 2019 at 11:48 AM
> > Alex
> > > Harui
> > > > > <ah...@adobe.com.invalid>
> > > > > > wrote:
> > > > > >
> > > > > >> Again, I don't know anything
> about
> > > Docker, but
> > > > before we
> > > > > spend a lot of
> > > > > >> time on Docker, I also want to
> > point
> > > out that the
> > > > process
> > > > > to create a
> > > > > >> release cannot really be thought
> > of as
> > > "one
> > > > application".
> > > > > It will be a
> > > > > >> series of "steps" to run. How
> > many
> > > steps
> > > > depends on
> > > > > whether we think we
> > > > > >> can isolate enough stuff via
> > Docker to
> > > be able to
> > > > run
> > > > > Docker on the RM's
> > > > > >> computer instead of some shared
> > > computer. On a
> > > > shared
> > > > > computer there will
> > > > > >> be dozens of steps because the
> RM
> > will
> > > need to
> > > > enter
> > > > > passwords to commit
> > > > > >> stuff. On a local computer I
> > guess the
> > > RM can
> > > > supply
> > > > > passwords but I think
> > > > > >> there will be stopping points
> > where the
> > > Maven
> > > > artifacts are
> > > > > deployed and
> > > > > >> the staging repo is closed, and
> > another
> > > stopping
> > > > point for
> > > > > the vote. It
> > > > > >> seems like Docker works by
> > downloading
> > > > dependencies. Given
> > > > > that the
> > > > > >> problem the RMs had last time
> > involved
> > > downloads
> > > > and
> > > > > uploads, why do we
> > > > > >> think Docker will really solve
> > this for
> > > creating
> > > > releases
> > > > > on local machines?
> > > > > >>
> > > > > >> The reason to do this on a
> shared
> > > machine is so
> > > > that new
> > > > > RMs don't have
> > > > > >> to do as much setup. But then I
> > wonder
> > > about the
> > > > > efficiency of kicking off
> > > > > >> that many Docker images.
> Jenkins
> > can
> > > manage that
> > > > already.
> > > > > Does Docker
> > > > > >> have some sort of similar
> > Dashboard or
> > > would we
> > > > use Jenkins
> > > > > to kick off
> > > > > >> Docker steps? I can't quite
> > picture
> > > what is the
> > > > outermost
> > > > > >> control/dashboard.
> > > > > >>
> > > > > >> -Alex
> > > > > >>
> > > > > >> On 2/6/19, 11:03 AM, "Harbs" <
> > > > harbs.lists@gmail.com> wrote:
> > > > > >>
> > > > > >> A quick search turns up
> this:
> > > > > >>
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363009383&sdata=shD%2BU359FtLW0dop3XNWI0qAzQypbRL3%2F774uHxgWwY%3D&reserved=0
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363009383&sdata=shD%2BU359FtLW0dop3XNWI0qAzQypbRL3%2F774uHxgWwY%3D&reserved=0
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363009383&sdata=CWT8R19x%2FNGMUpu30kcKuQLUKenANCxcKy4dbQMrpUg%3D&reserved=0
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363009383&sdata=CWT8R19x%2FNGMUpu30kcKuQLUKenANCxcKy4dbQMrpUg%3D&reserved=0
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363009383&sdata=axHk7pd1ONATK1zsljR8jYtxjYLipeg3kOqIpsMSMrE%3D&reserved=0
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363019375&sdata=SXFxhZosDq9YblRPRBK3iqGIk15P2agpXCl7BlPMO7s%3D&reserved=0
> > > > > >> >
> > > > > >>
> > > > > >> > On Feb 6, 2019, at 8:59
> PM,
> > Alex
> > > Harui
> > > > > <ah...@adobe.com.INVALID>
> > > > > >> wrote:
> > > > > >> >
> > > > > >> > Thanks for volunteering to
> > try it
> > > Om. IMO,
> > > > even more
> > > > > important
> > > > > >> than Firefox+Flash is
> > > SomeBrowser+Selenium. We
> > > > may also
> > > > > need to run Adobe
> > > > > >> AIR's adb. We could probably
> > turn off
> > > the Flash
> > > > tests or
> > > > > replace Flash
> > > > > >> with AIR.
> > > > > >> >
> > > > > >> > Thanks,
> > > > > >> > -Alex
> > > > > >> >
> > > > > >> > On 2/6/19, 10:54 AM,
> "Carlos
> > > Rovira" <
> > > > > carlosrovira@apache.org>
> > > > > >> wrote:
> > > > > >> >
> > > > > >> > Hi Om, that would be
> > great!
> > > waiting for
> > > > your
> > > > > experience with a
> > > > > >> that! :)
> > > > > >> >
> > > > > >> > El mié., 6 feb. 2019 a
> > las
> > > 19:31,
> > > > OmPrakash
> > > > > Muppirala (<
> > > > > >> bigosmallm@gmail.com>)
> > > > > >> > escribió:
> > > > > >> >
> > > > > >> >> Yes, I agree with Alex
> > about not
> > > being
> > > > able to run
> > > > > UI out of docker
> > > > > >> >> containers. I never
> > thought of
> > > the
> > > > checkintests
> > > > > when I made the
> > > > > >> >> suggestion.
> > > > > >> >>
> > > > > >> >> The firefox-flash image
> > that
> > > Yishay
> > > > pointed out
> > > > > looks promising.
> > > > > >> I will
> > > > > >> >> poke around with it and
> > see if
> > > that works
> > > > for us.
> > > > > >> >>
> > > > > >> >> Thanks,
> > > > > >> >> Om
> > > > > >> >>
> > > > > >> >> On Wed, Feb 6, 2019 at
> > 12:41 AM
> > > Yishay
> > > > Weiss <
> > > > > >> yishayjobs@hotmail.com>
> > > > > >> >> wrote:
> > > > > >> >>
> > > > > >> >>> I’ll let Om or someone
> > else
> > > with docker
> > > > experience
> > > > > tell us if
> > > > > >> this [1] is
> > > > > >> >>> relevant.
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>> [1]
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363019375&sdata=JF9Hm0gHw2ZCrLOSScIZI%2Fgx9eya5tZiCBtzZUnwwvg%3D&reserved=0
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > ________________________________
> > > > > >> >>> From: Alex Harui
> > > <aharui@adobe.com.INVALID
> > > > >
> > > > > >> >>> Sent: Wednesday,
> February
> > 6,
> > > 2019
> > > > 10:05:54 AM
> > > > > >> >>> To:
> dev@royale.apache.org
> > > > > >> >>> Subject: Re: 0.9.6
> Release
> > > > > >> >>>
> > > > > >> >>> I don't anything about
> > docker,
> > > but in 15
> > > > minutes of
> > > > > reading I ran
> > > > > >> into
> > > > > >> >>> this:
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363019375&sdata=sXHjFPVrpkfSF%2BoeEwtu4ajfQUsMLx3%2F2wOaQ%2FWtfak%3D&reserved=0
> > > > > >> >>>
> > > > > >> >>> Which says: Docker can't
> > " Run
> > > > applications with
> > > > > graphical
> > > > > >> interfaces".
> > > > > >> >>> If you want Royale to
> use
> > > Docker for
> > > > releases, show
> > > > > that it can
> > > > > >> run
> > > > > >> >>> checkintests with Flash
> > and the
> > > Browser.
> > > > Then I
> > > > > will look into
> > > > > >> it more.
> > > > > >> >>>
> > > > > >> >>> The highest level goal
> is
> > to
> > > make it as
> > > > easy as
> > > > > possible for
> > > > > >> someone to
> > > > > >> >>> volunteer to be an RM.
> > Any
> > > requirement
> > > > of "install
> > > > > this (Docker,
> > > > > >> etc) on
> > > > > >> >>> your computer" is, IMO,
> > another
> > > barrier
> > > > to entry.
> > > > > Yeah, RMs will
> > > > > >> have to
> > > > > >> >>> have Maven installed and
> > maybe
> > > Ant, but
> > > > you should
> > > > > already have
> > > > > >> those
> > > > > >> >>> installed to be a
> > committer/PMC
> > > member.
> > > > > >> >>>
> > > > > >> >>> That said, a good
> > takeaway from
> > > the
> > > > Docker idea is
> > > > > to try to find
> > > > > >> a way
> > > > > >> >> to
> > > > > >> >>> make an "Image" of
> > whatever we
> > > end up
> > > > with on
> > > > > whatever server we
> > > > > >> end up
> > > > > >> >>> using so if the image
> can
> > be
> > > copied and
> > > > used on
> > > > > other servers.
> > > > > >> I'm not
> > > > > >> >>> exactly sure how to do
> > that
> > > with Azure,
> > > > which hosts
> > > > > my CI
> > > > > >> server. I will
> > > > > >> >>> spend a few more minutes
> > > researching that.
> > > > > >> >>>
> > > > > >> >>> I could not quickly find
> > any
> > > way to get a
> > > > free VM
> > > > > on Azure or AWS
> > > > > >> that
> > > > > >> >>> isn't a
> > > > free-trial-start-paying-after-a-year. So,
> > > > > unless someone
> > > > > >> comes
> > > > > >> >> up
> > > > > >> >>> with a free server we
> can
> > use
> > > "forever",
> > > > I'm going
> > > > > to just start
> > > > > >> with my
> > > > > >> >>> Azure VM.
> > > > > >> >>>
> > > > > >> >>> -Alex
> > > > > >> >>>
> > > > > >> >>> On 2/5/19, 10:59 PM,
> > "Carlos
> > > Rovira" <
> > > > > carlosrovira@apache.org>
> > > > > >> wrote:
> > > > > >> >>>
> > > > > >> >>> Hi.
> > > > > >> >>>
> > > > > >> >>> the plan sounds very
> > good to
> > > me. Just
> > > > my 2
> > > > > thoughts on this:
> > > > > >> >>>
> > > > > >> >>> 1.- As I was reading
> I
> > was
> > > thinking as
> > > > well on
> > > > > something like
> > > > > >> Docker
> > > > > >> >>> and
> > > > > >> >>> see Om as well
> > thinking on
> > > the same.
> > > > Maybe is
> > > > > the way to this
> > > > > >> with
> > > > > >> >> the
> > > > > >> >>> actual technology.
> > Seems VMs
> > > are
> > > > stepping out a
> > > > > bit this days
> > > > > >> in
> > > > > >> >> favor
> > > > > >> >>> of
> > > > > >> >>> things like Docker.
> > Maybe
> > > the same did
> > > > Git over
> > > > > Svn, and today
> > > > > >> Svn is
> > > > > >> >>> an
> > > > > >> >>> old remembrance. I
> > must say
> > > that I
> > > > have no
> > > > > experience with
> > > > > >> Docker, so
> > > > > >> >>> doing
> > > > > >> >>> that will require
> > acquire
> > > that
> > > > knowledge, but
> > > > > seems it could
> > > > > >> be worth
> > > > > >> >>> it.
> > > > > >> >>>
> > > > > >> >>> 2.- Maybe is not
> > possible,
> > > but I want
> > > > to propose
> > > > > to do this
> > > > > >> work I a
> > > > > >> >>> separate branch, so
> it
> > could
> > > be in
> > > > parallel to
> > > > > other
> > > > > >> developments. I
> > > > > >> >>> think
> > > > > >> >>> work over develop is
> > > practical if
> > > > there's
> > > > > something tiny that
> > > > > >> could
> > > > > >> >> be
> > > > > >> >>> done
> > > > > >> >>> in a commit. But as
> we
> > need
> > > more than
> > > > one, or is
> > > > > a long
> > > > > >> process (like
> > > > > >> >>> this), chances are to
> > make
> > > develop
> > > > branch
> > > > > unstable and even
> > > > > >> for some
> > > > > >> >>> days.
> > > > > >> >>> I think we should try
> > to
> > > avoid that
> > > > scenario,
> > > > > and branches are
> > > > > >> the
> > > > > >> >> best
> > > > > >> >>> way. If we do this
> way,
> > > we'll benefit
> > > > of more
> > > > > reliable develop
> > > > > >> >> branch.
> > > > > >> >>>
> > > > > >> >>> Thanks and good to
> > know of
> > > this plan :)
> > > > > >> >>>
> > > > > >> >>> Carlos
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>> El mar., 5 feb. 2019
> a
> > las
> > > 23:19,
> > > > Harbs (<
> > > > > >> harbs.lists@gmail.com>)
> > > > > >> >>> escribió:
> > > > > >> >>>
> > > > > >> >>>> I’ve never used Docker
> > myself,
> > > but that
> > > > might be a
> > > > > good plan.
> > > > > >> >>>>
> > > > > >> >>>>> On Feb 6, 2019, at
> > 12:07 AM,
> > > OmPrakash
> > > > Muppirala <
> > > > > >> >>> bigosmallm@gmail.com>
> > > > > >> >>>> wrote:
> > > > > >> >>>>>
> > > > > >> >>>>> I was wondering if we
> > can use
> > > docker
> > > > images to
> > > > > setup and seal
> > > > > >> the
> > > > > >> >>> RM
> > > > > >> >>>>> environment. Then
> > other RMs
> > > simply
> > > > need to run
> > > > > the image
> > > > > >> locally
> > > > > >> >>> and run
> > > > > >> >>>>> the release scripts.
> > Might
> > > be easier.
> > > > If folks
> > > > > like this plan,
> > > > > >> >> I
> > > > > >> >>> can
> > > > > >> >>>> try
> > > > > >> >>>>> to put something
> > together.
> > > > > >> >>>>>
> > > > > >> >>>>> Thanks,
> > > > > >> >>>>> Om
> > > > > >> >>>>>
> > > > > >> >>>>> On Tue, Feb 5, 2019 at
> > 1:40
> > > PM Harbs <
> > > > > harbs.lists@gmail.com>
> > > > > >> >>> wrote:
> > > > > >> >>>>>
> > > > > >> >>>>>> In a recent
> > discussion, it
> > > looks like
> > > > other
> > > > > projects have
> > > > > >> gotten
> > > > > >> >>>> resources
> > > > > >> >>>>>> from AWS.
> > > > > >> >>>>>>
> > > > > >> >>>>>> Whatever service we
> > use,
> > > could setup a
> > > > “shared”
> > > > > Royale account
> > > > > >> >>> that all
> > > > > >> >>>>>> PMC members could
> have
> > > access to.
> > > > > >> >>>>>>
> > > > > >> >>>>>> I don’t know if
> > there’s some
> > > way we
> > > > could
> > > > > leverage Gitlab’s
> > > > > >> >>> integration
> > > > > >> >>>>>> pipelines
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363019375&sdata=p6LGHK3Q8aGZ9ZeaGGZc83Mv19k71%2BvJ49nFLQaKjt4%3D&reserved=0
> > > > > >> >>> <
> > > > > >> >>>>>>
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363019375&sdata=p6LGHK3Q8aGZ9ZeaGGZc83Mv19k71%2BvJ49nFLQaKjt4%3D&reserved=0
> > > > > >> >>>>
> > > > > >> >>>>>>
> > > > > >> >>>>>>> On Feb 5, 2019, at
> > 11:33
> > > PM, Alex
> > > > Harui
> > > > > >> >> <aharui@adobe.com.INVALID
> > > > > >> >>>>
> > > > > >> >>>>>> wrote:
> > > > > >> >>>>>>>
> > > > > >> >>>>>>> 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" <
> > > > > >> >>
> piotrzarzycki21@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.lists@gmail.com
> > > > > >> >>> wrote:
> > > > > >> >>>>>>>
> > > > > >> >>>>>>>> A big +1 from me!
> > > > > >> >>>>>>>>
> > > > > >> >>>>>>>> Looking forward!
> > > > > >> >>>>>>>>
> > > > > >> >>>>>>>>> On Feb 5, 2019, at
> > 9:34
> > > PM, Alex
> > > > Harui
> > > > > >> >>>
> <aharui@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
> > > > >
> >
> >
> >
>
> --
> Carlos Rovira
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363019375&sdata=BvZcg85VxoHU%2FJEUaNMjnYfEeZKgWGgFoKsQ7uMIh44%3D&reserved=0
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363019375&sdata=3B%2BNE7pDyafx9cFrLHRs%2BD6C7UFPU7G3qFxbowHic%2Bg%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C3775d449f101420bcf2008d6f335b448%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963809363019375&sdata=3B%2BNE7pDyafx9cFrLHRs%2BD6C7UFPU7G3qFxbowHic%2Bg%3D&reserved=0>*
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
ASDoc is not fully working for me. I've been working on that the past several days. It took quite a while to fix the JSON output from new and interesting ASDoc patterns. I'm now looking into failures due to changes in coercion rules in the JS output. ASDoc was trying to save time by using plain objects that were isomorphic to a class instead of actual class instances.
MXTests are failing on the CI server and probably locally but I haven't gotten that far.
I would think we want these things to work, but you are the RM so it is up to you. Volunteers are welcome to help with these and other tasks.
-Alex
On 6/17/19, 12:44 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Hi Alex,
I don't see any answer here - can I start with trying your instruction and
start release ?
Thanks,
Piotr
śr., 12 cze 2019 o 10:12 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Alex,
> just build from scratch right now and seems maven and ant was ok
>
> El mié., 12 jun. 2019 a las 10:02, Alex Harui (<ah...@adobe.com.invalid>)
> escribió:
>
> > The merge is complete, and the main builds seem to be successful, except
> > for Maven on royale-asjs which was failing before the merge.
> >
> > I'm still catching up on other things, but I think there are some bugs we
> > need to fix before cutting the release? I think ASDoc may not be fully
> > working? What else?
> >
> > -Alex
> >
> > On 6/10/19, 11:05 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
> >
> > Hi Alex,
> >
> > Many thanks for that! I will try to be RM. I will have some dedicated
> > time
> > for that. I will wait for your instruction and merge to develop.
> >
> > Thanks,
> > Piotr
> >
> >
> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui <ah...@adobe.com.invalid>
> > wrote:
> >
> > > Well, that turned out to be much more time-consuming than I
> > expected, but
> > > we can now create identical release artifacts on Mac and Win. I am
> > hopeful
> > > this effort will pay off not only now in having other folks
> generate
> > > releases, but also in the future if signed binaries become a
> > requirement.
> > >
> > > There continues to be a lot of distractions in my life that can
> cause
> > > delays, but I hope to merge the release_practice branches into
> > develop over
> > > the next day or two and figure out where in the wiki to document
> the
> > > release process. So, now is the time for one or more people to
> step
> > up to
> > > be the RMs for 0.9.6 and help debug and improve the process.
> > >
> > > I am going to try very hard not to "own" the process. If something
> > goes
> > > wrong, I am going to ask others to try to debug and fix it first
> > because it
> > > is in the project's best interests for others to truly understand
> > how this
> > > stuff works.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> > >
> > > It has turned out to be harder than expected to get the same
> > binaries
> > > on Mac and Win. I now have the identical binaries for
> > royale-compiler and
> > > royale-typedefs Maven artifacts and am starting on royale-asjs. I
> > might
> > > get lucky and the changes that fixed royale-typedefs SWCs will
> > magically
> > > get the royale-asjs SWCs to match. Then we have to make the Ant
> > artifacts
> > > match.
> > >
> > > There have been a lot of distractions in my non-work life which
> > has
> > > also impeded progress. I hope to make much progress this coming
> > week and
> > > if we're lucky, I will be asking for a volunteer (or volunteers) to
> > test
> > > drive all of this stuff and be the RM for 0.9.6. I am not going to
> > be the
> > > RM.
> > >
> > > -Alex
> > >
> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com
> > >
> > > wrote:
> > >
> > > Hi Alex,
> > >
> > > It's been a while since you have started effort with
> > automating
> > > build.
> > > Where are you with that ? Are we closer to started 0.9.6.
> Do
> > you
> > > need any
> > > help with this ?
> > >
> > > Thanks,
> > > Piotr
> > >
> > > wt., 2 kwi 2019 o 19:30 Alex Harui
> <aharui@adobe.com.invalid
> > >
> > > napisał(a):
> > >
> > > > Update:
> > > >
> > > > In order to make verification of binary release packages
> > created
> > > on the
> > > > server easier, I have made changes to our build scripts
> and
> > > tools to try to
> > > > generate reproducible binaries. I've seen two different
> > builds
> > > compare on
> > > > my Mac. The next challenge will be to see if the server
> > can
> > > build a
> > > > package on Windows that will compare on Mac.
> > > >
> > > > One of the changes I needed to make is to JBurg. The
> > version of
> > > JBurg we
> > > > use generates method names including a hash that doesn't
> > > reproduce the same
> > > > name each time. I have changes to JBurg ready, however
> > JBurg is
> > > currently
> > > > under CPL which is category B. We only need one file, we
> > don't
> > > need or
> > > > want all of JBurg at this time. The one JBurg file is
> > jointly
> > > owned by
> > > > Adobe and Tom Harwood. I've contact Tom and he will be
> > filing
> > > an ICLA and
> > > > has given me permission to commit the lines he owns in
> > that one
> > > file.
> > > >
> > > > This is the revision of the file that will be donated by
> > > Tom/Adobe.
> > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=b70CftgUQmkNU%2BaLs8hw4ZcSCxhpoh4oZ%2FhJ9BCFjUQ%3D&reserved=0
> > > >
> > > > Once this file goes in with the changes to keep the
> method
> > names
> > > the same,
> > > > there will be more tweaks to the release tasks and then
> we
> > can
> > > try cutting
> > > > a release. I'm thinking we'll be at that point in early
> > May, so
> > > now is the
> > > > time to get stuff in for the 0.9.6 release.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com>
> wrote:
> > > >
> > > > I would much rather have others find and fix issues
> > > themselves. That
> > > > way, more people than just me will know how to maintain
> the
> > > system. It
> > > > actually turns out that, IMO, a group of people can work
> > on the
> > > release.
> > > > There are 14 steps. Literally, 14 different people could
> > > execute one step
> > > > each.
> > > >
> > > > My 2 cents,
> > > > -Alex
> > > >
> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > > wrote:
> > > >
> > > > Hi Alex,
> > > >
> > > > amazing work! congrats to reach to this point! :)
> > > >
> > > > I need to put my head on all of this, but count
> on
> > me to
> > > be a RM.
> > > > I think
> > > > the best thing should be that you be the first RM
> > to try
> > > your own
> > > > development at least for the first time, and then
> > the
> > > rest of us
> > > > will
> > > > follow you on the next releases. With all this on
> > place
> > > we maybe
> > > > could
> > > > release once a month or every two months...
> > > >
> > > > Thanks for doing this :)
> > > >
> > > > Carlos
> > > >
> > > >
> > > > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > > > (<ah...@adobe.com.invalid>)
> > > > escribió:
> > > >
> > > > > OK, I've now seen Jenkins perform the steps to
> > build
> > > the release
> > > > > artifacts. Folks interested in Docker-izing
> the
> > steps
> > > are
> > > > welcome to look
> > > > > at the jobs on the "Royale Release" tab on the
> CI
> > > server.
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GZZ35qSSBDcI24AgDEdV6o9ujYAT%2BB11a4%2FHeXiVnCY%3D&reserved=0
> > > > >
> > > > > These steps assume that the RM can run the
> basic
> > Maven
> > > and Ant
> > > > build on
> > > > > the RM's computer. I think that's a fair
> > requirement
> > > since all
> > > > of us on the
> > > > > PMC need to able to do that to build the RC in
> > order
> > > to vote on
> > > > it.
> > > > > Jenkins does other tasks like run the Maven
> > release
> > > plugin
> > > > steps.
> > > > >
> > > > > Currently that results in binaries on Jenkins
> > that are
> > > > downloaded to the
> > > > > RM's computer. These binaries need to be
> > verified by
> > > the RM
> > > > which is the
> > > > > next phase I will be starting on now. The RM
> > verifies
> > > the bits
> > > > and then
> > > > > PGP signs them. And then the bits are uploaded
> > off
> > > the RM's
> > > > computer to
> > > > > Maven Staging or dist.a.o/dev. If that
> > uploading
> > > turns out to
> > > > be a point
> > > > > of failure, we have the option of having
> Jenkins
> > > upload the big
> > > > files and
> > > > > have the RM only upload PGP signature files.
> Or
> > > finding a way
> > > > for Jenkins
> > > > > to get the signature files from the RM. The
> > uploads
> > > worked fine
> > > > for me,
> > > > > but then again, so did the old script's
> uploads.
> > > > >
> > > > > Therefore, once I get the binary verification
> > phase
> > > completed, I
> > > > think
> > > > > someone other than me should be the RM and try
> > to use
> > > these
> > > > steps to
> > > > > generate the release and help debug the process
> > for
> > > the next
> > > > RM. So,
> > > > > please try to carve out some time to be the RM.
> > One
> > > advantage
> > > > of doing
> > > > > most of the work on Jenkins is that it frees up
> > my
> > > computer to
> > > > do other
> > > > > things while Jenkins is cranking away.
> > > > >
> > > > > I think we're at least a week away from binary
> > > verification,
> > > > maybe two, so
> > > > > it is time to start thinking about what is
> going
> > in
> > > this release.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
> > > <ah...@adobe.com.INVALID>
> > > > wrote:
> > > > >
> > > > > In case you haven't guessed, I'm testing
> out
> > > Jenkins and its
> > > > ability
> > > > > to create the artifacts and send emails.
> Please
> > > ignore any
> > > > email that
> > > > > looks like a vote or discuss thread.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 2/10/19, 8:44 PM, "Alex Harui"
> > > <ah...@adobe.com.INVALID>
> > > > wrote:
> > > > >
> > > > > Om,
> > > > >
> > > > > Well, that's what I used for the last
> > > release. I'm sure
> > > > there is
> > > > > probably some inaccuracy in it.
> > > > >
> > > > > That said, I'm abandoning that document
> > and
> > > taking a new
> > > > angle
> > > > > because that document presumed that the release
> > > manager was
> > > > trying to
> > > > > create a release on his/her computer. I've
> > given up
> > > on that and
> > > > working on
> > > > > making releases from a shared computer for the
> > reasons
> > > I've
> > > > stated
> > > > > upthread. I hope to make some progress on that
> > this
> > > week.
> > > > >
> > > > > The key difference is that the new
> angle
> > does
> > > not
> > > > presume that you
> > > > > have Git SSH and PGP signatures all set up on
> > some
> > > computer. I
> > > > have not
> > > > > looked into how Docker would handle that. You
> > > certainly
> > > > wouldn't want the
> > > > > Docker image to contain your SSH or PGP
> > keys/creds.
> > > And if the
> > > > Docker
> > > > > image doesn't, then that is another stumbling
> > block
> > > for future
> > > > RMs.
> > > > >
> > > > > The other key difference is that the
> old
> > > script presumed
> > > > you could
> > > > > create the 3 release in 3 huge "easy" steps.
> > We've
> > > seen that is
> > > > only true
> > > > > for me. So the new angle creates many discrete
> > steps
> > > managed by
> > > > Jenkins.
> > > > >
> > > > > So, it is up to you to decide what you
> > want to
> > > > "Docker-ize". You
> > > > > can try to Docker-ize the current 3 big steps,
> > so RMs
> > > can try to
> > > > run it on
> > > > > their systems, but I'd bet they will just faiI
> > due to
> > > network
> > > > issues. I
> > > > > would be interested in using Docker to make
> each
> > of
> > > these many
> > > > discrete
> > > > > steps portable to another server. I'm not
> > going to
> > > involve
> > > > Docker at this
> > > > > point. My main goal is just to see if I can
> > create a
> > > workflow
> > > > of many
> > > > > discrete steps that isn't horribly painful.
> > Once we
> > > see what
> > > > these steps
> > > > > turn out to be, then we can worry about server
> > > portability of
> > > > those steps.
> > > > >
> > > > > Either way, we want to know about
> running
> > > > Browser+Selenium for
> > > > > sure. And maybe FlashPlayerDebugger or AIR. I
> > would
> > > want to
> > > > know, for
> > > > > example, how you debug a failing checkintest
> in a
> > > Docker
> > > > container.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > >
> > > > > On 2/10/19, 5:18 PM, "OmPrakash
> > Muppirala" <
> > > > bigosmallm@gmail.com>
> > > > > wrote:
> > > > >
> > > > > Alex,
> > > > >
> > > > > Just to be clear, I am following
> the
> > steps
> > > from here
> > > > to try
> > > > > and setup a
> > > > > docker container.
> > > > >
> > > > >
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=%2F9mdYnvJTSx1BVR6I0FyoH%2BbKSbiCET7hCoO1y%2FvgrQ%3D&reserved=0
> > > > >
> > > > > Is this doc up to date?
> > > > >
> > > > > Thanks,
> > > > > Om
> > > > >
> > > > > On Wed, Feb 6, 2019 at 12:02 PM
> > OmPrakash
> > > Muppirala <
> > > > > bigosmallm@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > One approach is to have each step
> > in the
> > > process
> > > > spin up a
> > > > > docker image.
> > > > > > And use docker-compose to run
> each
> > > step. All the
> > > > images can
> > > > > be made to
> > > > > > share a common volume where all
> the
> > > artifacts are
> > > > stored
> > > > > across steps.
> > > > > >
> > > > > > You are right about the
> networking
> > issue
> > > though.
> > > > Any
> > > > > network related
> > > > > > failure that occurs on the host
> > machine
> > > will most
> > > > likely
> > > > > occur in the
> > > > > > docker container. Although, I am
> > not
> > > clear how we
> > > > can
> > > > > guarantee that the
> > > > > > same issues will not occur on the
> > > Jenkins server.
> > > > I mean,
> > > > > what is special
> > > > > > about the Jenkins server that
> > makes it
> > > immune to
> > > > these
> > > > > networking issues?
> > > > > >
> > > > > > Thanks,
> > > > > > Om
> > > > > >
> > > > > > On Wed, Feb 6, 2019 at 11:48 AM
> > Alex
> > > Harui
> > > > > <ah...@adobe.com.invalid>
> > > > > > wrote:
> > > > > >
> > > > > >> Again, I don't know anything
> about
> > > Docker, but
> > > > before we
> > > > > spend a lot of
> > > > > >> time on Docker, I also want to
> > point
> > > out that the
> > > > process
> > > > > to create a
> > > > > >> release cannot really be thought
> > of as
> > > "one
> > > > application".
> > > > > It will be a
> > > > > >> series of "steps" to run. How
> > many
> > > steps
> > > > depends on
> > > > > whether we think we
> > > > > >> can isolate enough stuff via
> > Docker to
> > > be able to
> > > > run
> > > > > Docker on the RM's
> > > > > >> computer instead of some shared
> > > computer. On a
> > > > shared
> > > > > computer there will
> > > > > >> be dozens of steps because the
> RM
> > will
> > > need to
> > > > enter
> > > > > passwords to commit
> > > > > >> stuff. On a local computer I
> > guess the
> > > RM can
> > > > supply
> > > > > passwords but I think
> > > > > >> there will be stopping points
> > where the
> > > Maven
> > > > artifacts are
> > > > > deployed and
> > > > > >> the staging repo is closed, and
> > another
> > > stopping
> > > > point for
> > > > > the vote. It
> > > > > >> seems like Docker works by
> > downloading
> > > > dependencies. Given
> > > > > that the
> > > > > >> problem the RMs had last time
> > involved
> > > downloads
> > > > and
> > > > > uploads, why do we
> > > > > >> think Docker will really solve
> > this for
> > > creating
> > > > releases
> > > > > on local machines?
> > > > > >>
> > > > > >> The reason to do this on a
> shared
> > > machine is so
> > > > that new
> > > > > RMs don't have
> > > > > >> to do as much setup. But then I
> > wonder
> > > about the
> > > > > efficiency of kicking off
> > > > > >> that many Docker images.
> Jenkins
> > can
> > > manage that
> > > > already.
> > > > > Does Docker
> > > > > >> have some sort of similar
> > Dashboard or
> > > would we
> > > > use Jenkins
> > > > > to kick off
> > > > > >> Docker steps? I can't quite
> > picture
> > > what is the
> > > > outermost
> > > > > >> control/dashboard.
> > > > > >>
> > > > > >> -Alex
> > > > > >>
> > > > > >> On 2/6/19, 11:03 AM, "Harbs" <
> > > > harbs.lists@gmail.com> wrote:
> > > > > >>
> > > > > >> A quick search turns up
> this:
> > > > > >>
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=L%2FSQRtItveWwGWXpiz5ImQHJ%2BD0kyqIWy9%2BN8KFpfGg%3D&reserved=0
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=L%2FSQRtItveWwGWXpiz5ImQHJ%2BD0kyqIWy9%2BN8KFpfGg%3D&reserved=0
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GgxPOsJMU7xnieSkFk%2FF5Ntp75tvg4y8VVOJitIEEYI%3D&reserved=0
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GgxPOsJMU7xnieSkFk%2FF5Ntp75tvg4y8VVOJitIEEYI%3D&reserved=0
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=oAwxtBcYuuB73255nFD40k2NqnLKIJWo92htZkychLc%3D&reserved=0
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=oAwxtBcYuuB73255nFD40k2NqnLKIJWo92htZkychLc%3D&reserved=0
> > > > > >> >
> > > > > >>
> > > > > >> > On Feb 6, 2019, at 8:59
> PM,
> > Alex
> > > Harui
> > > > > <ah...@adobe.com.INVALID>
> > > > > >> wrote:
> > > > > >> >
> > > > > >> > Thanks for volunteering to
> > try it
> > > Om. IMO,
> > > > even more
> > > > > important
> > > > > >> than Firefox+Flash is
> > > SomeBrowser+Selenium. We
> > > > may also
> > > > > need to run Adobe
> > > > > >> AIR's adb. We could probably
> > turn off
> > > the Flash
> > > > tests or
> > > > > replace Flash
> > > > > >> with AIR.
> > > > > >> >
> > > > > >> > Thanks,
> > > > > >> > -Alex
> > > > > >> >
> > > > > >> > On 2/6/19, 10:54 AM,
> "Carlos
> > > Rovira" <
> > > > > carlosrovira@apache.org>
> > > > > >> wrote:
> > > > > >> >
> > > > > >> > Hi Om, that would be
> > great!
> > > waiting for
> > > > your
> > > > > experience with a
> > > > > >> that! :)
> > > > > >> >
> > > > > >> > El mié., 6 feb. 2019 a
> > las
> > > 19:31,
> > > > OmPrakash
> > > > > Muppirala (<
> > > > > >> bigosmallm@gmail.com>)
> > > > > >> > escribió:
> > > > > >> >
> > > > > >> >> Yes, I agree with Alex
> > about not
> > > being
> > > > able to run
> > > > > UI out of docker
> > > > > >> >> containers. I never
> > thought of
> > > the
> > > > checkintests
> > > > > when I made the
> > > > > >> >> suggestion.
> > > > > >> >>
> > > > > >> >> The firefox-flash image
> > that
> > > Yishay
> > > > pointed out
> > > > > looks promising.
> > > > > >> I will
> > > > > >> >> poke around with it and
> > see if
> > > that works
> > > > for us.
> > > > > >> >>
> > > > > >> >> Thanks,
> > > > > >> >> Om
> > > > > >> >>
> > > > > >> >> On Wed, Feb 6, 2019 at
> > 12:41 AM
> > > Yishay
> > > > Weiss <
> > > > > >> yishayjobs@hotmail.com>
> > > > > >> >> wrote:
> > > > > >> >>
> > > > > >> >>> I’ll let Om or someone
> > else
> > > with docker
> > > > experience
> > > > > tell us if
> > > > > >> this [1] is
> > > > > >> >>> relevant.
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>> [1]
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=oE4%2F%2FqGiaVmCU3VShIMUbUMJc%2BiwF%2F07dkEgYhcgQJA%3D&reserved=0
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > ________________________________
> > > > > >> >>> From: Alex Harui
> > > <aharui@adobe.com.INVALID
> > > > >
> > > > > >> >>> Sent: Wednesday,
> February
> > 6,
> > > 2019
> > > > 10:05:54 AM
> > > > > >> >>> To:
> dev@royale.apache.org
> > > > > >> >>> Subject: Re: 0.9.6
> Release
> > > > > >> >>>
> > > > > >> >>> I don't anything about
> > docker,
> > > but in 15
> > > > minutes of
> > > > > reading I ran
> > > > > >> into
> > > > > >> >>> this:
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=iyP6ZrHSV24Ykd5zjCPwrQYD%2F378Ek9pHNj4n2mTIp8%3D&reserved=0
> > > > > >> >>>
> > > > > >> >>> Which says: Docker can't
> > " Run
> > > > applications with
> > > > > graphical
> > > > > >> interfaces".
> > > > > >> >>> If you want Royale to
> use
> > > Docker for
> > > > releases, show
> > > > > that it can
> > > > > >> run
> > > > > >> >>> checkintests with Flash
> > and the
> > > Browser.
> > > > Then I
> > > > > will look into
> > > > > >> it more.
> > > > > >> >>>
> > > > > >> >>> The highest level goal
> is
> > to
> > > make it as
> > > > easy as
> > > > > possible for
> > > > > >> someone to
> > > > > >> >>> volunteer to be an RM.
> > Any
> > > requirement
> > > > of "install
> > > > > this (Docker,
> > > > > >> etc) on
> > > > > >> >>> your computer" is, IMO,
> > another
> > > barrier
> > > > to entry.
> > > > > Yeah, RMs will
> > > > > >> have to
> > > > > >> >>> have Maven installed and
> > maybe
> > > Ant, but
> > > > you should
> > > > > already have
> > > > > >> those
> > > > > >> >>> installed to be a
> > committer/PMC
> > > member.
> > > > > >> >>>
> > > > > >> >>> That said, a good
> > takeaway from
> > > the
> > > > Docker idea is
> > > > > to try to find
> > > > > >> a way
> > > > > >> >> to
> > > > > >> >>> make an "Image" of
> > whatever we
> > > end up
> > > > with on
> > > > > whatever server we
> > > > > >> end up
> > > > > >> >>> using so if the image
> can
> > be
> > > copied and
> > > > used on
> > > > > other servers.
> > > > > >> I'm not
> > > > > >> >>> exactly sure how to do
> > that
> > > with Azure,
> > > > which hosts
> > > > > my CI
> > > > > >> server. I will
> > > > > >> >>> spend a few more minutes
> > > researching that.
> > > > > >> >>>
> > > > > >> >>> I could not quickly find
> > any
> > > way to get a
> > > > free VM
> > > > > on Azure or AWS
> > > > > >> that
> > > > > >> >>> isn't a
> > > > free-trial-start-paying-after-a-year. So,
> > > > > unless someone
> > > > > >> comes
> > > > > >> >> up
> > > > > >> >>> with a free server we
> can
> > use
> > > "forever",
> > > > I'm going
> > > > > to just start
> > > > > >> with my
> > > > > >> >>> Azure VM.
> > > > > >> >>>
> > > > > >> >>> -Alex
> > > > > >> >>>
> > > > > >> >>> On 2/5/19, 10:59 PM,
> > "Carlos
> > > Rovira" <
> > > > > carlosrovira@apache.org>
> > > > > >> wrote:
> > > > > >> >>>
> > > > > >> >>> Hi.
> > > > > >> >>>
> > > > > >> >>> the plan sounds very
> > good to
> > > me. Just
> > > > my 2
> > > > > thoughts on this:
> > > > > >> >>>
> > > > > >> >>> 1.- As I was reading
> I
> > was
> > > thinking as
> > > > well on
> > > > > something like
> > > > > >> Docker
> > > > > >> >>> and
> > > > > >> >>> see Om as well
> > thinking on
> > > the same.
> > > > Maybe is
> > > > > the way to this
> > > > > >> with
> > > > > >> >> the
> > > > > >> >>> actual technology.
> > Seems VMs
> > > are
> > > > stepping out a
> > > > > bit this days
> > > > > >> in
> > > > > >> >> favor
> > > > > >> >>> of
> > > > > >> >>> things like Docker.
> > Maybe
> > > the same did
> > > > Git over
> > > > > Svn, and today
> > > > > >> Svn is
> > > > > >> >>> an
> > > > > >> >>> old remembrance. I
> > must say
> > > that I
> > > > have no
> > > > > experience with
> > > > > >> Docker, so
> > > > > >> >>> doing
> > > > > >> >>> that will require
> > acquire
> > > that
> > > > knowledge, but
> > > > > seems it could
> > > > > >> be worth
> > > > > >> >>> it.
> > > > > >> >>>
> > > > > >> >>> 2.- Maybe is not
> > possible,
> > > but I want
> > > > to propose
> > > > > to do this
> > > > > >> work I a
> > > > > >> >>> separate branch, so
> it
> > could
> > > be in
> > > > parallel to
> > > > > other
> > > > > >> developments. I
> > > > > >> >>> think
> > > > > >> >>> work over develop is
> > > practical if
> > > > there's
> > > > > something tiny that
> > > > > >> could
> > > > > >> >> be
> > > > > >> >>> done
> > > > > >> >>> in a commit. But as
> we
> > need
> > > more than
> > > > one, or is
> > > > > a long
> > > > > >> process (like
> > > > > >> >>> this), chances are to
> > make
> > > develop
> > > > branch
> > > > > unstable and even
> > > > > >> for some
> > > > > >> >>> days.
> > > > > >> >>> I think we should try
> > to
> > > avoid that
> > > > scenario,
> > > > > and branches are
> > > > > >> the
> > > > > >> >> best
> > > > > >> >>> way. If we do this
> way,
> > > we'll benefit
> > > > of more
> > > > > reliable develop
> > > > > >> >> branch.
> > > > > >> >>>
> > > > > >> >>> Thanks and good to
> > know of
> > > this plan :)
> > > > > >> >>>
> > > > > >> >>> Carlos
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>> El mar., 5 feb. 2019
> a
> > las
> > > 23:19,
> > > > Harbs (<
> > > > > >> harbs.lists@gmail.com>)
> > > > > >> >>> escribió:
> > > > > >> >>>
> > > > > >> >>>> I’ve never used Docker
> > myself,
> > > but that
> > > > might be a
> > > > > good plan.
> > > > > >> >>>>
> > > > > >> >>>>> On Feb 6, 2019, at
> > 12:07 AM,
> > > OmPrakash
> > > > Muppirala <
> > > > > >> >>> bigosmallm@gmail.com>
> > > > > >> >>>> wrote:
> > > > > >> >>>>>
> > > > > >> >>>>> I was wondering if we
> > can use
> > > docker
> > > > images to
> > > > > setup and seal
> > > > > >> the
> > > > > >> >>> RM
> > > > > >> >>>>> environment. Then
> > other RMs
> > > simply
> > > > need to run
> > > > > the image
> > > > > >> locally
> > > > > >> >>> and run
> > > > > >> >>>>> the release scripts.
> > Might
> > > be easier.
> > > > If folks
> > > > > like this plan,
> > > > > >> >> I
> > > > > >> >>> can
> > > > > >> >>>> try
> > > > > >> >>>>> to put something
> > together.
> > > > > >> >>>>>
> > > > > >> >>>>> Thanks,
> > > > > >> >>>>> Om
> > > > > >> >>>>>
> > > > > >> >>>>> On Tue, Feb 5, 2019 at
> > 1:40
> > > PM Harbs <
> > > > > harbs.lists@gmail.com>
> > > > > >> >>> wrote:
> > > > > >> >>>>>
> > > > > >> >>>>>> In a recent
> > discussion, it
> > > looks like
> > > > other
> > > > > projects have
> > > > > >> gotten
> > > > > >> >>>> resources
> > > > > >> >>>>>> from AWS.
> > > > > >> >>>>>>
> > > > > >> >>>>>> Whatever service we
> > use,
> > > could setup a
> > > > “shared”
> > > > > Royale account
> > > > > >> >>> that all
> > > > > >> >>>>>> PMC members could
> have
> > > access to.
> > > > > >> >>>>>>
> > > > > >> >>>>>> I don’t know if
> > there’s some
> > > way we
> > > > could
> > > > > leverage Gitlab’s
> > > > > >> >>> integration
> > > > > >> >>>>>> pipelines
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GSexC31IRXLohkmy%2F1kx1PrVgcu0Ixu1%2BtQNMaCOUr4%3D&reserved=0
> > > > > >> >>> <
> > > > > >> >>>>>>
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542822996552&sdata=GSexC31IRXLohkmy%2F1kx1PrVgcu0Ixu1%2BtQNMaCOUr4%3D&reserved=0
> > > > > >> >>>>
> > > > > >> >>>>>>
> > > > > >> >>>>>>> On Feb 5, 2019, at
> > 11:33
> > > PM, Alex
> > > > Harui
> > > > > >> >> <aharui@adobe.com.INVALID
> > > > > >> >>>>
> > > > > >> >>>>>> wrote:
> > > > > >> >>>>>>>
> > > > > >> >>>>>>> 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" <
> > > > > >> >>
> piotrzarzycki21@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.lists@gmail.com
> > > > > >> >>> wrote:
> > > > > >> >>>>>>>
> > > > > >> >>>>>>>> A big +1 from me!
> > > > > >> >>>>>>>>
> > > > > >> >>>>>>>> Looking forward!
> > > > > >> >>>>>>>>
> > > > > >> >>>>>>>>> On Feb 5, 2019, at
> > 9:34
> > > PM, Alex
> > > > Harui
> > > > > >> >>>
> <aharui@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
> > > > >
> >
> >
> >
>
> --
> Carlos Rovira
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542823006545&sdata=IqYeRFQyKmIse1xD5qA8MUPMadljfjLBbzYayWw6AtQ%3D&reserved=0
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542823006545&sdata=5VexoocnThIqHb1XE5tl%2BFl6awXBdtxBIPVrXX9r5LI%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C4fbab457c2f44cd240d908d6f2f7a7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636963542823006545&sdata=5VexoocnThIqHb1XE5tl%2BFl6awXBdtxBIPVrXX9r5LI%3D&reserved=0>*
Re: 0.9.6 Release
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Alex,
I don't see any answer here - can I start with trying your instruction and
start release ?
Thanks,
Piotr
śr., 12 cze 2019 o 10:12 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Alex,
> just build from scratch right now and seems maven and ant was ok
>
> El mié., 12 jun. 2019 a las 10:02, Alex Harui (<ah...@adobe.com.invalid>)
> escribió:
>
> > The merge is complete, and the main builds seem to be successful, except
> > for Maven on royale-asjs which was failing before the merge.
> >
> > I'm still catching up on other things, but I think there are some bugs we
> > need to fix before cutting the release? I think ASDoc may not be fully
> > working? What else?
> >
> > -Alex
> >
> > On 6/10/19, 11:05 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
> >
> > Hi Alex,
> >
> > Many thanks for that! I will try to be RM. I will have some dedicated
> > time
> > for that. I will wait for your instruction and merge to develop.
> >
> > Thanks,
> > Piotr
> >
> >
> > On Mon, Jun 10, 2019, 7:31 PM Alex Harui <ah...@adobe.com.invalid>
> > wrote:
> >
> > > Well, that turned out to be much more time-consuming than I
> > expected, but
> > > we can now create identical release artifacts on Mac and Win. I am
> > hopeful
> > > this effort will pay off not only now in having other folks
> generate
> > > releases, but also in the future if signed binaries become a
> > requirement.
> > >
> > > There continues to be a lot of distractions in my life that can
> cause
> > > delays, but I hope to merge the release_practice branches into
> > develop over
> > > the next day or two and figure out where in the wiki to document
> the
> > > release process. So, now is the time for one or more people to
> step
> > up to
> > > be the RMs for 0.9.6 and help debug and improve the process.
> > >
> > > I am going to try very hard not to "own" the process. If something
> > goes
> > > wrong, I am going to ask others to try to debug and fix it first
> > because it
> > > is in the project's best interests for others to truly understand
> > how this
> > > stuff works.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> > >
> > > It has turned out to be harder than expected to get the same
> > binaries
> > > on Mac and Win. I now have the identical binaries for
> > royale-compiler and
> > > royale-typedefs Maven artifacts and am starting on royale-asjs. I
> > might
> > > get lucky and the changes that fixed royale-typedefs SWCs will
> > magically
> > > get the royale-asjs SWCs to match. Then we have to make the Ant
> > artifacts
> > > match.
> > >
> > > There have been a lot of distractions in my non-work life which
> > has
> > > also impeded progress. I hope to make much progress this coming
> > week and
> > > if we're lucky, I will be asking for a volunteer (or volunteers) to
> > test
> > > drive all of this stuff and be the RM for 0.9.6. I am not going to
> > be the
> > > RM.
> > >
> > > -Alex
> > >
> > > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <
> piotrzarzycki21@gmail.com
> > >
> > > wrote:
> > >
> > > Hi Alex,
> > >
> > > It's been a while since you have started effort with
> > automating
> > > build.
> > > Where are you with that ? Are we closer to started 0.9.6.
> Do
> > you
> > > need any
> > > help with this ?
> > >
> > > Thanks,
> > > Piotr
> > >
> > > wt., 2 kwi 2019 o 19:30 Alex Harui
> <aharui@adobe.com.invalid
> > >
> > > napisał(a):
> > >
> > > > Update:
> > > >
> > > > In order to make verification of binary release packages
> > created
> > > on the
> > > > server easier, I have made changes to our build scripts
> and
> > > tools to try to
> > > > generate reproducible binaries. I've seen two different
> > builds
> > > compare on
> > > > my Mac. The next challenge will be to see if the server
> > can
> > > build a
> > > > package on Windows that will compare on Mac.
> > > >
> > > > One of the changes I needed to make is to JBurg. The
> > version of
> > > JBurg we
> > > > use generates method names including a hash that doesn't
> > > reproduce the same
> > > > name each time. I have changes to JBurg ready, however
> > JBurg is
> > > currently
> > > > under CPL which is category B. We only need one file, we
> > don't
> > > need or
> > > > want all of JBurg at this time. The one JBurg file is
> > jointly
> > > owned by
> > > > Adobe and Tom Harwood. I've contact Tom and he will be
> > filing
> > > an ICLA and
> > > > has given me permission to commit the lines he owns in
> > that one
> > > file.
> > > >
> > > > This is the revision of the file that will be donated by
> > > Tom/Adobe.
> > > >
> > > >
> > >
> >
> https://sourceforge.net/p/jburg/code/ci/66c287943376a74ac791f3d3bf969ab160bf80ff/tree/src/generator/jburg/burg/JBurgGenerator.java
> > > >
> > > > Once this file goes in with the changes to keep the
> method
> > names
> > > the same,
> > > > there will be more tweaks to the release tasks and then
> we
> > can
> > > try cutting
> > > > a release. I'm thinking we'll be at that point in early
> > May, so
> > > now is the
> > > > time to get stuff in for the 0.9.6 release.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com>
> wrote:
> > > >
> > > > I would much rather have others find and fix issues
> > > themselves. That
> > > > way, more people than just me will know how to maintain
> the
> > > system. It
> > > > actually turns out that, IMO, a group of people can work
> > on the
> > > release.
> > > > There are 14 steps. Literally, 14 different people could
> > > execute one step
> > > > each.
> > > >
> > > > My 2 cents,
> > > > -Alex
> > > >
> > > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > > wrote:
> > > >
> > > > Hi Alex,
> > > >
> > > > amazing work! congrats to reach to this point! :)
> > > >
> > > > I need to put my head on all of this, but count
> on
> > me to
> > > be a RM.
> > > > I think
> > > > the best thing should be that you be the first RM
> > to try
> > > your own
> > > > development at least for the first time, and then
> > the
> > > rest of us
> > > > will
> > > > follow you on the next releases. With all this on
> > place
> > > we maybe
> > > > could
> > > > release once a month or every two months...
> > > >
> > > > Thanks for doing this :)
> > > >
> > > > Carlos
> > > >
> > > >
> > > > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > > > (<ah...@adobe.com.invalid>)
> > > > escribió:
> > > >
> > > > > OK, I've now seen Jenkins perform the steps to
> > build
> > > the release
> > > > > artifacts. Folks interested in Docker-izing
> the
> > steps
> > > are
> > > > welcome to look
> > > > > at the jobs on the "Royale Release" tab on the
> CI
> > > server.
> > > > >
> > > >
> > >
> >
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/
> > > > >
> > > > > These steps assume that the RM can run the
> basic
> > Maven
> > > and Ant
> > > > build on
> > > > > the RM's computer. I think that's a fair
> > requirement
> > > since all
> > > > of us on the
> > > > > PMC need to able to do that to build the RC in
> > order
> > > to vote on
> > > > it.
> > > > > Jenkins does other tasks like run the Maven
> > release
> > > plugin
> > > > steps.
> > > > >
> > > > > Currently that results in binaries on Jenkins
> > that are
> > > > downloaded to the
> > > > > RM's computer. These binaries need to be
> > verified by
> > > the RM
> > > > which is the
> > > > > next phase I will be starting on now. The RM
> > verifies
> > > the bits
> > > > and then
> > > > > PGP signs them. And then the bits are uploaded
> > off
> > > the RM's
> > > > computer to
> > > > > Maven Staging or dist.a.o/dev. If that
> > uploading
> > > turns out to
> > > > be a point
> > > > > of failure, we have the option of having
> Jenkins
> > > upload the big
> > > > files and
> > > > > have the RM only upload PGP signature files.
> Or
> > > finding a way
> > > > for Jenkins
> > > > > to get the signature files from the RM. The
> > uploads
> > > worked fine
> > > > for me,
> > > > > but then again, so did the old script's
> uploads.
> > > > >
> > > > > Therefore, once I get the binary verification
> > phase
> > > completed, I
> > > > think
> > > > > someone other than me should be the RM and try
> > to use
> > > these
> > > > steps to
> > > > > generate the release and help debug the process
> > for
> > > the next
> > > > RM. So,
> > > > > please try to carve out some time to be the RM.
> > One
> > > advantage
> > > > of doing
> > > > > most of the work on Jenkins is that it frees up
> > my
> > > computer to
> > > > do other
> > > > > things while Jenkins is cranking away.
> > > > >
> > > > > I think we're at least a week away from binary
> > > verification,
> > > > maybe two, so
> > > > > it is time to start thinking about what is
> going
> > in
> > > this release.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 3/7/19, 4:15 PM, "Alex Harui"
> > > <ah...@adobe.com.INVALID>
> > > > wrote:
> > > > >
> > > > > In case you haven't guessed, I'm testing
> out
> > > Jenkins and its
> > > > ability
> > > > > to create the artifacts and send emails.
> Please
> > > ignore any
> > > > email that
> > > > > looks like a vote or discuss thread.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 2/10/19, 8:44 PM, "Alex Harui"
> > > <ah...@adobe.com.INVALID>
> > > > wrote:
> > > > >
> > > > > Om,
> > > > >
> > > > > Well, that's what I used for the last
> > > release. I'm sure
> > > > there is
> > > > > probably some inaccuracy in it.
> > > > >
> > > > > That said, I'm abandoning that document
> > and
> > > taking a new
> > > > angle
> > > > > because that document presumed that the release
> > > manager was
> > > > trying to
> > > > > create a release on his/her computer. I've
> > given up
> > > on that and
> > > > working on
> > > > > making releases from a shared computer for the
> > reasons
> > > I've
> > > > stated
> > > > > upthread. I hope to make some progress on that
> > this
> > > week.
> > > > >
> > > > > The key difference is that the new
> angle
> > does
> > > not
> > > > presume that you
> > > > > have Git SSH and PGP signatures all set up on
> > some
> > > computer. I
> > > > have not
> > > > > looked into how Docker would handle that. You
> > > certainly
> > > > wouldn't want the
> > > > > Docker image to contain your SSH or PGP
> > keys/creds.
> > > And if the
> > > > Docker
> > > > > image doesn't, then that is another stumbling
> > block
> > > for future
> > > > RMs.
> > > > >
> > > > > The other key difference is that the
> old
> > > script presumed
> > > > you could
> > > > > create the 3 release in 3 huge "easy" steps.
> > We've
> > > seen that is
> > > > only true
> > > > > for me. So the new angle creates many discrete
> > steps
> > > managed by
> > > > Jenkins.
> > > > >
> > > > > So, it is up to you to decide what you
> > want to
> > > > "Docker-ize". You
> > > > > can try to Docker-ize the current 3 big steps,
> > so RMs
> > > can try to
> > > > run it on
> > > > > their systems, but I'd bet they will just faiI
> > due to
> > > network
> > > > issues. I
> > > > > would be interested in using Docker to make
> each
> > of
> > > these many
> > > > discrete
> > > > > steps portable to another server. I'm not
> > going to
> > > involve
> > > > Docker at this
> > > > > point. My main goal is just to see if I can
> > create a
> > > workflow
> > > > of many
> > > > > discrete steps that isn't horribly painful.
> > Once we
> > > see what
> > > > these steps
> > > > > turn out to be, then we can worry about server
> > > portability of
> > > > those steps.
> > > > >
> > > > > Either way, we want to know about
> running
> > > > Browser+Selenium for
> > > > > sure. And maybe FlashPlayerDebugger or AIR. I
> > would
> > > want to
> > > > know, for
> > > > > example, how you debug a failing checkintest
> in a
> > > Docker
> > > > container.
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > >
> > > > > On 2/10/19, 5:18 PM, "OmPrakash
> > Muppirala" <
> > > > bigosmallm@gmail.com>
> > > > > wrote:
> > > > >
> > > > > Alex,
> > > > >
> > > > > Just to be clear, I am following
> the
> > steps
> > > from here
> > > > to try
> > > > > and setup a
> > > > > docker container.
> > > > >
> > > > >
> > > > >
> > > >
> > > https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
> > > > >
> > > > > Is this doc up to date?
> > > > >
> > > > > Thanks,
> > > > > Om
> > > > >
> > > > > On Wed, Feb 6, 2019 at 12:02 PM
> > OmPrakash
> > > Muppirala <
> > > > > bigosmallm@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > One approach is to have each step
> > in the
> > > process
> > > > spin up a
> > > > > docker image.
> > > > > > And use docker-compose to run
> each
> > > step. All the
> > > > images can
> > > > > be made to
> > > > > > share a common volume where all
> the
> > > artifacts are
> > > > stored
> > > > > across steps.
> > > > > >
> > > > > > You are right about the
> networking
> > issue
> > > though.
> > > > Any
> > > > > network related
> > > > > > failure that occurs on the host
> > machine
> > > will most
> > > > likely
> > > > > occur in the
> > > > > > docker container. Although, I am
> > not
> > > clear how we
> > > > can
> > > > > guarantee that the
> > > > > > same issues will not occur on the
> > > Jenkins server.
> > > > I mean,
> > > > > what is special
> > > > > > about the Jenkins server that
> > makes it
> > > immune to
> > > > these
> > > > > networking issues?
> > > > > >
> > > > > > Thanks,
> > > > > > Om
> > > > > >
> > > > > > On Wed, Feb 6, 2019 at 11:48 AM
> > Alex
> > > Harui
> > > > > <ah...@adobe.com.invalid>
> > > > > > wrote:
> > > > > >
> > > > > >> Again, I don't know anything
> about
> > > Docker, but
> > > > before we
> > > > > spend a lot of
> > > > > >> time on Docker, I also want to
> > point
> > > out that the
> > > > process
> > > > > to create a
> > > > > >> release cannot really be thought
> > of as
> > > "one
> > > > application".
> > > > > It will be a
> > > > > >> series of "steps" to run. How
> > many
> > > steps
> > > > depends on
> > > > > whether we think we
> > > > > >> can isolate enough stuff via
> > Docker to
> > > be able to
> > > > run
> > > > > Docker on the RM's
> > > > > >> computer instead of some shared
> > > computer. On a
> > > > shared
> > > > > computer there will
> > > > > >> be dozens of steps because the
> RM
> > will
> > > need to
> > > > enter
> > > > > passwords to commit
> > > > > >> stuff. On a local computer I
> > guess the
> > > RM can
> > > > supply
> > > > > passwords but I think
> > > > > >> there will be stopping points
> > where the
> > > Maven
> > > > artifacts are
> > > > > deployed and
> > > > > >> the staging repo is closed, and
> > another
> > > stopping
> > > > point for
> > > > > the vote. It
> > > > > >> seems like Docker works by
> > downloading
> > > > dependencies. Given
> > > > > that the
> > > > > >> problem the RMs had last time
> > involved
> > > downloads
> > > > and
> > > > > uploads, why do we
> > > > > >> think Docker will really solve
> > this for
> > > creating
> > > > releases
> > > > > on local machines?
> > > > > >>
> > > > > >> The reason to do this on a
> shared
> > > machine is so
> > > > that new
> > > > > RMs don't have
> > > > > >> to do as much setup. But then I
> > wonder
> > > about the
> > > > > efficiency of kicking off
> > > > > >> that many Docker images.
> Jenkins
> > can
> > > manage that
> > > > already.
> > > > > Does Docker
> > > > > >> have some sort of similar
> > Dashboard or
> > > would we
> > > > use Jenkins
> > > > > to kick off
> > > > > >> Docker steps? I can't quite
> > picture
> > > what is the
> > > > outermost
> > > > > >> control/dashboard.
> > > > > >>
> > > > > >> -Alex
> > > > > >>
> > > > > >> On 2/6/19, 11:03 AM, "Harbs" <
> > > > harbs.lists@gmail.com> wrote:
> > > > > >>
> > > > > >> A quick search turns up
> this:
> > > > > >>
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > > https://codingsans.com/blog/selenium-with-docker-testing
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > > https://codingsans.com/blog/selenium-with-docker-testing
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > >
> https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > > https://github.com/SeleniumHQ/docker-selenium
> > > > > >> <
> > > > > >>
> > > > >
> > > >
> > > https://github.com/SeleniumHQ/docker-selenium
> > > > > >> >
> > > > > >>
> > > > > >> > On Feb 6, 2019, at 8:59
> PM,
> > Alex
> > > Harui
> > > > > <ah...@adobe.com.INVALID>
> > > > > >> wrote:
> > > > > >> >
> > > > > >> > Thanks for volunteering to
> > try it
> > > Om. IMO,
> > > > even more
> > > > > important
> > > > > >> than Firefox+Flash is
> > > SomeBrowser+Selenium. We
> > > > may also
> > > > > need to run Adobe
> > > > > >> AIR's adb. We could probably
> > turn off
> > > the Flash
> > > > tests or
> > > > > replace Flash
> > > > > >> with AIR.
> > > > > >> >
> > > > > >> > Thanks,
> > > > > >> > -Alex
> > > > > >> >
> > > > > >> > On 2/6/19, 10:54 AM,
> "Carlos
> > > Rovira" <
> > > > > carlosrovira@apache.org>
> > > > > >> wrote:
> > > > > >> >
> > > > > >> > Hi Om, that would be
> > great!
> > > waiting for
> > > > your
> > > > > experience with a
> > > > > >> that! :)
> > > > > >> >
> > > > > >> > El mié., 6 feb. 2019 a
> > las
> > > 19:31,
> > > > OmPrakash
> > > > > Muppirala (<
> > > > > >> bigosmallm@gmail.com>)
> > > > > >> > escribió:
> > > > > >> >
> > > > > >> >> Yes, I agree with Alex
> > about not
> > > being
> > > > able to run
> > > > > UI out of docker
> > > > > >> >> containers. I never
> > thought of
> > > the
> > > > checkintests
> > > > > when I made the
> > > > > >> >> suggestion.
> > > > > >> >>
> > > > > >> >> The firefox-flash image
> > that
> > > Yishay
> > > > pointed out
> > > > > looks promising.
> > > > > >> I will
> > > > > >> >> poke around with it and
> > see if
> > > that works
> > > > for us.
> > > > > >> >>
> > > > > >> >> Thanks,
> > > > > >> >> Om
> > > > > >> >>
> > > > > >> >> On Wed, Feb 6, 2019 at
> > 12:41 AM
> > > Yishay
> > > > Weiss <
> > > > > >> yishayjobs@hotmail.com>
> > > > > >> >> wrote:
> > > > > >> >>
> > > > > >> >>> I’ll let Om or someone
> > else
> > > with docker
> > > > experience
> > > > > tell us if
> > > > > >> this [1] is
> > > > > >> >>> relevant.
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>> [1]
> > > > > >>
> > > > >
> > > >
> > > https://hub.docker.com/r/beli/firefox-flash/
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>>
> > ________________________________
> > > > > >> >>> From: Alex Harui
> > > <aharui@adobe.com.INVALID
> > > > >
> > > > > >> >>> Sent: Wednesday,
> February
> > 6,
> > > 2019
> > > > 10:05:54 AM
> > > > > >> >>> To:
> dev@royale.apache.org
> > > > > >> >>> Subject: Re: 0.9.6
> Release
> > > > > >> >>>
> > > > > >> >>> I don't anything about
> > docker,
> > > but in 15
> > > > minutes of
> > > > > reading I ran
> > > > > >> into
> > > > > >> >>> this:
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://www.channelfutures.com/open-source/when-not-to-use-docker-understanding-the-limitations-of-containers
> > > > > >> >>>
> > > > > >> >>> Which says: Docker can't
> > " Run
> > > > applications with
> > > > > graphical
> > > > > >> interfaces".
> > > > > >> >>> If you want Royale to
> use
> > > Docker for
> > > > releases, show
> > > > > that it can
> > > > > >> run
> > > > > >> >>> checkintests with Flash
> > and the
> > > Browser.
> > > > Then I
> > > > > will look into
> > > > > >> it more.
> > > > > >> >>>
> > > > > >> >>> The highest level goal
> is
> > to
> > > make it as
> > > > easy as
> > > > > possible for
> > > > > >> someone to
> > > > > >> >>> volunteer to be an RM.
> > Any
> > > requirement
> > > > of "install
> > > > > this (Docker,
> > > > > >> etc) on
> > > > > >> >>> your computer" is, IMO,
> > another
> > > barrier
> > > > to entry.
> > > > > Yeah, RMs will
> > > > > >> have to
> > > > > >> >>> have Maven installed and
> > maybe
> > > Ant, but
> > > > you should
> > > > > already have
> > > > > >> those
> > > > > >> >>> installed to be a
> > committer/PMC
> > > member.
> > > > > >> >>>
> > > > > >> >>> That said, a good
> > takeaway from
> > > the
> > > > Docker idea is
> > > > > to try to find
> > > > > >> a way
> > > > > >> >> to
> > > > > >> >>> make an "Image" of
> > whatever we
> > > end up
> > > > with on
> > > > > whatever server we
> > > > > >> end up
> > > > > >> >>> using so if the image
> can
> > be
> > > copied and
> > > > used on
> > > > > other servers.
> > > > > >> I'm not
> > > > > >> >>> exactly sure how to do
> > that
> > > with Azure,
> > > > which hosts
> > > > > my CI
> > > > > >> server. I will
> > > > > >> >>> spend a few more minutes
> > > researching that.
> > > > > >> >>>
> > > > > >> >>> I could not quickly find
> > any
> > > way to get a
> > > > free VM
> > > > > on Azure or AWS
> > > > > >> that
> > > > > >> >>> isn't a
> > > > free-trial-start-paying-after-a-year. So,
> > > > > unless someone
> > > > > >> comes
> > > > > >> >> up
> > > > > >> >>> with a free server we
> can
> > use
> > > "forever",
> > > > I'm going
> > > > > to just start
> > > > > >> with my
> > > > > >> >>> Azure VM.
> > > > > >> >>>
> > > > > >> >>> -Alex
> > > > > >> >>>
> > > > > >> >>> On 2/5/19, 10:59 PM,
> > "Carlos
> > > Rovira" <
> > > > > carlosrovira@apache.org>
> > > > > >> wrote:
> > > > > >> >>>
> > > > > >> >>> Hi.
> > > > > >> >>>
> > > > > >> >>> the plan sounds very
> > good to
> > > me. Just
> > > > my 2
> > > > > thoughts on this:
> > > > > >> >>>
> > > > > >> >>> 1.- As I was reading
> I
> > was
> > > thinking as
> > > > well on
> > > > > something like
> > > > > >> Docker
> > > > > >> >>> and
> > > > > >> >>> see Om as well
> > thinking on
> > > the same.
> > > > Maybe is
> > > > > the way to this
> > > > > >> with
> > > > > >> >> the
> > > > > >> >>> actual technology.
> > Seems VMs
> > > are
> > > > stepping out a
> > > > > bit this days
> > > > > >> in
> > > > > >> >> favor
> > > > > >> >>> of
> > > > > >> >>> things like Docker.
> > Maybe
> > > the same did
> > > > Git over
> > > > > Svn, and today
> > > > > >> Svn is
> > > > > >> >>> an
> > > > > >> >>> old remembrance. I
> > must say
> > > that I
> > > > have no
> > > > > experience with
> > > > > >> Docker, so
> > > > > >> >>> doing
> > > > > >> >>> that will require
> > acquire
> > > that
> > > > knowledge, but
> > > > > seems it could
> > > > > >> be worth
> > > > > >> >>> it.
> > > > > >> >>>
> > > > > >> >>> 2.- Maybe is not
> > possible,
> > > but I want
> > > > to propose
> > > > > to do this
> > > > > >> work I a
> > > > > >> >>> separate branch, so
> it
> > could
> > > be in
> > > > parallel to
> > > > > other
> > > > > >> developments. I
> > > > > >> >>> think
> > > > > >> >>> work over develop is
> > > practical if
> > > > there's
> > > > > something tiny that
> > > > > >> could
> > > > > >> >> be
> > > > > >> >>> done
> > > > > >> >>> in a commit. But as
> we
> > need
> > > more than
> > > > one, or is
> > > > > a long
> > > > > >> process (like
> > > > > >> >>> this), chances are to
> > make
> > > develop
> > > > branch
> > > > > unstable and even
> > > > > >> for some
> > > > > >> >>> days.
> > > > > >> >>> I think we should try
> > to
> > > avoid that
> > > > scenario,
> > > > > and branches are
> > > > > >> the
> > > > > >> >> best
> > > > > >> >>> way. If we do this
> way,
> > > we'll benefit
> > > > of more
> > > > > reliable develop
> > > > > >> >> branch.
> > > > > >> >>>
> > > > > >> >>> Thanks and good to
> > know of
> > > this plan :)
> > > > > >> >>>
> > > > > >> >>> Carlos
> > > > > >> >>>
> > > > > >> >>>
> > > > > >> >>> El mar., 5 feb. 2019
> a
> > las
> > > 23:19,
> > > > Harbs (<
> > > > > >> harbs.lists@gmail.com>)
> > > > > >> >>> escribió:
> > > > > >> >>>
> > > > > >> >>>> I’ve never used Docker
> > myself,
> > > but that
> > > > might be a
> > > > > good plan.
> > > > > >> >>>>
> > > > > >> >>>>> On Feb 6, 2019, at
> > 12:07 AM,
> > > OmPrakash
> > > > Muppirala <
> > > > > >> >>> bigosmallm@gmail.com>
> > > > > >> >>>> wrote:
> > > > > >> >>>>>
> > > > > >> >>>>> I was wondering if we
> > can use
> > > docker
> > > > images to
> > > > > setup and seal
> > > > > >> the
> > > > > >> >>> RM
> > > > > >> >>>>> environment. Then
> > other RMs
> > > simply
> > > > need to run
> > > > > the image
> > > > > >> locally
> > > > > >> >>> and run
> > > > > >> >>>>> the release scripts.
> > Might
> > > be easier.
> > > > If folks
> > > > > like this plan,
> > > > > >> >> I
> > > > > >> >>> can
> > > > > >> >>>> try
> > > > > >> >>>>> to put something
> > together.
> > > > > >> >>>>>
> > > > > >> >>>>> Thanks,
> > > > > >> >>>>> Om
> > > > > >> >>>>>
> > > > > >> >>>>> On Tue, Feb 5, 2019 at
> > 1:40
> > > PM Harbs <
> > > > > harbs.lists@gmail.com>
> > > > > >> >>> wrote:
> > > > > >> >>>>>
> > > > > >> >>>>>> In a recent
> > discussion, it
> > > looks like
> > > > other
> > > > > projects have
> > > > > >> gotten
> > > > > >> >>>> resources
> > > > > >> >>>>>> from AWS.
> > > > > >> >>>>>>
> > > > > >> >>>>>> Whatever service we
> > use,
> > > could setup a
> > > > “shared”
> > > > > Royale account
> > > > > >> >>> that all
> > > > > >> >>>>>> PMC members could
> have
> > > access to.
> > > > > >> >>>>>>
> > > > > >> >>>>>> I don’t know if
> > there’s some
> > > way we
> > > > could
> > > > > leverage Gitlab’s
> > > > > >> >>> integration
> > > > > >> >>>>>> pipelines
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > > https://docs.gitlab.com/ee/ci/README.html
> > > > > >> >>> <
> > > > > >> >>>>>>
> > > > > >> >>>
> > > > > >> >>
> > > > > >>
> > > > >
> > > >
> > > https://docs.gitlab.com/ee/ci/README.html
> > > > > >> >>>>
> > > > > >> >>>>>>
> > > > > >> >>>>>>> On Feb 5, 2019, at
> > 11:33
> > > PM, Alex
> > > > Harui
> > > > > >> >> <aharui@adobe.com.INVALID
> > > > > >> >>>>
> > > > > >> >>>>>> wrote:
> > > > > >> >>>>>>>
> > > > > >> >>>>>>> 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" <
> > > > > >> >>
> piotrzarzycki21@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.lists@gmail.com
> > > > > >> >>> wrote:
> > > > > >> >>>>>>>
> > > > > >> >>>>>>>> A big +1 from me!
> > > > > >> >>>>>>>>
> > > > > >> >>>>>>>> Looking forward!
> > > > > >> >>>>>>>>
> > > > > >> >>>>>>>>> On Feb 5, 2019, at
> > 9:34
> > > PM, Alex
> > > > Harui
> > > > > >> >>>
> <aharui@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
> > > > >
> >
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: 0.9.6 Release
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,
just build from scratch right now and seems maven and ant was ok
El mié., 12 jun. 2019 a las 10:02, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> The merge is complete, and the main builds seem to be successful, except
> for Maven on royale-asjs which was failing before the merge.
>
> I'm still catching up on other things, but I think there are some bugs we
> need to fix before cutting the release? I think ASDoc may not be fully
> working? What else?
>
> -Alex
>
> On 6/10/19, 11:05 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> Hi Alex,
>
> Many thanks for that! I will try to be RM. I will have some dedicated
> time
> for that. I will wait for your instruction and merge to develop.
>
> Thanks,
> Piotr
>
>
> On Mon, Jun 10, 2019, 7:31 PM Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
> > Well, that turned out to be much more time-consuming than I
> expected, but
> > we can now create identical release artifacts on Mac and Win. I am
> hopeful
> > this effort will pay off not only now in having other folks generate
> > releases, but also in the future if signed binaries become a
> requirement.
> >
> > There continues to be a lot of distractions in my life that can cause
> > delays, but I hope to merge the release_practice branches into
> develop over
> > the next day or two and figure out where in the wiki to document the
> > release process. So, now is the time for one or more people to step
> up to
> > be the RMs for 0.9.6 and help debug and improve the process.
> >
> > I am going to try very hard not to "own" the process. If something
> goes
> > wrong, I am going to ask others to try to debug and fix it first
> because it
> > is in the project's best interests for others to truly understand
> how this
> > stuff works.
> >
> > Thanks,
> > -Alex
> >
> > On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> >
> > It has turned out to be harder than expected to get the same
> binaries
> > on Mac and Win. I now have the identical binaries for
> royale-compiler and
> > royale-typedefs Maven artifacts and am starting on royale-asjs. I
> might
> > get lucky and the changes that fixed royale-typedefs SWCs will
> magically
> > get the royale-asjs SWCs to match. Then we have to make the Ant
> artifacts
> > match.
> >
> > There have been a lot of distractions in my non-work life which
> has
> > also impeded progress. I hope to make much progress this coming
> week and
> > if we're lucky, I will be asking for a volunteer (or volunteers) to
> test
> > drive all of this stuff and be the RM for 0.9.6. I am not going to
> be the
> > RM.
> >
> > -Alex
> >
> > On 5/23/19, 9:39 AM, "Piotr Zarzycki" <piotrzarzycki21@gmail.com
> >
> > wrote:
> >
> > Hi Alex,
> >
> > It's been a while since you have started effort with
> automating
> > build.
> > Where are you with that ? Are we closer to started 0.9.6. Do
> you
> > need any
> > help with this ?
> >
> > Thanks,
> > Piotr
> >
> > wt., 2 kwi 2019 o 19:30 Alex Harui <aharui@adobe.com.invalid
> >
> > napisał(a):
> >
> > > Update:
> > >
> > > In order to make verification of binary release packages
> created
> > on the
> > > server easier, I have made changes to our build scripts and
> > tools to try to
> > > generate reproducible binaries. I've seen two different
> builds
> > compare on
> > > my Mac. The next challenge will be to see if the server
> can
> > build a
> > > package on Windows that will compare on Mac.
> > >
> > > One of the changes I needed to make is to JBurg. The
> version of
> > JBurg we
> > > use generates method names including a hash that doesn't
> > reproduce the same
> > > name each time. I have changes to JBurg ready, however
> JBurg is
> > currently
> > > under CPL which is category B. We only need one file, we
> don't
> > need or
> > > want all of JBurg at this time. The one JBurg file is
> jointly
> > owned by
> > > Adobe and Tom Harwood. I've contact Tom and he will be
> filing
> > an ICLA and
> > > has given me permission to commit the lines he owns in
> that one
> > file.
> > >
> > > This is the revision of the file that will be donated by
> > Tom/Adobe.
> > >
> > >
> >
> https://sourceforge.net/p/jburg/code/ci/66c287943376a74ac791f3d3bf969ab160bf80ff/tree/src/generator/jburg/burg/JBurgGenerator.java
> > >
> > > Once this file goes in with the changes to keep the method
> names
> > the same,
> > > there will be more tweaks to the release tasks and then we
> can
> > try cutting
> > > a release. I'm thinking we'll be at that point in early
> May, so
> > now is the
> > > time to get stuff in for the 0.9.6 release.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com> wrote:
> > >
> > > I would much rather have others find and fix issues
> > themselves. That
> > > way, more people than just me will know how to maintain the
> > system. It
> > > actually turns out that, IMO, a group of people can work
> on the
> > release.
> > > There are 14 steps. Literally, 14 different people could
> > execute one step
> > > each.
> > >
> > > My 2 cents,
> > > -Alex
> > >
> > > On 3/8/19, 2:13 AM, "Carlos Rovira" <
> carlosrovira@apache.org>
> > wrote:
> > >
> > > Hi Alex,
> > >
> > > amazing work! congrats to reach to this point! :)
> > >
> > > I need to put my head on all of this, but count on
> me to
> > be a RM.
> > > I think
> > > the best thing should be that you be the first RM
> to try
> > your own
> > > development at least for the first time, and then
> the
> > rest of us
> > > will
> > > follow you on the next releases. With all this on
> place
> > we maybe
> > > could
> > > release once a month or every two months...
> > >
> > > Thanks for doing this :)
> > >
> > > Carlos
> > >
> > >
> > > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > > (<ah...@adobe.com.invalid>)
> > > escribió:
> > >
> > > > OK, I've now seen Jenkins perform the steps to
> build
> > the release
> > > > artifacts. Folks interested in Docker-izing the
> steps
> > are
> > > welcome to look
> > > > at the jobs on the "Royale Release" tab on the CI
> > server.
> > > >
> > >
> >
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/
> > > >
> > > > These steps assume that the RM can run the basic
> Maven
> > and Ant
> > > build on
> > > > the RM's computer. I think that's a fair
> requirement
> > since all
> > > of us on the
> > > > PMC need to able to do that to build the RC in
> order
> > to vote on
> > > it.
> > > > Jenkins does other tasks like run the Maven
> release
> > plugin
> > > steps.
> > > >
> > > > Currently that results in binaries on Jenkins
> that are
> > > downloaded to the
> > > > RM's computer. These binaries need to be
> verified by
> > the RM
> > > which is the
> > > > next phase I will be starting on now. The RM
> verifies
> > the bits
> > > and then
> > > > PGP signs them. And then the bits are uploaded
> off
> > the RM's
> > > computer to
> > > > Maven Staging or dist.a.o/dev. If that
> uploading
> > turns out to
> > > be a point
> > > > of failure, we have the option of having Jenkins
> > upload the big
> > > files and
> > > > have the RM only upload PGP signature files. Or
> > finding a way
> > > for Jenkins
> > > > to get the signature files from the RM. The
> uploads
> > worked fine
> > > for me,
> > > > but then again, so did the old script's uploads.
> > > >
> > > > Therefore, once I get the binary verification
> phase
> > completed, I
> > > think
> > > > someone other than me should be the RM and try
> to use
> > these
> > > steps to
> > > > generate the release and help debug the process
> for
> > the next
> > > RM. So,
> > > > please try to carve out some time to be the RM.
> One
> > advantage
> > > of doing
> > > > most of the work on Jenkins is that it frees up
> my
> > computer to
> > > do other
> > > > things while Jenkins is cranking away.
> > > >
> > > > I think we're at least a week away from binary
> > verification,
> > > maybe two, so
> > > > it is time to start thinking about what is going
> in
> > this release.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 3/7/19, 4:15 PM, "Alex Harui"
> > <ah...@adobe.com.INVALID>
> > > wrote:
> > > >
> > > > In case you haven't guessed, I'm testing out
> > Jenkins and its
> > > ability
> > > > to create the artifacts and send emails. Please
> > ignore any
> > > email that
> > > > looks like a vote or discuss thread.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > > On 2/10/19, 8:44 PM, "Alex Harui"
> > <ah...@adobe.com.INVALID>
> > > wrote:
> > > >
> > > > Om,
> > > >
> > > > Well, that's what I used for the last
> > release. I'm sure
> > > there is
> > > > probably some inaccuracy in it.
> > > >
> > > > That said, I'm abandoning that document
> and
> > taking a new
> > > angle
> > > > because that document presumed that the release
> > manager was
> > > trying to
> > > > create a release on his/her computer. I've
> given up
> > on that and
> > > working on
> > > > making releases from a shared computer for the
> reasons
> > I've
> > > stated
> > > > upthread. I hope to make some progress on that
> this
> > week.
> > > >
> > > > The key difference is that the new angle
> does
> > not
> > > presume that you
> > > > have Git SSH and PGP signatures all set up on
> some
> > computer. I
> > > have not
> > > > looked into how Docker would handle that. You
> > certainly
> > > wouldn't want the
> > > > Docker image to contain your SSH or PGP
> keys/creds.
> > And if the
> > > Docker
> > > > image doesn't, then that is another stumbling
> block
> > for future
> > > RMs.
> > > >
> > > > The other key difference is that the old
> > script presumed
> > > you could
> > > > create the 3 release in 3 huge "easy" steps.
> We've
> > seen that is
> > > only true
> > > > for me. So the new angle creates many discrete
> steps
> > managed by
> > > Jenkins.
> > > >
> > > > So, it is up to you to decide what you
> want to
> > > "Docker-ize". You
> > > > can try to Docker-ize the current 3 big steps,
> so RMs
> > can try to
> > > run it on
> > > > their systems, but I'd bet they will just faiI
> due to
> > network
> > > issues. I
> > > > would be interested in using Docker to make each
> of
> > these many
> > > discrete
> > > > steps portable to another server. I'm not
> going to
> > involve
> > > Docker at this
> > > > point. My main goal is just to see if I can
> create a
> > workflow
> > > of many
> > > > discrete steps that isn't horribly painful.
> Once we
> > see what
> > > these steps
> > > > turn out to be, then we can worry about server
> > portability of
> > > those steps.
> > > >
> > > > Either way, we want to know about running
> > > Browser+Selenium for
> > > > sure. And maybe FlashPlayerDebugger or AIR. I
> would
> > want to
> > > know, for
> > > > example, how you debug a failing checkintest in a
> > Docker
> > > container.
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > >
> > > > On 2/10/19, 5:18 PM, "OmPrakash
> Muppirala" <
> > > bigosmallm@gmail.com>
> > > > wrote:
> > > >
> > > > Alex,
> > > >
> > > > Just to be clear, I am following the
> steps
> > from here
> > > to try
> > > > and setup a
> > > > docker container.
> > > >
> > > >
> > > >
> > >
> > https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
> > > >
> > > > Is this doc up to date?
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Wed, Feb 6, 2019 at 12:02 PM
> OmPrakash
> > Muppirala <
> > > > bigosmallm@gmail.com>
> > > > wrote:
> > > >
> > > > > One approach is to have each step
> in the
> > process
> > > spin up a
> > > > docker image.
> > > > > And use docker-compose to run each
> > step. All the
> > > images can
> > > > be made to
> > > > > share a common volume where all the
> > artifacts are
> > > stored
> > > > across steps.
> > > > >
> > > > > You are right about the networking
> issue
> > though.
> > > Any
> > > > network related
> > > > > failure that occurs on the host
> machine
> > will most
> > > likely
> > > > occur in the
> > > > > docker container. Although, I am
> not
> > clear how we
> > > can
> > > > guarantee that the
> > > > > same issues will not occur on the
> > Jenkins server.
> > > I mean,
> > > > what is special
> > > > > about the Jenkins server that
> makes it
> > immune to
> > > these
> > > > networking issues?
> > > > >
> > > > > Thanks,
> > > > > Om
> > > > >
> > > > > On Wed, Feb 6, 2019 at 11:48 AM
> Alex
> > Harui
> > > > <ah...@adobe.com.invalid>
> > > > > wrote:
> > > > >
> > > > >> Again, I don't know anything about
> > Docker, but
> > > before we
> > > > spend a lot of
> > > > >> time on Docker, I also want to
> point
> > out that the
> > > process
> > > > to create a
> > > > >> release cannot really be thought
> of as
> > "one
> > > application".
> > > > It will be a
> > > > >> series of "steps" to run. How
> many
> > steps
> > > depends on
> > > > whether we think we
> > > > >> can isolate enough stuff via
> Docker to
> > be able to
> > > run
> > > > Docker on the RM's
> > > > >> computer instead of some shared
> > computer. On a
> > > shared
> > > > computer there will
> > > > >> be dozens of steps because the RM
> will
> > need to
> > > enter
> > > > passwords to commit
> > > > >> stuff. On a local computer I
> guess the
> > RM can
> > > supply
> > > > passwords but I think
> > > > >> there will be stopping points
> where the
> > Maven
> > > artifacts are
> > > > deployed and
> > > > >> the staging repo is closed, and
> another
> > stopping
> > > point for
> > > > the vote. It
> > > > >> seems like Docker works by
> downloading
> > > dependencies. Given
> > > > that the
> > > > >> problem the RMs had last time
> involved
> > downloads
> > > and
> > > > uploads, why do we
> > > > >> think Docker will really solve
> this for
> > creating
> > > releases
> > > > on local machines?
> > > > >>
> > > > >> The reason to do this on a shared
> > machine is so
> > > that new
> > > > RMs don't have
> > > > >> to do as much setup. But then I
> wonder
> > about the
> > > > efficiency of kicking off
> > > > >> that many Docker images. Jenkins
> can
> > manage that
> > > already.
> > > > Does Docker
> > > > >> have some sort of similar
> Dashboard or
> > would we
> > > use Jenkins
> > > > to kick off
> > > > >> Docker steps? I can't quite
> picture
> > what is the
> > > outermost
> > > > >> control/dashboard.
> > > > >>
> > > > >> -Alex
> > > > >>
> > > > >> On 2/6/19, 11:03 AM, "Harbs" <
> > > harbs.lists@gmail.com> wrote:
> > > > >>
> > > > >> A quick search turns up this:
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> > https://codingsans.com/blog/selenium-with-docker-testing
> > > > >> <
> > > > >>
> > > >
> > >
> > https://codingsans.com/blog/selenium-with-docker-testing
> > > > >> >
> > > > >>
> > > > >>
> > > >
> > >
> > https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker
> > > > >> <
> > > > >>
> > > >
> > >
> > https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker
> > > > >> >
> > > > >>
> > > > >>
> > > >
> > >
> > https://github.com/SeleniumHQ/docker-selenium
> > > > >> <
> > > > >>
> > > >
> > >
> > https://github.com/SeleniumHQ/docker-selenium
> > > > >> >
> > > > >>
> > > > >> > On Feb 6, 2019, at 8:59 PM,
> Alex
> > Harui
> > > > <ah...@adobe.com.INVALID>
> > > > >> wrote:
> > > > >> >
> > > > >> > Thanks for volunteering to
> try it
> > Om. IMO,
> > > even more
> > > > important
> > > > >> than Firefox+Flash is
> > SomeBrowser+Selenium. We
> > > may also
> > > > need to run Adobe
> > > > >> AIR's adb. We could probably
> turn off
> > the Flash
> > > tests or
> > > > replace Flash
> > > > >> with AIR.
> > > > >> >
> > > > >> > Thanks,
> > > > >> > -Alex
> > > > >> >
> > > > >> > On 2/6/19, 10:54 AM, "Carlos
> > Rovira" <
> > > > carlosrovira@apache.org>
> > > > >> wrote:
> > > > >> >
> > > > >> > Hi Om, that would be
> great!
> > waiting for
> > > your
> > > > experience with a
> > > > >> that! :)
> > > > >> >
> > > > >> > El mié., 6 feb. 2019 a
> las
> > 19:31,
> > > OmPrakash
> > > > Muppirala (<
> > > > >> bigosmallm@gmail.com>)
> > > > >> > escribió:
> > > > >> >
> > > > >> >> Yes, I agree with Alex
> about not
> > being
> > > able to run
> > > > UI out of docker
> > > > >> >> containers. I never
> thought of
> > the
> > > checkintests
> > > > when I made the
> > > > >> >> suggestion.
> > > > >> >>
> > > > >> >> The firefox-flash image
> that
> > Yishay
> > > pointed out
> > > > looks promising.
> > > > >> I will
> > > > >> >> poke around with it and
> see if
> > that works
> > > for us.
> > > > >> >>
> > > > >> >> Thanks,
> > > > >> >> Om
> > > > >> >>
> > > > >> >> On Wed, Feb 6, 2019 at
> 12:41 AM
> > Yishay
> > > Weiss <
> > > > >> yishayjobs@hotmail.com>
> > > > >> >> wrote:
> > > > >> >>
> > > > >> >>> I’ll let Om or someone
> else
> > with docker
> > > experience
> > > > tell us if
> > > > >> this [1] is
> > > > >> >>> relevant.
> > > > >> >>>
> > > > >> >>>
> > > > >> >>>
> > > > >> >>> [1]
> > > > >>
> > > >
> > >
> > https://hub.docker.com/r/beli/firefox-flash/
> > > > >> >>>
> > > > >> >>>
> > > > >> >>>
> > > > >> >>>
> ________________________________
> > > > >> >>> From: Alex Harui
> > <aharui@adobe.com.INVALID
> > > >
> > > > >> >>> Sent: Wednesday, February
> 6,
> > 2019
> > > 10:05:54 AM
> > > > >> >>> To: dev@royale.apache.org
> > > > >> >>> Subject: Re: 0.9.6 Release
> > > > >> >>>
> > > > >> >>> I don't anything about
> docker,
> > but in 15
> > > minutes of
> > > > reading I ran
> > > > >> into
> > > > >> >>> this:
> > > > >> >>>
> > > > >> >>>
> > > > >> >>
> > > > >>
> > > >
> > >
> >
> https://www.channelfutures.com/open-source/when-not-to-use-docker-understanding-the-limitations-of-containers
> > > > >> >>>
> > > > >> >>> Which says: Docker can't
> " Run
> > > applications with
> > > > graphical
> > > > >> interfaces".
> > > > >> >>> If you want Royale to use
> > Docker for
> > > releases, show
> > > > that it can
> > > > >> run
> > > > >> >>> checkintests with Flash
> and the
> > Browser.
> > > Then I
> > > > will look into
> > > > >> it more.
> > > > >> >>>
> > > > >> >>> The highest level goal is
> to
> > make it as
> > > easy as
> > > > possible for
> > > > >> someone to
> > > > >> >>> volunteer to be an RM.
> Any
> > requirement
> > > of "install
> > > > this (Docker,
> > > > >> etc) on
> > > > >> >>> your computer" is, IMO,
> another
> > barrier
> > > to entry.
> > > > Yeah, RMs will
> > > > >> have to
> > > > >> >>> have Maven installed and
> maybe
> > Ant, but
> > > you should
> > > > already have
> > > > >> those
> > > > >> >>> installed to be a
> committer/PMC
> > member.
> > > > >> >>>
> > > > >> >>> That said, a good
> takeaway from
> > the
> > > Docker idea is
> > > > to try to find
> > > > >> a way
> > > > >> >> to
> > > > >> >>> make an "Image" of
> whatever we
> > end up
> > > with on
> > > > whatever server we
> > > > >> end up
> > > > >> >>> using so if the image can
> be
> > copied and
> > > used on
> > > > other servers.
> > > > >> I'm not
> > > > >> >>> exactly sure how to do
> that
> > with Azure,
> > > which hosts
> > > > my CI
> > > > >> server. I will
> > > > >> >>> spend a few more minutes
> > researching that.
> > > > >> >>>
> > > > >> >>> I could not quickly find
> any
> > way to get a
> > > free VM
> > > > on Azure or AWS
> > > > >> that
> > > > >> >>> isn't a
> > > free-trial-start-paying-after-a-year. So,
> > > > unless someone
> > > > >> comes
> > > > >> >> up
> > > > >> >>> with a free server we can
> use
> > "forever",
> > > I'm going
> > > > to just start
> > > > >> with my
> > > > >> >>> Azure VM.
> > > > >> >>>
> > > > >> >>> -Alex
> > > > >> >>>
> > > > >> >>> On 2/5/19, 10:59 PM,
> "Carlos
> > Rovira" <
> > > > carlosrovira@apache.org>
> > > > >> wrote:
> > > > >> >>>
> > > > >> >>> Hi.
> > > > >> >>>
> > > > >> >>> the plan sounds very
> good to
> > me. Just
> > > my 2
> > > > thoughts on this:
> > > > >> >>>
> > > > >> >>> 1.- As I was reading I
> was
> > thinking as
> > > well on
> > > > something like
> > > > >> Docker
> > > > >> >>> and
> > > > >> >>> see Om as well
> thinking on
> > the same.
> > > Maybe is
> > > > the way to this
> > > > >> with
> > > > >> >> the
> > > > >> >>> actual technology.
> Seems VMs
> > are
> > > stepping out a
> > > > bit this days
> > > > >> in
> > > > >> >> favor
> > > > >> >>> of
> > > > >> >>> things like Docker.
> Maybe
> > the same did
> > > Git over
> > > > Svn, and today
> > > > >> Svn is
> > > > >> >>> an
> > > > >> >>> old remembrance. I
> must say
> > that I
> > > have no
> > > > experience with
> > > > >> Docker, so
> > > > >> >>> doing
> > > > >> >>> that will require
> acquire
> > that
> > > knowledge, but
> > > > seems it could
> > > > >> be worth
> > > > >> >>> it.
> > > > >> >>>
> > > > >> >>> 2.- Maybe is not
> possible,
> > but I want
> > > to propose
> > > > to do this
> > > > >> work I a
> > > > >> >>> separate branch, so it
> could
> > be in
> > > parallel to
> > > > other
> > > > >> developments. I
> > > > >> >>> think
> > > > >> >>> work over develop is
> > practical if
> > > there's
> > > > something tiny that
> > > > >> could
> > > > >> >> be
> > > > >> >>> done
> > > > >> >>> in a commit. But as we
> need
> > more than
> > > one, or is
> > > > a long
> > > > >> process (like
> > > > >> >>> this), chances are to
> make
> > develop
> > > branch
> > > > unstable and even
> > > > >> for some
> > > > >> >>> days.
> > > > >> >>> I think we should try
> to
> > avoid that
> > > scenario,
> > > > and branches are
> > > > >> the
> > > > >> >> best
> > > > >> >>> way. If we do this way,
> > we'll benefit
> > > of more
> > > > reliable develop
> > > > >> >> branch.
> > > > >> >>>
> > > > >> >>> Thanks and good to
> know of
> > this plan :)
> > > > >> >>>
> > > > >> >>> Carlos
> > > > >> >>>
> > > > >> >>>
> > > > >> >>> El mar., 5 feb. 2019 a
> las
> > 23:19,
> > > Harbs (<
> > > > >> harbs.lists@gmail.com>)
> > > > >> >>> escribió:
> > > > >> >>>
> > > > >> >>>> I’ve never used Docker
> myself,
> > but that
> > > might be a
> > > > good plan.
> > > > >> >>>>
> > > > >> >>>>> On Feb 6, 2019, at
> 12:07 AM,
> > OmPrakash
> > > Muppirala <
> > > > >> >>> bigosmallm@gmail.com>
> > > > >> >>>> wrote:
> > > > >> >>>>>
> > > > >> >>>>> I was wondering if we
> can use
> > docker
> > > images to
> > > > setup and seal
> > > > >> the
> > > > >> >>> RM
> > > > >> >>>>> environment. Then
> other RMs
> > simply
> > > need to run
> > > > the image
> > > > >> locally
> > > > >> >>> and run
> > > > >> >>>>> the release scripts.
> Might
> > be easier.
> > > If folks
> > > > like this plan,
> > > > >> >> I
> > > > >> >>> can
> > > > >> >>>> try
> > > > >> >>>>> to put something
> together.
> > > > >> >>>>>
> > > > >> >>>>> Thanks,
> > > > >> >>>>> Om
> > > > >> >>>>>
> > > > >> >>>>> On Tue, Feb 5, 2019 at
> 1:40
> > PM Harbs <
> > > > harbs.lists@gmail.com>
> > > > >> >>> wrote:
> > > > >> >>>>>
> > > > >> >>>>>> In a recent
> discussion, it
> > looks like
> > > other
> > > > projects have
> > > > >> gotten
> > > > >> >>>> resources
> > > > >> >>>>>> from AWS.
> > > > >> >>>>>>
> > > > >> >>>>>> Whatever service we
> use,
> > could setup a
> > > “shared”
> > > > Royale account
> > > > >> >>> that all
> > > > >> >>>>>> PMC members could have
> > access to.
> > > > >> >>>>>>
> > > > >> >>>>>> I don’t know if
> there’s some
> > way we
> > > could
> > > > leverage Gitlab’s
> > > > >> >>> integration
> > > > >> >>>>>> pipelines
> > > > >> >>>
> > > > >> >>
> > > > >>
> > > >
> > >
> > https://docs.gitlab.com/ee/ci/README.html
> > > > >> >>> <
> > > > >> >>>>>>
> > > > >> >>>
> > > > >> >>
> > > > >>
> > > >
> > >
> > https://docs.gitlab.com/ee/ci/README.html
> > > > >> >>>>
> > > > >> >>>>>>
> > > > >> >>>>>>> On Feb 5, 2019, at
> 11:33
> > PM, Alex
> > > Harui
> > > > >> >> <aharui@adobe.com.INVALID
> > > > >> >>>>
> > > > >> >>>>>> wrote:
> > > > >> >>>>>>>
> > > > >> >>>>>>> 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" <
> > > > >> >> piotrzarzycki21@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.lists@gmail.com
> > > > >> >>> wrote:
> > > > >> >>>>>>>
> > > > >> >>>>>>>> A big +1 from me!
> > > > >> >>>>>>>>
> > > > >> >>>>>>>> Looking forward!
> > > > >> >>>>>>>>
> > > > >> >>>>>>>>> On Feb 5, 2019, at
> 9:34
> > PM, Alex
> > > Harui
> > > > >> >>> <aharui@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
> > > >
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
The merge is complete, and the main builds seem to be successful, except for Maven on royale-asjs which was failing before the merge.
I'm still catching up on other things, but I think there are some bugs we need to fix before cutting the release? I think ASDoc may not be fully working? What else?
-Alex
On 6/10/19, 11:05 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Hi Alex,
Many thanks for that! I will try to be RM. I will have some dedicated time
for that. I will wait for your instruction and merge to develop.
Thanks,
Piotr
On Mon, Jun 10, 2019, 7:31 PM Alex Harui <ah...@adobe.com.invalid> wrote:
> Well, that turned out to be much more time-consuming than I expected, but
> we can now create identical release artifacts on Mac and Win. I am hopeful
> this effort will pay off not only now in having other folks generate
> releases, but also in the future if signed binaries become a requirement.
>
> There continues to be a lot of distractions in my life that can cause
> delays, but I hope to merge the release_practice branches into develop over
> the next day or two and figure out where in the wiki to document the
> release process. So, now is the time for one or more people to step up to
> be the RMs for 0.9.6 and help debug and improve the process.
>
> I am going to try very hard not to "own" the process. If something goes
> wrong, I am going to ask others to try to debug and fix it first because it
> is in the project's best interests for others to truly understand how this
> stuff works.
>
> Thanks,
> -Alex
>
> On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> It has turned out to be harder than expected to get the same binaries
> on Mac and Win. I now have the identical binaries for royale-compiler and
> royale-typedefs Maven artifacts and am starting on royale-asjs. I might
> get lucky and the changes that fixed royale-typedefs SWCs will magically
> get the royale-asjs SWCs to match. Then we have to make the Ant artifacts
> match.
>
> There have been a lot of distractions in my non-work life which has
> also impeded progress. I hope to make much progress this coming week and
> if we're lucky, I will be asking for a volunteer (or volunteers) to test
> drive all of this stuff and be the RM for 0.9.6. I am not going to be the
> RM.
>
> -Alex
>
> On 5/23/19, 9:39 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
>
> Hi Alex,
>
> It's been a while since you have started effort with automating
> build.
> Where are you with that ? Are we closer to started 0.9.6. Do you
> need any
> help with this ?
>
> Thanks,
> Piotr
>
> wt., 2 kwi 2019 o 19:30 Alex Harui <ah...@adobe.com.invalid>
> napisał(a):
>
> > Update:
> >
> > In order to make verification of binary release packages created
> on the
> > server easier, I have made changes to our build scripts and
> tools to try to
> > generate reproducible binaries. I've seen two different builds
> compare on
> > my Mac. The next challenge will be to see if the server can
> build a
> > package on Windows that will compare on Mac.
> >
> > One of the changes I needed to make is to JBurg. The version of
> JBurg we
> > use generates method names including a hash that doesn't
> reproduce the same
> > name each time. I have changes to JBurg ready, however JBurg is
> currently
> > under CPL which is category B. We only need one file, we don't
> need or
> > want all of JBurg at this time. The one JBurg file is jointly
> owned by
> > Adobe and Tom Harwood. I've contact Tom and he will be filing
> an ICLA and
> > has given me permission to commit the lines he owns in that one
> file.
> >
> > This is the revision of the file that will be donated by
> Tom/Adobe.
> >
> >
> https://sourceforge.net/p/jburg/code/ci/66c287943376a74ac791f3d3bf969ab160bf80ff/tree/src/generator/jburg/burg/JBurgGenerator.java
> >
> > Once this file goes in with the changes to keep the method names
> the same,
> > there will be more tweaks to the release tasks and then we can
> try cutting
> > a release. I'm thinking we'll be at that point in early May, so
> now is the
> > time to get stuff in for the 0.9.6 release.
> >
> > Thanks,
> > -Alex
> >
> > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >
> > I would much rather have others find and fix issues
> themselves. That
> > way, more people than just me will know how to maintain the
> system. It
> > actually turns out that, IMO, a group of people can work on the
> release.
> > There are 14 steps. Literally, 14 different people could
> execute one step
> > each.
> >
> > My 2 cents,
> > -Alex
> >
> > On 3/8/19, 2:13 AM, "Carlos Rovira" <ca...@apache.org>
> wrote:
> >
> > Hi Alex,
> >
> > amazing work! congrats to reach to this point! :)
> >
> > I need to put my head on all of this, but count on me to
> be a RM.
> > I think
> > the best thing should be that you be the first RM to try
> your own
> > development at least for the first time, and then the
> rest of us
> > will
> > follow you on the next releases. With all this on place
> we maybe
> > could
> > release once a month or every two months...
> >
> > Thanks for doing this :)
> >
> > Carlos
> >
> >
> > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > (<ah...@adobe.com.invalid>)
> > escribió:
> >
> > > OK, I've now seen Jenkins perform the steps to build
> the release
> > > artifacts. Folks interested in Docker-izing the steps
> are
> > welcome to look
> > > at the jobs on the "Royale Release" tab on the CI
> server.
> > >
> >
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/
> > >
> > > These steps assume that the RM can run the basic Maven
> and Ant
> > build on
> > > the RM's computer. I think that's a fair requirement
> since all
> > of us on the
> > > PMC need to able to do that to build the RC in order
> to vote on
> > it.
> > > Jenkins does other tasks like run the Maven release
> plugin
> > steps.
> > >
> > > Currently that results in binaries on Jenkins that are
> > downloaded to the
> > > RM's computer. These binaries need to be verified by
> the RM
> > which is the
> > > next phase I will be starting on now. The RM verifies
> the bits
> > and then
> > > PGP signs them. And then the bits are uploaded off
> the RM's
> > computer to
> > > Maven Staging or dist.a.o/dev. If that uploading
> turns out to
> > be a point
> > > of failure, we have the option of having Jenkins
> upload the big
> > files and
> > > have the RM only upload PGP signature files. Or
> finding a way
> > for Jenkins
> > > to get the signature files from the RM. The uploads
> worked fine
> > for me,
> > > but then again, so did the old script's uploads.
> > >
> > > Therefore, once I get the binary verification phase
> completed, I
> > think
> > > someone other than me should be the RM and try to use
> these
> > steps to
> > > generate the release and help debug the process for
> the next
> > RM. So,
> > > please try to carve out some time to be the RM. One
> advantage
> > of doing
> > > most of the work on Jenkins is that it frees up my
> computer to
> > do other
> > > things while Jenkins is cranking away.
> > >
> > > I think we're at least a week away from binary
> verification,
> > maybe two, so
> > > it is time to start thinking about what is going in
> this release.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 3/7/19, 4:15 PM, "Alex Harui"
> <ah...@adobe.com.INVALID>
> > wrote:
> > >
> > > In case you haven't guessed, I'm testing out
> Jenkins and its
> > ability
> > > to create the artifacts and send emails. Please
> ignore any
> > email that
> > > looks like a vote or discuss thread.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 2/10/19, 8:44 PM, "Alex Harui"
> <ah...@adobe.com.INVALID>
> > wrote:
> > >
> > > Om,
> > >
> > > Well, that's what I used for the last
> release. I'm sure
> > there is
> > > probably some inaccuracy in it.
> > >
> > > That said, I'm abandoning that document and
> taking a new
> > angle
> > > because that document presumed that the release
> manager was
> > trying to
> > > create a release on his/her computer. I've given up
> on that and
> > working on
> > > making releases from a shared computer for the reasons
> I've
> > stated
> > > upthread. I hope to make some progress on that this
> week.
> > >
> > > The key difference is that the new angle does
> not
> > presume that you
> > > have Git SSH and PGP signatures all set up on some
> computer. I
> > have not
> > > looked into how Docker would handle that. You
> certainly
> > wouldn't want the
> > > Docker image to contain your SSH or PGP keys/creds.
> And if the
> > Docker
> > > image doesn't, then that is another stumbling block
> for future
> > RMs.
> > >
> > > The other key difference is that the old
> script presumed
> > you could
> > > create the 3 release in 3 huge "easy" steps. We've
> seen that is
> > only true
> > > for me. So the new angle creates many discrete steps
> managed by
> > Jenkins.
> > >
> > > So, it is up to you to decide what you want to
> > "Docker-ize". You
> > > can try to Docker-ize the current 3 big steps, so RMs
> can try to
> > run it on
> > > their systems, but I'd bet they will just faiI due to
> network
> > issues. I
> > > would be interested in using Docker to make each of
> these many
> > discrete
> > > steps portable to another server. I'm not going to
> involve
> > Docker at this
> > > point. My main goal is just to see if I can create a
> workflow
> > of many
> > > discrete steps that isn't horribly painful. Once we
> see what
> > these steps
> > > turn out to be, then we can worry about server
> portability of
> > those steps.
> > >
> > > Either way, we want to know about running
> > Browser+Selenium for
> > > sure. And maybe FlashPlayerDebugger or AIR. I would
> want to
> > know, for
> > > example, how you debug a failing checkintest in a
> Docker
> > container.
> > >
> > > Thanks,
> > > -Alex
> > >
> > >
> > > On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <
> > bigosmallm@gmail.com>
> > > wrote:
> > >
> > > Alex,
> > >
> > > Just to be clear, I am following the steps
> from here
> > to try
> > > and setup a
> > > docker container.
> > >
> > >
> > >
> >
> https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
> > >
> > > Is this doc up to date?
> > >
> > > Thanks,
> > > Om
> > >
> > > On Wed, Feb 6, 2019 at 12:02 PM OmPrakash
> Muppirala <
> > > bigosmallm@gmail.com>
> > > wrote:
> > >
> > > > One approach is to have each step in the
> process
> > spin up a
> > > docker image.
> > > > And use docker-compose to run each
> step. All the
> > images can
> > > be made to
> > > > share a common volume where all the
> artifacts are
> > stored
> > > across steps.
> > > >
> > > > You are right about the networking issue
> though.
> > Any
> > > network related
> > > > failure that occurs on the host machine
> will most
> > likely
> > > occur in the
> > > > docker container. Although, I am not
> clear how we
> > can
> > > guarantee that the
> > > > same issues will not occur on the
> Jenkins server.
> > I mean,
> > > what is special
> > > > about the Jenkins server that makes it
> immune to
> > these
> > > networking issues?
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Wed, Feb 6, 2019 at 11:48 AM Alex
> Harui
> > > <ah...@adobe.com.invalid>
> > > > wrote:
> > > >
> > > >> Again, I don't know anything about
> Docker, but
> > before we
> > > spend a lot of
> > > >> time on Docker, I also want to point
> out that the
> > process
> > > to create a
> > > >> release cannot really be thought of as
> "one
> > application".
> > > It will be a
> > > >> series of "steps" to run. How many
> steps
> > depends on
> > > whether we think we
> > > >> can isolate enough stuff via Docker to
> be able to
> > run
> > > Docker on the RM's
> > > >> computer instead of some shared
> computer. On a
> > shared
> > > computer there will
> > > >> be dozens of steps because the RM will
> need to
> > enter
> > > passwords to commit
> > > >> stuff. On a local computer I guess the
> RM can
> > supply
> > > passwords but I think
> > > >> there will be stopping points where the
> Maven
> > artifacts are
> > > deployed and
> > > >> the staging repo is closed, and another
> stopping
> > point for
> > > the vote. It
> > > >> seems like Docker works by downloading
> > dependencies. Given
> > > that the
> > > >> problem the RMs had last time involved
> downloads
> > and
> > > uploads, why do we
> > > >> think Docker will really solve this for
> creating
> > releases
> > > on local machines?
> > > >>
> > > >> The reason to do this on a shared
> machine is so
> > that new
> > > RMs don't have
> > > >> to do as much setup. But then I wonder
> about the
> > > efficiency of kicking off
> > > >> that many Docker images. Jenkins can
> manage that
> > already.
> > > Does Docker
> > > >> have some sort of similar Dashboard or
> would we
> > use Jenkins
> > > to kick off
> > > >> Docker steps? I can't quite picture
> what is the
> > outermost
> > > >> control/dashboard.
> > > >>
> > > >> -Alex
> > > >>
> > > >> On 2/6/19, 11:03 AM, "Harbs" <
> > harbs.lists@gmail.com> wrote:
> > > >>
> > > >> A quick search turns up this:
> > > >>
> > > >>
> > > >>
> > >
> >
> https://codingsans.com/blog/selenium-with-docker-testing
> > > >> <
> > > >>
> > >
> >
> https://codingsans.com/blog/selenium-with-docker-testing
> > > >> >
> > > >>
> > > >>
> > >
> >
> https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker
> > > >> <
> > > >>
> > >
> >
> https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker
> > > >> >
> > > >>
> > > >>
> > >
> >
> https://github.com/SeleniumHQ/docker-selenium
> > > >> <
> > > >>
> > >
> >
> https://github.com/SeleniumHQ/docker-selenium
> > > >> >
> > > >>
> > > >> > On Feb 6, 2019, at 8:59 PM, Alex
> Harui
> > > <ah...@adobe.com.INVALID>
> > > >> wrote:
> > > >> >
> > > >> > Thanks for volunteering to try it
> Om. IMO,
> > even more
> > > important
> > > >> than Firefox+Flash is
> SomeBrowser+Selenium. We
> > may also
> > > need to run Adobe
> > > >> AIR's adb. We could probably turn off
> the Flash
> > tests or
> > > replace Flash
> > > >> with AIR.
> > > >> >
> > > >> > Thanks,
> > > >> > -Alex
> > > >> >
> > > >> > On 2/6/19, 10:54 AM, "Carlos
> Rovira" <
> > > carlosrovira@apache.org>
> > > >> wrote:
> > > >> >
> > > >> > Hi Om, that would be great!
> waiting for
> > your
> > > experience with a
> > > >> that! :)
> > > >> >
> > > >> > El mié., 6 feb. 2019 a las
> 19:31,
> > OmPrakash
> > > Muppirala (<
> > > >> bigosmallm@gmail.com>)
> > > >> > escribió:
> > > >> >
> > > >> >> Yes, I agree with Alex about not
> being
> > able to run
> > > UI out of docker
> > > >> >> containers. I never thought of
> the
> > checkintests
> > > when I made the
> > > >> >> suggestion.
> > > >> >>
> > > >> >> The firefox-flash image that
> Yishay
> > pointed out
> > > looks promising.
> > > >> I will
> > > >> >> poke around with it and see if
> that works
> > for us.
> > > >> >>
> > > >> >> Thanks,
> > > >> >> Om
> > > >> >>
> > > >> >> On Wed, Feb 6, 2019 at 12:41 AM
> Yishay
> > Weiss <
> > > >> yishayjobs@hotmail.com>
> > > >> >> wrote:
> > > >> >>
> > > >> >>> I’ll let Om or someone else
> with docker
> > experience
> > > tell us if
> > > >> this [1] is
> > > >> >>> relevant.
> > > >> >>>
> > > >> >>>
> > > >> >>>
> > > >> >>> [1]
> > > >>
> > >
> >
> https://hub.docker.com/r/beli/firefox-flash/
> > > >> >>>
> > > >> >>>
> > > >> >>>
> > > >> >>> ________________________________
> > > >> >>> From: Alex Harui
> <aharui@adobe.com.INVALID
> > >
> > > >> >>> Sent: Wednesday, February 6,
> 2019
> > 10:05:54 AM
> > > >> >>> To: dev@royale.apache.org
> > > >> >>> Subject: Re: 0.9.6 Release
> > > >> >>>
> > > >> >>> I don't anything about docker,
> but in 15
> > minutes of
> > > reading I ran
> > > >> into
> > > >> >>> this:
> > > >> >>>
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://www.channelfutures.com/open-source/when-not-to-use-docker-understanding-the-limitations-of-containers
> > > >> >>>
> > > >> >>> Which says: Docker can't " Run
> > applications with
> > > graphical
> > > >> interfaces".
> > > >> >>> If you want Royale to use
> Docker for
> > releases, show
> > > that it can
> > > >> run
> > > >> >>> checkintests with Flash and the
> Browser.
> > Then I
> > > will look into
> > > >> it more.
> > > >> >>>
> > > >> >>> The highest level goal is to
> make it as
> > easy as
> > > possible for
> > > >> someone to
> > > >> >>> volunteer to be an RM. Any
> requirement
> > of "install
> > > this (Docker,
> > > >> etc) on
> > > >> >>> your computer" is, IMO, another
> barrier
> > to entry.
> > > Yeah, RMs will
> > > >> have to
> > > >> >>> have Maven installed and maybe
> Ant, but
> > you should
> > > already have
> > > >> those
> > > >> >>> installed to be a committer/PMC
> member.
> > > >> >>>
> > > >> >>> That said, a good takeaway from
> the
> > Docker idea is
> > > to try to find
> > > >> a way
> > > >> >> to
> > > >> >>> make an "Image" of whatever we
> end up
> > with on
> > > whatever server we
> > > >> end up
> > > >> >>> using so if the image can be
> copied and
> > used on
> > > other servers.
> > > >> I'm not
> > > >> >>> exactly sure how to do that
> with Azure,
> > which hosts
> > > my CI
> > > >> server. I will
> > > >> >>> spend a few more minutes
> researching that.
> > > >> >>>
> > > >> >>> I could not quickly find any
> way to get a
> > free VM
> > > on Azure or AWS
> > > >> that
> > > >> >>> isn't a
> > free-trial-start-paying-after-a-year. So,
> > > unless someone
> > > >> comes
> > > >> >> up
> > > >> >>> with a free server we can use
> "forever",
> > I'm going
> > > to just start
> > > >> with my
> > > >> >>> Azure VM.
> > > >> >>>
> > > >> >>> -Alex
> > > >> >>>
> > > >> >>> On 2/5/19, 10:59 PM, "Carlos
> Rovira" <
> > > carlosrovira@apache.org>
> > > >> wrote:
> > > >> >>>
> > > >> >>> Hi.
> > > >> >>>
> > > >> >>> the plan sounds very good to
> me. Just
> > my 2
> > > thoughts on this:
> > > >> >>>
> > > >> >>> 1.- As I was reading I was
> thinking as
> > well on
> > > something like
> > > >> Docker
> > > >> >>> and
> > > >> >>> see Om as well thinking on
> the same.
> > Maybe is
> > > the way to this
> > > >> with
> > > >> >> the
> > > >> >>> actual technology. Seems VMs
> are
> > stepping out a
> > > bit this days
> > > >> in
> > > >> >> favor
> > > >> >>> of
> > > >> >>> things like Docker. Maybe
> the same did
> > Git over
> > > Svn, and today
> > > >> Svn is
> > > >> >>> an
> > > >> >>> old remembrance. I must say
> that I
> > have no
> > > experience with
> > > >> Docker, so
> > > >> >>> doing
> > > >> >>> that will require acquire
> that
> > knowledge, but
> > > seems it could
> > > >> be worth
> > > >> >>> it.
> > > >> >>>
> > > >> >>> 2.- Maybe is not possible,
> but I want
> > to propose
> > > to do this
> > > >> work I a
> > > >> >>> separate branch, so it could
> be in
> > parallel to
> > > other
> > > >> developments. I
> > > >> >>> think
> > > >> >>> work over develop is
> practical if
> > there's
> > > something tiny that
> > > >> could
> > > >> >> be
> > > >> >>> done
> > > >> >>> in a commit. But as we need
> more than
> > one, or is
> > > a long
> > > >> process (like
> > > >> >>> this), chances are to make
> develop
> > branch
> > > unstable and even
> > > >> for some
> > > >> >>> days.
> > > >> >>> I think we should try to
> avoid that
> > scenario,
> > > and branches are
> > > >> the
> > > >> >> best
> > > >> >>> way. If we do this way,
> we'll benefit
> > of more
> > > reliable develop
> > > >> >> branch.
> > > >> >>>
> > > >> >>> Thanks and good to know of
> this plan :)
> > > >> >>>
> > > >> >>> Carlos
> > > >> >>>
> > > >> >>>
> > > >> >>> El mar., 5 feb. 2019 a las
> 23:19,
> > Harbs (<
> > > >> harbs.lists@gmail.com>)
> > > >> >>> escribió:
> > > >> >>>
> > > >> >>>> I’ve never used Docker myself,
> but that
> > might be a
> > > good plan.
> > > >> >>>>
> > > >> >>>>> On Feb 6, 2019, at 12:07 AM,
> OmPrakash
> > Muppirala <
> > > >> >>> bigosmallm@gmail.com>
> > > >> >>>> wrote:
> > > >> >>>>>
> > > >> >>>>> I was wondering if we can use
> docker
> > images to
> > > setup and seal
> > > >> the
> > > >> >>> RM
> > > >> >>>>> environment. Then other RMs
> simply
> > need to run
> > > the image
> > > >> locally
> > > >> >>> and run
> > > >> >>>>> the release scripts. Might
> be easier.
> > If folks
> > > like this plan,
> > > >> >> I
> > > >> >>> can
> > > >> >>>> try
> > > >> >>>>> to put something together.
> > > >> >>>>>
> > > >> >>>>> Thanks,
> > > >> >>>>> Om
> > > >> >>>>>
> > > >> >>>>> On Tue, Feb 5, 2019 at 1:40
> PM Harbs <
> > > harbs.lists@gmail.com>
> > > >> >>> wrote:
> > > >> >>>>>
> > > >> >>>>>> In a recent discussion, it
> looks like
> > other
> > > projects have
> > > >> gotten
> > > >> >>>> resources
> > > >> >>>>>> from AWS.
> > > >> >>>>>>
> > > >> >>>>>> Whatever service we use,
> could setup a
> > “shared”
> > > Royale account
> > > >> >>> that all
> > > >> >>>>>> PMC members could have
> access to.
> > > >> >>>>>>
> > > >> >>>>>> I don’t know if there’s some
> way we
> > could
> > > leverage Gitlab’s
> > > >> >>> integration
> > > >> >>>>>> pipelines
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://docs.gitlab.com/ee/ci/README.html
> > > >> >>> <
> > > >> >>>>>>
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://docs.gitlab.com/ee/ci/README.html
> > > >> >>>>
> > > >> >>>>>>
> > > >> >>>>>>> On Feb 5, 2019, at 11:33
> PM, Alex
> > Harui
> > > >> >> <aharui@adobe.com.INVALID
> > > >> >>>>
> > > >> >>>>>> wrote:
> > > >> >>>>>>>
> > > >> >>>>>>> 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" <
> > > >> >> piotrzarzycki21@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.lists@gmail.com
> > > >> >>> wrote:
> > > >> >>>>>>>
> > > >> >>>>>>>> A big +1 from me!
> > > >> >>>>>>>>
> > > >> >>>>>>>> Looking forward!
> > > >> >>>>>>>>
> > > >> >>>>>>>>> On Feb 5, 2019, at 9:34
> PM, Alex
> > Harui
> > > >> >>> <ah...@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
> > >
Re: 0.9.6 Release
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Alex,
Many thanks for that! I will try to be RM. I will have some dedicated time
for that. I will wait for your instruction and merge to develop.
Thanks,
Piotr
On Mon, Jun 10, 2019, 7:31 PM Alex Harui <ah...@adobe.com.invalid> wrote:
> Well, that turned out to be much more time-consuming than I expected, but
> we can now create identical release artifacts on Mac and Win. I am hopeful
> this effort will pay off not only now in having other folks generate
> releases, but also in the future if signed binaries become a requirement.
>
> There continues to be a lot of distractions in my life that can cause
> delays, but I hope to merge the release_practice branches into develop over
> the next day or two and figure out where in the wiki to document the
> release process. So, now is the time for one or more people to step up to
> be the RMs for 0.9.6 and help debug and improve the process.
>
> I am going to try very hard not to "own" the process. If something goes
> wrong, I am going to ask others to try to debug and fix it first because it
> is in the project's best interests for others to truly understand how this
> stuff works.
>
> Thanks,
> -Alex
>
> On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> It has turned out to be harder than expected to get the same binaries
> on Mac and Win. I now have the identical binaries for royale-compiler and
> royale-typedefs Maven artifacts and am starting on royale-asjs. I might
> get lucky and the changes that fixed royale-typedefs SWCs will magically
> get the royale-asjs SWCs to match. Then we have to make the Ant artifacts
> match.
>
> There have been a lot of distractions in my non-work life which has
> also impeded progress. I hope to make much progress this coming week and
> if we're lucky, I will be asking for a volunteer (or volunteers) to test
> drive all of this stuff and be the RM for 0.9.6. I am not going to be the
> RM.
>
> -Alex
>
> On 5/23/19, 9:39 AM, "Piotr Zarzycki" <pi...@gmail.com>
> wrote:
>
> Hi Alex,
>
> It's been a while since you have started effort with automating
> build.
> Where are you with that ? Are we closer to started 0.9.6. Do you
> need any
> help with this ?
>
> Thanks,
> Piotr
>
> wt., 2 kwi 2019 o 19:30 Alex Harui <ah...@adobe.com.invalid>
> napisał(a):
>
> > Update:
> >
> > In order to make verification of binary release packages created
> on the
> > server easier, I have made changes to our build scripts and
> tools to try to
> > generate reproducible binaries. I've seen two different builds
> compare on
> > my Mac. The next challenge will be to see if the server can
> build a
> > package on Windows that will compare on Mac.
> >
> > One of the changes I needed to make is to JBurg. The version of
> JBurg we
> > use generates method names including a hash that doesn't
> reproduce the same
> > name each time. I have changes to JBurg ready, however JBurg is
> currently
> > under CPL which is category B. We only need one file, we don't
> need or
> > want all of JBurg at this time. The one JBurg file is jointly
> owned by
> > Adobe and Tom Harwood. I've contact Tom and he will be filing
> an ICLA and
> > has given me permission to commit the lines he owns in that one
> file.
> >
> > This is the revision of the file that will be donated by
> Tom/Adobe.
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=XMDpGg0yPP530enC02eH8CQXf66Lsn97FFaqHxJaaio%3D&reserved=0
> >
> > Once this file goes in with the changes to keep the method names
> the same,
> > there will be more tweaks to the release tasks and then we can
> try cutting
> > a release. I'm thinking we'll be at that point in early May, so
> now is the
> > time to get stuff in for the 0.9.6 release.
> >
> > Thanks,
> > -Alex
> >
> > On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >
> > I would much rather have others find and fix issues
> themselves. That
> > way, more people than just me will know how to maintain the
> system. It
> > actually turns out that, IMO, a group of people can work on the
> release.
> > There are 14 steps. Literally, 14 different people could
> execute one step
> > each.
> >
> > My 2 cents,
> > -Alex
> >
> > On 3/8/19, 2:13 AM, "Carlos Rovira" <ca...@apache.org>
> wrote:
> >
> > Hi Alex,
> >
> > amazing work! congrats to reach to this point! :)
> >
> > I need to put my head on all of this, but count on me to
> be a RM.
> > I think
> > the best thing should be that you be the first RM to try
> your own
> > development at least for the first time, and then the
> rest of us
> > will
> > follow you on the next releases. With all this on place
> we maybe
> > could
> > release once a month or every two months...
> >
> > Thanks for doing this :)
> >
> > Carlos
> >
> >
> > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> > (<ah...@adobe.com.invalid>)
> > escribió:
> >
> > > OK, I've now seen Jenkins perform the steps to build
> the release
> > > artifacts. Folks interested in Docker-izing the steps
> are
> > welcome to look
> > > at the jobs on the "Royale Release" tab on the CI
> server.
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=ag8xFP8FhC0ndIumEhlwAKTNImbUy3vLwVGYWiK0a68%3D&reserved=0
> > >
> > > These steps assume that the RM can run the basic Maven
> and Ant
> > build on
> > > the RM's computer. I think that's a fair requirement
> since all
> > of us on the
> > > PMC need to able to do that to build the RC in order
> to vote on
> > it.
> > > Jenkins does other tasks like run the Maven release
> plugin
> > steps.
> > >
> > > Currently that results in binaries on Jenkins that are
> > downloaded to the
> > > RM's computer. These binaries need to be verified by
> the RM
> > which is the
> > > next phase I will be starting on now. The RM verifies
> the bits
> > and then
> > > PGP signs them. And then the bits are uploaded off
> the RM's
> > computer to
> > > Maven Staging or dist.a.o/dev. If that uploading
> turns out to
> > be a point
> > > of failure, we have the option of having Jenkins
> upload the big
> > files and
> > > have the RM only upload PGP signature files. Or
> finding a way
> > for Jenkins
> > > to get the signature files from the RM. The uploads
> worked fine
> > for me,
> > > but then again, so did the old script's uploads.
> > >
> > > Therefore, once I get the binary verification phase
> completed, I
> > think
> > > someone other than me should be the RM and try to use
> these
> > steps to
> > > generate the release and help debug the process for
> the next
> > RM. So,
> > > please try to carve out some time to be the RM. One
> advantage
> > of doing
> > > most of the work on Jenkins is that it frees up my
> computer to
> > do other
> > > things while Jenkins is cranking away.
> > >
> > > I think we're at least a week away from binary
> verification,
> > maybe two, so
> > > it is time to start thinking about what is going in
> this release.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 3/7/19, 4:15 PM, "Alex Harui"
> <ah...@adobe.com.INVALID>
> > wrote:
> > >
> > > In case you haven't guessed, I'm testing out
> Jenkins and its
> > ability
> > > to create the artifacts and send emails. Please
> ignore any
> > email that
> > > looks like a vote or discuss thread.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 2/10/19, 8:44 PM, "Alex Harui"
> <ah...@adobe.com.INVALID>
> > wrote:
> > >
> > > Om,
> > >
> > > Well, that's what I used for the last
> release. I'm sure
> > there is
> > > probably some inaccuracy in it.
> > >
> > > That said, I'm abandoning that document and
> taking a new
> > angle
> > > because that document presumed that the release
> manager was
> > trying to
> > > create a release on his/her computer. I've given up
> on that and
> > working on
> > > making releases from a shared computer for the reasons
> I've
> > stated
> > > upthread. I hope to make some progress on that this
> week.
> > >
> > > The key difference is that the new angle does
> not
> > presume that you
> > > have Git SSH and PGP signatures all set up on some
> computer. I
> > have not
> > > looked into how Docker would handle that. You
> certainly
> > wouldn't want the
> > > Docker image to contain your SSH or PGP keys/creds.
> And if the
> > Docker
> > > image doesn't, then that is another stumbling block
> for future
> > RMs.
> > >
> > > The other key difference is that the old
> script presumed
> > you could
> > > create the 3 release in 3 huge "easy" steps. We've
> seen that is
> > only true
> > > for me. So the new angle creates many discrete steps
> managed by
> > Jenkins.
> > >
> > > So, it is up to you to decide what you want to
> > "Docker-ize". You
> > > can try to Docker-ize the current 3 big steps, so RMs
> can try to
> > run it on
> > > their systems, but I'd bet they will just faiI due to
> network
> > issues. I
> > > would be interested in using Docker to make each of
> these many
> > discrete
> > > steps portable to another server. I'm not going to
> involve
> > Docker at this
> > > point. My main goal is just to see if I can create a
> workflow
> > of many
> > > discrete steps that isn't horribly painful. Once we
> see what
> > these steps
> > > turn out to be, then we can worry about server
> portability of
> > those steps.
> > >
> > > Either way, we want to know about running
> > Browser+Selenium for
> > > sure. And maybe FlashPlayerDebugger or AIR. I would
> want to
> > know, for
> > > example, how you debug a failing checkintest in a
> Docker
> > container.
> > >
> > > Thanks,
> > > -Alex
> > >
> > >
> > > On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <
> > bigosmallm@gmail.com>
> > > wrote:
> > >
> > > Alex,
> > >
> > > Just to be clear, I am following the steps
> from here
> > to try
> > > and setup a
> > > docker container.
> > >
> > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=JfJSK%2B4xchkDWpv78GpWtFlVMQ%2BoUAE10rv7HdeCZck%3D&reserved=0
> > >
> > > Is this doc up to date?
> > >
> > > Thanks,
> > > Om
> > >
> > > On Wed, Feb 6, 2019 at 12:02 PM OmPrakash
> Muppirala <
> > > bigosmallm@gmail.com>
> > > wrote:
> > >
> > > > One approach is to have each step in the
> process
> > spin up a
> > > docker image.
> > > > And use docker-compose to run each
> step. All the
> > images can
> > > be made to
> > > > share a common volume where all the
> artifacts are
> > stored
> > > across steps.
> > > >
> > > > You are right about the networking issue
> though.
> > Any
> > > network related
> > > > failure that occurs on the host machine
> will most
> > likely
> > > occur in the
> > > > docker container. Although, I am not
> clear how we
> > can
> > > guarantee that the
> > > > same issues will not occur on the
> Jenkins server.
> > I mean,
> > > what is special
> > > > about the Jenkins server that makes it
> immune to
> > these
> > > networking issues?
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Wed, Feb 6, 2019 at 11:48 AM Alex
> Harui
> > > <ah...@adobe.com.invalid>
> > > > wrote:
> > > >
> > > >> Again, I don't know anything about
> Docker, but
> > before we
> > > spend a lot of
> > > >> time on Docker, I also want to point
> out that the
> > process
> > > to create a
> > > >> release cannot really be thought of as
> "one
> > application".
> > > It will be a
> > > >> series of "steps" to run. How many
> steps
> > depends on
> > > whether we think we
> > > >> can isolate enough stuff via Docker to
> be able to
> > run
> > > Docker on the RM's
> > > >> computer instead of some shared
> computer. On a
> > shared
> > > computer there will
> > > >> be dozens of steps because the RM will
> need to
> > enter
> > > passwords to commit
> > > >> stuff. On a local computer I guess the
> RM can
> > supply
> > > passwords but I think
> > > >> there will be stopping points where the
> Maven
> > artifacts are
> > > deployed and
> > > >> the staging repo is closed, and another
> stopping
> > point for
> > > the vote. It
> > > >> seems like Docker works by downloading
> > dependencies. Given
> > > that the
> > > >> problem the RMs had last time involved
> downloads
> > and
> > > uploads, why do we
> > > >> think Docker will really solve this for
> creating
> > releases
> > > on local machines?
> > > >>
> > > >> The reason to do this on a shared
> machine is so
> > that new
> > > RMs don't have
> > > >> to do as much setup. But then I wonder
> about the
> > > efficiency of kicking off
> > > >> that many Docker images. Jenkins can
> manage that
> > already.
> > > Does Docker
> > > >> have some sort of similar Dashboard or
> would we
> > use Jenkins
> > > to kick off
> > > >> Docker steps? I can't quite picture
> what is the
> > outermost
> > > >> control/dashboard.
> > > >>
> > > >> -Alex
> > > >>
> > > >> On 2/6/19, 11:03 AM, "Harbs" <
> > harbs.lists@gmail.com> wrote:
> > > >>
> > > >> A quick search turns up this:
> > > >>
> > > >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=FUYuwlg6rT8EgffgT3QoP8YWcyzjXxNdrT8aN0jq1H4%3D&reserved=0
> > > >> <
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=FUYuwlg6rT8EgffgT3QoP8YWcyzjXxNdrT8aN0jq1H4%3D&reserved=0
> > > >> >
> > > >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=T4QPL4Hh552jE67uYLU1Xu2hDv61NLfuk4u2V6GS%2Bek%3D&reserved=0
> > > >> <
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=T4QPL4Hh552jE67uYLU1Xu2hDv61NLfuk4u2V6GS%2Bek%3D&reserved=0
> > > >> >
> > > >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=3r1pbB7qdx%2FQUpas%2FyQFs4ICsZUF7vBemIOm%2FArz6ZM%3D&reserved=0
> > > >> <
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=3r1pbB7qdx%2FQUpas%2FyQFs4ICsZUF7vBemIOm%2FArz6ZM%3D&reserved=0
> > > >> >
> > > >>
> > > >> > On Feb 6, 2019, at 8:59 PM, Alex
> Harui
> > > <ah...@adobe.com.INVALID>
> > > >> wrote:
> > > >> >
> > > >> > Thanks for volunteering to try it
> Om. IMO,
> > even more
> > > important
> > > >> than Firefox+Flash is
> SomeBrowser+Selenium. We
> > may also
> > > need to run Adobe
> > > >> AIR's adb. We could probably turn off
> the Flash
> > tests or
> > > replace Flash
> > > >> with AIR.
> > > >> >
> > > >> > Thanks,
> > > >> > -Alex
> > > >> >
> > > >> > On 2/6/19, 10:54 AM, "Carlos
> Rovira" <
> > > carlosrovira@apache.org>
> > > >> wrote:
> > > >> >
> > > >> > Hi Om, that would be great!
> waiting for
> > your
> > > experience with a
> > > >> that! :)
> > > >> >
> > > >> > El mié., 6 feb. 2019 a las
> 19:31,
> > OmPrakash
> > > Muppirala (<
> > > >> bigosmallm@gmail.com>)
> > > >> > escribió:
> > > >> >
> > > >> >> Yes, I agree with Alex about not
> being
> > able to run
> > > UI out of docker
> > > >> >> containers. I never thought of
> the
> > checkintests
> > > when I made the
> > > >> >> suggestion.
> > > >> >>
> > > >> >> The firefox-flash image that
> Yishay
> > pointed out
> > > looks promising.
> > > >> I will
> > > >> >> poke around with it and see if
> that works
> > for us.
> > > >> >>
> > > >> >> Thanks,
> > > >> >> Om
> > > >> >>
> > > >> >> On Wed, Feb 6, 2019 at 12:41 AM
> Yishay
> > Weiss <
> > > >> yishayjobs@hotmail.com>
> > > >> >> wrote:
> > > >> >>
> > > >> >>> I’ll let Om or someone else
> with docker
> > experience
> > > tell us if
> > > >> this [1] is
> > > >> >>> relevant.
> > > >> >>>
> > > >> >>>
> > > >> >>>
> > > >> >>> [1]
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=t1ZG3j7i5LnUTpdSEW78jLfn4K3gIDLnhpJNeaonTjg%3D&reserved=0
> > > >> >>>
> > > >> >>>
> > > >> >>>
> > > >> >>> ________________________________
> > > >> >>> From: Alex Harui
> <aharui@adobe.com.INVALID
> > >
> > > >> >>> Sent: Wednesday, February 6,
> 2019
> > 10:05:54 AM
> > > >> >>> To: dev@royale.apache.org
> > > >> >>> Subject: Re: 0.9.6 Release
> > > >> >>>
> > > >> >>> I don't anything about docker,
> but in 15
> > minutes of
> > > reading I ran
> > > >> into
> > > >> >>> this:
> > > >> >>>
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=ZOuiuLuyYx1I5w2expOtx1tGxDXIQqnKcSoFYUNkZeA%3D&reserved=0
> > > >> >>>
> > > >> >>> Which says: Docker can't " Run
> > applications with
> > > graphical
> > > >> interfaces".
> > > >> >>> If you want Royale to use
> Docker for
> > releases, show
> > > that it can
> > > >> run
> > > >> >>> checkintests with Flash and the
> Browser.
> > Then I
> > > will look into
> > > >> it more.
> > > >> >>>
> > > >> >>> The highest level goal is to
> make it as
> > easy as
> > > possible for
> > > >> someone to
> > > >> >>> volunteer to be an RM. Any
> requirement
> > of "install
> > > this (Docker,
> > > >> etc) on
> > > >> >>> your computer" is, IMO, another
> barrier
> > to entry.
> > > Yeah, RMs will
> > > >> have to
> > > >> >>> have Maven installed and maybe
> Ant, but
> > you should
> > > already have
> > > >> those
> > > >> >>> installed to be a committer/PMC
> member.
> > > >> >>>
> > > >> >>> That said, a good takeaway from
> the
> > Docker idea is
> > > to try to find
> > > >> a way
> > > >> >> to
> > > >> >>> make an "Image" of whatever we
> end up
> > with on
> > > whatever server we
> > > >> end up
> > > >> >>> using so if the image can be
> copied and
> > used on
> > > other servers.
> > > >> I'm not
> > > >> >>> exactly sure how to do that
> with Azure,
> > which hosts
> > > my CI
> > > >> server. I will
> > > >> >>> spend a few more minutes
> researching that.
> > > >> >>>
> > > >> >>> I could not quickly find any
> way to get a
> > free VM
> > > on Azure or AWS
> > > >> that
> > > >> >>> isn't a
> > free-trial-start-paying-after-a-year. So,
> > > unless someone
> > > >> comes
> > > >> >> up
> > > >> >>> with a free server we can use
> "forever",
> > I'm going
> > > to just start
> > > >> with my
> > > >> >>> Azure VM.
> > > >> >>>
> > > >> >>> -Alex
> > > >> >>>
> > > >> >>> On 2/5/19, 10:59 PM, "Carlos
> Rovira" <
> > > carlosrovira@apache.org>
> > > >> wrote:
> > > >> >>>
> > > >> >>> Hi.
> > > >> >>>
> > > >> >>> the plan sounds very good to
> me. Just
> > my 2
> > > thoughts on this:
> > > >> >>>
> > > >> >>> 1.- As I was reading I was
> thinking as
> > well on
> > > something like
> > > >> Docker
> > > >> >>> and
> > > >> >>> see Om as well thinking on
> the same.
> > Maybe is
> > > the way to this
> > > >> with
> > > >> >> the
> > > >> >>> actual technology. Seems VMs
> are
> > stepping out a
> > > bit this days
> > > >> in
> > > >> >> favor
> > > >> >>> of
> > > >> >>> things like Docker. Maybe
> the same did
> > Git over
> > > Svn, and today
> > > >> Svn is
> > > >> >>> an
> > > >> >>> old remembrance. I must say
> that I
> > have no
> > > experience with
> > > >> Docker, so
> > > >> >>> doing
> > > >> >>> that will require acquire
> that
> > knowledge, but
> > > seems it could
> > > >> be worth
> > > >> >>> it.
> > > >> >>>
> > > >> >>> 2.- Maybe is not possible,
> but I want
> > to propose
> > > to do this
> > > >> work I a
> > > >> >>> separate branch, so it could
> be in
> > parallel to
> > > other
> > > >> developments. I
> > > >> >>> think
> > > >> >>> work over develop is
> practical if
> > there's
> > > something tiny that
> > > >> could
> > > >> >> be
> > > >> >>> done
> > > >> >>> in a commit. But as we need
> more than
> > one, or is
> > > a long
> > > >> process (like
> > > >> >>> this), chances are to make
> develop
> > branch
> > > unstable and even
> > > >> for some
> > > >> >>> days.
> > > >> >>> I think we should try to
> avoid that
> > scenario,
> > > and branches are
> > > >> the
> > > >> >> best
> > > >> >>> way. If we do this way,
> we'll benefit
> > of more
> > > reliable develop
> > > >> >> branch.
> > > >> >>>
> > > >> >>> Thanks and good to know of
> this plan :)
> > > >> >>>
> > > >> >>> Carlos
> > > >> >>>
> > > >> >>>
> > > >> >>> El mar., 5 feb. 2019 a las
> 23:19,
> > Harbs (<
> > > >> harbs.lists@gmail.com>)
> > > >> >>> escribió:
> > > >> >>>
> > > >> >>>> I’ve never used Docker myself,
> but that
> > might be a
> > > good plan.
> > > >> >>>>
> > > >> >>>>> On Feb 6, 2019, at 12:07 AM,
> OmPrakash
> > Muppirala <
> > > >> >>> bigosmallm@gmail.com>
> > > >> >>>> wrote:
> > > >> >>>>>
> > > >> >>>>> I was wondering if we can use
> docker
> > images to
> > > setup and seal
> > > >> the
> > > >> >>> RM
> > > >> >>>>> environment. Then other RMs
> simply
> > need to run
> > > the image
> > > >> locally
> > > >> >>> and run
> > > >> >>>>> the release scripts. Might
> be easier.
> > If folks
> > > like this plan,
> > > >> >> I
> > > >> >>> can
> > > >> >>>> try
> > > >> >>>>> to put something together.
> > > >> >>>>>
> > > >> >>>>> Thanks,
> > > >> >>>>> Om
> > > >> >>>>>
> > > >> >>>>> On Tue, Feb 5, 2019 at 1:40
> PM Harbs <
> > > harbs.lists@gmail.com>
> > > >> >>> wrote:
> > > >> >>>>>
> > > >> >>>>>> In a recent discussion, it
> looks like
> > other
> > > projects have
> > > >> gotten
> > > >> >>>> resources
> > > >> >>>>>> from AWS.
> > > >> >>>>>>
> > > >> >>>>>> Whatever service we use,
> could setup a
> > “shared”
> > > Royale account
> > > >> >>> that all
> > > >> >>>>>> PMC members could have
> access to.
> > > >> >>>>>>
> > > >> >>>>>> I don’t know if there’s some
> way we
> > could
> > > leverage Gitlab’s
> > > >> >>> integration
> > > >> >>>>>> pipelines
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=nfhbWtXmtxNEITbNNH4pvU37rQo6glA2VUBJFPC1Flg%3D&reserved=0
> > > >> >>> <
> > > >> >>>>>>
> > > >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=nfhbWtXmtxNEITbNNH4pvU37rQo6glA2VUBJFPC1Flg%3D&reserved=0
> > > >> >>>>
> > > >> >>>>>>
> > > >> >>>>>>> On Feb 5, 2019, at 11:33
> PM, Alex
> > Harui
> > > >> >> <aharui@adobe.com.INVALID
> > > >> >>>>
> > > >> >>>>>> wrote:
> > > >> >>>>>>>
> > > >> >>>>>>> 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" <
> > > >> >> piotrzarzycki21@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.lists@gmail.com
> > > >> >>> wrote:
> > > >> >>>>>>>
> > > >> >>>>>>>> A big +1 from me!
> > > >> >>>>>>>>
> > > >> >>>>>>>> Looking forward!
> > > >> >>>>>>>>
> > > >> >>>>>>>>> On Feb 5, 2019, at 9:34
> PM, Alex
> > Harui
> > > >> >>> <ah...@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
> > >
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Well, that turned out to be much more time-consuming than I expected, but we can now create identical release artifacts on Mac and Win. I am hopeful this effort will pay off not only now in having other folks generate releases, but also in the future if signed binaries become a requirement.
There continues to be a lot of distractions in my life that can cause delays, but I hope to merge the release_practice branches into develop over the next day or two and figure out where in the wiki to document the release process. So, now is the time for one or more people to step up to be the RMs for 0.9.6 and help debug and improve the process.
I am going to try very hard not to "own" the process. If something goes wrong, I am going to ask others to try to debug and fix it first because it is in the project's best interests for others to truly understand how this stuff works.
Thanks,
-Alex
On 5/23/19, 9:54 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
It has turned out to be harder than expected to get the same binaries on Mac and Win. I now have the identical binaries for royale-compiler and royale-typedefs Maven artifacts and am starting on royale-asjs. I might get lucky and the changes that fixed royale-typedefs SWCs will magically get the royale-asjs SWCs to match. Then we have to make the Ant artifacts match.
There have been a lot of distractions in my non-work life which has also impeded progress. I hope to make much progress this coming week and if we're lucky, I will be asking for a volunteer (or volunteers) to test drive all of this stuff and be the RM for 0.9.6. I am not going to be the RM.
-Alex
On 5/23/19, 9:39 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Hi Alex,
It's been a while since you have started effort with automating build.
Where are you with that ? Are we closer to started 0.9.6. Do you need any
help with this ?
Thanks,
Piotr
wt., 2 kwi 2019 o 19:30 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> Update:
>
> In order to make verification of binary release packages created on the
> server easier, I have made changes to our build scripts and tools to try to
> generate reproducible binaries. I've seen two different builds compare on
> my Mac. The next challenge will be to see if the server can build a
> package on Windows that will compare on Mac.
>
> One of the changes I needed to make is to JBurg. The version of JBurg we
> use generates method names including a hash that doesn't reproduce the same
> name each time. I have changes to JBurg ready, however JBurg is currently
> under CPL which is category B. We only need one file, we don't need or
> want all of JBurg at this time. The one JBurg file is jointly owned by
> Adobe and Tom Harwood. I've contact Tom and he will be filing an ICLA and
> has given me permission to commit the lines he owns in that one file.
>
> This is the revision of the file that will be donated by Tom/Adobe.
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=XMDpGg0yPP530enC02eH8CQXf66Lsn97FFaqHxJaaio%3D&reserved=0
>
> Once this file goes in with the changes to keep the method names the same,
> there will be more tweaks to the release tasks and then we can try cutting
> a release. I'm thinking we'll be at that point in early May, so now is the
> time to get stuff in for the 0.9.6 release.
>
> Thanks,
> -Alex
>
> On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com> wrote:
>
> I would much rather have others find and fix issues themselves. That
> way, more people than just me will know how to maintain the system. It
> actually turns out that, IMO, a group of people can work on the release.
> There are 14 steps. Literally, 14 different people could execute one step
> each.
>
> My 2 cents,
> -Alex
>
> On 3/8/19, 2:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Alex,
>
> amazing work! congrats to reach to this point! :)
>
> I need to put my head on all of this, but count on me to be a RM.
> I think
> the best thing should be that you be the first RM to try your own
> development at least for the first time, and then the rest of us
> will
> follow you on the next releases. With all this on place we maybe
> could
> release once a month or every two months...
>
> Thanks for doing this :)
>
> Carlos
>
>
> El vie., 8 mar. 2019 a las 1:55, Alex Harui
> (<ah...@adobe.com.invalid>)
> escribió:
>
> > OK, I've now seen Jenkins perform the steps to build the release
> > artifacts. Folks interested in Docker-izing the steps are
> welcome to look
> > at the jobs on the "Royale Release" tab on the CI server.
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=ag8xFP8FhC0ndIumEhlwAKTNImbUy3vLwVGYWiK0a68%3D&reserved=0
> >
> > These steps assume that the RM can run the basic Maven and Ant
> build on
> > the RM's computer. I think that's a fair requirement since all
> of us on the
> > PMC need to able to do that to build the RC in order to vote on
> it.
> > Jenkins does other tasks like run the Maven release plugin
> steps.
> >
> > Currently that results in binaries on Jenkins that are
> downloaded to the
> > RM's computer. These binaries need to be verified by the RM
> which is the
> > next phase I will be starting on now. The RM verifies the bits
> and then
> > PGP signs them. And then the bits are uploaded off the RM's
> computer to
> > Maven Staging or dist.a.o/dev. If that uploading turns out to
> be a point
> > of failure, we have the option of having Jenkins upload the big
> files and
> > have the RM only upload PGP signature files. Or finding a way
> for Jenkins
> > to get the signature files from the RM. The uploads worked fine
> for me,
> > but then again, so did the old script's uploads.
> >
> > Therefore, once I get the binary verification phase completed, I
> think
> > someone other than me should be the RM and try to use these
> steps to
> > generate the release and help debug the process for the next
> RM. So,
> > please try to carve out some time to be the RM. One advantage
> of doing
> > most of the work on Jenkins is that it frees up my computer to
> do other
> > things while Jenkins is cranking away.
> >
> > I think we're at least a week away from binary verification,
> maybe two, so
> > it is time to start thinking about what is going in this release.
> >
> > Thanks,
> > -Alex
> >
> > On 3/7/19, 4:15 PM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> >
> > In case you haven't guessed, I'm testing out Jenkins and its
> ability
> > to create the artifacts and send emails. Please ignore any
> email that
> > looks like a vote or discuss thread.
> >
> > Thanks,
> > -Alex
> >
> > On 2/10/19, 8:44 PM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> >
> > Om,
> >
> > Well, that's what I used for the last release. I'm sure
> there is
> > probably some inaccuracy in it.
> >
> > That said, I'm abandoning that document and taking a new
> angle
> > because that document presumed that the release manager was
> trying to
> > create a release on his/her computer. I've given up on that and
> working on
> > making releases from a shared computer for the reasons I've
> stated
> > upthread. I hope to make some progress on that this week.
> >
> > The key difference is that the new angle does not
> presume that you
> > have Git SSH and PGP signatures all set up on some computer. I
> have not
> > looked into how Docker would handle that. You certainly
> wouldn't want the
> > Docker image to contain your SSH or PGP keys/creds. And if the
> Docker
> > image doesn't, then that is another stumbling block for future
> RMs.
> >
> > The other key difference is that the old script presumed
> you could
> > create the 3 release in 3 huge "easy" steps. We've seen that is
> only true
> > for me. So the new angle creates many discrete steps managed by
> Jenkins.
> >
> > So, it is up to you to decide what you want to
> "Docker-ize". You
> > can try to Docker-ize the current 3 big steps, so RMs can try to
> run it on
> > their systems, but I'd bet they will just faiI due to network
> issues. I
> > would be interested in using Docker to make each of these many
> discrete
> > steps portable to another server. I'm not going to involve
> Docker at this
> > point. My main goal is just to see if I can create a workflow
> of many
> > discrete steps that isn't horribly painful. Once we see what
> these steps
> > turn out to be, then we can worry about server portability of
> those steps.
> >
> > Either way, we want to know about running
> Browser+Selenium for
> > sure. And maybe FlashPlayerDebugger or AIR. I would want to
> know, for
> > example, how you debug a failing checkintest in a Docker
> container.
> >
> > Thanks,
> > -Alex
> >
> >
> > On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <
> bigosmallm@gmail.com>
> > wrote:
> >
> > Alex,
> >
> > Just to be clear, I am following the steps from here
> to try
> > and setup a
> > docker container.
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=JfJSK%2B4xchkDWpv78GpWtFlVMQ%2BoUAE10rv7HdeCZck%3D&reserved=0
> >
> > Is this doc up to date?
> >
> > Thanks,
> > Om
> >
> > On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <
> > bigosmallm@gmail.com>
> > wrote:
> >
> > > One approach is to have each step in the process
> spin up a
> > docker image.
> > > And use docker-compose to run each step. All the
> images can
> > be made to
> > > share a common volume where all the artifacts are
> stored
> > across steps.
> > >
> > > You are right about the networking issue though.
> Any
> > network related
> > > failure that occurs on the host machine will most
> likely
> > occur in the
> > > docker container. Although, I am not clear how we
> can
> > guarantee that the
> > > same issues will not occur on the Jenkins server.
> I mean,
> > what is special
> > > about the Jenkins server that makes it immune to
> these
> > networking issues?
> > >
> > > Thanks,
> > > Om
> > >
> > > On Wed, Feb 6, 2019 at 11:48 AM Alex Harui
> > <ah...@adobe.com.invalid>
> > > wrote:
> > >
> > >> Again, I don't know anything about Docker, but
> before we
> > spend a lot of
> > >> time on Docker, I also want to point out that the
> process
> > to create a
> > >> release cannot really be thought of as "one
> application".
> > It will be a
> > >> series of "steps" to run. How many steps
> depends on
> > whether we think we
> > >> can isolate enough stuff via Docker to be able to
> run
> > Docker on the RM's
> > >> computer instead of some shared computer. On a
> shared
> > computer there will
> > >> be dozens of steps because the RM will need to
> enter
> > passwords to commit
> > >> stuff. On a local computer I guess the RM can
> supply
> > passwords but I think
> > >> there will be stopping points where the Maven
> artifacts are
> > deployed and
> > >> the staging repo is closed, and another stopping
> point for
> > the vote. It
> > >> seems like Docker works by downloading
> dependencies. Given
> > that the
> > >> problem the RMs had last time involved downloads
> and
> > uploads, why do we
> > >> think Docker will really solve this for creating
> releases
> > on local machines?
> > >>
> > >> The reason to do this on a shared machine is so
> that new
> > RMs don't have
> > >> to do as much setup. But then I wonder about the
> > efficiency of kicking off
> > >> that many Docker images. Jenkins can manage that
> already.
> > Does Docker
> > >> have some sort of similar Dashboard or would we
> use Jenkins
> > to kick off
> > >> Docker steps? I can't quite picture what is the
> outermost
> > >> control/dashboard.
> > >>
> > >> -Alex
> > >>
> > >> On 2/6/19, 11:03 AM, "Harbs" <
> harbs.lists@gmail.com> wrote:
> > >>
> > >> A quick search turns up this:
> > >>
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=FUYuwlg6rT8EgffgT3QoP8YWcyzjXxNdrT8aN0jq1H4%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=FUYuwlg6rT8EgffgT3QoP8YWcyzjXxNdrT8aN0jq1H4%3D&reserved=0
> > >> >
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=T4QPL4Hh552jE67uYLU1Xu2hDv61NLfuk4u2V6GS%2Bek%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686158656&sdata=T4QPL4Hh552jE67uYLU1Xu2hDv61NLfuk4u2V6GS%2Bek%3D&reserved=0
> > >> >
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=3r1pbB7qdx%2FQUpas%2FyQFs4ICsZUF7vBemIOm%2FArz6ZM%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=3r1pbB7qdx%2FQUpas%2FyQFs4ICsZUF7vBemIOm%2FArz6ZM%3D&reserved=0
> > >> >
> > >>
> > >> > On Feb 6, 2019, at 8:59 PM, Alex Harui
> > <ah...@adobe.com.INVALID>
> > >> wrote:
> > >> >
> > >> > Thanks for volunteering to try it Om. IMO,
> even more
> > important
> > >> than Firefox+Flash is SomeBrowser+Selenium. We
> may also
> > need to run Adobe
> > >> AIR's adb. We could probably turn off the Flash
> tests or
> > replace Flash
> > >> with AIR.
> > >> >
> > >> > Thanks,
> > >> > -Alex
> > >> >
> > >> > On 2/6/19, 10:54 AM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > >> wrote:
> > >> >
> > >> > Hi Om, that would be great! waiting for
> your
> > experience with a
> > >> that! :)
> > >> >
> > >> > El mié., 6 feb. 2019 a las 19:31,
> OmPrakash
> > Muppirala (<
> > >> bigosmallm@gmail.com>)
> > >> > escribió:
> > >> >
> > >> >> Yes, I agree with Alex about not being
> able to run
> > UI out of docker
> > >> >> containers. I never thought of the
> checkintests
> > when I made the
> > >> >> suggestion.
> > >> >>
> > >> >> The firefox-flash image that Yishay
> pointed out
> > looks promising.
> > >> I will
> > >> >> poke around with it and see if that works
> for us.
> > >> >>
> > >> >> Thanks,
> > >> >> Om
> > >> >>
> > >> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay
> Weiss <
> > >> yishayjobs@hotmail.com>
> > >> >> wrote:
> > >> >>
> > >> >>> I’ll let Om or someone else with docker
> experience
> > tell us if
> > >> this [1] is
> > >> >>> relevant.
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>> [1]
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=t1ZG3j7i5LnUTpdSEW78jLfn4K3gIDLnhpJNeaonTjg%3D&reserved=0
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>> ________________________________
> > >> >>> From: Alex Harui <aharui@adobe.com.INVALID
> >
> > >> >>> Sent: Wednesday, February 6, 2019
> 10:05:54 AM
> > >> >>> To: dev@royale.apache.org
> > >> >>> Subject: Re: 0.9.6 Release
> > >> >>>
> > >> >>> I don't anything about docker, but in 15
> minutes of
> > reading I ran
> > >> into
> > >> >>> this:
> > >> >>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=ZOuiuLuyYx1I5w2expOtx1tGxDXIQqnKcSoFYUNkZeA%3D&reserved=0
> > >> >>>
> > >> >>> Which says: Docker can't " Run
> applications with
> > graphical
> > >> interfaces".
> > >> >>> If you want Royale to use Docker for
> releases, show
> > that it can
> > >> run
> > >> >>> checkintests with Flash and the Browser.
> Then I
> > will look into
> > >> it more.
> > >> >>>
> > >> >>> The highest level goal is to make it as
> easy as
> > possible for
> > >> someone to
> > >> >>> volunteer to be an RM. Any requirement
> of "install
> > this (Docker,
> > >> etc) on
> > >> >>> your computer" is, IMO, another barrier
> to entry.
> > Yeah, RMs will
> > >> have to
> > >> >>> have Maven installed and maybe Ant, but
> you should
> > already have
> > >> those
> > >> >>> installed to be a committer/PMC member.
> > >> >>>
> > >> >>> That said, a good takeaway from the
> Docker idea is
> > to try to find
> > >> a way
> > >> >> to
> > >> >>> make an "Image" of whatever we end up
> with on
> > whatever server we
> > >> end up
> > >> >>> using so if the image can be copied and
> used on
> > other servers.
> > >> I'm not
> > >> >>> exactly sure how to do that with Azure,
> which hosts
> > my CI
> > >> server. I will
> > >> >>> spend a few more minutes researching that.
> > >> >>>
> > >> >>> I could not quickly find any way to get a
> free VM
> > on Azure or AWS
> > >> that
> > >> >>> isn't a
> free-trial-start-paying-after-a-year. So,
> > unless someone
> > >> comes
> > >> >> up
> > >> >>> with a free server we can use "forever",
> I'm going
> > to just start
> > >> with my
> > >> >>> Azure VM.
> > >> >>>
> > >> >>> -Alex
> > >> >>>
> > >> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > >> wrote:
> > >> >>>
> > >> >>> Hi.
> > >> >>>
> > >> >>> the plan sounds very good to me. Just
> my 2
> > thoughts on this:
> > >> >>>
> > >> >>> 1.- As I was reading I was thinking as
> well on
> > something like
> > >> Docker
> > >> >>> and
> > >> >>> see Om as well thinking on the same.
> Maybe is
> > the way to this
> > >> with
> > >> >> the
> > >> >>> actual technology. Seems VMs are
> stepping out a
> > bit this days
> > >> in
> > >> >> favor
> > >> >>> of
> > >> >>> things like Docker. Maybe the same did
> Git over
> > Svn, and today
> > >> Svn is
> > >> >>> an
> > >> >>> old remembrance. I must say that I
> have no
> > experience with
> > >> Docker, so
> > >> >>> doing
> > >> >>> that will require acquire that
> knowledge, but
> > seems it could
> > >> be worth
> > >> >>> it.
> > >> >>>
> > >> >>> 2.- Maybe is not possible, but I want
> to propose
> > to do this
> > >> work I a
> > >> >>> separate branch, so it could be in
> parallel to
> > other
> > >> developments. I
> > >> >>> think
> > >> >>> work over develop is practical if
> there's
> > something tiny that
> > >> could
> > >> >> be
> > >> >>> done
> > >> >>> in a commit. But as we need more than
> one, or is
> > a long
> > >> process (like
> > >> >>> this), chances are to make develop
> branch
> > unstable and even
> > >> for some
> > >> >>> days.
> > >> >>> I think we should try to avoid that
> scenario,
> > and branches are
> > >> the
> > >> >> best
> > >> >>> way. If we do this way, we'll benefit
> of more
> > reliable develop
> > >> >> branch.
> > >> >>>
> > >> >>> Thanks and good to know of this plan :)
> > >> >>>
> > >> >>> Carlos
> > >> >>>
> > >> >>>
> > >> >>> El mar., 5 feb. 2019 a las 23:19,
> Harbs (<
> > >> harbs.lists@gmail.com>)
> > >> >>> escribió:
> > >> >>>
> > >> >>>> I’ve never used Docker myself, but that
> might be a
> > good plan.
> > >> >>>>
> > >> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash
> Muppirala <
> > >> >>> bigosmallm@gmail.com>
> > >> >>>> wrote:
> > >> >>>>>
> > >> >>>>> I was wondering if we can use docker
> images to
> > setup and seal
> > >> the
> > >> >>> RM
> > >> >>>>> environment. Then other RMs simply
> need to run
> > the image
> > >> locally
> > >> >>> and run
> > >> >>>>> the release scripts. Might be easier.
> If folks
> > like this plan,
> > >> >> I
> > >> >>> can
> > >> >>>> try
> > >> >>>>> to put something together.
> > >> >>>>>
> > >> >>>>> Thanks,
> > >> >>>>> Om
> > >> >>>>>
> > >> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <
> > harbs.lists@gmail.com>
> > >> >>> wrote:
> > >> >>>>>
> > >> >>>>>> In a recent discussion, it looks like
> other
> > projects have
> > >> gotten
> > >> >>>> resources
> > >> >>>>>> from AWS.
> > >> >>>>>>
> > >> >>>>>> Whatever service we use, could setup a
> “shared”
> > Royale account
> > >> >>> that all
> > >> >>>>>> PMC members could have access to.
> > >> >>>>>>
> > >> >>>>>> I don’t know if there’s some way we
> could
> > leverage Gitlab’s
> > >> >>> integration
> > >> >>>>>> pipelines
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=nfhbWtXmtxNEITbNNH4pvU37rQo6glA2VUBJFPC1Flg%3D&reserved=0
> > >> >>> <
> > >> >>>>>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=nfhbWtXmtxNEITbNNH4pvU37rQo6glA2VUBJFPC1Flg%3D&reserved=0
> > >> >>>>
> > >> >>>>>>
> > >> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex
> Harui
> > >> >> <aharui@adobe.com.INVALID
> > >> >>>>
> > >> >>>>>> wrote:
> > >> >>>>>>>
> > >> >>>>>>> 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" <
> > >> >> piotrzarzycki21@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.lists@gmail.com
> > >> >>> wrote:
> > >> >>>>>>>
> > >> >>>>>>>> A big +1 from me!
> > >> >>>>>>>>
> > >> >>>>>>>> Looking forward!
> > >> >>>>>>>>
> > >> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex
> Harui
> > >> >>> <ah...@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
> > >> >>>>>>>>>
> > >> >>>>>>>>
> > >> >>>>>>>>
> > >> >>>>>>>
> > >> >>>>>>>
> > >> >>>>>>
> > >> >>>>>>
> > >> >>>>
> > >> >>>>
> > >> >>>
> > >> >>> --
> > >> >>> Carlos Rovira
> > >> >>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=aFVs1XRlpMcj%2FowuTBSqaMBV5trkxpWw3G1YtTW5TdA%3D&reserved=0
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>
> > >> >
> > >> >
> > >> > --
> > >> > Carlos Rovira
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=aFVs1XRlpMcj%2FowuTBSqaMBV5trkxpWw3G1YtTW5TdA%3D&reserved=0
> > >> >
> > >> >
> > >>
> > >>
> > >>
> > >>
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=aFVs1XRlpMcj%2FowuTBSqaMBV5trkxpWw3G1YtTW5TdA%3D&reserved=0
>
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686168650&sdata=xaAiKgOCGXApwtixrYSPmBJbdqbQsnKuX3pqObtH16w%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C0f33e0555f7f4b92400e08d6df9f50ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942272686178646&sdata=cnTaZKSrQhWnYJ%2BgW1J6ht2mbZsgsRHD94By%2BZKvAXc%3D&reserved=0>*
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
It has turned out to be harder than expected to get the same binaries on Mac and Win. I now have the identical binaries for royale-compiler and royale-typedefs Maven artifacts and am starting on royale-asjs. I might get lucky and the changes that fixed royale-typedefs SWCs will magically get the royale-asjs SWCs to match. Then we have to make the Ant artifacts match.
There have been a lot of distractions in my non-work life which has also impeded progress. I hope to make much progress this coming week and if we're lucky, I will be asking for a volunteer (or volunteers) to test drive all of this stuff and be the RM for 0.9.6. I am not going to be the RM.
-Alex
On 5/23/19, 9:39 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
Hi Alex,
It's been a while since you have started effort with automating build.
Where are you with that ? Are we closer to started 0.9.6. Do you need any
help with this ?
Thanks,
Piotr
wt., 2 kwi 2019 o 19:30 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> Update:
>
> In order to make verification of binary release packages created on the
> server easier, I have made changes to our build scripts and tools to try to
> generate reproducible binaries. I've seen two different builds compare on
> my Mac. The next challenge will be to see if the server can build a
> package on Windows that will compare on Mac.
>
> One of the changes I needed to make is to JBurg. The version of JBurg we
> use generates method names including a hash that doesn't reproduce the same
> name each time. I have changes to JBurg ready, however JBurg is currently
> under CPL which is category B. We only need one file, we don't need or
> want all of JBurg at this time. The one JBurg file is jointly owned by
> Adobe and Tom Harwood. I've contact Tom and he will be filing an ICLA and
> has given me permission to commit the lines he owns in that one file.
>
> This is the revision of the file that will be donated by Tom/Adobe.
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fjburg%2Fcode%2Fci%2F66c287943376a74ac791f3d3bf969ab160bf80ff%2Ftree%2Fsrc%2Fgenerator%2Fjburg%2Fburg%2FJBurgGenerator.java&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095&sdata=1p0EhJm%2Be7CdkNlE5MHMEJ9EoPINgBGKVU6hlE8C0kQ%3D&reserved=0
>
> Once this file goes in with the changes to keep the method names the same,
> there will be more tweaks to the release tasks and then we can try cutting
> a release. I'm thinking we'll be at that point in early May, so now is the
> time to get stuff in for the 0.9.6 release.
>
> Thanks,
> -Alex
>
> On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com> wrote:
>
> I would much rather have others find and fix issues themselves. That
> way, more people than just me will know how to maintain the system. It
> actually turns out that, IMO, a group of people can work on the release.
> There are 14 steps. Literally, 14 different people could execute one step
> each.
>
> My 2 cents,
> -Alex
>
> On 3/8/19, 2:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Alex,
>
> amazing work! congrats to reach to this point! :)
>
> I need to put my head on all of this, but count on me to be a RM.
> I think
> the best thing should be that you be the first RM to try your own
> development at least for the first time, and then the rest of us
> will
> follow you on the next releases. With all this on place we maybe
> could
> release once a month or every two months...
>
> Thanks for doing this :)
>
> Carlos
>
>
> El vie., 8 mar. 2019 a las 1:55, Alex Harui
> (<ah...@adobe.com.invalid>)
> escribió:
>
> > OK, I've now seen Jenkins perform the steps to build the release
> > artifacts. Folks interested in Docker-izing the steps are
> welcome to look
> > at the jobs on the "Royale Release" tab on the CI server.
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095&sdata=OtDqx0O91trBGYlhEimqYdhTiJXhsCw1YRe6uaV9OF8%3D&reserved=0
> >
> > These steps assume that the RM can run the basic Maven and Ant
> build on
> > the RM's computer. I think that's a fair requirement since all
> of us on the
> > PMC need to able to do that to build the RC in order to vote on
> it.
> > Jenkins does other tasks like run the Maven release plugin
> steps.
> >
> > Currently that results in binaries on Jenkins that are
> downloaded to the
> > RM's computer. These binaries need to be verified by the RM
> which is the
> > next phase I will be starting on now. The RM verifies the bits
> and then
> > PGP signs them. And then the bits are uploaded off the RM's
> computer to
> > Maven Staging or dist.a.o/dev. If that uploading turns out to
> be a point
> > of failure, we have the option of having Jenkins upload the big
> files and
> > have the RM only upload PGP signature files. Or finding a way
> for Jenkins
> > to get the signature files from the RM. The uploads worked fine
> for me,
> > but then again, so did the old script's uploads.
> >
> > Therefore, once I get the binary verification phase completed, I
> think
> > someone other than me should be the RM and try to use these
> steps to
> > generate the release and help debug the process for the next
> RM. So,
> > please try to carve out some time to be the RM. One advantage
> of doing
> > most of the work on Jenkins is that it frees up my computer to
> do other
> > things while Jenkins is cranking away.
> >
> > I think we're at least a week away from binary verification,
> maybe two, so
> > it is time to start thinking about what is going in this release.
> >
> > Thanks,
> > -Alex
> >
> > On 3/7/19, 4:15 PM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> >
> > In case you haven't guessed, I'm testing out Jenkins and its
> ability
> > to create the artifacts and send emails. Please ignore any
> email that
> > looks like a vote or discuss thread.
> >
> > Thanks,
> > -Alex
> >
> > On 2/10/19, 8:44 PM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> >
> > Om,
> >
> > Well, that's what I used for the last release. I'm sure
> there is
> > probably some inaccuracy in it.
> >
> > That said, I'm abandoning that document and taking a new
> angle
> > because that document presumed that the release manager was
> trying to
> > create a release on his/her computer. I've given up on that and
> working on
> > making releases from a shared computer for the reasons I've
> stated
> > upthread. I hope to make some progress on that this week.
> >
> > The key difference is that the new angle does not
> presume that you
> > have Git SSH and PGP signatures all set up on some computer. I
> have not
> > looked into how Docker would handle that. You certainly
> wouldn't want the
> > Docker image to contain your SSH or PGP keys/creds. And if the
> Docker
> > image doesn't, then that is another stumbling block for future
> RMs.
> >
> > The other key difference is that the old script presumed
> you could
> > create the 3 release in 3 huge "easy" steps. We've seen that is
> only true
> > for me. So the new angle creates many discrete steps managed by
> Jenkins.
> >
> > So, it is up to you to decide what you want to
> "Docker-ize". You
> > can try to Docker-ize the current 3 big steps, so RMs can try to
> run it on
> > their systems, but I'd bet they will just faiI due to network
> issues. I
> > would be interested in using Docker to make each of these many
> discrete
> > steps portable to another server. I'm not going to involve
> Docker at this
> > point. My main goal is just to see if I can create a workflow
> of many
> > discrete steps that isn't horribly painful. Once we see what
> these steps
> > turn out to be, then we can worry about server portability of
> those steps.
> >
> > Either way, we want to know about running
> Browser+Selenium for
> > sure. And maybe FlashPlayerDebugger or AIR. I would want to
> know, for
> > example, how you debug a failing checkintest in a Docker
> container.
> >
> > Thanks,
> > -Alex
> >
> >
> > On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <
> bigosmallm@gmail.com>
> > wrote:
> >
> > Alex,
> >
> > Just to be clear, I am following the steps from here
> to try
> > and setup a
> > docker container.
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095&sdata=M3ckCTAILe%2FVyVIeMmV3tybH8JiVq6cy7PmvCSkH3Pk%3D&reserved=0
> >
> > Is this doc up to date?
> >
> > Thanks,
> > Om
> >
> > On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <
> > bigosmallm@gmail.com>
> > wrote:
> >
> > > One approach is to have each step in the process
> spin up a
> > docker image.
> > > And use docker-compose to run each step. All the
> images can
> > be made to
> > > share a common volume where all the artifacts are
> stored
> > across steps.
> > >
> > > You are right about the networking issue though.
> Any
> > network related
> > > failure that occurs on the host machine will most
> likely
> > occur in the
> > > docker container. Although, I am not clear how we
> can
> > guarantee that the
> > > same issues will not occur on the Jenkins server.
> I mean,
> > what is special
> > > about the Jenkins server that makes it immune to
> these
> > networking issues?
> > >
> > > Thanks,
> > > Om
> > >
> > > On Wed, Feb 6, 2019 at 11:48 AM Alex Harui
> > <ah...@adobe.com.invalid>
> > > wrote:
> > >
> > >> Again, I don't know anything about Docker, but
> before we
> > spend a lot of
> > >> time on Docker, I also want to point out that the
> process
> > to create a
> > >> release cannot really be thought of as "one
> application".
> > It will be a
> > >> series of "steps" to run. How many steps
> depends on
> > whether we think we
> > >> can isolate enough stuff via Docker to be able to
> run
> > Docker on the RM's
> > >> computer instead of some shared computer. On a
> shared
> > computer there will
> > >> be dozens of steps because the RM will need to
> enter
> > passwords to commit
> > >> stuff. On a local computer I guess the RM can
> supply
> > passwords but I think
> > >> there will be stopping points where the Maven
> artifacts are
> > deployed and
> > >> the staging repo is closed, and another stopping
> point for
> > the vote. It
> > >> seems like Docker works by downloading
> dependencies. Given
> > that the
> > >> problem the RMs had last time involved downloads
> and
> > uploads, why do we
> > >> think Docker will really solve this for creating
> releases
> > on local machines?
> > >>
> > >> The reason to do this on a shared machine is so
> that new
> > RMs don't have
> > >> to do as much setup. But then I wonder about the
> > efficiency of kicking off
> > >> that many Docker images. Jenkins can manage that
> already.
> > Does Docker
> > >> have some sort of similar Dashboard or would we
> use Jenkins
> > to kick off
> > >> Docker steps? I can't quite picture what is the
> outermost
> > >> control/dashboard.
> > >>
> > >> -Alex
> > >>
> > >> On 2/6/19, 11:03 AM, "Harbs" <
> harbs.lists@gmail.com> wrote:
> > >>
> > >> A quick search turns up this:
> > >>
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095&sdata=qxK2JWFPpxzEBAlERUEYahRC1sB02Nbo8YnNBEchWPk%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095&sdata=qxK2JWFPpxzEBAlERUEYahRC1sB02Nbo8YnNBEchWPk%3D&reserved=0
> > >> >
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907528095&sdata=NplRCecGDitm7JlODUJPaNi294kXdr2UVVvhm%2BuPFQ0%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=d9WGdfMgG%2BeOXY18VGdFon39GxraphfngvhrbnsfwUQ%3D&reserved=0
> > >> >
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=Rzs4ZWB8ZsALg%2FCjfyRXNtQqfgZcF70eGrnbZDQMkWo%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=Rzs4ZWB8ZsALg%2FCjfyRXNtQqfgZcF70eGrnbZDQMkWo%3D&reserved=0
> > >> >
> > >>
> > >> > On Feb 6, 2019, at 8:59 PM, Alex Harui
> > <ah...@adobe.com.INVALID>
> > >> wrote:
> > >> >
> > >> > Thanks for volunteering to try it Om. IMO,
> even more
> > important
> > >> than Firefox+Flash is SomeBrowser+Selenium. We
> may also
> > need to run Adobe
> > >> AIR's adb. We could probably turn off the Flash
> tests or
> > replace Flash
> > >> with AIR.
> > >> >
> > >> > Thanks,
> > >> > -Alex
> > >> >
> > >> > On 2/6/19, 10:54 AM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > >> wrote:
> > >> >
> > >> > Hi Om, that would be great! waiting for
> your
> > experience with a
> > >> that! :)
> > >> >
> > >> > El mié., 6 feb. 2019 a las 19:31,
> OmPrakash
> > Muppirala (<
> > >> bigosmallm@gmail.com>)
> > >> > escribió:
> > >> >
> > >> >> Yes, I agree with Alex about not being
> able to run
> > UI out of docker
> > >> >> containers. I never thought of the
> checkintests
> > when I made the
> > >> >> suggestion.
> > >> >>
> > >> >> The firefox-flash image that Yishay
> pointed out
> > looks promising.
> > >> I will
> > >> >> poke around with it and see if that works
> for us.
> > >> >>
> > >> >> Thanks,
> > >> >> Om
> > >> >>
> > >> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay
> Weiss <
> > >> yishayjobs@hotmail.com>
> > >> >> wrote:
> > >> >>
> > >> >>> I’ll let Om or someone else with docker
> experience
> > tell us if
> > >> this [1] is
> > >> >>> relevant.
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>> [1]
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=dxaDA7W1gty6zgFaB8HbmRFj5BW8v8JFH5icojRgQic%3D&reserved=0
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>> ________________________________
> > >> >>> From: Alex Harui <aharui@adobe.com.INVALID
> >
> > >> >>> Sent: Wednesday, February 6, 2019
> 10:05:54 AM
> > >> >>> To: dev@royale.apache.org
> > >> >>> Subject: Re: 0.9.6 Release
> > >> >>>
> > >> >>> I don't anything about docker, but in 15
> minutes of
> > reading I ran
> > >> into
> > >> >>> this:
> > >> >>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=U1sknyW%2FIRwPeQperIpjyLOE%2B52%2FmTB2IDpNwyG6jz4%3D&reserved=0
> > >> >>>
> > >> >>> Which says: Docker can't " Run
> applications with
> > graphical
> > >> interfaces".
> > >> >>> If you want Royale to use Docker for
> releases, show
> > that it can
> > >> run
> > >> >>> checkintests with Flash and the Browser.
> Then I
> > will look into
> > >> it more.
> > >> >>>
> > >> >>> The highest level goal is to make it as
> easy as
> > possible for
> > >> someone to
> > >> >>> volunteer to be an RM. Any requirement
> of "install
> > this (Docker,
> > >> etc) on
> > >> >>> your computer" is, IMO, another barrier
> to entry.
> > Yeah, RMs will
> > >> have to
> > >> >>> have Maven installed and maybe Ant, but
> you should
> > already have
> > >> those
> > >> >>> installed to be a committer/PMC member.
> > >> >>>
> > >> >>> That said, a good takeaway from the
> Docker idea is
> > to try to find
> > >> a way
> > >> >> to
> > >> >>> make an "Image" of whatever we end up
> with on
> > whatever server we
> > >> end up
> > >> >>> using so if the image can be copied and
> used on
> > other servers.
> > >> I'm not
> > >> >>> exactly sure how to do that with Azure,
> which hosts
> > my CI
> > >> server. I will
> > >> >>> spend a few more minutes researching that.
> > >> >>>
> > >> >>> I could not quickly find any way to get a
> free VM
> > on Azure or AWS
> > >> that
> > >> >>> isn't a
> free-trial-start-paying-after-a-year. So,
> > unless someone
> > >> comes
> > >> >> up
> > >> >>> with a free server we can use "forever",
> I'm going
> > to just start
> > >> with my
> > >> >>> Azure VM.
> > >> >>>
> > >> >>> -Alex
> > >> >>>
> > >> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > >> wrote:
> > >> >>>
> > >> >>> Hi.
> > >> >>>
> > >> >>> the plan sounds very good to me. Just
> my 2
> > thoughts on this:
> > >> >>>
> > >> >>> 1.- As I was reading I was thinking as
> well on
> > something like
> > >> Docker
> > >> >>> and
> > >> >>> see Om as well thinking on the same.
> Maybe is
> > the way to this
> > >> with
> > >> >> the
> > >> >>> actual technology. Seems VMs are
> stepping out a
> > bit this days
> > >> in
> > >> >> favor
> > >> >>> of
> > >> >>> things like Docker. Maybe the same did
> Git over
> > Svn, and today
> > >> Svn is
> > >> >>> an
> > >> >>> old remembrance. I must say that I
> have no
> > experience with
> > >> Docker, so
> > >> >>> doing
> > >> >>> that will require acquire that
> knowledge, but
> > seems it could
> > >> be worth
> > >> >>> it.
> > >> >>>
> > >> >>> 2.- Maybe is not possible, but I want
> to propose
> > to do this
> > >> work I a
> > >> >>> separate branch, so it could be in
> parallel to
> > other
> > >> developments. I
> > >> >>> think
> > >> >>> work over develop is practical if
> there's
> > something tiny that
> > >> could
> > >> >> be
> > >> >>> done
> > >> >>> in a commit. But as we need more than
> one, or is
> > a long
> > >> process (like
> > >> >>> this), chances are to make develop
> branch
> > unstable and even
> > >> for some
> > >> >>> days.
> > >> >>> I think we should try to avoid that
> scenario,
> > and branches are
> > >> the
> > >> >> best
> > >> >>> way. If we do this way, we'll benefit
> of more
> > reliable develop
> > >> >> branch.
> > >> >>>
> > >> >>> Thanks and good to know of this plan :)
> > >> >>>
> > >> >>> Carlos
> > >> >>>
> > >> >>>
> > >> >>> El mar., 5 feb. 2019 a las 23:19,
> Harbs (<
> > >> harbs.lists@gmail.com>)
> > >> >>> escribió:
> > >> >>>
> > >> >>>> I’ve never used Docker myself, but that
> might be a
> > good plan.
> > >> >>>>
> > >> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash
> Muppirala <
> > >> >>> bigosmallm@gmail.com>
> > >> >>>> wrote:
> > >> >>>>>
> > >> >>>>> I was wondering if we can use docker
> images to
> > setup and seal
> > >> the
> > >> >>> RM
> > >> >>>>> environment. Then other RMs simply
> need to run
> > the image
> > >> locally
> > >> >>> and run
> > >> >>>>> the release scripts. Might be easier.
> If folks
> > like this plan,
> > >> >> I
> > >> >>> can
> > >> >>>> try
> > >> >>>>> to put something together.
> > >> >>>>>
> > >> >>>>> Thanks,
> > >> >>>>> Om
> > >> >>>>>
> > >> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <
> > harbs.lists@gmail.com>
> > >> >>> wrote:
> > >> >>>>>
> > >> >>>>>> In a recent discussion, it looks like
> other
> > projects have
> > >> gotten
> > >> >>>> resources
> > >> >>>>>> from AWS.
> > >> >>>>>>
> > >> >>>>>> Whatever service we use, could setup a
> “shared”
> > Royale account
> > >> >>> that all
> > >> >>>>>> PMC members could have access to.
> > >> >>>>>>
> > >> >>>>>> I don’t know if there’s some way we
> could
> > leverage Gitlab’s
> > >> >>> integration
> > >> >>>>>> pipelines
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=DPP6VhjSgo5mGugE1xxzMK7z3Q0aXz%2FSi4QJr3sO3z0%3D&reserved=0
> > >> >>> <
> > >> >>>>>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=DPP6VhjSgo5mGugE1xxzMK7z3Q0aXz%2FSi4QJr3sO3z0%3D&reserved=0
> > >> >>>>
> > >> >>>>>>
> > >> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex
> Harui
> > >> >> <aharui@adobe.com.INVALID
> > >> >>>>
> > >> >>>>>> wrote:
> > >> >>>>>>>
> > >> >>>>>>> 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" <
> > >> >> piotrzarzycki21@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.lists@gmail.com
> > >> >>> wrote:
> > >> >>>>>>>
> > >> >>>>>>>> A big +1 from me!
> > >> >>>>>>>>
> > >> >>>>>>>> Looking forward!
> > >> >>>>>>>>
> > >> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex
> Harui
> > >> >>> <ah...@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
> > >> >>>>>>>>>
> > >> >>>>>>>>
> > >> >>>>>>>>
> > >> >>>>>>>
> > >> >>>>>>>
> > >> >>>>>>
> > >> >>>>>>
> > >> >>>>
> > >> >>>>
> > >> >>>
> > >> >>> --
> > >> >>> Carlos Rovira
> > >> >>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=blcYO7%2F37ZW%2FEBFhqN7aIqnfGdDEz2idac%2BbrGa5cTE%3D&reserved=0
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>
> > >> >
> > >> >
> > >> > --
> > >> > Carlos Rovira
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907538090&sdata=blcYO7%2F37ZW%2FEBFhqN7aIqnfGdDEz2idac%2BbrGa5cTE%3D&reserved=0
> > >> >
> > >> >
> > >>
> > >>
> > >>
> > >>
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907548084&sdata=H6LPsS7BpzoZiaRUEf4n3XdEpvTWQlzIUknJaXFZBGo%3D&reserved=0
>
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907548084&sdata=f4S4MDFSY1Y5%2Fstuucdc4KqI94YJWwmcNas%2F8GHevCA%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C74ccc0a4a31440c0651708d6df9d4326%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636942263907548084&sdata=f4S4MDFSY1Y5%2Fstuucdc4KqI94YJWwmcNas%2F8GHevCA%3D&reserved=0>*
Re: 0.9.6 Release
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Alex,
It's been a while since you have started effort with automating build.
Where are you with that ? Are we closer to started 0.9.6. Do you need any
help with this ?
Thanks,
Piotr
wt., 2 kwi 2019 o 19:30 Alex Harui <ah...@adobe.com.invalid> napisał(a):
> Update:
>
> In order to make verification of binary release packages created on the
> server easier, I have made changes to our build scripts and tools to try to
> generate reproducible binaries. I've seen two different builds compare on
> my Mac. The next challenge will be to see if the server can build a
> package on Windows that will compare on Mac.
>
> One of the changes I needed to make is to JBurg. The version of JBurg we
> use generates method names including a hash that doesn't reproduce the same
> name each time. I have changes to JBurg ready, however JBurg is currently
> under CPL which is category B. We only need one file, we don't need or
> want all of JBurg at this time. The one JBurg file is jointly owned by
> Adobe and Tom Harwood. I've contact Tom and he will be filing an ICLA and
> has given me permission to commit the lines he owns in that one file.
>
> This is the revision of the file that will be donated by Tom/Adobe.
>
> https://sourceforge.net/p/jburg/code/ci/66c287943376a74ac791f3d3bf969ab160bf80ff/tree/src/generator/jburg/burg/JBurgGenerator.java
>
> Once this file goes in with the changes to keep the method names the same,
> there will be more tweaks to the release tasks and then we can try cutting
> a release. I'm thinking we'll be at that point in early May, so now is the
> time to get stuff in for the 0.9.6 release.
>
> Thanks,
> -Alex
>
> On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com> wrote:
>
> I would much rather have others find and fix issues themselves. That
> way, more people than just me will know how to maintain the system. It
> actually turns out that, IMO, a group of people can work on the release.
> There are 14 steps. Literally, 14 different people could execute one step
> each.
>
> My 2 cents,
> -Alex
>
> On 3/8/19, 2:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Alex,
>
> amazing work! congrats to reach to this point! :)
>
> I need to put my head on all of this, but count on me to be a RM.
> I think
> the best thing should be that you be the first RM to try your own
> development at least for the first time, and then the rest of us
> will
> follow you on the next releases. With all this on place we maybe
> could
> release once a month or every two months...
>
> Thanks for doing this :)
>
> Carlos
>
>
> El vie., 8 mar. 2019 a las 1:55, Alex Harui
> (<ah...@adobe.com.invalid>)
> escribió:
>
> > OK, I've now seen Jenkins perform the steps to build the release
> > artifacts. Folks interested in Docker-izing the steps are
> welcome to look
> > at the jobs on the "Royale Release" tab on the CI server.
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352984672&sdata=iVyd9X1U0qVPwCk0ZW9xa7YsPp64EgAxgIwljR7VbNs%3D&reserved=0
> >
> > These steps assume that the RM can run the basic Maven and Ant
> build on
> > the RM's computer. I think that's a fair requirement since all
> of us on the
> > PMC need to able to do that to build the RC in order to vote on
> it.
> > Jenkins does other tasks like run the Maven release plugin
> steps.
> >
> > Currently that results in binaries on Jenkins that are
> downloaded to the
> > RM's computer. These binaries need to be verified by the RM
> which is the
> > next phase I will be starting on now. The RM verifies the bits
> and then
> > PGP signs them. And then the bits are uploaded off the RM's
> computer to
> > Maven Staging or dist.a.o/dev. If that uploading turns out to
> be a point
> > of failure, we have the option of having Jenkins upload the big
> files and
> > have the RM only upload PGP signature files. Or finding a way
> for Jenkins
> > to get the signature files from the RM. The uploads worked fine
> for me,
> > but then again, so did the old script's uploads.
> >
> > Therefore, once I get the binary verification phase completed, I
> think
> > someone other than me should be the RM and try to use these
> steps to
> > generate the release and help debug the process for the next
> RM. So,
> > please try to carve out some time to be the RM. One advantage
> of doing
> > most of the work on Jenkins is that it frees up my computer to
> do other
> > things while Jenkins is cranking away.
> >
> > I think we're at least a week away from binary verification,
> maybe two, so
> > it is time to start thinking about what is going in this release.
> >
> > Thanks,
> > -Alex
> >
> > On 3/7/19, 4:15 PM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> >
> > In case you haven't guessed, I'm testing out Jenkins and its
> ability
> > to create the artifacts and send emails. Please ignore any
> email that
> > looks like a vote or discuss thread.
> >
> > Thanks,
> > -Alex
> >
> > On 2/10/19, 8:44 PM, "Alex Harui" <ah...@adobe.com.INVALID>
> wrote:
> >
> > Om,
> >
> > Well, that's what I used for the last release. I'm sure
> there is
> > probably some inaccuracy in it.
> >
> > That said, I'm abandoning that document and taking a new
> angle
> > because that document presumed that the release manager was
> trying to
> > create a release on his/her computer. I've given up on that and
> working on
> > making releases from a shared computer for the reasons I've
> stated
> > upthread. I hope to make some progress on that this week.
> >
> > The key difference is that the new angle does not
> presume that you
> > have Git SSH and PGP signatures all set up on some computer. I
> have not
> > looked into how Docker would handle that. You certainly
> wouldn't want the
> > Docker image to contain your SSH or PGP keys/creds. And if the
> Docker
> > image doesn't, then that is another stumbling block for future
> RMs.
> >
> > The other key difference is that the old script presumed
> you could
> > create the 3 release in 3 huge "easy" steps. We've seen that is
> only true
> > for me. So the new angle creates many discrete steps managed by
> Jenkins.
> >
> > So, it is up to you to decide what you want to
> "Docker-ize". You
> > can try to Docker-ize the current 3 big steps, so RMs can try to
> run it on
> > their systems, but I'd bet they will just faiI due to network
> issues. I
> > would be interested in using Docker to make each of these many
> discrete
> > steps portable to another server. I'm not going to involve
> Docker at this
> > point. My main goal is just to see if I can create a workflow
> of many
> > discrete steps that isn't horribly painful. Once we see what
> these steps
> > turn out to be, then we can worry about server portability of
> those steps.
> >
> > Either way, we want to know about running
> Browser+Selenium for
> > sure. And maybe FlashPlayerDebugger or AIR. I would want to
> know, for
> > example, how you debug a failing checkintest in a Docker
> container.
> >
> > Thanks,
> > -Alex
> >
> >
> > On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <
> bigosmallm@gmail.com>
> > wrote:
> >
> > Alex,
> >
> > Just to be clear, I am following the steps from here
> to try
> > and setup a
> > docker container.
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352984672&sdata=o%2FXh1PiseHkFbL8AY%2B45VQYXzAngZyTXl%2FErp83HPXY%3D&reserved=0
> >
> > Is this doc up to date?
> >
> > Thanks,
> > Om
> >
> > On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <
> > bigosmallm@gmail.com>
> > wrote:
> >
> > > One approach is to have each step in the process
> spin up a
> > docker image.
> > > And use docker-compose to run each step. All the
> images can
> > be made to
> > > share a common volume where all the artifacts are
> stored
> > across steps.
> > >
> > > You are right about the networking issue though.
> Any
> > network related
> > > failure that occurs on the host machine will most
> likely
> > occur in the
> > > docker container. Although, I am not clear how we
> can
> > guarantee that the
> > > same issues will not occur on the Jenkins server.
> I mean,
> > what is special
> > > about the Jenkins server that makes it immune to
> these
> > networking issues?
> > >
> > > Thanks,
> > > Om
> > >
> > > On Wed, Feb 6, 2019 at 11:48 AM Alex Harui
> > <ah...@adobe.com.invalid>
> > > wrote:
> > >
> > >> Again, I don't know anything about Docker, but
> before we
> > spend a lot of
> > >> time on Docker, I also want to point out that the
> process
> > to create a
> > >> release cannot really be thought of as "one
> application".
> > It will be a
> > >> series of "steps" to run. How many steps
> depends on
> > whether we think we
> > >> can isolate enough stuff via Docker to be able to
> run
> > Docker on the RM's
> > >> computer instead of some shared computer. On a
> shared
> > computer there will
> > >> be dozens of steps because the RM will need to
> enter
> > passwords to commit
> > >> stuff. On a local computer I guess the RM can
> supply
> > passwords but I think
> > >> there will be stopping points where the Maven
> artifacts are
> > deployed and
> > >> the staging repo is closed, and another stopping
> point for
> > the vote. It
> > >> seems like Docker works by downloading
> dependencies. Given
> > that the
> > >> problem the RMs had last time involved downloads
> and
> > uploads, why do we
> > >> think Docker will really solve this for creating
> releases
> > on local machines?
> > >>
> > >> The reason to do this on a shared machine is so
> that new
> > RMs don't have
> > >> to do as much setup. But then I wonder about the
> > efficiency of kicking off
> > >> that many Docker images. Jenkins can manage that
> already.
> > Does Docker
> > >> have some sort of similar Dashboard or would we
> use Jenkins
> > to kick off
> > >> Docker steps? I can't quite picture what is the
> outermost
> > >> control/dashboard.
> > >>
> > >> -Alex
> > >>
> > >> On 2/6/19, 11:03 AM, "Harbs" <
> harbs.lists@gmail.com> wrote:
> > >>
> > >> A quick search turns up this:
> > >>
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=EbV3MJ0pgO4rtL4b9v6SG439%2F%2FE5NQyynRAN2yYbNKM%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=EbV3MJ0pgO4rtL4b9v6SG439%2F%2FE5NQyynRAN2yYbNKM%3D&reserved=0
> > >> >
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=J2%2Bn5aiSLZCbBmiEr72Ww3pS1RLRjm9ywZJBcJTdGKc%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=J2%2Bn5aiSLZCbBmiEr72Ww3pS1RLRjm9ywZJBcJTdGKc%3D&reserved=0
> > >> >
> > >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=g5IwXSR7RyPo96uBfRyV80sQ7re7vd46kWBtPFW%2FtRo%3D&reserved=0
> > >> <
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=g5IwXSR7RyPo96uBfRyV80sQ7re7vd46kWBtPFW%2FtRo%3D&reserved=0
> > >> >
> > >>
> > >> > On Feb 6, 2019, at 8:59 PM, Alex Harui
> > <ah...@adobe.com.INVALID>
> > >> wrote:
> > >> >
> > >> > Thanks for volunteering to try it Om. IMO,
> even more
> > important
> > >> than Firefox+Flash is SomeBrowser+Selenium. We
> may also
> > need to run Adobe
> > >> AIR's adb. We could probably turn off the Flash
> tests or
> > replace Flash
> > >> with AIR.
> > >> >
> > >> > Thanks,
> > >> > -Alex
> > >> >
> > >> > On 2/6/19, 10:54 AM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > >> wrote:
> > >> >
> > >> > Hi Om, that would be great! waiting for
> your
> > experience with a
> > >> that! :)
> > >> >
> > >> > El mié., 6 feb. 2019 a las 19:31,
> OmPrakash
> > Muppirala (<
> > >> bigosmallm@gmail.com>)
> > >> > escribió:
> > >> >
> > >> >> Yes, I agree with Alex about not being
> able to run
> > UI out of docker
> > >> >> containers. I never thought of the
> checkintests
> > when I made the
> > >> >> suggestion.
> > >> >>
> > >> >> The firefox-flash image that Yishay
> pointed out
> > looks promising.
> > >> I will
> > >> >> poke around with it and see if that works
> for us.
> > >> >>
> > >> >> Thanks,
> > >> >> Om
> > >> >>
> > >> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay
> Weiss <
> > >> yishayjobs@hotmail.com>
> > >> >> wrote:
> > >> >>
> > >> >>> I’ll let Om or someone else with docker
> experience
> > tell us if
> > >> this [1] is
> > >> >>> relevant.
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>> [1]
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=MydXohXUzlTPpR5NrxBlIbLl8HJsSSr1bj3supZbDPc%3D&reserved=0
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>> ________________________________
> > >> >>> From: Alex Harui <aharui@adobe.com.INVALID
> >
> > >> >>> Sent: Wednesday, February 6, 2019
> 10:05:54 AM
> > >> >>> To: dev@royale.apache.org
> > >> >>> Subject: Re: 0.9.6 Release
> > >> >>>
> > >> >>> I don't anything about docker, but in 15
> minutes of
> > reading I ran
> > >> into
> > >> >>> this:
> > >> >>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=6c31f%2F3r3tL7t9z0w8%2B3bc38NIngLrOXZPH3K%2B1QZVE%3D&reserved=0
> > >> >>>
> > >> >>> Which says: Docker can't " Run
> applications with
> > graphical
> > >> interfaces".
> > >> >>> If you want Royale to use Docker for
> releases, show
> > that it can
> > >> run
> > >> >>> checkintests with Flash and the Browser.
> Then I
> > will look into
> > >> it more.
> > >> >>>
> > >> >>> The highest level goal is to make it as
> easy as
> > possible for
> > >> someone to
> > >> >>> volunteer to be an RM. Any requirement
> of "install
> > this (Docker,
> > >> etc) on
> > >> >>> your computer" is, IMO, another barrier
> to entry.
> > Yeah, RMs will
> > >> have to
> > >> >>> have Maven installed and maybe Ant, but
> you should
> > already have
> > >> those
> > >> >>> installed to be a committer/PMC member.
> > >> >>>
> > >> >>> That said, a good takeaway from the
> Docker idea is
> > to try to find
> > >> a way
> > >> >> to
> > >> >>> make an "Image" of whatever we end up
> with on
> > whatever server we
> > >> end up
> > >> >>> using so if the image can be copied and
> used on
> > other servers.
> > >> I'm not
> > >> >>> exactly sure how to do that with Azure,
> which hosts
> > my CI
> > >> server. I will
> > >> >>> spend a few more minutes researching that.
> > >> >>>
> > >> >>> I could not quickly find any way to get a
> free VM
> > on Azure or AWS
> > >> that
> > >> >>> isn't a
> free-trial-start-paying-after-a-year. So,
> > unless someone
> > >> comes
> > >> >> up
> > >> >>> with a free server we can use "forever",
> I'm going
> > to just start
> > >> with my
> > >> >>> Azure VM.
> > >> >>>
> > >> >>> -Alex
> > >> >>>
> > >> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> > >> wrote:
> > >> >>>
> > >> >>> Hi.
> > >> >>>
> > >> >>> the plan sounds very good to me. Just
> my 2
> > thoughts on this:
> > >> >>>
> > >> >>> 1.- As I was reading I was thinking as
> well on
> > something like
> > >> Docker
> > >> >>> and
> > >> >>> see Om as well thinking on the same.
> Maybe is
> > the way to this
> > >> with
> > >> >> the
> > >> >>> actual technology. Seems VMs are
> stepping out a
> > bit this days
> > >> in
> > >> >> favor
> > >> >>> of
> > >> >>> things like Docker. Maybe the same did
> Git over
> > Svn, and today
> > >> Svn is
> > >> >>> an
> > >> >>> old remembrance. I must say that I
> have no
> > experience with
> > >> Docker, so
> > >> >>> doing
> > >> >>> that will require acquire that
> knowledge, but
> > seems it could
> > >> be worth
> > >> >>> it.
> > >> >>>
> > >> >>> 2.- Maybe is not possible, but I want
> to propose
> > to do this
> > >> work I a
> > >> >>> separate branch, so it could be in
> parallel to
> > other
> > >> developments. I
> > >> >>> think
> > >> >>> work over develop is practical if
> there's
> > something tiny that
> > >> could
> > >> >> be
> > >> >>> done
> > >> >>> in a commit. But as we need more than
> one, or is
> > a long
> > >> process (like
> > >> >>> this), chances are to make develop
> branch
> > unstable and even
> > >> for some
> > >> >>> days.
> > >> >>> I think we should try to avoid that
> scenario,
> > and branches are
> > >> the
> > >> >> best
> > >> >>> way. If we do this way, we'll benefit
> of more
> > reliable develop
> > >> >> branch.
> > >> >>>
> > >> >>> Thanks and good to know of this plan :)
> > >> >>>
> > >> >>> Carlos
> > >> >>>
> > >> >>>
> > >> >>> El mar., 5 feb. 2019 a las 23:19,
> Harbs (<
> > >> harbs.lists@gmail.com>)
> > >> >>> escribió:
> > >> >>>
> > >> >>>> I’ve never used Docker myself, but that
> might be a
> > good plan.
> > >> >>>>
> > >> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash
> Muppirala <
> > >> >>> bigosmallm@gmail.com>
> > >> >>>> wrote:
> > >> >>>>>
> > >> >>>>> I was wondering if we can use docker
> images to
> > setup and seal
> > >> the
> > >> >>> RM
> > >> >>>>> environment. Then other RMs simply
> need to run
> > the image
> > >> locally
> > >> >>> and run
> > >> >>>>> the release scripts. Might be easier.
> If folks
> > like this plan,
> > >> >> I
> > >> >>> can
> > >> >>>> try
> > >> >>>>> to put something together.
> > >> >>>>>
> > >> >>>>> Thanks,
> > >> >>>>> Om
> > >> >>>>>
> > >> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <
> > harbs.lists@gmail.com>
> > >> >>> wrote:
> > >> >>>>>
> > >> >>>>>> In a recent discussion, it looks like
> other
> > projects have
> > >> gotten
> > >> >>>> resources
> > >> >>>>>> from AWS.
> > >> >>>>>>
> > >> >>>>>> Whatever service we use, could setup a
> “shared”
> > Royale account
> > >> >>> that all
> > >> >>>>>> PMC members could have access to.
> > >> >>>>>>
> > >> >>>>>> I don’t know if there’s some way we
> could
> > leverage Gitlab’s
> > >> >>> integration
> > >> >>>>>> pipelines
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=1Dzn7Eqn%2FubKMx5LsQN%2BWZ3sbIE4XnG9P9uHlfK16co%3D&reserved=0
> > >> >>> <
> > >> >>>>>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368353004686&sdata=FvSI93YtuUcLpGFVAIHeM3ZJ9sOqVWT%2FkD%2BcDe03naw%3D&reserved=0
> > >> >>>>
> > >> >>>>>>
> > >> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex
> Harui
> > >> >> <aharui@adobe.com.INVALID
> > >> >>>>
> > >> >>>>>> wrote:
> > >> >>>>>>>
> > >> >>>>>>> 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" <
> > >> >> piotrzarzycki21@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.lists@gmail.com
> > >> >>> wrote:
> > >> >>>>>>>
> > >> >>>>>>>> A big +1 from me!
> > >> >>>>>>>>
> > >> >>>>>>>> Looking forward!
> > >> >>>>>>>>
> > >> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex
> Harui
> > >> >>> <ah...@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
> > >> >>>>>>>>>
> > >> >>>>>>>>
> > >> >>>>>>>>
> > >> >>>>>>>
> > >> >>>>>>>
> > >> >>>>>>
> > >> >>>>>>
> > >> >>>>
> > >> >>>>
> > >> >>>
> > >> >>> --
> > >> >>> Carlos Rovira
> > >> >>>
> > >> >>>
> > >> >>
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368353004686&sdata=Pf9ASbhvR0hQ4akNEExnOuQzw5OKxa69ahiDG2Pqyss%3D&reserved=0
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>
> > >> >
> > >> >
> > >> > --
> > >> > Carlos Rovira
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368353004686&sdata=Pf9ASbhvR0hQ4akNEExnOuQzw5OKxa69ahiDG2Pqyss%3D&reserved=0
> > >> >
> > >> >
> > >>
> > >>
> > >>
> > >>
> >
> >
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368353004686&sdata=Pf9ASbhvR0hQ4akNEExnOuQzw5OKxa69ahiDG2Pqyss%3D&reserved=0
>
>
>
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Update:
In order to make verification of binary release packages created on the server easier, I have made changes to our build scripts and tools to try to generate reproducible binaries. I've seen two different builds compare on my Mac. The next challenge will be to see if the server can build a package on Windows that will compare on Mac.
One of the changes I needed to make is to JBurg. The version of JBurg we use generates method names including a hash that doesn't reproduce the same name each time. I have changes to JBurg ready, however JBurg is currently under CPL which is category B. We only need one file, we don't need or want all of JBurg at this time. The one JBurg file is jointly owned by Adobe and Tom Harwood. I've contact Tom and he will be filing an ICLA and has given me permission to commit the lines he owns in that one file.
This is the revision of the file that will be donated by Tom/Adobe.
https://sourceforge.net/p/jburg/code/ci/66c287943376a74ac791f3d3bf969ab160bf80ff/tree/src/generator/jburg/burg/JBurgGenerator.java
Once this file goes in with the changes to keep the method names the same, there will be more tweaks to the release tasks and then we can try cutting a release. I'm thinking we'll be at that point in early May, so now is the time to get stuff in for the 0.9.6 release.
Thanks,
-Alex
On 3/8/19, 9:27 AM, "Alex Harui" <ah...@adobe.com> wrote:
I would much rather have others find and fix issues themselves. That way, more people than just me will know how to maintain the system. It actually turns out that, IMO, a group of people can work on the release. There are 14 steps. Literally, 14 different people could execute one step each.
My 2 cents,
-Alex
On 3/8/19, 2:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi Alex,
amazing work! congrats to reach to this point! :)
I need to put my head on all of this, but count on me to be a RM. I think
the best thing should be that you be the first RM to try your own
development at least for the first time, and then the rest of us will
follow you on the next releases. With all this on place we maybe could
release once a month or every two months...
Thanks for doing this :)
Carlos
El vie., 8 mar. 2019 a las 1:55, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> OK, I've now seen Jenkins perform the steps to build the release
> artifacts. Folks interested in Docker-izing the steps are welcome to look
> at the jobs on the "Royale Release" tab on the CI server.
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352984672&sdata=iVyd9X1U0qVPwCk0ZW9xa7YsPp64EgAxgIwljR7VbNs%3D&reserved=0
>
> These steps assume that the RM can run the basic Maven and Ant build on
> the RM's computer. I think that's a fair requirement since all of us on the
> PMC need to able to do that to build the RC in order to vote on it.
> Jenkins does other tasks like run the Maven release plugin steps.
>
> Currently that results in binaries on Jenkins that are downloaded to the
> RM's computer. These binaries need to be verified by the RM which is the
> next phase I will be starting on now. The RM verifies the bits and then
> PGP signs them. And then the bits are uploaded off the RM's computer to
> Maven Staging or dist.a.o/dev. If that uploading turns out to be a point
> of failure, we have the option of having Jenkins upload the big files and
> have the RM only upload PGP signature files. Or finding a way for Jenkins
> to get the signature files from the RM. The uploads worked fine for me,
> but then again, so did the old script's uploads.
>
> Therefore, once I get the binary verification phase completed, I think
> someone other than me should be the RM and try to use these steps to
> generate the release and help debug the process for the next RM. So,
> please try to carve out some time to be the RM. One advantage of doing
> most of the work on Jenkins is that it frees up my computer to do other
> things while Jenkins is cranking away.
>
> I think we're at least a week away from binary verification, maybe two, so
> it is time to start thinking about what is going in this release.
>
> Thanks,
> -Alex
>
> On 3/7/19, 4:15 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> In case you haven't guessed, I'm testing out Jenkins and its ability
> to create the artifacts and send emails. Please ignore any email that
> looks like a vote or discuss thread.
>
> Thanks,
> -Alex
>
> On 2/10/19, 8:44 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> Om,
>
> Well, that's what I used for the last release. I'm sure there is
> probably some inaccuracy in it.
>
> That said, I'm abandoning that document and taking a new angle
> because that document presumed that the release manager was trying to
> create a release on his/her computer. I've given up on that and working on
> making releases from a shared computer for the reasons I've stated
> upthread. I hope to make some progress on that this week.
>
> The key difference is that the new angle does not presume that you
> have Git SSH and PGP signatures all set up on some computer. I have not
> looked into how Docker would handle that. You certainly wouldn't want the
> Docker image to contain your SSH or PGP keys/creds. And if the Docker
> image doesn't, then that is another stumbling block for future RMs.
>
> The other key difference is that the old script presumed you could
> create the 3 release in 3 huge "easy" steps. We've seen that is only true
> for me. So the new angle creates many discrete steps managed by Jenkins.
>
> So, it is up to you to decide what you want to "Docker-ize". You
> can try to Docker-ize the current 3 big steps, so RMs can try to run it on
> their systems, but I'd bet they will just faiI due to network issues. I
> would be interested in using Docker to make each of these many discrete
> steps portable to another server. I'm not going to involve Docker at this
> point. My main goal is just to see if I can create a workflow of many
> discrete steps that isn't horribly painful. Once we see what these steps
> turn out to be, then we can worry about server portability of those steps.
>
> Either way, we want to know about running Browser+Selenium for
> sure. And maybe FlashPlayerDebugger or AIR. I would want to know, for
> example, how you debug a failing checkintest in a Docker container.
>
> Thanks,
> -Alex
>
>
> On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <bi...@gmail.com>
> wrote:
>
> Alex,
>
> Just to be clear, I am following the steps from here to try
> and setup a
> docker container.
>
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352984672&sdata=o%2FXh1PiseHkFbL8AY%2B45VQYXzAngZyTXl%2FErp83HPXY%3D&reserved=0
>
> Is this doc up to date?
>
> Thanks,
> Om
>
> On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <
> bigosmallm@gmail.com>
> wrote:
>
> > One approach is to have each step in the process spin up a
> docker image.
> > And use docker-compose to run each step. All the images can
> be made to
> > share a common volume where all the artifacts are stored
> across steps.
> >
> > You are right about the networking issue though. Any
> network related
> > failure that occurs on the host machine will most likely
> occur in the
> > docker container. Although, I am not clear how we can
> guarantee that the
> > same issues will not occur on the Jenkins server. I mean,
> what is special
> > about the Jenkins server that makes it immune to these
> networking issues?
> >
> > Thanks,
> > Om
> >
> > On Wed, Feb 6, 2019 at 11:48 AM Alex Harui
> <ah...@adobe.com.invalid>
> > wrote:
> >
> >> Again, I don't know anything about Docker, but before we
> spend a lot of
> >> time on Docker, I also want to point out that the process
> to create a
> >> release cannot really be thought of as "one application".
> It will be a
> >> series of "steps" to run. How many steps depends on
> whether we think we
> >> can isolate enough stuff via Docker to be able to run
> Docker on the RM's
> >> computer instead of some shared computer. On a shared
> computer there will
> >> be dozens of steps because the RM will need to enter
> passwords to commit
> >> stuff. On a local computer I guess the RM can supply
> passwords but I think
> >> there will be stopping points where the Maven artifacts are
> deployed and
> >> the staging repo is closed, and another stopping point for
> the vote. It
> >> seems like Docker works by downloading dependencies. Given
> that the
> >> problem the RMs had last time involved downloads and
> uploads, why do we
> >> think Docker will really solve this for creating releases
> on local machines?
> >>
> >> The reason to do this on a shared machine is so that new
> RMs don't have
> >> to do as much setup. But then I wonder about the
> efficiency of kicking off
> >> that many Docker images. Jenkins can manage that already.
> Does Docker
> >> have some sort of similar Dashboard or would we use Jenkins
> to kick off
> >> Docker steps? I can't quite picture what is the outermost
> >> control/dashboard.
> >>
> >> -Alex
> >>
> >> On 2/6/19, 11:03 AM, "Harbs" <ha...@gmail.com> wrote:
> >>
> >> A quick search turns up this:
> >>
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=EbV3MJ0pgO4rtL4b9v6SG439%2F%2FE5NQyynRAN2yYbNKM%3D&reserved=0
> >> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=EbV3MJ0pgO4rtL4b9v6SG439%2F%2FE5NQyynRAN2yYbNKM%3D&reserved=0
> >> >
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=J2%2Bn5aiSLZCbBmiEr72Ww3pS1RLRjm9ywZJBcJTdGKc%3D&reserved=0
> >> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=J2%2Bn5aiSLZCbBmiEr72Ww3pS1RLRjm9ywZJBcJTdGKc%3D&reserved=0
> >> >
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=g5IwXSR7RyPo96uBfRyV80sQ7re7vd46kWBtPFW%2FtRo%3D&reserved=0
> >> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=g5IwXSR7RyPo96uBfRyV80sQ7re7vd46kWBtPFW%2FtRo%3D&reserved=0
> >> >
> >>
> >> > On Feb 6, 2019, at 8:59 PM, Alex Harui
> <ah...@adobe.com.INVALID>
> >> wrote:
> >> >
> >> > Thanks for volunteering to try it Om. IMO, even more
> important
> >> than Firefox+Flash is SomeBrowser+Selenium. We may also
> need to run Adobe
> >> AIR's adb. We could probably turn off the Flash tests or
> replace Flash
> >> with AIR.
> >> >
> >> > Thanks,
> >> > -Alex
> >> >
> >> > On 2/6/19, 10:54 AM, "Carlos Rovira" <
> carlosrovira@apache.org>
> >> wrote:
> >> >
> >> > Hi Om, that would be great! waiting for your
> experience with a
> >> that! :)
> >> >
> >> > El mié., 6 feb. 2019 a las 19:31, OmPrakash
> Muppirala (<
> >> bigosmallm@gmail.com>)
> >> > escribió:
> >> >
> >> >> Yes, I agree with Alex about not being able to run
> UI out of docker
> >> >> containers. I never thought of the checkintests
> when I made the
> >> >> suggestion.
> >> >>
> >> >> The firefox-flash image that Yishay pointed out
> looks promising.
> >> I will
> >> >> poke around with it and see if that works for us.
> >> >>
> >> >> Thanks,
> >> >> Om
> >> >>
> >> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <
> >> yishayjobs@hotmail.com>
> >> >> wrote:
> >> >>
> >> >>> I’ll let Om or someone else with docker experience
> tell us if
> >> this [1] is
> >> >>> relevant.
> >> >>>
> >> >>>
> >> >>>
> >> >>> [1]
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=MydXohXUzlTPpR5NrxBlIbLl8HJsSSr1bj3supZbDPc%3D&reserved=0
> >> >>>
> >> >>>
> >> >>>
> >> >>> ________________________________
> >> >>> From: Alex Harui <ah...@adobe.com.INVALID>
> >> >>> Sent: Wednesday, February 6, 2019 10:05:54 AM
> >> >>> To: dev@royale.apache.org
> >> >>> Subject: Re: 0.9.6 Release
> >> >>>
> >> >>> I don't anything about docker, but in 15 minutes of
> reading I ran
> >> into
> >> >>> this:
> >> >>>
> >> >>>
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=6c31f%2F3r3tL7t9z0w8%2B3bc38NIngLrOXZPH3K%2B1QZVE%3D&reserved=0
> >> >>>
> >> >>> Which says: Docker can't " Run applications with
> graphical
> >> interfaces".
> >> >>> If you want Royale to use Docker for releases, show
> that it can
> >> run
> >> >>> checkintests with Flash and the Browser. Then I
> will look into
> >> it more.
> >> >>>
> >> >>> The highest level goal is to make it as easy as
> possible for
> >> someone to
> >> >>> volunteer to be an RM. Any requirement of "install
> this (Docker,
> >> etc) on
> >> >>> your computer" is, IMO, another barrier to entry.
> Yeah, RMs will
> >> have to
> >> >>> have Maven installed and maybe Ant, but you should
> already have
> >> those
> >> >>> installed to be a committer/PMC member.
> >> >>>
> >> >>> That said, a good takeaway from the Docker idea is
> to try to find
> >> a way
> >> >> to
> >> >>> make an "Image" of whatever we end up with on
> whatever server we
> >> end up
> >> >>> using so if the image can be copied and used on
> other servers.
> >> I'm not
> >> >>> exactly sure how to do that with Azure, which hosts
> my CI
> >> server. I will
> >> >>> spend a few more minutes researching that.
> >> >>>
> >> >>> I could not quickly find any way to get a free VM
> on Azure or AWS
> >> that
> >> >>> isn't a free-trial-start-paying-after-a-year. So,
> unless someone
> >> comes
> >> >> up
> >> >>> with a free server we can use "forever", I'm going
> to just start
> >> with my
> >> >>> Azure VM.
> >> >>>
> >> >>> -Alex
> >> >>>
> >> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <
> carlosrovira@apache.org>
> >> wrote:
> >> >>>
> >> >>> Hi.
> >> >>>
> >> >>> the plan sounds very good to me. Just my 2
> thoughts on this:
> >> >>>
> >> >>> 1.- As I was reading I was thinking as well on
> something like
> >> Docker
> >> >>> and
> >> >>> see Om as well thinking on the same. Maybe is
> the way to this
> >> with
> >> >> the
> >> >>> actual technology. Seems VMs are stepping out a
> bit this days
> >> in
> >> >> favor
> >> >>> of
> >> >>> things like Docker. Maybe the same did Git over
> Svn, and today
> >> Svn is
> >> >>> an
> >> >>> old remembrance. I must say that I have no
> experience with
> >> Docker, so
> >> >>> doing
> >> >>> that will require acquire that knowledge, but
> seems it could
> >> be worth
> >> >>> it.
> >> >>>
> >> >>> 2.- Maybe is not possible, but I want to propose
> to do this
> >> work I a
> >> >>> separate branch, so it could be in parallel to
> other
> >> developments. I
> >> >>> think
> >> >>> work over develop is practical if there's
> something tiny that
> >> could
> >> >> be
> >> >>> done
> >> >>> in a commit. But as we need more than one, or is
> a long
> >> process (like
> >> >>> this), chances are to make develop branch
> unstable and even
> >> for some
> >> >>> days.
> >> >>> I think we should try to avoid that scenario,
> and branches are
> >> the
> >> >> best
> >> >>> way. If we do this way, we'll benefit of more
> reliable develop
> >> >> branch.
> >> >>>
> >> >>> Thanks and good to know of this plan :)
> >> >>>
> >> >>> Carlos
> >> >>>
> >> >>>
> >> >>> El mar., 5 feb. 2019 a las 23:19, Harbs (<
> >> harbs.lists@gmail.com>)
> >> >>> escribió:
> >> >>>
> >> >>>> I’ve never used Docker myself, but that might be a
> good plan.
> >> >>>>
> >> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
> >> >>> bigosmallm@gmail.com>
> >> >>>> wrote:
> >> >>>>>
> >> >>>>> I was wondering if we can use docker images to
> setup and seal
> >> the
> >> >>> RM
> >> >>>>> environment. Then other RMs simply need to run
> the image
> >> locally
> >> >>> and run
> >> >>>>> the release scripts. Might be easier. If folks
> like this plan,
> >> >> I
> >> >>> can
> >> >>>> try
> >> >>>>> to put something together.
> >> >>>>>
> >> >>>>> Thanks,
> >> >>>>> Om
> >> >>>>>
> >> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <
> harbs.lists@gmail.com>
> >> >>> wrote:
> >> >>>>>
> >> >>>>>> In a recent discussion, it looks like other
> projects have
> >> gotten
> >> >>>> resources
> >> >>>>>> from AWS.
> >> >>>>>>
> >> >>>>>> Whatever service we use, could setup a “shared”
> Royale account
> >> >>> that all
> >> >>>>>> PMC members could have access to.
> >> >>>>>>
> >> >>>>>> I don’t know if there’s some way we could
> leverage Gitlab’s
> >> >>> integration
> >> >>>>>> pipelines
> >> >>>
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=1Dzn7Eqn%2FubKMx5LsQN%2BWZ3sbIE4XnG9P9uHlfK16co%3D&reserved=0
> >> >>> <
> >> >>>>>>
> >> >>>
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368353004686&sdata=FvSI93YtuUcLpGFVAIHeM3ZJ9sOqVWT%2FkD%2BcDe03naw%3D&reserved=0
> >> >>>>
> >> >>>>>>
> >> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
> >> >> <aharui@adobe.com.INVALID
> >> >>>>
> >> >>>>>> wrote:
> >> >>>>>>>
> >> >>>>>>> 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" <
> >> >> piotrzarzycki21@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.lists@gmail.com
> >> >>> wrote:
> >> >>>>>>>
> >> >>>>>>>> A big +1 from me!
> >> >>>>>>>>
> >> >>>>>>>> Looking forward!
> >> >>>>>>>>
> >> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
> >> >>> <ah...@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
> >> >>>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>
> >> >>>>
> >> >>>
> >> >>> --
> >> >>> Carlos Rovira
> >> >>>
> >> >>>
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368353004686&sdata=Pf9ASbhvR0hQ4akNEExnOuQzw5OKxa69ahiDG2Pqyss%3D&reserved=0
> >> >>>
> >> >>>
> >> >>>
> >> >>
> >> >
> >> >
> >> > --
> >> > Carlos Rovira
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368353004686&sdata=Pf9ASbhvR0hQ4akNEExnOuQzw5OKxa69ahiDG2Pqyss%3D&reserved=0
> >> >
> >> >
> >>
> >>
> >>
> >>
>
>
>
>
>
>
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368353004686&sdata=Pf9ASbhvR0hQ4akNEExnOuQzw5OKxa69ahiDG2Pqyss%3D&reserved=0
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I would much rather have others find and fix issues themselves. That way, more people than just me will know how to maintain the system. It actually turns out that, IMO, a group of people can work on the release. There are 14 steps. Literally, 14 different people could execute one step each.
My 2 cents,
-Alex
On 3/8/19, 2:13 AM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi Alex,
amazing work! congrats to reach to this point! :)
I need to put my head on all of this, but count on me to be a RM. I think
the best thing should be that you be the first RM to try your own
development at least for the first time, and then the rest of us will
follow you on the next releases. With all this on place we maybe could
release once a month or every two months...
Thanks for doing this :)
Carlos
El vie., 8 mar. 2019 a las 1:55, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> OK, I've now seen Jenkins perform the steps to build the release
> artifacts. Folks interested in Docker-izing the steps are welcome to look
> at the jobs on the "Royale Release" tab on the CI server.
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2F&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352984672&sdata=iVyd9X1U0qVPwCk0ZW9xa7YsPp64EgAxgIwljR7VbNs%3D&reserved=0
>
> These steps assume that the RM can run the basic Maven and Ant build on
> the RM's computer. I think that's a fair requirement since all of us on the
> PMC need to able to do that to build the RC in order to vote on it.
> Jenkins does other tasks like run the Maven release plugin steps.
>
> Currently that results in binaries on Jenkins that are downloaded to the
> RM's computer. These binaries need to be verified by the RM which is the
> next phase I will be starting on now. The RM verifies the bits and then
> PGP signs them. And then the bits are uploaded off the RM's computer to
> Maven Staging or dist.a.o/dev. If that uploading turns out to be a point
> of failure, we have the option of having Jenkins upload the big files and
> have the RM only upload PGP signature files. Or finding a way for Jenkins
> to get the signature files from the RM. The uploads worked fine for me,
> but then again, so did the old script's uploads.
>
> Therefore, once I get the binary verification phase completed, I think
> someone other than me should be the RM and try to use these steps to
> generate the release and help debug the process for the next RM. So,
> please try to carve out some time to be the RM. One advantage of doing
> most of the work on Jenkins is that it frees up my computer to do other
> things while Jenkins is cranking away.
>
> I think we're at least a week away from binary verification, maybe two, so
> it is time to start thinking about what is going in this release.
>
> Thanks,
> -Alex
>
> On 3/7/19, 4:15 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> In case you haven't guessed, I'm testing out Jenkins and its ability
> to create the artifacts and send emails. Please ignore any email that
> looks like a vote or discuss thread.
>
> Thanks,
> -Alex
>
> On 2/10/19, 8:44 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> Om,
>
> Well, that's what I used for the last release. I'm sure there is
> probably some inaccuracy in it.
>
> That said, I'm abandoning that document and taking a new angle
> because that document presumed that the release manager was trying to
> create a release on his/her computer. I've given up on that and working on
> making releases from a shared computer for the reasons I've stated
> upthread. I hope to make some progress on that this week.
>
> The key difference is that the new angle does not presume that you
> have Git SSH and PGP signatures all set up on some computer. I have not
> looked into how Docker would handle that. You certainly wouldn't want the
> Docker image to contain your SSH or PGP keys/creds. And if the Docker
> image doesn't, then that is another stumbling block for future RMs.
>
> The other key difference is that the old script presumed you could
> create the 3 release in 3 huge "easy" steps. We've seen that is only true
> for me. So the new angle creates many discrete steps managed by Jenkins.
>
> So, it is up to you to decide what you want to "Docker-ize". You
> can try to Docker-ize the current 3 big steps, so RMs can try to run it on
> their systems, but I'd bet they will just faiI due to network issues. I
> would be interested in using Docker to make each of these many discrete
> steps portable to another server. I'm not going to involve Docker at this
> point. My main goal is just to see if I can create a workflow of many
> discrete steps that isn't horribly painful. Once we see what these steps
> turn out to be, then we can worry about server portability of those steps.
>
> Either way, we want to know about running Browser+Selenium for
> sure. And maybe FlashPlayerDebugger or AIR. I would want to know, for
> example, how you debug a failing checkintest in a Docker container.
>
> Thanks,
> -Alex
>
>
> On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <bi...@gmail.com>
> wrote:
>
> Alex,
>
> Just to be clear, I am following the steps from here to try
> and setup a
> docker container.
>
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352984672&sdata=o%2FXh1PiseHkFbL8AY%2B45VQYXzAngZyTXl%2FErp83HPXY%3D&reserved=0
>
> Is this doc up to date?
>
> Thanks,
> Om
>
> On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <
> bigosmallm@gmail.com>
> wrote:
>
> > One approach is to have each step in the process spin up a
> docker image.
> > And use docker-compose to run each step. All the images can
> be made to
> > share a common volume where all the artifacts are stored
> across steps.
> >
> > You are right about the networking issue though. Any
> network related
> > failure that occurs on the host machine will most likely
> occur in the
> > docker container. Although, I am not clear how we can
> guarantee that the
> > same issues will not occur on the Jenkins server. I mean,
> what is special
> > about the Jenkins server that makes it immune to these
> networking issues?
> >
> > Thanks,
> > Om
> >
> > On Wed, Feb 6, 2019 at 11:48 AM Alex Harui
> <ah...@adobe.com.invalid>
> > wrote:
> >
> >> Again, I don't know anything about Docker, but before we
> spend a lot of
> >> time on Docker, I also want to point out that the process
> to create a
> >> release cannot really be thought of as "one application".
> It will be a
> >> series of "steps" to run. How many steps depends on
> whether we think we
> >> can isolate enough stuff via Docker to be able to run
> Docker on the RM's
> >> computer instead of some shared computer. On a shared
> computer there will
> >> be dozens of steps because the RM will need to enter
> passwords to commit
> >> stuff. On a local computer I guess the RM can supply
> passwords but I think
> >> there will be stopping points where the Maven artifacts are
> deployed and
> >> the staging repo is closed, and another stopping point for
> the vote. It
> >> seems like Docker works by downloading dependencies. Given
> that the
> >> problem the RMs had last time involved downloads and
> uploads, why do we
> >> think Docker will really solve this for creating releases
> on local machines?
> >>
> >> The reason to do this on a shared machine is so that new
> RMs don't have
> >> to do as much setup. But then I wonder about the
> efficiency of kicking off
> >> that many Docker images. Jenkins can manage that already.
> Does Docker
> >> have some sort of similar Dashboard or would we use Jenkins
> to kick off
> >> Docker steps? I can't quite picture what is the outermost
> >> control/dashboard.
> >>
> >> -Alex
> >>
> >> On 2/6/19, 11:03 AM, "Harbs" <ha...@gmail.com> wrote:
> >>
> >> A quick search turns up this:
> >>
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=EbV3MJ0pgO4rtL4b9v6SG439%2F%2FE5NQyynRAN2yYbNKM%3D&reserved=0
> >> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=EbV3MJ0pgO4rtL4b9v6SG439%2F%2FE5NQyynRAN2yYbNKM%3D&reserved=0
> >> >
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=J2%2Bn5aiSLZCbBmiEr72Ww3pS1RLRjm9ywZJBcJTdGKc%3D&reserved=0
> >> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=J2%2Bn5aiSLZCbBmiEr72Ww3pS1RLRjm9ywZJBcJTdGKc%3D&reserved=0
> >> >
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=g5IwXSR7RyPo96uBfRyV80sQ7re7vd46kWBtPFW%2FtRo%3D&reserved=0
> >> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=g5IwXSR7RyPo96uBfRyV80sQ7re7vd46kWBtPFW%2FtRo%3D&reserved=0
> >> >
> >>
> >> > On Feb 6, 2019, at 8:59 PM, Alex Harui
> <ah...@adobe.com.INVALID>
> >> wrote:
> >> >
> >> > Thanks for volunteering to try it Om. IMO, even more
> important
> >> than Firefox+Flash is SomeBrowser+Selenium. We may also
> need to run Adobe
> >> AIR's adb. We could probably turn off the Flash tests or
> replace Flash
> >> with AIR.
> >> >
> >> > Thanks,
> >> > -Alex
> >> >
> >> > On 2/6/19, 10:54 AM, "Carlos Rovira" <
> carlosrovira@apache.org>
> >> wrote:
> >> >
> >> > Hi Om, that would be great! waiting for your
> experience with a
> >> that! :)
> >> >
> >> > El mié., 6 feb. 2019 a las 19:31, OmPrakash
> Muppirala (<
> >> bigosmallm@gmail.com>)
> >> > escribió:
> >> >
> >> >> Yes, I agree with Alex about not being able to run
> UI out of docker
> >> >> containers. I never thought of the checkintests
> when I made the
> >> >> suggestion.
> >> >>
> >> >> The firefox-flash image that Yishay pointed out
> looks promising.
> >> I will
> >> >> poke around with it and see if that works for us.
> >> >>
> >> >> Thanks,
> >> >> Om
> >> >>
> >> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <
> >> yishayjobs@hotmail.com>
> >> >> wrote:
> >> >>
> >> >>> I’ll let Om or someone else with docker experience
> tell us if
> >> this [1] is
> >> >>> relevant.
> >> >>>
> >> >>>
> >> >>>
> >> >>> [1]
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=MydXohXUzlTPpR5NrxBlIbLl8HJsSSr1bj3supZbDPc%3D&reserved=0
> >> >>>
> >> >>>
> >> >>>
> >> >>> ________________________________
> >> >>> From: Alex Harui <ah...@adobe.com.INVALID>
> >> >>> Sent: Wednesday, February 6, 2019 10:05:54 AM
> >> >>> To: dev@royale.apache.org
> >> >>> Subject: Re: 0.9.6 Release
> >> >>>
> >> >>> I don't anything about docker, but in 15 minutes of
> reading I ran
> >> into
> >> >>> this:
> >> >>>
> >> >>>
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=6c31f%2F3r3tL7t9z0w8%2B3bc38NIngLrOXZPH3K%2B1QZVE%3D&reserved=0
> >> >>>
> >> >>> Which says: Docker can't " Run applications with
> graphical
> >> interfaces".
> >> >>> If you want Royale to use Docker for releases, show
> that it can
> >> run
> >> >>> checkintests with Flash and the Browser. Then I
> will look into
> >> it more.
> >> >>>
> >> >>> The highest level goal is to make it as easy as
> possible for
> >> someone to
> >> >>> volunteer to be an RM. Any requirement of "install
> this (Docker,
> >> etc) on
> >> >>> your computer" is, IMO, another barrier to entry.
> Yeah, RMs will
> >> have to
> >> >>> have Maven installed and maybe Ant, but you should
> already have
> >> those
> >> >>> installed to be a committer/PMC member.
> >> >>>
> >> >>> That said, a good takeaway from the Docker idea is
> to try to find
> >> a way
> >> >> to
> >> >>> make an "Image" of whatever we end up with on
> whatever server we
> >> end up
> >> >>> using so if the image can be copied and used on
> other servers.
> >> I'm not
> >> >>> exactly sure how to do that with Azure, which hosts
> my CI
> >> server. I will
> >> >>> spend a few more minutes researching that.
> >> >>>
> >> >>> I could not quickly find any way to get a free VM
> on Azure or AWS
> >> that
> >> >>> isn't a free-trial-start-paying-after-a-year. So,
> unless someone
> >> comes
> >> >> up
> >> >>> with a free server we can use "forever", I'm going
> to just start
> >> with my
> >> >>> Azure VM.
> >> >>>
> >> >>> -Alex
> >> >>>
> >> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <
> carlosrovira@apache.org>
> >> wrote:
> >> >>>
> >> >>> Hi.
> >> >>>
> >> >>> the plan sounds very good to me. Just my 2
> thoughts on this:
> >> >>>
> >> >>> 1.- As I was reading I was thinking as well on
> something like
> >> Docker
> >> >>> and
> >> >>> see Om as well thinking on the same. Maybe is
> the way to this
> >> with
> >> >> the
> >> >>> actual technology. Seems VMs are stepping out a
> bit this days
> >> in
> >> >> favor
> >> >>> of
> >> >>> things like Docker. Maybe the same did Git over
> Svn, and today
> >> Svn is
> >> >>> an
> >> >>> old remembrance. I must say that I have no
> experience with
> >> Docker, so
> >> >>> doing
> >> >>> that will require acquire that knowledge, but
> seems it could
> >> be worth
> >> >>> it.
> >> >>>
> >> >>> 2.- Maybe is not possible, but I want to propose
> to do this
> >> work I a
> >> >>> separate branch, so it could be in parallel to
> other
> >> developments. I
> >> >>> think
> >> >>> work over develop is practical if there's
> something tiny that
> >> could
> >> >> be
> >> >>> done
> >> >>> in a commit. But as we need more than one, or is
> a long
> >> process (like
> >> >>> this), chances are to make develop branch
> unstable and even
> >> for some
> >> >>> days.
> >> >>> I think we should try to avoid that scenario,
> and branches are
> >> the
> >> >> best
> >> >>> way. If we do this way, we'll benefit of more
> reliable develop
> >> >> branch.
> >> >>>
> >> >>> Thanks and good to know of this plan :)
> >> >>>
> >> >>> Carlos
> >> >>>
> >> >>>
> >> >>> El mar., 5 feb. 2019 a las 23:19, Harbs (<
> >> harbs.lists@gmail.com>)
> >> >>> escribió:
> >> >>>
> >> >>>> I’ve never used Docker myself, but that might be a
> good plan.
> >> >>>>
> >> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
> >> >>> bigosmallm@gmail.com>
> >> >>>> wrote:
> >> >>>>>
> >> >>>>> I was wondering if we can use docker images to
> setup and seal
> >> the
> >> >>> RM
> >> >>>>> environment. Then other RMs simply need to run
> the image
> >> locally
> >> >>> and run
> >> >>>>> the release scripts. Might be easier. If folks
> like this plan,
> >> >> I
> >> >>> can
> >> >>>> try
> >> >>>>> to put something together.
> >> >>>>>
> >> >>>>> Thanks,
> >> >>>>> Om
> >> >>>>>
> >> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <
> harbs.lists@gmail.com>
> >> >>> wrote:
> >> >>>>>
> >> >>>>>> In a recent discussion, it looks like other
> projects have
> >> gotten
> >> >>>> resources
> >> >>>>>> from AWS.
> >> >>>>>>
> >> >>>>>> Whatever service we use, could setup a “shared”
> Royale account
> >> >>> that all
> >> >>>>>> PMC members could have access to.
> >> >>>>>>
> >> >>>>>> I don’t know if there’s some way we could
> leverage Gitlab’s
> >> >>> integration
> >> >>>>>> pipelines
> >> >>>
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368352994681&sdata=1Dzn7Eqn%2FubKMx5LsQN%2BWZ3sbIE4XnG9P9uHlfK16co%3D&reserved=0
> >> >>> <
> >> >>>>>>
> >> >>>
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368353004686&sdata=FvSI93YtuUcLpGFVAIHeM3ZJ9sOqVWT%2FkD%2BcDe03naw%3D&reserved=0
> >> >>>>
> >> >>>>>>
> >> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
> >> >> <aharui@adobe.com.INVALID
> >> >>>>
> >> >>>>>> wrote:
> >> >>>>>>>
> >> >>>>>>> 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" <
> >> >> piotrzarzycki21@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.lists@gmail.com
> >> >>> wrote:
> >> >>>>>>>
> >> >>>>>>>> A big +1 from me!
> >> >>>>>>>>
> >> >>>>>>>> Looking forward!
> >> >>>>>>>>
> >> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
> >> >>> <ah...@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
> >> >>>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>
> >> >>>>
> >> >>>
> >> >>> --
> >> >>> Carlos Rovira
> >> >>>
> >> >>>
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368353004686&sdata=Pf9ASbhvR0hQ4akNEExnOuQzw5OKxa69ahiDG2Pqyss%3D&reserved=0
> >> >>>
> >> >>>
> >> >>>
> >> >>
> >> >
> >> >
> >> > --
> >> > Carlos Rovira
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368353004686&sdata=Pf9ASbhvR0hQ4akNEExnOuQzw5OKxa69ahiDG2Pqyss%3D&reserved=0
> >> >
> >> >
> >>
> >>
> >>
> >>
>
>
>
>
>
>
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C46d1fe9de1214422ce9f08d6a3aec4d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876368353004686&sdata=Pf9ASbhvR0hQ4akNEExnOuQzw5OKxa69ahiDG2Pqyss%3D&reserved=0
Re: 0.9.6 Release
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,
amazing work! congrats to reach to this point! :)
I need to put my head on all of this, but count on me to be a RM. I think
the best thing should be that you be the first RM to try your own
development at least for the first time, and then the rest of us will
follow you on the next releases. With all this on place we maybe could
release once a month or every two months...
Thanks for doing this :)
Carlos
El vie., 8 mar. 2019 a las 1:55, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> OK, I've now seen Jenkins perform the steps to build the release
> artifacts. Folks interested in Docker-izing the steps are welcome to look
> at the jobs on the "Royale Release" tab on the CI server.
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/
>
> These steps assume that the RM can run the basic Maven and Ant build on
> the RM's computer. I think that's a fair requirement since all of us on the
> PMC need to able to do that to build the RC in order to vote on it.
> Jenkins does other tasks like run the Maven release plugin steps.
>
> Currently that results in binaries on Jenkins that are downloaded to the
> RM's computer. These binaries need to be verified by the RM which is the
> next phase I will be starting on now. The RM verifies the bits and then
> PGP signs them. And then the bits are uploaded off the RM's computer to
> Maven Staging or dist.a.o/dev. If that uploading turns out to be a point
> of failure, we have the option of having Jenkins upload the big files and
> have the RM only upload PGP signature files. Or finding a way for Jenkins
> to get the signature files from the RM. The uploads worked fine for me,
> but then again, so did the old script's uploads.
>
> Therefore, once I get the binary verification phase completed, I think
> someone other than me should be the RM and try to use these steps to
> generate the release and help debug the process for the next RM. So,
> please try to carve out some time to be the RM. One advantage of doing
> most of the work on Jenkins is that it frees up my computer to do other
> things while Jenkins is cranking away.
>
> I think we're at least a week away from binary verification, maybe two, so
> it is time to start thinking about what is going in this release.
>
> Thanks,
> -Alex
>
> On 3/7/19, 4:15 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> In case you haven't guessed, I'm testing out Jenkins and its ability
> to create the artifacts and send emails. Please ignore any email that
> looks like a vote or discuss thread.
>
> Thanks,
> -Alex
>
> On 2/10/19, 8:44 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> Om,
>
> Well, that's what I used for the last release. I'm sure there is
> probably some inaccuracy in it.
>
> That said, I'm abandoning that document and taking a new angle
> because that document presumed that the release manager was trying to
> create a release on his/her computer. I've given up on that and working on
> making releases from a shared computer for the reasons I've stated
> upthread. I hope to make some progress on that this week.
>
> The key difference is that the new angle does not presume that you
> have Git SSH and PGP signatures all set up on some computer. I have not
> looked into how Docker would handle that. You certainly wouldn't want the
> Docker image to contain your SSH or PGP keys/creds. And if the Docker
> image doesn't, then that is another stumbling block for future RMs.
>
> The other key difference is that the old script presumed you could
> create the 3 release in 3 huge "easy" steps. We've seen that is only true
> for me. So the new angle creates many discrete steps managed by Jenkins.
>
> So, it is up to you to decide what you want to "Docker-ize". You
> can try to Docker-ize the current 3 big steps, so RMs can try to run it on
> their systems, but I'd bet they will just faiI due to network issues. I
> would be interested in using Docker to make each of these many discrete
> steps portable to another server. I'm not going to involve Docker at this
> point. My main goal is just to see if I can create a workflow of many
> discrete steps that isn't horribly painful. Once we see what these steps
> turn out to be, then we can worry about server portability of those steps.
>
> Either way, we want to know about running Browser+Selenium for
> sure. And maybe FlashPlayerDebugger or AIR. I would want to know, for
> example, how you debug a failing checkintest in a Docker container.
>
> Thanks,
> -Alex
>
>
> On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <bi...@gmail.com>
> wrote:
>
> Alex,
>
> Just to be clear, I am following the steps from here to try
> and setup a
> docker container.
>
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=rJsHtgUQ%2BH5iQOXlZc%2FCEvtxH0Lm25fGn0wlAe6oqSs%3D&reserved=0
>
> Is this doc up to date?
>
> Thanks,
> Om
>
> On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <
> bigosmallm@gmail.com>
> wrote:
>
> > One approach is to have each step in the process spin up a
> docker image.
> > And use docker-compose to run each step. All the images can
> be made to
> > share a common volume where all the artifacts are stored
> across steps.
> >
> > You are right about the networking issue though. Any
> network related
> > failure that occurs on the host machine will most likely
> occur in the
> > docker container. Although, I am not clear how we can
> guarantee that the
> > same issues will not occur on the Jenkins server. I mean,
> what is special
> > about the Jenkins server that makes it immune to these
> networking issues?
> >
> > Thanks,
> > Om
> >
> > On Wed, Feb 6, 2019 at 11:48 AM Alex Harui
> <ah...@adobe.com.invalid>
> > wrote:
> >
> >> Again, I don't know anything about Docker, but before we
> spend a lot of
> >> time on Docker, I also want to point out that the process
> to create a
> >> release cannot really be thought of as "one application".
> It will be a
> >> series of "steps" to run. How many steps depends on
> whether we think we
> >> can isolate enough stuff via Docker to be able to run
> Docker on the RM's
> >> computer instead of some shared computer. On a shared
> computer there will
> >> be dozens of steps because the RM will need to enter
> passwords to commit
> >> stuff. On a local computer I guess the RM can supply
> passwords but I think
> >> there will be stopping points where the Maven artifacts are
> deployed and
> >> the staging repo is closed, and another stopping point for
> the vote. It
> >> seems like Docker works by downloading dependencies. Given
> that the
> >> problem the RMs had last time involved downloads and
> uploads, why do we
> >> think Docker will really solve this for creating releases
> on local machines?
> >>
> >> The reason to do this on a shared machine is so that new
> RMs don't have
> >> to do as much setup. But then I wonder about the
> efficiency of kicking off
> >> that many Docker images. Jenkins can manage that already.
> Does Docker
> >> have some sort of similar Dashboard or would we use Jenkins
> to kick off
> >> Docker steps? I can't quite picture what is the outermost
> >> control/dashboard.
> >>
> >> -Alex
> >>
> >> On 2/6/19, 11:03 AM, "Harbs" <ha...@gmail.com> wrote:
> >>
> >> A quick search turns up this:
> >>
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=fA7bthRUAGXzqJdmK4raheZMEHQ4qyy3NHXjufAF6jc%3D&reserved=0
> >> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=fA7bthRUAGXzqJdmK4raheZMEHQ4qyy3NHXjufAF6jc%3D&reserved=0
> >> >
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=QeJ5h98H2ghmY%2BMoGWKVgYaS6OKiv9BY7Cbu%2FRYh9K0%3D&reserved=0
> >> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=QeJ5h98H2ghmY%2BMoGWKVgYaS6OKiv9BY7Cbu%2FRYh9K0%3D&reserved=0
> >> >
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=pvNt%2B4Spevu9uXaZeX1bV4AKi3p1KVnwND4XZvqlxt0%3D&reserved=0
> >> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=pvNt%2B4Spevu9uXaZeX1bV4AKi3p1KVnwND4XZvqlxt0%3D&reserved=0
> >> >
> >>
> >> > On Feb 6, 2019, at 8:59 PM, Alex Harui
> <ah...@adobe.com.INVALID>
> >> wrote:
> >> >
> >> > Thanks for volunteering to try it Om. IMO, even more
> important
> >> than Firefox+Flash is SomeBrowser+Selenium. We may also
> need to run Adobe
> >> AIR's adb. We could probably turn off the Flash tests or
> replace Flash
> >> with AIR.
> >> >
> >> > Thanks,
> >> > -Alex
> >> >
> >> > On 2/6/19, 10:54 AM, "Carlos Rovira" <
> carlosrovira@apache.org>
> >> wrote:
> >> >
> >> > Hi Om, that would be great! waiting for your
> experience with a
> >> that! :)
> >> >
> >> > El mié., 6 feb. 2019 a las 19:31, OmPrakash
> Muppirala (<
> >> bigosmallm@gmail.com>)
> >> > escribió:
> >> >
> >> >> Yes, I agree with Alex about not being able to run
> UI out of docker
> >> >> containers. I never thought of the checkintests
> when I made the
> >> >> suggestion.
> >> >>
> >> >> The firefox-flash image that Yishay pointed out
> looks promising.
> >> I will
> >> >> poke around with it and see if that works for us.
> >> >>
> >> >> Thanks,
> >> >> Om
> >> >>
> >> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <
> >> yishayjobs@hotmail.com>
> >> >> wrote:
> >> >>
> >> >>> I’ll let Om or someone else with docker experience
> tell us if
> >> this [1] is
> >> >>> relevant.
> >> >>>
> >> >>>
> >> >>>
> >> >>> [1]
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=O5WCCm7fcFGjaXpoDum5hMAJXl3JWscFMRMywpBAN1w%3D&reserved=0
> >> >>>
> >> >>>
> >> >>>
> >> >>> ________________________________
> >> >>> From: Alex Harui <ah...@adobe.com.INVALID>
> >> >>> Sent: Wednesday, February 6, 2019 10:05:54 AM
> >> >>> To: dev@royale.apache.org
> >> >>> Subject: Re: 0.9.6 Release
> >> >>>
> >> >>> I don't anything about docker, but in 15 minutes of
> reading I ran
> >> into
> >> >>> this:
> >> >>>
> >> >>>
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=bjIQhi1pOBfBd8jQAc0XmbrsWzlDwSqieUiUoSovnIE%3D&reserved=0
> >> >>>
> >> >>> Which says: Docker can't " Run applications with
> graphical
> >> interfaces".
> >> >>> If you want Royale to use Docker for releases, show
> that it can
> >> run
> >> >>> checkintests with Flash and the Browser. Then I
> will look into
> >> it more.
> >> >>>
> >> >>> The highest level goal is to make it as easy as
> possible for
> >> someone to
> >> >>> volunteer to be an RM. Any requirement of "install
> this (Docker,
> >> etc) on
> >> >>> your computer" is, IMO, another barrier to entry.
> Yeah, RMs will
> >> have to
> >> >>> have Maven installed and maybe Ant, but you should
> already have
> >> those
> >> >>> installed to be a committer/PMC member.
> >> >>>
> >> >>> That said, a good takeaway from the Docker idea is
> to try to find
> >> a way
> >> >> to
> >> >>> make an "Image" of whatever we end up with on
> whatever server we
> >> end up
> >> >>> using so if the image can be copied and used on
> other servers.
> >> I'm not
> >> >>> exactly sure how to do that with Azure, which hosts
> my CI
> >> server. I will
> >> >>> spend a few more minutes researching that.
> >> >>>
> >> >>> I could not quickly find any way to get a free VM
> on Azure or AWS
> >> that
> >> >>> isn't a free-trial-start-paying-after-a-year. So,
> unless someone
> >> comes
> >> >> up
> >> >>> with a free server we can use "forever", I'm going
> to just start
> >> with my
> >> >>> Azure VM.
> >> >>>
> >> >>> -Alex
> >> >>>
> >> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <
> carlosrovira@apache.org>
> >> wrote:
> >> >>>
> >> >>> Hi.
> >> >>>
> >> >>> the plan sounds very good to me. Just my 2
> thoughts on this:
> >> >>>
> >> >>> 1.- As I was reading I was thinking as well on
> something like
> >> Docker
> >> >>> and
> >> >>> see Om as well thinking on the same. Maybe is
> the way to this
> >> with
> >> >> the
> >> >>> actual technology. Seems VMs are stepping out a
> bit this days
> >> in
> >> >> favor
> >> >>> of
> >> >>> things like Docker. Maybe the same did Git over
> Svn, and today
> >> Svn is
> >> >>> an
> >> >>> old remembrance. I must say that I have no
> experience with
> >> Docker, so
> >> >>> doing
> >> >>> that will require acquire that knowledge, but
> seems it could
> >> be worth
> >> >>> it.
> >> >>>
> >> >>> 2.- Maybe is not possible, but I want to propose
> to do this
> >> work I a
> >> >>> separate branch, so it could be in parallel to
> other
> >> developments. I
> >> >>> think
> >> >>> work over develop is practical if there's
> something tiny that
> >> could
> >> >> be
> >> >>> done
> >> >>> in a commit. But as we need more than one, or is
> a long
> >> process (like
> >> >>> this), chances are to make develop branch
> unstable and even
> >> for some
> >> >>> days.
> >> >>> I think we should try to avoid that scenario,
> and branches are
> >> the
> >> >> best
> >> >>> way. If we do this way, we'll benefit of more
> reliable develop
> >> >> branch.
> >> >>>
> >> >>> Thanks and good to know of this plan :)
> >> >>>
> >> >>> Carlos
> >> >>>
> >> >>>
> >> >>> El mar., 5 feb. 2019 a las 23:19, Harbs (<
> >> harbs.lists@gmail.com>)
> >> >>> escribió:
> >> >>>
> >> >>>> I’ve never used Docker myself, but that might be a
> good plan.
> >> >>>>
> >> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
> >> >>> bigosmallm@gmail.com>
> >> >>>> wrote:
> >> >>>>>
> >> >>>>> I was wondering if we can use docker images to
> setup and seal
> >> the
> >> >>> RM
> >> >>>>> environment. Then other RMs simply need to run
> the image
> >> locally
> >> >>> and run
> >> >>>>> the release scripts. Might be easier. If folks
> like this plan,
> >> >> I
> >> >>> can
> >> >>>> try
> >> >>>>> to put something together.
> >> >>>>>
> >> >>>>> Thanks,
> >> >>>>> Om
> >> >>>>>
> >> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <
> harbs.lists@gmail.com>
> >> >>> wrote:
> >> >>>>>
> >> >>>>>> In a recent discussion, it looks like other
> projects have
> >> gotten
> >> >>>> resources
> >> >>>>>> from AWS.
> >> >>>>>>
> >> >>>>>> Whatever service we use, could setup a “shared”
> Royale account
> >> >>> that all
> >> >>>>>> PMC members could have access to.
> >> >>>>>>
> >> >>>>>> I don’t know if there’s some way we could
> leverage Gitlab’s
> >> >>> integration
> >> >>>>>> pipelines
> >> >>>
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=ZrqmL9%2B0oXasDm4aDW2q8K%2F%2BEkSc17zQerzJ4m%2BM7lU%3D&reserved=0
> >> >>> <
> >> >>>>>>
> >> >>>
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=ZrqmL9%2B0oXasDm4aDW2q8K%2F%2BEkSc17zQerzJ4m%2BM7lU%3D&reserved=0
> >> >>>>
> >> >>>>>>
> >> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
> >> >> <aharui@adobe.com.INVALID
> >> >>>>
> >> >>>>>> wrote:
> >> >>>>>>>
> >> >>>>>>> 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" <
> >> >> piotrzarzycki21@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.lists@gmail.com
> >> >>> wrote:
> >> >>>>>>>
> >> >>>>>>>> A big +1 from me!
> >> >>>>>>>>
> >> >>>>>>>> Looking forward!
> >> >>>>>>>>
> >> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
> >> >>> <ah...@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
> >> >>>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>
> >> >>>>
> >> >>>
> >> >>> --
> >> >>> Carlos Rovira
> >> >>>
> >> >>>
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=egeH1lqxrifO9sWYd0PO67pKuQP6Riv0N2tEDf9rriA%3D&reserved=0
> >> >>>
> >> >>>
> >> >>>
> >> >>
> >> >
> >> >
> >> > --
> >> > Carlos Rovira
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=egeH1lqxrifO9sWYd0PO67pKuQP6Riv0N2tEDf9rriA%3D&reserved=0
> >> >
> >> >
> >>
> >>
> >>
> >>
>
>
>
>
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
OK, I've now seen Jenkins perform the steps to build the release artifacts. Folks interested in Docker-izing the steps are welcome to look at the jobs on the "Royale Release" tab on the CI server. http://apacheroyaleci.westus2.cloudapp.azure.com:8080/view/Royale%20Release/
These steps assume that the RM can run the basic Maven and Ant build on the RM's computer. I think that's a fair requirement since all of us on the PMC need to able to do that to build the RC in order to vote on it. Jenkins does other tasks like run the Maven release plugin steps.
Currently that results in binaries on Jenkins that are downloaded to the RM's computer. These binaries need to be verified by the RM which is the next phase I will be starting on now. The RM verifies the bits and then PGP signs them. And then the bits are uploaded off the RM's computer to Maven Staging or dist.a.o/dev. If that uploading turns out to be a point of failure, we have the option of having Jenkins upload the big files and have the RM only upload PGP signature files. Or finding a way for Jenkins to get the signature files from the RM. The uploads worked fine for me, but then again, so did the old script's uploads.
Therefore, once I get the binary verification phase completed, I think someone other than me should be the RM and try to use these steps to generate the release and help debug the process for the next RM. So, please try to carve out some time to be the RM. One advantage of doing most of the work on Jenkins is that it frees up my computer to do other things while Jenkins is cranking away.
I think we're at least a week away from binary verification, maybe two, so it is time to start thinking about what is going in this release.
Thanks,
-Alex
On 3/7/19, 4:15 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
In case you haven't guessed, I'm testing out Jenkins and its ability to create the artifacts and send emails. Please ignore any email that looks like a vote or discuss thread.
Thanks,
-Alex
On 2/10/19, 8:44 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
Om,
Well, that's what I used for the last release. I'm sure there is probably some inaccuracy in it.
That said, I'm abandoning that document and taking a new angle because that document presumed that the release manager was trying to create a release on his/her computer. I've given up on that and working on making releases from a shared computer for the reasons I've stated upthread. I hope to make some progress on that this week.
The key difference is that the new angle does not presume that you have Git SSH and PGP signatures all set up on some computer. I have not looked into how Docker would handle that. You certainly wouldn't want the Docker image to contain your SSH or PGP keys/creds. And if the Docker image doesn't, then that is another stumbling block for future RMs.
The other key difference is that the old script presumed you could create the 3 release in 3 huge "easy" steps. We've seen that is only true for me. So the new angle creates many discrete steps managed by Jenkins.
So, it is up to you to decide what you want to "Docker-ize". You can try to Docker-ize the current 3 big steps, so RMs can try to run it on their systems, but I'd bet they will just faiI due to network issues. I would be interested in using Docker to make each of these many discrete steps portable to another server. I'm not going to involve Docker at this point. My main goal is just to see if I can create a workflow of many discrete steps that isn't horribly painful. Once we see what these steps turn out to be, then we can worry about server portability of those steps.
Either way, we want to know about running Browser+Selenium for sure. And maybe FlashPlayerDebugger or AIR. I would want to know, for example, how you debug a failing checkintest in a Docker container.
Thanks,
-Alex
On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
Alex,
Just to be clear, I am following the steps from here to try and setup a
docker container.
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=rJsHtgUQ%2BH5iQOXlZc%2FCEvtxH0Lm25fGn0wlAe6oqSs%3D&reserved=0
Is this doc up to date?
Thanks,
Om
On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <bi...@gmail.com>
wrote:
> One approach is to have each step in the process spin up a docker image.
> And use docker-compose to run each step. All the images can be made to
> share a common volume where all the artifacts are stored across steps.
>
> You are right about the networking issue though. Any network related
> failure that occurs on the host machine will most likely occur in the
> docker container. Although, I am not clear how we can guarantee that the
> same issues will not occur on the Jenkins server. I mean, what is special
> about the Jenkins server that makes it immune to these networking issues?
>
> Thanks,
> Om
>
> On Wed, Feb 6, 2019 at 11:48 AM Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
>> Again, I don't know anything about Docker, but before we spend a lot of
>> time on Docker, I also want to point out that the process to create a
>> release cannot really be thought of as "one application". It will be a
>> series of "steps" to run. How many steps depends on whether we think we
>> can isolate enough stuff via Docker to be able to run Docker on the RM's
>> computer instead of some shared computer. On a shared computer there will
>> be dozens of steps because the RM will need to enter passwords to commit
>> stuff. On a local computer I guess the RM can supply passwords but I think
>> there will be stopping points where the Maven artifacts are deployed and
>> the staging repo is closed, and another stopping point for the vote. It
>> seems like Docker works by downloading dependencies. Given that the
>> problem the RMs had last time involved downloads and uploads, why do we
>> think Docker will really solve this for creating releases on local machines?
>>
>> The reason to do this on a shared machine is so that new RMs don't have
>> to do as much setup. But then I wonder about the efficiency of kicking off
>> that many Docker images. Jenkins can manage that already. Does Docker
>> have some sort of similar Dashboard or would we use Jenkins to kick off
>> Docker steps? I can't quite picture what is the outermost
>> control/dashboard.
>>
>> -Alex
>>
>> On 2/6/19, 11:03 AM, "Harbs" <ha...@gmail.com> wrote:
>>
>> A quick search turns up this:
>>
>>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=fA7bthRUAGXzqJdmK4raheZMEHQ4qyy3NHXjufAF6jc%3D&reserved=0
>> <
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=fA7bthRUAGXzqJdmK4raheZMEHQ4qyy3NHXjufAF6jc%3D&reserved=0
>> >
>>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=QeJ5h98H2ghmY%2BMoGWKVgYaS6OKiv9BY7Cbu%2FRYh9K0%3D&reserved=0
>> <
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=QeJ5h98H2ghmY%2BMoGWKVgYaS6OKiv9BY7Cbu%2FRYh9K0%3D&reserved=0
>> >
>>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=pvNt%2B4Spevu9uXaZeX1bV4AKi3p1KVnwND4XZvqlxt0%3D&reserved=0
>> <
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=pvNt%2B4Spevu9uXaZeX1bV4AKi3p1KVnwND4XZvqlxt0%3D&reserved=0
>> >
>>
>> > On Feb 6, 2019, at 8:59 PM, Alex Harui <ah...@adobe.com.INVALID>
>> wrote:
>> >
>> > Thanks for volunteering to try it Om. IMO, even more important
>> than Firefox+Flash is SomeBrowser+Selenium. We may also need to run Adobe
>> AIR's adb. We could probably turn off the Flash tests or replace Flash
>> with AIR.
>> >
>> > Thanks,
>> > -Alex
>> >
>> > On 2/6/19, 10:54 AM, "Carlos Rovira" <ca...@apache.org>
>> wrote:
>> >
>> > Hi Om, that would be great! waiting for your experience with a
>> that! :)
>> >
>> > El mié., 6 feb. 2019 a las 19:31, OmPrakash Muppirala (<
>> bigosmallm@gmail.com>)
>> > escribió:
>> >
>> >> Yes, I agree with Alex about not being able to run UI out of docker
>> >> containers. I never thought of the checkintests when I made the
>> >> suggestion.
>> >>
>> >> The firefox-flash image that Yishay pointed out looks promising.
>> I will
>> >> poke around with it and see if that works for us.
>> >>
>> >> Thanks,
>> >> Om
>> >>
>> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <
>> yishayjobs@hotmail.com>
>> >> wrote:
>> >>
>> >>> I’ll let Om or someone else with docker experience tell us if
>> this [1] is
>> >>> relevant.
>> >>>
>> >>>
>> >>>
>> >>> [1]
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396&sdata=O5WCCm7fcFGjaXpoDum5hMAJXl3JWscFMRMywpBAN1w%3D&reserved=0
>> >>>
>> >>>
>> >>>
>> >>> ________________________________
>> >>> From: Alex Harui <ah...@adobe.com.INVALID>
>> >>> Sent: Wednesday, February 6, 2019 10:05:54 AM
>> >>> To: dev@royale.apache.org
>> >>> Subject: Re: 0.9.6 Release
>> >>>
>> >>> I don't anything about docker, but in 15 minutes of reading I ran
>> into
>> >>> this:
>> >>>
>> >>>
>> >>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=bjIQhi1pOBfBd8jQAc0XmbrsWzlDwSqieUiUoSovnIE%3D&reserved=0
>> >>>
>> >>> Which says: Docker can't " Run applications with graphical
>> interfaces".
>> >>> If you want Royale to use Docker for releases, show that it can
>> run
>> >>> checkintests with Flash and the Browser. Then I will look into
>> it more.
>> >>>
>> >>> The highest level goal is to make it as easy as possible for
>> someone to
>> >>> volunteer to be an RM. Any requirement of "install this (Docker,
>> etc) on
>> >>> your computer" is, IMO, another barrier to entry. Yeah, RMs will
>> have to
>> >>> have Maven installed and maybe Ant, but you should already have
>> those
>> >>> installed to be a committer/PMC member.
>> >>>
>> >>> That said, a good takeaway from the Docker idea is to try to find
>> a way
>> >> to
>> >>> make an "Image" of whatever we end up with on whatever server we
>> end up
>> >>> using so if the image can be copied and used on other servers.
>> I'm not
>> >>> exactly sure how to do that with Azure, which hosts my CI
>> server. I will
>> >>> spend a few more minutes researching that.
>> >>>
>> >>> I could not quickly find any way to get a free VM on Azure or AWS
>> that
>> >>> isn't a free-trial-start-paying-after-a-year. So, unless someone
>> comes
>> >> up
>> >>> with a free server we can use "forever", I'm going to just start
>> with my
>> >>> Azure VM.
>> >>>
>> >>> -Alex
>> >>>
>> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org>
>> wrote:
>> >>>
>> >>> Hi.
>> >>>
>> >>> the plan sounds very good to me. Just my 2 thoughts on this:
>> >>>
>> >>> 1.- As I was reading I was thinking as well on something like
>> Docker
>> >>> and
>> >>> see Om as well thinking on the same. Maybe is the way to this
>> with
>> >> the
>> >>> actual technology. Seems VMs are stepping out a bit this days
>> in
>> >> favor
>> >>> of
>> >>> things like Docker. Maybe the same did Git over Svn, and today
>> Svn is
>> >>> an
>> >>> old remembrance. I must say that I have no experience with
>> Docker, so
>> >>> doing
>> >>> that will require acquire that knowledge, but seems it could
>> be worth
>> >>> it.
>> >>>
>> >>> 2.- Maybe is not possible, but I want to propose to do this
>> work I a
>> >>> separate branch, so it could be in parallel to other
>> developments. I
>> >>> think
>> >>> work over develop is practical if there's something tiny that
>> could
>> >> be
>> >>> done
>> >>> in a commit. But as we need more than one, or is a long
>> process (like
>> >>> this), chances are to make develop branch unstable and even
>> for some
>> >>> days.
>> >>> I think we should try to avoid that scenario, and branches are
>> the
>> >> best
>> >>> way. If we do this way, we'll benefit of more reliable develop
>> >> branch.
>> >>>
>> >>> Thanks and good to know of this plan :)
>> >>>
>> >>> Carlos
>> >>>
>> >>>
>> >>> El mar., 5 feb. 2019 a las 23:19, Harbs (<
>> harbs.lists@gmail.com>)
>> >>> escribió:
>> >>>
>> >>>> I’ve never used Docker myself, but that might be a good plan.
>> >>>>
>> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
>> >>> bigosmallm@gmail.com>
>> >>>> wrote:
>> >>>>>
>> >>>>> I was wondering if we can use docker images to setup and seal
>> the
>> >>> RM
>> >>>>> environment. Then other RMs simply need to run the image
>> locally
>> >>> and run
>> >>>>> the release scripts. Might be easier. If folks like this plan,
>> >> I
>> >>> can
>> >>>> try
>> >>>>> to put something together.
>> >>>>>
>> >>>>> Thanks,
>> >>>>> Om
>> >>>>>
>> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com>
>> >>> wrote:
>> >>>>>
>> >>>>>> In a recent discussion, it looks like other projects have
>> gotten
>> >>>> resources
>> >>>>>> from AWS.
>> >>>>>>
>> >>>>>> Whatever service we use, could setup a “shared” Royale account
>> >>> that all
>> >>>>>> PMC members could have access to.
>> >>>>>>
>> >>>>>> I don’t know if there’s some way we could leverage Gitlab’s
>> >>> integration
>> >>>>>> pipelines
>> >>>
>> >>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=ZrqmL9%2B0oXasDm4aDW2q8K%2F%2BEkSc17zQerzJ4m%2BM7lU%3D&reserved=0
>> >>> <
>> >>>>>>
>> >>>
>> >>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=ZrqmL9%2B0oXasDm4aDW2q8K%2F%2BEkSc17zQerzJ4m%2BM7lU%3D&reserved=0
>> >>>>
>> >>>>>>
>> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
>> >> <aharui@adobe.com.INVALID
>> >>>>
>> >>>>>> wrote:
>> >>>>>>>
>> >>>>>>> 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" <
>> >> piotrzarzycki21@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.lists@gmail.com
>> >>> wrote:
>> >>>>>>>
>> >>>>>>>> A big +1 from me!
>> >>>>>>>>
>> >>>>>>>> Looking forward!
>> >>>>>>>>
>> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
>> >>> <ah...@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
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>
>> >>>>
>> >>>
>> >>> --
>> >>> Carlos Rovira
>> >>>
>> >>>
>> >>
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=egeH1lqxrifO9sWYd0PO67pKuQP6Riv0N2tEDf9rriA%3D&reserved=0
>> >>>
>> >>>
>> >>>
>> >>
>> >
>> >
>> > --
>> > Carlos Rovira
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505602405&sdata=egeH1lqxrifO9sWYd0PO67pKuQP6Riv0N2tEDf9rriA%3D&reserved=0
>> >
>> >
>>
>>
>>
>>
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
In case you haven't guessed, I'm testing out Jenkins and its ability to create the artifacts and send emails. Please ignore any email that looks like a vote or discuss thread.
Thanks,
-Alex
On 2/10/19, 8:44 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
Om,
Well, that's what I used for the last release. I'm sure there is probably some inaccuracy in it.
That said, I'm abandoning that document and taking a new angle because that document presumed that the release manager was trying to create a release on his/her computer. I've given up on that and working on making releases from a shared computer for the reasons I've stated upthread. I hope to make some progress on that this week.
The key difference is that the new angle does not presume that you have Git SSH and PGP signatures all set up on some computer. I have not looked into how Docker would handle that. You certainly wouldn't want the Docker image to contain your SSH or PGP keys/creds. And if the Docker image doesn't, then that is another stumbling block for future RMs.
The other key difference is that the old script presumed you could create the 3 release in 3 huge "easy" steps. We've seen that is only true for me. So the new angle creates many discrete steps managed by Jenkins.
So, it is up to you to decide what you want to "Docker-ize". You can try to Docker-ize the current 3 big steps, so RMs can try to run it on their systems, but I'd bet they will just faiI due to network issues. I would be interested in using Docker to make each of these many discrete steps portable to another server. I'm not going to involve Docker at this point. My main goal is just to see if I can create a workflow of many discrete steps that isn't horribly painful. Once we see what these steps turn out to be, then we can worry about server portability of those steps.
Either way, we want to know about running Browser+Selenium for sure. And maybe FlashPlayerDebugger or AIR. I would want to know, for example, how you debug a failing checkintest in a Docker container.
Thanks,
-Alex
On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
Alex,
Just to be clear, I am following the steps from here to try and setup a
docker container.
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955237368&sdata=C2ctMRVZzdUAjIgVwO3OvqTjMfrMRmbd4Ruuxx2yC4k%3D&reserved=0
Is this doc up to date?
Thanks,
Om
On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <bi...@gmail.com>
wrote:
> One approach is to have each step in the process spin up a docker image.
> And use docker-compose to run each step. All the images can be made to
> share a common volume where all the artifacts are stored across steps.
>
> You are right about the networking issue though. Any network related
> failure that occurs on the host machine will most likely occur in the
> docker container. Although, I am not clear how we can guarantee that the
> same issues will not occur on the Jenkins server. I mean, what is special
> about the Jenkins server that makes it immune to these networking issues?
>
> Thanks,
> Om
>
> On Wed, Feb 6, 2019 at 11:48 AM Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
>> Again, I don't know anything about Docker, but before we spend a lot of
>> time on Docker, I also want to point out that the process to create a
>> release cannot really be thought of as "one application". It will be a
>> series of "steps" to run. How many steps depends on whether we think we
>> can isolate enough stuff via Docker to be able to run Docker on the RM's
>> computer instead of some shared computer. On a shared computer there will
>> be dozens of steps because the RM will need to enter passwords to commit
>> stuff. On a local computer I guess the RM can supply passwords but I think
>> there will be stopping points where the Maven artifacts are deployed and
>> the staging repo is closed, and another stopping point for the vote. It
>> seems like Docker works by downloading dependencies. Given that the
>> problem the RMs had last time involved downloads and uploads, why do we
>> think Docker will really solve this for creating releases on local machines?
>>
>> The reason to do this on a shared machine is so that new RMs don't have
>> to do as much setup. But then I wonder about the efficiency of kicking off
>> that many Docker images. Jenkins can manage that already. Does Docker
>> have some sort of similar Dashboard or would we use Jenkins to kick off
>> Docker steps? I can't quite picture what is the outermost
>> control/dashboard.
>>
>> -Alex
>>
>> On 2/6/19, 11:03 AM, "Harbs" <ha...@gmail.com> wrote:
>>
>> A quick search turns up this:
>>
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955237368&sdata=SN87cX9SZv9ZvykqF13LyVLpQpzNYOPjJKXZoJiJ0U0%3D&reserved=0
>> <
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955237368&sdata=SN87cX9SZv9ZvykqF13LyVLpQpzNYOPjJKXZoJiJ0U0%3D&reserved=0
>> >
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955237368&sdata=7fIOx6HMg4gWvlvqkB1K3F3iIFsEoInsqDQ%2BZTaL7h0%3D&reserved=0
>> <
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955247386&sdata=z0o2EpQr0OLl8WRIgWFsd4f1l9%2B6d3L5K5wXaH0NWvg%3D&reserved=0
>> >
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955247386&sdata=%2Fepy%2Bu37DffUaV%2BduhvEFmKkyY784R%2FTRlC9ra83TqA%3D&reserved=0
>> <
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955247386&sdata=%2Fepy%2Bu37DffUaV%2BduhvEFmKkyY784R%2FTRlC9ra83TqA%3D&reserved=0
>> >
>>
>> > On Feb 6, 2019, at 8:59 PM, Alex Harui <ah...@adobe.com.INVALID>
>> wrote:
>> >
>> > Thanks for volunteering to try it Om. IMO, even more important
>> than Firefox+Flash is SomeBrowser+Selenium. We may also need to run Adobe
>> AIR's adb. We could probably turn off the Flash tests or replace Flash
>> with AIR.
>> >
>> > Thanks,
>> > -Alex
>> >
>> > On 2/6/19, 10:54 AM, "Carlos Rovira" <ca...@apache.org>
>> wrote:
>> >
>> > Hi Om, that would be great! waiting for your experience with a
>> that! :)
>> >
>> > El mié., 6 feb. 2019 a las 19:31, OmPrakash Muppirala (<
>> bigosmallm@gmail.com>)
>> > escribió:
>> >
>> >> Yes, I agree with Alex about not being able to run UI out of docker
>> >> containers. I never thought of the checkintests when I made the
>> >> suggestion.
>> >>
>> >> The firefox-flash image that Yishay pointed out looks promising.
>> I will
>> >> poke around with it and see if that works for us.
>> >>
>> >> Thanks,
>> >> Om
>> >>
>> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <
>> yishayjobs@hotmail.com>
>> >> wrote:
>> >>
>> >>> I’ll let Om or someone else with docker experience tell us if
>> this [1] is
>> >>> relevant.
>> >>>
>> >>>
>> >>>
>> >>> [1]
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955247386&sdata=HgJykzQLEFIxDxlFieTg4%2BbR4G0YpyIOhmBUf5Qoug4%3D&reserved=0
>> >>>
>> >>>
>> >>>
>> >>> ________________________________
>> >>> From: Alex Harui <ah...@adobe.com.INVALID>
>> >>> Sent: Wednesday, February 6, 2019 10:05:54 AM
>> >>> To: dev@royale.apache.org
>> >>> Subject: Re: 0.9.6 Release
>> >>>
>> >>> I don't anything about docker, but in 15 minutes of reading I ran
>> into
>> >>> this:
>> >>>
>> >>>
>> >>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955247386&sdata=tzj8jMAhSSEcqgAIRziLcgqi2ofu6gW1pyrG1Jj0ekI%3D&reserved=0
>> >>>
>> >>> Which says: Docker can't " Run applications with graphical
>> interfaces".
>> >>> If you want Royale to use Docker for releases, show that it can
>> run
>> >>> checkintests with Flash and the Browser. Then I will look into
>> it more.
>> >>>
>> >>> The highest level goal is to make it as easy as possible for
>> someone to
>> >>> volunteer to be an RM. Any requirement of "install this (Docker,
>> etc) on
>> >>> your computer" is, IMO, another barrier to entry. Yeah, RMs will
>> have to
>> >>> have Maven installed and maybe Ant, but you should already have
>> those
>> >>> installed to be a committer/PMC member.
>> >>>
>> >>> That said, a good takeaway from the Docker idea is to try to find
>> a way
>> >> to
>> >>> make an "Image" of whatever we end up with on whatever server we
>> end up
>> >>> using so if the image can be copied and used on other servers.
>> I'm not
>> >>> exactly sure how to do that with Azure, which hosts my CI
>> server. I will
>> >>> spend a few more minutes researching that.
>> >>>
>> >>> I could not quickly find any way to get a free VM on Azure or AWS
>> that
>> >>> isn't a free-trial-start-paying-after-a-year. So, unless someone
>> comes
>> >> up
>> >>> with a free server we can use "forever", I'm going to just start
>> with my
>> >>> Azure VM.
>> >>>
>> >>> -Alex
>> >>>
>> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org>
>> wrote:
>> >>>
>> >>> Hi.
>> >>>
>> >>> the plan sounds very good to me. Just my 2 thoughts on this:
>> >>>
>> >>> 1.- As I was reading I was thinking as well on something like
>> Docker
>> >>> and
>> >>> see Om as well thinking on the same. Maybe is the way to this
>> with
>> >> the
>> >>> actual technology. Seems VMs are stepping out a bit this days
>> in
>> >> favor
>> >>> of
>> >>> things like Docker. Maybe the same did Git over Svn, and today
>> Svn is
>> >>> an
>> >>> old remembrance. I must say that I have no experience with
>> Docker, so
>> >>> doing
>> >>> that will require acquire that knowledge, but seems it could
>> be worth
>> >>> it.
>> >>>
>> >>> 2.- Maybe is not possible, but I want to propose to do this
>> work I a
>> >>> separate branch, so it could be in parallel to other
>> developments. I
>> >>> think
>> >>> work over develop is practical if there's something tiny that
>> could
>> >> be
>> >>> done
>> >>> in a commit. But as we need more than one, or is a long
>> process (like
>> >>> this), chances are to make develop branch unstable and even
>> for some
>> >>> days.
>> >>> I think we should try to avoid that scenario, and branches are
>> the
>> >> best
>> >>> way. If we do this way, we'll benefit of more reliable develop
>> >> branch.
>> >>>
>> >>> Thanks and good to know of this plan :)
>> >>>
>> >>> Carlos
>> >>>
>> >>>
>> >>> El mar., 5 feb. 2019 a las 23:19, Harbs (<
>> harbs.lists@gmail.com>)
>> >>> escribió:
>> >>>
>> >>>> I’ve never used Docker myself, but that might be a good plan.
>> >>>>
>> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
>> >>> bigosmallm@gmail.com>
>> >>>> wrote:
>> >>>>>
>> >>>>> I was wondering if we can use docker images to setup and seal
>> the
>> >>> RM
>> >>>>> environment. Then other RMs simply need to run the image
>> locally
>> >>> and run
>> >>>>> the release scripts. Might be easier. If folks like this plan,
>> >> I
>> >>> can
>> >>>> try
>> >>>>> to put something together.
>> >>>>>
>> >>>>> Thanks,
>> >>>>> Om
>> >>>>>
>> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com>
>> >>> wrote:
>> >>>>>
>> >>>>>> In a recent discussion, it looks like other projects have
>> gotten
>> >>>> resources
>> >>>>>> from AWS.
>> >>>>>>
>> >>>>>> Whatever service we use, could setup a “shared” Royale account
>> >>> that all
>> >>>>>> PMC members could have access to.
>> >>>>>>
>> >>>>>> I don’t know if there’s some way we could leverage Gitlab’s
>> >>> integration
>> >>>>>> pipelines
>> >>>
>> >>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955247386&sdata=5YJ1c6hQeJc%2BY6r%2ByCeUsneC0OKg8PS%2FVctphWAR%2Bb0%3D&reserved=0
>> >>> <
>> >>>>>>
>> >>>
>> >>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955247386&sdata=5YJ1c6hQeJc%2BY6r%2ByCeUsneC0OKg8PS%2FVctphWAR%2Bb0%3D&reserved=0
>> >>>>
>> >>>>>>
>> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
>> >> <aharui@adobe.com.INVALID
>> >>>>
>> >>>>>> wrote:
>> >>>>>>>
>> >>>>>>> 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" <
>> >> piotrzarzycki21@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.lists@gmail.com
>> >>> wrote:
>> >>>>>>>
>> >>>>>>>> A big +1 from me!
>> >>>>>>>>
>> >>>>>>>> Looking forward!
>> >>>>>>>>
>> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
>> >>> <ah...@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
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>
>> >>>>
>> >>>
>> >>> --
>> >>> Carlos Rovira
>> >>>
>> >>>
>> >>
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955247386&sdata=157i5wc2OahsQeR4IKy8Odz3WslPU5MR79HJtBy1cdo%3D&reserved=0
>> >>>
>> >>>
>> >>>
>> >>
>> >
>> >
>> > --
>> > Carlos Rovira
>> >
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ce58d923805b6466d511a08d68fdbaa66%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854570955247386&sdata=157i5wc2OahsQeR4IKy8Odz3WslPU5MR79HJtBy1cdo%3D&reserved=0
>> >
>> >
>>
>>
>>
>>
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Om,
Well, that's what I used for the last release. I'm sure there is probably some inaccuracy in it.
That said, I'm abandoning that document and taking a new angle because that document presumed that the release manager was trying to create a release on his/her computer. I've given up on that and working on making releases from a shared computer for the reasons I've stated upthread. I hope to make some progress on that this week.
The key difference is that the new angle does not presume that you have Git SSH and PGP signatures all set up on some computer. I have not looked into how Docker would handle that. You certainly wouldn't want the Docker image to contain your SSH or PGP keys/creds. And if the Docker image doesn't, then that is another stumbling block for future RMs.
The other key difference is that the old script presumed you could create the 3 release in 3 huge "easy" steps. We've seen that is only true for me. So the new angle creates many discrete steps managed by Jenkins.
So, it is up to you to decide what you want to "Docker-ize". You can try to Docker-ize the current 3 big steps, so RMs can try to run it on their systems, but I'd bet they will just faiI due to network issues. I would be interested in using Docker to make each of these many discrete steps portable to another server. I'm not going to involve Docker at this point. My main goal is just to see if I can create a workflow of many discrete steps that isn't horribly painful. Once we see what these steps turn out to be, then we can worry about server portability of those steps.
Either way, we want to know about running Browser+Selenium for sure. And maybe FlashPlayerDebugger or AIR. I would want to know, for example, how you debug a failing checkintest in a Docker container.
Thanks,
-Alex
On 2/10/19, 5:18 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
Alex,
Just to be clear, I am following the steps from here to try and setup a
docker container.
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358460836&sdata=oAewapXVBbNYLxoy2FTVm5Za%2BbBULGazJS4%2BYXeajP8%3D&reserved=0
Is this doc up to date?
Thanks,
Om
On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <bi...@gmail.com>
wrote:
> One approach is to have each step in the process spin up a docker image.
> And use docker-compose to run each step. All the images can be made to
> share a common volume where all the artifacts are stored across steps.
>
> You are right about the networking issue though. Any network related
> failure that occurs on the host machine will most likely occur in the
> docker container. Although, I am not clear how we can guarantee that the
> same issues will not occur on the Jenkins server. I mean, what is special
> about the Jenkins server that makes it immune to these networking issues?
>
> Thanks,
> Om
>
> On Wed, Feb 6, 2019 at 11:48 AM Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
>> Again, I don't know anything about Docker, but before we spend a lot of
>> time on Docker, I also want to point out that the process to create a
>> release cannot really be thought of as "one application". It will be a
>> series of "steps" to run. How many steps depends on whether we think we
>> can isolate enough stuff via Docker to be able to run Docker on the RM's
>> computer instead of some shared computer. On a shared computer there will
>> be dozens of steps because the RM will need to enter passwords to commit
>> stuff. On a local computer I guess the RM can supply passwords but I think
>> there will be stopping points where the Maven artifacts are deployed and
>> the staging repo is closed, and another stopping point for the vote. It
>> seems like Docker works by downloading dependencies. Given that the
>> problem the RMs had last time involved downloads and uploads, why do we
>> think Docker will really solve this for creating releases on local machines?
>>
>> The reason to do this on a shared machine is so that new RMs don't have
>> to do as much setup. But then I wonder about the efficiency of kicking off
>> that many Docker images. Jenkins can manage that already. Does Docker
>> have some sort of similar Dashboard or would we use Jenkins to kick off
>> Docker steps? I can't quite picture what is the outermost
>> control/dashboard.
>>
>> -Alex
>>
>> On 2/6/19, 11:03 AM, "Harbs" <ha...@gmail.com> wrote:
>>
>> A quick search turns up this:
>>
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358460836&sdata=bQYy5hTabKWf%2F7ge%2BmwxojZnsQwo1RyVD1r4V2yYZas%3D&reserved=0
>> <
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358470845&sdata=HwU%2FgPw7U3QwHjy1eK%2Fio%2B%2F9HMdFuMNsBFd%2B958q8Bc%3D&reserved=0
>> >
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358470845&sdata=%2FVJ9oD6KaQRHZlFRXJApo7ti9cjzzBYyJEtzgJfnm6c%3D&reserved=0
>> <
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358470845&sdata=%2FVJ9oD6KaQRHZlFRXJApo7ti9cjzzBYyJEtzgJfnm6c%3D&reserved=0
>> >
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358470845&sdata=7oj3cu8KnB8wRjI075LnShfLCsTyYHpnOnTQtKMT704%3D&reserved=0
>> <
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358470845&sdata=7oj3cu8KnB8wRjI075LnShfLCsTyYHpnOnTQtKMT704%3D&reserved=0
>> >
>>
>> > On Feb 6, 2019, at 8:59 PM, Alex Harui <ah...@adobe.com.INVALID>
>> wrote:
>> >
>> > Thanks for volunteering to try it Om. IMO, even more important
>> than Firefox+Flash is SomeBrowser+Selenium. We may also need to run Adobe
>> AIR's adb. We could probably turn off the Flash tests or replace Flash
>> with AIR.
>> >
>> > Thanks,
>> > -Alex
>> >
>> > On 2/6/19, 10:54 AM, "Carlos Rovira" <ca...@apache.org>
>> wrote:
>> >
>> > Hi Om, that would be great! waiting for your experience with a
>> that! :)
>> >
>> > El mié., 6 feb. 2019 a las 19:31, OmPrakash Muppirala (<
>> bigosmallm@gmail.com>)
>> > escribió:
>> >
>> >> Yes, I agree with Alex about not being able to run UI out of docker
>> >> containers. I never thought of the checkintests when I made the
>> >> suggestion.
>> >>
>> >> The firefox-flash image that Yishay pointed out looks promising.
>> I will
>> >> poke around with it and see if that works for us.
>> >>
>> >> Thanks,
>> >> Om
>> >>
>> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <
>> yishayjobs@hotmail.com>
>> >> wrote:
>> >>
>> >>> I’ll let Om or someone else with docker experience tell us if
>> this [1] is
>> >>> relevant.
>> >>>
>> >>>
>> >>>
>> >>> [1]
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358470845&sdata=4gq%2BDCfHpyoSVIVLQdCher0PFZ5NGWn06l%2BxLDTEbXk%3D&reserved=0
>> >>>
>> >>>
>> >>>
>> >>> ________________________________
>> >>> From: Alex Harui <ah...@adobe.com.INVALID>
>> >>> Sent: Wednesday, February 6, 2019 10:05:54 AM
>> >>> To: dev@royale.apache.org
>> >>> Subject: Re: 0.9.6 Release
>> >>>
>> >>> I don't anything about docker, but in 15 minutes of reading I ran
>> into
>> >>> this:
>> >>>
>> >>>
>> >>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358470845&sdata=JozuLRcwxNr65SWVxNk14hZWPiG5IQM06IsC3Ch5OSE%3D&reserved=0
>> >>>
>> >>> Which says: Docker can't " Run applications with graphical
>> interfaces".
>> >>> If you want Royale to use Docker for releases, show that it can
>> run
>> >>> checkintests with Flash and the Browser. Then I will look into
>> it more.
>> >>>
>> >>> The highest level goal is to make it as easy as possible for
>> someone to
>> >>> volunteer to be an RM. Any requirement of "install this (Docker,
>> etc) on
>> >>> your computer" is, IMO, another barrier to entry. Yeah, RMs will
>> have to
>> >>> have Maven installed and maybe Ant, but you should already have
>> those
>> >>> installed to be a committer/PMC member.
>> >>>
>> >>> That said, a good takeaway from the Docker idea is to try to find
>> a way
>> >> to
>> >>> make an "Image" of whatever we end up with on whatever server we
>> end up
>> >>> using so if the image can be copied and used on other servers.
>> I'm not
>> >>> exactly sure how to do that with Azure, which hosts my CI
>> server. I will
>> >>> spend a few more minutes researching that.
>> >>>
>> >>> I could not quickly find any way to get a free VM on Azure or AWS
>> that
>> >>> isn't a free-trial-start-paying-after-a-year. So, unless someone
>> comes
>> >> up
>> >>> with a free server we can use "forever", I'm going to just start
>> with my
>> >>> Azure VM.
>> >>>
>> >>> -Alex
>> >>>
>> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org>
>> wrote:
>> >>>
>> >>> Hi.
>> >>>
>> >>> the plan sounds very good to me. Just my 2 thoughts on this:
>> >>>
>> >>> 1.- As I was reading I was thinking as well on something like
>> Docker
>> >>> and
>> >>> see Om as well thinking on the same. Maybe is the way to this
>> with
>> >> the
>> >>> actual technology. Seems VMs are stepping out a bit this days
>> in
>> >> favor
>> >>> of
>> >>> things like Docker. Maybe the same did Git over Svn, and today
>> Svn is
>> >>> an
>> >>> old remembrance. I must say that I have no experience with
>> Docker, so
>> >>> doing
>> >>> that will require acquire that knowledge, but seems it could
>> be worth
>> >>> it.
>> >>>
>> >>> 2.- Maybe is not possible, but I want to propose to do this
>> work I a
>> >>> separate branch, so it could be in parallel to other
>> developments. I
>> >>> think
>> >>> work over develop is practical if there's something tiny that
>> could
>> >> be
>> >>> done
>> >>> in a commit. But as we need more than one, or is a long
>> process (like
>> >>> this), chances are to make develop branch unstable and even
>> for some
>> >>> days.
>> >>> I think we should try to avoid that scenario, and branches are
>> the
>> >> best
>> >>> way. If we do this way, we'll benefit of more reliable develop
>> >> branch.
>> >>>
>> >>> Thanks and good to know of this plan :)
>> >>>
>> >>> Carlos
>> >>>
>> >>>
>> >>> El mar., 5 feb. 2019 a las 23:19, Harbs (<
>> harbs.lists@gmail.com>)
>> >>> escribió:
>> >>>
>> >>>> I’ve never used Docker myself, but that might be a good plan.
>> >>>>
>> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
>> >>> bigosmallm@gmail.com>
>> >>>> wrote:
>> >>>>>
>> >>>>> I was wondering if we can use docker images to setup and seal
>> the
>> >>> RM
>> >>>>> environment. Then other RMs simply need to run the image
>> locally
>> >>> and run
>> >>>>> the release scripts. Might be easier. If folks like this plan,
>> >> I
>> >>> can
>> >>>> try
>> >>>>> to put something together.
>> >>>>>
>> >>>>> Thanks,
>> >>>>> Om
>> >>>>>
>> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com>
>> >>> wrote:
>> >>>>>
>> >>>>>> In a recent discussion, it looks like other projects have
>> gotten
>> >>>> resources
>> >>>>>> from AWS.
>> >>>>>>
>> >>>>>> Whatever service we use, could setup a “shared” Royale account
>> >>> that all
>> >>>>>> PMC members could have access to.
>> >>>>>>
>> >>>>>> I don’t know if there’s some way we could leverage Gitlab’s
>> >>> integration
>> >>>>>> pipelines
>> >>>
>> >>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358470845&sdata=AihEq9KjfpCnjHd7L8w%2BGuIqS0%2Bpsvm54WXQfXGCOlE%3D&reserved=0
>> >>> <
>> >>>>>>
>> >>>
>> >>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358470845&sdata=AihEq9KjfpCnjHd7L8w%2BGuIqS0%2Bpsvm54WXQfXGCOlE%3D&reserved=0
>> >>>>
>> >>>>>>
>> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
>> >> <aharui@adobe.com.INVALID
>> >>>>
>> >>>>>> wrote:
>> >>>>>>>
>> >>>>>>> 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" <
>> >> piotrzarzycki21@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.lists@gmail.com
>> >>> wrote:
>> >>>>>>>
>> >>>>>>>> A big +1 from me!
>> >>>>>>>>
>> >>>>>>>> Looking forward!
>> >>>>>>>>
>> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
>> >>> <ah...@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
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>
>> >>>>
>> >>>
>> >>> --
>> >>> Carlos Rovira
>> >>>
>> >>>
>> >>
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358480850&sdata=2rGFcgf35WvEQlAF4Gqrqlp%2FKcMK9EezdWxRzjQQDAU%3D&reserved=0
>> >>>
>> >>>
>> >>>
>> >>
>> >
>> >
>> > --
>> > Carlos Rovira
>> >
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C792607ae6ff14e1890bf08d68fbee33a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636854447358480850&sdata=2rGFcgf35WvEQlAF4Gqrqlp%2FKcMK9EezdWxRzjQQDAU%3D&reserved=0
>> >
>> >
>>
>>
>>
>>
Re: 0.9.6 Release
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Alex,
Just to be clear, I am following the steps from here to try and setup a
docker container.
https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
Is this doc up to date?
Thanks,
Om
On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <bi...@gmail.com>
wrote:
> One approach is to have each step in the process spin up a docker image.
> And use docker-compose to run each step. All the images can be made to
> share a common volume where all the artifacts are stored across steps.
>
> You are right about the networking issue though. Any network related
> failure that occurs on the host machine will most likely occur in the
> docker container. Although, I am not clear how we can guarantee that the
> same issues will not occur on the Jenkins server. I mean, what is special
> about the Jenkins server that makes it immune to these networking issues?
>
> Thanks,
> Om
>
> On Wed, Feb 6, 2019 at 11:48 AM Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
>> Again, I don't know anything about Docker, but before we spend a lot of
>> time on Docker, I also want to point out that the process to create a
>> release cannot really be thought of as "one application". It will be a
>> series of "steps" to run. How many steps depends on whether we think we
>> can isolate enough stuff via Docker to be able to run Docker on the RM's
>> computer instead of some shared computer. On a shared computer there will
>> be dozens of steps because the RM will need to enter passwords to commit
>> stuff. On a local computer I guess the RM can supply passwords but I think
>> there will be stopping points where the Maven artifacts are deployed and
>> the staging repo is closed, and another stopping point for the vote. It
>> seems like Docker works by downloading dependencies. Given that the
>> problem the RMs had last time involved downloads and uploads, why do we
>> think Docker will really solve this for creating releases on local machines?
>>
>> The reason to do this on a shared machine is so that new RMs don't have
>> to do as much setup. But then I wonder about the efficiency of kicking off
>> that many Docker images. Jenkins can manage that already. Does Docker
>> have some sort of similar Dashboard or would we use Jenkins to kick off
>> Docker steps? I can't quite picture what is the outermost
>> control/dashboard.
>>
>> -Alex
>>
>> On 2/6/19, 11:03 AM, "Harbs" <ha...@gmail.com> wrote:
>>
>> A quick search turns up this:
>>
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=5wwLQFM5nPZtALgsrzdXKMxbBxyenWFhU9EBUojLB5M%3D&reserved=0
>> <
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=5wwLQFM5nPZtALgsrzdXKMxbBxyenWFhU9EBUojLB5M%3D&reserved=0
>> >
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=2iGtMmdkiH57E2U6SZZ7t7t%2BoyetJ69pMYVmb%2BzO8og%3D&reserved=0
>> <
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=2iGtMmdkiH57E2U6SZZ7t7t%2BoyetJ69pMYVmb%2BzO8og%3D&reserved=0
>> >
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=XwBOh%2FrpNch5DRWwFCOnYmkJ9EGFumxBuYR9EF7EfTU%3D&reserved=0
>> <
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=XwBOh%2FrpNch5DRWwFCOnYmkJ9EGFumxBuYR9EF7EfTU%3D&reserved=0
>> >
>>
>> > On Feb 6, 2019, at 8:59 PM, Alex Harui <ah...@adobe.com.INVALID>
>> wrote:
>> >
>> > Thanks for volunteering to try it Om. IMO, even more important
>> than Firefox+Flash is SomeBrowser+Selenium. We may also need to run Adobe
>> AIR's adb. We could probably turn off the Flash tests or replace Flash
>> with AIR.
>> >
>> > Thanks,
>> > -Alex
>> >
>> > On 2/6/19, 10:54 AM, "Carlos Rovira" <ca...@apache.org>
>> wrote:
>> >
>> > Hi Om, that would be great! waiting for your experience with a
>> that! :)
>> >
>> > El mié., 6 feb. 2019 a las 19:31, OmPrakash Muppirala (<
>> bigosmallm@gmail.com>)
>> > escribió:
>> >
>> >> Yes, I agree with Alex about not being able to run UI out of docker
>> >> containers. I never thought of the checkintests when I made the
>> >> suggestion.
>> >>
>> >> The firefox-flash image that Yishay pointed out looks promising.
>> I will
>> >> poke around with it and see if that works for us.
>> >>
>> >> Thanks,
>> >> Om
>> >>
>> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <
>> yishayjobs@hotmail.com>
>> >> wrote:
>> >>
>> >>> I’ll let Om or someone else with docker experience tell us if
>> this [1] is
>> >>> relevant.
>> >>>
>> >>>
>> >>>
>> >>> [1]
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=URxwcqjZjslBTKS2eUxxW6F9GtxrWpvJIEISv9HIEj0%3D&reserved=0
>> >>>
>> >>>
>> >>>
>> >>> ________________________________
>> >>> From: Alex Harui <ah...@adobe.com.INVALID>
>> >>> Sent: Wednesday, February 6, 2019 10:05:54 AM
>> >>> To: dev@royale.apache.org
>> >>> Subject: Re: 0.9.6 Release
>> >>>
>> >>> I don't anything about docker, but in 15 minutes of reading I ran
>> into
>> >>> this:
>> >>>
>> >>>
>> >>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=6UfyKYUY4wJpa%2B9mxm2B4WLW2sFrGFtUrS6YTLWWa7Q%3D&reserved=0
>> >>>
>> >>> Which says: Docker can't " Run applications with graphical
>> interfaces".
>> >>> If you want Royale to use Docker for releases, show that it can
>> run
>> >>> checkintests with Flash and the Browser. Then I will look into
>> it more.
>> >>>
>> >>> The highest level goal is to make it as easy as possible for
>> someone to
>> >>> volunteer to be an RM. Any requirement of "install this (Docker,
>> etc) on
>> >>> your computer" is, IMO, another barrier to entry. Yeah, RMs will
>> have to
>> >>> have Maven installed and maybe Ant, but you should already have
>> those
>> >>> installed to be a committer/PMC member.
>> >>>
>> >>> That said, a good takeaway from the Docker idea is to try to find
>> a way
>> >> to
>> >>> make an "Image" of whatever we end up with on whatever server we
>> end up
>> >>> using so if the image can be copied and used on other servers.
>> I'm not
>> >>> exactly sure how to do that with Azure, which hosts my CI
>> server. I will
>> >>> spend a few more minutes researching that.
>> >>>
>> >>> I could not quickly find any way to get a free VM on Azure or AWS
>> that
>> >>> isn't a free-trial-start-paying-after-a-year. So, unless someone
>> comes
>> >> up
>> >>> with a free server we can use "forever", I'm going to just start
>> with my
>> >>> Azure VM.
>> >>>
>> >>> -Alex
>> >>>
>> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org>
>> wrote:
>> >>>
>> >>> Hi.
>> >>>
>> >>> the plan sounds very good to me. Just my 2 thoughts on this:
>> >>>
>> >>> 1.- As I was reading I was thinking as well on something like
>> Docker
>> >>> and
>> >>> see Om as well thinking on the same. Maybe is the way to this
>> with
>> >> the
>> >>> actual technology. Seems VMs are stepping out a bit this days
>> in
>> >> favor
>> >>> of
>> >>> things like Docker. Maybe the same did Git over Svn, and today
>> Svn is
>> >>> an
>> >>> old remembrance. I must say that I have no experience with
>> Docker, so
>> >>> doing
>> >>> that will require acquire that knowledge, but seems it could
>> be worth
>> >>> it.
>> >>>
>> >>> 2.- Maybe is not possible, but I want to propose to do this
>> work I a
>> >>> separate branch, so it could be in parallel to other
>> developments. I
>> >>> think
>> >>> work over develop is practical if there's something tiny that
>> could
>> >> be
>> >>> done
>> >>> in a commit. But as we need more than one, or is a long
>> process (like
>> >>> this), chances are to make develop branch unstable and even
>> for some
>> >>> days.
>> >>> I think we should try to avoid that scenario, and branches are
>> the
>> >> best
>> >>> way. If we do this way, we'll benefit of more reliable develop
>> >> branch.
>> >>>
>> >>> Thanks and good to know of this plan :)
>> >>>
>> >>> Carlos
>> >>>
>> >>>
>> >>> El mar., 5 feb. 2019 a las 23:19, Harbs (<
>> harbs.lists@gmail.com>)
>> >>> escribió:
>> >>>
>> >>>> I’ve never used Docker myself, but that might be a good plan.
>> >>>>
>> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
>> >>> bigosmallm@gmail.com>
>> >>>> wrote:
>> >>>>>
>> >>>>> I was wondering if we can use docker images to setup and seal
>> the
>> >>> RM
>> >>>>> environment. Then other RMs simply need to run the image
>> locally
>> >>> and run
>> >>>>> the release scripts. Might be easier. If folks like this plan,
>> >> I
>> >>> can
>> >>>> try
>> >>>>> to put something together.
>> >>>>>
>> >>>>> Thanks,
>> >>>>> Om
>> >>>>>
>> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com>
>> >>> wrote:
>> >>>>>
>> >>>>>> In a recent discussion, it looks like other projects have
>> gotten
>> >>>> resources
>> >>>>>> from AWS.
>> >>>>>>
>> >>>>>> Whatever service we use, could setup a “shared” Royale account
>> >>> that all
>> >>>>>> PMC members could have access to.
>> >>>>>>
>> >>>>>> I don’t know if there’s some way we could leverage Gitlab’s
>> >>> integration
>> >>>>>> pipelines
>> >>>
>> >>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=j%2BruVgViQyGs8eeG0w42zC%2FesywKZZtcHK2yNrDAx2I%3D&reserved=0
>> >>> <
>> >>>>>>
>> >>>
>> >>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=j%2BruVgViQyGs8eeG0w42zC%2FesywKZZtcHK2yNrDAx2I%3D&reserved=0
>> >>>>
>> >>>>>>
>> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
>> >> <aharui@adobe.com.INVALID
>> >>>>
>> >>>>>> wrote:
>> >>>>>>>
>> >>>>>>> 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" <
>> >> piotrzarzycki21@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.lists@gmail.com
>> >>> wrote:
>> >>>>>>>
>> >>>>>>>> A big +1 from me!
>> >>>>>>>>
>> >>>>>>>> Looking forward!
>> >>>>>>>>
>> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
>> >>> <ah...@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
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>
>> >>>>
>> >>>
>> >>> --
>> >>> Carlos Rovira
>> >>>
>> >>>
>> >>
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=1mT1tcyvA2FhL6H00OpkLIvtWO4QmdmZeGDegzv6sMI%3D&reserved=0
>> >>>
>> >>>
>> >>>
>> >>
>> >
>> >
>> > --
>> > Carlos Rovira
>> >
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018902709&sdata=HsMakDZC74F3Qx9e3AYL5h6Gfz5SkO9866mdyXyiLBg%3D&reserved=0
>> >
>> >
>>
>>
>>
>>
Re: 0.9.6 Release
Posted by OmPrakash Muppirala <bi...@gmail.com>.
One approach is to have each step in the process spin up a docker image.
And use docker-compose to run each step. All the images can be made to
share a common volume where all the artifacts are stored across steps.
You are right about the networking issue though. Any network related
failure that occurs on the host machine will most likely occur in the
docker container. Although, I am not clear how we can guarantee that the
same issues will not occur on the Jenkins server. I mean, what is special
about the Jenkins server that makes it immune to these networking issues?
Thanks,
Om
On Wed, Feb 6, 2019 at 11:48 AM Alex Harui <ah...@adobe.com.invalid> wrote:
> Again, I don't know anything about Docker, but before we spend a lot of
> time on Docker, I also want to point out that the process to create a
> release cannot really be thought of as "one application". It will be a
> series of "steps" to run. How many steps depends on whether we think we
> can isolate enough stuff via Docker to be able to run Docker on the RM's
> computer instead of some shared computer. On a shared computer there will
> be dozens of steps because the RM will need to enter passwords to commit
> stuff. On a local computer I guess the RM can supply passwords but I think
> there will be stopping points where the Maven artifacts are deployed and
> the staging repo is closed, and another stopping point for the vote. It
> seems like Docker works by downloading dependencies. Given that the
> problem the RMs had last time involved downloads and uploads, why do we
> think Docker will really solve this for creating releases on local machines?
>
> The reason to do this on a shared machine is so that new RMs don't have to
> do as much setup. But then I wonder about the efficiency of kicking off
> that many Docker images. Jenkins can manage that already. Does Docker
> have some sort of similar Dashboard or would we use Jenkins to kick off
> Docker steps? I can't quite picture what is the outermost
> control/dashboard.
>
> -Alex
>
> On 2/6/19, 11:03 AM, "Harbs" <ha...@gmail.com> wrote:
>
> A quick search turns up this:
>
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=5wwLQFM5nPZtALgsrzdXKMxbBxyenWFhU9EBUojLB5M%3D&reserved=0
> <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=5wwLQFM5nPZtALgsrzdXKMxbBxyenWFhU9EBUojLB5M%3D&reserved=0
> >
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=2iGtMmdkiH57E2U6SZZ7t7t%2BoyetJ69pMYVmb%2BzO8og%3D&reserved=0
> <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=2iGtMmdkiH57E2U6SZZ7t7t%2BoyetJ69pMYVmb%2BzO8og%3D&reserved=0
> >
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=XwBOh%2FrpNch5DRWwFCOnYmkJ9EGFumxBuYR9EF7EfTU%3D&reserved=0
> <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=XwBOh%2FrpNch5DRWwFCOnYmkJ9EGFumxBuYR9EF7EfTU%3D&reserved=0
> >
>
> > On Feb 6, 2019, at 8:59 PM, Alex Harui <ah...@adobe.com.INVALID>
> wrote:
> >
> > Thanks for volunteering to try it Om. IMO, even more important than
> Firefox+Flash is SomeBrowser+Selenium. We may also need to run Adobe AIR's
> adb. We could probably turn off the Flash tests or replace Flash with AIR.
> >
> > Thanks,
> > -Alex
> >
> > On 2/6/19, 10:54 AM, "Carlos Rovira" <ca...@apache.org>
> wrote:
> >
> > Hi Om, that would be great! waiting for your experience with a
> that! :)
> >
> > El mié., 6 feb. 2019 a las 19:31, OmPrakash Muppirala (<
> bigosmallm@gmail.com>)
> > escribió:
> >
> >> Yes, I agree with Alex about not being able to run UI out of docker
> >> containers. I never thought of the checkintests when I made the
> >> suggestion.
> >>
> >> The firefox-flash image that Yishay pointed out looks promising. I
> will
> >> poke around with it and see if that works for us.
> >>
> >> Thanks,
> >> Om
> >>
> >> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <
> yishayjobs@hotmail.com>
> >> wrote:
> >>
> >>> I’ll let Om or someone else with docker experience tell us if this
> [1] is
> >>> relevant.
> >>>
> >>>
> >>>
> >>> [1]
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=URxwcqjZjslBTKS2eUxxW6F9GtxrWpvJIEISv9HIEj0%3D&reserved=0
> >>>
> >>>
> >>>
> >>> ________________________________
> >>> From: Alex Harui <ah...@adobe.com.INVALID>
> >>> Sent: Wednesday, February 6, 2019 10:05:54 AM
> >>> To: dev@royale.apache.org
> >>> Subject: Re: 0.9.6 Release
> >>>
> >>> I don't anything about docker, but in 15 minutes of reading I ran
> into
> >>> this:
> >>>
> >>>
> >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=6UfyKYUY4wJpa%2B9mxm2B4WLW2sFrGFtUrS6YTLWWa7Q%3D&reserved=0
> >>>
> >>> Which says: Docker can't " Run applications with graphical
> interfaces".
> >>> If you want Royale to use Docker for releases, show that it can run
> >>> checkintests with Flash and the Browser. Then I will look into it
> more.
> >>>
> >>> The highest level goal is to make it as easy as possible for
> someone to
> >>> volunteer to be an RM. Any requirement of "install this (Docker,
> etc) on
> >>> your computer" is, IMO, another barrier to entry. Yeah, RMs will
> have to
> >>> have Maven installed and maybe Ant, but you should already have
> those
> >>> installed to be a committer/PMC member.
> >>>
> >>> That said, a good takeaway from the Docker idea is to try to find
> a way
> >> to
> >>> make an "Image" of whatever we end up with on whatever server we
> end up
> >>> using so if the image can be copied and used on other servers.
> I'm not
> >>> exactly sure how to do that with Azure, which hosts my CI server.
> I will
> >>> spend a few more minutes researching that.
> >>>
> >>> I could not quickly find any way to get a free VM on Azure or AWS
> that
> >>> isn't a free-trial-start-paying-after-a-year. So, unless someone
> comes
> >> up
> >>> with a free server we can use "forever", I'm going to just start
> with my
> >>> Azure VM.
> >>>
> >>> -Alex
> >>>
> >>> On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org>
> wrote:
> >>>
> >>> Hi.
> >>>
> >>> the plan sounds very good to me. Just my 2 thoughts on this:
> >>>
> >>> 1.- As I was reading I was thinking as well on something like
> Docker
> >>> and
> >>> see Om as well thinking on the same. Maybe is the way to this
> with
> >> the
> >>> actual technology. Seems VMs are stepping out a bit this days in
> >> favor
> >>> of
> >>> things like Docker. Maybe the same did Git over Svn, and today
> Svn is
> >>> an
> >>> old remembrance. I must say that I have no experience with
> Docker, so
> >>> doing
> >>> that will require acquire that knowledge, but seems it could be
> worth
> >>> it.
> >>>
> >>> 2.- Maybe is not possible, but I want to propose to do this
> work I a
> >>> separate branch, so it could be in parallel to other
> developments. I
> >>> think
> >>> work over develop is practical if there's something tiny that
> could
> >> be
> >>> done
> >>> in a commit. But as we need more than one, or is a long process
> (like
> >>> this), chances are to make develop branch unstable and even for
> some
> >>> days.
> >>> I think we should try to avoid that scenario, and branches are
> the
> >> best
> >>> way. If we do this way, we'll benefit of more reliable develop
> >> branch.
> >>>
> >>> Thanks and good to know of this plan :)
> >>>
> >>> Carlos
> >>>
> >>>
> >>> El mar., 5 feb. 2019 a las 23:19, Harbs (<harbs.lists@gmail.com
> >)
> >>> escribió:
> >>>
> >>>> I’ve never used Docker myself, but that might be a good plan.
> >>>>
> >>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
> >>> bigosmallm@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>> I was wondering if we can use docker images to setup and seal the
> >>> RM
> >>>>> environment. Then other RMs simply need to run the image locally
> >>> and run
> >>>>> the release scripts. Might be easier. If folks like this plan,
> >> I
> >>> can
> >>>> try
> >>>>> to put something together.
> >>>>>
> >>>>> Thanks,
> >>>>> Om
> >>>>>
> >>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com>
> >>> wrote:
> >>>>>
> >>>>>> In a recent discussion, it looks like other projects have gotten
> >>>> resources
> >>>>>> from AWS.
> >>>>>>
> >>>>>> Whatever service we use, could setup a “shared” Royale account
> >>> that all
> >>>>>> PMC members could have access to.
> >>>>>>
> >>>>>> I don’t know if there’s some way we could leverage Gitlab’s
> >>> integration
> >>>>>> pipelines
> >>>
> >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=j%2BruVgViQyGs8eeG0w42zC%2FesywKZZtcHK2yNrDAx2I%3D&reserved=0
> >>> <
> >>>>>>
> >>>
> >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=j%2BruVgViQyGs8eeG0w42zC%2FesywKZZtcHK2yNrDAx2I%3D&reserved=0
> >>>>
> >>>>>>
> >>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
> >> <aharui@adobe.com.INVALID
> >>>>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> 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" <
> >> piotrzarzycki21@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.lists@gmail.com
> >>> wrote:
> >>>>>>>
> >>>>>>>> A big +1 from me!
> >>>>>>>>
> >>>>>>>> Looking forward!
> >>>>>>>>
> >>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
> >>> <ah...@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
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>>
> >>>
> >>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=1mT1tcyvA2FhL6H00OpkLIvtWO4QmdmZeGDegzv6sMI%3D&reserved=0
> >>>
> >>>
> >>>
> >>
> >
> >
> > --
> > Carlos Rovira
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018902709&sdata=HsMakDZC74F3Qx9e3AYL5h6Gfz5SkO9866mdyXyiLBg%3D&reserved=0
> >
> >
>
>
>
>
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Again, I don't know anything about Docker, but before we spend a lot of time on Docker, I also want to point out that the process to create a release cannot really be thought of as "one application". It will be a series of "steps" to run. How many steps depends on whether we think we can isolate enough stuff via Docker to be able to run Docker on the RM's computer instead of some shared computer. On a shared computer there will be dozens of steps because the RM will need to enter passwords to commit stuff. On a local computer I guess the RM can supply passwords but I think there will be stopping points where the Maven artifacts are deployed and the staging repo is closed, and another stopping point for the vote. It seems like Docker works by downloading dependencies. Given that the problem the RMs had last time involved downloads and uploads, why do we think Docker will really solve this for creating releases on local machines?
The reason to do this on a shared machine is so that new RMs don't have to do as much setup. But then I wonder about the efficiency of kicking off that many Docker images. Jenkins can manage that already. Does Docker have some sort of similar Dashboard or would we use Jenkins to kick off Docker steps? I can't quite picture what is the outermost control/dashboard.
-Alex
On 2/6/19, 11:03 AM, "Harbs" <ha...@gmail.com> wrote:
A quick search turns up this:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=5wwLQFM5nPZtALgsrzdXKMxbBxyenWFhU9EBUojLB5M%3D&reserved=0 <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testing&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=5wwLQFM5nPZtALgsrzdXKMxbBxyenWFhU9EBUojLB5M%3D&reserved=0>
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=2iGtMmdkiH57E2U6SZZ7t7t%2BoyetJ69pMYVmb%2BzO8og%3D&reserved=0 <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-docker&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=2iGtMmdkiH57E2U6SZZ7t7t%2BoyetJ69pMYVmb%2BzO8og%3D&reserved=0>
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=XwBOh%2FrpNch5DRWwFCOnYmkJ9EGFumxBuYR9EF7EfTU%3D&reserved=0 <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-selenium&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=XwBOh%2FrpNch5DRWwFCOnYmkJ9EGFumxBuYR9EF7EfTU%3D&reserved=0>
> On Feb 6, 2019, at 8:59 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> Thanks for volunteering to try it Om. IMO, even more important than Firefox+Flash is SomeBrowser+Selenium. We may also need to run Adobe AIR's adb. We could probably turn off the Flash tests or replace Flash with AIR.
>
> Thanks,
> -Alex
>
> On 2/6/19, 10:54 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Om, that would be great! waiting for your experience with a that! :)
>
> El mié., 6 feb. 2019 a las 19:31, OmPrakash Muppirala (<bi...@gmail.com>)
> escribió:
>
>> Yes, I agree with Alex about not being able to run UI out of docker
>> containers. I never thought of the checkintests when I made the
>> suggestion.
>>
>> The firefox-flash image that Yishay pointed out looks promising. I will
>> poke around with it and see if that works for us.
>>
>> Thanks,
>> Om
>>
>> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <yi...@hotmail.com>
>> wrote:
>>
>>> I’ll let Om or someone else with docker experience tell us if this [1] is
>>> relevant.
>>>
>>>
>>>
>>> [1] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=URxwcqjZjslBTKS2eUxxW6F9GtxrWpvJIEISv9HIEj0%3D&reserved=0
>>>
>>>
>>>
>>> ________________________________
>>> From: Alex Harui <ah...@adobe.com.INVALID>
>>> Sent: Wednesday, February 6, 2019 10:05:54 AM
>>> To: dev@royale.apache.org
>>> Subject: Re: 0.9.6 Release
>>>
>>> I don't anything about docker, but in 15 minutes of reading I ran into
>>> this:
>>>
>>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=6UfyKYUY4wJpa%2B9mxm2B4WLW2sFrGFtUrS6YTLWWa7Q%3D&reserved=0
>>>
>>> Which says: Docker can't " Run applications with graphical interfaces".
>>> If you want Royale to use Docker for releases, show that it can run
>>> checkintests with Flash and the Browser. Then I will look into it more.
>>>
>>> The highest level goal is to make it as easy as possible for someone to
>>> volunteer to be an RM. Any requirement of "install this (Docker, etc) on
>>> your computer" is, IMO, another barrier to entry. Yeah, RMs will have to
>>> have Maven installed and maybe Ant, but you should already have those
>>> installed to be a committer/PMC member.
>>>
>>> That said, a good takeaway from the Docker idea is to try to find a way
>> to
>>> make an "Image" of whatever we end up with on whatever server we end up
>>> using so if the image can be copied and used on other servers. I'm not
>>> exactly sure how to do that with Azure, which hosts my CI server. I will
>>> spend a few more minutes researching that.
>>>
>>> I could not quickly find any way to get a free VM on Azure or AWS that
>>> isn't a free-trial-start-paying-after-a-year. So, unless someone comes
>> up
>>> with a free server we can use "forever", I'm going to just start with my
>>> Azure VM.
>>>
>>> -Alex
>>>
>>> On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>>>
>>> Hi.
>>>
>>> the plan sounds very good to me. Just my 2 thoughts on this:
>>>
>>> 1.- As I was reading I was thinking as well on something like Docker
>>> and
>>> see Om as well thinking on the same. Maybe is the way to this with
>> the
>>> actual technology. Seems VMs are stepping out a bit this days in
>> favor
>>> of
>>> things like Docker. Maybe the same did Git over Svn, and today Svn is
>>> an
>>> old remembrance. I must say that I have no experience with Docker, so
>>> doing
>>> that will require acquire that knowledge, but seems it could be worth
>>> it.
>>>
>>> 2.- Maybe is not possible, but I want to propose to do this work I a
>>> separate branch, so it could be in parallel to other developments. I
>>> think
>>> work over develop is practical if there's something tiny that could
>> be
>>> done
>>> in a commit. But as we need more than one, or is a long process (like
>>> this), chances are to make develop branch unstable and even for some
>>> days.
>>> I think we should try to avoid that scenario, and branches are the
>> best
>>> way. If we do this way, we'll benefit of more reliable develop
>> branch.
>>>
>>> Thanks and good to know of this plan :)
>>>
>>> Carlos
>>>
>>>
>>> El mar., 5 feb. 2019 a las 23:19, Harbs (<ha...@gmail.com>)
>>> escribió:
>>>
>>>> I’ve never used Docker myself, but that might be a good plan.
>>>>
>>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
>>> bigosmallm@gmail.com>
>>>> wrote:
>>>>>
>>>>> I was wondering if we can use docker images to setup and seal the
>>> RM
>>>>> environment. Then other RMs simply need to run the image locally
>>> and run
>>>>> the release scripts. Might be easier. If folks like this plan,
>> I
>>> can
>>>> try
>>>>> to put something together.
>>>>>
>>>>> Thanks,
>>>>> Om
>>>>>
>>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com>
>>> wrote:
>>>>>
>>>>>> In a recent discussion, it looks like other projects have gotten
>>>> resources
>>>>>> from AWS.
>>>>>>
>>>>>> Whatever service we use, could setup a “shared” Royale account
>>> that all
>>>>>> PMC members could have access to.
>>>>>>
>>>>>> I don’t know if there’s some way we could leverage Gitlab’s
>>> integration
>>>>>> pipelines
>>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=j%2BruVgViQyGs8eeG0w42zC%2FesywKZZtcHK2yNrDAx2I%3D&reserved=0
>>> <
>>>>>>
>>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=j%2BruVgViQyGs8eeG0w42zC%2FesywKZZtcHK2yNrDAx2I%3D&reserved=0
>>>>
>>>>>>
>>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
>> <aharui@adobe.com.INVALID
>>>>
>>>>>> wrote:
>>>>>>>
>>>>>>> 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" <
>> piotrzarzycki21@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.lists@gmail.com
>>> wrote:
>>>>>>>
>>>>>>>> A big +1 from me!
>>>>>>>>
>>>>>>>> Looking forward!
>>>>>>>>
>>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
>>> <ah...@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
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>> --
>>> Carlos Rovira
>>>
>>>
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700&sdata=1mT1tcyvA2FhL6H00OpkLIvtWO4QmdmZeGDegzv6sMI%3D&reserved=0
>>>
>>>
>>>
>>
>
>
> --
> Carlos Rovira
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018902709&sdata=HsMakDZC74F3Qx9e3AYL5h6Gfz5SkO9866mdyXyiLBg%3D&reserved=0
>
>
Re: 0.9.6 Release
Posted by Harbs <ha...@gmail.com>.
A quick search turns up this:
https://codingsans.com/blog/selenium-with-docker-testing <https://codingsans.com/blog/selenium-with-docker-testing>
https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker <https://www.blazemeter.com/blog/how-to-run-selenium-tests-in-docker>
https://github.com/SeleniumHQ/docker-selenium <https://github.com/SeleniumHQ/docker-selenium>
> On Feb 6, 2019, at 8:59 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> Thanks for volunteering to try it Om. IMO, even more important than Firefox+Flash is SomeBrowser+Selenium. We may also need to run Adobe AIR's adb. We could probably turn off the Flash tests or replace Flash with AIR.
>
> Thanks,
> -Alex
>
> On 2/6/19, 10:54 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Om, that would be great! waiting for your experience with a that! :)
>
> El mié., 6 feb. 2019 a las 19:31, OmPrakash Muppirala (<bi...@gmail.com>)
> escribió:
>
>> Yes, I agree with Alex about not being able to run UI out of docker
>> containers. I never thought of the checkintests when I made the
>> suggestion.
>>
>> The firefox-flash image that Yishay pointed out looks promising. I will
>> poke around with it and see if that works for us.
>>
>> Thanks,
>> Om
>>
>> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <yi...@hotmail.com>
>> wrote:
>>
>>> I’ll let Om or someone else with docker experience tell us if this [1] is
>>> relevant.
>>>
>>>
>>>
>>> [1] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C6b6fabe26f1a4300616808d68c647e10%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850760589907404&sdata=6mIWHg4PFkyEG2nUPdjtjnYkkbmK%2BLAFx%2Fev7%2Fxe3Lw%3D&reserved=0
>>>
>>>
>>>
>>> ________________________________
>>> From: Alex Harui <ah...@adobe.com.INVALID>
>>> Sent: Wednesday, February 6, 2019 10:05:54 AM
>>> To: dev@royale.apache.org
>>> Subject: Re: 0.9.6 Release
>>>
>>> I don't anything about docker, but in 15 minutes of reading I ran into
>>> this:
>>>
>>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C6b6fabe26f1a4300616808d68c647e10%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850760589907404&sdata=V9iwab%2FNowIVB7lXCQfj1vAPNObehQZ%2FzRL6Rp%2FKsBA%3D&reserved=0
>>>
>>> Which says: Docker can't " Run applications with graphical interfaces".
>>> If you want Royale to use Docker for releases, show that it can run
>>> checkintests with Flash and the Browser. Then I will look into it more.
>>>
>>> The highest level goal is to make it as easy as possible for someone to
>>> volunteer to be an RM. Any requirement of "install this (Docker, etc) on
>>> your computer" is, IMO, another barrier to entry. Yeah, RMs will have to
>>> have Maven installed and maybe Ant, but you should already have those
>>> installed to be a committer/PMC member.
>>>
>>> That said, a good takeaway from the Docker idea is to try to find a way
>> to
>>> make an "Image" of whatever we end up with on whatever server we end up
>>> using so if the image can be copied and used on other servers. I'm not
>>> exactly sure how to do that with Azure, which hosts my CI server. I will
>>> spend a few more minutes researching that.
>>>
>>> I could not quickly find any way to get a free VM on Azure or AWS that
>>> isn't a free-trial-start-paying-after-a-year. So, unless someone comes
>> up
>>> with a free server we can use "forever", I'm going to just start with my
>>> Azure VM.
>>>
>>> -Alex
>>>
>>> On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>>>
>>> Hi.
>>>
>>> the plan sounds very good to me. Just my 2 thoughts on this:
>>>
>>> 1.- As I was reading I was thinking as well on something like Docker
>>> and
>>> see Om as well thinking on the same. Maybe is the way to this with
>> the
>>> actual technology. Seems VMs are stepping out a bit this days in
>> favor
>>> of
>>> things like Docker. Maybe the same did Git over Svn, and today Svn is
>>> an
>>> old remembrance. I must say that I have no experience with Docker, so
>>> doing
>>> that will require acquire that knowledge, but seems it could be worth
>>> it.
>>>
>>> 2.- Maybe is not possible, but I want to propose to do this work I a
>>> separate branch, so it could be in parallel to other developments. I
>>> think
>>> work over develop is practical if there's something tiny that could
>> be
>>> done
>>> in a commit. But as we need more than one, or is a long process (like
>>> this), chances are to make develop branch unstable and even for some
>>> days.
>>> I think we should try to avoid that scenario, and branches are the
>> best
>>> way. If we do this way, we'll benefit of more reliable develop
>> branch.
>>>
>>> Thanks and good to know of this plan :)
>>>
>>> Carlos
>>>
>>>
>>> El mar., 5 feb. 2019 a las 23:19, Harbs (<ha...@gmail.com>)
>>> escribió:
>>>
>>>> I’ve never used Docker myself, but that might be a good plan.
>>>>
>>>>> On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
>>> bigosmallm@gmail.com>
>>>> wrote:
>>>>>
>>>>> I was wondering if we can use docker images to setup and seal the
>>> RM
>>>>> environment. Then other RMs simply need to run the image locally
>>> and run
>>>>> the release scripts. Might be easier. If folks like this plan,
>> I
>>> can
>>>> try
>>>>> to put something together.
>>>>>
>>>>> Thanks,
>>>>> Om
>>>>>
>>>>> On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com>
>>> wrote:
>>>>>
>>>>>> In a recent discussion, it looks like other projects have gotten
>>>> resources
>>>>>> from AWS.
>>>>>>
>>>>>> Whatever service we use, could setup a “shared” Royale account
>>> that all
>>>>>> PMC members could have access to.
>>>>>>
>>>>>> I don’t know if there’s some way we could leverage Gitlab’s
>>> integration
>>>>>> pipelines
>>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C6b6fabe26f1a4300616808d68c647e10%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850760589907404&sdata=e5rQBGRni7XM3qInhySfB08GDTS9KQErSg9mAxmP%2FVU%3D&reserved=0
>>> <
>>>>>>
>>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C6b6fabe26f1a4300616808d68c647e10%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850760589907404&sdata=e5rQBGRni7XM3qInhySfB08GDTS9KQErSg9mAxmP%2FVU%3D&reserved=0
>>>>
>>>>>>
>>>>>>> On Feb 5, 2019, at 11:33 PM, Alex Harui
>> <aharui@adobe.com.INVALID
>>>>
>>>>>> wrote:
>>>>>>>
>>>>>>> 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" <
>> piotrzarzycki21@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.lists@gmail.com
>>> wrote:
>>>>>>>
>>>>>>>> A big +1 from me!
>>>>>>>>
>>>>>>>> Looking forward!
>>>>>>>>
>>>>>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
>>> <ah...@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
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>> --
>>> Carlos Rovira
>>>
>>>
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C6b6fabe26f1a4300616808d68c647e10%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850760589907404&sdata=fMF6hvJJy73TWPPebOTkVKxXC0mzUhv0Jrb3FEl4n%2Bw%3D&reserved=0
>>>
>>>
>>>
>>
>
>
> --
> Carlos Rovira
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C6b6fabe26f1a4300616808d68c647e10%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850760589907404&sdata=fMF6hvJJy73TWPPebOTkVKxXC0mzUhv0Jrb3FEl4n%2Bw%3D&reserved=0
>
>
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Thanks for volunteering to try it Om. IMO, even more important than Firefox+Flash is SomeBrowser+Selenium. We may also need to run Adobe AIR's adb. We could probably turn off the Flash tests or replace Flash with AIR.
Thanks,
-Alex
On 2/6/19, 10:54 AM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi Om, that would be great! waiting for your experience with a that! :)
El mié., 6 feb. 2019 a las 19:31, OmPrakash Muppirala (<bi...@gmail.com>)
escribió:
> Yes, I agree with Alex about not being able to run UI out of docker
> containers. I never thought of the checkintests when I made the
> suggestion.
>
> The firefox-flash image that Yishay pointed out looks promising. I will
> poke around with it and see if that works for us.
>
> Thanks,
> Om
>
> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <yi...@hotmail.com>
> wrote:
>
> > I’ll let Om or someone else with docker experience tell us if this [1] is
> > relevant.
> >
> >
> >
> > [1] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fbeli%2Ffirefox-flash%2F&data=02%7C01%7Caharui%40adobe.com%7C6b6fabe26f1a4300616808d68c647e10%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850760589907404&sdata=6mIWHg4PFkyEG2nUPdjtjnYkkbmK%2BLAFx%2Fev7%2Fxe3Lw%3D&reserved=0
> >
> >
> >
> > ________________________________
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, February 6, 2019 10:05:54 AM
> > To: dev@royale.apache.org
> > Subject: Re: 0.9.6 Release
> >
> > I don't anything about docker, but in 15 minutes of reading I ran into
> > this:
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.channelfutures.com%2Fopen-source%2Fwhen-not-to-use-docker-understanding-the-limitations-of-containers&data=02%7C01%7Caharui%40adobe.com%7C6b6fabe26f1a4300616808d68c647e10%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850760589907404&sdata=V9iwab%2FNowIVB7lXCQfj1vAPNObehQZ%2FzRL6Rp%2FKsBA%3D&reserved=0
> >
> > Which says: Docker can't " Run applications with graphical interfaces".
> > If you want Royale to use Docker for releases, show that it can run
> > checkintests with Flash and the Browser. Then I will look into it more.
> >
> > The highest level goal is to make it as easy as possible for someone to
> > volunteer to be an RM. Any requirement of "install this (Docker, etc) on
> > your computer" is, IMO, another barrier to entry. Yeah, RMs will have to
> > have Maven installed and maybe Ant, but you should already have those
> > installed to be a committer/PMC member.
> >
> > That said, a good takeaway from the Docker idea is to try to find a way
> to
> > make an "Image" of whatever we end up with on whatever server we end up
> > using so if the image can be copied and used on other servers. I'm not
> > exactly sure how to do that with Azure, which hosts my CI server. I will
> > spend a few more minutes researching that.
> >
> > I could not quickly find any way to get a free VM on Azure or AWS that
> > isn't a free-trial-start-paying-after-a-year. So, unless someone comes
> up
> > with a free server we can use "forever", I'm going to just start with my
> > Azure VM.
> >
> > -Alex
> >
> > On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org> wrote:
> >
> > Hi.
> >
> > the plan sounds very good to me. Just my 2 thoughts on this:
> >
> > 1.- As I was reading I was thinking as well on something like Docker
> > and
> > see Om as well thinking on the same. Maybe is the way to this with
> the
> > actual technology. Seems VMs are stepping out a bit this days in
> favor
> > of
> > things like Docker. Maybe the same did Git over Svn, and today Svn is
> > an
> > old remembrance. I must say that I have no experience with Docker, so
> > doing
> > that will require acquire that knowledge, but seems it could be worth
> > it.
> >
> > 2.- Maybe is not possible, but I want to propose to do this work I a
> > separate branch, so it could be in parallel to other developments. I
> > think
> > work over develop is practical if there's something tiny that could
> be
> > done
> > in a commit. But as we need more than one, or is a long process (like
> > this), chances are to make develop branch unstable and even for some
> > days.
> > I think we should try to avoid that scenario, and branches are the
> best
> > way. If we do this way, we'll benefit of more reliable develop
> branch.
> >
> > Thanks and good to know of this plan :)
> >
> > Carlos
> >
> >
> > El mar., 5 feb. 2019 a las 23:19, Harbs (<ha...@gmail.com>)
> > escribió:
> >
> > > I’ve never used Docker myself, but that might be a good plan.
> > >
> > > > On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
> > bigosmallm@gmail.com>
> > > wrote:
> > > >
> > > > I was wondering if we can use docker images to setup and seal the
> > RM
> > > > environment. Then other RMs simply need to run the image locally
> > and run
> > > > the release scripts. Might be easier. If folks like this plan,
> I
> > can
> > > try
> > > > to put something together.
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com>
> > wrote:
> > > >
> > > >> In a recent discussion, it looks like other projects have gotten
> > > resources
> > > >> from AWS.
> > > >>
> > > >> Whatever service we use, could setup a “shared” Royale account
> > that all
> > > >> PMC members could have access to.
> > > >>
> > > >> I don’t know if there’s some way we could leverage Gitlab’s
> > integration
> > > >> pipelines
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C6b6fabe26f1a4300616808d68c647e10%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850760589907404&sdata=e5rQBGRni7XM3qInhySfB08GDTS9KQErSg9mAxmP%2FVU%3D&reserved=0
> > <
> > > >>
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7C6b6fabe26f1a4300616808d68c647e10%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850760589907404&sdata=e5rQBGRni7XM3qInhySfB08GDTS9KQErSg9mAxmP%2FVU%3D&reserved=0
> > >
> > > >>
> > > >>> On Feb 5, 2019, at 11:33 PM, Alex Harui
> <aharui@adobe.com.INVALID
> > >
> > > >> wrote:
> > > >>>
> > > >>> 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" <
> piotrzarzycki21@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.lists@gmail.com
> > wrote:
> > > >>>
> > > >>>> A big +1 from me!
> > > >>>>
> > > >>>> Looking forward!
> > > >>>>
> > > >>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
> > <ah...@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
> > > >>>>>
> > > >>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C6b6fabe26f1a4300616808d68c647e10%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850760589907404&sdata=fMF6hvJJy73TWPPebOTkVKxXC0mzUhv0Jrb3FEl4n%2Bw%3D&reserved=0
> >
> >
> >
>
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C6b6fabe26f1a4300616808d68c647e10%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850760589907404&sdata=fMF6hvJJy73TWPPebOTkVKxXC0mzUhv0Jrb3FEl4n%2Bw%3D&reserved=0
Re: 0.9.6 Release
Posted by Carlos Rovira <ca...@apache.org>.
Hi Om, that would be great! waiting for your experience with a that! :)
El mié., 6 feb. 2019 a las 19:31, OmPrakash Muppirala (<bi...@gmail.com>)
escribió:
> Yes, I agree with Alex about not being able to run UI out of docker
> containers. I never thought of the checkintests when I made the
> suggestion.
>
> The firefox-flash image that Yishay pointed out looks promising. I will
> poke around with it and see if that works for us.
>
> Thanks,
> Om
>
> On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <yi...@hotmail.com>
> wrote:
>
> > I’ll let Om or someone else with docker experience tell us if this [1] is
> > relevant.
> >
> >
> >
> > [1] https://hub.docker.com/r/beli/firefox-flash/
> >
> >
> >
> > ________________________________
> > From: Alex Harui <ah...@adobe.com.INVALID>
> > Sent: Wednesday, February 6, 2019 10:05:54 AM
> > To: dev@royale.apache.org
> > Subject: Re: 0.9.6 Release
> >
> > I don't anything about docker, but in 15 minutes of reading I ran into
> > this:
> >
> >
> https://www.channelfutures.com/open-source/when-not-to-use-docker-understanding-the-limitations-of-containers
> >
> > Which says: Docker can't " Run applications with graphical interfaces".
> > If you want Royale to use Docker for releases, show that it can run
> > checkintests with Flash and the Browser. Then I will look into it more.
> >
> > The highest level goal is to make it as easy as possible for someone to
> > volunteer to be an RM. Any requirement of "install this (Docker, etc) on
> > your computer" is, IMO, another barrier to entry. Yeah, RMs will have to
> > have Maven installed and maybe Ant, but you should already have those
> > installed to be a committer/PMC member.
> >
> > That said, a good takeaway from the Docker idea is to try to find a way
> to
> > make an "Image" of whatever we end up with on whatever server we end up
> > using so if the image can be copied and used on other servers. I'm not
> > exactly sure how to do that with Azure, which hosts my CI server. I will
> > spend a few more minutes researching that.
> >
> > I could not quickly find any way to get a free VM on Azure or AWS that
> > isn't a free-trial-start-paying-after-a-year. So, unless someone comes
> up
> > with a free server we can use "forever", I'm going to just start with my
> > Azure VM.
> >
> > -Alex
> >
> > On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org> wrote:
> >
> > Hi.
> >
> > the plan sounds very good to me. Just my 2 thoughts on this:
> >
> > 1.- As I was reading I was thinking as well on something like Docker
> > and
> > see Om as well thinking on the same. Maybe is the way to this with
> the
> > actual technology. Seems VMs are stepping out a bit this days in
> favor
> > of
> > things like Docker. Maybe the same did Git over Svn, and today Svn is
> > an
> > old remembrance. I must say that I have no experience with Docker, so
> > doing
> > that will require acquire that knowledge, but seems it could be worth
> > it.
> >
> > 2.- Maybe is not possible, but I want to propose to do this work I a
> > separate branch, so it could be in parallel to other developments. I
> > think
> > work over develop is practical if there's something tiny that could
> be
> > done
> > in a commit. But as we need more than one, or is a long process (like
> > this), chances are to make develop branch unstable and even for some
> > days.
> > I think we should try to avoid that scenario, and branches are the
> best
> > way. If we do this way, we'll benefit of more reliable develop
> branch.
> >
> > Thanks and good to know of this plan :)
> >
> > Carlos
> >
> >
> > El mar., 5 feb. 2019 a las 23:19, Harbs (<ha...@gmail.com>)
> > escribió:
> >
> > > I’ve never used Docker myself, but that might be a good plan.
> > >
> > > > On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
> > bigosmallm@gmail.com>
> > > wrote:
> > > >
> > > > I was wondering if we can use docker images to setup and seal the
> > RM
> > > > environment. Then other RMs simply need to run the image locally
> > and run
> > > > the release scripts. Might be easier. If folks like this plan,
> I
> > can
> > > try
> > > > to put something together.
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com>
> > wrote:
> > > >
> > > >> In a recent discussion, it looks like other projects have gotten
> > > resources
> > > >> from AWS.
> > > >>
> > > >> Whatever service we use, could setup a “shared” Royale account
> > that all
> > > >> PMC members could have access to.
> > > >>
> > > >> I don’t know if there’s some way we could leverage Gitlab’s
> > integration
> > > >> pipelines
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7Cef2b34e531be41983c1208d68c009d75%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850331599744364&sdata=ux3NQZcnILfobRoGhlxI509Z30JI2Tba4O%2FDxWFii9w%3D&reserved=0
> > <
> > > >>
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7Cef2b34e531be41983c1208d68c009d75%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850331599744364&sdata=ux3NQZcnILfobRoGhlxI509Z30JI2Tba4O%2FDxWFii9w%3D&reserved=0
> > >
> > > >>
> > > >>> On Feb 5, 2019, at 11:33 PM, Alex Harui
> <aharui@adobe.com.INVALID
> > >
> > > >> wrote:
> > > >>>
> > > >>> 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" <
> piotrzarzycki21@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.lists@gmail.com
> > wrote:
> > > >>>
> > > >>>> A big +1 from me!
> > > >>>>
> > > >>>> Looking forward!
> > > >>>>
> > > >>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
> > <ah...@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
> > > >>>>>
> > > >>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cef2b34e531be41983c1208d68c009d75%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850331599744364&sdata=%2BBjFv4hgPoVNn5ymJnenJAvPkkTJzZx%2FeXfMtSpogEE%3D&reserved=0
> >
> >
> >
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: 0.9.6 Release
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Yes, I agree with Alex about not being able to run UI out of docker
containers. I never thought of the checkintests when I made the
suggestion.
The firefox-flash image that Yishay pointed out looks promising. I will
poke around with it and see if that works for us.
Thanks,
Om
On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss <yi...@hotmail.com> wrote:
> I’ll let Om or someone else with docker experience tell us if this [1] is
> relevant.
>
>
>
> [1] https://hub.docker.com/r/beli/firefox-flash/
>
>
>
> ________________________________
> From: Alex Harui <ah...@adobe.com.INVALID>
> Sent: Wednesday, February 6, 2019 10:05:54 AM
> To: dev@royale.apache.org
> Subject: Re: 0.9.6 Release
>
> I don't anything about docker, but in 15 minutes of reading I ran into
> this:
>
> https://www.channelfutures.com/open-source/when-not-to-use-docker-understanding-the-limitations-of-containers
>
> Which says: Docker can't " Run applications with graphical interfaces".
> If you want Royale to use Docker for releases, show that it can run
> checkintests with Flash and the Browser. Then I will look into it more.
>
> The highest level goal is to make it as easy as possible for someone to
> volunteer to be an RM. Any requirement of "install this (Docker, etc) on
> your computer" is, IMO, another barrier to entry. Yeah, RMs will have to
> have Maven installed and maybe Ant, but you should already have those
> installed to be a committer/PMC member.
>
> That said, a good takeaway from the Docker idea is to try to find a way to
> make an "Image" of whatever we end up with on whatever server we end up
> using so if the image can be copied and used on other servers. I'm not
> exactly sure how to do that with Azure, which hosts my CI server. I will
> spend a few more minutes researching that.
>
> I could not quickly find any way to get a free VM on Azure or AWS that
> isn't a free-trial-start-paying-after-a-year. So, unless someone comes up
> with a free server we can use "forever", I'm going to just start with my
> Azure VM.
>
> -Alex
>
> On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi.
>
> the plan sounds very good to me. Just my 2 thoughts on this:
>
> 1.- As I was reading I was thinking as well on something like Docker
> and
> see Om as well thinking on the same. Maybe is the way to this with the
> actual technology. Seems VMs are stepping out a bit this days in favor
> of
> things like Docker. Maybe the same did Git over Svn, and today Svn is
> an
> old remembrance. I must say that I have no experience with Docker, so
> doing
> that will require acquire that knowledge, but seems it could be worth
> it.
>
> 2.- Maybe is not possible, but I want to propose to do this work I a
> separate branch, so it could be in parallel to other developments. I
> think
> work over develop is practical if there's something tiny that could be
> done
> in a commit. But as we need more than one, or is a long process (like
> this), chances are to make develop branch unstable and even for some
> days.
> I think we should try to avoid that scenario, and branches are the best
> way. If we do this way, we'll benefit of more reliable develop branch.
>
> Thanks and good to know of this plan :)
>
> Carlos
>
>
> El mar., 5 feb. 2019 a las 23:19, Harbs (<ha...@gmail.com>)
> escribió:
>
> > I’ve never used Docker myself, but that might be a good plan.
> >
> > > On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
> bigosmallm@gmail.com>
> > wrote:
> > >
> > > I was wondering if we can use docker images to setup and seal the
> RM
> > > environment. Then other RMs simply need to run the image locally
> and run
> > > the release scripts. Might be easier. If folks like this plan, I
> can
> > try
> > > to put something together.
> > >
> > > Thanks,
> > > Om
> > >
> > > On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com>
> wrote:
> > >
> > >> In a recent discussion, it looks like other projects have gotten
> > resources
> > >> from AWS.
> > >>
> > >> Whatever service we use, could setup a “shared” Royale account
> that all
> > >> PMC members could have access to.
> > >>
> > >> I don’t know if there’s some way we could leverage Gitlab’s
> integration
> > >> pipelines
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7Cef2b34e531be41983c1208d68c009d75%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850331599744364&sdata=ux3NQZcnILfobRoGhlxI509Z30JI2Tba4O%2FDxWFii9w%3D&reserved=0
> <
> > >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7Cef2b34e531be41983c1208d68c009d75%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850331599744364&sdata=ux3NQZcnILfobRoGhlxI509Z30JI2Tba4O%2FDxWFii9w%3D&reserved=0
> >
> > >>
> > >>> On Feb 5, 2019, at 11:33 PM, Alex Harui <aharui@adobe.com.INVALID
> >
> > >> wrote:
> > >>>
> > >>> 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" <pi...@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.lists@gmail.com
> wrote:
> > >>>
> > >>>> A big +1 from me!
> > >>>>
> > >>>> Looking forward!
> > >>>>
> > >>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui
> <ah...@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
> > >>>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>
> > >>
> >
> >
>
> --
> Carlos Rovira
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cef2b34e531be41983c1208d68c009d75%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850331599744364&sdata=%2BBjFv4hgPoVNn5ymJnenJAvPkkTJzZx%2FeXfMtSpogEE%3D&reserved=0
>
>
>
RE: 0.9.6 Release
Posted by Yishay Weiss <yi...@hotmail.com>.
I’ll let Om or someone else with docker experience tell us if this [1] is relevant.
[1] https://hub.docker.com/r/beli/firefox-flash/
________________________________
From: Alex Harui <ah...@adobe.com.INVALID>
Sent: Wednesday, February 6, 2019 10:05:54 AM
To: dev@royale.apache.org
Subject: Re: 0.9.6 Release
I don't anything about docker, but in 15 minutes of reading I ran into this:
https://www.channelfutures.com/open-source/when-not-to-use-docker-understanding-the-limitations-of-containers
Which says: Docker can't " Run applications with graphical interfaces". If you want Royale to use Docker for releases, show that it can run checkintests with Flash and the Browser. Then I will look into it more.
The highest level goal is to make it as easy as possible for someone to volunteer to be an RM. Any requirement of "install this (Docker, etc) on your computer" is, IMO, another barrier to entry. Yeah, RMs will have to have Maven installed and maybe Ant, but you should already have those installed to be a committer/PMC member.
That said, a good takeaway from the Docker idea is to try to find a way to make an "Image" of whatever we end up with on whatever server we end up using so if the image can be copied and used on other servers. I'm not exactly sure how to do that with Azure, which hosts my CI server. I will spend a few more minutes researching that.
I could not quickly find any way to get a free VM on Azure or AWS that isn't a free-trial-start-paying-after-a-year. So, unless someone comes up with a free server we can use "forever", I'm going to just start with my Azure VM.
-Alex
On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi.
the plan sounds very good to me. Just my 2 thoughts on this:
1.- As I was reading I was thinking as well on something like Docker and
see Om as well thinking on the same. Maybe is the way to this with the
actual technology. Seems VMs are stepping out a bit this days in favor of
things like Docker. Maybe the same did Git over Svn, and today Svn is an
old remembrance. I must say that I have no experience with Docker, so doing
that will require acquire that knowledge, but seems it could be worth it.
2.- Maybe is not possible, but I want to propose to do this work I a
separate branch, so it could be in parallel to other developments. I think
work over develop is practical if there's something tiny that could be done
in a commit. But as we need more than one, or is a long process (like
this), chances are to make develop branch unstable and even for some days.
I think we should try to avoid that scenario, and branches are the best
way. If we do this way, we'll benefit of more reliable develop branch.
Thanks and good to know of this plan :)
Carlos
El mar., 5 feb. 2019 a las 23:19, Harbs (<ha...@gmail.com>) escribió:
> I’ve never used Docker myself, but that might be a good plan.
>
> > On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <bi...@gmail.com>
> wrote:
> >
> > I was wondering if we can use docker images to setup and seal the RM
> > environment. Then other RMs simply need to run the image locally and run
> > the release scripts. Might be easier. If folks like this plan, I can
> try
> > to put something together.
> >
> > Thanks,
> > Om
> >
> > On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com> wrote:
> >
> >> In a recent discussion, it looks like other projects have gotten
> resources
> >> from AWS.
> >>
> >> Whatever service we use, could setup a “shared” Royale account that all
> >> PMC members could have access to.
> >>
> >> I don’t know if there’s some way we could leverage Gitlab’s integration
> >> pipelines https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7Cef2b34e531be41983c1208d68c009d75%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850331599744364&sdata=ux3NQZcnILfobRoGhlxI509Z30JI2Tba4O%2FDxWFii9w%3D&reserved=0 <
> >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7Cef2b34e531be41983c1208d68c009d75%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850331599744364&sdata=ux3NQZcnILfobRoGhlxI509Z30JI2Tba4O%2FDxWFii9w%3D&reserved=0>
> >>
> >>> On Feb 5, 2019, at 11:33 PM, Alex Harui <ah...@adobe.com.INVALID>
> >> wrote:
> >>>
> >>> 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" <pi...@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.lists@gmail.com wrote:
> >>>
> >>>> A big +1 from me!
> >>>>
> >>>> Looking forward!
> >>>>
> >>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui <ah...@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
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
>
>
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cef2b34e531be41983c1208d68c009d75%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850331599744364&sdata=%2BBjFv4hgPoVNn5ymJnenJAvPkkTJzZx%2FeXfMtSpogEE%3D&reserved=0
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I don't anything about docker, but in 15 minutes of reading I ran into this:
https://www.channelfutures.com/open-source/when-not-to-use-docker-understanding-the-limitations-of-containers
Which says: Docker can't " Run applications with graphical interfaces". If you want Royale to use Docker for releases, show that it can run checkintests with Flash and the Browser. Then I will look into it more.
The highest level goal is to make it as easy as possible for someone to volunteer to be an RM. Any requirement of "install this (Docker, etc) on your computer" is, IMO, another barrier to entry. Yeah, RMs will have to have Maven installed and maybe Ant, but you should already have those installed to be a committer/PMC member.
That said, a good takeaway from the Docker idea is to try to find a way to make an "Image" of whatever we end up with on whatever server we end up using so if the image can be copied and used on other servers. I'm not exactly sure how to do that with Azure, which hosts my CI server. I will spend a few more minutes researching that.
I could not quickly find any way to get a free VM on Azure or AWS that isn't a free-trial-start-paying-after-a-year. So, unless someone comes up with a free server we can use "forever", I'm going to just start with my Azure VM.
-Alex
On 2/5/19, 10:59 PM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi.
the plan sounds very good to me. Just my 2 thoughts on this:
1.- As I was reading I was thinking as well on something like Docker and
see Om as well thinking on the same. Maybe is the way to this with the
actual technology. Seems VMs are stepping out a bit this days in favor of
things like Docker. Maybe the same did Git over Svn, and today Svn is an
old remembrance. I must say that I have no experience with Docker, so doing
that will require acquire that knowledge, but seems it could be worth it.
2.- Maybe is not possible, but I want to propose to do this work I a
separate branch, so it could be in parallel to other developments. I think
work over develop is practical if there's something tiny that could be done
in a commit. But as we need more than one, or is a long process (like
this), chances are to make develop branch unstable and even for some days.
I think we should try to avoid that scenario, and branches are the best
way. If we do this way, we'll benefit of more reliable develop branch.
Thanks and good to know of this plan :)
Carlos
El mar., 5 feb. 2019 a las 23:19, Harbs (<ha...@gmail.com>) escribió:
> I’ve never used Docker myself, but that might be a good plan.
>
> > On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <bi...@gmail.com>
> wrote:
> >
> > I was wondering if we can use docker images to setup and seal the RM
> > environment. Then other RMs simply need to run the image locally and run
> > the release scripts. Might be easier. If folks like this plan, I can
> try
> > to put something together.
> >
> > Thanks,
> > Om
> >
> > On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com> wrote:
> >
> >> In a recent discussion, it looks like other projects have gotten
> resources
> >> from AWS.
> >>
> >> Whatever service we use, could setup a “shared” Royale account that all
> >> PMC members could have access to.
> >>
> >> I don’t know if there’s some way we could leverage Gitlab’s integration
> >> pipelines https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7Cef2b34e531be41983c1208d68c009d75%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850331599744364&sdata=ux3NQZcnILfobRoGhlxI509Z30JI2Tba4O%2FDxWFii9w%3D&reserved=0 <
> >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.html&data=02%7C01%7Caharui%40adobe.com%7Cef2b34e531be41983c1208d68c009d75%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850331599744364&sdata=ux3NQZcnILfobRoGhlxI509Z30JI2Tba4O%2FDxWFii9w%3D&reserved=0>
> >>
> >>> On Feb 5, 2019, at 11:33 PM, Alex Harui <ah...@adobe.com.INVALID>
> >> wrote:
> >>>
> >>> 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" <pi...@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.lists@gmail.com wrote:
> >>>
> >>>> A big +1 from me!
> >>>>
> >>>> Looking forward!
> >>>>
> >>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui <ah...@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
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
>
>
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cef2b34e531be41983c1208d68c009d75%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850331599744364&sdata=%2BBjFv4hgPoVNn5ymJnenJAvPkkTJzZx%2FeXfMtSpogEE%3D&reserved=0
Re: 0.9.6 Release
Posted by Carlos Rovira <ca...@apache.org>.
Hi.
the plan sounds very good to me. Just my 2 thoughts on this:
1.- As I was reading I was thinking as well on something like Docker and
see Om as well thinking on the same. Maybe is the way to this with the
actual technology. Seems VMs are stepping out a bit this days in favor of
things like Docker. Maybe the same did Git over Svn, and today Svn is an
old remembrance. I must say that I have no experience with Docker, so doing
that will require acquire that knowledge, but seems it could be worth it.
2.- Maybe is not possible, but I want to propose to do this work I a
separate branch, so it could be in parallel to other developments. I think
work over develop is practical if there's something tiny that could be done
in a commit. But as we need more than one, or is a long process (like
this), chances are to make develop branch unstable and even for some days.
I think we should try to avoid that scenario, and branches are the best
way. If we do this way, we'll benefit of more reliable develop branch.
Thanks and good to know of this plan :)
Carlos
El mar., 5 feb. 2019 a las 23:19, Harbs (<ha...@gmail.com>) escribió:
> I’ve never used Docker myself, but that might be a good plan.
>
> > On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <bi...@gmail.com>
> wrote:
> >
> > I was wondering if we can use docker images to setup and seal the RM
> > environment. Then other RMs simply need to run the image locally and run
> > the release scripts. Might be easier. If folks like this plan, I can
> try
> > to put something together.
> >
> > Thanks,
> > Om
> >
> > On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com> wrote:
> >
> >> In a recent discussion, it looks like other projects have gotten
> resources
> >> from AWS.
> >>
> >> Whatever service we use, could setup a “shared” Royale account that all
> >> PMC members could have access to.
> >>
> >> I don’t know if there’s some way we could leverage Gitlab’s integration
> >> pipelines https://docs.gitlab.com/ee/ci/README.html <
> >> https://docs.gitlab.com/ee/ci/README.html>
> >>
> >>> On Feb 5, 2019, at 11:33 PM, Alex Harui <ah...@adobe.com.INVALID>
> >> wrote:
> >>>
> >>> 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" <pi...@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.lists@gmail.com wrote:
> >>>
> >>>> A big +1 from me!
> >>>>
> >>>> Looking forward!
> >>>>
> >>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui <ah...@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
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: 0.9.6 Release
Posted by Harbs <ha...@gmail.com>.
I’ve never used Docker myself, but that might be a good plan.
> On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <bi...@gmail.com> wrote:
>
> I was wondering if we can use docker images to setup and seal the RM
> environment. Then other RMs simply need to run the image locally and run
> the release scripts. Might be easier. If folks like this plan, I can try
> to put something together.
>
> Thanks,
> Om
>
> On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com> wrote:
>
>> In a recent discussion, it looks like other projects have gotten resources
>> from AWS.
>>
>> Whatever service we use, could setup a “shared” Royale account that all
>> PMC members could have access to.
>>
>> I don’t know if there’s some way we could leverage Gitlab’s integration
>> pipelines https://docs.gitlab.com/ee/ci/README.html <
>> https://docs.gitlab.com/ee/ci/README.html>
>>
>>> On Feb 5, 2019, at 11:33 PM, Alex Harui <ah...@adobe.com.INVALID>
>> wrote:
>>>
>>> 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" <pi...@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.lists@gmail.com wrote:
>>>
>>>> A big +1 from me!
>>>>
>>>> Looking forward!
>>>>
>>>>> On Feb 5, 2019, at 9:34 PM, Alex Harui <ah...@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
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
Re: 0.9.6 Release
Posted by OmPrakash Muppirala <bi...@gmail.com>.
I was wondering if we can use docker images to setup and seal the RM
environment. Then other RMs simply need to run the image locally and run
the release scripts. Might be easier. If folks like this plan, I can try
to put something together.
Thanks,
Om
On Tue, Feb 5, 2019 at 1:40 PM Harbs <ha...@gmail.com> wrote:
> In a recent discussion, it looks like other projects have gotten resources
> from AWS.
>
> Whatever service we use, could setup a “shared” Royale account that all
> PMC members could have access to.
>
> I don’t know if there’s some way we could leverage Gitlab’s integration
> pipelines https://docs.gitlab.com/ee/ci/README.html <
> https://docs.gitlab.com/ee/ci/README.html>
>
> > On Feb 5, 2019, at 11:33 PM, Alex Harui <ah...@adobe.com.INVALID>
> wrote:
> >
> > 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" <pi...@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.lists@gmail.com wrote:
> >
> >> A big +1 from me!
> >>
> >> Looking forward!
> >>
> >>> On Feb 5, 2019, at 9:34 PM, Alex Harui <ah...@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
> >>>
> >>
> >>
> >
> >
>
>
Re: 0.9.6 Release
Posted by Harbs <ha...@gmail.com>.
In a recent discussion, it looks like other projects have gotten resources from AWS.
Whatever service we use, could setup a “shared” Royale account that all PMC members could have access to.
I don’t know if there’s some way we could leverage Gitlab’s integration pipelines https://docs.gitlab.com/ee/ci/README.html <https://docs.gitlab.com/ee/ci/README.html>
> On Feb 5, 2019, at 11:33 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> 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" <pi...@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.lists@gmail.com wrote:
>
>> A big +1 from me!
>>
>> Looking forward!
>>
>>> On Feb 5, 2019, at 9:34 PM, Alex Harui <ah...@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
>>>
>>
>>
>
>
Re: 0.9.6 Release
Posted by Alex Harui <ah...@adobe.com.INVALID>.
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" <pi...@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.lists@gmail.com wrote:
> A big +1 from me!
>
> Looking forward!
>
> > On Feb 5, 2019, at 9:34 PM, Alex Harui <ah...@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
> >
>
>
Re: 0.9.6 Release
Posted by Piotr Zarzycki <pi...@gmail.com>.
Sounds like best plan ever. Using the same PC by everyone is awesome!
On Tue, Feb 5, 2019, 8:39 PM Harbs <harbs.lists@gmail.com wrote:
> A big +1 from me!
>
> Looking forward!
>
> > On Feb 5, 2019, at 9:34 PM, Alex Harui <ah...@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
> >
>
>
Re: 0.9.6 Release
Posted by Harbs <ha...@gmail.com>.
A big +1 from me!
Looking forward!
> On Feb 5, 2019, at 9:34 PM, Alex Harui <ah...@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
>