Replies: 1 comment
-
I think it's a nice suggestion, so I will create an issue out of it |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I would appreciate it if the GitVersion CLI could output all the variables in
dotenv
format:This would allow more simplified CI/CD jobs with the two most important CI systems, GitLab CI and GitHub Actions. Both allow to pass environment variables to other jobs by writing them to a specific file (as documented for GitLab and GitHub). The first step of the pipeline would calculate the GitVersion-variables and export them, and all subsequent jobs could use those variables.
One important thing to consider is what to do with
null
values. In the example above,BuildMetaData
isnull
. If it's in the output, the environment variable will be defined as empty. But most probably, all GitVersion-variables that arenull
should not be printed at all indotenv
mode.Beta Was this translation helpful? Give feedback.
All reactions