Leon
Leon
same problem
I figured it out. You need to shade the -plugin and not -api version because the api version does not include the nms packages thus not finding the classes.
Same on our builds after upgrading from 866 to 874. Behavior of env.BRANCH_NAME was changed I think.
@andrey-fomin can you take a look if your changes are the issue here please?
@jglick is there any update on this? this is messing up a few of our build logs
> @schiasileon do you have some one-character passwords? > > …is it `x`? This mostly concerns us as we use a custom implementation that allows for multiline secrets from vault...
> Hi, Thanks for your PR, this is going to the right direction. I can reproduce the test failures locally as well. Can you look at those? Maybe it's possible...
@olamy Tests are now all passing
any feedback pls? @olamy
Hi, I cannot see where permissions would matter in this context. You are just looking for a Item the user already has access to to get cause of blockage. Please...