Clearcase hudson issue - continuous-integration

I have configured ClearCase plugin in Hudson .
I created a project , by giving new hudson_view_name as view name for the Hudson project and provided config spec.
I identified in my view storage directory it is creating multiple folders related to the view. like ,
hudson_view_name.vws
hudson_view_name.1.vws
hudson_view_name.2.vws
, but when I see my "cleartool lsview" command only hudson_view_name.vws is visible not the hudson_view_name.x.vws.
When I do the following command:
cleartool rmview -force -tag hudson_view_name
hudson_view_name.2.vws is being removed but hudson_view_name.vws and
hudson_view_name.1.vws remains , How can I remove those two as well.
Another question is why Hudson created many view storage locations like viewname.x.vws?

viewname.x.vws is the naming convention for view storage for views whose tag is reused.
That is the case when the view is not deleted on the client side, but only on the view server side (i.e "cleartool unregister", followed by a "cleartool rmtag"):
The view is essentially gone for ClearCase, but its client-side view storage (which is now useless) remains.
(That is what Trent Fisher says in his comment of the Hudson ClearCase Plugin page)
In this scenario, you can re-create a view by reusing the former view tag, but, since a corresponding view storage still exists, a new storage.x.vws is created.
I would really-really recommend selecting the option "use existing dynamic view" to avoid that:
(but contrary to this picture, I would not select the "Do not reset the config spec").

Related

Importing my Unmanaged Solution does not change the Account form

I have a customized Account "Main" Form in CRM.
I added a new tab, a new section, and new fields inside it.
I published all customizations before-hand, then export, then import into my test environment. I publish all in the test environment.
The Unmanaged Solution contains this form and its new fields; When I review the Form XML in the exported zip's customizations.xml file, it indeed has the new tab label, new section label, I can see the fields in the XML.
PROBLEM: But after importing and publishing into the test environment... the changes don't show up!
What I see in its place is the way that section looked BEFORE (not sure how long ago last time it was changed). It's simply not getting my latest changes.
How can an Unmanaged solution import have these issues? What else is there to check/consider? I don't think Solution Layers would cause this since it's Unmanaged, nothing stood out there anyway.
Please follow this check list, also note* with Dynamics it needs more env/info including your environment to trouble shoot, since it could be something in tandem with your env.
1. Usual Suspects in an UnManaged Solution
With yours being an UNMANAGED solution, I strongly suspect its a security permissions issue not setup/enabled in the Target environment, check your logs, you may see something like this
Try these Solution Importing steps
Import your main solution (note* without field security profiles).
Now, Publish all your customizations (note* you can enable/import the field security after this step)
Lastly, Import the second solution which would contain your field security profiles
2. Troubleshooting Checklist
To resolve/hunt down the issue, try these checklist steps
Check IIS: if you reset/restart IIS, (after define and publish your field)
Clear you client side cache: run it by
pressing Ctrl+F5
Clear you server side cache:
https://learn.microsoft.com/en-us/powerapps/maker/portals/admin/clear-server-side-cache
Are using the entity form:
Do you have the correct: entity permissions Notes & Sub Grid
https://learn.microsoft.com/en-us/powerapps/maker/portals/configure-notes
Did you add the metadata
Lastly are you using activities

How to create a Checkpoint in UFT

Strange enough that I have to ask such a simple question.
I started automating with UFT and I suppose the correct way to check if for instance my login has worked is to add a checkpoint on the next page.
But how do I do that?
All info I get from google is on how to add an already existing checkpoint to may page. But I don't have any.
Here is how I go about automating:
I add manually the relevant objects to the object repository
I create parameters for my action
I create the code that does the steps on the page
one action per page seems to be fine for me
But in the Object Repository of UFT 14.53, there is no button to add a Checkpoint.
A workaround for me would be to just add another Object and check it's existence and forget about checkpoints. Until I hopefully get an answer here, I will try to do just that.
In UFT there are typically two ways to verify that things are working as expected.
Flow (implicit) - In order to verify that progress in the application is successful (e.g. login) one usually just keeps working with the app, assuming that if the previous step failed, the objects needed for the next steps won't exist and the test will fail due to ObjectNotFound errors
State (explicit) - In order to see that objects have a specific state, checkpoints are usually used. Checkpoints are typically added during a record session, I'm not sure if there's a way to add them directly to the repository. An alternative to checkpoints, which works better with keyword driven testing (no recording), is to use the built in CheckProperty method.

'ClientFilter' validation failed: client view is too loose . each client should include one project only

I am trying to do same operations that I do with perforce GUI using command line.
When I tried to do p4 edit on any file, it said Client '<host-name>' unknown - use 'client' command to create it.
So, I tried p4 client -o <my-workspace-name> | p4 client -i but this returned:
Error in client specification.
'ClientFilter' validation failed:
======================================================
client view is too loose !!!
each client should include one project only
======================================================
I have no experience of p4 tool. Please help me explain what it means with client view too loose !!!
This is a trigger that your admin has set up. Based on the error, I surmise that they want you to set up your client's View to only include one project (they want to keep you from syncing down the entire world when you set up your new client).
To create a new client, run:
p4 set P4CLIENT=your_workspace_name
p4 client
and take a look at the form that pops up. The View field defines which part of the depot(s) your client will "see" and operate on. According to the error message, your admin wants you to restrict this to a single "project" -- I don't know what that means in this context (maybe it means just a single depot, or maybe a single folder in a particular depot?) so you might need to talk to your admin about it, or maybe browse around in the GUI and try to glean from context clues (i.e. names of directories) what that message is referring to.
Just to use a made-up example, if you have a few different depots your default ("loose") View might look like:
//depot_one/... //your_workspace_name/depot_one/...
//mumble/... //your_workspace_name/mumble/...
//widgets/... //your_workspace_name/widgets/...
and if you want to only map the project //mumble/core to your workspace root, you'd change that View to:
//mumble/core/... //your_workspace_name/...

Compare what files when update the service reference

Say I updated one WCF service, so in the client side I can view the changes by click view history on the service reference node.
My question is if I wonder what are changed between the changesets, what files should I select?
I think that I can select reference.cs to make a comparison. But is it right? There are many other files such as xsd files.
Try to right-click the service reference and view it in object browser. You could see the generated proxy class.
If you want to compare the difference between the updated service reference and the old one, you could generate client proxy class via SVCUtil.exe tool and then check all generated files.
https://learn.microsoft.com/en-us/previous-versions/dotnet/netframework-3.5/aa347733(v=vs.90)
such as,
Svcutil.exe http://localhost:1300/mex /Directory:D:

Is there a right way to add an existing SQLite database to a Xamarin project?

Every example I've found creates the database for you and then has you create tables and populate them in code. My problem, though, is that I would like to create and populate the database elsewhere (SQLiteStudio) and then include it in my app.
I sense (through the general feel of ...whatever I've been looking at. We'll call it documentation) that you are supposed to copy the database to the Environment.SpecialFolder.Personal directory. So my workflow is to include the database as a resource and then copy it to the Environment.SpecialFolder.Personal directory. Is that right? Has anyone written any of this down succinctly and authoritatively (as opposed to loose collections of articles)?
I'd prefer not to have two copies of the same database but if that's what everyone else is doing then ...okay.
I have not been able to find an answer on any of the following web pages.
https://github.com/xamarin/recipes/tree/master/Recipes/ios/data/sqlite/create_a_database_with_sqlitenet
https://forums.xamarin.com/discussion/8188/creating-database-with-sqlite-only-once
https://github.com/praeclarum/sqlite-net
https://github.com/praeclarum/sqlite-net/wiki/GettingStarted
https://forums.xamarin.com/discussion/3773/system-environment-specialfolder
https://forums.xamarin.com/discussion/36285/where-do-you-store-your-sqlite-database-in-the-app
https://learn.microsoft.com/en-us/xamarin/xamarin-forms/app-fundamentals/databases
Since you tagged pcl, have you tried treating this as an embedded resource? You pretty much just make a folder, drop in the database, and set the build action as an embedded resource. You can access the file through your SQLite library by linking up to the path of where the database is.
https://learn.microsoft.com/en-us/xamarin/xamarin-forms/app-fundamentals/files?tabs=vswin

Resources