JENKINS-45085 captures the problem I was seeing. The multiple-scms plugin causes a null pointer exception in my multi-branch pipeline job when opening the configure URL of the job. That problem is visible with Jenkins 2.46.3 and 2.60.1.
Since my environment does not need or use the multiple-scms plugin, I removed it from my Docker image and resolved the problem. Mark Waite On Thursday, June 22, 2017 at 10:10:45 AM UTC-6, Mark Waite wrote: > > False alarm, or rather, accurate alarm that has nothing to do with the > alpha releases of the plugins. > > I see an NPE in the console log with the released versions of all plugins, > using Jenkins 2.46.3. It is an issue, but not an issue with the alpha > releases of the plugins. > > Mark Waite > > On Thursday, June 22, 2017 at 9:13:17 AM UTC-6, Mark Waite wrote: >> >> Sorry, fat fingers. >> >> I have a multi-branch pipeline job defined to read from >> https://github.com/MarkEWaite/git-client-plugin using Git with username >> / password credentials. It works as expected with the alpha versions of >> the plugins. When I "configure" that job, it shows the project repository, >> and shows the credentials as "MarkEWaite github username/password". >> >> I have a multi-branch pipeline job defined to read from >> https://github.com/MarkEWaite/git-client-plugin using GitHub with >> username / password credentials. It works as expected with the alpha >> versions of the plugins. However, when I configure that job, it shows the >> GitHub credentials box and then reports HTTP Error 404 - problem accessing >> job/Git-Client-Folder/job/git-client-pipeline-github/null : Reason: not >> found. >> >> I assume something is causing that trailing "null" on the end of the >> request URL, though I don't know what would do that. Is that likely >> related to the alpha versions of the plugins, or should I look elsewhere >> for the difference? >> >> Those two pipeline jobs are both able to be configured in my docker >> instance that runs released versions of all the plugins (except the git >> plugin and the git client plugin, which always seem to be in some >> pre-release state in that docker instance). >> >> Suggestions of where I should search? >> >> Mark Waite >> >> On Thursday, June 22, 2017 at 9:04:53 AM UTC-6, Mark Waite wrote: >>> >>> My docker image that I've upgraded is showing an unexpected behavior in >>> a GitHub (not git) >>> >>> On Friday, June 16, 2017 at 12:19:24 PM UTC-6, Stephen Connolly wrote: >>>> >>>> Just a quick status update. >>>> >>>> In final stages of this work now. Bobby is being a superstar and >>>> reviewing my 13k LoC change on the Bitbucket branch source - brings lots >>>> of >>>> feature parity with GitHub and adds the configuration ability of the pure >>>> Git branch source >>>> >>>> I am finalising the GitHub Branch Source changes... likely to be >>>> another big PR >>>> >>>> Then there's a 5k LoC change in the Git plugin >>>> >>>> Plan is to try and get all merged next week and cut a beta >>>> >>>> I'll be looking for people to help test at that stage. >>>> >>>> Please respond if you think you can help (lots of bugs fixed as a side >>>> effect of the refactoring - it makes things more easy to test => I found >>>> and fixed bugs) >>>> -- >>>> Sent from my phone >>>> >>> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7dca457a-6089-4bb2-8b0a-5db183b2fdca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
