[
https://issues.jenkins-ci.org/browse/JENKINS-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162245#comment-162245
]
pjdarton commented on JENKINS-13424:
------------------------------------
I had a flurry of activity on it until I got it "working for me". There's
still some stuff unresolved from my point of view, but it's good enough and
"real work" (what I was doing which meant I found the problems in the first
place) then intervened and I stopped.
I think that your configuration setting should really be on a per-server basis,
not global and not per-project, as it's necessary when you're building from a
replica server instead of the master.
I think that your approach of emailing people is probably the right one - I
don't have commit access to the repo either, but I did as you did - made a
patch and asked for it to be included. It might make life a little simpler if
you get your own github fork, put the changes on there and then ask for that to
be pulled, but a .patch file ought to work just as well.
If you don't get any response, you can always build a local copy and use that.
> Need option to run "accurev replica sync" before populating the stream
> ----------------------------------------------------------------------
>
> Key: JENKINS-13424
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13424
> Project: Jenkins
> Issue Type: Bug
> Components: accurev
> Environment: plugin version is 0.6.18
> Reporter: pickgr1
> Assignee: Scott Tatum
> Attachments: JENKINS-13424.patch
>
>
> This needs to either be an option or the default behavior. Ideally, this is
> the default behavior or a global setting so we don't have to re-configure all
> of our projects.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
