When TriggeringUsersAuthorizationStrategy is used for a build all read or write access to properties of currentBuild, like e.g. currentBuild.result throw AbortExceptions causing the complete build to abort.

This happens although the triggering user has full access to the folder/project using an item role with all permissions enabled. Everything in the buildjob works, only currentBuild access doesn't.

The only way to fix the problem is to grant global read access to the affected user, but this makes all item roles useless, because the user is then allowed to access anything.

Another simple fix is to build the job as SYSTEM which is also insecure.

The root cause of the problem is that the access to currentBuild properties should be allowed, but it isn't.