-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NullPointerException return value of "hudson.model.View.getOwner()" is null #323
Comments
@zisuu I am facing the similar issue on folder that have VaultAwsIamCredentials with error 'CannotResolveClassException: currentClientToken' as in latest code currentClientToken field is removed from src/main/java/com/datapipe/jenkins/vault/credentials/AbstractVaultTokenCredentialWithExpiration.java. |
I am facing the same issue after updating to the latest version of the Vault Jenkins plugin [364.vf5d54b_3dc313] where when I go to some folders I cant see any jobs in the folder. I'm also willing to test any potential fixes if needed. |
Downgrading to a version prior to the above mentioned fixed the issue for us. |
With
|
In my case i just resolve it in
After update to 364.vf5d54b_3dc313 this line has been removed, but if you revert it and restart - you may to resolve problem |
A fix was created: #325 |
Maybe root cause for my problem is quite different from original message. If I stop Jenkins, remove tokenExpiry from config.xml, start Jenkins, error goes away on Downgrading to |
Ya config.xml would still fail but it should prevent the error from coming back when saving/creating a folder. What if you create a new folder and see if |
Co-authored-by: saville <[email protected]>
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Reproduction steps
Expected Results
Jobs in the folder or view were shown and listed
Actual Results
for some Jobs:
for some views:
we have around 100 Job Folders, most of them are unaffected of this issue. We've seen this only on a few (7-8 jobs/views) so far.
Anything else?
or
Are you interested in contributing a fix?
We're open to test any potential fix for this.
The text was updated successfully, but these errors were encountered: