Royale_Release_Step_008 - Build # 13 - Still Failing!

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

Royale_Release_Step_008 - Build # 12 - Still Failing!

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

Royale_Release_Step_008 - Build # 11 - Still Failing!

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

Royale_Release_Step_008 - Build # 10 - Still Failing!

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

Royale_Release_Step_008 - Build # 9 - Failure!

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

Release Step 007 Succeeded

>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.8 -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

Royale_Release_Step_007 - Build # 17 - Still Failing!

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

Royale_Release_Step_007 - Build # 16 - Failure!

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

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.8-rc2 You will need your Apache/Github username and 2FA token.

Release Step 005 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands: git push You will need your Apache/Github username and 2FA token.

Release Step 004 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands: git push git checkout release/0.9.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.

Royale_Release_Step_004 - Build # 22 - Still Failing!

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

Royale_Release_Step_004 - Build # 21 - Still Failing!

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

Royale_Release_Step_004 - Build # 20 - Failure!

Royale_Release_Step_004 - Build # 20 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/20/ 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.8 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

Royale_Release_Step_003 - Build # 30 - Failure!

Royale_Release_Step_003 - Build # 30 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_003/30/ 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.8 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

Release Step 003 Succeeded

>From the royale-compiler repo: 1. Run: ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8 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

Royale_Release_Step_003 - Build # 27 - Still Failing!

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

Royale_Release_Step_003 - Build # 26 - Still Failing!

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

Royale_Release_Step_003 - Build # 25 - Failure!

Royale_Release_Step_003 - Build # 25 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_003/25/ 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.8 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

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.8-rc2 You will need your Apache/Github username and 2FA token.

Royale_Release_Step_002 - Build # 56 - Failure!

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

Release Step 001 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 26 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 25 - Still Failing!

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

Royale Compiler Build Tools Release Step 001 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-0.9.8-rc2 You will need your

Royale Compiler Build Tools Release Step 001 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-0.9.8-rc2 You will need your

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 24 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 23 - Failure!

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 23 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_001/23/ 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.8 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

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.8-rc1 You will need your Apache/Github username and 2FA token.

Royale_Release_Step_002 - Build # 54 - Still Failing!

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

Royale_Release_Step_002 - Build # 53 - Still Failing!

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

Royale_Release_Step_002 - Build # 52 - Still Failing!

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

Royale_Release_Step_002 - Build # 51 - Still Failing!

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

Release Step 001 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.

Royale Compiler Build Tools Release Step 003 Succeeded

Folder 1.2.1 created. Login to CI server. Change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_003 and run 'svn commit -m "add version folder" -- username='. You will need your svn username and password.

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 24 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 23 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 22 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 21 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 20 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 19 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 18 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 17 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!

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

Royale Compiler Build Tools Release Step 001 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-1.2.1-rc1 You will need your

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 21 - Failure!

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

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 14 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 13 - Failure!

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

Royale Compiler Build Tools Release Step 001 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-1.2.1-rc1 You will need your

Royale_Release_Step_002 - Build # 50 - Still Failing!

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

Royale_Release_Step_002 - Build # 49 - Still Failing!

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

Royale_Release_Step_002 - Build # 48 - Failure!

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

Release Step 001 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.

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

See Changes: -- [...truncated 2.05 MB...] check-compiler-home: check-compile-env: [echo] OS: Windows Server 2016 / 10.0 / amd64 [echo] VM:

Build failed in Jenkins: royale-asjs #1255

See Changes: -- [...truncated 136.52 KB...] [echo] swc-date is 05/28/20 04:21 + [delete] Deleting:

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

See Changes: -- [...truncated 2.05 MB...] check-compiler-home: check-compile-env: [echo] OS: Windows Server 2016 / 10.0 / amd64 [echo] VM:

Build failed in Jenkins: royale-asjs #1254

See Changes: -- [...truncated 135.88 KB...] [echo] swc-date is 05/28/20 02:55 + [delete] Deleting:

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

See Changes: -- [...truncated 2.05 MB...] check-compiler-home: check-compile-env: [echo] OS: Windows Server 2016 / 10.0 / amd64 [echo] VM:

Build failed in Jenkins: royale-asjs #1253

See Changes: -- [...truncated 137.16 KB...] [echo] swc-date is 05/27/20 17:28 + [delete] Deleting:

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

See Changes: [carlos.rovira] jewel: default css was not updated for BinaryImage -- [...truncated 2.05 MB...] check-compiler-home:

Build failed in Jenkins: royale-asjs #1252

See Changes: [carlos.rovira] jewel: default css was not updated for BinaryImage -- [...truncated 135.89 KB...] [echo] swc-date is 05/27/20

Build failed in Jenkins: royale-asjs #1251

See Changes: -- [...truncated 137.24 KB...] [echo] swc-date is 05/27/20 12:27 + [delete] Deleting:

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

See Changes: -- [...truncated 250.10 KB...] check-sum: [echo] basedir is C:\jenkins\workspace\royale-compiler\compiler\src\main\resources

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

See

Build failed in Jenkins: royale-asjs_jsonly #1550

See Changes: -- [...truncated 1.16 MB...] [java] repl parameters not found! 0 [java] stream parameters not found! 0 [java] tls

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

