Knowledge Base

Welcome to the Inedo Knowledge Base

The knowledge base is a collection of small articles that are BuildMaster, ProGet, or Inedo related. Use the search box below to search for articles.

All Articles

KB #1106: Upgrade Notes for ProGet 3.8

Last Updated: 8/26/2015

<a href="/proget/3.8">ProGet v3.8</a> is a minor release, and introduces the following changes/additions:

KB #1104: Upgrade Notes for ProGet 3.7

Last Updated: 8/26/2015

<a href="/proget/3.7">ProGet v3.7</a> is a minor release, and introduces the following changes/additions:

KB #1102: Upgrade Notes for ProGet 3.6

Last Updated: 8/26/2015

<a href="/proget/3.6">ProGet v3.6</a> is a minor release that introduces the Feed Retention feature, adds a unified system for scheduling tasks, and updates the UI for feed administration.

KB #1099: Upgrade Notes for ProGet 3.5

Last Updated: 8/26/2015

<a href="/proget/3.5">ProGet v3.5</a> is a minor release that introduces the Feed Sync feature, adds better support for tracking events, and has a few other minor performance and security enhancements.

KB #1105: BuildMaster 4.8 Upgrade Notes

Last Updated: 8/7/2015

<strong>TLDR; application groups can now be grouped within other groups, application navigation and overview has changed, and error logging is handled and filtered differently</strong>. Please read these notes to see how this will impact you and what you can do to mitigate risks.

KB #1100: Getting Started with ProGet for Linux

Last Updated: 6/29/2015

Starting with ProGet 4.0, we plan to officially support Linux installations.

KB #1077: Configuring BuildMaster to Run As a Windows Domain Account

Last Updated: 6/29/2015

During BuildMaster installation, you can select the user account that BuildMaster will run as:

KB #1103: BuildMaster 4.7 Upgrade Notes

Last Updated: 6/5/2015

<strong>TLDR; new operations for the 5 most popular Source Control Providers and the 3 most popular Issue Tracking Providers</strong>. Please read these notes to see how this will impact you and what you can do to mitigate risks.

KB #1038: Scriptable BuildMaster Agent Deployment

Last Updated: 6/5/2015

As of BuildMaster v4.0, this article is deprecated. Agent silent installation can be accomplished by running the installer from the command line. See the following documentation for more information: <a href="/support/documentation/buildmaster/installation/silent-agent-installation">BuildMaster Silent Agent Installation</a>

KB #1101: ProGet Maven Preview

Last Updated: 4/27/2015

Starting with ProGet 3.7, we plan to officially support Maven repositories.

KB #1098: Introducing ProGet Feed Sync

Last Updated: 2/23/2015

We've partnered with <a href="http://myget.org/">MyGet</a> to bring you the <b>Feed Sync</b> feature in ProGet 3.5. Feed Sync allows you to synchronize the NuGet packages on multiple ProGet servers through the cloud.

KB #1063: A Comparison: BuildMaster vs. Octopus Deploy

Last Updated: 1/30/2015

<a href="http://octopusdeploy.com/">Octopus Deploy</a> and BuildMaster are different products that can both be used to automate .NET deployments. There are several difference between the two products, but the largest is in the scope and problem space the products are designed to solve:

KB #1097: BuildMaster 4.6 Upgrade Notes

Last Updated: 1/15/2015

<strong>TLDR; new operations for BuildMaster administration</strong>. Please read these notes to see how this will impact you and what you can do to mitigate risks. 

KB #1096: Upgrade Notes for ProGet 3.4

Last Updated: 1/15/2015

<a href="/proget/3.4">ProGet v3.4</a> is a minor release that introduces some performance and indexing enhancements, and adds support for Bower feeds.

KB #1095: Introducing Bower Support for ProGet

Last Updated: 1/9/2015

As of version 3.4, you ProGet now supports adding a Bower feed type. This package management system uses metadata similar to npm, but is designed more for browser-based development. See <a href="http://bower.io/">bower.io</a> for lots more about Bower.

KB #1087: Introducing npm Support for ProGet

Last Updated: 1/9/2015

ProGet now supports a new type of feed as of v3.2: npm. This popular package management system is used with <a href="http://nodejs.org/">Node.js</a> to enable easy dependency management of node modules, but if you are reading this article, you probably already knew that.

KB #1048: Releases vs. Builds

Last Updated: 12/17/2014

The content of this article has been moved to the <a href="/support/documentation/buildmaster/core-concepts/releases">documentation section for Releases</a>.

KB #1018: Automatically Promoting Builds to Environments

Last Updated: 12/17/2014

As of BuildMaster v4.4, this article is deprecated because automatic promotions are a core component of workflows. Simply add a <b>Automotically Promote Build to the Next Environment</b> post-deployment step to any workflow or build step achieve this behavior.

KB #1094: About ProGet Legacy Feeds

Last Updated: 11/24/2014

ProGet 3.3 changes the way NuGet feeds are stored and indexed. If you have upgraded from an earlier version, you will see a notice on existing feeds about migrating to the new type. For instructions on performing this migration, please see <a href="/support/kb/1092">KB#1092</a>. This article describes the changes that were made and the reason for the changes.

KB #1093: Upgrade Notes for ProGet 3.3

Last Updated: 11/21/2014

<a href="/proget/3.3">ProGet v3.3</a> is a minor release that introduces many performance and indexing enhancements, changing the way packages are stored on disk for the default package store, and changing the way they are served by the ProGet server.

KB #1092: Migrating Legacy ProGet Feeds

Last Updated: 11/21/2014

ProGet 3.3 supports a new, more efficient method for storing NuGet packages. If you've upgraded an existing installation to 3.3 or newer, you will need to migrate your existing feeds to the new format if you want to take advantage of all of the performance improvements. Note that your legacy feeds will still work; they will just continue to consume system resources for large numbers of packages as in previous versions.

KB #1091: BuildMaster 4.5 Upgrade Notes

Last Updated: 11/5/2014

<strong>TLDR; major configuration file module changes</strong>. Please read these notes to see how this will impact you and what you can do to mitigate risks. 

KB #1090: Granting Service Control Privileges for the BuildMaster Web Application

Last Updated: 11/5/2014

In order to be able to restart a Windows service, you normally need to be running as a machine administrator. However, it may not be desirable or even permitted to run the BuildMaster web application as an administrator account in your environment. This means that you will not be able to control the BuildMaster service using the web interface.

KB #1086: BuildMaster 4.4 Upgrade Notes

Last Updated: 11/5/2014

<strong>TLDR; major promotion workflow changes</strong>. Please read these notes to see how this will impact you and what you can do to mitigate risks.  Or as Abe Lincoln once said, <em>give me six hours to chop down a tree and I will spend the first four sharpening the axe</em>.

KB #1089: Upgrade Notes for ProGet 3.2

Last Updated: 10/3/2014

<a href="/proget/3.2">ProGet v3.2</a> is a minor release that introduces npm registry support and adds support for high-availability installations and load-balancing options. This version essentially replaces what would have been the v3.1.8 maintenance release, and all users who were planning to upgrade to v3.1.8 for bugfixes should upgrade to v3.2.X instead.

KB #1073: Load-balanced and High-availability Installation of ProGet

Last Updated: 10/3/2014

For environments that need load-balancing or high-availability, a single ProGet installation can utilize multiple servers.

KB #1003: .NET Assembly Versions with BuildMaster

Last Updated: 9/30/2014

.NET assemblies include a variety of metadata, most of which are typically defined in code in a file like AssemblyInfo.cs. When compiled, this metadata will be embedded in the resulting assembly. This article concerns two attributes typically placed in AssemblyInfo.cs:

KB #1088: Using PowerShell to Install and Configure ProGet

Last Updated: 9/29/2014

Since ProGet supports silent installation, it is pretty straightforward to automatically deploy it as part of a script. However, it is also possible to use the SQL API to add some standard initial configuration.

KB #1014: Changing BuildMaster’s or ProGet’s URL with the Integrated Web Server

Last Updated: 8/21/2014

Both BuildMaster and ProGet can run using an Integrated Web Server instead of IIS. While this offers a simpler configuration and installation, the integrated web server lacks many of the advanced features of a full-fledged web application server, and certain configuration is far from obvious. For example, this post will cover binding the integrated web server to a host name.

KB #1046: Supported SQL Server Editions

Last Updated: 8/12/2014

BuildMaster and ProGet have the same database requirements. This table summarizes the options available:

KB #1085: Upgrade Notes for ProGet 3.1

Last Updated: 6/20/2014

<a href="/proget/3.1">ProGet v3.1</a> is a minor release that introduces some helpful features regarding symbol serving, and connector improvements. This version essentially replaces what would have been the v3.0.4 maintenance release, and all users who were planning to upgrade to v3.0.4 for bugfixes should upgrade to v3.1.X instead.

KB #1084: Upgrade Notes for BuildMaster 4.3

Last Updated: 6/20/2014

<strong>TLDR; major deployment plan and deployment execution changes</strong>. It’s another big one. Please read these notes to see how this will impact you and what you can do to mitigate risks.  Or as Benjamin Franklin would say, <em>by failing to prepare, you are preparing to fail</em>.

KB #1083: Upgrade Notes for ProGet 3.0

Last Updated: 6/20/2014

<a href="/proget/3.0">ProGet 3.0</a> is a major release that introduces a new suite of deployment features for ProGet. These features have been added side-by-side, such that upgrading to v3.0 from v2.2 should introduce very little risk beyond that of a typical maintenance release upgrade. If you are upgrading from a version before v2.2, make sure to view the <a href="/support/tag/upgrade-notes" target="_blank">upgrade notes</a> for all minor versions prior to this one.

KB #1082: Upgrade Notes for BuildMaster 4.2

Last Updated: 6/20/2014

<strong>TLDR; major variable and deployment plan changes</strong> - if you are upgrading to 4.2, you  really should spend a few moments to read this article to see how this upgrade may impact your configuration. You know what they say about an ounce of preparation…

KB #1081: Upgrade Notes for BuildMaster 4.1

Last Updated: 6/20/2014

<a href="/buildmaster/4.1">BuildMaster 4.1</a> is a minor release with the following changes:

KB #1074: Upgrade Notes for ProGet 2.2

Last Updated: 6/20/2014

<a href="/proget/2.2">ProGet 2.2</a> is a minor release of ProGet with the following changes and bug fixes:

KB #1066: Upgrade Notes for BuildMaster 4.0

Last Updated: 6/20/2014

Please read this document carefully as there are several changes which may impact your installation, configuration, and customizations of BuildMaster.

KB #1049: ProGet Client Tools Roadmap and Known Issues

Last Updated: 4/25/2014

<i>April 25, 2014</i> - While these tools were never officially supported, the ProGet Client Tools are being officially removed due to extreme lack of demand. We will still offer the ProGet.exe tool for automated deployment and testing scenarios, but will only support its use in conjunction with a valid BuildMaster license.

KB #1052: Troubleshooting Failed Builds and Deployments

Last Updated: 4/8/2014

While BuildMaster is designed to automate your entire build and deploy process without error, there are times when errors do occur when a build is executed. While most errors will be self-documenting in the deployment log, others may be a little trickier to track down. This article will present some of the most common troubleshooting ideas for any failed build.

KB #1024: Integrating BuildMaster and Mercurial

Last Updated: 2/18/2014

Since Mercurial is a Distributed Version Control System, BuildMaster can either connect to a local repository, or connect to a remote repository in order to function as a source control provider.

KB #1076: Introducing ProGet Deploy

Last Updated: 1/13/2014

This content has been superseded by <a href="/support/tutorials/a-gentle-introduction-to-proget-deploy">A Gentle Introduction to ProGet Deploy</a>

KB #1079: Common Uses for Variables

Last Updated: 12/20/2013

KB #1078: Using the Loupe Live Session Viewer to Debug the Service

Last Updated: 12/19/2013

The BuildMaster service ships with an instance of the live logging product named <a href="http://www.gibraltarsoftware.com/" target="_blank">Loupe from Gibraltar Software</a>. Loupe allows you to view all log information written out by the BuildMaster service in real time. It can be used to troubleshoot bugs or other oddities that can arise from an automated deployment scenario.

KB #1015: Running the BuildMaster Service(s) Interactively

Last Updated: 12/19/2013

Note: You will have to stop the BuildMaster service in order to run the service interactively. If BuildMaster is running on a production system, you might consider <a href="/support/kb/1078/using-the-loupe-live-session-viewer-to-debug-the-service">using the Loupe Live Session Viewer to debug the service</a> instead.

KB #1013: Hosting BuildMaster or ProGet Through IIS Instead of the Integrated Web Server

Last Updated: 12/12/2013

When you install BuildMaster or ProGet using the installer, you’re presented with two application hosting options: Integrated Web Server or IIS Web Application.

KB #1071: Upgrade Notes for BuildMaster 3.7

Last Updated: 11/21/2013

BuildMaster 3.7 exists only to provide support to for users who cannot yet upgrade to BuildMaster 4.x; we advise upgrading directly to BuildMaster 4.0 or later.

KB #1067: BuildMaster 4.0 Beta Notes

Last Updated: 11/21/2013

<strong>This article is outdated, as BuildMaster 4.0 is no longer in beta.</strong>

KB #1064: Upgrading Agents for BuildMaster 4.0

Last Updated: 11/21/2013

For BuildMaster 4.0, we have taken advantage of the major version change to make several breaking changes that prevent BuildMaster from automatically updating 3.x agents:

KB #1075: Upgrading Extensions in BuildMaster 4.0

Last Updated: 11/12/2013

Because of the .NET Platform and SDK changes, all extensions built against pre-4.0 SDK versions must be updated. Your custom-built extensions must be recompiled against the new SDK. After upgrading to BuildMaster 4.0, you'll be presented with an upgrade checklist that will look similar to:

KB #1072: ProGet vs. NuGet.Server

Last Updated: 10/17/2013

<a href="https://www.nuget.org/packages/NuGet.Server">NuGet.Server</a> is designed with the primary goal of being the website hosted at NuGet.org, which is the definitive source for open source packages submitted by multiple authors that are available to the public. With a bit of set up and some customization, it can be adapted to become a private server. If you want to host open source packages on the public internet, or create a similarly purposed project like <a href="http://chocolatey.org/">Chocolatey</a>, then NuGet.Server is a perfect fit.

KB #1070: Writing an Agent-based Action

Last Updated: 10/10/2013

As of BuildMaster 4.0, there is a new base class for custom actions called <font face="Consolas"><a href="/support/sdk-reference/buildmaster/Inedo.BuildMaster.Extensibility.Actions/AgentBasedActionBase">AgentBasedActionBase</a></font>. Like <font face="Consolas"><a href="/support/sdk-reference/buildmaster/Inedo.BuildMaster.Extensibility.Actions/RemoteActionBase">RemoteActionBase</a></font>, <font face="Consolas">AgentBaseActionBase</font> is intended for actions which execute against a specific server. However, unlike <font face="Consolas">RemoteActionBase</font>, there is no automatic proxying performed. Instead, you request access to various services using the <font face="Consolas"><a href="/support/sdk-reference/buildmaster/Inedo.BuildMaster.Extensibility.Agents/AgentBase/GetService(TService)">GetService</a></font>method accessible from the <font face="Consolas"><a href="/support/sdk-reference/buildmaster/Inedo.BuildMaster.Extensibility.Actions/IAgentBasedActionExecutionContext/Agent">AgentBasedActionBase.Context.Agent</a></font> property.

KB #1069: BuildMaster 4.0 SDK Changes

Last Updated: 10/4/2013

BuildMaster 4.0 makes a number of significant breaking changes with previous SDK versions. This article will help prepare you for updating any custom extensions you may have.

KB #1068: BuildMaster 4.0 UI and UX Tour

Last Updated: 9/26/2013

While the new UI for BuildMaster 4.0 may look completely different from the &lt; 4.0 versions, we’ve tried to maintain much of the same functionality, and only make improvements where they were needed most. This article will describe the differences between both the UX and UI in each version.

KB #1065: Running the UTC date fix tool

Last Updated: 9/26/2013

<strong>Note: This article only applies to users who have upgraded a BuildMaster installation from a pre-4.0 version to a 4.0+ version.</strong>

KB #1062: Upgrade Notes for ProGet 2.1

Last Updated: 9/26/2013

ProGet 2.1 is a minor release of ProGet with the following changes and bug fixes:

KB #1061: Connecting BuildMaster to Subversion over SSH

Last Updated: 9/26/2013

Creating a Subversion provider requires that the Subversion extension v3.5 or later is installed. Once the extension is installed, select "Admin" &gt; "Configure Source Control Integration" and "Create New Source Control Provider". This will bring up the familiar provider editing dialog.

