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

2020-03-24 Thread Alex Harui
I'm not quite sure whether the problem you want to solve is that the timestamp of ZipFileEntru is not matching or the timestamps in the catalog.xml are not matching. I could be wrong, but I believe ZipFileEntry problem is different from what is described in the linked article. IIRC, the issue

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

2020-03-24 Thread 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 cal

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

2020-03-24 Thread 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 re

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

2020-03-24 Thread Christofer Dutz
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 search

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

2020-03-24 Thread 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/2

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

2020-03-24 Thread 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. Chri

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

2020-03-24 Thread 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

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

2020-03-24 Thread 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

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

2020-03-24 Thread 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?

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

2020-03-24 Thread 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

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

2020-03-24 Thread 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

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

2020-03-24 Thread 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) .

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

2020-03-24 Thread 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 step

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

2020-03-23 Thread 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

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

2020-03-23 Thread 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 l

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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