Skip to content

installApps parameter in settings.json - path interpreted differently (Local Dev v.s. GitHub Actions) #1

@BMI-Mike

Description

@BMI-Mike

I've used this template for a project that is dependent on some 3rd party *.app files. I'm using the installApps parameter in settings.json to automatically install the project dependencies. I created a new directory in the root of the repository called 3rdPartyApps and added this directory to my Workspace in VS Code. There appears to be a difference in path interpretation between GitHub and local development environments.

This definition works in GitHub Actions:
"installApps": "3rdPartyApps\\Some App1.app,3rdPartyApps\\Some App2.app"

This definition works locally (Local-DevEnv.ps1 Local-Pipeline.ps1 DevOps-Pipeline.ps1):
"installApps": "..\\3rdPartyApps\\Some App1.app,..\\3rdPartyApps\\Some App2.app"

Short of using a URL to store a *.zip file containing the dependencies, is there anything I may be missing?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions