how can create automatically a work item when i checkin project? - visual-studio-2010

i want to create a work item (For example a task and assign to administrator) automatically when i checkin project in tfs 2010.
thanks for your help.

You can configure a CI to build each check-in and customize build process to create a task workitem and assign it to administrator.

You can set up WCF Service endpoint and subscribe to various TFS events.Check Answer 5 of this, for an example of a Checkin-Notification.Once you 're successful on that, check here for an intro on how to generate any work item using the TFS-SDK.

Related

How to trigger release pipeline when artifacts are generated from main code not from shelveset code in TFS 2017?

I am working on TFS 2017 and using release pipeline feature.
I have enabled "Continuous Deployment" and as soon as a new artifact version is available it trigger the release pipeline irrespective of whether it is generated by shelveset or by main code but I need to trigger only when the artifact is generated by main code not by shelveset .
Please Note - I cannot write ne(variables['Build.Reason'],'Shelveset') in publish task of Build definition because the manual tester needs artifacts.
Any help is appreciated
Thanks
The following is a good approach to take in TFS, using the workflow and task-based approach. Basically, you are defining a tag when that is automatically assigned to a build when a build successfully completes based on certain conditions, in the below example only if a build is scheduled, but you can customize the condition to run on all build reasons except shelveset builds too if you want.
At the end of your Build Definition create a new task for "PowerShell Script" and in the Inline Script put in the following:
Write-Host "##vso[build.addbuildtag]TriggerRelease"
Further down go to the Control Options and change the "Run this Task" to custom tasks and put the following: More variables can be found here, this is the page that details the different build.reason variables that are accessible. The conditions and how to use them can be found here
and(succeeded(), in(variables['Build.Reason'], 'Schedule'))

SonarQube 6.7: how do no-admin users create a project?

I have just installed SonarQube 6.7 and I am creating users for my colleagues, who would like to create a project from their source code hosted on GitHub repositories.
So far I did not find a way to let users create a project, without setting them as system administrator. Apparently a project is created indeed from the Create Project button on the Administration > Projects > Management page as reported in the official documentation.
Unfortunately in this way, most users should be set as admin if they want to create projects: therefore they will be able to manage the users and the whole system. As you can imagine it is not ideal situation, when a lot of administrators on a system.
How can users be able to create a project without having admin privileges over the whole system (configuration, security, users, etc.)?
I thank you in advance for your help!
Your users need the Create Projects global permission. You can grant this individually or by putting them in a group and giving the group the permission.
They'll need the Execute Analysis global permission as well (another argument for using a group). Once these permissions are granted, they'll be able to analyze projects. Any project that doesn't already exist will be created in SonarQube on the first analysis.
Vittorio C. I have the same issue as you in the SonarQube 6.7.
Issue: few options will not show up for example "create projects under global permissions"
Resolution: Just search the "create user"s in the search window( shown in the screenshot) and it will start appearing.
Also if you think any option is not appearing but which ideally should, you can apply the same trick.
for example with maven, mvn package sonar:sonar will create project if no exist in sonarqube. If you want to create it before first use you can use web api, for example have a look at https://next.sonarqube.com/sonarqube/web_api/api/projects/create If i'm not wrong the create API is open to everyone.

Enable/Disable a group of task at the time of Release Management in Visual Studio Online

How to enable/disable a group of task in Visual Studio Online at the time of Release Management by using global/local variable?
can we enable/disable by using Manual Intervention task ,if yes then how?
It is currently not posible to enable or disable tasks during a build.
You can request/vote for this feature on http://visualstudio.uservoice.com
It is impossible now, I submit a user voice here: Enable/disable task and task group by using variable
The workaround is that you can clone the release definition (right click a release definition > Clone), then remove some tasks or task groups and save it, after that you can create release with corresponding release definition per to detail scenario.

Is it possible to add subscriptions?

We have a setup so initially report is deployed to the draft folder of the server and then we manually move that report to its folder. The problem is that we have lots of subscriptions that needs to be recreated in the SSRS interface every time and thats annoying.
So is it possible to setup those subscriptions in Visual Studio so each deployed version of the report would have all subscriptions ready to go?
The project definition has event generator, which will trigger the batch file you difined, then each time you build new version the event will be triggered.
If you want to triggered the event after running some tasks of new build, you could write batch file to trigger the build and run the task.

TeamCity post-build action

We are using TeamCity Enterprise v.9.1.1
Is there a way to trigger some action after build is complete?
I have tried adding last build step but it executed before artifacts are published.
Update: I am not looking for deployment solution. I need a way to specify generic action on build completion.
There's no generic solution at the moment.
You might want vote for the Post build task feature.
Possible workarounds include:
adding dependent build configuration (using Trigger)
creating new TeamCity plugin (e.g. custom notifier plugin, such as teamcity-slack-integration one)

Resources