Thank you for your answer Ethan,
It does appear that the task is actually running on the build agent.
Here is the error:
2016-07-29T01:36:52.8159870Z ##[section]Starting: JFrogArtifactoryPromote
2016-07-29T01:36:53.0988410Z ##[error]Supported task execution handler not
found. Supported handlers: Node
2016-07-29T01:36:53.1038520Z ##[section]Finishing: JFrogArtifactoryPromote
As you see the only handler supported is Node, not PowerShell (my agent runs
on Linux)
When I unzipped the JFrog.jfrog-artifactory-1.0.0.vsix extension and looked
at the JFrogArtifactoryPromote's task.json, I saw the following:
"execution": {
"PowerShell": {
"target": "$(currentDirectory)\\ArtifactoryPromote.ps1",
"argumentFormat": "",
"workingDirectory": "$(currentDirectory)"
}
Compare this to the PublishCodeCoverageResults task which supports both
PowerShell and Node:
https://github.com/Microsoft/vsts-tasks/blob/master/Tasks/PublishCodeCoverageResults/task.json#L58
It makes sense to assume that JFrogArtifactoryPromote is running on the
build agent since I am adding it as a build task and it shows up in the
build log.
--
View this message in context:
http://forums.jfrog.org/VSTS-plugin-running-on-Linux-tp7581131p7581138.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
_______________________________________________
Artifactory-users mailing list
Artifactory-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/artifactory-users
