The current situation of requiring the "az cli" to be installed on every node is not tenable. It's something you'd do on your local jenkins server, however if your jenkins setup involves multiple build nodes and/or agent. There must be a way to configure the Azure CLI like any other tool like, Git, Java, Ant, Maven, JFrog Cli, etc. And it may differ dependent on what the OS of the build host is.
Also may be good to add declarative pipeline support by e.g. allowing people to use az command directly instead of having to wrap it into a "sh" multi-line script.
What feature do you want to see added?
The current situation of requiring the "az cli" to be installed on every node is not tenable. It's something you'd do on your local jenkins server, however if your jenkins setup involves multiple build nodes and/or agent. There must be a way to configure the Azure CLI like any other tool like, Git, Java, Ant, Maven, JFrog Cli, etc. And it may differ dependent on what the OS of the build host is.
See the Jenkins developer docs: https://wiki.jenkins.io/JENKINS/Manage-global-settings-and-tools-installations.html
Also may be good to add declarative pipeline support by e.g. allowing people to use az command directly instead of having to wrap it into a "sh" multi-line script.
Upstream changes
No response