RE: Royale Compiler Build Tools Release Step 002 Succeeded

Hi Chris, I was indeed comparing the wrong jars. After looking at the ant script I can see that what needs to be compared is between jars downloaded from the archive [1] and the binaries build a second time from src [2] The ant script fails with a message if the binaries don’t match, but does

Re: Add Key to Royale Key Server

What documentation steps are you trying to follow? Are you using: [1] https://infra.apache.org/release-signing.html#key-basics [2] https://infra.apache.org/openpgp.html#gnupg [3] https://infra.apache.org/release-signing.html#keyserver-upload I don't think there is a keyserver there. I think

Re: Create new branch when creating a release (was Fwd: Royale Releases)

It is Maven's default settings so it seems like their recommended workflow. Any changes to the develop branch after the release branches are cut are not going to be in the 0.9.7 artifacts, so I would think you would want to bump up the version to avoid confusion. -Alex On 4/13/20, 12:52 AM,

Re: Add Key to Royale Key Server

For my sins, I am responsible for maintaining that document. Please let me know if parts are unclear or inaccurate/ Andrew Virus-free. www.avast.com

Royale Compiler Build Tools Release Step 003 Succeeded

Folder 1.2.0 already exists. Continue to next step.

Re: [DISCUSS] Discuss Release Apache Royale 1.2.0

Hi, I'm having problems verifying signature. I can't check the public key with the apache key servers in documentation. What should you do in this cases? (what command you use that is currently working for you?) thanks El lun., 13 abr. 2020 a las 22:33, escribió: > This is the discussion

Re: [DISCUSS] Discuss Release Apache Royale 1.2.0

I haven't tried it myself, but I'm pretty sure we need to re-import the KEYS file. Steps should be something like: 1) download https://downloads.apache.org/royale/KEYS 2) gpg --import HTH, -Alex On 4/13/20, 3:27 PM, "Carlos Rovira" wrote: Hi, I'm having problems verifying

Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

+1 Package https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/apache-royale-compiler-build-tools-1.2.0-source-release.zip Java 1.8 OS: Mac OS X x86_64 10.15.3 Source kit signatures match: y Source kit builds: y README is ok: ${readme.ok} RELEASE_NOTES is ok:

Re: Staging Folder Number

Try this link: https://repository.apache.org/#stagingRepositories Otherwise, in the left pane should be: "Build Promotion". Expand that. Then you should see "Staging Repositories". Click on that. Then a datagrid should show up in the main area and scroll down. PS: I already looked and the

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 11 - Failure!

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 11 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_004/11/ to view the results.

RE: Royale_Compiler_Build_Tools_Release_Step_004 - Build # 13 - Still Failing!

Actually, this was the message that I saw: Folder 1.2.0 already exists. Continue to next step. From: Alex Harui Sent: Monday, April 13, 2020 9:49:37 PM To: dev@royale.apache.org ; dev@royale.apache.org Subject: Re:

Re: Royale_Compiler_Build_Tools_Release_Step_004 - Build # 13 - Still Failing!

Sorry, I grabbed the wrong thread. In step 002, the last sentence should be "hit the close button" On 4/13/20, 12:00 PM, "Yishay Weiss" wrote: Actually, this was the message that I saw: Folder 1.2.0 already exists. Continue to next step.

[DISCUSS] Discuss Release Apache Royale 1.2.0

This is the discussion thread. Thanks, Yishay Weiss

Re: Royale_Compiler_Build_Tools_Release_Step_004 - Build # 14 - Still Failing!

The Nexus sig validation is separate from KEYS, IIRC. Usually it means the .asc files did not get uploaded from your local machine. But it looks like the second attempt worked. Congratulations! -Alex On 4/13/20, 12:32 PM, "Yishay Weiss" wrote: Looks like signature validation failed

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 12 - Still Failing!

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 12 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_004/12/ to view the results.

Re: Royale_Compiler_Build_Tools_Release_Step_004 - Build # 13 - Still Failing!

Yishay, it looks like you missed the final instruction in the success email: " hit the close button to close the staging repo." Ideas on how to make that more obvious are welcome. -Alex On 4/13/20, 11:46 AM, "apacheroyal...@gmail.com" wrote: Royale_Compiler_Build_Tools_Release_Step_004

RE: Royale Compiler Build Tools Release Step 003 Succeeded

Finally saw the correct instruction. I was confused because the steps 1-4 are numbered, but the last instruction looks like a footnote without a number. I would put the last instruction as (5) right underneath (4) and leave the m2 settings xml as a footnote. From: Alex Harui Sent: Monday,

Staging Folder Number

I couldn’t figure it out using these instructions [1]. How do I look for the folder name? [1] The number of the staging folder in https://repository.apache.org. The folder name will be something like orgapacheroyale-1234. Only enter the 1234.

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 13 - Still Failing!

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 13 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_004/13/ to view the results.

Royale Compiler Build Tools Release Step 004 Succeeded

Log in to the server, open a command prompt and change directory to: C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_004\dist\dev 1. Run svn --username= commit -m "Compiler Build Tools 1.2.0 rc 3" This will upload the signed artifacts to dist.apache.org. You will need your svn

RE: Add Key to Royale Key Server

Hi Andrew, It’s not clear to me from our docs [1] what the equivalent of –keyserver is as described in this doc [2]. Alex, I don’t understand how to manually copy a file. Under which repo is it? [1] https://infra.apache.org/release-signing.html#keyserver-upload [2]

Re: Add Key to Royale Key Server

The Royale keys file is in this folder: URL: https://dist.apache.org/repos/dist/release/royale If you run: gpg --armor --export yishayw It should dump the public key to the console. It should look like: -BEGIN PGP PUBLIC KEY BLOCK- Comment: GPGTools - http://gpgtools.org

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 14 - Still Failing!

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 14 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_004/14/ to view the results.

RE: Add Key to Royale Key Server

> Please run a diff before committing to make sure nothing else got changed. I guess what I was missing was how to commit files to dist.a.o On 4/13/20, 10:26 AM, "Yishay Weiss" wrote: Hi Andrew, It’s not clear to me from our docs [1] what the equivalent of –keyserver is as described

RE: Royale Compiler Build Tools Release Step 003 Succeeded

Looks like the email wasn’t sent correctly, which is why I got the ‘folder already exists’ message instead. From: apacheroyal...@gmail.com Sent: Saturday, April 11, 2020 8:36 AM To: dev@royale.apache.org Subject: Royale Compiler

[VOTE] Release Apache Royale Compiler Build Tools 1.2.0

Hi, This is the vote for the 1.2.0 release of Apache Royale Compiler Build Tools. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/ Before voting please review the section,'What are the ASF requirements on approving a

Re: Add Key to Royale Key Server

Dist.a.o uses Subversion. To get the KEYS file, try creating a folder to store the working copy on your machine, then in that folder: svn checkout --non-recursive https://dist.apache.org/repos/dist dist cd .\dist svn update --non-recursive release cd release svn update --depth infinity royale

Re: Royale Compiler Build Tools Release Step 003 Succeeded

The one from today looks ok. The one you quoted was from my practice runs over the weekend which I fixed. That folder does exist so step 003's message is correct. I think Step 004 is failing because you missed the last instruction in 002's email. -Alex On 4/13/20, 12:08 PM, "Yishay Weiss"

Re: Prioritize Release Jobs on CI

Alex, I believe this is your personal Azure subscription right? Any chance I can get access to it so I can try to copy the image out the machine and redeploy it somewhere else? Thanks, Om On Sun, Apr 12, 2020 at 6:18 PM OmPrakash Muppirala wrote: > I can help set this up on Azure. Give me

Re: Create new branch when creating a release (was Fwd: Royale Releases)

Hi Alex, I think there's a misunderstanding about this. Now that you passed compiler and reach typedefs, you can see we have commits in both repositories in develop branch with version changes. So this morning, building from sources is making me build 0.9.8 of compiler and typedefs. But people

Re: Create new branch when creating a release (was Fwd: Royale Releases)

Why should we have a different branch strategy than what Maven recommends? On 4/13/20, 12:38 AM, "Carlos Rovira" wrote: Hi Alex, I think there's a misunderstanding about this. Now that you passed compiler and reach typedefs, you can see we have commits in both repositories in

RE: Prioritize Release Jobs on CI

Can’t you do that with remote desktop? From: OmPrakash Muppirala Sent: Monday, April 13, 2020 9:51:25 AM To: Apache Royale Development Subject: Re: Prioritize Release Jobs on CI Alex, I believe this is your personal Azure subscription right? Any chance I can

RE: Prioritize Release Jobs on CI

Related, as most (all?) of the instructions don’t require anything but a shell wouldn’t it be easier and faster to access the machine with ssh [1], rather than using remote desktop? [1] https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse From:

Re: Prioritize Release Jobs on CI

I don't think I should be giving out my MSDN credentials. If you can install other shell capabilities or access the image via RDP, go for it. If there is some secure way to share the image let me know what it is. I don't know much about Azure. -Alex On 4/13/20, 12:02 AM, "Yishay Weiss"

Re: Royale Compiler Build Tools Release Step 001 Succeeded

Don't it's needed to increase rc number if it didn't go to a vote. I think rc versions is just to indicate voters are voting a different version than before that corrects the problems in the previous rc. thanks El dom., 12 abr. 2020 a las 20:13, Alex Harui () escribió: > I think you will have to

Re: Royale Compiler Build Tools Release Step 001 Succeeded

Technically you are correct, but then you should go delete the tag. And by using a different RC number we can compare what he produces against the folder I produced. -Alex On 4/13/20, 12:30 AM, "Carlos Rovira" wrote: Don't it's needed to increase rc number if it didn't go to a vote. I

Re: Prioritize Release Jobs on CI

I don't know much about Azure. I could not figure out how to add a user. I have to stop work for tonight. If you have explicit steps I can try again tomorrow evening. -Alex On 4/13/20, 12:34 AM, "OmPrakash Muppirala" wrote: You wont have to share your MSDN credentials. You can add

RE: Royale Compiler Build Tools Release Step 002 Succeeded

>2. Validate that the compiled artifacts match the downloaded artifacts. What does this mean? Looks to me like the jars are different [1]. I’ll see if I understand why. [1] C:\temp1>git diff

Re: Royale Compiler Build Tools Release Step 002 Succeeded

Hi Yishay, ok ... we never talked about comparing the JavaDocs ... just the binary artifacts. I updated the maven-javadoc-plugin to 3.2.0 which is the first reproducible version. Please feel free to merge the PRs (I also disabled the Javadoc in the typedefs as this doesn't make any sense