Darren, Thank you for your assistance, it's given me a path forward and I appreciate it. As far as storing the text file content (build #) as an environment, do you have any documentation how to accomplish this? I'm in windows, and I have trouble understanding your bash example.
Thanks again, munchrall On Tuesday, October 3, 2017 at 5:24:37 PM UTC-6, munchrall wrote: > > Somewhat new to GO and I inherited our company's CICD system recently from > someone who's no longer available to inquire, so please bare with me. > > Our pipelines inherit from a Template that has 4 Stages > > - Build > - DeployToDev > - DeployToTest > - DeployToProd > > We utilize TFS as our respostory and use OctopusDeploy to deploy and > promote our code. > > Our build script creates a release / version number that is a composite of > [ChangeSet].[BuildSystemVersionChangeSet].[%PipelineCounter%][%StepCounter]. > This is all derived in the Build Stage and passed into the build script. > > I need to retain this number somehow so that I can use it in the > DeployToDev / DeployToTest / DeployToProd Stages in order to specify to > OctopusDeploy which specific release / version needs to be promoted for > that specific step. > > Therefore, my question is what is the correct manner to store this value > from the build stage for later stages, but only for that specific pipeline > 'release'. > > Any help is appreciated. > > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
