The UI experience has been great for me in the two or three places where 
I've used it.  I was a little surprised (and pleased) with the adaptation 
that the local branch setting is now a toggle.  I think that's the right 
approach, since (as far as I can tell) that is the 99% use case.

Earlier I reported an NPE when configuring a multi-branch pipeline that 
uses GitHub as source instead of Git as source.  The NPE was resolved by 
removing the multiple-scms plugin.  Unfortunately, the 404 is still there, 
along with a stack trace that starts with this:

Jun 23, 2017 9:51:38 AM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: 
descriptor.calcFillSettings(field,attrs) in 
/job/Git-Client-Folder/job/git-client-pipeline-github/configure. Reason: 
java.lang.IllegalStateException: class 
org.jenkinsci.plugins.github_branch_source.GitHubSCMSource$DescriptorImpl 
doesn't have the doFillCredentialsIdItems method for filling a drop-down 
list
java.lang.IllegalStateException: class 
org.jenkinsci.plugins.github_branch_source.GitHubSCMSource$DescriptorImpl 
doesn't have the doFillCredentialsIdItems method for filling a drop-down 
list
at hudson.model.Descriptor.calcFillSettings(Descriptor.java:412)
at sun.reflect.GeneratedMethodAccessor578.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at 
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at 
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
at 
org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24)
at 
org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)

I'm not sure how to provide a repeatable condition for that bug yet, but 
wanted to alert you about it.  I won't investigate further on it until 
after the end of the working day today.

Mark Waite

On Friday, June 23, 2017 at 7:32:54 AM UTC-6, Stephen Connolly wrote:
>
> How do you find the new UI compared with the previous one?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" 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-dev/f22a03c7-6d9a-42b2-bc2f-58acc3d0fb5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to