[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading

2014-06-13 Thread f...@wizcorp.jp (JIRA)














































Frank Lee
 updated  JENKINS-23415


2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
















Change By:


Frank Lee
(13/Jun/14 7:09 AM)




Description:


Problem:Ajobkeepstriggeringwhenitshouldnot.Background:2separatejobsareconfiguredtobetriggeredonthesameGithubrepositorydependingonbranchthatpushedto.Whenpushingtothe1stbranch,origin/test/branch1,the1stjobistriggered.Good.Whenpushingtothe2ndbranch,origin/test/branch2,the2ndjobtriggers.Good.Butthe1stjobistriggeredagain.Bad.Theresonlybeen2pushes.Therepositoryisverylarge,sothegitclonetakesafewminutesforbothjobs.Theproblemconsistentlyoccurswhenpushingtothe1stbranch,THENimmediatelypushingtothe2ndbranch.The1stjobistriggeredandgitcloning.Andthe2ndjobistriggeredandqueued.BUTanother1stjobistriggeredandqueued.Seemstohappenwhenitsstilldownloadingduringtheclone.Thatextratriggeredjobiscausingusgrief,becauseitsusedfordeployments.Thisisreproducibleconsistentlywiththisscript:#!/bin/bashpushdmydirectorygitcheckoutdevelopecho${1}dd.txtgitadd.gitcommit-m${1}dgitpushgitcheckouttest/branch1gitpull--no-editupstreamdevelopgitpushgitcheckouttest/branch2gitpull--no-editupstreamtest/branch1gitpushpopdAndrunitas:#./script1#./script2etc...Jenkinsv1.558GitClientv1.9.0Gitpluginv2.2.1GitHubAPIv1.44GithubOAuthv0.14GitHubPullRequestBuilder1.12
GitHubpluginv1.8



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading

2014-06-13 Thread f...@wizcorp.jp (JIRA)














































Frank Lee
 commented on  JENKINS-23415


2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading















I edited the original post to add one more plugin: "GitHub plugin v1.8".
I'm guessing the GitHub payloads are triggered with that plugin.
If there's anything else I can do to move this issue forward, let me know.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading

2014-06-12 Thread f...@wizcorp.jp (JIRA)














































Frank Lee
 created  JENKINS-23415


2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git, git-client, github, github-api, github-oauth



Created:


12/Jun/14 10:58 AM



Description:


Problem:
A job keeps triggering when it should not.

Background:
2 separate jobs are configured to be triggered on the same Github repository depending on branch that pushed to.

When pushing to the 1st branch, "origin/test/branch1", the 1st job is triggered. Good.
When pushing to the 2nd branch, "origin/test/branch2", the 2nd job triggers. Good.
But the 1st job is triggered again. Bad. There's only been 2 pushes.

The repository is very large, so the git clone takes a few minutes for both jobs.

The problem consistently occurs when pushing to the 1st branch, THEN immediately pushing to the 2nd branch. The 1st job is triggered and git cloning. And the 2nd job is triggered and queued. BUT another 1st job is triggered and queued.

Seems to happen when it's still downloading during the clone.

That extra triggered job is causing us grief, because it's used for deployments.

This is reproducible consistently with this script:



#!/bin/bash
pushd mydirectory
  git checkout develop
  echo ${1}d  d.txt
  git add .
  git commit -m "${1}d"
  git push 

git checkout test/branch1
git pull --no-edit upstream develop
git push

git checkout test/main
git pull --no-edit upstream test/branch2
git push
popd


And run it as:


	./script 1
	./script 2
etc...




Jenkins v1.558
Git Client v1.9.0
Git plugin v2.2.1
GitHub API v1.44
Github OAuth v0.14
GitHub Pull Request Builder 1.12




Environment:


CentOS 5, JDK 1.7




Project:


Jenkins



Labels:


jenkins
git
scm




Priority:


Major



Reporter:


Frank Lee

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading

2014-06-12 Thread f...@wizcorp.jp (JIRA)














































Frank Lee
 updated  JENKINS-23415


2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
















Change By:


Frank Lee
(13/Jun/14 1:50 AM)




Description:


Problem:Ajobkeepstriggeringwhenitshouldnot.Background:2separatejobsareconfiguredtobetriggeredonthesameGithubrepositorydependingonbranchthatpushedto.Whenpushingtothe1stbranch,origin/test/branch1,the1stjobistriggered.Good.Whenpushingtothe2ndbranch,origin/test/branch2,the2ndjobtriggers.Good.Butthe1stjobistriggeredagain.Bad.Theresonlybeen2pushes.Therepositoryisverylarge,sothegitclonetakesafewminutesforbothjobs.Theproblemconsistentlyoccurswhenpushingtothe1stbranch,THENimmediatelypushingtothe2ndbranch.The1stjobistriggeredandgitcloning.Andthe2ndjobistriggeredandqueued.BUTanother1stjobistriggeredandqueued.Seemstohappenwhenitsstilldownloadingduringtheclone.Thatextratriggeredjobiscausingusgrief,becauseitsusedfordeployments.Thisisreproducibleconsistentlywiththisscript:#!/bin/bashpushdmydirectorygitcheckoutdevelopecho${1}dd.txtgitadd.gitcommit-m${1}dgitpushgitcheckouttest/branch1gitpull--no-editupstreamdevelopgitpushgitcheckouttest/
main
branch2
gitpull--no-editupstreamtest/
branch2
branch1
gitpushpopdAndrunitas:#./script1#./script2etc...Jenkinsv1.558GitClientv1.9.0Gitpluginv2.2.1GitHubAPIv1.44GithubOAuthv0.14GitHubPullRequestBuilder1.12



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading

2014-06-12 Thread f...@wizcorp.jp (JIRA)














































Frank Lee
 commented on  JENKINS-23415


2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading















Thank you for the quick reply!

Sorry, the branches in my original post with the last "git checkout" and "git pull" was wrong. I've corrected the branches above. It's pulling the "develop" branch into "test/branch1". Then pulling "test/branch1" into "test/branch2".

Could you try that to see if it's reproducible?

Not sure if it makes a difference, but instead of polling, I'm using githhub-webhook on the Github repo. So pushes to the Github repo triggers Github to send payloads to the Jenkins server.

Details on the configuration of the job for branch1 are:

	"Discard Old Builds" is checked
	"Max # of builds to keep" is set to 50
	"Enable project-based security" is set.
	"GitHub project" is set with the URL of the github repo.
	"HipChat Notifications" is set with the Project Room.
	"Restrict where this project can be run" is set with "Label _expression_" set to "master".
	"Source Code Management" is set with "Git" selected. In that section the following are set:
	
		"Repository URL" has the ssh URL from Github.
		"Credentials" is set to none.
		"Branch Specifier" is set to "origin/test/branch1"
		"Additional Behaviours" has "Advanced sub-modules behaviours" set with "Disable submodules processing" checked.
	
	
	"Build Triggers" has "Build when a change is pushed to GitHub" checked.
	"Build Environment" has "Delete workspace before build starts" and "Color ANSI Console Output" both checked.
	"Build" has "Execute shell" with a shell script to do stuff for branch1.
	The "Post-build Actions" has HipChat and email notification.




Details for the job for branch2 are the exact same, except for:

	"Branch Specifier" is set to "origin/test/branch2"




To add, originally, we wanted only 1 job by using regex as follows:

	"Branch Specifier" is set to "origin/test/**"



And in the "Execute shell" have "if GIT_BRANCH=branch1 then do...  if GIT_BRANCH=branch2 then do ...", which is more maintainable than maintaining multiple Jenkins jobs.

But with the 1 job with the regex, we're having the opposite problem. Instead of the job triggers an extra build, it's ignores subsequent triggers when the first build is running. So for example: when we push 2 or more times immediately while the job is running from the first push that triggered it, consecutive jobs won't queue up. The jenkins.log does show Jenkins receiving the webhook and poking the job, but the job just doesn't trigger. This is a separate problem, but I mention it because it may have some relationship to the original problem.

I'll try duplicating it in a test environment. And try testing 1.9.1.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading

2014-06-12 Thread f...@wizcorp.jp (JIRA)














































Frank Lee
 commented on  JENKINS-23415


2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading















Actually, I'd much prefer having the job with the regex work (e.g. queue up builds).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading

2014-06-12 Thread f...@wizcorp.jp (JIRA)














































Frank Lee
 updated  JENKINS-23415


2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
















Change By:


Frank Lee
(13/Jun/14 3:33 AM)




Labels:


git
github
scm



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading

2014-06-12 Thread f...@wizcorp.jp (JIRA)














































Frank Lee
 commented on  JENKINS-23415


2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
















To have the job queue multiple builds, you might try the "allow concurrent builds" check box, in hopes that would not optimize away the second request to build.
That's a interesting idea. Unfortunately in this case, the job isn't made to run concurrently, else the concurrent builds will step on each other.


I removed the GitHub components from the bug report because I assumed it was generic to the git client plugin. You'll probably need to put them back, or confirm that you can see the problem without requiring a GitHub push notification.
Since it's going through the GitHub component because "Build when a change is pushed to GitHub" is checked and I'm not sure how to reproduce this problem without having GitHub push notification setup, I've added them back.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [cli] (JENKINS-21086) jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown

2014-04-25 Thread f...@wizcorp.jp (JIRA)














































Frank Lee
 commented on  JENKINS-21086


jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown















This is also occurring with Jenkins v1.558.

I have the same error as well with delete-job command. The Jenkins server authenticates with LDAP. When no permissions are allowed for Anonymous, the same error occurs. When Overall Read permissions is applied to Anonymous, a "java.lang.NullPointerException" error occurs.


Command:
java -jar /usr/lib/jenkins/jenkins-cli.jar -s http://localhost:8080 delete-job blah-job --username admin --password mypassword

Permissions:
no permissions are allowed for Anonymous

Error:
hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission
	at hudson.security.ACL.checkPermission(ACL.java:54)
	at hudson.model.Node.checkPermission(Node.java:418)
	at hudson.cli.declarative.CLIRegisterer$1.main(CLIRegisterer.java:180)
	at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92)
	at sun.reflect.GeneratedMethodAccessor409.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63)
	at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95)
	at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)


