Add finished date to copy_reference_file.log

[jonesbusy]

I'm unvestigating some issue with one of my controller that the copy reference function take much more time that usual. It's probably due to something in my infra.

In order to compare timeout I would like to have the end date/time when reference are copied into the volume.

The copy_reference_file.log already contains the start date/time and would be useful to also have the end time

Testing done

Didn't test but I don't expect any side effect for adding a log

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[MarkEWaite]

Isn't that information already available from the last modified date of the file?

I don't object to writing the date to the log as well, but it seems that you can already obtain that information with either stat or ls-L. A stackoverflow article discusses the complexities of file modification times

[jonesbusy]

I'm also interested by the history (when the container is upgraded/recreated). It's personally also easier for me to just grab all the log file and perform some comparaison across my controller

[jonesbusy]

This was caused by many service in one of my namespace causing slowing then bash environment contains too much environment variables

I've open a PR on jenkinsci/helm-charts#1191 to allow disable service links if required