Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `find' for nil:NilClass #21

Closed
ikus060 opened this issue Jan 30, 2016 · 8 comments

Comments

@ikus060
Copy link

ikus060 commented Jan 30, 2016

This problem seams to happen after an upgrade in Jenkins or Gitlab. I don't know which one since I didn't track the upgrade. My mistake.

See log in attachment.
jenkins.txt

GitLab Community Edition 8.4.0 1b1c0ba
Jenkins ver. 1.644
Gitlab Hook Plugin 1.4.1.1

Thanks for help

@javiplx
Copy link

javiplx commented Feb 1, 2016

From the line with the error, looks looks related with parametrization. Are you using in any of your rdiffweb* repos a parametrized branch name?
Not sure, but your error might happen if you use a git branch with a parameter but the project has no parameter defined. If that were the case, just appending or [] to line 98 of models/values/project.rb should work

@ikus060
Copy link
Author

ikus060 commented Feb 1, 2016

I've recently create a new project with parameters, but it's not related to
Yep, I've recently create a new project with parameters. But it's not related to the repo git.patrikdufresne.com:pdsl/rdiffweb.git.

Also, none of the repo listed in the logs is parametrized.

@javiplx
Copy link

javiplx commented Feb 1, 2016

In any case, the fix I propose should work. Can you test it?
And if you could send me the config.xml for the rdiff* jobs, it might help to actually find the issue, even if the workaround works as expected.

@ikus060
Copy link
Author

ikus060 commented Feb 1, 2016

ha ha, just to make sure, I've double-check each project configuration. One of them was parameterized, but without a parameter :S.

Anyway, I've fix the configuration and it's working again.

@ikus060
Copy link
Author

ikus060 commented Feb 1, 2016

Thanks for you help and time !

@javiplx
Copy link

javiplx commented Feb 4, 2016

Could you explain me what change did you perform in the job? When trying to issue a warning for a case like yours, I've realized that a project without parameters should never reach the line with your exception, because the protection I wanted to introduce was already there.

@javiplx
Copy link

javiplx commented Feb 9, 2016

Forget my question. Looking again I see the issue now. At one place it checks if project is parametrized, that it does not mean that it has any parameter, which is the error reason. Now that I've seen it, I'll fix it and issue a warning to logfile

@javiplx javiplx closed this as completed Feb 9, 2016
@inforedaster
Copy link

Hi what's the environment variable mean the branche name it is ${branch}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants