Royale_Compiler_Build_Tools_Release_Step_001 - Build # 9 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 8 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 7 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 6 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 5 - Failure!

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

Jenkins build is back to normal : royale-asjs #1012

See

Build failed in Jenkins: royale-asjs #1011

See Changes: -- [...truncated 360.56 KB...] double-check-file: [echo] Need file: ${still_no_file} get-from-cache-if-needed: [echo] basedir is C:\jen

Jenkins build is back to normal : royale-compiler-integration-tests #791

See

Build failed in Jenkins: royale-compiler-integration-tests #790

See Changes: -- [...truncated 129.88 KB...] [junit]^ [junit] [junit] Apr 02, 2020 3:06:24 PM com.google.javascript.js

Build failed in Jenkins: royale-compiler-integration-tests #789

See Changes: -- [...truncated 131.53 KB...] [junit] SEVERE: goog/object/object.js:269: ERROR - This language feature is only supported

Jenkins build is back to normal : royale-asjs_MXTests #867

See

Build failed in Jenkins: royale-compiler-integration-tests #788

See Changes: [greg.dove] fix for the original tweak I did here, adding more support for line [greg.dove] fix for const or var as main definition instead of a class. T

Build failed in Jenkins: royale-asjs_MXTests #866

See Changes: [greg.dove] match ant build for settings [greg.dove] Add missing field for now. [greg.dove] Updates to XML classes to support improved e4x conformance.

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

See

Build failed in Jenkins: royale-asjs_jsonly #1180

See Changes: -- [...truncated 1.17 MB...] [java] var events = require('events'); [java] ^^^ [java] [java] Apr 01, 2

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 git push origin org.apache.royale.compiler-build-tools-1.2.0-rc1 You will need your Apache/Github username and 2FA token.

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 3 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 2 - Still Failing!

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

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 1 - Failure!

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

Jenkins build is back to normal : royale-asjs #999

See

Build failed in Jenkins: royale-asjs #998

