[JIRA] [workflow-plugin] (JENKINS-26157) Subversion doesn't work correctly

Fri, 02 Jan 2015 08:21:04 -0800

Jesse Glick commented on Bug JENKINS-26157

My error was to move the step into a method (with a nice URL parameter), and to call it from the node closure. Polling works when I put the snippet directly into the node closure.

I know of no reason why it would not work identically when wrapped inside a method. Can you reproduce this from scratch? If so, please provide details.

with all the unused options the 'general SCM' snippe[t] doesn't look nice

Currently you need to manually trim off unnecessary options which default to non-null values: JENKINS-25779

some way to declare a trigger, and another way to declare used repositories

Not sure I follow.

just about 50 lines of stack trace compared to 100 lines in a 'workflow build'

There are two distinct exceptions shown. Do you mean that a freestyle build shows only the first? The second (NPE from SubversionSCM.checkout) is clearly a bug in the Subversion plugin, which I filed as JENKINS-26264.

aggressive testing in the freestyle SCM form, which makes it difficult to enter an inaccessible SCM repository

You can simply ignore form validation errors and Save despite them.

Stack traces in builds just don't look very nice

Agreed, and my suggested fix of JENKINS-26264 would get rid of the stack trace.
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to