My apologies, it wasn't the project we created yesterday. We'd been running the buggy build of Jenkins long enough that two of the other projects which depend on Sugar had their "build after" trigger updated recently.

Saving those fixed the issue.

There are two things that make this a nightmare to track down:

  • When the NPE occurs, there is no indication in the log of which project caused it
  • The build that experiences the NPE is marked as successful so we never see a notification that there is an issue

If we had that, this issue would be much easier to recover from.

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