boolbysigma / fetchbuildartifact Goto Github PK

Hi there,

I'm successfully using your extension to download build artifacts. In our case we download the web app artifact to a web server while the integration test artifact is deployed to another machine.

Currently the integration test artifact gets unzipped into the Target Folder. The tests are run directly from the Target Folder.

Each Test Run creates some result files which are published to VSTS. But Nobody deletes these files and the next Test Run publishes new and old files together.

I could add a new build step deleting the Target Folder myself. Wouldn't it be nice to have such an Option inside your Extension?

What do you think?

I was looking for the source code in order to hopefully submit a Pull Request with #7, but noticed the source code is not here.
Contributions is one motivator, but also it would be easier to trust this extension if we were able to see the source.

Hi,
I couldn't find any License Information for your Plugin on this page or the code.

Could you please add the license to the overview or tell me what model you are using?

Thanks,
Daniel

logs_64587.zip

A new issue has arisen with the fetch operation. The artifact is named "drop" in my build and the software is looking for the folder ......\drop which in my build does not exist in my build. However I manually created the folder at that location and Fetch Artifact still cannot find the folder.

Today all of a sudden the task starts throwing the error: Allow Scripts to access Oauth Token.
this is already selected at the "run on agent" task.

the logs show that it is enabled as well. any pointers?

2017-04-14T07:38:12.5806221Z ##[debug]system.enableAccessToken=True
2017-04-14T07:38:12.5806221Z ##[debug]task result: Failed
2017-04-14T07:38:12.5962466Z ##[error]'Allow Scripts to Access OAuth Token' must be enabled.
2017-04-14T07:38:12.5962466Z ##[debug]Processed: ##vso[task.issue type=error;]'Allow Scripts to Access OAuth Token' must be enabled.
2017-04-14T07:38:12.5962466Z ##[debug]Processed: ##vso[task.complete result=Failed;]'Allow Scripts to Access OAuth Token' must be enabled.
2017-04-14T07:38:12.5962466Z ##[section]Finishing: Fetch Artifact: Sitecore-Package-Single-Instance

Hi Team, I am getting the below error when trying to execute Fetch Build Artifacts I am fetching the build artifacts of another build here and it worked fine till Monday(05-03-2018). From Tuesday morning the build is failing due to the following reasons. 2018-03-09T00:10:43.8270079Z ##[error]Could not find project 'd2cf0979-3417-4674-b89e-db3bd8077c85'. Make sure that the project exists. Can some one help It is urgent .

logs_64653.zip

One more issue. Operation not permitted getting the drop zip.

Thanks for all the help, hopefully the last.

Dave

When attempting to fetch an artifact in a TFS2017 build an error occurs because the project [Guid] cannot be found. Obviously replacing with an actual guid. Maybe TFS2017 has changed the way it refers to projects? I have the OAuth option enabled and the correct project selected etc, but this error still occurs.

sometimes i just want to be able to use the artifacts of a specific release instead of the latest that exists. is it possible to add something like that to your task? would be great.

in VSTS this is already possible for your artifacts.

Custom pipeline tasks always have access to the OAuth token. The proper way to retrieve it in a Node handler is:

const tl = require("azure-pipelines-task-lib/task");
const token = tl.getEndpointAuthorizationParameter('SystemVssConnection', 'AccessToken', false);

Get rid of this requirement, and there will be one less thing for the task users to miconfigure. :)

I get an error when the copy is attempted. It creates the destination folder but fails to copy the artifact.

``Querying project 'Instrument Control' for completed successful builds of build definition '669'

build:

{"_links":{"self":{"href":"http://tfs:8080/tfs/DefaultCollection/dad31c62-fbe8-4d21-851e-bd512969b1f4/_apis/build/Builds/39950"},"web":{"href":"http://tfs:8080/tfs/_permalink/_build/index?collectionId=4b019454-626e-4582-b569-ee8f8bbefa4d&projectId=dad31c62-fbe8-4d21-851e-bd512969b1f4&buildId=39950"},"details":{"href":"http://tfs:8080/tfs/DefaultCollection/dad31c62-fbe8-4d21-851e-bd512969b1f4/_apis/build/Builds/39950/Details?api-version=1.0"}},"id":39950,"buildNumber":"InstrumentControlSDK_Aries10_Market1.Rel_2.1.942.0_B.1","status":"completed","result":"succeeded","queueTime":"2015-04-04T06:00:00.72Z","startTime":"2015-04-04T06:00:04.75Z","finishTime":"2015-04-04T06:17:24.067Z","url":"http://tfs:8080/tfs/DefaultCollection/dad31c62-fbe8-4d21-851e-bd512969b1f4/_apis/build/Builds/39950","definition":{"type":"xaml","createdDate":"2014-11-03T17:42:17.55Z","id":669,"name":"InstrumentControlSDK_Aries10_Market1.Rel","url":"http://tfs:8080/tfs/DefaultCollection/dad31c62-fbe8-4d21-851e-bd512969b1f4/_apis/build...

buildId=39950
Found build '39950'
Querying build artifact 'drop'
Found build artifact 'drop'
Downloading build artifact 'drop' to C:\BuildAgent2017_work\1\s\Prerequisites\drop.zip

task result: Failed

Invalid protocol: file:

Processed: ##vso[task.issue type=error;]Invalid protocol: file:

Processed: ##vso[task.complete result=Failed;]Invalid protocol: file:``

Hello,

This plugin support only Artifact Type "Server". Is it possible also add support for Artifact Type "File Share" ?
Hint:
REST API
.._apis/build/builds//artifacts?artifactName=

return follow valuses:
in case "Server" .. "resource":{"type":"Container"...
in case "File Share" ..resource":{"type":"filepath", ...
and in "data": is path to folder which is just needed to copy to target folder

Thank you

Tomas

Our agents are inside a corporate network and communicate with VSTS on Azure via a proxy.
We have the following error in this task:

##[debug]{"name":"RequestError","message":"Error: tunneling socket could not be established, cause=socket hang up","cause":{"code":"ECONNRESET"},"error":{"code":"ECONNRESET"},"options":{"rejectUnauthorized":false,"auth":{"bearer":********},"json":true,"qs":{"definitions":1996,"statusFilter":"completed","resultFilter":"succeeded","$top":1,"api-version":"2.0"},