Build failed in Jenkins: royale-asjs_jsonly #3058

See -- [...truncated 2.12 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 Re

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 Re

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.

Release Step 008 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_008 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 007 Succeeded

>From the royale-typedefs repo: 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.xm

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

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.

Royale_Release_Step_002 - Build # 34 - Failure!

Royale_Release_Step_002 - Build # 34 - Failure: Check console output at http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/34/ 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: git push 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.

Embedded Assets (was Re: AIR and Royale)

Regarding embedded assets in Royale: There is no embedded asset support at this time because it is not obvious to me it will be worth it. We need a volunteer to devise a strategy that works and implement it. In Flex/Flash, my understanding is that folks embedded assets to save on server reque

Re: AIR and Royale

Hi Dave, If I understand from those page not only companies can be listed but also individuals - Am I correct? Thanks, Piotr On Wed, Jun 5, 2019, 5:53 PM Dave Fisher wrote: > This is fine as long as it is done in a vendor neutral manner with clear > instruction on how to ask to be added. Also

Re: AIR and Royale

This is fine as long as it is done in a vendor neutral manner with clear instruction on how to ask to be added. Also, there should be clarity that no vendor is “endorsed”. Examples: https://www.openoffice.org/bizdev/consultants.html https://wiki.apache.org/cassandra/ThirdPartySupport https://cwi

Re: Compiler Build Failing on Windows

As discussed recently on some other thread, environment variables matter and the documentation may not be up-to-date. We build both SWF&JS or JS-Only packages based on environment variables. Either you have the Adobe stuff for SWF and environment variables pointing to them or not. If you only

Re: Compiler Build Failing on Windows

Carlos, I think it is ANT build. Yesterday I tried locally and had the same issue. I was going to report it here as well. Thanks, Piotr śr., 5 cze 2019 o 16:00 Carlos Rovira napisał(a): > Hi > > can you provide more info about what method are you using to build? ANT? > Maven? and provide the s

Re: AIR and Royale

Hi, I think one thing we can do is create some page on website where we can list companies that can give services around Royale (consultancy, development, etc...). I think that could be good for Royale. Don't know if that is a problem with Apache. Only giving a list of posible companies should be

Re: AIR and Royale

Yes, me :-) I'm pushing Royale internally, I think it has a lot of promise - although I still do find it a little frustrating at times internally! In terms of what support you can give, the sorts of things you're already doing are great, but yes it might mean we lean a little more on this maili

Re: Compiler Build Failing on Windows

Hi can you provide more info about what method are you using to build? ANT? Maven? and provide the steps you use, also if you have set up some env vars? thanks El mié., 5 jun. 2019 a las 12:43, Shiffy () escribió: > I’m trying to build the compiler on Windows and it keeps failing in the > tests.

Build failed in Jenkins: royale-asjs_jsonly #3056

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

Re: Build failed in Jenkins: royale-asjs_jsonly #3027

What we actually are doing with Selenium? What important they are doing ? wt., 4 cze 2019 o 15:07 Piotr Zarzycki napisał(a): > I doubt that - how it may be connected to his work. I checked Jenkins > configuration and I don't see anything new. > > On Tue, Jun 4, 2019, 3:04 PM Carlos Rovira > wro

Compiler Build Failing on Windows

I’m trying to build the compiler on Windows and it keeps failing in the tests. Here’s one example of a failed test that I’m getting: https://pastebin.com/TpQynEmF The test results are hard to read, but one difference I see between the expected results and the actual results is that it expects ex