#gocd

/

      • arvindsv has quit
      • arvindsv joined the channel
      • arvindsv has quit
      • arvindsv joined the channel
      • arvindsv has quit
      • arvindsv joined the channel
      • arvindsv has quit
      • arvindsv joined the channel
      • arvindsv has quit
      • arvindsv joined the channel
      • harms joined the channel
      • harms
        Hi, experimenting with GoCD, and was wondering how to set a Mercurial material to use a named branch and not the "default" branch.
      • arvindsv
        harms: Search for "Specifying a mercurial branch" in this page: https://docs.gocd.org/current/configuration/con...
      • tl; dr - You specify it after the URL "url##branch".
      • harms
        OK, thank you, arvindsv, trying now
      • Got it to work. Thanks again.
      • On other CI systems I've been using Virtualenv from Python to isolate some build Python dependencies that would otherwise be installed on the agent. Virtualenvs need to be "activated" with a command, before proceeding to do other things. Is there a way to do this in GoCD?
      • I guess what I'm asking is, will system environment variables changes in one Task be carried over to the next Task in the same Job?
      • arvindsv
        You'd do it in a shell script and check that it. Each task is independent.
      • harms
        OK, I guess that makes sense.
      • Neighbour has left the channel