I need to build a report in Report Builder 2.0
The report is finished, but we use the report to view open issues and bugs. The report works fine, but now we need to set the current project ourselves in the report. I would like to pass the current project, or read it out somehow, so the report can be used in all our projects without having to change the report everytime.
So when I open the TFS portal, and select a specific project, I want the report to read the project and build the report.. That way we can use the report in all our projects.
Hope somebody can help me with this! Thanks in advance!
Ok I've found it.. If somebody issues the same problem, read this
Related
I am using Fortify Audit Workbench 18.20.1071 to do analysis on already created Fortify projects. The Fortify projects (extension .fpr) were created using standard Fortify commands. The discovered code issues, are listed on the left pane, and are grouped by categories, depending on a predefined view. When clicking on those issues, I was previously able to see the code in the source code panel/viewer/editor (separate panel to the center-right). For some reason I am not able to open that panel anymore. I don't recall changing anything in the settings, but I'm not able to see the associated code anymore.
If I create a pdf Developer Workbook report, from the Fortify project, I am able to see the source code (in the pdf file), therefore I know that the source code is available. I assume it's just some Audit Workbench settings that I need to change, but I don't know which ones.
There is no code associated with my question, as it is related to the functionality of the Audit Workbench application.
What I expect to see is the following: When I click on a listed issue on the left pane, the source code file associated with the flagged issue should open on the pane to the center-right.
Any suggestion would be greatly appreciated. Thanks a bunch!
I had the same issue using ver 19.10 and here's how I got the source code tab to show again.
Reset the config (options/options/audit configuration/reset interface)
Reboot computer
Open audit workbench and reload project
long time listener, first time caller!
I've spent two days searching for an answer to this so hopefully someone here may be able to help.
I've set up a personal/free VSTS instance and created a project.
One of the first tasks I want to do is setup the build pipeline, so create a new pipeline, define the agent pool as VS2017, connect to my Github repo etc, all of which is fine.
Next I try to add an Agent Job, again choosing VS2017 as the agent. With no other options chosen, if I try to save the build definition I get the following error message (and cannot save it);
The AllowScriptsAuthAccess build option is not supported in API versions greater than 4.0.
Allow scripts to access the OAuth token is unchecked on the Agent job configuration under phases and on the Build/Options tab (slider set to disabled)
I've googled and searched for all sorts of stuff to try and find someone with the same problem but it's almost like I'm the first to discover this - which is highly unlikely!! It has almost driven me to using Bing to search for a solution, but let's not get carried away.
Any ideas or suggestions would be greatly appreciated!
So it turns out that turning off the "New YAML pipeline creation experience" and "New Navigation" under preview features fixes the problem, insofar as I can now create and save a build pipeline without the error.
Also, if you have "Build YAML Pipelines" enabled under preview features for the Organisation, you get the "View YAML" link that I was missing also.
Thanks all for your help. I'd be interested to know the root cause of this still. I'll update the Microsoft support ticket with the same and post back here if they have any insights.
There's an similar issue here:https://developercommunity.visualstudio.com/content/problem/123012/getting-multiconfiguration-build-option-not-suppor.html
Seems the build template was broken. So, you can try with other build templates or starting over with an empty template, then add the needed tasks manually to check if that works.
Besides, you can try below things:
Clean the caches on your client machine, also clean the browser
caches, then check it again. See How to clear the TFS cache on
client machines.
Create a new team project and create a new build pipeline within the
new team project to check if that works
I am assuming this is a bug in the VSTS system and it will likely be fixed soon. But for the time being, I found a workaround:
I was also getting the AllowScriptsAuthAccess error and struggled with it for hours. I don't think any of the configuration settings you mentioned have anything to do with it (free account, GitHub, OAuth token unchecked).
To solve it, I converted the Agent Job to YAML (which is as easy as clicking "View YAML" in the upper right). Save the code to a file named .vsts-ci.yml, and save this in the root folder of your solution. Commit/push the new file, then queue the build. (Note that the conversion to YAML is one-way, so you may want to Clone your build.)
That should get rid of the AllowScriptsAuthAccess error. After that I had to add a few variables, but then it's just a matter of following the error messages.
I hope this helps. Sorry I can't answer this more authoritatively. Please post a comment if I am missing any steps.
I had this issue and it turned out that I didn't have Build Admin permissions in VSTS for the project. Not a very helpful error message for this.
We have lot of builds for each version after we integrated the CI system.
However, if we want to check the issues of one specified version, we have to select all builds of this version, which is very inconvenient.
How to resolve this problem?
You can filter Version on the dashboard.
Check the image dropdown.
There is not a way to select multiple builds at this time. I'll let the team know you are interested :)
The Application Data folder for Visual Studio could not be created, this is the problem showing in my Jenkins. Before it works, all of sudden it is not working now after restarting the machine. I tried all the ways given in on-line and given in the below document too.
http://saurabharorablog.blogspot.ca/2012/06/solution-application-data-folder-for.html
Could anyone help me. Thanks in advance.
We solved this issue by simply running Visual Studio as an Administrator. This created the necessary folders and we were able to use it normally n all scenarios after that, including in Jenkins.
Key is: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders]
Entry inside this is ‘AppData’ which had the value %APPDATA%.
Then I changed it to this value %USERPROFILE%\AppData\Roaming
Then all the applications started working as usual. I wish any of you who find similar error message could use this solution to fix it.
[NOTE: The following link is broken from the US. Perhaps other locations as well. It should not be clicked as the site it reaches does not appear safe.]
Ref:http://tutewall[do not use]com/application-data-folder-for-visual-studio-could-not-be-created/
I'm working in a project and I'm trying to optimize testing process so, when I execute a test case and I found a bug, I would like to associate this bug to the current build.
The builds are created automatically but when I try to select the built in the droplist there are not builds to select, so... How can I do it to get all the builds that I've made automatically?
Maybe is there any issue with Global List?
Im using VS 2010 and I have installed TFS 2010 Power Tools.
Thanks in advance!!
The global list is normally updated by an event subscription on the server that handles the BuildCompleted event. On your TFS server, there should be an executable named BisSubscribe.exe. You can use that to verify or fix the subscription. For more details, check out Jason Prickett's blog post on How to filter the Build Completion Event.