Skip to content

Export PSReadLine to changes to public project #996

Description

This is just so I remember to do this for Jason Shirk (@lzybkr).

Activity

  1. andyleejordan commented on Jun 24, 2016

    @andyleejordan
    MemberAuthor

    While extracting the history and making PSReadLine build stand-alone against the public reference assemblies, I got blocked by a weird .NET possible bug. Filed https://github.com/dotnet/corefx/issues/9658.

  2. 5 remaining items

  3. modified the milestones: , post-6.0.0 on Oct 17, 2016
  4. modified the milestones: , on May 22, 2017
  5. added a commit that references this issue on Jan 20, 2018
    beffdcf
  6. it-praktyk commented on Jan 20, 2018

    @it-praktyk
    Contributor

    After this change, the easiest way to pull the Pester module from PowerShell Gallery is to add it to the file src/Modules/PSGalleryModules.csproj but as the result,

    • Pester module will be pulled every time
    • the switch CI used in the functions
      • Start-PSBuild
      • Restore-PSModuleToBuild
        will be useless and have to be removed.

    Another option - probably a more accurate - is to create the new one csproj file - by analogy to src/Modules/PSGalleryModules.csproj (the proposed name PSGalleryModulesCI.csproj) and add an additional parameter to the function Copy-PSGalleryModules that will contain a path to csproj file (an equivalent of the current line 2484) and call the function Copy-PSGalleryModules twice when $CI will be used.

    In both options the functions

    What do you think? Am I right?

    My comment is related to #4618.

  7. lzybkr commented on Jan 21, 2018

    @lzybkr
    Contributor

    Wojciech Sciesinski (@it-praktyk) - msbuild restore caches the package locally, so if the cache already has the correct version, nothing is pulled.

    Furthermore, at least in AppVeyor (I'm not sure about Travis) - the cache is saved across builds, so we shouldn't see too many pulls from CI.

    I think what I did for PSReadLine can be done for Pester as well and as you point out - that would get rid of some code in build.psm1 - but I haven't looked as closely as you - maybe we don't need the -CI parameter assuming the nuget cache is working as I described.

  8. TravisEz13 commented on Jan 23, 2018

    @TravisEz13
    Member

    travis-ci can cache... I started working on making it but never finished. The -CI parameter is to pull in Pester only during CI builds. The desire is to not ship pester with PowerShell and have people use Install-Module to get pester.

  9. iSazonov commented on Jan 23, 2018

    @iSazonov
    Collaborator

    Can we leave Pester in debug builds? I don't like run Restore-PSPester every time.

  10. added a commit that references this issue on Aug 6, 2026
    6776fcb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions