> > > "The pipeline will behave as you defined it, rather than artificial > constraints designed for freestyle jobs" will not make a good warning. > > Agreed :) I was more thinking about something like 'Warning: Recorder xxx is configured to run after Notifier yyy, which might result in unexpected results'.
To me it is more about making sure that a Jenkins user has a direction to search when something behave abnormally, without having to go to the plugin source code to check if the plugin is marked as a Recorder or a Notifier, which is today the only way to diagnose for certainty that something is wrong with the definition used. The fact that we have issues reported about incorrect behaviors of plugins is also a sign that it is not matching users expectations. At the very least, it means the javadoc is incorrect, and that plugins developers are developing publishers with incorrect assumptions. -- 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/9ce87243-6b7c-455d-8ef2-e03f0c7127af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
