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

[Christofer Dutz]

Hi all,

yes, now I am certain that updating the other 9 places to set the time-zone of 
the SimpleDateFormat will help.

Here's a great article on exactly this topic:
https://www.codeproject.com/Tips/1190426/When-Parsing-Formatting-Dates-in-Java-Make-Sure-Yo

And now I'm hopefully really gonna call it a night.

Chris

Am 24.03.20, 21:50 schrieb "Carlos Rovira" :

Thanks for the huge effort Chris,
I think it's being tough these days.
Let's get rest and see if tomorrow we can get over step 7 :)

Carlos


El mar., 24 mar. 2020 a las 21:37, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:

> HI Alex,
>
> I think we're getting closer ...
>
> The maven reproducible build mechanism and the release plugin all work
> with a standard time format:
>
> 
2020-03-24T19:00:04Z
> The format is:
> -MM-dd'T'HH:mm:ss'Z'
> So it actually doesn't contain time-zone information.
>
> Also did I do a little more searching in the compiler code and sort of
> identical code was found in 9 places.
>
> I will try tomorrow if it helps setting the time-zone to UTC for every
> place where the getSWFMetadataDate and getSWFMetadataDateFormat are used 
in
> a SimpleDateFormat. I would assume if no timezone information is provided,
> the SimpleDateFormat assumes it's the VMs default one. Now I could imagine
> that if you call getTime this sort of is influenced by this.
>
> Now after a second full day of working on this I just want to go to bed 
;-)
>
> Good night to you all,
>
> Chris
>
>
>
> Am 24.03.20, 20:57 schrieb "Alex Harui" :
>
> Ok, I think I have a better idea of what code you are referring to.
>
> I can look into it with more detail later, but I recall thinking that
> there could be a problem during the weeks the world is not synced on
> "daylight savings time".
>
> Over on the US west coast, I was typing in dates like: "02/25/20 14:51
> -0800".  The CI server is somewhere in the US, IIRC.  And IIRC, I had to
> use ""02/25/20 14:51 -0700" instead (or maybe the other way around) during
> the period of time the US was changing from "PST" to "PDT" or back.
>
> So try adding or subtracting a zone from the date you are feeding into
> Jenkins and see what happens.
>
> HTH,
> -Alex
>
>
> On 3/24/20, 12:34 PM, "Christofer Dutz" 
> wrote:
>
> Hi Alex,
>
> Well it seems as if the "mod" attribute in the catalog.xml is
> generated from the zipfile entry
> xmlWriter.writeAttribute(ATTR_MOD,
> String.valueOf(file.getLastModified()));
>
> And in the SWCWriter there's this code that cuts off the timezone,
> you even wrote a comment on it
>
> if (metadataDate != null)
> {
> // TODO: Perhaps parsing without modification and then
> serializing with a default timezone is the more solid approach.
> // strip off timezone.  Zip format doesn't store
> timezone
> // and the goal is to have the same date and time
> regardless
> // of which timezone the build machine is using.
> int c = metadataDate.lastIndexOf(' ');
> if(c != -1) {
> metadataDate = metadataDate.substring(0, c);
> }
> c = metadataFormat.lastIndexOf(' ');
> if(c != -1) {
> metadataFormat = metadataFormat.substring(0, c);
> }
> try {
> SimpleDateFormat sdf = new
> SimpleDateFormat(metadataFormat);
> sdf.setTimeZone(TimeZone.getTimeZone("UTC"));
> fileDate =
> sdf.parse(metadataDate).getTime();
> } catch (ParseException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> } catch (IllegalArgumentException e1) {
> e1.printStackTrace();
> }
> }
>
> So in general it doesn’t matter what timezone is in the string
> input, it was cut off anyway.
> I added the line:
>
> sdf.setTimeZone(TimeZone.getTimeZone("UTC"));
>
> But it seems I still have the same issue with the con
>
> re-inspecting the code I noticed, it's probably just the timestamp
> used in the zip file metadata ... not that used in the catalog.xml.
> Will have 

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

[Carlos Rovira]

Thanks for the huge effort Chris,
I think it's being tough these days.
Let's get rest and see if tomorrow we can get over step 7 :)

Carlos


El mar., 24 mar. 2020 a las 21:37, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:

> HI Alex,
>
> I think we're getting closer ...
>
> The maven reproducible build mechanism and the release plugin all work
> with a standard time format:
>
> 2020-03-24T19:00:04Z
> The format is:
> -MM-dd'T'HH:mm:ss'Z'
> So it actually doesn't contain time-zone information.
>
> Also did I do a little more searching in the compiler code and sort of
> identical code was found in 9 places.
>
> I will try tomorrow if it helps setting the time-zone to UTC for every
> place where the getSWFMetadataDate and getSWFMetadataDateFormat are used in
> a SimpleDateFormat. I would assume if no timezone information is provided,
> the SimpleDateFormat assumes it's the VMs default one. Now I could imagine
> that if you call getTime this sort of is influenced by this.
>
> Now after a second full day of working on this I just want to go to bed ;-)
>
> Good night to you all,
>
> Chris
>
>
>
> Am 24.03.20, 20:57 schrieb "Alex Harui" :
>
> Ok, I think I have a better idea of what code you are referring to.
>
> I can look into it with more detail later, but I recall thinking that
> there could be a problem during the weeks the world is not synced on
> "daylight savings time".
>
> Over on the US west coast, I was typing in dates like: "02/25/20 14:51
> -0800".  The CI server is somewhere in the US, IIRC.  And IIRC, I had to
> use ""02/25/20 14:51 -0700" instead (or maybe the other way around) during
> the period of time the US was changing from "PST" to "PDT" or back.
>
> So try adding or subtracting a zone from the date you are feeding into
> Jenkins and see what happens.
>
> HTH,
> -Alex
>
>
> On 3/24/20, 12:34 PM, "Christofer Dutz" 
> wrote:
>
> Hi Alex,
>
> Well it seems as if the "mod" attribute in the catalog.xml is
> generated from the zipfile entry
> xmlWriter.writeAttribute(ATTR_MOD,
> String.valueOf(file.getLastModified()));
>
> And in the SWCWriter there's this code that cuts off the timezone,
> you even wrote a comment on it
>
> if (metadataDate != null)
> {
> // TODO: Perhaps parsing without modification and then
> serializing with a default timezone is the more solid approach.
> // strip off timezone.  Zip format doesn't store
> timezone
> // and the goal is to have the same date and time
> regardless
> // of which timezone the build machine is using.
> int c = metadataDate.lastIndexOf(' ');
> if(c != -1) {
> metadataDate = metadataDate.substring(0, c);
> }
> c = metadataFormat.lastIndexOf(' ');
> if(c != -1) {
> metadataFormat = metadataFormat.substring(0, c);
> }
> try {
> SimpleDateFormat sdf = new
> SimpleDateFormat(metadataFormat);
> sdf.setTimeZone(TimeZone.getTimeZone("UTC"));
> fileDate =
> sdf.parse(metadataDate).getTime();
> } catch (ParseException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> } catch (IllegalArgumentException e1) {
> e1.printStackTrace();
> }
> }
>
> So in general it doesn’t matter what timezone is in the string
> input, it was cut off anyway.
> I added the line:
>
> sdf.setTimeZone(TimeZone.getTimeZone("UTC"));
>
> But it seems I still have the same issue with the con
>
> re-inspecting the code I noticed, it's probably just the timestamp
> used in the zip file metadata ... not that used in the catalog.xml.
> Will have another look at why I'm having this 36 offset. ... I
> just did a little math and it's exactly one hour off ...
>
> The difference of all tags is:
> 360 milliseconds, which is exactly one hour. So the timestamps
> on the CI server are exactly one hour ahead of the builds we do in Europe.
>
> This is currently the last issue preventing us from finishing the
> steps for the typedefs.
>
> Do you have any idea? ... Anything with the US being Summer-Time
> and us still on Winter-Time?
>
> Perhaps you could try executing this command in the typedefs:
>
> ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7
> -DskipTests=true
>
> Would be interesting if this succeeds for you.
>
> Well actually the library.swf in the swc seems to have a "net"
> 

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

[Alex Harui]

Ok, I think I have a better idea of what code you are referring to.

I can look into it with more detail later, but I recall thinking that there 
could be a problem during the weeks the world is not synced on "daylight 
savings time".

Over on the US west coast, I was typing in dates like: "02/25/20 14:51 -0800".  
The CI server is somewhere in the US, IIRC.  And IIRC, I had to use ""02/25/20 
14:51 -0700" instead (or maybe the other way around) during the period of time 
the US was changing from "PST" to "PDT" or back.

So try adding or subtracting a zone from the date you are feeding into Jenkins 
and see what happens.

HTH,
-Alex


On 3/24/20, 12:34 PM, "Christofer Dutz"  wrote:

Hi Alex,

