The connector authentication is for basic auth, if you're using integrate authentication then it may not be required (assuming that it's configured properly on the Windwos/domain side)

Status code 403 is an authentication problem; so most likely, the user or account that Git is pointing to has a password or permissions change.

Ah, I see -- everything is logged to that in the database, there are no additional files. The error log is primarily for diagnostic purposes, and sometimes errors are expected. That particular error, for example, it sounds like your server is trying to connect to Inedo.com to see the available extensions. It's OK if you can't do that, but, that's where it's logged.

Alex, different Workflows, of course! Sorry I should have thought of that. Thanks!

The Click Once Action is essentially a wrapper around mage.exe; you can see exactly how this is wrapping that utility in the source code: the source code, and what those options mean at msdn. The AppCodeBase is the deployment root of your application in IIS, generally "/", but it could be "/MyApp" or something as well. If you specify "CopyFiles" in the action, then the application files and manifest will be in whatever target directory you specify. If you do not specify a source and target directory, then the default/working directory will be used for both (which means the output will be exactly where the input was -- in the $CurrentDirectory).

The current (v4) execution engine does not support Array-type variables, so this would not be possible using that technique. But we will soon (couple weeks) be shipping v4.9, which will include a brand new execution engine, that will include Array/Vector variables, so you could do something like ... foreach $value in @MyVariableList { Transform-Config (...); }

Got it working. Thanks, that helps a lot!

These "URL scanners" all use the same, third-party reporting source, so they will all report the same false positives. We have no control over that obviously, and this only seems to affect certain URLS (not files or content at the url), and only for a couple days... which reaffirms that these URL scanners are fairly worthless, since a malicious file would just use a dynamic url. If you are concerned about the url scanner, then just use a different url to download the file --- https://s3.amazonaws.com/cdn.inedo.com/XXX instead of http:///cdn.inedo.com/XXX Even if Amazon's CDN servers were compromised , you can be rest assured that, if the installer you download is signed by Inedo, then it's the package we published. You can always manually install if you are you don't trust installers. WE would appreciate, however, if you report the false positive, as that's the only way these 3rd party reporting services will update their lists.

Yes, the privileges are scoped to a certain feed. You're right, As soon as i scope to "All Feeds", login works. That's great! I'm still abit confued about how to limit some people to only one feed. They should be able to Add, View, Download packages of one feed only (including uploading packages using the web ui). Other feeds should not be visible to them. How to achieve that without scoping my privilege to a certain feed. What I didis to create a new Role "HomePageViewer" Role with only the General_ViewHomePage Task. Then, I've created two assignments for my ProductDevelopers group: Principal:ProductDevelopers, Role:Package Consumer and Adder, Scope: MyFeed Principal:ProductDevelopers, Role:HomePageViewer, Scope: (System) Would that be a recommended way or did I think too complicated?

We've finally tracked down what was causing this issue. We had two feeds configured that both had two connectors that connected back to the same ProGet server on different feeds. Turns out that this causes a very high request queue on the ProGet server, which in turn caused timeouts and eventually errors during package restore. I've now created a separate web application in IIS hosting the same ProGet folder but running on a different port and configured those two feeds to connect to the other port. This seems to alleviate the problem for now. Would be nice though if this was supported by ProGet itself. I've seen many artifact repositories that support such a feature where sort of virtualized feeds can be created by combining other feeds.

if you specify the /LogFile=[filename] argument, then the install log will be written there.

Hi, I'll try to answer the various questions here... When that publish completes successfully in TC, can we easily 'start' a build to DEV integration environment. Yes, for this , you may want to use a "URL-based Trigger" to import the build files from TC. Lastly, can we schedule a PROD release once we are done for hte middle of the night and have it alert us via text if it fails? You can schedule the promotion / deployment, and set up an event listener to email you on failure. These are extensbile, so if the SMS is needed (instead of email), you can either have a script call an SMS gateway or write an extension to do that. In addition, we don't like the non-graphical configuration, etc of bathc files as it is not overly intuitive (but works fine). Please let me know how this would work in your environment. Sure, you can run a batch/cmd file... unless it's prompting for input (like by using PAUSE command) or doing other things that can only work interactively. But, you'll find out quickly what works / doesn't. Sometimes it will be easier just to use the built-in actions in BuildMaster. Originally our organization mandated octopus, but has since undone that mandate, so I'm trying to see what options I have...The challenge is in general we have it working, so cost may be the reason we don't convert, but that is something to understand after a POC. For a comparison check out A Comparison: BuildMaster vs. Octopus Deploy .

This is likely an incorrect error that's being reported; next time you see this, just try to restart the web app by going to, Admin > All Settings > Save. This will re-establish a connection to the service on restart, and should clear this error.

This is fairly easy to reproduce -- just turn off the SQL Server. As to why it's happening, that's hard to say... perhaps it's being rebooted? Or you have network connectivity issues? If this is happening, I wouldn't disable pooling --- instead, just try to restart the web app by going to, Admin > All Settings > Save. This will re-establish a connection to the service on restart, and should clear this error. Another thing you may want to do, is to configure the service to crash on database errors; then set auto-recovery. You can do this by setting a value in your service's application configuration file, "CrashOnDbFailure" to "True", and changing the recovery settings in Windows.

The installer has an issue creating the initial database due to a (recently) undocumented change on their end, but you can fairly easily work-around the issue until the installer is adjusted for this... see Question #3924.

Would love to see a VSIX feed (didn't see a way to vote for this feature).

You recommenced ADInsight previously. It is an obsolete tool that is no longer maintained. It does not work in Windows 2008 R2 nor on machines with VMWare tools installed.

In the v5 plans (which we will ship in 4.9), you can have "output variables" from your powershell scripts. But currently, you can't communicate back to the BuildMAster execution engine via a script with anything but exit codes.

Yes, that's correct; if your doing this with a custom extension, then you can use the "StoredProcs.Variables_CreateOrUpdateVariableDefinition" method directly, and pass null in where appropriate.

We don't have a built-in mechanism to do that just yet