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

Visual Studio 2017 and network installs #11

Closed
wants to merge 40 commits into from

Conversation

taliesins
Copy link

Added Visual Studio 2017
Added network install feature for offline cache (there is no ISO for Visual Studio 2017)

taliesins and others added 23 commits April 25, 2017 14:19
…ork or local install. This means we don't want to extract or clean Visual Studio ISO.
…nstaller_file. The installer_file could be the path the full path to the network install
Add ability to install via web installer
--all	Optional: Whether to install all workloads and components for a product.
--allWorkloads	Optional: Installs all workloads and their required components, no recommended or optional components.
--includeRecommended	Optional: Includes the recommended components for any workloads that are installed, but not the optional components. The workloads are specified either with --allWorkloads or --add.
--includeOptional	Optional: Includes the optional components for any workloads that are installed, but not the recommended components. The workloads are specified either with --allWorkloads or --add.
…commandline and its already installed. Perhaps passing in all the options will stop that.
@taliesins taliesins mentioned this pull request May 2, 2017
@steveruddell
Copy link

@sneal what needs to be done by @taliesins to unblock this and get it merged?

@sneal
Copy link
Contributor

sneal commented May 26, 2017

@steveruddell We need to fix the RuboCop warnings so the build passes. Ideally we replace RuboCop with cookstyle, similar to what was done here.

@taliesins
Copy link
Author

@sneal what would you like me to do to get this merged :>

@ryangribble
Copy link

Did you have a working example of installing from the network install cache location @taliesins ?

Im having trouble actually getting this working.

Apart from the fact that I have credential/authentication issues in accessing the UNC location from chef (should this cookbook allow attributes to be specified for user/password and then use a powershell or mount resource to enable access to the location, or is that left up to the consuming users to do before they call the resource from this cookbook?), I also cant seem to actually get chef to try and execute the package installer in-situ from the network location.

When specifying the installer_path as \\\\server,domain\path\to\installer.exe the chef run ends up executing a blank command (eg cmd /c /wait "" --silent etc) and when specifying installer_path as file://server.domain/path/to/installer.exe it seems the package resource attempts to download the exe locally which would then result in it not actually using any of the cached packages on the network share.

@spotlesscoder
Copy link

What's the status here? can't wait to get VS 2017 support

@taliesins
Copy link
Author

@ryangribble I added sample usage to read me https://github.com/taliesins/visualstudio/blob/NetworkInstall/README.md

node.override['visualstudio']['version'] = '2017' node.override['visualstudio']['edition'] = 'professional' node.override['visualstudio']['source'] = '' node.override['visualstudio']['2017']['professional']['default_source'] = '' node.override['visualstudio']['2017']['professional']['source'] = '' node.override['visualstudio']['2017']['professional']['filename'] = '' node.override['visualstudio']['2017']['professional']['checksum'] = nil node.override['visualstudio']['2017']['professional']['installer_file'] = '//myartifactrepo/visualstudio/vs_professional.exe'

@ryangribble
Copy link

I'm pretty sure that's what I tried but as I mentioned it uses the remote_file resource which tries to download the installer file and thus isn't running it "in situ" from the network cache location (and therefore doesn't use any of the cached workloads)?

@taliesins taliesins mentioned this pull request Oct 5, 2017
@@ -40,3 +40,4 @@
include_attribute 'visualstudio::vs2012'
include_attribute 'visualstudio::vs2013'
include_attribute 'visualstudio::vs2015'
include_attribute 'visualstudio::vs2017'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is redundant, the chef-client run merges all files in the attributes folder anyway.

@Sauraus
Copy link
Contributor

Sauraus commented Nov 7, 2017

This PR should be broken up into 2 pieces:

  1. Network Install
  2. vs2017 addition

And a rebase -i HEAD~X would do wonder in terms of being able to grok the whole thing. :)

@chaim1221
Copy link
Contributor

Hello there, this has gone stale, any interest among the interested parties in reviving it? The AppVeyor build is currently broken, but I'll accept being able to manually confirm the results (myself, in a fresh environment) until I get #18 done.

@Sauraus
Copy link
Contributor

Sauraus commented Mar 5, 2018

I've gone ahead and made a fork here https://github.com/Roblox/visualstudio that does the vs2017 installs just fine for us.

@ghost
Copy link

ghost commented Mar 5, 2018

Great, feel free to make a PR!

@Sauraus
Copy link
Contributor

Sauraus commented Mar 5, 2018

Ok I will squash all the commits for just vs2017 installation, I've left out the network installation which I didn't need and I also do not feel should be in the same PR anyway, give me a day or 2 to clean things up.

@ghost
Copy link

ghost commented Mar 5, 2018

Cool. And no need to squash the commits if it's extra work. I just look at diffs.

@Sauraus
Copy link
Contributor

Sauraus commented Mar 5, 2018

Need to squash the commits to make sense of the changes myself. :D

@ryangribble
Copy link

i agree the network install should be done separately. i think it could possibly even deserve being a new resource as it is fairly different to the way the online installs are being done

@laurencee
Copy link

@Sauraus Heya, were you still creating a PR with just the VS2017 installation part?

@Sauraus
Copy link
Contributor

Sauraus commented May 9, 2018

Yes its on my 'ever' to-do list sorry. :( I will try to make some time in the next 2 weeks.

@smitsdj
Copy link

smitsdj commented Sep 20, 2018

Gents, what is the status of this PR? I'm looking for VS2017 support.

@chaim1221
Copy link
Contributor

Sorry! I have had no time to focus on this repo; went from some very intense DevOps to some very intense unemployment, now getting back in the saddle. The build appears to be broken. I will look when I get a chance.

@yamamoto52
Copy link

what status is of this changes ? will it be merged successfully into master ?

@chaim1221
Copy link
Contributor

chaim1221 commented Oct 18, 2018 via email

@EasyAsABC123
Copy link

We are not in 2019...where is this support?

@jonathanan
Copy link

Haven't tried it but this cookbook looks promising:
https://supermarket.chef.io/cookbooks/vs-2017
https://github.com/btc-ag/chef-vs2017

@Stromweld
Copy link

closing this PR as old and outdated now.

@Stromweld Stromweld closed this May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.