I am trying to get cc-tray to work instead of using the web dashboard. I'm not sure how I can get the correct url for the server that my cruisecontrol is running on and I can't find any useful documentations online. Can anyone help?
Thanks
I had the same trouble and was resolved setting this Url in the Add Server (http): http://yourserver/ccnet/server/local/ViewServerReport.aspx. It works fine with this.
It depends a bit on the version you use. It is always a good idea to use the version of CCTray that you download from your running instance of the CCNet dashboard (on the dashboard, in the left column, you'll find a link 'Download CCTray').
Then it is mostly a matter of "Add Server". Older versions required a Remoting connection that requires some ports open in your connection to CCNet. Nowadays, you can connect over HTTP.
If you are using a version after 1.1 then you will want to point your CC tray client to the web dashboard site.
You should make sure you have the CCNET dashboard setup of a web server then you can do the following.
File > Settings > Build Projects (click add)
Add Server (click)
Choose Via the CruiseControl dashboard
Enter the address of your web dashboard site. Perhaps something like "yourserver.com/ccnet". You can find this via browsing to the web dashboard then copying the URL upto the folder level.
Click OK, choose the projects to watch
Profit!
Related
I am new to Azure and I have created a very simple App Service in Azure with everything default. Changed the App Service Plan to B1. I can browse the app service home page and see the default page. I then connect using FTP and try to change the default page, but it did not reflect changes.
I even downloaded publish profile and published a .net core 3.1 web api with defaults, I can see the files are deployed using FTP but the api is not present. I even deleted the default page but the home page still appears. It seems the ftp is not pointing to default location where files are being picked up by asp.net core.
You can refer my answer in this post. Then use kudu to check whether the time of the last update file via FTP is consistent with the release time. If the file is not updated, of course this update has no effect. Then we can check the FTP connection str.
But first, I suggest you to modify index.html or default interface function and update by kudu. Then check if the update file is effective. If success, I can sure you code is ok.
Second, check your FTP Connection str.
Step 1. Find Deployment Center->FTP, click FTP then you can see Dashboard, into Dashboard find FTPS Endpoint,Username and Password.
Step 2. Use FileZilla, connect it. You can see files in it.
Then you can try again. Under normal circumstances, there is no problem to update via FTP.If the problem is still not resolved, I suggest that you can deploy to local IIS for debugging.
I was facing same problem like, publish contain not displaying when visit website. then i change following settings and it worked.
I had the same issue updating files in FTP and the dlls weren't being updated as they were being used by the site. I had to stop the App Service first and then update the files. The changes then reflected when restarting it.
OK, I've created an Azure Mobile Services project in Visual Studio 2013.
I run it up as-is, then in the browser I test it by adding a todo item via the simple browser app that seems to get baked into these service projects. It gives me a '201 success' message - brilliant.
I then convert the project from IIS Express to Local IIS as the web host, recompile and try again, and although I get the same smiley face app telling me that everything is OK, when I try and add a todo item I get a 404 error. This is contrary to the Microsoft article that gives these instructions, which clearly says I am able to choose either IIS Express or Local IIS when setting up the project.
My guess is that web.config is missing something when this project runs on the local IIS server.
I'm hoping someone already has a solution before I spend hours trying to work out how to configure IIS for this type of project.
I've already wasted a load of time working through loads of bugs and gotchas with Azure Mobile, and I'm starting to run out of steam - so I'm hoping someone can help me before I go and grab an account at Parse.com
Many thanks in anticipation.
Dean
The easiest approach for your situation might be to just deploy to the cloud, and use that service for your testing. Visual Studio 2013 Update 2 makes it easy to deploy your app and connect to it for remote debugging. It is a little slower than using a local instance, but you are also assured that there will be no surprises when you eventually go live (since you are live the whole time).
That said, we will investigate the issue you are seeing with using IIS directly. Some things you might want to try on your own:
Verify that you can view the web side from your Mac's browser, to make sure that the firewall is letting the requests through.
Try using the "Getting Starting" link from the smiley-face page, to see if the REST endpoints are behaving correctly.
I have a small solution that is composed out of 2 main projects a Mvc4 Web Api and a silverlight 5 Application. I've configured and deploy the application initially on the Azure platform and it all went great, but ever since when I deploy again the silverlight project does not get pushed and the online site has the old version.
I should mention all works great with the azure simulator on my local dev machine.
Anybody had a similar issue?
Regards,
I would suspect first (as Simon suggests) that the browser likely still has the previous client cached and loads that instead of downloading your new client.
You can use the version number in the code on your page that hosts the silverlight app to help. While it's easy for you to clear the cache - you don't really want to have to tell users to do that whenever you update.
Set the version to whatever your latest assembly version is (silverlight client project assembly), this will force the browser to download the client if the cached version is a lower number.
<param name="source" value="AppPath/App.xap?version=2.0.0.6"/>
Ok,
So after pulling my hair out, I finally figured out.
I have to change the build configuration to release in VS do a rebuild and then do publish because apparently the azure project does not do rebuild on the project when you publish it.
To solve this issue you'll need to identify the source of the problem (is it a client side problem where you have a caching issue or not). Even though you say caching isn't the problem we'll need to be sure about this first.
What I suggest is that you do the following first:
Activate Remote Desktop on your role
Connect through RDP and save this file to the role: http://support.microsoft.com/kb/841290 (fciv.exe)
Find the *.xap file (usually in E:\sitesroot) and get its checksum (using fciv.exe)
Modify the Silverlight project locally (maybe change a label or move around an element) to make sure its hash has changed.
Redeploy the application
Connect through RDP and use fciv.exe to get the checksum of the *.xap file once again
Compare both checksums
If the checksums are different, then it means that the deployment worked correctly and the Silverlight xap has been updated. If the checksum is the same, the problem lies with the deployment.
Please let us know the result so we can help you find the solution.
I am using CCnet 1.6 and cctray 1.6. On the build server, the tray works properly using localhost. Remotely though, I am not able to connect the tray to the dashboard. The dashboard URL works great, but when I put that into the cctray settings, I get a 500 internal server error.
This worked up until I had to move CCnet from defaultwebsite to its own. Did I miss something when I changed it over?
Thanks,
Joe
Actually this is similar to a question I just asked but if you want to persist with remoting (but may not work so well over the Internet with firwalls and the like)
Open your dashboard.config (likely path is C:\Program Files (x86)\CruiseControl.NET\webdashboard\dashboard.config)
Find the port number your dashboard is connecting to the server on (eg: 21234)
In CC Tray, select remoting and enter hostname:portnumber (eg: mycruiseserver:21234)
Assuming that the CCNET server is part of your local network this should work:
Select .NET remoting as connection type
Specify the CCNET server's address only by its IP address (instead of using the dashboard URL)
Try switching off your firewall, it may be that you havn't opened your port.
Then, use the buildserver:port method (remotely via .NET).
I just fixed my problem (v1.8.3 for my installation).
I set the name attribute in the <server /> tag in dashboard.config to match the hostname. I'm not sure if that is required but that is the first thing I tried.
Then I inspected the bindings for the site that the dashboard is hosted under in IIS. The hostname for the binding was blank, so I changed it to the hostname for the site.
I noticed that the CCNet machine's event log had exceptions logged for unknown domain when I was trying to connect CCTray to it.
When I went to add a build server in CCTray on the remote machine, I selected via dashboard and it worked for me.
I just deployed a website into IIS 7 (about which I am woefully ignorant), and upon trying to build the site, I receive this error. I did a little googleing and I saw an article that said I should put system.web.extensions.dll into the /bin. But, I also saw an article saying not to do that. I tried it anyway, but I just received a different error ('Resource cannot be found').
I am totally clueless as to what else to try
Can you use the "Publish" command in Visual Studio to publish directly to the site? If not, then use that command to publish to a similar site on your machine, then copy it to the customer site.
You should also look into the IIS Web Deployment Tool. It can copy an entire site, including IIS settings and any databases. It will be built into VS2010.
Go to control panel, then programs, turn windows features on or off, scroll down to Microsoft.net framework 3.5.1 expand, make sure both sub options are selected, this might help your issue.