-
Notifications
You must be signed in to change notification settings - Fork 867
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
Publish artifacts syntax #1431
Publish artifacts syntax #1431
Conversation
echo world > layoutDir/world.txt | ||
|
||
- publishArtifact: layout | ||
sourceFolder: layoutDir # or $(system.defaultWorkingDirectory)/layoutDir |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how about path instead of sourceFolder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops I originally meant to put sourcePath
.
I don't mind changing this to simply path
. My thinking was to make way for targetPath
for things like file share artifacts, or even the current server artifacts can use a user-specified path to put it under a specific folder. Multiple publish steps can be used today to contribute to a single artifact, if the subpaths are different.
echo hello > layoutDir/hello.txt | ||
echo world > layoutDir/world.txt | ||
|
||
- publishArtifact: layout |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would publish
be sufficient?
steps: | ||
- script: echo hello > $(build.artifactStagingDirectory)/hello.txt | ||
|
||
- publishArtifact: drop |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps don't require an artifact name and default to "drop" if not specified. That's what our designer templates do with the PublishBuildArtifacts task.
@vtbassmatt - Can you take a look at this one? |
No description provided.