On Mon, Mar 7, 2016 at 8:02 AM, domi <[email protected]> wrote: > …and some might actually just change the labels…
For example https://github.com/jenkinsci/branch-api-plugin/blob/60c05e72532cd00e964090c82d01f86b977e9a33/src/main/java/jenkins/branch/MultiBranchProject.java#L618-L621 As Daniel pointed out, we have an existing `AlternativeUiTextProvider` API, and it is not hard to imagine similar pluggability whereby an SCM source could indicate the kind of term it prefers to be used for various repositories or branches it produces, etc. > if thing like this get implemented, then it would be wise > to have some kind of abstraction. That was the gist of my comment in the PR. That said, we need some polish quickly for the one source which is available in an OSS plugin today, GitHub. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr080iPywCRT4%2B8LD6ZbdJ-6YmRwxtyZSUX0pPADRTs6aA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
