Code Monkey home page Code Monkey logo

exportimportbuilddefinition's Introduction

Export/Import Build Definition

Download this extension from the VS Marketplace or get the specific version from Releases.


Thanks to all of you for using this extension. Unfortunately, I am not able to work on this extension lately. I am aware of these problems, but it is becoming hard for me to keep the extension up to date with the API changes and ECMA compatibility for all supported browsers due to time constraints.

Export and Import your build definitions. Useful for recreating all the build steps, variables, schedules, etc in a different team project.

See the change log for changes and road map.

Features

  • Version control your definitions (exported file is a JSON file, which can be checked-in in to your source control as any other file).
  • Avoid manually duplicating the definition in another team project/account.
  • No need to manually add steps and set their values.
  • The extension also validates and highlights any missing service endpoints.

Context Menu

Note: The extension only supports new (non XAML) build definitions.

Export build definition

  • Right-click and click Export on the build definition you would like to export.
  • You will be prompted save the definition as a file.
  • Save the file with JSON extension.

Import build definition

  • Right click on any existing build definitions and click on Import.

  • You will be prompted to upload a build definition file.

  • You can either drag and drop a file or use the Browse button to select the file you want to import.

  • Once you upload the file, the file will be parsed and the dialog will highlight you if any issues with the definition.

    Import Dialog

  • Click Import. If import is successful, you will have your build created, with all your steps, variables, schedules and other build definition parameters.

DefinitionCopy

Get Started

To contribute to this project, you'll need to do a few things first:

  • Fork the project on GitHub
  • Clone it to your computer
  • Install Visual Studio Code
  • Open the the folder you cloned in Code.
  • Run npm install when in the directory you cloned (directory containing package.json file).

To install local fork into your on-premise TFS (TFS 2017 and above) using VSIX, run npm run package:dev which will create the VSIX file. You can then upload it into TFS by following steps mentioned here.

You can also automate the publishing step by running npm run publish:dev command.

Finally, To see the Export and Import menu items, you need to run the web pack dev server by running npm run dev command.

License

MIT

exportimportbuilddefinition's People

Contributors

onlyutkarsh avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

exportimportbuilddefinition's Issues

Export not exporting definition in TFS 2017

Installed product versions

  • Export/Import Buid Definition extension: 0.0.8

Description

Export not creating/downloading file when extension installed into TFS2017 Ver 15.117.26714.0

Steps to recreate

  1. Install Export/Import Build Definition extensions from VS Marketplace into TFS 2017
  2. Select build definition to be exported on the Build Definitions page
  3. Select Export

Current behavior

Following selection of Export nothing happens.

Expected behavior

My assumption is that a file should be created which would then be referenced for importing the build definition into another environment/collection/project. This is our first time installing this extension.

If further details are required to debug this issue please advise what steps to perform and I will extract the requested details.

Export/Import Task-group

Installed product versions

  • Export/Import Buid Definition extension: where to fould (installed 6-12-2016)

Description

Build Definitions can also consist of Task groups. The actual taks group isn't exported now.
The task is there in the build definition

Steps to recreate

1 Create a task group
2 Add task group to a build definition
3 create an export
4 import it in a differnt project or TFS instance

Current behavior

Task group is added to the build definition correctly.
But states: "This task is no longer installed."

Expected behavior

That during the export also the task group is exported

import multiple builddefinitions at once

Installed product versions

  • Export/Import Buid Definition extension: 0.0.1

Description

It would be nice that you can import multiple builddefinitions at once

Current behavior

only 1 builddefinition can be imported

Export/Import Menu Item not Displaying

Installed product versions

Export/Import Build Definition extension: 0.0.6

Description

The import/export menu item is not showing up in VSTS under the Build and Explorer tabs

Steps to recreate

  1. Open Build tab
  2. Open menu for Build Definition

Current behavior

Export/Import menu item doesn't appear

Expected behavior

Export/Import menu item appears

Export/Import Multiple Build Definitions(Folder) ?

I have got multiple Build Definitions for my Project and they all are in Folder. I would like to move them all to a new project. I cannot see Export/Import Option for the Folder. Can you please help me if there is any option?
There are 40 Build Definitions I want to move. Any suggestions? Thanks

Import not working on VS2015

Installed product versions

  • Export/Import Buid Definition extension: 0.0.2

Used this specific version because the latest version gave me this error:
Scope is not valid: 'vso.agentpools'

I followed the advice you gave Nagraj on 16Feb2017, in here: https://marketplace.visualstudio.com/items?itemName=onlyutkarsh.ExportImportBuildDefinition#review-details

Description

Exported one build and imported it into another. The second build remained unchanged.
I also tried a new build.

Steps to recreate

Manually create one build.
Export it to a file (e.g. x.json).
Manually create a second, different build (empty or not).
Import the file (x.json) to the second build.

Current behavior

The second build remains unchanged.

Expected behavior

The second build will be identical to the first.

Import/Export History with Builds/Releases Definition

Installed product versions

  • Export/Import Build Definition extension: [example 1.1.21]

Description

The requirement is to migrate the CI/CD pipeline to from one VSTS account to the other with the history, Is this feature capable to import/export the builds history when working with builds definitions. I'm also looking for something similar with releases as well for migration.

Current behavior

It looks like none of the history associated with the CI gets exported, since this the requirement that has come up.

Expected behavior

All the history associated with the builds and release definitions should get migrated from one VSTS account to the other.

Import Error: TFS.WebApi.Exception: The collection must contain at least one element.

Installed product versions

  • Export/Import Buid Definition extension: .8

Description

When importing a build definition, I receive the following error:
TFS.WebApi.Exception: The collection must contain at least one element.

Parameter name: BranchFilters

Steps to recreate

  1. Import definition.

Current behavior

Throws above error and fails

Expected behavior

Should import definition without error

Build in new team project stalling

Installed product versions

0.0.2

Description

Importing build to new project; seems to stall out on getting sources phase. We have updated the mappings to the files in the new project, but nothing is get therefore the build fails. If we change the scope from team project to project collection, it then works.

"Scope is not Valid" Error

Installed product versions

  • Export/Import Build Definition extension: 0.0.8

Description

Received the error "Scope is not valid: 'vso.agentpools'"

Steps to recreate

  1. Downloaded older v0.0.2 as per https://marketplace.visualstudio.com/items?itemName=onlyutkarsh.ExportImportBuildDefinition#review-details
  2. Imported it to TFS 2015 Update 3

Current behavior

Received error "Scope is not valid: 'vso.agentpools'".
Import/Export menu item doesn't appear in Chrome

Expected behavior

No error

can we export build for tfs 2015

Installed product versions

  • Export/Import Buid Definition extension: [example 1.1.21]

Description

Replace this text with a short description

Steps to recreate

  1. Replace this
  2. text with
  3. the steps
  4. to recreate

Current behavior

Explain what it's doing and why it's wrong

Expected behavior

Explain what it should be doing after it's fixed.

Get sources: mappings not imported

Installed product versions

  • Export/Import Buid Definition extension: [example 0.0.8]

Description

Problem with the "Get sources" build step.
Workspace mappings from "This project" are not imported. Have tested to export and re-import same project. The re-imported project contains only the Server path to the complete repo.

Steps to recreate

  1. Create TFS build project
  2. Add two workspace mappings:
    $/[project]/[name A]
    $/[project]/[name B]
  3. Add Visual Studio Build step (might be empty).
  4. Export project
  5. Re-import project

Current behavior

The workspace mappings are missing. Only one mapping exist, and it is always: $/[project]

Expected behavior

The re-imported project should have the two workspace mappings from the original exported project.

Import dialog empty

Installed product versions

  • 0.0.8
    TFS 2017

Description

Import dialog is empty

Steps to recreate

  1. Go to all build definitions
  2. Click on an elepsis for a build
  3. Click on import

Current behavior

An empty popup shows up

Expected behavior

I assume it's not supposed to be empty.

Timed out waiting for extension validation to be performed. Try again later.

Installed product versions

  • Export/Import Buid Definition extension: [example 0.0.2

Description

Timed out waiting for extension validation to be performed. Try again later.

Steps to recreate

when using onpremise tfs 2015 update3

Current behavior

install option is not coming it get upload with error as timed out

Expected behavior

Explain what it should be doing after it's fixed.

Install on AWS w/ TFS Server Error

Installed product versions

  • Export/Import Buid Definition extension: 0.0.8

Description

Install errors, saying products are missing.

Steps to recreate

  1. Download extension
  2. Transfer to AWS server through RDP
  3. Install extension

Current behavior

Error on install.

From log:

9/19/2017 4:16:46 PM - Searching for applicable products... 9/19/2017 4:16:46 PM - Found installed product - Microsoft Visual Studio Professional 2013 9/19/2017 4:16:46 PM - Found installed product - Microsoft Visual Studio 2013 Shell (Integrated) 9/19/2017 4:16:46 PM - Found installed product - Microsoft Visual Studio Enterprise 2015 9/19/2017 4:16:46 PM - Found installed product - Microsoft Visual Studio Professional 2015 9/19/2017 4:16:46 PM - Found installed product - Microsoft Visual Studio Community 2015 9/19/2017 4:16:46 PM - Found installed product - Microsoft Visual Studio 2015 Shell (Integrated) 9/19/2017 4:16:46 PM - Found installed product - Global Location 9/19/2017 4:16:46 PM - Found installed product - Visual Studio Enterprise 2017 9/19/2017 4:16:46 PM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products. at VSIXInstaller.App.GetInstallableData(String vsixPath, Boolean isRepairSupported, IEnumerable1& skuData)
at VSIXInstaller.App.Initialize(Boolean isRepairSupported)
at VSIXInstaller.App.Initialize()
at System.Threading.Tasks.Task1.InnerInvoke() at System.Threading.Tasks.Task.Execute()

Expected behavior

The install should complete successfully since TFS Server 2017 IS installed there.

Extension manifest file format is invalid

Installed product versions

  • Microsoft Visual Studio Team Foundation Server: 14.0.24606.0
  • Export/Import Buid Definition extension: 0.0.2

Description

Attempts to install the extension on TFS 2015 fail with the following error:
"Extension manifest file format is invalid".

Steps to recreate

  1. Download Export/Import Build Definition for Team Foundation Server version 0.0.2.
  2. Open Control panel - Extensions using admin account in TFS 14.0.24606.0.
    The url is http://:8080/tfs/_admin/_extensions
  3. Press "Install" button.
  4. Select Export/Import Build Definition .vsix file using "Choose file" button.
  5. Press "Ok".

Current behavior

The following message is shown:
"Extension manifest file format is invalid".
Installation can't be completed.

Expected behavior

The extension should be installed normally or instructions about how to get around the problem are provided.

Export doesn't do anything

Installed product versions

  • Export/Import Buid Definition extension: 0.0.7
  • TFS 2015 14.95.25122.0

Description

Tried to export on Chrome, Firefox and IE11. Choosing Import pops up a dialog box, but nothing happens when I right click and choose Export.

Steps to recreate

  1. Login
  2. Right click on a (new style) build definition
  3. Select Export

Current behavior

Nothing happens.
See this error in the console:
:8080/tfs/_static/tfs/Dev14.M95.3/_scripts/TFS/min/corejs?v=IiKWXrylMIeJdHBpXJwuE0SpVjVnmci79kLQuyG8-s41:22 TypeError: Cannot read property 'status' of undefined
at d (:8080/tfs/_static/tfs/Dev14.M95.3/_scripts/TFS/min/corejs?v=IiKWXrylMIeJdHBpXJwuE0SpVjVnmci79kLQuyG8-s41:64)
at :8080/tfs/_static/tfs/Dev14.M95.3/_scripts/TFS/min/corejs?v=IiKWXrylMIeJdHBpXJwuE0SpVjVnmci79kLQuyG8-s41:64
at l (:8080/tfs/_static/tfs/Dev14.M95.3/_scripts/TFS/min/q.js:27)
at :8080/tfs/_static/tfs/Dev14.M95.3/_scripts/TFS/min/q.js:27
at t.when (:8080/tfs/_static/tfs/Dev14.M95.3/_scripts/TFS/min/q.js:27)
at t.u.promiseDispatch (:8080/tfs/_static/tfs/Dev14.M95.3/_scripts/TFS/min/q.js:27)
at :8080/tfs/_static/tfs/Dev14.M95.3/_scripts/TFS/min/q.js:27
at MessagePort.t (:8080/tfs/_static/tfs/Dev14.M95.3/_scripts/TFS/min/q.js:27)

Expected behavior

Expect a file to download.

Exporting release pipeline definitaion

Hey,

I'd like to version control of our release pipelines. To do that, I need to automate exporting them from Azure DevOps.

What I have found is the API that downloads information about pipeline but not the json definition itself - all the tasks, inputs etc.

Could you help achieve it?
Thanks,
R

Unable to parse the uploaded JSON due to error TFS.Web Api.Exception

Installed product versions

  • Export/Import Buid Definition extension: Version 0.0.8

Description

Unable to parse the uploaded JSON due to error TFS.Web Api.Exception

Steps to recreate

  1. Tried the Import option on an existing build definition
  2. When trying to upload a json file, we received an error

Error

Unable to parse the uploaded JSON due to error TFS.Web Api.Exception: Tfs400813: resource not available for anonymous access. Client authentication required

This extension is not installable on any currently installed products??

Installed product versions

  • Export/Import Buid Definition extension: [Latest version (as of 2/15/18)]

Description

I just tried to install the extension and I get this:

Found installed product - Visual Studio Enterprise 2017
2/15/2018 4:45:37 PM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.

I thought that maybe it needed to be installed on the server tier, so I downloaded and installed TFS2018 and I still get the same error.

Steps to recreate

  1. run the .vsix
  2. error window appears

Current behavior

It should install

Expected behavior

It should install

Exporting Build and Importing to a different tfs server

Installed product versions

  • Export/Import Buid Definition extension: [example 1.1.21]

Description

Replace this text with a short description

Steps to recreate

  1. Export a build on server A
  2. Import the build on server B

Current behavior

Receiving message
"An error occurred while importing the definition!"
TFS.WebApi.Exception: No agent queue found with identifier 5.

Expected behavior

Importing build to server b.

Import into VSTS bring none of the previous mappings

Installed product versions

  • Export/Import Buid Definition extension: Current version as of 4/24/2017

Description

None of the repository mappings get imported. One of my build definitions has 35 mappings and they are lost on every import.

Steps to recreate

  1. Create a new build definition with mappings in VSTS
  2. Export the build definition
  3. Run Microsofts TfsMigrator import command to create a new VSTS account using our collection.
  4. Re-import the build definition and it has no mappings.

Current behavior

Explain what it's doing and why it's wrong

Expected behavior

Explain what it should be doing after it's fixed.

Won't install on Visual Studio Enterprise 2017 (Version 15.4.3)

Installed product versions

  • Export/Import Buid Definition extension: 0.0.8

Description

Won't install for TFS 2017 Update 2

Steps to recreate

  1. Download onlyutkarsh.ExportImportBuildDefinition-0.0.8.vsix
  2. Double-click on onlyutkarsh.ExportImportBuildDefinition-0.0.8.vsix

Current behavior

A pop-up occurs saying "This extension is not installable on any currently installed products"
The contents of the log file:
09-11-2017 15:47:22 - Microsoft VSIX Installer
09-11-2017 15:47:22 - -------------------------------------------
09-11-2017 15:47:22 - vsixinstaller.exe version:
09-11-2017 15:47:22 - 15.0.437+g8d2477ee3d
09-11-2017 15:47:22 - -------------------------------------------
09-11-2017 15:47:22 - Command line parameters:
09-11-2017 15:47:22 - C:\program files (x86)\microsoft visual studio\installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service\VSIXInstaller.exe,C:\Users\tqhoang\Downloads\onlyutkarsh.ExportImportBuildDefinition-0.0.8.vsix
09-11-2017 15:47:22 - -------------------------------------------
09-11-2017 15:47:22 - Microsoft VSIX Installer
09-11-2017 15:47:22 - -------------------------------------------
09-11-2017 15:47:22 - Initializing Install...
09-11-2017 15:47:23 - Extension Details...
09-11-2017 15:47:23 - Identifier : ExportImportBuildDefinition
09-11-2017 15:47:23 - Name : Export/Import Build Definition
09-11-2017 15:47:23 - Author : onlyutkarsh
09-11-2017 15:47:23 - Version : 0.0.8
09-11-2017 15:47:23 - Description : Export and Import your build definitions. Useful for recreating all the build steps, variables, schedules, etc in a different team project.
09-11-2017 15:47:23 - Locale : en-US
09-11-2017 15:47:23 - MoreInfoURL :
09-11-2017 15:47:23 - InstalledByMSI : False
09-11-2017 15:47:23 - SupportedFrameworkVersionRange : [0.0,2147483647.2147483647]
09-11-2017 15:47:23 -
09-11-2017 15:47:23 - SignatureState : Unsigned
09-11-2017 15:47:23 - Supported Products :
09-11-2017 15:47:23 - Microsoft.VisualStudio.Services
09-11-2017 15:47:23 - Version :
09-11-2017 15:47:23 -
09-11-2017 15:47:23 - References :
09-11-2017 15:47:23 - Signature Details...
09-11-2017 15:47:23 - Extension is not signed.
09-11-2017 15:47:23 -
09-11-2017 15:47:23 - Searching for applicable products...
09-11-2017 15:47:23 - Found installed product - Microsoft Visual Studio 2010 Professional
09-11-2017 15:47:23 - Found installed product - Microsoft Visual Studio Premium 2013
09-11-2017 15:47:23 - Found installed product - Microsoft Visual Studio Professional 2013
09-11-2017 15:47:23 - Found installed product - Microsoft Visual Studio 2013 Shell (Integrated)
09-11-2017 15:47:23 - Found installed product - Global Location
09-11-2017 15:47:23 - Found installed product - Visual Studio Enterprise 2017
09-11-2017 15:47:23 - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
at VSIXInstaller.App.GetInstallableData(String vsixPath, Boolean isRepairSupported, IEnumerable1& skuData) at VSIXInstaller.App.Initialize(Boolean isRepairSupported) at VSIXInstaller.App.Initialize() at System.Threading.Tasks.Task1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()

Expected behavior

Should install sucessfully

Error after import: "Cannot read property 'length' of undefined"

Installed product versions

  • Export/Import Buid Definition extension: v0.0.8

Description

Error "Cannot read property 'length' of undefined" after importing a build definition in a VSTS account, which was exported from a different VSTS account.
The build definition is about a Xamarin Android project and consists of the following tasks:

Steps to recreate

  1. Export the build definition from a VSTS account
  2. Log in in a different VSTST account
  3. Go to Builds
  4. Click Import
  5. Choose the export file and click Import

Current behavior

After the import an error is shown: Cannot read property 'length' of undefined

Expected behavior

No error should be shown, the build definition should be correctly imported

Additional information

The marketplace build tasks "Version assemblies" and "Google Play - Release" have been added to the targtet VSTS account before trying to import the build definition.

Unable to Import - TFS.WebApi.Exception: TF400813

Installed product versions

  • Export/Import Buid Definition extension: 0.0.8

Description

Export seems to work fine. Importing gives me the following error (same Collection and same Team Project):

"Unable to parse the uploaded JSON due to error TFS.WebApi.Exception: TF400813: Resource not available for anonymous access. Client authentication required."

I am using TFS 2017 (15.105.25910.0). My TFS website is HTTP. My user account is part of the Project Collection Administrators security group. Same result on IE, Edge, and Chrome.

I notice when I install the extension it asks for the following permissions:

  • Agent Pools (read)
  • Build (read and execute)
  • Build (read)

Shouldn't there be some 'write' permissions for importing?

Looks like a great extension when working! I would love to be able to use it! Thanks!

tfs 2017 import export build def install

tfs 2017 import export build def error

Export includes references to unused tasks causing issue during import

Installed product versions

  • Export/Import Buid Definition extension: 0.0.8

Description

System A has tasks available for build definitions, which are provided by a TFS extension, and are only available on this system (example: "SSIS Build & Deploy").

When exporting a build definition with your TFS extension, the resulting JSON file contains references to such tasks, although these type of tasks are not used within the exported build definition - thus causing the following kind of message during import on System B:
"Issues with icon should be resolved before importing. If you continue, you might get an ERROR during import."

Below this, one or more lines mentioning task types not existing are listed - for example:
"Task SSIS Deploy & Build 1.0.1151 by ToxicGlobe does not exist."

The strange thing here is, that the tasks are NOT used within the exported definition, so I really don't understand why they are referenced in the JSON file and - naturally - causing an issue on the target system during import.

The good thing: the build-definitions got imported despite the error displayed.
The bad thing: users will most likely get confused and calling us (the TFS admins) for help.

Steps to recreate

  1. Have two TFS on-prem systems, where System A has a TFS extension installed and active in the collection where you do an export of a build-definition, and System B does not have this TFS extension installed
  2. Create a simple build-definition in a TFS project on System A
  3. Export the build-definition created in step 2.
  4. Import the build-definition into a TFS project on System B

Current behavior

See above and attached screenshot (with an import error dialog referencing three different tasks, which are not used but referenced inside the imported build-definition).
2018-11-08 13_59_05-all definitions

Expected behavior

Build-Tasks not being used in a build-definition should not be referenced in the exported JSON file. However, if it is necessary to reference them for whatever reason, ensure that they do not cause issues during import if they are not used within the build-definition itself.

Export Build Definition Fails in Firefox

Installed product versions

  • Export/Import Build Definition extension: [0.0.2]

Description

Export build definition fails with an unresizable system dialog titled "Problem loading..." when using Firefox. A workaround to use IE instead is needed.

Steps to recreate

  1. Using an on-premises TFS site, right-click a build definition.
  2. Click "Export"

Current behavior

An unresizable system dialog titled "Problem loading..." shows up when using using Firefox.

Screenshot

Expected behavior

A download prompt for the build definition .json file is shown.

Only steps for on phase are included

Installed product versions

  • Export/Import Buid Definition extension: 0.0.8

Description

We are using TFS 2018 Update 3 on premise (16.131.28226.3)

I wanted to exporte a build definition that contains 3 phases. However the exported file only contains the first phase

Steps to recreate

  1. Create a build with multiple phases
  2. Export
  3. Open json file. You will only see the first phase in the exported file

Expected behavior

All phases should be included in the exported file.

TFS.WebApi.Exception - Resource not availible for anonymous access

Installed product versions

  • Export/Import Buid Definition extension: 0.0.2 and TFS2017

Description

Unable to export. After clicking on Export from context menu, a alert pops up With the text: TFS.WebApi.Exception - Resource not availible for anonymous Access. Client Authenticatio requireed

Steps to recreate

  1. Click on export from context menu

Current behavior

a alert pops up With the text: TFS.WebApi.Exception - Resource not availible for anonymous Access. Client Authenticatio requireed

Expected behavior

Anything but an error

Promise polyfill required?

Installed product versions

  • Export/Import Build Definition extension: 0.0.8

Description

In IE 11 - clicking export displays no error and no user feedback. Inspecting the console reveals: "'Promise' is undefined". I think this project might need a polyfill or documentation of limitations in browsers without native Promise support.

I do see that q is included with this lib, so I'm unsure what the real culprit is...

Steps to recreate

  1. Open IE11
  2. Navigate to build definition in TFS
  3. Open DevTools (F12)
  4. Select the menu ··· and "Export"
  5. Error in console

Current behavior

Fails to export - error attached.

Error

Expected behavior

Exports properly in browsers without native Promise implementations.

Thanks for the lib - works great otherwise. Ran into this attempting to migrate a build so figured I'd pass it along.

The collection must contain at least one element

Installed product versions

  • Export/Import Buid Definition extension: 0.0.8, TFS 2017.2

Description

When doing an import between two collections I get the following error: TFS.WebAPIException The collection must contain at least one element. ParameterName Pathfilters

Steps to recreate

  1. Export build in one collection
  2. Import in another

Please advise

TFS.WebApi.Exception: The user doesn't have access to the service endpoint(s) added to this definition or they are not found. Names/IDs:

Installed product versions

  • Export/Import Buid Definition extension:

Description

TFS.WebApi.Exception: The user doesn't have access to the service endpoint(s) added to this definition or they are not found. Names/IDs:

Steps to recreate

We have TFS 2018 update 2 and are on-premise
1.create endpoints in new project or collection
2. export build definitiion
3.import .json to project or collection
4. get import export window saying : if the import succeeds, it will create a new definition named TestTableauJenkins
Build queue ReportPool (id: 522) referenced in the JSON is not found. The definition will use build queue ReportPool (id: 114) instead.
5. after clicking import get message TFS.WebApi.Exception: The user doesn't have access to the service endpoint(s) added to this definition or they are not found. Names/IDs: id # here but we can't find it in our database. it changes to a different ID per user.

Current behavior

failure on import to project on same collection or project in a different collection

Expected behavior

allows to import

Either exported JSON is not valid or it is not compatible with current product. Please export again and try importing again.

Installed product versions

  • Export/Import Buid Definition extension

Description

When importing a build definition i get the following error:

Either exported JSON is not valid or it is not compatible with current product. Please export again and try importing again.

Steps to recreate

  1. just multiple build definitions from our TFS 2017 update 1 environment to import to our VSTS environment,
  2. created a new build definition with one simple buildstep that isn't custom
  3. tried a different project

all three failed with the same error

Current behavior

we cant import our buildsteps because we get the following error:

Either exported JSON is not valid or it is not compatible with current product. Please export again and try importing again.

Expected behavior

it should import the build steps

extension is not installable

Hello,

Is it installable on vs 2017 ent?

onlyutkarsh.ExportImportBuildDefinition-0.0.8.vsix

9/8/2017 4:18:37 PM - Found installed product - Visual Studio Team Explorer 2017
9/8/2017 4:18:37 PM - Found installed product - Visual Studio Enterprise 2017 (2)
9/8/2017 4:18:37 PM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.

image

Export/Import automation

Hi Team,

I found an extension where in we can export/import build definition. Is there any API's or extension to automate the export procedure?

If yes, please throw some light on it

Thanks,
Naveen Kumar

Export/Import with Secret Variable issue with V2.x agents

Installed product versions

  • Export/Import Buid Definition extension 0.02

Description

Created a build definition by importing a template.
Build on a V1.x agent and a V2.x agent.
The V2.x agent builds log show that secret variables passed to scripts are empty.

Steps to recreate

  1. Make sure you build agent is v2.x
  2. Create a new build definition
  3. Add a Secret Variable named Password
  4. Pass the secret variable to a script using $(Password)
  5. build and verify that the secret variable was passed
  6. Export the build definition
  7. Import to a new build definition
  8. build and verify that the secret variable was passed properly
    (FAIL, secret variable empty)

Current behavior

We noted that secret variable were not working for all build definition which we imported from a saved template. The build definition actually shows the secret variable properly, but the end results show that the script only get empty strings.

Expected behavior

Secret Variable should work the same as the original build definition

401 when trying to import

Whenever I try to import a definition it fails:
image

image

We're using the latest version of the extension 0.0.8

It fails with a 401 when checking the queues

VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products on Foudation 2015 installed on my Windows Server R2

Installed product versions

  • Export/Import Buid Definition extension: [example 1.1.21]

Description

VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products on Foudation 2015 installed on my Windows Server R2

Steps to recreate

  1. Replace this
  2. text with
  3. the steps
  4. to recreate

Current behavior

I have Team foudation 2015 installed on Windows server 2012 R2 I´m getting a error on the intallation.

See the log below:

1/26/2017 8:46:47 AM - Microsoft VSIX Installer
1/26/2017 8:46:47 AM - -------------------------------------------
1/26/2017 8:46:47 AM - Initializing Install...
1/26/2017 8:46:47 AM - Extension Details...
1/26/2017 8:46:47 AM - Identifier : ExportImportBuildDefinition
1/26/2017 8:46:47 AM - Name : Export/Import Build Definition
1/26/2017 8:46:47 AM - Author : onlyutkarsh
1/26/2017 8:46:47 AM - Version : 0.0.2
1/26/2017 8:46:47 AM - Description : Export/Import your build definitions. Useful for recreating all the build steps, variables, schedules, etc in a different team project.
1/26/2017 8:46:47 AM - Locale : en-US
1/26/2017 8:46:47 AM - MoreInfoURL :
1/26/2017 8:46:47 AM - InstalledByMSI : False
1/26/2017 8:46:47 AM - SupportedFrameworkVersionRange : [0.0,2147483647.2147483647]
1/26/2017 8:46:47 AM -
1/26/2017 8:46:47 AM - SignatureState : Unsigned
1/26/2017 8:46:47 AM - Supported Products :
1/26/2017 8:46:47 AM - Microsoft.VisualStudio.Services
1/26/2017 8:46:47 AM - Version :
1/26/2017 8:46:47 AM -
1/26/2017 8:46:47 AM - References :
1/26/2017 8:46:47 AM - Signature Details...
1/26/2017 8:46:47 AM - Extension is not signed.
1/26/2017 8:46:47 AM -
1/26/2017 8:46:47 AM - Searching for applicable products...
1/26/2017 8:46:47 AM - Found installed product - Microsoft Visual Studio Professional 2015
1/26/2017 8:46:47 AM - Found installed product - Microsoft Visual Studio Community 2015
1/26/2017 8:46:47 AM - Found installed product - Microsoft Visual Studio 2015 Shell (Integrated)
1/26/2017 8:46:47 AM - Found installed product - Global Location
1/26/2017 8:46:47 AM - Found installed product - ssms
1/26/2017 8:46:47 AM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
at VSIXInstaller.App.InitializeInstall(Boolean isRepairSupported)
at VSIXInstaller.App.InitializeInstall()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()

Expected behavior

Install the extension on Team foudation 2015

Override existing Builddefinitions

Installed product versions

  • Export/Import Buid Definition extension: 0.01

Description

When importing a builddefinition there is no option to override the existing build. It would be nice to have a override option

Steps to recreate

  1. export builddefinition
  2. edit the builddefinition
  3. import builddefinition

Current behavior

it makes a copy of the build

Expected behavior

override the existing build

Custom Conditions Not Importing

Installed product versions

  • Export/Import Build Definition extension: 0.0.8

Description

Custom Conditions on Tasks not imported

Steps to recreate

  1. Add a task to a build definition, or select an existing build task
  2. Add a custom condition
  3. Save and export the build definition
  4. Verify in the export that your custom condition is in the export.
  5. Import the build definition
  6. Verify that the custom condition added in step 2 is not there, this is the defect

Current behavior

The ability to import custom conditions is available in api version 3.2+

Expected behavior

Tasks with custom conditions should import successfully

Import/Export causes TFS.WebApi.Exception Error

Installed product versions

  • Export/Import Buid Definition extension: 0.0.8

Description

Import Error
image
Export Error
image

Steps to recreate

Import Error

  1. Go to Build Definitions
  2. Go to an existing build and attempt to "Import" using the context menu
  3. The error appears on Importing an JSON template.
    Export Error
  4. Go to Build Definitions
  5. Go to an existing build and attempt to "Export" using the context menu
  6. Error appears.

Current behavior

The Build Import/Export results in the an error saying:
TFS.WebApi.Exception: An Undefined error occurred while attempting to connect to the server. Status code 0

Expected behavior

Should be able to Import Builds using templates or Export Builds using existing builds.

"TFS.WebApi.Exception: 401: error" exception dialog on export

Installed product versions

  • Export/Import Buid Definition extension: 0.0.2

Description

Export fails immediately with exception dialog being shown: TFS.WebApi.Exception: 401: error

Steps to recreate

  1. Call export from the context menu
  2. Error dialog appears

capture

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.