Thanks Philipe; all operation documentation is automatically updated within the software once the latest version of the relevant extension is installed (i.e. the Windows extension in this case). The documentation on the website will also get updated with any minor version of the software is released, or the Inedo.SDK is updated.

Hope this helps,
-Tod

As a followup, support for the Portable PDB format in the symbol/source server has since been added to ProGet.

The Active Directory user directory has since been open-sourced here: https://github.com/Inedo/inedox-inedocore/blob/master/InedoCore/InedoExtension/UserDirectories/ADUserDirectory.cs

This appears to be an issue with the TFS credentials provider - the 401 status code means credentials were not supplied (and the error message confirms that as well); but typically clients should followup with a 2nd request that includes credentials when the 401 is received.

If credentials are actually sent and are invalid/forbidden, then a 403 would be returned by ProGet.

This can occur if the username/password credentials for Git are invalid, or more commonly, if a Git raft is configured as read-only (which probably doesn't require authentication e.g. GitHub) then is reconfigured to support write operations.

As a followup, it's worth mentioning that this occurs specifically when directory providers are switched. The "Active Directory (New)" user directory requires the user@domain.tld format, so switching from the previous "LDAP & Active Directory" user directory (which supported netBIOSdomain\user) no longer can impersonate.

Thank you for the report; this will be resolved by the following issue: BM-3364

Hi Bret,

A tutorial for TeamCity is here: https://inedo.com/support/tutorials/buildmaster/teamcity/choosing-specific-artifact-from-teamcity

Future note, the TeamCity tutorial may be moved to https://github.com/inedo/inedox-teamcity/wiki as part of a docs re-organization.

As for controlling Apache, this is done through the httpd command, which can be executed with an Exec operation in your deployment plans, e.g.:

# Deploy to Apache
{
    Exec httpd -k stop;

    # deploy artifacts...

    Exec httpd -k start;
}

Are you granting "Anonymous" the permission to view/download packages? If you remove that from the User Tasks page, then authentication would be required.

To use script assets, use the CollectScript and/or ConfigureScript properties, for example:

# ensures the BuildMaster Agent service exists on the remote server, using a
# PowerShell script asset to perform the configuration
PSEnsure(
    Key: BuildMasterAgentInstalled,
    # returns the count of INEDOBMAGT services installed
    Collect: @(Get-Service | Where-Object {$_.Name -eq "INEDOBMAGT"}).Count,
    # expected value is 1
    Value: 1,
    # use script stored in InstallBmAgent asset
    ConfigureScript: InstallBmAgent,
    ConfigureScriptParams: %(
        AgentType: TCP,
        Port: 1000),
    Debug: true,
    Verbose: true
);