Bug 55550 - No last updated line in the HTML builds because of too shallow git repository during build
No last updated line in the HTML builds because of too shallow git repository...
Status: NEW
Product: UCS manual
Classification: Unclassified
Component: General
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Docu maintainers
Docu maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2023-01-09 18:03 CET by Nico Gulden
Modified: 2023-02-01 06:44 CET (History)
2 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Gulden univentionstaff 2023-01-09 18:03:52 CET
The GitLab build process uses a shallow Git repository per default. When the build process can't determine the last change to a file from the git repository, the HTML build doesn't have a last updated line for that page.

The HTML build job needs to use a full clone of the repository to determine the timestamp.
Comment 2 Ingo Steuwer univentionstaff 2023-01-09 18:14:39 CET
Maybe a commit hook [1] can be introduced which identifies the latest commit timestamp at "push" time and writes it into a file?


[1] not sure if "commit hook" is the right wording, I think of some code that runs server side with each "git push"
Comment 3 Nico Gulden univentionstaff 2023-01-10 09:10:21 CET
There is at least one extension for Sphinx that determines the timestamp for each file from the Git history. I'd like to try all possibilities with this approach first, before I choose the path of an own implementation.
Comment 4 Philipp Hahn univentionstaff 2023-02-01 06:44:35 CET
(In reply to Ingo Steuwer from comment #2)
> Maybe a commit hook [1] can be introduced which identifies the latest commit
> timestamp at "push" time and writes it into a file?

Please no: our build infrastructure should remain stateless.
And please try to not add any custom implementation someone has to maintain.