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

Add support for Drop artifact to Publish and Download build artifacts… #2

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

mortezag
Copy link
Owner

… tasks

manifestid: artifact.resource.data
};

tl.command("artifact.download", properties, downloadPath);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note, we should not add this command permanently. When this command is used, I would have the command handler check the currently running task and verify the ID is your task otherwise fail. Customers should not be able to use this in their ad hoc scripts. Fire and forget command doesn't make sense for download, from user scripts.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be just switch the entire drop download into C# when GA?

"version": {
"Major": 1,
"Minor": 131,
"Major": 2,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should take this opportunity to rename the task "PublishDropArtifact" since this should work in the future from a release as well

"Major": 1,
"Minor": 131,
"Major": 2,
"Minor": 0,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2.133.0 instead 2.0.0 :)

@@ -68,7 +68,7 @@ async function run() {

// upload or copy
if (artifactType === "container") {
Copy link

@hashtagchris hashtagchris Apr 24, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a good opportunity to rename the task value for "Visual Studio Team Services/TFS" to server or possibly drop. I know we don't have to, but continuing to have container in the build definition will be confusing.

As far as people switching from v1 to v2: We're allowed to make breaking changes in new major versions, but we could check if (artifactType === "filepath") { first and handle other values (server or container) in the else clause.

"Major": 1,
"Minor": 131,
"Major": 2,
"Minor": 0,
"Patch": 0
},
"demands": [],

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add preview and releaseNotes. Example from Xcode's task.json:

    "preview": true,
    "releaseNotes": "This version of the task is compatible with Xcode 8 and Xcode 9. Features that were there solely to maintain compat with Xcode 7 have been removed. The task has better options to work with the Hosted macOS pool.",

manifestid: artifact.resource.data
};

tl.command("artifact.download", properties, downloadPath);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does console.log(tl.loc('ArtifactsSuccessfullyDownloaded', downloadPath)); below the diff execute before the artifact is downloaded? Not sure if there's a way to monitor completion/success.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's why artifact.download needs to be removed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants