It wouldn't be so bad if renaming of jobs would just not work with the Git backend. But what I'm seeing is that in case of renaming a job all files below jobs/<new_job_name> including all builds and the complete workspace get committed to the Git repository that is supposed to just hold the changes to configuration files. As a result, the Git repository size has grow to over 7 GiB for our project. Given this, I'd say this is a blocker.

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

Reply via email to