Royale_Release_Step_002 - Build # 14 - Failure!

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

Royale_Release_Step_002 - Build # 16 - Failure!

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

Royale_Release_Step_002 - Build # 12 - Still Failing!

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

Royale_Release_Step_002 - Build # 17 - Still Failing!

Royale_Release_Step_002 - Build # 17 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/17/ 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 #1097

See Changes: [greg.dove] Adding some small changes to support porting. MX Fade is a placeholder. -- Started by an SCM change Running as

Royale_Release_Step_002 - Build # 9 - Still Failing!

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

Royale_Release_Step_002 - Build # 10 - Still Failing!

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

Build failed in Jenkins: royale-asjs_jsonly #1096

See Changes: [greg.dove] quick sweep through manualtests [greg.dove] Sidestepping a few issues with swf html-template stuff to get past upper

Re: Memory on the CI server

Hi all, I had a hunch and had a look at windows virtual memory settings and indeed virtual memory was turned off ... turning it on seems to help. So keep your fingers crossed ;-) Chris Am 23.03.20, 10:56 schrieb "Christofer Dutz" : Hi all, as you can see we’re having issues with

Royale_Release_Step_002 - Build # 18 - Still Failing!

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

Memory on the CI server

Hi all, as you can see we’re having issues with the release steps … unfortunately we’ve run into one we don’t know how to handle. It seems the CI server has so little memory that Windows is killing the Java process at random times. You can usually see this in form: [DEBUG]

Royale_Release_Step_002 - Build # 19 - Still Failing!

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

Royale_Release_Step_003 - Build # 2 - Still Failing!

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

Findings and Changed to the release steps and the CI configuration.

Here come some things we noticed while working on the release steps: * All Jenkins release emails were discarded by my email server, I had to use ponymail to read them Observations: * Step 001 * How can you push without providing credentials on the CI server? It seems that

Royale_Release_Step_001 - Build # 13 - Failure!

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

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.

Royale_Release_Step_003 - Build # 3 - Still Failing!

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

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

Royale_Release_Step_001 - Build # 15 - Still Failing!

Royale_Release_Step_001 - Build # 15 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001/15/ 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.

Royale_Release_Step_003 - Build # 1 - Failure!

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

Royale_Release_Step_001 - Build # 14 - Still Failing!

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

Build failed in Jenkins: royale-asjs_jsonly #1099

See Changes: -- Started by upstream project "royale-typedefs" build number 438 originally caused by: Started by upstream project "royale-compiler"

Re: Maven Distribution SDK fixed and working for IDEs

Hi Guys, I just checked Maven Distribution with Moonshine and I was able to build Jewel Hello World and TourDeJewel. :) Thanks, Piotr niedz., 22 mar 2020 o 20:58 Carlos Rovira napisał(a): > Hi Piotr, > > nothing happens or log is printed in the console, is like if I didn't push > the menu

Re: Maven Distribution SDK fixed and working for IDEs

Very cool Piotr! seems we finally has Maven distribution sdk working! :) El lun., 23 mar. 2020 a las 14:44, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Hi Guys, > > I just checked Maven Distribution with Moonshine and I was able to build > Jewel Hello World and TourDeJewel. :) > >

Build failed in Jenkins: royale-asjs_jsonly #1098

See Changes: -- Started by upstream project "royale-typedefs" build number 437 originally caused by: Started by upstream project "royale-compiler"

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

Re: Ways for dumping the effective-configuration of the compiler?

Yes, the dump-config compiler option is exactly what you are looking for. Set it to a file path, and it will output the full configuration used in the current session. -- Josh Tynjala Bowler Hat LLC On Sat, Mar 21, 2020 at 7:50 AM Christofer Dutz wrote: > Hi all, > >

Re: Maven Distribution SDK fixed and working for IDEs

Next is reproduce your problem with Moonshine. ;) pon., 23 mar 2020 o 15:02 Carlos Rovira napisał(a): > Very cool Piotr! > seems we finally has Maven distribution sdk working! :) > > El lun., 23 mar. 2020 a las 14:44, Piotr Zarzycki (< > piotrzarzyck...@gmail.com>) escribió: > > > Hi Guys, > >

Re: Maven Distribution SDK fixed and working for IDEs

Yeah, hope someone on your team could know where we can start looking :) thanks! Carlos El lun., 23 mar. 2020 a las 15:04, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Next is reproduce your problem with Moonshine. ;) > > pon., 23 mar 2020 o 15:02 Carlos Rovira > napisał(a): > > >

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 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.

Royale_Release_Step_001 - Build # 19 - Still Failing!

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

Royale_Release_Step_002a_If_Utils - Build # 1 - Failure!

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

Royale_Release_Step_001 - Build # 18 - Failure!

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

Re: Findings and Changed to the release steps and the CI configuration.

On 3/23/20, 6:01 AM, "Christofer Dutz" wrote: Here come some things we noticed while working on the release steps: * All Jenkins release emails were discarded by my email server, I had to use ponymail to read them Observations: * Step 001

Build failed in Jenkins: royale-asjs_jsonly #1100

See Changes: -- Started by upstream project "royale-typedefs" build number 439 originally caused by: Started by upstream project "royale-compiler"

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.

Royale_Release_Step_002a_If_Utils - Build # 2 - Still Failing!

Royale_Release_Step_002a_If_Utils - Build # 2 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002a_If_Utils/2/ 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.

Royale_Release_Step_002a_If_Utils - Build # 3 - Still Failing!

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

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

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.

Re: Findings and Changed to the release steps and the CI configuration.

Hi Alex, regarding the credentials ... I was just surprised that Carlos didn't have to provide any credentials to push on the CI machine itself. Are you saying the RemoteDesktop thing is doing some weird magic in forwarding credentials from the RDP client to the Server? Just asking out of

Re: Findings and Changed to the release steps and the CI configuration.

On 3/23/20, 9:31 AM, "Christofer Dutz" wrote: Hi Alex, regarding the credentials ... I was just surprised that Carlos didn't have to provide any credentials to push on the CI machine itself. Are you saying the RemoteDesktop thing is doing some weird magic in forwarding

Re: Memory on the CI server

On 3/23/20, 3:11 AM, "Christofer Dutz" wrote: Hi all, I had a hunch and had a look at windows virtual memory settings and indeed virtual memory was turned off ... turning it on seems to help. So keep your fingers crossed ;-) What setting did you change? Just in case we

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.

Re: Findings and Changed to the release steps and the CI configuration.

On 3/23/20, 11:32 AM, "Christofer Dutz" wrote: Hi Alex, I did check and I didn't directly find any .git .ssh or whatsoever directories ... do you have an Idea where that would be saved on windows? The commits are authorized by Carlos and it's his RDP connection, that's why

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

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

Re: Findings and Changed to the release steps and the CI configuration.

Hi Alex, I did check and I didn't directly find any .git .ssh or whatsoever directories ... do you have an Idea where that would be saved on windows? The commits are authorized by Carlos and it's his RDP connection, that's why I'm asking if there is any RDP magic going on. I didn't see him

Release Step 002a Succeeded

Continue on to Release Step 003

Re: Findings and Changed to the release steps and the CI configuration.

Hi, we just saw that windows stores a personal access token in Windows Crendetials, so the RM is responsible to remove it when finish all the operations. El lun., 23 mar. 2020 a las 19:44, Alex Harui () escribió: > > > On 3/23/20, 11:32 AM, "Christofer Dutz" > wrote: > > Hi Alex, > >

Re: Findings and Changed to the release steps and the CI configuration.

Ok .. so we found out what's going on. As soon as you push the first time, a popup opens and asks you for your credentials and 2fa. If you enter that stuff, windows automatically stores that in it's password manager. So the release manager will have to make sure the credentials are cleared

Re: Findings and Changed to the release steps and the CI configuration.