KB #1060: Upgrade Notes for BuildMaster 3.6

Last Updated: 9/26/2013

BuildMaster 3.6 is a minor release of BuildMaster with the following changes:

KB #1059: When should I update BuildMaster?

Last Updated: 9/26/2013

Updating any software to a newer version requires users to weigh the costs associated with the update process against the value and benefits of the new features or bug fixes added – and this is no different with BuildMaster. BuildMaster is designed and released through a process (<a href="/specifics/buildmaster-overview">using BuildMaster of course</a>) that permits a super-agile deployment methodology, allowing many releases to occur in a short time frame.

KB #1057: A Comparison Between BuildMaster vs. Hudson

Last Updated: 9/26/2013

<a href="http://hudson-ci.org/">Hudson</a> and BuildMaster are different products, the main difference being that Hudson is a Continuous Integration server (i.e. it will automatically take code from SCM, build it, then put artifacts on an integration server), while BuildMaster can <a href="/buildmaster/features/continuous-integration">perform Continuous Integration</a> related tasks, and additionally set up plans for your builds to be deployed through various environments (development, test, production, etc.) while also:

KB #1056: A Comparison Between BuildMaster vs. Jenkins

Last Updated: 9/26/2013

<a href="http://jenkins-ci.org/">Jenkins</a> and BuildMaster are different products, the main difference being that Jenkins is a Continuous Integration server (i.e. it will automatically take code from SCM, build it, then put artifacts on an integration server), while BuildMaster can <a href="/buildmaster/features/continuous-integration">perform Continuous Integration</a> related tasks, and additionally set up plans for your builds to be deployed through various environments (development, test, production, etc.) while also:

KB #1055: Integrating Hudson with BuildMaster

Last Updated: 9/26/2013

The <a href="/buildmaster/extensions/Hudson">Hudson extension</a> includes actions for both creating builds in Hudson and retrieving/extracting artifacts from the Hudson server. For this extension to work correctly, the BuildMaster server must be able to access the Hudson server.

KB #1054: Integrating Jenkins with BuildMaster

Last Updated: 9/26/2013

The <a href="/buildmaster/extensions/jenkins">Jenkins extension</a> includes actions for both creating builds in Jenkins and retrieving/extracting artifacts from the Jenkins server. For this extension to work correctly, the BuildMaster server must be able to access the Jenkins server.

KB #1053: Troubleshooting BuildMaster Installations

Last Updated: 9/26/2013

We try to make installing BuildMaster as simple as possible, and while it usually installs with no issues, once in a while something goes wrong (which is probably why you are here reading this).

KB #1051: Upgrade Notes for ProGet 2.0

Last Updated: 9/26/2013

ProGet 2.0 is a major release of ProGet with the following changes:

KB #1050: Differences Between ProGet Client Tools and NuGet Tools

Last Updated: 9/26/2013

Whereas NuGet is designed to make using the latest open-source libraries incredibly easy, ProGet is designed to serve as an enterprise dependency management system. This is why ProGet's server has concepts like authentication, access controls, and auditing. However, as we learned through our ProGet Enterprise users, NuGet's client tools made it challenging to enable the workflows needed in enterprise environments.

KB #1047: SQL Server 2005 and Windows 8

Last Updated: 9/26/2013

BuildMaster/ProGet requires any SQL Server from 2005 to 2012 to be installed. As a database-based application, there’s no getting around that. To make installation simpler for users that would just like to quickly get started using or evaluating the software, we distribute an installer with SQL Express 2005 included, and provide the option of automatically installing an instance as part of installation.

KB #1045: Highly Experimental and Other Feature Levels

Last Updated: 9/26/2013

If you've spent even a few minutes using BuildMaster, you've probably noticed that there are a whole lot of features and options. Some might even say, <em>too many options</em>. But because we want BuildMaster to be used by both developers who've never automated a build and release engineers with a decade of experience, we need a user interface that can work for all users. To accomplish this, we have a concept called <em>feature levels</em>.

KB #1044: Which API Should I Use (SOAP, JSON, SQL)?

Last Updated: 9/26/2013

There are three primarily channels for communicating with BuildMaster via the BuildMaster API:

KB #1043: Creating a Copy Action Recipe On-Demand

Last Updated: 9/26/2013

