Release Step 001 Succeeded

[apacheroyaleci]

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 #1251

[apacheroyaleci]

See 

Build failed in Jenkins: royale-asjs_jsonly #1250

[apacheroyaleci]

See 


Changes:


--
[...truncated 1.17 MB...]
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:84: WARNING - name module is not defined in the 
externs.
 [java] module.exports = readline;
 [java] ^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:24: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:48: WARNING - name module is not defined in the 
externs.
 [java] module.exports = repl;
 [java] ^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [stream]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [stream]:254: WARNING - name module is not defined in the 
externs.
 [java] module.exports = stream;
 [java] ^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [string_decoder]:52: WARNING - name module is not defined 
in the externs.
 [java] module.exports = StringDecoder;
 [java] ^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var crypto = require('crypto');
 [java]  ^^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:24: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:25: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var net = require('net');
 [java]   ^^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:26: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:148: WARNING - name module is not defined in the 
externs.
 [java] module.exports = tls;
 [java] ^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tty]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var net = require('net');
 [java]   ^^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tty]:75: WARNING - name module is not defined in the 
externs.
 [java] module.exports = tty;
 [java] ^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [url]:57: WARNING - name module is not defined in the 
externs.
 [java] module.exports = url;
 [java] ^^
 [java] 
 [java] Apr 12, 2020 4:19:10 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [util]:112: WARNING - name module is not defined in the 
externs.
 [java] module.exports = util;
 

Release Step 001 Succeeded

[apacheroyaleci]

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 # 32 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_001 - Build # 32 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001/32/
 to view the results.

Royale_Release_Step_001 - Build # 31 - Failure!

[apacheroyaleci]

Royale_Release_Step_001 - Build # 31 - Failure:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001/31/
 to view the results.

Re: Royale Releases

[Alex Harui]

I have seen the CI server produce a valid set of bits for compiler-build-tools 
1.2.0.  Yishay, please find time to try out the 
Royale_Compiler_Build_Tools_Release_Steps_001 and others.

I will be testing out the Royale_Release_Steps shortly.

-Alex

On 4/9/20, 10:08 PM, "Alex Harui"  wrote:

Hi Carlos,

I'm still back on getting compiler-build-tools 1.2.0 released.  What was 
posted on dist for compiler-build-tools was not complete, and I am trying to 
get the CI server to do it using JGit because that is more secure, but had to 
fix a JGit bug first.  I hope the first 7 steps of the actual Royale release go 
quickly once we get to that point.

-Alex

On 4/9/20, 12:28 AM, "Carlos Rovira"  wrote:

 Hi Alex,

don't understand the problem. Chris and I was able to reach step 7. The 
big
problem is there with compiler generating classes with lines in 
different
orders depending on OS (and probably JDK vendor). I think solving that 
will
make you move from the problematic point. But don't understand that you
have problems in steps 1 to 6.



El jue., 9 abr. 2020 a las 9:21, Alex Harui ()
escribió:

> FWIW, I saw Royale_Compiler_Build_Tools_Release_Step_002 work.  I'm 
done
> for tonight.  If anyone is bored, they can try to get the
> Royale_Compiler_Build_Tools_Release_Step_002_Sign target to work in
> compiler-build-tools/releasesteps.xml by renaming
> Royale_Compiler_Build_Tools_Release_Step_003_Sign and fixing up the 
paths.
> Otherwise I will start there tomorrow evening.
>
> -Alex
>
> On 4/8/20, 9:03 PM, "Yishay Weiss"  wrote:
>
> >sounds good :)
>
> Hi Carlos,
>
> This sounds like a good plan to me too. Alex and I will do our 
best to
> get 0.9.7 out in April. Harbs will be in charge of releasing 0.9.8 in 
May,
> and you will be in charge of releasing 0.9.9 in June.
>
> Are we still in agreement on that?
>
> Thanks,
> Yishay
>
> From: Carlos Rovira
> Sent: Thursday, April 2, 2020 6:47 PM
> To: Apache Royale Development
> Subject: Re: Royale Releases
>
> Hi Harbs,
>
> sounds good :)
>
> As well, I expect I can do 0.9.9 in June from my local machine 
with the
> process we already exposed too :)
>
> Thanks
>
> Carlos
>
>
> El jue., 2 abr. 2020 a las 15:50, Harbs ()
> escribió:
>
> > I spent over an hour with Alex on the Zoom last night trying to
> understand
> > all the different technical points.
> >
> > One point which became clear to me last night is that Ant and 
Maven
> are
> > distributed differently so there are points of failure that one 
has
> which
> > the other doesn’t.
> >
> > I also want to stress that Alex is actually a fan of Maven.
> >
> > We all want the Maven release to be easier, but somehow this is 
being
> > conflated with bashing Ant.
> >
> > As far as I’m concerned, the steps forward are:
> >
> > 1. Yishay should work on releasing 0.9.7.
> > 2. He will hopefully be supported by Alex, Chris and Carlos to 
make
> it as
> > smooth as possible.
> > 3. When he’s done, I plan on sitting down with him to discuss 
his
> > experience.
> > 4. I plan on working on releasing 0.9.8 sometime in May.
> > 5. While I’m working on 0.9.8 I expect to use Yishay’s 
experiences
> as well
> > as my own to try and understand as much about the process as I 
can
> (Ant,
> > Maven and NPM too).
> > 6. I hope to work with anyone who wants to help to improve the
> process as
> > much as I can.
> >
> > Sounds OK?
> >
> > Harbs
> >
> > > On Apr 2, 2020, at 4:38 PM, Christofer Dutz <
> christofer.d...@c-ware.de>
> > wrote:
> > >
> > > Hi folks,
> > >
> > > I would say we have coverage for both maven ant equally as 
we're
> > building the same code.
> > >
> > > However we are missing the important assertions. It's not 
that the
> Ant
> > build is running some tests Maven isn't.
> > > It's just that the settings for Ant seem to be different than 
for
   

Royale Compiler Build Tools Release Step 004 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt and change directory to:
C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_004\dist\dev
1. Run svn --username= commit -m "Compiler Build Tools 1.2.0 
rc 2"
This will upload the signed artifacts to dist.apache.org.

You will need your svn password.

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 9 - Failure!

[apacheroyaleci]

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 9 - Failure:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_004/9/
 to view the results.

Royale Compiler Build Tools Release Step 004 Succeeded

[apacheroyaleci]

>From the svn repo
1. Run svn add .
2. Run svn commit -m "Compiler Build Tools 1.2.0 rc 2
This will upload the signed artifacts to dist.apache.org.

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 7 - Still Failing!

[apacheroyaleci]

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 7 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_004/7/
 to view the results.

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 6 - Still Failing!

[apacheroyaleci]

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 6 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_004/6/
 to view the results.

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 5 - Still Failing!

[apacheroyaleci]

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 5 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_004/5/
 to view the results.

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 4 - Still Failing!

[apacheroyaleci]

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 4 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_004/4/
 to view the results.

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 3 - Still Failing!

[apacheroyaleci]

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 3 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_004/3/
 to view the results.

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 2 - Still Failing!

[apacheroyaleci]

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 2 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_004/2/
 to view the results.

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 1 - Failure!

[apacheroyaleci]

Royale_Compiler_Build_Tools_Release_Step_004 - Build # 1 - Failure:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_004/1/
 to view the results.