Skip to content

Consider appveyor artifact for module #622

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

Open
RamblingCookieMonster opened this issue Sep 26, 2016 · 4 comments
Open

Consider appveyor artifact for module #622

RamblingCookieMonster opened this issue Sep 26, 2016 · 4 comments

Comments

@RamblingCookieMonster
Copy link

Hi!

Love that this project is open sourced, and I can see work on #605 right in PR #617. I browsed to AppVeyor to see if there was a module or nuget package I could test with, but noticed it looks like it's just the repo zipped up.

Have you or would you consider publishing pre-built modules to AppVeyor (a la DSC resources)? This would help folks willing to start kicking the tires, who don't have the software ready to go to build these themselves, speed up the process for folks who do have the tools, etc.

Cheers!

@kapilmb
Copy link

kapilmb commented Sep 26, 2016

@RamblingCookieMonster Thanks for the suggestion! I agree that this would help get a feature or fix out in the wild earlier. Will try to get this checked-in soon.

@kapilmb kapilmb added this to the 1610 milestone Sep 26, 2016
@kapilmb kapilmb self-assigned this Sep 26, 2016
@kapilmb
Copy link

kapilmb commented Sep 26, 2016

A workaround for now would be to extract the psscriptanalyzer.zip artifact and use the out/PSScriptAnalyzer directory - import-module /path/to/artifact/out/psscriptanalyzer. This will work only on Windows PowerShell though (not on any core version).

@kapilmb kapilmb modified the milestones: 1610, 1611 Nov 1, 2016
@kapilmb kapilmb modified the milestones: 1611, 1612 Dec 2, 2016
@bergmeister
Copy link
Collaborator

This workaround seems to be broken now. When I import the psd1 file, no commands get exported and when I try to import the dll, then I get a hint why:

ipmo : Could not load file or assembly 'file:///C:\Users\cberg\Downloads\psscriptanalyzer
(1)\out\PSScriptAnalyzer\Microsoft.Windows.PowerShell.ScriptAnalyzer.dll' or one of its dependencies. Operation is not
supported. (Exception from HRESULT: 0x80131515)
At line:1 char:2
+  ipmo 'C:\Users\cberg\Downloads\psscriptanalyzer (1)\out\PSScriptAnal ...
+  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Import-Module], FileLoadException
    + FullyQualifiedErrorId : System.IO.FileLoadException,Microsoft.PowerShell.Commands.ImportModuleCommand

@bergmeister bergmeister modified the milestones: 1612, Backlog May 11, 2018
@bergmeister
Copy link
Collaborator

I found out by coincidence what the reason for the error above was, when downloading the artifact as a zip, Windows does not trust the code, therefore before extracting the zip file, one has to go the file's properties, tick Unblock and then press OK.
image
I will add a PR soon that makes it upload only the artifacts instead of the whole checkout

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

No branches or pull requests

3 participants