Well it seems as if the "mod" attribute in the catalog.xml is generated 
from the zipfile entry 
xmlWriter.writeAttribute(ATTR_MOD, 
String.valueOf(file.getLastModified()));

And in the SWCWriter there's this code that cuts off the timezone, you even 
wrote a comment on it

if (metadataDate != null)
{
// TODO: Perhaps parsing without modification and then 
serializing with a default timezone is the more solid approach.
// strip off timezone.  Zip format doesn't store timezone
// and the goal is to have the same date and time regardless
// of which timezone the build machine is using.
int c = metadataDate.lastIndexOf(' ');
if(c != -1) {
metadataDate = metadataDate.substring(0, c);
}
c = metadataFormat.lastIndexOf(' ');
if(c != -1) {
metadataFormat = metadataFormat.substring(0, c);
}
try {
SimpleDateFormat sdf = new 
SimpleDateFormat(metadataFormat);
sdf.setTimeZone(TimeZone.getTimeZone("UTC"));
fileDate = sdf.parse(metadataDate).getTime();
} catch (ParseException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (IllegalArgumentException e1) {
e1.printStackTrace();
}
}

So in general it doesn’t matter what timezone is in the string input, it 
was cut off anyway.
I added the line:

sdf.setTimeZone(TimeZone.getTimeZone("UTC"));

But it seems I still have the same issue with the con

re-inspecting the code I noticed, it's probably just the timestamp used in 
the zip file metadata ... not that used in the catalog.xml.
Will have another look at why I'm having this 36 offset. ... I just did a 
little math and it's exactly one hour off ... 

The difference of all tags is: 
360 milliseconds, which is exactly one hour. So the timestamps on the 
CI server are exactly one hour ahead of the builds we do in Europe.

This is currently the last issue preventing us from finishing the steps for 
the typedefs.

Do you have any idea? ... Anything with the US being Summer-Time and us 
still on Winter-Time?

Perhaps you could try executing this command in the typedefs:

ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7 
-DskipTests=true

Would be interesting if this succeeds for you. 

Well actually the library.swf in the swc seems to have a "net" Object in 
the locally built version and a "http" Object instead on the CI Server-Version.

Currently I'm trying to fix the timestamp version and address the other 
problem after that's solved.

Chris



Am 24.03.20, 20:08 schrieb "Alex Harui" :

Good to see progress.

Re timestamps:  I’m not quite sure what you are running into.

The builds were taking a time that included a timezone.  Here's some 
output from recent builds:

 [java] -metadata.date=02/25/20 14:51 +
 [java] -metadata.dateFormat=MM/dd/yy HH:mm Z

So I'm not sure how the timezone got lost on what you are seeing.  The 
RM was supposed to type in something like "02/25/20 14:51 +".  The prompts 
on the Jenkins job were supposed to hint that.

HTH,
-Alex

On 3/24/20, 7:47 AM, "Carlos Rovira"  wrote:

Hi Alex,
I finally said Chris to try it myself, so going with that now :)

El mar., 24 mar. 2020 a las 15:40, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:

> Hi Alex,
>
> I added a call to set a fixed timezone to the simpledateformat in 
the
> SWCWriter ... could you please review this?
>
> Chris

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

[Christofer Dutz]

Mabe an update:

So I took the timestamp the maven-release plugin generates:
  
2020-03-24T19:00:04Z
That parsed as unix-time is:
1585072804000
Which matches the version I built locally ... the one built on the CI server is 
one hour in the future.
1585076404000

Perhaps this helps even more.

Chris


Am 24.03.20, 20:34 schrieb "Christofer Dutz" :

Hi Alex,

Well it seems as if the "mod" attribute in the catalog.xml is generated 
from the zipfile entry 
xmlWriter.writeAttribute(ATTR_MOD, 
String.valueOf(file.getLastModified()));

And in the SWCWriter there's this code that cuts off the timezone, you even 
wrote a comment on it

if (metadataDate != null)
{
// TODO: Perhaps parsing without modification and then 
serializing with a default timezone is the more solid approach.
// strip off timezone.  Zip format doesn't store timezone
// and the goal is to have the same date and time regardless
// of which timezone the build machine is using.
int c = metadataDate.lastIndexOf(' ');
if(c != -1) {
metadataDate = metadataDate.substring(0, c);
}
c = metadataFormat.lastIndexOf(' ');
if(c != -1) {
metadataFormat = metadataFormat.substring(0, c);
}
try {
SimpleDateFormat sdf = new 
SimpleDateFormat(metadataFormat);
sdf.setTimeZone(TimeZone.getTimeZone("UTC"));
fileDate = sdf.parse(metadataDate).getTime();
} catch (ParseException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (IllegalArgumentException e1) {
e1.printStackTrace();
}
}

So in general it doesn’t matter what timezone is in the string input, it 
was cut off anyway.
I added the line:

sdf.setTimeZone(TimeZone.getTimeZone("UTC"));

But it seems I still have the same issue with the con

re-inspecting the code I noticed, it's probably just the timestamp used in 
the zip file metadata ... not that used in the catalog.xml.
Will have another look at why I'm having this 36 offset. ... I just did a 
little math and it's exactly one hour off ... 

The difference of all tags is: 
360 milliseconds, which is exactly one hour. So the timestamps on the 
CI server are exactly one hour ahead of the builds we do in Europe.

This is currently the last issue preventing us from finishing the steps for 
the typedefs.

Do you have any idea? ... Anything with the US being Summer-Time and us 
still on Winter-Time?

Perhaps you could try executing this command in the typedefs:

ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7 
-DskipTests=true

Would be interesting if this succeeds for you. 

Well actually the library.swf in the swc seems to have a "net" Object in 
the locally built version and a "http" Object instead on the CI Server-Version.

Currently I'm trying to fix the timestamp version and address the other 
problem after that's solved.

Chris



Am 24.03.20, 20:08 schrieb "Alex Harui" :

Good to see progress.

Re timestamps:  I’m not quite sure what you are running into.

The builds were taking a time that included a timezone.  Here's some 
output from recent builds:

 [java] -metadata.date=02/25/20 14:51 +
 [java] -metadata.dateFormat=MM/dd/yy HH:mm Z

So I'm not sure how the timezone got lost on what you are seeing.  The 
RM was supposed to type in something like "02/25/20 14:51 +".  The prompts 
on the Jenkins job were supposed to hint that.

HTH,
-Alex

On 3/24/20, 7:47 AM, "Carlos Rovira"  wrote:

Hi Alex,
I finally said Chris to try it myself, so going with that now :)

El mar., 24 mar. 2020 a las 15:40, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:

> Hi Alex,
>
> I added a call to set a fixed timezone to the simpledateformat in 
the
> SWCWriter ... could you please review this?
>
> Chris
>
>
>
> Am 24.03.20, 15:26 schrieb "Christofer Dutz" 
:
>
> Hi all,
>
> so today we made progress ... not only did we fix the version 
skipping
> we observed yesterday. For this the commands done manually in the 
001a step
  

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

[Christofer Dutz]

Hi Alex,

Well it seems as if the "mod" attribute in the catalog.xml is generated from 
the zipfile entry 
xmlWriter.writeAttribute(ATTR_MOD, 
String.valueOf(file.getLastModified()));

And in the SWCWriter there's this code that cuts off the timezone, you even 
wrote a comment on it

if (metadataDate != null)
{
// TODO: Perhaps parsing without modification and then serializing 
with a default timezone is the more solid approach.
// strip off timezone.  Zip format doesn't store timezone
// and the goal is to have the same date and time regardless
// of which timezone the build machine is using.
int c = metadataDate.lastIndexOf(' ');
if(c != -1) {
metadataDate = metadataDate.substring(0, c);
}
c = metadataFormat.lastIndexOf(' ');
if(c != -1) {
metadataFormat = metadataFormat.substring(0, c);
}
try {
SimpleDateFormat sdf = new 
SimpleDateFormat(metadataFormat);
sdf.setTimeZone(TimeZone.getTimeZone("UTC"));
fileDate = sdf.parse(metadataDate).getTime();
} catch (ParseException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (IllegalArgumentException e1) {
e1.printStackTrace();
}
}

So in general it doesn’t matter what timezone is in the string input, it was 
cut off anyway.
I added the line:

sdf.setTimeZone(TimeZone.getTimeZone("UTC"));

But it seems I still have the same issue with the con

re-inspecting the code I noticed, it's probably just the timestamp used in the 
zip file metadata ... not that used in the catalog.xml.
Will have another look at why I'm having this 36 offset. ... I just did a 
little math and it's exactly one hour off ... 

The difference of all tags is: 
360 milliseconds, which is exactly one hour. So the timestamps on the CI 
server are exactly one hour ahead of the builds we do in Europe.

This is currently the last issue preventing us from finishing the steps for the 
typedefs.

Do you have any idea? ... Anything with the US being Summer-Time and us still 
on Winter-Time?

Perhaps you could try executing this command in the typedefs:

ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7 
-DskipTests=true

Would be interesting if this succeeds for you. 

Well actually the library.swf in the swc seems to have a "net" Object in the 
locally built version and a "http" Object instead on the CI Server-Version.

Currently I'm trying to fix the timestamp version and address the other problem 
after that's solved.

Chris



Am 24.03.20, 20:08 schrieb "Alex Harui" :

Good to see progress.

Re timestamps:  I’m not quite sure what you are running into.

The builds were taking a time that included a timezone.  Here's some output 
from recent builds:

 [java] -metadata.date=02/25/20 14:51 +
 [java] -metadata.dateFormat=MM/dd/yy HH:mm Z

So I'm not sure how the timezone got lost on what you are seeing.  The RM 
was supposed to type in something like "02/25/20 14:51 +".  The prompts on 
the Jenkins job were supposed to hint that.

HTH,
-Alex

On 3/24/20, 7:47 AM, "Carlos Rovira"  wrote:

Hi Alex,
I finally said Chris to try it myself, so going with that now :)

