I know its possible to get all the developers in the system in SonarQube using : "/api/resources?qualifiers=DEV". But I want all the developers for a particular project. Basically I want to get the developer metrics of all the developers for a particular project.
Looking at your question, you are using the commercial SonarSource DevCockpit plugin for SonarQube. In such case, this means that you have purchased a license for it so you have access to SonarSource commercial support. I suggest you to contact it directly.
Related
In Plastic SCM documentation, I saw mentions of mergebot and other automation tools and I'd like to also add them to my project.
But I know nothing about DevOps stuff and I'm wondering how to do it. I found info that I need to use webadmin for this but I struggle to set up it.
Could anyone please provide some instruction steps or link to documentation? From what I tried to search there is different info about this and it's spread among a bunch of web pages (and none of them helped me).
And BTW, are automation tools available at all in CLoud Edition? And does it matter whether I work centralized or decentralized? (I use the former option)
So I contacted Plastic SCM support and it turns out mergebot isn't available in Cloud Edition, only in Enterprise
I have one small doubt regarding Microsoft.Xrm.SDK.dll. Recently I received an email from Microsoft saying they are turning off support for any Microsoft.Xrm.Sdk.dll version less than 8.2.
I am using Dynamics CRM 2016 (App version: 8.1.1.1183, DB Version: 8.1.1.1183), and SDK client to connect to this CRM. This SDK client uses Microsoft.Xrm.Sdk.dll v6.1.
I want to know will it continue to work or do I have to make change in the code and upgrade the dll?
Thanks
This is probably related to ACS deprecation (which is only applicable for online orgs):
See: https://blogs.msdn.microsoft.com/crm/2017/05/29/update-dynamics-crm-client-sdk-version-to-avoid-calls-to-acs/
With the deprecation of Azure Access Control Service (ACS), you should
modify the SDK authentication code by removing all references to ACS.
Effective from Microsoft Dynamics CRM Online 2016 Update 1 (v8.1.1)
and Microsoft Dynamics 365 (v8.2), we removed Live ID support and ACS
dependencies on the server-side. It is required to update the
references in all client side components by updating the SDK.
For custom applications you need to make sure you have the correct version of the SDK.
Custom Application(s) – If you have developed a Web/Windows/Console
application that is interacting with Dynamics CRM
Scan the folders on your server where the solution is running and look for: Microsoft.XRM.SDK.dll. If found, use the table given in the
Team Blog site to determine which version of the SDK you need to
download.
Using the table, determine which version of .NET that you have deployed against, and confirm the version of Dynamics 365 CRM service
you are using. If you are uncertain which .NET version your solution
is using, contact your development or engineering teams.
Once you have determined the correct SDK version to use simply replace the Microsoft.XRM.SDK.dll found in /bin folder with the latest
version of the SDK dll.Replace Microsoft.XRM.SDK.dll with latest
version of SDK dll
I recommend you to go through the MSDN blog
Without knowing when & where (which CRM version your) project started & staying in 2016 now and what’s your future project plans (whether sustenance mode or stay current), could not comment on action.
As a general practice, do a pilot with an upgrade in separate copy/sandbox & see. Then plan for code Update & sdk upgrade in Live.
I'm searching for a well documented XACML3-Framework in the open source world. I tried AuthZForce and AT&T XACML. Both seems to have many features. The problem: to get them running, I have to read the source code or find test-classes. There are no examples or anything else, that helps to understand the functionality of the framework. I thought XACML is the future of authorization but at the bottom there is no real community.
Is there an XACML-alternative for ABAC-implementations or is there no other way and I must use RBAC with programmed constraints?
Regarding AuthzForce Core (Java library), you have a tutorial on the home page of the github project: Getting started; and an example of usage with a PEP in a real-world scenario. If you are missing info on something, feel free to contact us on our support mailing list. I also emphasize the fact that all Java classes have Javadoc and Javadoc artifacts are published on Maven Central with every release. You can download them manually or make sure your IDE is properly set up to automatically download them when you use Maven dependencies in your Java project.
WSO2 IS can help (opensource):
https://docs.wso2.com/display/IS510/XACML+Architecture
http://wso2.com/library/tutorials/2016/02/tutorial-how-to-enable-role-based-access-control-for-wso2-api-manager-using-xacml/
Policy handling can be done via web interface (Carbon).
ON TFS2012 is it possible to request feedback from customers that are utilizing the web client without them having to install feedbackclient.exe on their machines
Usersnap allows customers to add feedback without installing anything locally. It integrates into Microsoft Team Foundation Service (this means, every feedback from your customers is automatically created as ticket inside your TFS workflow).
Your customers even don't need an account in TFS to provide feedback.
It's easy to integrate Usersnap with TFS, you can have a look at the docs here: https://usersnap.com/support/docs/apicfg#tfs
To work with the feedback request like it is explained here it is not possible to give feedback without installing the client tool.
I thought it would work also by logging in in the TFS web interface then open the feedback request and answer to it but apparently after testing it myself I did not found a solution directly. Though the feedback would be filled in completely manually while all the needed tools are available with the client tool.
I have developed an extension to Magento Community edition.
I would like to test it on the Enterprise edition.
How can I do that?
Do you think there will be changes between those versions code-wise?
Thanks
I use EE daily. All the differences I can detect are in the form of extra modules in "app/code/core/Enterprise", class names start with "Enterprise" instead of "Mage", some are encoded with ionCube. There is an "enterprise" theme too but it is very similar to "modern". The rest of Magento is the same as the Community Edition so your extension will likely work on both equally.
However you cannot claim compatibility without testing it, that would be irresponsible. It is possible you have overridden something which is then later re-overridden by the other edition. You probably don't want to buy a years licence just for that so you'll have to ask for volunteers, the best places are Magento's forum and chat. Failing that you could advertise on one of the many freelance programmer sites for someone who is in a position to help, that will be cheaper than a whole copy of EE.
Lastly there is the issue of registering on Magento Connect. So far only aheadWorks have the privilege of appearing in the "Enterprise Ed." section. (The "Professional Ed." section isn't even active yet.) You may not get a chance to list your extension there although you can always explain the salient parts on your own website.
Magento Enterprise edition differs from Community edition by following items:
1) There are additional modules, that complement Mage modules. They all have Enterprise namespace (Enterprise_ prefix instead of Mage_ prefix). Enterprise modules either add some new functionality, or modifiy behaviour of Mage modules.
2) Enterprise has its own design scheme. About 30% of templates are overriden, others fall back to base/default theme
3) Enterprise has different license
So, reviewing mentioned above, you cannot guarantee stable work of your CE extension without testing it on EE. It's very probable that your module will fork fine, but I'd estimate a 10% probability that your extension requires some fixes to work normally with EE.
Strictly speaking, you can test your extension only having your own Magento EE ($10 000+).
However there's the other way. Magento EE license allows the buyer to give access to his Magento EE version to people, that are developing some functionality for buyer's Magento. So you can sell your extension to someone having Magento EE, notifying him, that it was not tested on EE and you need to do it. Your client will give you access to his Magento EE and you'll be able to test and debug the extension. That conforms Magento EE license, because you'll be a hired developer for Magento EE owner and you'll be developing extension for his Magento EE.
Of course you should notice that your account at Magento Connect must have special access to posting EE-extensions - usual account can not do this. You need to ask Magento support how to get such privilege.
From my own opinion I recommend do not bother with EE functionality, as it's not easy to perform whole process of testing and posting it as EE extension. CE market is wider (although not so money-full), so you can sell it here.
I agree with clockworkgeek that you are likely not to have any problems, but also that there are overrides in Magento EE that you need to be aware of. Please do find an EE installation to check on, as there may be changes.
I have developed a magento module. It works fine for community edition and enterprise edition in my local environment. After installed it in the live site it works fine for community edition, but not for enterprise edition. It is not showing any admin configuration in enterprise edition. Am I missing anything?