Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tfs_addon [2017/12/23 20:30] – [Enable TFS AddOn for Models] admin | tfs_addon [2020/05/10 03:34] (current) – removed admin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Microsoft TFS/VSTS AddOn Configuration ===== | ||
- | //TFS Addon// communicates with {{https:// | ||
- | |||
- | You may use any text editor to add/update settings. | ||
- | |||
- | ==== Minimum Configuration ==== | ||
- | First pick a unique name for your TFS/VSTS system, e.g. MYTFS. The name must be in uppercase. | ||
- | |||
- | Copy and paste following settings into // | ||
- | ADDON.MYTFS.CLASS=com.webmbt.alm.addon.AddOnTFS | ||
- | ADDON.MYTFS.URL=https:// | ||
- | ADDON.MYTFS.AUTH.TYPE=Basic | ||
- | ADDON.MYTFS.AUTH.USERNAME=userid | ||
- | ADDON.MYTFS.AUTH.PASSWORD=password/ | ||
- | ADDON.MYTFS.BUG.ENABLED=true | ||
- | ADDON.MYTFS.REQ.ENABLED=true | ||
- | |||
- | |||
- | ==== Enable TFS AddOn for Models ===== | ||
- | Each model that needs to access // | ||
- | * Enable [[ALMPlugin | ALM Plugin]] in the model using [[modelnode | Model Property]]. | ||
- | * Select ' | ||
- | |||
- | === Requirements Setting === | ||
- | * PROJECT=project name, required, it tells the ALM plugin which project in TFS/VSTS to search for the requirements, | ||
- | * TEAM=team name, optional, to instruct addon to pull requirement items for the specified team if REQ_WIQL has not been specified, it must be the same for both Requirement and Defect. | ||
- | * REQ_QUERY_ID=query-id, | ||
- | |||
- | === Defect Setting === | ||
- | * PROJECT=project name, required, it tells the ALM plugin which project in TFS/VSTS to search for the defects, must be the same for both Requirement and Defects setting. | ||
- | * TEAM=team name, optional, if specified it must be the same for both Requirement and Defect. | ||
- | * BUG_QUERY_ID=query-id, | ||
- | * BUG_ITERATION=iteration name - optional. if specified, it will set bug item's IterationPath accordingly | ||
- | |||
- | |||
- | ==== AddOn Settings ==== | ||
- | AddOn Settings are defined in file // | ||
- | |||
- | * ADDON.MYTFS.CLASS=com.webmbt.alm.addon.AddOnTFS | ||
- | * ADDON.MYTFS.URL=host and port pointing to your tfs/vsts server | ||
- | * ADDON.MYTFS.AUTH.TYPE=Basic | ||
- | * ADDON.MYTFS.AUTH.USERNAME=userid | ||
- | * ADDON.MYTFS.AUTH.PASSWORD=either password or access token generated from TFS/VSTS. | ||
- | * ADDON.MYTFS.BUG.ENABLED=true/ | ||
- | * ADDON.MYTFS.REQ.ENABLED=true/ | ||
- | * ADDON.MYTFS.REQ_WIQL=optional, | ||
- | * ADDON.MYTFS.BUG_WIQL=optional, | ||
- | * ADDON.MYTFS.REQ_ITEMTYPES=optional, | ||
- | * ADDON.MYTFS.BUG_ITEMTYPES=optional, | ||
- | * ADDON.MYTFS.REQ_ITEMSTATES=optional, | ||
- | * ADDON.MYTFS.BUG_ITEMSTATES=optional, | ||
- | * ADDON.MYTFS.BUG_NEWSTATE=optional, | ||
- | |||
- | |||
- | Additional AUTH_.* fields supported for OAuth and OAuth2: | ||
- | |||
- | * ADDON.MYJIRA.AUTH.OAUTH.CONSUMER.KEY | ||
- | * ADDON.MYJIRA.AUTH.OAUTH.CONSUMER.SECRET | ||
- | * ADDON.MYJIRA.AUTH.OAUTH.ACCESS.TOKEN | ||
- | * ADDON.MYJIRA.AUTH.OAUTH.SECRET.TOKEN | ||
- | * ADDON.MYJIRA.AUTH.OAUTH2.SECURITY.TOKEN | ||
- | * ADDON.MYJIRA.AUTH.OAUTH2.SIGNATURE | ||
- | |||
- | |||
- | ==== Requirement/ | ||
- | // | ||
- | |||
- | * Default WIQL - pull requirements and defect in Active,In Progress. | ||
- | * Custom item types and item state - similar to //Default WIQL// option except that you set the item types and item states | ||
- | * Custom WIQL - you specify {{https:// | ||
- | * Stored Query - have // | ||
- | |||
- | The last option is specific to each model (set in IDE [[alm_configuration| ALM_Config]]) while the rest are set for all models (set in config.properties file). | ||
- | |||
- | |||
- | |||
- | |||
- | |||