Yesterday we received an email in our support box asking for the ability to copy deployment plan actions within a single action group in BuildMaster. While there is already a mechanism to copy or share action <em>groups</em>, the ability to copy actions would greatly reduce deployment plan creation time for multiple build actions that require a lot of configuration within the same group.

KB #1042: Upgrade Notes for BuildMaster 3.5

Last Updated: 9/26/2013

BuildMaster 3.5 is a semi-major release of BuildMaster with the following changes:

KB #1041: Purging Build Artifacts

Last Updated: 9/26/2013

A good deployment plan will usually involve creation of one or more build artifacts. Eventually, one set of artifacts will be created as part of the build that gets deployed to production, but with very large artifacts it can be problematic to keep all of the ones that were generated for each rejected build. This is especially a problem when builds are created frequently – for example, as part of a CI strategy.

KB #1040: Securing Self-Hosted Agents using SSL

Last Updated: 9/26/2013

BuildMaster Agents exposed to the Internet should include additional security compared to agents running on a secure local network. The self-hosted agents in BuildMaster support the use of SSL encryption just like agents hosted using IIS.

KB #1039: Comparison of BuildMaster Agents

Last Updated: 9/26/2013

For BuildMaster to orchestrate a remote server, an Agent is required. Currently, BuildMaster has four types of agents:

KB #1037: Upgrade Notes for BuildMaster 3.3

Last Updated: 9/26/2013

BuildMaster 3.3 is a minor release of BuildMaster with the following changes:

KB #1036: Using ProGet's Symbol Server

Last Updated: 9/26/2013

ProGet Enterprise includes an integrated symbol/source server that makes .pdb symbol files stored in a Feed's packages accessible directly from a debugger such as Visual Studio.

KB #1035: Integrating FogBugz with BuildMaster

Last Updated: 9/26/2013

<a href="http://www.fogcreek.com/fogbugz/">FogBugz</a> is web-based bug-tracking software that is available both as a hosted service, and as software you install on your own server. The <a href="http://inedo.com/buildmaster/extensions/FogBugz">FogBugz Extension</a> includes a BuildMaster Issue Tracking Provider that allows you filter FogBugz items as a BuildMaster application’s issue tracker. If you are unfamiliar with configuring Issue Tracking Providers in BuildMaster, see <a href="http://inedo.com/support/kb/1006/integrating-an-issue-tracker-with-buildmaster">Integrating an Issue Tracker with BuildMaster</a>.

KB #1034: Uploading Files to Windows Azure Blob Storage in BuildMaster

Last Updated: 9/26/2013

<a href="http://www.windowsazure.com">Windows Azure</a> is a cloud service, so your BuildMaster server must have access to the internet for this extension to work properly. The <a href="/buildmaster/extensions/azure">Azure extension</a> includes an action for uploading files to Azure blob storage and must be installed from the Extension Gallery for the action to be available within BuildMaster.

KB #1032: The Difference Between Deployables and Applications

Last Updated: 9/26/2013

From the BuildMaster Documentation, we know that an <a href="/support/documentation/buildmaster/applications">application</a> is defined as:

KB #1030: Integrating Amazon Web Services with BuildMaster

Last Updated: 9/26/2013

AWS is a cloud service, so your BuildMaster server must have access to the Internet for this extension to work. The Amazon extension includes Actions for performing AWS tasks as part of your deployment plans.

KB #1029: Integrating LeanKit Kanban with BuildMaster

Last Updated: 9/26/2013

LeanKit Kanban is a hosted service, so your BuildMaster server must have access to the Internet for this extension to work. The LeanKit Kanban extension includes a BuildMaster Issue Tracking Provider that allows you to treat a Kanban board as a BuildMaster application’s issue tracker. If you are unfamiliar with configuring Issue Tracking Providers in BuildMaster, see <a href="http://inedo.com/support/kb/1006/integrating-an-issue-tracker-with-buildmaster">Integrating an Issue Tracker with BuildMaster</a>.

KB #1028: Integrating BuildMaster and Git

Last Updated: 9/26/2013

Because Git is a Distributed Version Control System, BuildMaster requires that you create a centralized repository which will be used for pulling the latest or labeled source code. This centralized repo may optionally pull from a remote repository URL such as GitHub.

KB #1027: Using ProGet with MyGet

