-
New Feature
-
Resolution: Won't Do
-
Major
-
None
Hello,
We have an issue internally that requires us to set the hash revision of a merge commit.
We found out that if we set the env variables GIT_AUTHOR_DATE and GIT_COMMITTER_DATE it will be possible. When we do this locally, it works. But when we try to do the same on Jenkins in a Pull Request build it doesn't work.
I've added the Jenkinsfile as attachment.
So it seems that the git plugin is ignoring the env variables when doing the automatic commit for the PR build. We also made sure that the env variables are set by priting them Can this be improved by letting the plugin read those two variables?
Thank you. If you need more information please let me know.
[JENKINS-73050] Env variables GIT_AUTHOR_DATE and GIT_COMMITTER_DATE being ignored
Marco
created issue -
Marco
made changes -
| Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Marco
made changes -
| Attachment | Original: consoleText.txt [ 62479 ] |
Marco
made changes -
| Description |
Original:
Hello,
We have an issue internally that requires us to set the hash revision of a merge commit. We found out that if we set the env variables GIT_AUTHOR_DATE and GIT_COMMITTER_DATE it will be possible. When we do this locally, it works. But when we try to do the same on Jenkins in a Pull Request build it doesn't work. I've added the Jenkinsfile and console output as attachments. So it seems that the git plugin is ignoring the env variables when doing the automatic commit for the PR build. We also made sure that the env variables are set by priting them Can this be improved by letting the plugin read those two variables? Thank you. If you need more information please let me know. |
New:
Hello,
We have an issue internally that requires us to set the hash revision of a merge commit. We found out that if we set the env variables GIT_AUTHOR_DATE and GIT_COMMITTER_DATE it will be possible. When we do this locally, it works. But when we try to do the same on Jenkins in a Pull Request build it doesn't work. I've added the Jenkinsfile as attachment. So it seems that the git plugin is ignoring the env variables when doing the automatic commit for the PR build. We also made sure that the env variables are set by priting them Can this be improved by letting the plugin read those two variables? Thank you. If you need more information please let me know. |
| Assignee | Original: Mark Waite [ markewaite ] |
| Resolution | New: Won't Do [ 10001 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |