Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ansible request for MSVS_2010, Win2012 #2165

Closed
1 of 3 tasks
Willsparker opened this issue Apr 30, 2021 · 3 comments · Fixed by #2168
Closed
1 of 3 tasks

Ansible request for MSVS_2010, Win2012 #2165

Willsparker opened this issue Apr 30, 2021 · 3 comments · Fixed by #2168

Comments

@Willsparker
Copy link
Contributor

Please put the name of the software product (and affected platforms if relevant) in the title of this issue

  • Missing install
  • Bug in ansible playbook
  • Request for new playbook addition

Details:
Seems the link we were using to install the MSVS_2010 installer has expired? It gives a 404 error now.

Ref: https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/OS=Win2012,label=vagrant/1140/console

Looks like we can install 2012 at oldest now : https://visualstudio.microsoft.com/vs/older-downloads/

@sxa
Copy link
Member

sxa commented Apr 30, 2021

Since adoptium/temurin-build#2191 was merged I think we may no longer require VS2010 anywhere but it would be useful to confirm this. See also the comment in adoptium/temurin-build#466 (comment) which indicated that was likely the only one left.

@sxa
Copy link
Member

sxa commented Apr 30, 2021

@andrew-m-leonard This scenario is some more "food for thought" for the work you're doing at the moment :-)

@Willsparker
Copy link
Contributor Author

From what I can gather from looking at those issues and the build repo code, is that MSVS_2010 is no longer used - both JDK8 HS and J9 use toolchain_version=2013 according to the builds too; so I'll create a PR to remove it :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants