[JIRA] [scm-sync-configuration-plugin] (JENKINS-27591) Improve performance of initial scan by narrowing the job config pattern

Thu, 26 Mar 2015 13:52:50 -0700

In JENKINS-19659, I was planning to disable strategies one by one (job strategies, standard config strategies, etc..)

Anyway, I don't understand your assumption :

If I understand the current suggestion in JENKINS-19659 and the SCM Sync Configuration Plugin source code, such a solution would have the drawback of losing the following functionality:

  • the SCM Sync status footer
  • detailed commit messages
  • the ability to customize commit messages

I don't think we would have this drawback.
What made you make this assumption?
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/d/optout.

Reply via email to