See Changes: [carlosrovira] fontawesome: add font awesome modifiers [carlosrovira] tour-de-jewel: add font awesome icons -- [...truncated 237.97 K

Jenkins build is back to normal : royale-asjs_MXTests #858

See

Jenkins build is back to normal : royale-asjs #997

See

Build failed in Jenkins: royale-asjs #996

See Changes: [carlosrovira] core-iicon: remove material from interface [carlosrovira] fontawe [carlosrovira] icons: - Add MaterialIcon and MaterialToggleIcon - Deprecate FontIcon [carlo

Build failed in Jenkins: royale-asjs_MXTests #857

See Changes: [carlosrovira] core-iicon: remove material from interface [carlosrovira] fontawe [carlosrovira] icons: - Add MaterialIcon and MaterialToggleIcon - Deprecate FontIcon

Jenkins build is back to normal : royale-compiler-integration-tests #775

See

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

See

Build failed in Jenkins: royale-compiler #305

See Changes: [joshtynjala] JSRoyaleDocEmitter: nocollapse is needed for constants too -- [...truncated 257.05 KB...] [echo] basedir is

Build failed in Jenkins: royale-compiler-integration-tests #774

See Changes: [joshtynjala] JSRoyaleDocEmitter: nocollapse is needed for constants too -- [...truncated 130.16 KB...] [jun

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

See

Build failed in Jenkins: royale-asjs_jsonly #1156

See Changes: [yishayjobs] Make sure mx combobox shows label -- [...truncated 1.17 MB...] [java] var events = require('events'); [

Build failed in Jenkins: royale-asjs_jsonly #1155

See Changes: [christofer.dutz] - Fixed the Apache headers of files I contributed years ago - Removed -- [...truncated 1.78 MB...] check-c

Jenkins build is back to normal : royale-compiler-integration-tests #761

See

Jenkins build is back to normal : royale-asjs #977

See

Build failed in Jenkins: royale-asjs #976

See Changes: -- [...truncated 1.87 MB...] [java] [java] public var ENTITIES:QName; [java] ^ [java] [java] c:\jenkins\workspac

Build failed in Jenkins: royale-asjs #975

See Changes: [carlosrovira] jewel-viewport: simplify some mehtods and solve a RTE with non [carlosrovira] jewel: add @royalesuppresspublicvarwarning -

Build failed in Jenkins: royale-asjs #974

See Changes: [yishayjobs] Set labels should not be nullified by missing data -- [...truncated 1.17 MB...] [java] [java] Mar 28, 2020 12:

Build failed in Jenkins: royale-compiler-integration-tests #760

See Changes: -- [...truncated 122.59 KB...] [junit] ^ [junit] [junit] Mar 28, 2020 11:46:07 AM com.google.javascript.jscomp

Jenkins build is back to normal : royale-compiler-integration-tests #747

See

Jenkins build is back to normal : royale-asjs_MXTests #825

See

Build failed in Jenkins: royale-compiler-integration-tests #746

See Changes: -- Started by upstream project "royale-asjs" build number 959 originally caused by: Started by upstream project "royale-asjs_

Build failed in Jenkins: royale-asjs_MXTests #824

See Changes: [carlosrovira] AMFCompressionException: required javadoc descriptions [carlosrovira] virtual-list: solve reassign dataprovider not refreshing the list with [carlosro

Jenkins build is back to normal : Verify_Royale_Config #827

See

Build failed in Jenkins: Verify_Royale_Config #826

See Changes: -- Started by upstream project "royale-asjs" build number 952 originally caused by: Started by upstream project "royale-asjs_jsonly" build

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

See

Build failed in Jenkins: royale-typedefs #455

See Changes: [carlosrovira] [maven-release-plugin] prepare branch @{releaseLabel} [carlosrovira] [maven-release-plugin] prepare for next development iteration [carlosrovira] reset ver

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

Release Step 005a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005a_If_Utils and run the following commands: git push 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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.

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

Release Step 005a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005a_If_Utils and run the following commands: git push 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.

Royale_Release_Step_005 - Build # 10 - Still Failing!

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

Royale_Release_Step_005 - Build # 9 - Still Failing!

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

Royale_Release_Step_005 - Build # 8 - Still Failing!

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

Royale_Release_Step_005 - Build # 7 - Still Failing!

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

Royale_Release_Step_005 - Build # 6 - Failure!

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

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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.

Release Step 003 Succeeded

>From the royale-compiler repo: 1. If you are releasing the utils jars (compiler-jburg-types and compiler-build-tools) - you have set in previous step for mentioned projects version ex. 1.1.0 not snapshot, run: ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7 -Dski

Release Step 002a Succeeded

Continue on to Release Step 003

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

Release Step 001a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following commands: (Push the local changes to develop) git push origin develop (Get the commit id of the last change (The output is considered COMMIT_ID)) git log

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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.

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

See

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-rc1 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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.

Royale_Release_Step_004 - Build # 13 - Failure!

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

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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.

Release Step 003 Succeeded

>From the royale-compiler repo: 1. If you are releasing the utils jars (compiler-jburg-types and compiler-build-tools) - you have set in previous step for mentioned projects version ex. 1.1.0 not snapshot, run: ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7 -Dski

Release Step 002a Succeeded

Continue on to Release Step 003

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

Release Step 001a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following commands: (Push the local changes to develop) git push origin develop (Get the commit id of the last change (The output is considered COMMIT_ID)) git log

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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.

Release Step 001a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following commands: (Push the local changes to develop) git push origin develop (Get the commit id of the last change (The output is considered COMMIT_ID)) git log

Royale_Release_Step_001a_If_Utils - Build # 12 - Still Failing!

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

Royale_Release_Step_001a_If_Utils - Build # 11 - Failure!

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

Release Step 001a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following commands: (Push the local changes to develop) git push origin develop (Get the commit id of the last change (The output is considered COMMIT_ID)) git log

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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.

Release Step 003 Succeeded

>From the royale-compiler repo: 1. If you are releasing the utils jars (compiler-jburg-types and compiler-build-tools) - you have set in previous step for mentioned projects version ex. 1.1.0 not snapshot, run: ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7 -Dski

Release Step 002a Succeeded

Continue on to Release Step 003

Royale_Release_Step_002a_If_Utils - Build # 12 - Failure!

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

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

Release Step 001a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following commands: (Push the local changes to develop) git push origin develop (Get the commit id of the last change (The output is considered COMMIT_ID)) git log

Royale_Release_Step_001a_If_Utils - Build # 8 - Failure!

Royale_Release_Step_001a_If_Utils - Build # 8 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001a_If_Utils/8/ 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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.

Build failed in Jenkins: royale-asjs_jsonly #1117

.com:8080/job/royale-asjs_jsonly/ws/mustella/tests/basicTests/bin/js-debug/index.html> [echo] script=<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/mustella/tests/basicTests/halo/scripts/ButtonTestScript.mxml> [echo] script=<http://apacheroya

Release Step 003 Succeeded

>From the royale-compiler repo: 1. If you are releasing the utils jars (compiler-jburg-types and compiler-build-tools) - you have set in previous step for mentioned projects version ex. 1.1.0 not snapshot, run: ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7 -Dski

Release Step 002a Succeeded

Continue on to Release Step 003

Royale_Release_Step_002a_If_Utils - Build # 10 - Still Failing!

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

Royale_Release_Step_002a_If_Utils - Build # 9 - Failure!

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

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

Build failed in Jenkins: royale-asjs_jsonly #1116

See Changes: [piotrzarzycki21] Adjust cleanup after moving TourDeJewel -- [...truncated 116.33 KB...] clean-tests: clean: [echo] swc

Build failed in Jenkins: royale-asjs_jsonly #1115

See Changes: [piotrzarzycki21] Adjust ant build after moving TourDeJewel to different folder -- Started by user Apache Royale Running as SY

Release Step 001a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following commands: (Push the local changes to develop) git push origin develop (Get the commit id of the last change (The output is considered COMMIT_ID)) git log

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.7 git push -u origin release/0.9.7 You will need your Apache/Github username and 2FA token.

<    5   6   7   8   9   10   11   12   13   14   >