Sending a Job to one Server or Another
I have a legacy situation using two servers. The users pick from some environment variables to describe what kind of build they want to do. Based on their choices, the job must be sent to server A or Server B. I want to use a single interface for the users, so I don't want to set up the following projects:
Job_for_Server_A
Job_for_Server_B
There can only be one project. I'm having trouble setting this up. What I have so far is Collector_A for Server_A and Collector_B for Server_B. The users pick from a list of customers: Bill, Fred and Burt. The jobs for Bill must go to Server_A. The rest must go to Server_B. How do I set up the selector, or multiple selectors, to do this?
Thanks,
John Bobinyec
Job_for_Server_A
Job_for_Server_B
There can only be one project. I'm having trouble setting this up. What I have so far is Collector_A for Server_A and Collector_B for Server_B. The users pick from a list of customers: Bill, Fred and Burt. The jobs for Bill must go to Server_A. The rest must go to Server_B. How do I set up the selector, or multiple selectors, to do this?
Thanks,
John Bobinyec
One answer
the feature you want to read about is .bset selector or .bset server
http://publib.boulder.ibm.com/infocenter/bldforge/v7r1m2/index.jsp?topic=%2Fcom.ibm.rational.buildforge.doc%2Ftopics%2Fdotcmd_bset.html
you could setup a pulldown variable named "USER" with values "A" and "B" and do something like
.bset selector Collector_$USER
or
.bset server SERVER_$USER
http://publib.boulder.ibm.com/infocenter/bldforge/v7r1m2/index.jsp?topic=%2Fcom.ibm.rational.buildforge.doc%2Ftopics%2Fdotcmd_bset.html
you could setup a pulldown variable named "USER" with values "A" and "B" and do something like
.bset selector Collector_$USER
or
.bset server SERVER_$USER