exposing executing AGENT as a GO environment variable

Follow

Comments

3 comments

  • Avatar
    Anush Ramani

    Lee,


    Could you elaborate on why you need to identify individual agents. I understand that you have multiple agents on the same machine, but each agent is sandboxed, so they should not conflict with each other.


    Ideally, your scripts should be completely agnostic to what agent they are running on. Only then would you be able to make full utilization of the flexibility of the agent grid. If your scripts are agent aware, that would introduce a lot of unnecessary complexities within your scripts.

  • Avatar
    LeeBenhart

    Anush,


    I have a pipelie which runs on all agents and would like to use the agent name in naming the output file.  Since I will review the artifacts later for any issues.  That is one scenario, there could be others as well.


    Lee

  • Avatar
    Anush Ramani

    Lee,


    In order to retrieve the generated artifacts, you'd likely have to go to the job details page anyway, right? The job details page does list the agent name on it. Does this work for you?


    I'd also like to mention that in Go 2.3, we're coming out with an new screen that gives you details about each agent. If the purpose of your script is to get some data around the agent, what kind of data are you extracting? I ask because it may be good feedback for features that could possibly go into the new agents page.

Please sign in to leave a comment.