[
https://issues.jenkins-ci.org/browse/JENKINS-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159772#comment-159772
]
pickgr1 commented on JENKINS-12954:
-----------------------------------
Unfortunately, the plugin does not recognize the Key/Value pair variable
substitution available in the node configuration:
15:14:58 [test_accurev_on_*_nodes] $ /usr/bin/accurev info -H
${ACCUREV_SERVER}:5050
15:15:00 FATAL: Domain: *
15:15:00 Server name: ${ACCUREV_SERVER}
15:15:00 Port: 5050
15:15:00 ACCUREV_BIN: /opt/accurev/bin
15:15:00 Client time: 2012/03/02 15:14:58 PST (1330730098)
15:15:00 h_errno: 1
15:15:00 get host: Unknown host
15:15:00 network error - Can't find host entry for ${ACCUREV_SERVER}
15:15:00 Attempt to contact AccuRev server on ${ACCUREV_SERVER} port 5050
failed.
15:15:00 Giving up.
15:15:00 AccuRev Error: 1
15:15:00
15:15:00 FATAL: info command (/usr/bin/accurev info -H ${ACCUREV_SERVER}:5050)
failed with exit code 1
15:15:00 Not currently authenticated with Accurev server
15:15:00 Authenticating with Accurev server...
There is also a "tool locations" for the node configuration. Ultimately, I
think this where this feature belongs. I see the git plugin uses this.
> Configure accurev server per Jenkins node
> -----------------------------------------
>
> Key: JENKINS-12954
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12954
> Project: Jenkins
> Issue Type: New Feature
> Components: accurev
> Environment: Ubuntu 10.04.04 - Jenkins LTS
> Reporter: pickgr1
> Assignee: Scott Tatum
>
> There may be a way to configure this already that I'm overlooking somewhere,
> but if not, this would be a great feature.
> In the Jenkins global configuration, it's possible to add multiple servers
> (replicas) We have replicas that are geographically diverse across a
> corporate WAN. For example, we have Jenkins nodes/slaves at both site A and
> site B. Each site also has it's own AccuRev replica. So we want nodes at
> site A to use their local AccuRev replica and nodes at site B use their local
> replica.
> I see that it's possible to configure this on a per-job basis, but what we
> really need is a per node/slave basis. Otherwise, we have to maintain
> separate jobs for each site.
--
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