Last Updated: 9/26/2013

<a href="http://www.myget.org/">MyGet</a> is  a NuGet as a Service platform that allows users to create hosted NuGet feeds. MyGet, in addition to the standard NuGet feed, gives you another package source where you can publish your libraries and dependencies without putting them on the official NuGet feed.

KB #1026: Upgrade Notes for BuildMaster 3.2

Last Updated: 9/26/2013

BuildMaster 3.2 is a minor release of BuildMaster, and focused on the following changes:

KB #1025: Integrating BuildMaster and Perforce

Last Updated: 9/26/2013

BuildMaster uses the Perforce Command-Line Client (p4, or p4.exe on Windows) for Perforce integration, and therefore the Command-Line Client must be installed on the same server that BuildMaster is installed on, or installed on a server that a BuildMaster agent is installed to. In either case (local or remote server), the setup is the same.

KB #1023: A Comparison Between BuildMaster vs. TeamCity

Last Updated: 9/26/2013

<a href="http://www.jetbrains.com/teamcity/">TeamCity</a> and BuildMaster are different products, the main difference being that TeamCity is a Continuous Integration server (i.e. it will automatically take code from SCM, build it, then put an artifact on an integration server), while BuildMaster can <a href="/buildmaster/features/continuous-integration">perform Continuous Integration</a> related tasks, and additionally set up plans for your builds to be deployed through various environments (development, test, production, etc.) while also:

KB #1022: Integrating BuildMaster and SourceGear Vault

Last Updated: 9/26/2013

SourceGear's Vault is a popular source control repository, especially for teams developing with Microsoft technology. Integrating SourceGear Vault and BuildMaster are pretty straight forward.

KB #1020: Using ProGet with Chocolatey

Last Updated: 9/26/2013

If you haven't heard of <a href="http://chocolatey.org/">Chocolatey</a> before, here's a quick overview from the <a href="https://github.com/chocolatey/chocolatey/wiki">Chocolatey Wiki</a>:

KB #1019: Workaround for Chrome File Uploading Bug

Last Updated: 9/26/2013

In Google Chrome 19, when IIS is configured for Integrated Windows Authentication configuration, uploading a file (such as a Database Change Script) may lead to a rather curious result:

KB #1017: ProGet Installation Guide

Last Updated: 9/26/2013

This guide will provide a step-by-step guide to installing ProGet and provide some detail as to what's happening behind the scenes.

KB #1016: Installing a BuildMaster Agent on Windows Server 2008 R2 Without IIS

Last Updated: 9/26/2013

There are two versions of the BuildMaster Windows Agent:

KB #1012: Registration and Activation of BuildMaster

Last Updated: 9/26/2013

Ever since we started offering BuildMaster as a download (first as a trial, and more recently the free edition), we’ve noticed some confusion in support about our registration mechanism. The most common misunderstanding is that a number of users have confused registration and activation.

KB #1011: Adding a New Remote Server to an Existing BuildMaster Installation

Last Updated: 9/26/2013

Orchestrating remote servers are an integral part of BuildMaster’s automated deployment mechanism. A server becomes recognized or registered with BuildMaster once the agent software has been installed on it, and a reference to the agent’s URL is added from within the BuildMaster software itself.

KB #1005: This Machine Cannot Be Uniquely Identified

Last Updated: 9/26/2013

Once in a blue moon, you might see BuildMaster suddenly stop working and give this fairly unhelpful message.

KB #1004: Release Numbering Schemes

Last Updated: 9/26/2013

The difference between a release and a build isn’t always that obvious, especially in corporate IT and other custom software shops.

KB #1002: Logging In Without Privileges

Last Updated: 9/26/2013

Lately we have been receiving reports of a Security Exception arising when a new user attempts to log-in to BuildMaster:

KB #1001: Backing-up and Restoring BuildMaster

Last Updated: 9/26/2013

As the home for all of your applications’ build and deployment plans – and all of the other application configuration data – BuildMaster should be backed-up frequently. Fortunately, this is relatively easy to do.

KB #1000: Using Source Control to Manage Stored Procedures

Last Updated: 9/26/2013

It goes without saying that source code files belong in source control. Using your production environment as the repository is not only difficult (for compiled applications, at least), but perhaps one of the worst possible practices. Code has to start in source control and move its way up to production.