Justin Ryan commented on Improvement JENKINS-17222

Copying from email:

Ideally we'd create a inner context to define concepts like this, like we do for the ant dsl method. The problem is that svn was written before we knew how to do that, so we just took a "configure" object. It's not really possible to make a change to the signature to take a context instead of a configure closure, without making it a breaking change. What do people feel about this? Should we "fix" the p4, svn and git commands?

In some respects, the resulting XML is pretty straightforward, though not completely obvious to someone new. E.g. from the ticket:

svn('https://some.repo.com/proj1/trunk', 'project1') \{
    it / locations / 'hudson.scm.SubversionSCM_-ModuleLocation' \{
    remote 'https://some.repo.com/proj2/branches/qwe'
    local 'project2_qwe'
  }
}

Maybe we can just document this (and pretend that the scm commands aren't as ugly as they are)?

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/groups/opt_out.
 
 

Reply via email to