Same command again with "Overall Read" permissions applied to Anonymous


java.lang.NullPointerException
	at hudson.model.AbstractItem.resolveForCLI(AbstractItem.java:677)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at hudson.cli.declarative.MethodBinder.call(MethodBinder.java:102)
	at hudson.cli.declarative.CLIRegisterer$1.main(CLIRegisterer.java:185)
	at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92)
	at sun.reflect.GeneratedMethodAccessor409.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63)
	at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95)
	at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA 

[JIRA] [cli] (JENKINS-21086) jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown

2014-04-25 Thread f...@wizcorp.jp (JIRA)














































Frank Lee
 commented on  JENKINS-21086


jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown















Found a workaround. Instead of using the jenkins-cli.jar, use curl:

curl -u admin:mypassword -fs --data "" "http://localhost:8080/job/blah-job/doDelete"

This works with no permissions given to Anonymous. Hopes this helps someone out there.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [ghprb] (JENKINS-22550) GHPRB NoSuchMethodError

2014-04-09 Thread f...@wizcorp.jp (JIRA)














































Frank Lee
 commented on  JENKINS-22550


GHPRB NoSuchMethodError















I have also upgraded to Jenkins v1.558 and GHPRB v1.11.2 and am getting the same error.
I have upgrade previously to Jenkins v1.557 and GHPRB v1.11.2 but did not get the error.

So I checked for differences between Jenkins 1.557 and 1.558.

Looks like there was a change to doCheckSpec as shown in this diff:
https://github.com/jenkinsci/jenkins/compare/jenkins-1.557...jenkins-1.558#diff-b96181c66eb8934a98153f7f6baeff05L74

I hope this helps getting this fixed quick!

Here's my error:


WARNING: Error while serving https://localhost:8080/view/PROJECTNAME/job/JOBNAME/descriptorByName/org.jenkinsci.plugins.ghprb.GhprbTrigger/checkCron
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at 

[JIRA] [ghprb] (JENKINS-22550) GHPRB NoSuchMethodError

2014-04-09 Thread f...@wizcorp.jp (JIRA)












































 
Frank Lee
 edited a comment on  JENKINS-22550


GHPRB NoSuchMethodError
















I have also upgraded to Jenkins v1.558 and GHPRB v1.11.2 and am getting the same error.
I have upgraded previously to Jenkins v1.557 and GHPRB v1.11.2 but did not get the same error.

So I checked for differences between Jenkins 1.557 and 1.558.

It looks like there was a change to doCheckSpec as shown in this diff:
https://github.com/jenkinsci/jenkins/compare/jenkins-1.557...jenkins-1.558#diff-b96181c66eb8934a98153f7f6baeff05L74

I hope this helps getting this fixed quick!

Here's my error:


WARNING: Error while serving https://localhost:8080/view/PROJECTNAME/job/JOBNAME/descriptorByName/org.jenkinsci.plugins.ghprb.GhprbTrigger/checkCron
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at