Release Step 007 Succeeded

>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant

Release Step 006 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands: git push git push origin org.apache.royale.typedefs-0.9.7-rc2 You will need your Apache/Github username and 2FA token.

Royale_Release_Step_006 - Build # 10 - Failure!

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

Release Step 003 Succeeded

>From the royale-compiler repo: 1. Run: ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7 This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps

Build failed in Jenkins: royale-asjs-agent2 #9

See Changes: -- [...truncated 2.05 MB...] flat-ui-icons: [java] Error: Unable to access jarfile

Release Step 002 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.7-rc2 You will need your Apache/Github username and 2FA token.

Release Step 013 Succeeded

>From the royale-asjs repo 1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.7 -Droyale.swc-date="04/24/20 09:07 -0700" -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=2 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Val

Release Step 007 Succeeded

>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant

Release Step 006 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands: git push git push origin org.apache.royale.typedefs-0.9.7-rc2 You will need your Apache/Github username and 2FA token.

Build failed in Jenkins: royale-asjs #1137

See Changes: -- [...truncated 1.35 MB...] [mxmlc] Loading configuration:

Royale_Release_Step_013 - Build # 4 - Still Failing!

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

Royale_Release_Step_013 - Build # 3 - Still Failing!

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

Royale_Release_Step_013 - Build # 2 - Still Failing!

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

Re: royale-asjs build error

To double-check: 1) The mm.cfg contains: ErrorReportingEnable=1 TraceOutputFileEnable=1 2) It is located at %HOMEDRIVE%/%HOMEPATH% 3) Your flashplayerdebugger is a projector debugger and not just a projector. Mine is 10MB HTH, -Alex On 4/24/20, 7:31 PM, "OmPrakash Muppirala" wrote:

Build failed in Jenkins: royale-asjs #1136

See Changes: -- [...truncated 1.34 MB...] [mxmlc] Loading configuration:

Build failed in Jenkins: royale-asjs-agent2 #8

See Changes: -- [...truncated 2.05 MB...] flat-ui-icons: [java] Error: Unable to access jarfile

Royale_Release_Step_013 - Build # 1 - Failure!

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

Re: royale-asjs build error

On Fri, Apr 24, 2020 at 7:25 PM Alex Harui wrote: > Yay, got past the socket error. Yass > FTR, on my VM, I think Jenkins is installed as a service and only that > service is running as User. > Yes, I have done the same thing on mine now. > > Now you got the error that you need the mm.cfg

Re: royale-asjs build error

It definitely went farther along. Now it is breaking at something else. I will keep debugging this over the weekend. On Fri, Apr 24, 2020 at 6:51 PM OmPrakash Muppirala wrote: > > > On Fri, Apr 24, 2020 at 5:43 PM Alex Harui > wrote: > >> Om, the next difference between logs is this on agent 2

Re: royale-asjs build error

Yay, got past the socket error. FTR, on my VM, I think Jenkins is installed as a service and only that service is running as User. Now you got the error that you need the mm.cfg in the appropriate place with the appropriate settings. Try taking the one from my VM. HTH, -Alex On 4/24/20, 6:5

Build failed in Jenkins: royale-asjs-agent2 #7

See Changes: -- [...truncated 2.05 MB...] flat-ui-icons: [java] Error: Unable to access jarfile

Re: royale-asjs build error

On Fri, Apr 24, 2020 at 5:43 PM Alex Harui wrote: > Om, the next difference between logs is this on agent 2: > > [royaleunit] Entry > [C:\jenkins\workspace\royale-asjs-agent2\frameworks\projects\Basic\src\test\royale] > already available in local trust file at > [C:\windows\system32\config\system

Re: royale-asjs build error

Om, the next difference between logs is this on agent 2: [royaleunit] Entry [C:\jenkins\workspace\royale-asjs-agent2\frameworks\projects\Basic\src\test\royale] already available in local trust file at [C:\windows\system32\config\systemprofile\AppData\Roaming\Macromedia\Flash Player\#Security\F

Build failed in Jenkins: royale-asjs #1135

See Changes: -- [...truncated 1.34 MB...] [mxmlc] Loading configuration:

Build failed in Jenkins: royale-asjs #1134

See Changes: [carlosrovira] core: add IRemovableBead with tearDown method for cleaning listeners [carlosrovira] jewel-ListKeyDownController: make IRemovableBead [carlosrovira] searchfor

Build failed in Jenkins: royale-asjs-agent2 #6

See Changes: [carlosrovira] searchforlist: fix to manage correctly hidden items with keys -- [...truncated 1.33 MB...] check-for-tests: clea

Jenkins build is back to normal : royale-asjs_jsonly #1369

See

Build failed in Jenkins: royale-asjs-agent2 #5

See Changes: [carlosrovira] UIBase: simplify a var assignment [carlosrovira] jewel-searchfilter: remove comments [carlosrovira] jewel-list: decouple mouse controller from key control

Re: royale-asjs build error

The change I made was to change the drive letter for the workspace from c: to C:. That was the only obvious difference between the successful job on royale-asjs and the failing job on agent2 and that change made a difference for Maven as well. HTH, -Alex On 4/24/20, 12:29 PM, "OmPrakash Mupp

Re: royale-asjs build error

On Fri, Apr 24, 2020 at 12:14 AM Alex Harui wrote: > Om, can you restart your VM? Jenkins didn't pick up the change I made. > I just restarted it. > > Also, I disabled SSH on my VM so we'll see if we get better success rate > on Agent 1. And I happened to see that there were Outbound Port Ru

Build failed in Jenkins: royale-asjs #1133

See Changes: [carlosrovira] jewel-ListKeyDownController: convert to IBeadKeyController [carlosrovira] jewel-combobox: should solve an issue where click in popup scrollbar [carlosrovira]

Build failed in Jenkins: royale-asjs #1132

See Changes: [carlosrovira] UIBase: simplify a var assignment [carlosrovira] jewel-searchfilter: remove comments [carlosrovira] jewel-list: decouple mouse controller from key controller

Release Step 011 Succeeded

Warning: this step requires a secret key, so it should not be performed on the CI server. It's probably best to perform it on your PC. >From the royale-asjs repo: 1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.7 -DskipTests=true This will download the artifacts then unzip

Build failed in Jenkins: royale-asjs #1131

See Changes: -- [...truncated 1.58 MB...] check-compiler-home: check-transpiler-home: check-compiler: test: clean: compile: [echo] Cross-compiling te

Build failed in Jenkins: royale-asjs #1130

See Changes: [greg.dove] Ported support for ChangeWatcher.watch (without weakReference) [greg.dove] Fix for XMLList top level function should return the original when [greg.dove] Add XML

Release Step 010 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands: git push git push origin org.apache.royale.framework-0.9.7-rc2 You will need your Apache/Github username and 2FA token.

Jenkins build is back to normal : royale-asjs_jsonly #1364

See

Release Step 003 Succeeded

>From the royale-compiler repo: 1. Run: ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7 This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps

Release Step 002 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.7-rc2 You will need your Apache/Github username and 2FA token.

Build failed in Jenkins: royale-asjs_jsonly #1363

See Changes: [greg.dove] Ported support for ChangeWatcher.watch (without weakReference) [greg.dove] Fix for XMLList top level function should return the original when [greg.dove]

Re: royale-asjs build error

Om, can you restart your VM? Jenkins didn't pick up the change I made. Also, I disabled SSH on my VM so we'll see if we get better success rate on Agent 1. And I happened to see that there were Outbound Port Rules for ports used by RoyaleUnit and Flash. Not sure if they are required though.