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

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

Open
BMI-Mike opened this issue Mar 29, 2021 · 2 comments

Comments

@BMI-Mike
Copy link

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?

@BMI-Mike
Copy link
Author

I'm checking back in to see if there is an update or something that I am obviously missing.

@freddydk
Copy link
Contributor

freddydk commented Jul 6, 2021

Sorry, didn't see the issue - will have a look.

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

2 participants