Environment variables across tasks

Comments

3 comments

  • Joel Johnson
    Don't recall seeing this go out on the email lists .... ?
    0
    Comment actions Permalink
  • Brad

    I haven't tried setting a variable that way via PDQ yet so I don't know for sure, but I wonder if it would be in scope for your subsequent task.

    You could also set a REG variable and store your serial number in your own registry entry, or create a txt file on the local file system containing whatever you need.  Then you wouldn't have to worry about scope.

    0
    Comment actions Permalink
  • Maria Olivero

    Brad, can you provide more information on using a text file.  We considering doing just that to automate our product deployments.  Jenkins can trigger PDQ just fine and we would like to be able to specify the version of the product we want deployed in a variable - we don't want to have to modify PDQ every time we release a new version...  We can't do it via command line to PDQ (at least not yet), but I have to believe we can write a file - ship that to the PDQ system and have PDQ read that as the first step of the package and then store the contents as variables somehow...  Suggestions?

    0
    Comment actions Permalink

Please sign in to leave a comment.