Thanks for the report! My guess for the reason for the slowdown is that when you ran builds triggered by users as the triggering user using Authorize Project Plugin, permission checks during the course of the build had to interact with your security realm and authorization strategy to figure out what permissions the user had based on your configuration. Builds that are triggered automatically run as the Jenkins SYSTEM user, which always has all permissions, and so permission checks are very quick. Maybe you could configure more aggressive caching or optimize your LDAP settings or something to improve the performance, depends on how things are configured in your instance. You could take thread dumps while the Pipeline is running slowly and see where threads are usually blocked to confirm/deny my hypothesis. I'm not sure about the warning. Perhaps the slowdown is significant enough to cause the relevant code to time out. If you aren't seeing it once you remove Authorize Project Plugin, I think you can safely ignore it. I'm going to close this issue, if you get thread dumps and think there is a bug somewhere based on that data, feel free to reopen it. |