Add tests for NanoServer and IoT for the debugging support to step in "Invoke-Command -ComputerName" #3236

Activity

1. Dongbo Wang (daxian-dbw)

   assigned

   Paul Higinbotham (PaulHigin)

   on Mar 1, 2017
2. Paul Higinbotham (PaulHigin)

   removed their assignment

   on Mar 1, 2017
3. Steve Lee (SteveL-MSFT)

   added

   WG-Interactive-Debuggingdebugging PowerShell scriptdebugging PowerShell script

   WG-Quality-Testissues in a test or in test infrastructureissues in a test or in test infrastructure

   on Mar 4, 2017
4. iSazonov commented on Aug 29, 2018

   

   Ilya (iSazonov)

   on Aug 29, 2018

   Collaborator

   More actions

   If MSFT team migrate tests to VS Team Services the issue must be taken into account.
   /cc Travis Plunk (@TravisEz13)
5. TravisEz13 commented on Aug 29, 2018

   

   Travis Plunk (TravisEz13)

   on Aug 29, 2018

   Member

   More actions

   Ilya (@iSazonov) Why is the Migration to VSTS relevant here?
6. iSazonov commented on Aug 29, 2018

   

   Ilya (iSazonov)

   on Aug 29, 2018

   Collaborator

   More actions

   Travis Plunk (@TravisEz13) I hope we'll can able to get VMs with full set platforms and versions (including IoT, Core, Server ...) and to implement remoting tests.
7. TravisEz13 commented on Aug 29, 2018

   

   Travis Plunk (TravisEz13)

   on Aug 29, 2018

   Member

   More actions

   Ahh, with VSTS we should be able to test with nanoserver and windowsservercore containers. Getting VMs would cost money for the times we keep them running.

   👍React with 👍1Reacted by Ilya
8. TravisEz13 commented on Aug 29, 2018

   

   Travis Plunk (TravisEz13)

   on Aug 29, 2018

   Member

   More actions

   Technically we can do this with AppVeyor, but... it's more complicated.
9. microsoft-github-policy-service commented on Nov 16, 2023

   

   microsoft-github-policy-servicebot

   on Nov 16, 2023 – with Microsoft GitHub Policy Service

   Contributor

   More actions

   This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
10. microsoft-github-policy-service commented on Nov 16, 2023

    

    microsoft-github-policy-servicebot

    on Nov 16, 2023 – with Microsoft GitHub Policy Service

    Contributor

    More actions

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
11. microsoft-github-policy-service

    added

    Resolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or more

    on Nov 16, 2023
12. microsoft-github-policy-service commented on Nov 16, 2023

    

    microsoft-github-policy-servicebot

    on Nov 16, 2023 – with Microsoft GitHub Policy Service

    Contributor

    More actions

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
13. microsoft-github-policy-service commented on Nov 23, 2023

    

    microsoft-github-policy-servicebot

    on Nov 23, 2023 – with Microsoft GitHub Policy Service

    Contributor

    More actions

    This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.
14. microsoft-github-policy-service

    closed this as completedon Nov 23, 2023