See Changes: -- [...truncated 2.05 MB...] check-compiler-home: check-compile-env: [echo] OS: Windows Server 2016 / 10.0 / amd64 [echo] VM:

Build failed in Jenkins: royale-asjs #1250

See Changes: -- [...truncated 136.60 KB...] [echo] swc-date is 05/27/20 04:20 + [delete] Deleting:

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

See Changes: -- [...truncated 2.05 MB...] check-compiler-home: check-compile-env: [echo] OS: Windows Server 2016 / 10.0 / amd64 [echo] VM:

Build failed in Jenkins: royale-asjs #1249

See Changes: -- [...truncated 135.96 KB...] [echo] swc-date is 05/27/20 02:54 + [delete] Deleting:

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

See Changes: [joshtynjala] UIBase: move getParentEventTarget() here from EventDispatcher to reduce -- [...truncated 2.05 MB...]

Build failed in Jenkins: royale-asjs #1248

See Changes: [joshtynjala] UIBase: move getParentEventTarget() here from EventDispatcher to reduce -- [...truncated 137.25 KB...] [echo]

Jenkins build is back to normal : royale-compiler #423

See

Build failed in Jenkins: royale-compiler #422

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. FATAL: java.nio.channels.ClosedChannelException

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

See Changes: [joshtynjala] RoyaleUnit: CIListener escapes attributes with the correct type to fix -- [...truncated 2.05 MB...]

Build failed in Jenkins: royale-asjs #1247

See Changes: [joshtynjala] RoyaleUnit: CIListener escapes attributes with the correct type to fix -- [...truncated 135.95 KB...] [echo]

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

See Changes: -- [...truncated 2.05 MB...] check-air-home: [echo] AIR_HOME is C:\adobe\air\4.0\AdobeAIRSDK check-compiler-home: check-compile-env:

Build failed in Jenkins: royale-asjs #1246

See Changes: -- [...truncated 137.15 KB...] [echo] swc-date is 05/26/20 12:28 + [delete] Deleting:

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

See Changes: -- [...truncated 2.05 MB...] check-air-home: [echo] AIR_HOME is C:\adobe\air\4.0\AdobeAIRSDK check-compiler-home: check-compile-env:

Build failed in Jenkins: royale-asjs #1245

See Changes: -- [...truncated 136.51 KB...] [echo] swc-date is 05/26/20 04:21 + [delete] Deleting:

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

See Changes: -- [...truncated 2.05 MB...] check-air-home: [echo] AIR_HOME is C:\adobe\air\4.0\AdobeAIRSDK check-compiler-home: check-compile-env:

Build failed in Jenkins: royale-asjs #1244

See Changes: -- [...truncated 135.88 KB...] [echo] swc-date is 05/26/20 02:55 + [delete] Deleting:

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

See Changes: [raudjcholo] Add BinaryImage to Jewel [raudjcholo] Change beads of BinaryImage to Basic class -- [...truncated 2.05 MB...]

Build failed in Jenkins: royale-asjs #1243

See Changes: [raudjcholo] Add BinaryImage to Jewel [raudjcholo] Change beads of BinaryImage to Basic class -- [...truncated 135.88 KB...]

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

See Changes: -- [...truncated 2.05 MB...] check-air-home: [echo] AIR_HOME is C:\adobe\air\4.0\AdobeAIRSDK check-compiler-home: check-compile-env:

Build failed in Jenkins: royale-asjs #1242

See Changes: -- [...truncated 137.14 KB...] [echo] swc-date is 05/25/20 12:29 + [delete] Deleting:

Jenkins build is back to normal : royale-typedefs #641

See

Build failed in Jenkins: royale-typedefs #640

See Changes: -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. FATAL: java.nio.channels.ClosedChannelException

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

See Changes: -- [...truncated 2.05 MB...] check-air-home: [echo] AIR_HOME is C:\adobe\air\4.0\AdobeAIRSDK check-compiler-home: check-compile-env:

Build failed in Jenkins: royale-asjs #1241

See Changes: -- [...truncated 135.87 KB...] [echo] swc-date is 05/25/20 02:54 + [delete] Deleting:

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

See Changes: [yishayjobs] Make mx comboboxes hide on mousedownout -- [...truncated 2.05 MB...] check-air-home: [echo] AIR_HOME is

Build failed in Jenkins: royale-asjs #1240

See Changes: [yishayjobs] Make mx comboboxes hide on mousedownout -- [...truncated 135.88 KB...] [echo] swc-date is 05/24/20 18:55 +

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

See Changes: -- [...truncated 2.05 MB...] check-air-home: [echo] AIR_HOME is C:\adobe\air\4.0\AdobeAIRSDK check-compiler-home: check-compile-env:

Build failed in Jenkins: royale-asjs #1239

See Changes: -- [...truncated 137.15 KB...] [echo] swc-date is 05/24/20 12:29 + [delete] Deleting:

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

See Changes: -- [...truncated 2.05 MB...] check-air-home: [echo] AIR_HOME is C:\adobe\air\4.0\AdobeAIRSDK check-compiler-home: check-compile-env:

Build failed in Jenkins: royale-asjs #1238

See Changes: -- [...truncated 136.52 KB...] [echo] swc-date is 05/24/20 04:20 + [delete] Deleting:

<    1   2   3   4   5   6   7   8   9   10   >