Closed marcjay closed 2 years ago
Taking https://releases.hashicorp.com/packer/1.7.0 as an example, the source contains:
<li>
<a data-product="packer" data-version="1.7.0" data-os="linux" data-arch="386" href="https://releases.hashicorp.com/packer/1.7.0/packer_1.7.0_linux_386.zip">packer_1.7.0_linux_386.zip</a>
</li>
<li>
<a data-product="packer" data-version="1.7.0" data-os="linux" data-arch="amd64" href="https://releases.hashicorp.com/packer/1.7.0/packer_1.7.0_linux_amd64.zip">packer_1.7.0_linux_amd64.zip</a>
</li>
<li>
<a data-product="packer" data-version="1.7.0" data-os="linux" data-arch="arm" href="https://releases.hashicorp.com/packer/1.7.0/packer_1.7.0_linux_arm.zip">packer_1.7.0_linux_arm.zip</a>
</li>
The tool-level pages use relative URLs (e.g. https://releases.hashicorp.com/packer) if that's what you're looking at?
This is broken on our Jenkins now, just found this PR. Nice work, need this asap to work with Terraform again
The tool-level pages use relative URLs (e.g. https://releases.hashicorp.com/packer) if that's what you're looking at?
🤦 Thanks!
@daniel-beck now that this is merged, does it fixes the issue automatically - or will take some time for this to be deployed somewhere and fixed?
Check file timestamps in https://updates.jenkins.io/updates/ ; once they're newer than "now", "Check for updates" in Jenkins.
Remove the base URL prefix that is being added to the URLs for Hashicorp tools from https://releases.hashicorp.com It appears that the release page used to have relative URLs, but a recent change (apparently in line with https://www.hashicorp.com/blog/announcing-the-hashicorp-releases-api) has caused the URLs to be absolute