El mar., 24 mar. 2020 a las 15:40, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:

> Hi Alex,
>
> I added a call to set a fixed timezone to the simpledateformat in the
> SWCWriter ... could you please review this?
>
> Chris
>
>
>
> Am 24.03.20, 15:26 schrieb "Christofer Dutz" 
:
>
> Hi all,
>
> so today we made progress ... not only did we fix the version 
skipping
> we observed yesterday. For this the commands done manually in the 
001a step
> had to be changed.
>
> Now we managed to get the compiler part reproducible, but not so 
much
> the typedef part.
> We are observing that the same timestamp is passed in to the build
> when building the release on the ci server and when building the 
release
> locally. However the timestamps have a strange constant offset 36 in 
two
> digits of the timestamp in the catalog.xml
>
> 1585054125000 on the CI server
> 1585057725000 locally
>
> I am assuming that perhaps there is time-zone information leaking 
into
> the parsing of the date as we are using a date-format without 
time-zone
> information.
>
> I would assume that Alex, perhaps you could have a 

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

[apacheroyaleci]

See 

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

[Alex Harui]

Good to see progress.

Re timestamps:  I’m not quite sure what you are running into.

The builds were taking a time that included a timezone.  Here's some output 
from recent builds:

 [java] -metadata.date=02/25/20 14:51 +
 [java] -metadata.dateFormat=MM/dd/yy HH:mm Z

So I'm not sure how the timezone got lost on what you are seeing.  The RM was 
supposed to type in something like "02/25/20 14:51 +".  The prompts on the 
Jenkins job were supposed to hint that.

HTH,
-Alex

On 3/24/20, 7:47 AM, "Carlos Rovira"  wrote:

Hi Alex,
I finally said Chris to try it myself, so going with that now :)

El mar., 24 mar. 2020 a las 15:40, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:

> Hi Alex,
>
> I added a call to set a fixed timezone to the simpledateformat in the
> SWCWriter ... could you please review this?
>
> Chris
>
>
>
> Am 24.03.20, 15:26 schrieb "Christofer Dutz" :
>
> Hi all,
>
> so today we made progress ... not only did we fix the version skipping
> we observed yesterday. For this the commands done manually in the 001a 
step
> had to be changed.
>
> Now we managed to get the compiler part reproducible, but not so much
> the typedef part.
> We are observing that the same timestamp is passed in to the build
> when building the release on the ci server and when building the release
> locally. However the timestamps have a strange constant offset 36 in two
> digits of the timestamp in the catalog.xml
>
> 1585054125000 on the CI server
> 1585057725000 locally
>
> I am assuming that perhaps there is time-zone information leaking into
> the parsing of the date as we are using a date-format without time-zone
> information.
>
> I would assume that Alex, perhaps you could have a look at what's
> happening in the SWCWriter constructor, where the parsing of the timestamp
> is implemented.
>
> Thanks,
>
> Chris
>
>
> Am 24.03.20, 09:36 schrieb "Christofer Dutz" <
> christofer.d...@c-ware.de>:
>
> Hi Alex,
>
> I had another look ... I think the version skips one is in step
> 001a ...
> There the job checks out develop, applies the update to the new
> version of the build tools and jburg types, but then this is pushed and
> then again to the release branch (hereby overwriting the old
> release-branch) ... I'll try out a way with cherry picking the change from
> develop into the release branch. Unfortunately I haven't been able to find
> where the text in the emails comes from ...
>
> I'm talking about the order of the constants in the class
> ProblemID. I forced that to be sorted now. That's why we have to 
re-release
> the build tools.
>
> Chris
>
> Am 24.03.20, 08:14 schrieb "Alex Harui"  >:
>
> Re: credentials:  Feel free to disable the credential store.
>  I did not have to both login and go through 2fa to Git Push.  There is
> some long password/token/credential/hash-like thing you get when you sign
> up with Apache Git that seems to work when you use it as a password.
>
> Re: the utils steps.  I just looked and it appears that
> compiler-jburg-types and compiler-build-tools are no longer
> child/submodules of the root pom.xml in royale-compiler.  So now I get how
> why the development version won't get bumped up twice.  I think the way it
> was working may be that the updated dev version never got pushed to
> develop.  If you are satisfied with that setup, that's fine with me.  So
> then it might make more sense to get rid of 1a and create a whole new set
> of steps for each of compiler-jburg-types and compiler-build-tools.  If I
> understand correctly, those new steps would run mvn release:branch, mvn
> release:prepare and mvn release:perform in compiler-jburg-types or
> compiler-build-tools, stopping if there are interim pushes that need to be
> done, then start their own vote emails by copying other CI steps.
>
> I use a Mac and thought I got all binaries to match from the
> .  I'm not sure what properties you are referring to.
>
> I'm done for tonight.  Will catch up in my morning.
>
> -Alex
>
> On 3/23/20, 11:15 PM, "Christofer Dutz" <
> christofer.d...@c-ware.de> wrote:
>
> Good morning all,
>
> well I didn't disable anythig as I didn't want to break
> anything. So I thought before simply changing something I'd ask first.
> So I would consider it a "bug" that it's there and when we
> continue today, we'll try to find out and disable the thing.
> 

Release Step 007 Succeeded

[apacheroyaleci]

>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 -f releasesteps.xml Release_Step_007_Sign 
-Drelease.version=0.9.7
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload 
-Drelease.version=0.9.7
This will upload the signed artifacts to Maven Release Staging. Do not "Close" 
the staging repository until the other repos have been added.

Release Step 006 Succeeded

[apacheroyaleci]

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

[apacheroyaleci]

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_004 - Build # 13 - Failure!

[apacheroyaleci]

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

[apacheroyaleci]

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

[apacheroyaleci]

>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 
-DskipTests=true
Otherwise, run:
  ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7
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 
-Drelease.version=0.9.7
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.7
This will upload the signed artifacts to Maven Release Staging. If you are 
getting 401 responses from Nexus (permission denied) please be sure to have 
your apache creedentials configured in your .m2/settings.xml file. 

Feel free to use this template if you haven't got a settings.xml yet:


http://maven.apache.org/SETTINGS/1.1.0 
http://maven.apache.org/xsd/settings-1.1.0.xsd; 
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
  


  apache.releases.https
  {your apache user id}
  {your apache user password}

  


(Be sure to replace the placeholders with your actual apache committer id and 
your Apache password)

If you already have a settings.xml, just be sure the "server" block containing 
your credentials is added to a servers block in that file.

Do not "Close" the staging repository until the other repos have been added.

Release Step 002a Succeeded

[apacheroyaleci]

Continue on to Release Step 003

Release Step 002 Succeeded

[apacheroyaleci]

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

[apacheroyaleci]

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 --format="%H" -n 1
(Switch to the release branch)
git checkout release/0.9.7
(Cherry-Pick the last change to develop to the release branch)
git cherry-pick {COMMIT_ID}
(Push the changes to the release branch)
git push origin release/0.9.7

You will need your Apache/Github username and 2FA token.

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.

Release Step 001a Succeeded

[apacheroyaleci]

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 --format="%H" -n 1
(Switch to the release branch)
git checkout release/0.9.7
(Cherry-Pick the last change to develop to the release branch)
git cherry-pick {COMMIT_ID}
(Push the changes to the release branch)
git push origin release/0.9.7

You will need your Apache/Github username and 2FA token.

Royale_Release_Step_001a_If_Utils - Build # 12 - Still Failing!

[apacheroyaleci]

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!

[apacheroyaleci]

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

[apacheroyaleci]

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 --format="%H" -n 1
(Switch to the release branch)
git checkout release/0.9.7
(Cherry-Pick the last change to develop to the release branch)
git cherry-pick {COMMIT_ID}
(Push the changes to the release branch)
git push origin release/0.9.7

You will need your Apache/Github username and 2FA token.

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.

Release Step 003 Succeeded

