+1 such change should be listed, with some flag/color to mark them "ignored path"
2014-11-29 12:32 GMT+01:00 Mark Waite <[email protected]>: > I prefer that the changes list shows all changes that were included in a > build. I think that the excluded paths are part of the commit history of > the repository and should be visible in the changes list. > > Having all changes visible in the changes list is also (for me) a > safeguard in those cases when I made a mistake in the exclusion or > inclusion regular expression. I've had cases where all changes visible in > the change list were the exact hint I needed to investigate why polling did > not detect a certain change that I expected to be visible. > > Mark Waite > > On Wed, Nov 26, 2014 at 3:00 AM, Pavel Baranchikov < > [email protected]> wrote: > >> Hello. >> >> I do not know, what behaviour should be the best for changes view for a >> build. I suggest to show only the changes, that are not excluded from >> polling. As for me, we have mulriple projects in the same Git repository. >> Build of a single project shows multiple changes, most of the (all except >> one) are changes in excluded paths, so they really do not affect the >> current build. >> >> >> - I suppose, that the default behaviour should not show the changes >> from excluded paths in the changes view >> - I suggest ro add additional Git option (disabled by default) to >> show all the changes. >> - Additional quetion is whether to include changes from ignored users >> and commits with ignored messages. I think, they should be shown. >> >> Could you please post here your oppinions on the subject. >> >> Best regards, >> Pavel. >> >> -- >> 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/6cf069a6-6d6a-44a5-8400-7a078b421147%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/6cf069a6-6d6a-44a5-8400-7a078b421147%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Thanks! > Mark Waite > > -- > 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/CAO49JtHfJq%2BvxCvKQQhZr_2-Y2ZrJji-1LV_EH51sz0ThO-%2Bhg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHfJq%2BvxCvKQQhZr_2-Y2ZrJji-1LV_EH51sz0ThO-%2Bhg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CANMVJzkqVr2yHqqtMMr3gsi4ZH5N0k%3DsHVz_URYv7m8%3DWD372w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
