Releases: jfrog/jfrog-azure-devops-extension
2.14.1
2.14.0
2.13.1
2.13.0
2.12.10
What's Changed
Improvements 🌱
- Removed automatic forwarding of
Agent.ProxyUrltoHTTP_PROXY/HTTPS_PROXYfor JFrog CLI @agrasth in #603
JFrog CLI no longer inherits ADO agent proxy by default.
Customers whose ADO agent is behind a proxy but Artifactory is reachable directly no longer
need any configuration — JFrog CLI will not route Artifactory traffic through the proxy.
If Artifactory must be reached through a proxy, set HTTP_PROXY/HTTPS_PROXY explicitly
in your pipeline. Native service connection support is planned for an upcoming release.
Full Changelog: 2.12.9...2.12.10
2.12.9
What's Changed
Other Changes 📚
Proxy Bypass — Automatic NO_PROXY Support
This release improves on the proxy change introduced in 2.12.8. The plugin now reads Agent.ProxyBypassList from the
ADO agent configuration and automatically sets NO_PROXY for JFrog CLI — so hosts that should bypass the proxy (e.g. an
internal Artifactory instance) are excluded without any pipeline changes.
Note:
Agent.ProxyBypassListentries from the.proxybypassfile are ECMAScript regex patterns (e.g.
artifactory\.corp\.com). This release correctly converts simple hostname patterns (escaped dots) to plain hostnames
forNO_PROXY. Complex regex patterns (e.g..*\.corp\.com) are not supported and should be replaced with plain
hostnames.
If you upgraded to 2.12.8 and your pipelines started failing, the recommended fix requires no pipeline changes:
Add a .env file to your ADO agent root directory:
NO_PROXY=artifactory.example.com
Replace artifactory.example.com with your Artifactory hostname. This is a one-time change per agent and applies to all
pipelines on that agent automatically.
For agent-level proxy configuration, see the Azure DevOps agent proxy documentation.
Full Changelog: 2.12.8...2.12.9
2.12.8
What's Changed
Improvements 🌱
- multiple node versions for tests by @reshmifrog in #588
- Add proxy support for OIDC authentication by @agrasth in
#593
Other Changes 📚
⚠️ Action Required — Proxy Behaviour Change
Starting with this release, if your ADO agent has a proxy configured (Agent.ProxyUrl), JFrog CLI will automatically
route all traffic through that proxy.
If your Artifactory instance is on an internal network and should connect directly (not via the corporate proxy),
you will see connection failures after upgrading.
Fix — no pipeline changes required:
Add a .env file to your ADO agent root directory with the following content:
NO_PROXY=artifactory.example.com
Replace artifactory.example.com with your actual Artifactory hostname. This is a one-time change per agent and
applies to all pipelines on that agent automatically — no individual pipeline updates are needed.
For more details on configuring environment variables at the agent level, see the Azure DevOps agent proxy documentation.
Full Changelog: 2.12.7...2.12.8
Full Changelog: 2.12.7...2.12.8