Having the source code for the Kitchen Sink app would be beneficial. https://github.com/vmware/clarity/wiki/Kitchen-Sink-App. http://clarity-ks.surge.sh/
Any chance this could be published?
Related
I have reportportal installation running on Windows box. I am planning to use it as dashboard to look at unit test and other automated test results. I understand reportportal integration with unit test frameworks is done at the logger level so that the test app itself can send results back to dashboard.
I have a scenario where the test application is an exe that I want to launch by sending a command from dashboard to system under test.
Are there any provisions for doing it?
Do I have to build an agent that talks to reportportal using its api for this?
Thanks
No, nothing similar at the moment.
It is pretty popular request, so we have it in backlog, but still focus on test reports aggregations first. And the other types of functionality will come later.
This may seem like a stupid question but I've been deploying updates to a development site for a project I adopted using a web deploy publishing profile.
This always takes 15 minutes or so.
However, I wanted to test a more realistic example so in order to take the app offline I followed these instructions here:
https://learn.microsoft.com/en-us/previous-versions/aspnet/ee942158(v=vs.110)#how-to-automatically-take-an-app-offline-during-deployment
So I pushed another update and kept refreshing the development site and sure enough, it showed under construction, but only for about 1 minute, and then it was back up.
However, even as I type this question, almost 15 minutes later Visual Studio is still rattling out line by line of publishing updates in the build output window.
Can someone help me understand the lifecycle of web deploy publish from Visual Studio?
According to your description, it seems that it dues to WebApp that does not enable Always on .
By default, web apps are unloaded if they are idle for some period of time. This lets the system conserve resources. In Basic or Standard mode, you can enable Always On to keep the app loaded all the time.
You could have a try to enable Always on and try it again.
If you want to understand web deploy you could refer to this article.
I am trying to create enterprise build for apple watch project by xcode 6.3
I tried to build by archive and by auto-build (shenzhen tool)
When I run it at iPhone, it crashes immediately but with ad-hoc build it's work fine.
I've found that Xcode Automatic selections do not work properly for code signing and provisioning profile when used with Apple Watch; sometimes it makes the wrong choice and you only notice when it has problems installing and launching.
For each of the App, App Extension, and Watch App, select the code signing certificate and provisioning profile explicitly (not automatic) in the pop up list.
For issues upon launch on the device (from spring board) the device console gives good information. Install iOS Console, from lemonjar.com to easily see such information.
I am not looking for Definitions for all these terms but interested in knowing "How Developers work when they are developing some software in ASP.net"
My senior has divided the project in 2 folders .first one is Development:D second is Subversion:S folder.Both folders contains same files.
While programming(development)on which folder should I work.( i mean on which file should I open to start programming : D folder or S folder ).
We are using Subversion and visual studio 2010.
If any one could explain me "Deployment scenario " then I would be very thankful to them.
Thanks.
We use SVN at our site (TortoiseSVN as client).
Each project has its own repository with three types, a Trunk, a Releases branch, and Branches. Trunk is a work in progress, Releases are snapshots of the source for major releases, and a new Branch gets created for a particular task. Upon completion a branch will get merged back into Trunk, and eventually a release gets created from Trunk.
Development phase and Production phase seem confusing, but I'm guessing development means code in the process of being developed, and production means code that has been released into the production environment. You generally don't want to do development in the production environment, you should start in development phase and once the functionality is thoroughly tested, promote it to production.
Ok.. I have looked through this site and just can't seem to find the answer I am looking for.
We have a multi server setup for our web sites, typically (DEV/QA/PRODUCTION). Our sites are .net which require some sort of build before being deployed. We are using SVN for source control and are looking for a tool/website/something that will allow our project managers to push button deploy changes to the different environments. It seems there is no silver bullet for this, am I correct in this assumption?
I like the functionality of Springloops but can't find any information regarding its use with .net. Sparing details, it would be nice to see a diagram of sorts on the whole end to end process. What I mean by that is, if multiple different tools are the only answer (no silver bullet), then a diagram that shows where the tools sit in relation to the whole process.
Look at CruiseControl.Net. It'll let you automate your builds and if there are errors it can notify certain people and even flash a big red light in the office.
The other thing it can do is automatically deploy to a chosen region such as Dev/Test/Stage/Prod when there are no errors.
Though you may want to make Prod a manual press of a button. :)
The new on click publishing features in Visual Studio 2010 are pretty easy to set up ans use: http://vishaljoshi.blogspot.com/2009/05/web-1-click-publish-with-vs-2010.html
Supports configuring IIS and deploying SQL packages too.
There is a msdeploy.exe file included in the that you could setup to run with .bat files or some configurable script runner.
Try ClickOnce deployment. Once a update is deployed on the server the client applications are automatically get updated on every client on their next run.