Open mmajcica opened 6 years ago
@mmajcica make.json
seems to be tied up with the build system used by vsts-tasks
repo (ref). We could probably take the key idea (i.e. pick up and package external data) in form of reusable gulp utilities. A generated task can use it as required.
Marking this issue as up for grabs if anyone wants to take a first shot at implementing this.
Few external sources come to mind:
Implementation needs to support versions and an action for each source to download
the dependency, extract and transform, and finally package it as a data in the task.
@codito Should we keep the same make.json file as MS does? I can give it a try although it would be my first time with gulp.
Thanks for signing up for this!
We can use the same format as make.json. It does model nuget with additional commands like cp
. I am not sure what are the other commands it supports. We can pick and choose only the ones we need.
"cp": [
{
"source": [
"*.dll",
"*.ps1",
"*.psd1",
"*.psm1",
"lib.json",
"Strings"
],
"dest": "ps_modules/VstsTaskSdk/",
"options": "-R"
}
]
It will be nice if the the delivered package procedure would take care adding depending modules for a task, like the one used by VSTS team, https://github.com/Microsoft/vsts-tasks/blob/master/Tasks/WindowsMachineFileCopy/make.json