I am attempting to display a project level property on a widget. Global properties work fine, but project properties come up blank.
I am using:
<%= configuration('sonar.projectlevel.prop1') -%>
in the .erb file, where sonar.projectlevel.prop1 is property name. It comes up blank. If I put in a global property instead of the project property,the property is displayed.
When I open the project dashboard and go into Configuration | Settings, I can see the project property and the value. I can also retrieve it using the ws properties api specifying the resource name, so the value must be there.
Should this work? If so, how?
I have also posted this question to the mailing, but have not had a response. Surely this can work and is easy to do. I must be missing something simple.
Thanks, Ben
Simon Brandhof replied to the mailing list question with the solution. To display a project level property in a widget use:
Property.value('sonar.projectlevel.prop1', #project.id)
instead of:
configuration('sonar.projectlevel.prop1')
Thanks Simon!
Related
So the column in question was a lookup column, which i deleted in the unmanaged solution, and mistakenly created a new column with the same name. Dynamics by default will use the same auto-generated schema name based on the display name. So when I go to import the unmanaged solution in my dev environment into the production environment as managed, obviously it throws an error because of the mismatched of data types per column schema name.
Error returned by Azure Pipeline
So I did the sensible next thing, and went to delete this column in my dev environment. But oh no! There are object dependencies which prevent me from deleting it, okay I look at which objects depend on this column, it is a form, i remove the column from the form, go to delete and oh no again! There is still a dependency on the form I just deleted the column from.
So what do I do? I can't change the column schema name, I can't change the data type back to the data type that's currently in the managed solution. Is this when I open up a microsoft support ticket? Hopefully someone here has some insight. Thanks!
The attribute can be associated with a custom control. Try removing this custom control using the classic form designer. It should be visible on one of the field property tabs.
If the attribute cannot be found anywhere on the form using the classic or modern form designer, try this:
Create a solution with this form only. Export the solution as unmanaged. Extract the customization.xml from the zip. Edit the xml and remove all references to your attribute. Paste the customization.xml into the zip and import and publish the solution.
The only way to delete a managed component is to upgrade the solution. In your case, you can delete the field and dependency in solution and apply the upgrade to target environment. Please noticed that all data in this field would get deleted when you apply the upgrade. You may check this link for more detail
Is there a way to set project tags similar to project key (sonar.projectKey) in the sonar-qube.properties for tags to be automatically added during project creation?
I was looking through the docs:
https://docs.sonarqube.org/display/SONAR/Analysis+Parameters
https://docs.sonarqube.org/display/SONAR/Project+Settings
and wasn't able to find info
Thanks
It can be done via the API.
curl https://my-sonar-server.com/api/project_tags/set?project=projectName&tags=foo,bar,baz,mumble
It is there a bit hidden under Project Information, Description it is possible to add the tags there... I was a bit lost for this myself... SQ is not great in terms of UI. You can type your tags and they will be possible to filter them.
Is there a way to see TeamCity configurations that override parameter defined in template?
I don't think so. What's worked for me in the past was to search through the project files on the filesystem. If you have many build configs, this will be faster than opening each of them in the GUI.
Search for something like this:
<param name="myParamInheritedFromTemplate" value="myOverrideValue" />
in <TeamCity data directory>/config/projects/**/*.xml. If it's absent in an XML file, that build config just inherits the value. If it's present, it overrides it.
It's hacky but it's quick.
There is a feature request https://youtrack.jetbrains.com/issue/TW-21212, please vote. Current workaround are to either search the raw XML files with the settings stored under TeamCity Data Directory on the server as #sferencik suggested, or use REST API to get settings of all the build configurations and search for the parameter there. Let me know if you need help on any of these.
I am making a new biztalk solution, where i am using existing maps, schemas and orchestrations. And the orchestrations is giving me lots of problems.
I get this erorr message when I try to build my orchestration:
a 'module' must have a non-null XmlNamespace under BPEL4WS compliance
I can't find any solution to it anywhere, so I hope somebody can help me here.
What does that error mean and how do I solve it??
It turned out that if I clicked on the Project name, there is a BPEL Compliance that was set to True. Should have been set to false.
This doesn't look familiar at all.
Right click on the project and hit properties. Check to see if your assembly namespace and name are set in the 'Application' tab.
Open the orchestration and click on the background between the port surfaces. Check the namespace in the properties window.
If that doesn't work perhaps you can temporarily remove items from the orchestration to see if you can isolate which shape is causing the error.
I have had very strange issues where the orchestration namespace was incorrect.
Some projects require the BPEL Compliance setting to be true. For those projects you may have two cases:
If you do not wish to export the orchestration as a module; make sure the Module Exportable setting is false.
If you wish to export the orchestration as a module; make sure the Module Exportable setting is true together with a Module XML Target Namespace setting that has a valid value instead of being empty (or null)
I am trying to add custom field to a bug in TFS.
I opened the Bug Work Item Type but i have to enter the RefName as show in the image below.
Does any body know how can create Custom RefName
I tried to do as Ewald Hofman said, i got the below error
Just enter a name. It is used as the identifier for the column in the rest of the work item and in the warehouse.
A possible format is YourCompanyName.Category.FieldName