mphilipps

I looks I'm also encountering this issue in 4.10.1 Jenkins using the dependency-Track plugin tries to push a new BOM in the post build action, which fails with a 500....

Also something to note: The code above it doesn't work. ( ) creates a subshell and **exit** just exits the subshell and continues with the base script.

Thanks, but how is this considered a feature? Logged in users keeping there permissions indefinitely is intended? The ideal solution and this I would agree is a feature/enhancement would be...

Just run into the same issue when trying to trigger a check now for ~800 services. Are there any plans to fix this? Apparently this bug report is almost 5...