|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I noticed the same behavior over here: It would be nice if Jenkins would not replace the symlink with a newly written file but instead update the sylinked file. In my case the symlink points to a file in a subdirectory within the job's directory (which is part of a Git repository).