search

History-Research-Environment / HRE--History-Research-Environment

Main repo for HRE code
https://historyresearchenvironment.org/
GNU Affero General Public License v3.0
32 stars 6 forks source link

Display Build Date to the user #35

Closed MichaelErichsen closed 4 years ago

MichaelErichsen commented 6 years ago

This could make error reporting and debugging easier.

Suggestions on how to do it in https://rterp.wordpress.com/2012/03/16/stamping-version-number-and-build-time-in-properties-file-with-maven/

ricko2001 commented 6 years ago

Build timestamp is fine, but please also : tag the git repo with the build number/timestamp and include the git commit sha in the build a well.

I think it is critical that each build used for testing by anyone except the developer be done from a completely defined set of files and procedures saved in the git repo. (sorry if this is obvious)

On Sun, Jun 24, 2018 at 2:09 AM Michael Erichsen notifications@github.com wrote:

This could make error reporting and debugging easier.

Suggestions on how to do it in

https://stackoverflow.com/questions/11202354/eclipse-java-how-to-insert-a-build-timestamp

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/History-Research-Environment/HRE--History-Research-Environment/issues/35, or mute the thread https://github.com/notifications/unsubscribe-auth/ATcR-D7f-qj7gjjlQ9SW7fZJyuF3Xargks5t_1dFgaJpZM4U1FRz .

MichaelErichsen commented 6 years ago

Hi

This is definitely not obvious to me. I would be grateful to be advised on how best to do this.

ricko2001 commented 6 years ago

It's all part of setting up a build system. Perhaps it's too early to worry about now, but I think it should be in place by the time non-developers start testing. The goal is to create a repeatable build process without manual steps so that there is an absolute link between the final build product and the source code and tools used to create it.

Write a "Build Script" in a scripting language that will-

The app's about box could then display the sha value and timestamp.

For C++ builds, the build script updates a .h file so the app has access to the variable defined at build time (like the time stamp and git sha). For C# builds, the build script updates custom attributes in the AssemblyIno.cs file.

on another matter- Any idea how you will be affected by the recent Java licensing roadmap put out by Oracle?

On Sun, Jun 24, 2018 at 12:02 PM Michael Erichsen notifications@github.com wrote:

Hi

This is definitely not obvious to me. I would be grateful to be advised on how best to do this.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/History-Research-Environment/HRE--History-Research-Environment/issues/35#issuecomment-399779425, or mute the thread https://github.com/notifications/unsubscribe-auth/ATcR-EE1TwiWlvQogqp-F_5Adb1ke-6Eks5t_-JXgaJpZM4U1FRz .

HREferg commented 6 years ago

Certainly a (single) build version no. of HRE placed somewhere easily found will make a lot of sense for test/debug work.

Don

HREferg commented 4 years ago

Closed - performed in Help About screen in current Build of HRE