Hi Team,

Any updates?

TIA

ctmiller it is a great help if you provide the details requested in "How to report an issue" so that others are more likely to give their time to assist. I know that I am much more interested in helping people when they provide details like the specific plugin versions they are running.

I think that I was able to avoid the issue with the following steps:

1. Define the list of plugins and their versions in a plugins.txt file (using the script from "How to report an issue")
2. Create a run-jenkins.sh script that starts Jenkins and downloads those plugin versions
3. Run the run-jenkins.sh script and choose to install no additional plugins
4. Confirm that the issue is not reported

I am able to duplicate the issue with the following steps:

1. Perform the prior steps to create an initial installation
2. Disable the job config history plugin (or remove it) and restart Jenkins
3. Confirm that the issue is reported

The crucial step in the failure is to remove the job config history plugin that is an optional dependency of the mail watcher plugin. I don't know why an optional dependency would fail in that way, but the workaround seems to work (at least it avoids the error message)

The mail watcher plugin is up for adoption. If your organization depends on it, you should consider adopting the plugin, modernizing it, and releasing a new version. The plugin health score of the mail watcher plugin is only 76 / 100, so there is room for improvement for the plugin.

Hi Mark,

Apologies in advance - I was unaware of the "How to report an issue" resource before I created this ticket - I will use it as a reference going forward.

I've attached a plugins.txt file for reference AFTER applying the fix you suggested of adding the job config history plugin to both of my NPE controllers. I no longer see the Warning message in the err.log on Jenkins startup and node status emails for offline/online are once again working.  I'll continue to test but it looks good so far - thanks for the assist.

To be very honest I don't have time for adopting any new projects, and since this issue was limited only to the mail watcher plugin, I'm really the only one that cared enough to pursue a fix because I use it. If we can update the plugin docs to reflect this issue I hope the directions that you provided can help someone else if they share the same experience in their environment(s).

Please let me know if you need anything else from my side but I believe we should be good to close this issue as resolved.

Thanks ctmiller. I'd like to leave the issue open because installing an optional plugin is unexpected and is a workaround rather than fixing the root issue.

Sure markewaite - thanks again.