Is your feature request related to a problem? Please describe.
Soon I have to migratie hundreds of Azure DevOps YAML pipelines to start using the JFrog SAAS offering.
I want to keep my pipeline as standard as possible, there are already lots of custom steps, so I want to keep it clean and readable.
The current JFrogCLIV2 task does not make jf available in the path, and it cleans up it's config at the end of the task.
Describe the solution you'd like to see
A task for JFrog CLI that's similar to NuGetAuthenticate@1 & NuGetToolInstaller@1 combined
Which a working token and respects my existing nuget.config and sets an environment variable so my nuget.config source can authenticate.
I understand jf is required for gathering build info and the ghost option looks nice, but I don't have a clear way of using it with Azure DevOps pipelines. Could you not configure that also in a step and use it during the scope of a job?
If we still need the jf executable, than at least make it available in the path for the rest of the job.
Describe alternatives you've considered
- Use the specific tasks, that works, but is really jfrog specific, why would I need a jfrog specific task to do
dotnet build
- Put everything in the JFrogCLIV2 task, that only works if you only use commands that start with
jf I want to do other things in my pipelines. And having a single step is not great for the readability.
Additional context
The way it's done in Github actions looks a lot like how I expected it. Set it up once, then just use it.
Is your feature request related to a problem? Please describe.
Soon I have to migratie hundreds of Azure DevOps YAML pipelines to start using the JFrog SAAS offering.
I want to keep my pipeline as standard as possible, there are already lots of custom steps, so I want to keep it clean and readable.
The current JFrogCLIV2 task does not make jf available in the path, and it cleans up it's config at the end of the task.
Describe the solution you'd like to see
A task for JFrog CLI that's similar to
NuGetAuthenticate@1&NuGetToolInstaller@1combinedWhich a working token and respects my existing nuget.config and sets an environment variable so my nuget.config source can authenticate.
I understand jf is required for gathering build info and the ghost option looks nice, but I don't have a clear way of using it with Azure DevOps pipelines. Could you not configure that also in a step and use it during the scope of a job?
If we still need the
jfexecutable, than at least make it available in the path for the rest of the job.Describe alternatives you've considered
dotnet buildjfI want to do other things in my pipelines. And having a single step is not great for the readability.Additional context
The way it's done in Github actions looks a lot like how I expected it. Set it up once, then just use it.