[apacheroyaleci]

>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 
-DskipTests=true
Otherwise, run:
  ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7
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 
-Drelease.version=0.9.7
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.7
This will upload the signed artifacts to Maven Release Staging. If you are 
getting 401 responses from Nexus (permission denied) please be sure to have 
your apache creedentials configured in your .m2/settings.xml file. 

Feel free to use this template if you haven't got a settings.xml yet:


http://maven.apache.org/SETTINGS/1.1.0 
http://maven.apache.org/xsd/settings-1.1.0.xsd; 
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
  


  apache.releases.https
  {your apache user id}
  {your apache user password}

  


(Be sure to replace the placeholders with your actual apache committer id and 
your Apache password)

If you already have a settings.xml, just be sure the "server" block containing 
your credentials is added to a servers block in that file.

Do not "Close" the staging repository until the other repos have been added.

Release Step 002a Succeeded

[apacheroyaleci]

Continue on to Release Step 003

Royale_Release_Step_002a_If_Utils - Build # 12 - Failure!

[apacheroyaleci]

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

[apacheroyaleci]

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

[apacheroyaleci]

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 --format="%H" -n 1
(Switch to the release branch)
git checkout release/0.9.7
(Cherry-Pick the last change to develop to the release branch)
git cherry-pick {COMMIT_ID}
(Push the changes to the release branch)
git push origin release/0.9.7

You will need your Apache/Github username and 2FA token.

Royale_Release_Step_001a_If_Utils - Build # 8 - Failure!

[apacheroyaleci]

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

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

Build failed in Jenkins: royale-asjs_jsonly #1117

[apacheroyaleci]

See 


Changes:


--
[...truncated 1.72 MB...]
main:

tweak-for-jsonly:
 [copy] Copying 1 file to 

 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

ide:

post-build:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

 [copy] Copying 1 file to 

 [copy] Copying 1 file to 

[touch] Creating 

[touch] Creating 

[touch] Creating 


last-message-if-airsdk:

main:
 [echo] ant main target completed on 03/24/2020 03:57:01 PM

sample-themes:

check-runtime-env:

runtime-setup:

mustella-setup:

load-task:

marmotinni-setup:

prepare:
 [echo] Making lib directory 
:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
[mkdir] Created dir: 


selenium3-jar-check:

selenium3-jar:
[mkdir] Created dir: 


download-zip:
[mkdir] Created dir: 

  [get] Getting: https://bit.ly/2zm3ZzF
  [get] To: 

  [get] https://bit.ly/2zm3ZzF permanently moved to 
https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip

untar-file:

unzip-file:
[unzip] Expanding: 

 into 


check-sum:

copy-downloaded-jar:
  [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
  [get] To: 

 [copy] Copying 10 files to 


clean:

main:

clean:
   [delete] Deleting: 


check-compiler-home:

check-compiler:

compile:

compile-js:
 [echo] Compiling mustella.swc
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [java] args:
 [java] 
+royalelib=
 [java] +playerglobal.version=11.7
 [java] +env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}
 [java] -compiler.strict-xml=true
 [java] -compiler.targets=SWF,JSRoyale
 [java] 
-output=
 [java] 
-load-config=
 [java] 
-load-config+=
 [java] 
-js-load-config=
 [java] 

Release Step 003 Succeeded

[apacheroyaleci]

>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 
-DskipTests=true
Otherwise, run:
  ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7
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 
-Drelease.version=0.9.7
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.7
This will upload the signed artifacts to Maven Release Staging. If you are 
getting 401 responses from Nexus (permission denied) please be sure to have 
your apache creedentials configured in your .m2/settings.xml file. 

Feel free to use this template if you haven't got a settings.xml yet:


http://maven.apache.org/SETTINGS/1.1.0 
http://maven.apache.org/xsd/settings-1.1.0.xsd; 
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
  


  apache.releases.https
  {your apache user id}
  {your apache user password}

  


(Be sure to replace the placeholders with your actual apache committer id and 
your Apache password)

If you already have a settings.xml, just be sure the "server" block containing 
your credentials is added to a servers block in that file.

Do not "Close" the staging repository until the other repos have been added.

Release Step 002a Succeeded

[apacheroyaleci]

Continue on to Release Step 003

Royale_Release_Step_002a_If_Utils - Build # 10 - Still Failing!

[apacheroyaleci]

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!

[apacheroyaleci]

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

[apacheroyaleci]

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

[apacheroyaleci]

 03/24/20 15:07 +
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/AceJS/AceJS.swc.properties>

clean:
 [echo] swc-date is 03/24/20 15:07 +
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/AceJS/AceJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 03/24/20 15:07 +
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

clean:
 [echo] swc-date is 03/24/20 15:07 +
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

check-for-tests:

clean-tests:
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/libs>

package-clean:
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/out>

clean-temp:
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp/royale-asjs>

checkintests-clean:
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/mustella/tests/basicTests/bin>

mxtests-clean:

clean:
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/royale-sdk-description.xml>
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/js/libs>
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp>
 [echo] ROYALE_HOME = 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/>
 [echo] royalelib = 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks>
 [echo] doc_output = 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output>
 [echo] compiler.source-path = 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/projects/*/src/main/royale>

clean:

super-clean:
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/libs/player>
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/libs/air>
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/locale>
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/mx>
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/rsls>
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/themes/Halo>
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/themes/Spark>
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/airmobile-config.xml>
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/macfonts.ser>
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/winfonts.ser>
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/localfonts.ser>
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/mxml-manifest.xml>
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/spark-manifest.xml>
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/ide/flashbuilder/flashbuilder-config.xml>

create-description:
 [echo] build.number is 20200324

js-output-royale-description:

swf-js-output-royale-description:

create-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks>

tweak-for-jsonly:

tweak-for-jsonly:
 [copy] Warning: Could not find file 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/js/libs/js.swc>
 to copy.
 [copy] Copying

Build failed in Jenkins: royale-asjs_jsonly #1115

[apacheroyaleci]

See 


Changes:

[piotrzarzycki21] Adjust ant build after moving TourDeJewel to different folder


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 151571cf6cbcae6412c7aff3e089cfd032f6bd6e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 151571cf6cbcae6412c7aff3e089cfd032f6bd6e
Commit message: "Adjust ant build after moving TourDeJewel to different folder"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 8a2aa8a421e4766fb9d2f19b2be92673588a23e3 # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Buildfile: 


block-flat-fonts:

check-compiler-home:

check-typedefs-home:

thirdparty-clean:

thirdparty-clean:

pixelbender-clean:

swfobject-clean:

flat-ui-clean:

gcl-clean:
 [echo] Deleting Google Closure Library

clean:

examples-clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

BUILD FAILED
:630:
 The following error occurred while executing this line:
:163:
 Basedir 

 does not exist

Total time: 1 second
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Release Step 001a Succeeded

[apacheroyaleci]

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 --format="%H" -n 1
(Switch to the release branch)
git checkout release/0.9.7
(Cherry-Pick the last change to develop to the release branch)
git cherry-pick {COMMIT_ID}
(Push the changes to the release branch)
git push origin release/0.9.7

You will need your Apache/Github username and 2FA token.

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.

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

[Carlos Rovira]

Hi Alex,
I finally said Chris to try it myself, so going with that now :)

El mar., 24 mar. 2020 a las 15:40, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:

> Hi Alex,
>
> I added a call to set a fixed timezone to the simpledateformat in the
> SWCWriter ... could you please review this?
>
> Chris
>
>
>
> Am 24.03.20, 15:26 schrieb "Christofer Dutz" :
>
> Hi all,
>
> so today we made progress ... not only did we fix the version skipping
> we observed yesterday. For this the commands done manually in the 001a step
> had to be changed.
>
> Now we managed to get the compiler part reproducible, but not so much
> the typedef part.
> We are observing that the same timestamp is passed in to the build
> when building the release on the ci server and when building the release
> locally. However the timestamps have a strange constant offset 36 in two
> digits of the timestamp in the catalog.xml
>
> 1585054125000 on the CI server
> 1585057725000 locally
>
> I am assuming that perhaps there is time-zone information leaking into
> the parsing of the date as we are using a date-format without time-zone
> information.
>
> I would assume that Alex, perhaps you could have a look at what's
> happening in the SWCWriter constructor, where the parsing of the timestamp
> is implemented.
>
> Thanks,
>
> Chris
>
>
> Am 24.03.20, 09:36 schrieb "Christofer Dutz" <
> christofer.d...@c-ware.de>:
>
> Hi Alex,
>
> I had another look ... I think the version skips one is in step
> 001a ...
> There the job checks out develop, applies the update to the new
> version of the build tools and jburg types, but then this is pushed and
> then again to the release branch (hereby overwriting the old
> release-branch) ... I'll try out a way with cherry picking the change from
> develop into the release branch. Unfortunately I haven't been able to find
> where the text in the emails comes from ...
>
> I'm talking about the order of the constants in the class
> ProblemID. I forced that to be sorted now. That's why we have to re-release
> the build tools.
>
> Chris
>
> Am 24.03.20, 08:14 schrieb "Alex Harui"  >:
>
> Re: credentials:  Feel free to disable the credential store.
>  I did not have to both login and go through 2fa to Git Push.  There is
> some long password/token/credential/hash-like thing you get when you sign
> up with Apache Git that seems to work when you use it as a password.
>
> Re: the utils steps.  I just looked and it appears that
> compiler-jburg-types and compiler-build-tools are no longer
> child/submodules of the root pom.xml in royale-compiler.  So now I get how
> why the development version won't get bumped up twice.  I think the way it
> was working may be that the updated dev version never got pushed to
> develop.  If you are satisfied with that setup, that's fine with me.  So
> then it might make more sense to get rid of 1a and create a whole new set
> of steps for each of compiler-jburg-types and compiler-build-tools.  If I
> understand correctly, those new steps would run mvn release:branch, mvn
> release:prepare and mvn release:perform in compiler-jburg-types or
> compiler-build-tools, stopping if there are interim pushes that need to be
> done, then start their own vote emails by copying other CI steps.
>
> I use a Mac and thought I got all binaries to match from the
> .  I'm not sure what properties you are referring to.
>
> I'm done for tonight.  Will catch up in my morning.
>
> -Alex
>
> On 3/23/20, 11:15 PM, "Christofer Dutz" <
> christofer.d...@c-ware.de> wrote:
>
> Good morning all,
>
> well I didn't disable anythig as I didn't want to break
> anything. So I thought before simply changing something I'd ask first.
> So I would consider it a "bug" that it's there and when we
> continue today, we'll try to find out and disable the thing.
> However I would assume then the RM will not only have to
> do his usual login but also the 2fa thing at every step too, correct?
>
> And, just a kindly meant question ... would it be possible
> to reply at the top instead of inline? I sort of have missed several
> Of your Inline comments in the past as at least in my mail
> client it's hard to spot what's mine and what's not.
> (I could start counting spaces)
>
> (I first missed this question of yours ... but discovered
> it after counting spaces ;-) )
>
> Well to release the build tool with maven you would simply
> do the:
> mvn release:prepare
> mvn release:perform
> for each of them, then adjust the main pom and do the mvn
> release:branch ... then prepare and perform after that.
>
> Currently also jburg types and the build-tools are sort of
> 

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

[Christofer Dutz]

Hi Alex, 

I added a call to set a fixed timezone to the simpledateformat in the SWCWriter 
... could you please review this?

Chris



Am 24.03.20, 15:26 schrieb "Christofer Dutz" :

Hi all,

so today we made progress ... not only did we fix the version skipping we 
observed yesterday. For this the commands done manually in the 001a step had to 
be changed. 

Now we managed to get the compiler part reproducible, but not so much the 
typedef part.
We are observing that the same timestamp is passed in to the build when 
building the release on the ci server and when building the release locally. 
However the timestamps have a strange constant offset 36 in two digits of the 
timestamp in the catalog.xml

1585054125000 on the CI server
1585057725000 locally 

I am assuming that perhaps there is time-zone information leaking into the 
parsing of the date as we are using a date-format without time-zone information.

I would assume that Alex, perhaps you could have a look at what's happening 
in the SWCWriter constructor, where the parsing of the timestamp is implemented.

Thanks,

Chris


Am 24.03.20, 09:36 schrieb "Christofer Dutz" :

Hi Alex,

I had another look ... I think the version skips one is in step 001a ...
There the job checks out develop, applies the update to the new version 
of the build tools and jburg types, but then this is pushed and then again to 
the release branch (hereby overwriting the old release-branch) ... I'll try out 
a way with cherry picking the change from develop into the release branch. 
Unfortunately I haven't been able to find where the text in the emails comes 
from ... 

I'm talking about the order of the constants in the class ProblemID. I 
forced that to be sorted now. That's why we have to re-release the build tools.

Chris

Am 24.03.20, 08:14 schrieb "Alex Harui" :

Re: credentials:  Feel free to disable the credential store.   I 
did not have to both login and go through 2fa to Git Push.  There is some long 
password/token/credential/hash-like thing you get when you sign up with Apache 
Git that seems to work when you use it as a password.

Re: the utils steps.  I just looked and it appears that 
compiler-jburg-types and compiler-build-tools are no longer child/submodules of 
the root pom.xml in royale-compiler.  So now I get how why the development 
version won't get bumped up twice.  I think the way it was working may be that 
the updated dev version never got pushed to develop.  If you are satisfied with 
that setup, that's fine with me.  So then it might make more sense to get rid 
of 1a and create a whole new set of steps for each of compiler-jburg-types and 
compiler-build-tools.  If I understand correctly, those new steps would run mvn 
release:branch, mvn release:prepare and mvn release:perform in 
compiler-jburg-types or compiler-build-tools, stopping if there are interim 
pushes that need to be done, then start their own vote emails by copying other 
CI steps.

I use a Mac and thought I got all binaries to match from the .  I'm 
not sure what properties you are referring to.

I'm done for tonight.  Will catch up in my morning.

-Alex

On 3/23/20, 11:15 PM, "Christofer Dutz"  
wrote:

Good morning all,

well I didn't disable anythig as I didn't want to break 
anything. So I thought before simply changing something I'd ask first.
So I would consider it a "bug" that it's there and when we 
continue today, we'll try to find out and disable the thing.
However I would assume then the RM will not only have to do his 
usual login but also the 2fa thing at every step too, correct?

And, just a kindly meant question ... would it be possible to 
reply at the top instead of inline? I sort of have missed several 
Of your Inline comments in the past as at least in my mail 
client it's hard to spot what's mine and what's not. 
(I could start counting spaces)

(I first missed this question of yours ... but discovered it 
after counting spaces ;-) )

Well to release the build tool with maven you would simply do 
the:
mvn release:prepare
mvn release:perform
for each of them, then adjust the main pom and do the mvn 
release:branch ... then prepare and perform after that.

Currently also jburg types and the build-tools are sort of 
released in parallel. With maven you would simply release only the module 
that's needed to be released. In our case build-tools would have been enough.

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

[Christofer Dutz]

Hi all,

so today we made progress ... not only did we fix the version skipping we 
observed yesterday. For this the commands done manually in the 001a step had to 
be changed. 

Now we managed to get the compiler part reproducible, but not so much the 
typedef part.
We are observing that the same timestamp is passed in to the build when 
building the release on the ci server and when building the release locally. 
However the timestamps have a strange constant offset 36 in two digits of the 
timestamp in the catalog.xml

1585054125000 on the CI server
1585057725000 locally 

I am assuming that perhaps there is time-zone information leaking into the 
parsing of the date as we are using a date-format without time-zone information.

I would assume that Alex, perhaps you could have a look at what's happening in 
the SWCWriter constructor, where the parsing of the timestamp is implemented.

Thanks,

Chris


Am 24.03.20, 09:36 schrieb "Christofer Dutz" :

Hi Alex,

I had another look ... I think the version skips one is in step 001a ...
There the job checks out develop, applies the update to the new version of 
the build tools and jburg types, but then this is pushed and then again to the 
release branch (hereby overwriting the old release-branch) ... I'll try out a 
way with cherry picking the change from develop into the release branch. 
Unfortunately I haven't been able to find where the text in the emails comes 
from ... 

I'm talking about the order of the constants in the class ProblemID. I 
forced that to be sorted now. That's why we have to re-release the build tools.

Chris

Am 24.03.20, 08:14 schrieb "Alex Harui" :

Re: credentials:  Feel free to disable the credential store.   I did 
not have to both login and go through 2fa to Git Push.  There is some long 
password/token/credential/hash-like thing you get when you sign up with Apache 
Git that seems to work when you use it as a password.

Re: the utils steps.  I just looked and it appears that 
compiler-jburg-types and compiler-build-tools are no longer child/submodules of 
the root pom.xml in royale-compiler.  So now I get how why the development 
version won't get bumped up twice.  I think the way it was working may be that 
the updated dev version never got pushed to develop.  If you are satisfied with 
that setup, that's fine with me.  So then it might make more sense to get rid 
of 1a and create a whole new set of steps for each of compiler-jburg-types and 
compiler-build-tools.  If I understand correctly, those new steps would run mvn 
release:branch, mvn release:prepare and mvn release:perform in 
compiler-jburg-types or compiler-build-tools, stopping if there are interim 
pushes that need to be done, then start their own vote emails by copying other 
CI steps.

I use a Mac and thought I got all binaries to match from the .  I'm not 
sure what properties you are referring to.

I'm done for tonight.  Will catch up in my morning.

-Alex

On 3/23/20, 11:15 PM, "Christofer Dutz"  
wrote:

Good morning all,

well I didn't disable anythig as I didn't want to break anything. 
So I thought before simply changing something I'd ask first.
So I would consider it a "bug" that it's there and when we continue 
today, we'll try to find out and disable the thing.
However I would assume then the RM will not only have to do his 
usual login but also the 2fa thing at every step too, correct?

And, just a kindly meant question ... would it be possible to reply 
at the top instead of inline? I sort of have missed several 
Of your Inline comments in the past as at least in my mail client 
it's hard to spot what's mine and what's not. 
(I could start counting spaces)

(I first missed this question of yours ... but discovered it after 
counting spaces ;-) )

Well to release the build tool with maven you would simply do the:
mvn release:prepare
mvn release:perform
for each of them, then adjust the main pom and do the mvn 
release:branch ... then prepare and perform after that.

Currently also jburg types and the build-tools are sort of released 
in parallel. With maven you would simply release only the module that's needed 
to be released. In our case build-tools would have been enough.

Speaking of build-tools ... are you possibly using Windows as OS on 
your system? Just asking because the build-tools seem to have always generated 
a sorted set of properties on windows and an unsorted one on Mac (Seems to be 
differences in the way the filesystem works) ... in that case it would have 
been impossible to have a release manager not using Java 8 on a Windows 
machine. (My changes recently 

Build failed in Jenkins: royale-asjs_jsonly #1114

[apacheroyaleci]

See 


Changes:


--
Started by upstream project "royale-typedefs" build number 450
originally caused by:
 Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 8a2aa8a421e4766fb9d2f19b2be92673588a23e3 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 8a2aa8a421e4766fb9d2f19b2be92673588a23e3
Commit message: "tour-de-jewel: update all examples to use 
itemsVerticalAlign="itemsCenter""
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 8a2aa8a421e4766fb9d2f19b2be92673588a23e3 # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Buildfile: 


block-flat-fonts:

check-compiler-home:

check-typedefs-home:

thirdparty-clean:

thirdparty-clean:

pixelbender-clean:

swfobject-clean:

flat-ui-clean:

gcl-clean:
 [echo] Deleting Google Closure Library

clean:

examples-clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

BUILD FAILED
:630:
 The following error occurred while executing this line:
:163:
 Basedir 

 does not exist

Total time: 0 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Release Step 007 Succeeded

[apacheroyaleci]

>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 -f releasesteps.xml Release_Step_007_Sign 
-Drelease.version=0.9.7
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload 
-Drelease.version=0.9.7
This will upload the signed artifacts to Maven Release Staging. Do not "Close" 
the staging repository until the other repos have been added.

Release Step 006 Succeeded

[apacheroyaleci]

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

[apacheroyaleci]

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

[apacheroyaleci]

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

[apacheroyaleci]

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.

Build failed in Jenkins: royale-asjs_jsonly #1113

[apacheroyaleci]

See 


Changes:


--
Started by upstream project "royale-typedefs" build number 449
originally caused by:
 Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 8a2aa8a421e4766fb9d2f19b2be92673588a23e3 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 8a2aa8a421e4766fb9d2f19b2be92673588a23e3
Commit message: "tour-de-jewel: update all examples to use 
itemsVerticalAlign="itemsCenter""
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 8a2aa8a421e4766fb9d2f19b2be92673588a23e3 # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Buildfile: 


block-flat-fonts:

check-compiler-home:

check-typedefs-home:

thirdparty-clean:

thirdparty-clean:

pixelbender-clean:

swfobject-clean:

flat-ui-clean:

gcl-clean:
 [echo] Deleting Google Closure Library

clean:

examples-clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

BUILD FAILED
:630:
 The following error occurred while executing this line:
:163:
 Basedir 

 does not exist

Total time: 0 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1112

[apacheroyaleci]

See 


Changes:

[carlosrovira] jewel-layouts: make itemsVerticalAlign accept "itemCenter" 
(instead

[carlosrovira] tour-de-jewel: update all examples to use


--
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 8a2aa8a421e4766fb9d2f19b2be92673588a23e3 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 8a2aa8a421e4766fb9d2f19b2be92673588a23e3
Commit message: "tour-de-jewel: update all examples to use 
itemsVerticalAlign="itemsCenter""
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > a538c215fb055da027ac815e0386bc2432a8aa1b # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Buildfile: 


block-flat-fonts:

check-compiler-home:

check-typedefs-home:

thirdparty-clean:

thirdparty-clean:

pixelbender-clean:

swfobject-clean:

flat-ui-clean:

gcl-clean:
 [echo] Deleting Google Closure Library

clean:

examples-clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

BUILD FAILED
:630:
 The following error occurred while executing this line:
:163:
 Basedir 

 does not exist

Total time: 0 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Royale_Release_Step_004 - Build # 10 - Failure!

[apacheroyaleci]

Royale_Release_Step_004 - Build # 10 - Failure:

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

Build failed in Jenkins: royale-asjs_jsonly #1111

[apacheroyaleci]

See 


Changes:


--
Started by upstream project "royale-typedefs" build number 448
originally caused by:
 Started by upstream project "royale-compiler" build number 279
 originally caused by:
  Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision a538c215fb055da027ac815e0386bc2432a8aa1b 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > a538c215fb055da027ac815e0386bc2432a8aa1b
Commit message: "jewel-button: css was left"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > a538c215fb055da027ac815e0386bc2432a8aa1b # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Buildfile: 


block-flat-fonts:

check-compiler-home:

check-typedefs-home:

thirdparty-clean:

thirdparty-clean:

pixelbender-clean:

swfobject-clean:

flat-ui-clean:

gcl-clean:
 [echo] Deleting Google Closure Library

clean:

examples-clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

BUILD FAILED
:630:
 The following error occurred while executing this line:
:163:
 Basedir 

 does not exist

Total time: 2 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Release Step 007 Succeeded

[apacheroyaleci]

>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 -f releasesteps.xml Release_Step_007_Sign 
-Drelease.version=0.9.7
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload 
-Drelease.version=0.9.7
This will upload the signed artifacts to Maven Release Staging. Do not "Close" 
the staging repository until the other repos have been added.

Build failed in Jenkins: royale-asjs_jsonly #1110

[apacheroyaleci]

See 


Changes:


--
Started by upstream project "royale-typedefs" build number 447
originally caused by:
 Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision a538c215fb055da027ac815e0386bc2432a8aa1b 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > a538c215fb055da027ac815e0386bc2432a8aa1b
Commit message: "jewel-button: css was left"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > a538c215fb055da027ac815e0386bc2432a8aa1b # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Buildfile: 


block-flat-fonts:

check-compiler-home:

check-typedefs-home:

thirdparty-clean:

thirdparty-clean:

pixelbender-clean:

swfobject-clean:

flat-ui-clean:

gcl-clean:
 [echo] Deleting Google Closure Library

clean:

examples-clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

BUILD FAILED
:630:
 The following error occurred while executing this line:
:163:
 Basedir 

 does not exist

Total time: 0 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Release Step 006 Succeeded

[apacheroyaleci]

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

[apacheroyaleci]

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

[apacheroyaleci]

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

[apacheroyaleci]

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 004 Succeeded

[apacheroyaleci]

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.

Build failed in Jenkins: royale-asjs_jsonly #1109

[apacheroyaleci]

See 


Changes:

[carlosrovira] jewel-button: css was left


--
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision a538c215fb055da027ac815e0386bc2432a8aa1b 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > a538c215fb055da027ac815e0386bc2432a8aa1b
Commit message: "jewel-button: css was left"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 5bc0782f905e10d6153d2dbc3ac7736fb6e6a121 # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Buildfile: 


block-flat-fonts:

check-compiler-home:

check-typedefs-home:

thirdparty-clean:

thirdparty-clean:

pixelbender-clean:

swfobject-clean:

flat-ui-clean:

gcl-clean:
 [echo] Deleting Google Closure Library

clean:

examples-clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

BUILD FAILED
:630:
 The following error occurred while executing this line:
:163:
 Basedir 

 does not exist

Total time: 0 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Release Step 007 Succeeded

[apacheroyaleci]

>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 -f releasesteps.xml Release_Step_007_Sign 
-Drelease.version=0.9.7
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload 
-Drelease.version=0.9.7
This will upload the signed artifacts to Maven Release Staging. Do not "Close" 
the staging repository until the other repos have been added.

Royale_Release_Step_007 - Build # 1 - Failure!

[apacheroyaleci]

Royale_Release_Step_007 - Build # 1 - Failure:

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

Release Step 006 Succeeded

[apacheroyaleci]

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.

Royale_Release_Step_006 - Build # 1 - Failure!

[apacheroyaleci]

Royale_Release_Step_006 - Build # 1 - Failure:

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

Release Step 005 Succeeded

[apacheroyaleci]

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 005 Succeeded

[apacheroyaleci]

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.

Build failed in Jenkins: royale-asjs_jsonly #1108

[apacheroyaleci]

See 


Changes:


--
Started by upstream project "royale-typedefs" build number 446
originally caused by:
 Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 5bc0782f905e10d6153d2dbc3ac7736fb6e6a121 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 5bc0782f905e10d6153d2dbc3ac7736fb6e6a121
Commit message: "Merge pull request #786 from chrisdutz/develop"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 5bc0782f905e10d6153d2dbc3ac7736fb6e6a121 # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Buildfile: 


block-flat-fonts:

check-compiler-home:

check-typedefs-home:

thirdparty-clean:

thirdparty-clean:

pixelbender-clean:

swfobject-clean:

flat-ui-clean:

gcl-clean:
 [echo] Deleting Google Closure Library

clean:

examples-clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

BUILD FAILED
:630:
 The following error occurred while executing this line:
:163:
 Basedir 

 does not exist

Total time: 1 second
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Release Step 004 Succeeded

[apacheroyaleci]

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

[apacheroyaleci]

Royale_Release_Step_004 - Build # 7 - Still Failing:

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

Royale_Release_Step_004 - Build # 6 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_004 - Build # 6 - Still Failing:

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

Royale_Release_Step_004 - Build # 5 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_004 - Build # 5 - Still Failing:

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

Build failed in Jenkins: royale-asjs_jsonly #1107

[apacheroyaleci]

See 


Changes:

[carlosrovira] tour-de-jewel: fix urls to source code now that TDJ is in jewel 
folder

[christofer.dutz] - Changed the developbranchname setting to "develop"


--
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 5bc0782f905e10d6153d2dbc3ac7736fb6e6a121 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 5bc0782f905e10d6153d2dbc3ac7736fb6e6a121
Commit message: "Merge pull request #786 from chrisdutz/develop"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > c009fb5cbbbfe457a9175ba2ff09da552c8ad000 # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Buildfile: 


block-flat-fonts:

check-compiler-home:

check-typedefs-home:

thirdparty-clean:

thirdparty-clean:

pixelbender-clean:

swfobject-clean:

flat-ui-clean:

gcl-clean:
 [echo] Deleting Google Closure Library

clean:

examples-clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

BUILD FAILED
:630:
 The following error occurred while executing this line:
:163:
 Basedir 

 does not exist

Total time: 0 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Release Step 004 Succeeded

[apacheroyaleci]

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 # 2 - Failure!

[apacheroyaleci]

Royale_Release_Step_004 - Build # 2 - Failure:

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

Release Step 004 Succeeded

[apacheroyaleci]

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.

Build failed in Jenkins: royale-asjs_jsonly #1106

[apacheroyaleci]

See 


Changes:


--
Started by upstream project "royale-typedefs" build number 445
originally caused by:
 Started by upstream project "royale-compiler" build number 277
 originally caused by:
  Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision c009fb5cbbbfe457a9175ba2ff09da552c8ad000 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > c009fb5cbbbfe457a9175ba2ff09da552c8ad000
Commit message: "Merge pull request #782 from chrisdutz/develop"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > c009fb5cbbbfe457a9175ba2ff09da552c8ad000 # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Buildfile: 


block-flat-fonts:

check-compiler-home:

check-typedefs-home:

thirdparty-clean:

thirdparty-clean:

pixelbender-clean:

swfobject-clean:

flat-ui-clean:

gcl-clean:
 [echo] Deleting Google Closure Library

clean:

examples-clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

BUILD FAILED
:630:
 The following error occurred while executing this line:
:163:
 Basedir 

 does not exist

Total time: 1 second
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Release Step 003 Succeeded

[apacheroyaleci]

>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 
-DskipTests=true
Otherwise, run:
  ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7
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 
-Drelease.version=0.9.7
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.7
This will upload the signed artifacts to Maven Release Staging. Do not "Close" 
the staging repository until the other repos have been added.

Release Step 002a Succeeded

[apacheroyaleci]

Continue on to Release Step 003

Build failed in Jenkins: royale-asjs_jsonly #1105

[apacheroyaleci]

See 


Changes:


--
Started by upstream project "royale-typedefs" build number 444
originally caused by:
 Started by upstream project "royale-compiler" build number 276
 originally caused by:
  Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision c009fb5cbbbfe457a9175ba2ff09da552c8ad000 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > c009fb5cbbbfe457a9175ba2ff09da552c8ad000
Commit message: "Merge pull request #782 from chrisdutz/develop"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > c009fb5cbbbfe457a9175ba2ff09da552c8ad000 # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Buildfile: 


block-flat-fonts:

check-compiler-home:

check-typedefs-home:

thirdparty-clean:

thirdparty-clean:

pixelbender-clean:

swfobject-clean:

flat-ui-clean:

gcl-clean:
 [echo] Deleting Google Closure Library

clean:

examples-clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

BUILD FAILED
:630:
 The following error occurred while executing this line:
:163:
 Basedir 

 does not exist

Total time: 1 second
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

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

[apacheroyaleci]

See 

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

[apacheroyaleci]

See 

Release Step 002 Succeeded

[apacheroyaleci]

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-typedefs #443

[apacheroyaleci]

See 


Changes:

[christofer.dutz] - Added a previously existing profile back which is used by 
the ant


--
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-typedefs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-typedefs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-typedefs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 70d835284e8ef4cc91ebff0fb7644ad47571a727 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 70d835284e8ef4cc91ebff0fb7644ad47571a727
Commit message: "Merge pull request #8 from chrisdutz/develop"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > a153d76374ff30c2c95a4d9a25a72b80d74bdf4d # timeout=10
[royale-typedefs] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-Dbuild.number=443 main && exit %%ERRORLEVEL%%"
Buildfile: 


main:
 [echo] swc-date is 03/24/20 09:06 +

download:
 [echo] 


BUILD FAILED
:58:
 The following error occurred while executing this line:
:91:
 src 
'
 doesn't exist.

Total time: 0 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure

Release Step 001a Succeeded

[apacheroyaleci]

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-asjs_jsonly #1104

[apacheroyaleci]

See 


Changes:

[christofer.dutz] - Added a previously existing profile back which is used by 
the ant


--
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent1 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision c009fb5cbbbfe457a9175ba2ff09da552c8ad000 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > c009fb5cbbbfe457a9175ba2ff09da552c8ad000
Commit message: "Merge pull request #782 from chrisdutz/develop"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > bf8a9ffb84f4a306f37306e12f87743a4aeb77e4 # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Buildfile: 


block-flat-fonts:

check-compiler-home:

check-typedefs-home:

thirdparty-clean:

thirdparty-clean:

pixelbender-clean:

swfobject-clean:

flat-ui-clean:

gcl-clean:
 [echo] Deleting Google Closure Library

clean:

examples-clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

BUILD FAILED
:630:
 The following error occurred while executing this line:
:163:
 Basedir 

 does not exist

Total time: 0 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

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.

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

[Christofer Dutz]

Hi Alex,

I had another look ... I think the version skips one is in step 001a ...
There the job checks out develop, applies the update to the new version of the 
build tools and jburg types, but then this is pushed and then again to the 
release branch (hereby overwriting the old release-branch) ... I'll try out a 
way with cherry picking the change from develop into the release branch. 
Unfortunately I haven't been able to find where the text in the emails comes 
from ... 

I'm talking about the order of the constants in the class ProblemID. I forced 
that to be sorted now. That's why we have to re-release the build tools.

Chris

Am 24.03.20, 08:14 schrieb "Alex Harui" :

Re: credentials:  Feel free to disable the credential store.   I did not 
have to both login and go through 2fa to Git Push.  There is some long 
password/token/credential/hash-like thing you get when you sign up with Apache 
Git that seems to work when you use it as a password.

Re: the utils steps.  I just looked and it appears that 
compiler-jburg-types and compiler-build-tools are no longer child/submodules of 
the root pom.xml in royale-compiler.  So now I get how why the development 
version won't get bumped up twice.  I think the way it was working may be that 
the updated dev version never got pushed to develop.  If you are satisfied with 
that setup, that's fine with me.  So then it might make more sense to get rid 
of 1a and create a whole new set of steps for each of compiler-jburg-types and 
compiler-build-tools.  If I understand correctly, those new steps would run mvn 
release:branch, mvn release:prepare and mvn release:perform in 
compiler-jburg-types or compiler-build-tools, stopping if there are interim 
pushes that need to be done, then start their own vote emails by copying other 
CI steps.

I use a Mac and thought I got all binaries to match from the .  I'm not 
sure what properties you are referring to.

I'm done for tonight.  Will catch up in my morning.

-Alex

On 3/23/20, 11:15 PM, "Christofer Dutz"  wrote:

Good morning all,

well I didn't disable anythig as I didn't want to break anything. So I 
thought before simply changing something I'd ask first.
So I would consider it a "bug" that it's there and when we continue 
today, we'll try to find out and disable the thing.
However I would assume then the RM will not only have to do his usual 
login but also the 2fa thing at every step too, correct?

And, just a kindly meant question ... would it be possible to reply at 
the top instead of inline? I sort of have missed several 
Of your Inline comments in the past as at least in my mail client it's 
hard to spot what's mine and what's not. 
(I could start counting spaces)

(I first missed this question of yours ... but discovered it after 
counting spaces ;-) )

Well to release the build tool with maven you would simply do the:
mvn release:prepare
mvn release:perform
for each of them, then adjust the main pom and do the mvn 
release:branch ... then prepare and perform after that.

Currently also jburg types and the build-tools are sort of released in 
parallel. With maven you would simply release only the module that's needed to 
be released. In our case build-tools would have been enough.

Speaking of build-tools ... are you possibly using Windows as OS on 
your system? Just asking because the build-tools seem to have always generated 
a sorted set of properties on windows and an unsorted one on Mac (Seems to be 
differences in the way the filesystem works) ... in that case it would have 
been impossible to have a release manager not using Java 8 on a Windows 
machine. (My changes recently never touched this)

Chris


Am 23.03.20, 22:59 schrieb "Alex Harui" :



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 login, it 
saves them in the password manager thingy of windows.

Did you try to disable the password manager?

It is true that I took those two out of the main maven reactor, 
but that's actually a good practice. In plc4x we setup a dedicated git repo for 
releasing these build tools. I have never seen any good coming from the old 
setup (I know ... I did it, but I learnt a lot). 

I am not opposed to moving those two projects to a different repo.  
It would require that we have a truly separate release vote for them, so more 

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

[Alex Harui]

Re: credentials:  Feel free to disable the credential store.   I did not have 
to both login and go through 2fa to Git Push.  There is some long 
password/token/credential/hash-like thing you get when you sign up with Apache 
Git that seems to work when you use it as a password.

Re: the utils steps.  I just looked and it appears that compiler-jburg-types 
and compiler-build-tools are no longer child/submodules of the root pom.xml in 
royale-compiler.  So now I get how why the development version won't get bumped 
up twice.  I think the way it was working may be that the updated dev version 
never got pushed to develop.  If you are satisfied with that setup, that's fine 
with me.  So then it might make more sense to get rid of 1a and create a whole 
new set of steps for each of compiler-jburg-types and compiler-build-tools.  If 
I understand correctly, those new steps would run mvn release:branch, mvn 
release:prepare and mvn release:perform in compiler-jburg-types or 
compiler-build-tools, stopping if there are interim pushes that need to be 
done, then start their own vote emails by copying other CI steps.

I use a Mac and thought I got all binaries to match from the .  I'm not sure 
what properties you are referring to.

I'm done for tonight.  Will catch up in my morning.

-Alex

On 3/23/20, 11:15 PM, "Christofer Dutz"  wrote:

Good morning all,

well I didn't disable anythig as I didn't want to break anything. So I 
thought before simply changing something I'd ask first.
So I would consider it a "bug" that it's there and when we continue today, 
we'll try to find out and disable the thing.
However I would assume then the RM will not only have to do his usual login 
but also the 2fa thing at every step too, correct?

And, just a kindly meant question ... would it be possible to reply at the 
top instead of inline? I sort of have missed several 
Of your Inline comments in the past as at least in my mail client it's hard 
to spot what's mine and what's not. 
(I could start counting spaces)

(I first missed this question of yours ... but discovered it after counting 
spaces ;-) )

Well to release the build tool with maven you would simply do the:
mvn release:prepare
mvn release:perform
for each of them, then adjust the main pom and do the mvn release:branch 
... then prepare and perform after that.

Currently also jburg types and the build-tools are sort of released in 
parallel. With maven you would simply release only the module that's needed to 
be released. In our case build-tools would have been enough.

Speaking of build-tools ... are you possibly using Windows as OS on your 
system? Just asking because the build-tools seem to have always generated a 
sorted set of properties on windows and an unsorted one on Mac (Seems to be 
differences in the way the filesystem works) ... in that case it would have 
been impossible to have a release manager not using Java 8 on a Windows 
machine. (My changes recently never touched this)

Chris


Am 23.03.20, 22:59 schrieb "Alex Harui" :



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 login, it 
saves them in the password manager thingy of windows.

Did you try to disable the password manager?

It is true that I took those two out of the main maven reactor, but 
that's actually a good practice. In plc4x we setup a dedicated git repo for 
releasing these build tools. I have never seen any good coming from the old 
setup (I know ... I did it, but I learnt a lot). 

I am not opposed to moving those two projects to a different repo.  It 
would require that we have a truly separate release vote for them, so more work 
in that regard, and the Ant build would have to be adjusted to download those 
jars.  I'm not sure now is the time to make that change, but maybe.  Let's see 
what others think.

Regarding the banches ... we did a git status after step 001a (the 
utils step) and indeed it was done on develop. As the maven release isn't doing 
any selecting and switching of branches it must have always been this way. If 
not the utils release versions would only be updated in the release branch and 
not develop. I couldn't find any cherry picking of commits in the process.

Well in the end the steps are way more complicated than I would be 
doing on my local machine. Especially this tolling around checking out branches 
and tagging and pushing is pretty complicated, in my opinion. Especially as 
most the stuff is fully automated.

The 

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

[Christofer Dutz]

Good morning all,

well I didn't disable anythig as I didn't want to break anything. So I thought 
before simply changing something I'd ask first.
So I would consider it a "bug" that it's there and when we continue today, 
we'll try to find out and disable the thing.
However I would assume then the RM will not only have to do his usual login but 
also the 2fa thing at every step too, correct?

And, just a kindly meant question ... would it be possible to reply at the top 
instead of inline? I sort of have missed several 
Of your Inline comments in the past as at least in my mail client it's hard to 
spot what's mine and what's not. 
(I could start counting spaces)

(I first missed this question of yours ... but discovered it after counting 
spaces ;-) )

Well to release the build tool with maven you would simply do the:
mvn release:prepare
mvn release:perform
for each of them, then adjust the main pom and do the mvn release:branch ... 
then prepare and perform after that.

Currently also jburg types and the build-tools are sort of released in 
parallel. With maven you would simply release only the module that's needed to 
be released. In our case build-tools would have been enough.

Speaking of build-tools ... are you possibly using Windows as OS on your 
system? Just asking because the build-tools seem to have always generated a 
sorted set of properties on windows and an unsorted one on Mac (Seems to be 
differences in the way the filesystem works) ... in that case it would have 
been impossible to have a release manager not using Java 8 on a Windows 
machine. (My changes recently never touched this)

Chris


Am 23.03.20, 22:59 schrieb "Alex Harui" :



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 login, it saves 
them in the password manager thingy of windows.

Did you try to disable the password manager?

It is true that I took those two out of the main maven reactor, but 
that's actually a good practice. In plc4x we setup a dedicated git repo for 
releasing these build tools. I have never seen any good coming from the old 
setup (I know ... I did it, but I learnt a lot). 

I am not opposed to moving those two projects to a different repo.  It 
would require that we have a truly separate release vote for them, so more work 
in that regard, and the Ant build would have to be adjusted to download those 
jars.  I'm not sure now is the time to make that change, but maybe.  Let's see 
what others think.

Regarding the banches ... we did a git status after step 001a (the 
utils step) and indeed it was done on develop. As the maven release isn't doing 
any selecting and switching of branches it must have always been this way. If 
not the utils release versions would only be updated in the release branch and 
not develop. I couldn't find any cherry picking of commits in the process.

Well in the end the steps are way more complicated than I would be 
doing on my local machine. Especially this tolling around checking out branches 
and tagging and pushing is pretty complicated, in my opinion. Especially as 
most the stuff is fully automated.

The Maven Release plugin automatically pushes and signs, so yes, the CI 
steps are more complicated because they have to continue on, but if there is a 
better way to stop and continue, let us know what that is.  But I was mainly 
addressing the branch/version issue for those two "utils" projects.  What would 
be the correct set of Maven Release commands to manage that locally without 
updating the develop version twice?  Or maybe as you mention above, there 
really is no good way and a separate repo is essentially the only way.

I think we managed to get the steps 1-4 (including the utils stuff) 
working again, while keeping the cleanup I did a while ago. 

I hope tomorrow it'll be simper to adjust the typedefs and the 
framework part. 

One thing we did notice however that even after addressing the memory 
issues, the build sometimes simply stuck and the build wouldn't continue. 
In these cases simply killing the job (and the processes on the CI 
server) didn't really help much ... we then had to reboot the machine in order 
to continue. I think we rebooted the thing 5-6 times today.

My experience was that the Jenkins slave would occasionally disconnect and 
the job would fail right away.  Rebooting didn’t help.  I didn't see it get 
stuck so unfortunately you are seeing something new that I haven't seen.  Did 
you search the internet to see if anyone else reported something similar with 
Jenkins?

Signing off for today,