Another thing we just discovered. The current setup seems to mess up the branches: - 001 creates the branch and updates develop rel = 0.9.7-SNAPSHOT, develop = 0.9.8-SNAPSHOT - 001b updates DEVELOP and not the release branch - 002 pushes develop to the release-branch hereby bumping the release

Re: Findings and Changed to the release steps and the CI configuration.

I do understand that Windows may store credentials, but how it can store personal token? Personal token is being typed every time. I do imagine than someone could Tyle his login and personal token as a mistake, but I'm sure I didn't do such mistake. On Mon, Mar 23, 2020, 8:11 PM Carlos Rovira

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 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.

Royale_Release_Step_001 - Build # 22 - Failure!

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

Build failed in Jenkins: royale-compiler #274

See Changes: [christofer.dutz] - Made the utils reporducible builds too - Bumped the apache parent [carlosrovira] [maven-release-plugin] prepare branch @{releaseLabel}

Release Step 002a Succeeded

Continue on to Release Step 003

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

Re: Ways for dumping the effective-configuration of the compiler?

No objections from me of someone wants to add this (and other compiler options) as top-level options of the plugin. As a workaround, you should be able to add it under addtionalCompllerOptions. HTH, -Alex On 3/23/20, 1:29 PM, "Christofer Dutz" wrote: Hi Josh, perhaps it would

Re: Ways for dumping the effective-configuration of the compiler?

Hi Josh, perhaps it would make sense to enable this in maven and in and so we can compare and more easily diagnose differences? Chris Am 23.03.20, 16:27 schrieb "Josh Tynjala" : Yes, the dump-config compiler option is exactly what you are looking for. Set it to a file path, and it

Re: Findings and Changed to the release steps and the CI configuration.

Re: credentials: Does that mean that the git config is set to use the credential manager? If so, maybe that should be turned off? When I did the release, I had to type my password many times. Not sure what Piotr's experience was. Re: Branches:I don't remember what the steps are. I

Re: Ways for dumping the effective-configuration of the compiler?

Yeah, makes sense to me. -- Josh Tynjala Bowler Hat LLC On Mon, Mar 23, 2020 at 1:29 PM Christofer Dutz wrote: > Hi Josh, > > perhaps it would make sense to enable this in maven and in and so we can > compare and more easily diagnose differences? > > Chris > > Am

Re: Findings and Changed to the release steps and the CI configuration.

Hi Alex, sorry for the confusion ,... I meant the 1a ... the one if you build the utils too. And regarding the credentials: Something must have changes as I have never seen that gui thingy pop up before and as soon as you login, it saves them in the password manager thingy of windows. It is

Re: Findings and Changed to the release steps and the CI configuration.

On 3/23/20, 2:29 PM, "Christofer Dutz" wrote: Hi Alex, sorry for the confusion ,... I meant the 1a ... the one if you build the utils too. And regarding the credentials: Something must have changes as I have never seen that gui thingy pop up before and as soon as you

Build failed in Jenkins: royale-typedefs #441

See Changes: [christofer.dutz] - Adjusted the releasesteps.xml files to the new server name and -- Started by an SCM change Running as SYSTEM

Build failed in Jenkins: royale-asjs_jsonly #1103

See Changes: -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on agent1 in workspace

Build failed in Jenkins: royale-typedefs #442

See Changes: -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on agent1 in workspace

Build failed in Jenkins: royale-typedefs #440

See Changes: [christofer.dutz] - Adjusted the git plugin settings to the same ones in the compiler -- Started by an SCM change Running as

Build failed in Jenkins: royale-asjs_jsonly #1101

See Changes: [christofer.dutz] - Adjusted the git plugin settings to the same ones in the compiler [christofer.dutz] - Adjusted the releasesteps.xml files to the new server name

Build failed in Jenkins: royale-asjs_jsonly #1102

See Changes: [carlosrovira] SetFocus: fix _strand. Warning this bead is still not working as -- Started by an SCM change Running as SYSTEM