Build failed in Jenkins: TourDeFlexMigration #531

See -- [...truncated 3.73 MB...] [mxmlc] using SWC: C:\jenkins\workspace\royale-asjs\frameworks\js\libs\BindingJS.swc [mxmlc] using SWC:

Build failed in Jenkins: royale-asjs_MXTests #513

See -- [...truncated 2.02 MB...] [mxmlc] using source file:

Royale_Release_Step_002 - Build # 12 - Failure!

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

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

See

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

Build failed in Jenkins: royale-asjs_MXTests #511

See Changes: [carlosrovira] BrowserOrientation bead to get device orientation (portrait or [carlosrovira] TDJ BrowserOrientation bead example of use [carlosrovira] fix

Build failed in Jenkins: royale-asjs_jsonly #2482

See Changes: [carlosrovira] jewel validator errortips: fix error tips location when controls change -- [...truncated 203.99 KB...]

Jenkins build is back to normal : TourDeFlexMigration #532

See

Build failed in Jenkins: royale-asjs_MXTests #514

See Changes: [carlosrovira] fix a regression in jewel item render that removes other content when -- [...truncated 2.02 MB...] [mxmlc]

Build failed in Jenkins: royale-asjs_jsonly #2484

See Changes: [carlosrovira] jewel-list: disabled styles [carlosrovira] jewel-themes: update with list disabled styles -- [...truncated

Build failed in Jenkins: royale-asjs_jsonly #2487

See Changes: [carlosrovira] remove some warnings [carlosrovira] decorate labels in itemrenders when using filter beads to show the --

Build failed in Jenkins: royale-compiler #732

See Changes: [joshtynjala] compiler: DynamicAccessNode resolves element type of Vector (closes #80) -- [...truncated 1.03 KB...]

Build failed in Jenkins: royale-compiler #731

See -- [...truncated 1.01 KB...] [royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml '"-Denv.ASJS_HOME=C:\Program Files

Build failed in Jenkins: royale-asjs #1967

See Changes: [carlosrovira] BrowserOrientation bead to get device orientation (portrait or [carlosrovira] TDJ BrowserOrientation bead example of use [carlosrovira] fix BrowserOrientation

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

See

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

See

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

See

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

See

Build failed in Jenkins: royale-asjs_MXTests #662

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #661

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Royale_Release_Step_002a_If_Utils - Build # 12 - Still Failing!

Royale_Release_Step_002a_If_Utils - Build # 12 - Still Failing: Check console output at http://apacheroyaleci.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.6-rc1 You will need your Apache/Github username and 2FA token.

Royale_Release_Step_002a_If_Utils - Build # 7 - Still Failing!

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

Release Step 003 Succeeded

1. Run ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6 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.xml Release_Step_003_Sign

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://apacheroyaleci.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 - Still Failing!

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

Royale_Release_Step_002a_If_Utils - Build # 6 - Still Failing!

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

Royale_Release_Step_002a_If_Utils - Build # 8 - Still Failing!

Royale_Release_Step_002a_If_Utils - Build # 8 - Still Failing: Check console output at http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002a_If_Utils/8/ 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.6-rc1 You will need your Apache/Github username and 2FA token.

Build failed in Jenkins: royale-asjs #2126

See -- [...truncated 2.11 MB...] [java] Writing file: js\out\mx\styles\IStyleManager2.js [java] Compiling file: mx.core.LayoutDirection [java]

Release Step 002a Succeeded

Continue on to Release Step 003

Build failed in Jenkins: royale-asjs_MXTests #656

See Changes: [greg.dove] Improvements to MouseEvent.createMouseEvent method: avoid try/catch in -- [...truncated 2.03 MB...] [mxmlc]

Build failed in Jenkins: royale-asjs_MXTests #657

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #658

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

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

See

Build failed in Jenkins: royale-asjs_MXTests #652

See Changes: [carlosrovira] jewel-wizard: support transitions navigating from a step to any other [carlosrovira] jewel-wizard: fixes when steps use bindings

Build failed in Jenkins: royale-asjs_MXTests #653

See -- [...truncated 2.11 MB...] [mxmlc]

Build failed in Jenkins: royale-asjs_MXTests #654

See -- [...truncated 2.04 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #664

See -- [...truncated 2.10 MB...] [mxmlc]

Build failed in Jenkins: royale-asjs_MXTests #663

See Changes: [carlosrovira] jewel-wizard: some fixes to make it work in IE11 partially -- [...truncated 2.05 MB...] [mxmlc] using source

Build failed in Jenkins: royale-asjs_MXTests #666

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

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

See

Build failed in Jenkins: royale-asjs_MXTests #665

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #667

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #672

See Changes: [harbs] Application is an IPopupHost but not an IUIBase -- [...truncated 2.04 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #673

See -- [...truncated 2.11 MB...] [mxmlc]

Build failed in Jenkins: royale-asjs_MXTests #669

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #668

See Changes: [yishayjobs] Make sure we don't remove a loader that doesn't exist -- [...truncated 2.05 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #676

See -- [...truncated 2.05 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #678

See -- [...truncated 2.11 MB...] [mxmlc]

Build failed in Jenkins: royale-asjs_MXTests #677

See Changes: [carlosrovira] jewel-slider: fix remove cast not needed [carlosrovira] jewel-tabbar: global improvements to the component. TabBar now selects [carlosrovira]

Build failed in Jenkins: royale-asjs_MXTests #683

See Changes: [carlosrovira] jewel-itemrenderer: fix listener to use positioner instead of element so [carlosrovira] core-HTMLElementWrapper: make getActualDispatcher_ function use

Build failed in Jenkins: royale-asjs_MXTests #685

See -- [...truncated 2.05 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #684

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #680

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #679

See -- [...truncated 2.05 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #686

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #681

See Changes: [carlosrovira] jewel-itemrenders: refactor align property to a new interface and remove -- [...truncated 2.03 MB...]

Build failed in Jenkins: royale-asjs_MXTests #670

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #671

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

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

Build failed in Jenkins: Royale_ASDoc_Example #1875

See -- [...truncated 301.50 KB...] [mxmlc] C:/Program Files

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

See

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

Release Step 002a Succeeded

Continue on to Release Step 003

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.6 git push -u origin release/0.9.6 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_001 - Build # 61 - Failure!

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

Release Step 003 Succeeded

1. If you are releasing the utils jars (compiler-jburg-types and compiler-build-tools), Run: ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6 Otherwise, Run: ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6 This will download the artifacts then

Release Step 005a Succeeded

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

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

Release Step 007 Succeeded

1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.6 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.xml Release_Step_007_Sign

Build failed in Jenkins: royale-asjs_MXTests #758

See -- [...truncated 2.04 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #757

See -- [...truncated 2.03 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #772

See -- [...truncated 2.04 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #773

See -- [...truncated 2.11 MB...] [mxmlc]

Build failed in Jenkins: royale-asjs_MXTests #770

See -- [...truncated 2.04 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #769

See -- [...truncated 2.04 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #774

See -- [...truncated 2.04 MB...] [mxmlc] using source file:

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

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

Release Step 003 Succeeded

1. If you are releasing the utils jars (compiler-jburg-types and compiler-build-tools), Run: ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6 Otherwise, Run: ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6 This will download the artifacts then

Release Step 007 Succeeded

1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.6 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.xml Release_Step_007_Sign

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.6 git push -u origin release/0.9.6 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 005a Succeeded

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

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

Build failed in Jenkins: royale-asjs_MXTests #817

See -- [...truncated 2.11 MB...] [mxmlc] using source file:

Release Step 011 Succeeded

>From the royale-asjs repo: 1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.6 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.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.6-rc1 You will need your Apache/Github username and 2FA token.

Release Step 009 Succeeded

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

Build failed in Jenkins: royale-asjs_MXTests #807

See -- [...truncated 2.11 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #806

See -- [...truncated 2.09 MB...] [mxmlc] using source file:

Release Step 005a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005a and run the following commands: git push 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), Run: ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6 Otherwise, Run: ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6 This will

Release Step 011 Succeeded

>From the royale-asjs repo: 1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.6 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.xml

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