We do same in our company. I download Proget from here http://inedo.com/proget/versions and the free verion option is available.

Hi Steve, good question. We don't currently have a custom description per each action, but that's going to be in the v5 style plans. You can use the action group description if feasible. We do have a "show full path on hover" coming in 4.8.1 (due later today), but we can probably add in a view as well.

Yes; deployment automation is a core function of BuildMaster. The pricing is specified here, BuildMaster Licensing and Pricing, and we have service partners around the globe that can help determine cost of services (or, you can learn/use BuildMaster yourself).

Yes indeed! BuildMaster has built-in database change script and database connections for running sql scripts in various environments

Just letting you know that we have added a feature to BuildMaster 4.8 that we're calling Ambient Script Variables that should solve this problem. Basically, it allows you do define script variables that BuildMaster will evaluate and assign before running a script. So, in your case you'd just add one called ReleaseNumber that contains the value $ReleaseNumber (the value can evaluate to anything though, and use any variables/functions that are in scope when the script runs). 4.8.0 should be released tomorrow.

For completeness, this specific issue was related to invalid credentials, in this case, the username was being entered with a domain prefix when the SVN server did not require one.

I had the same problem, the packages still showed up after deleting the conector. SOLUTION Restart Proget DETAILS I browsed the database and the packages folder for the offending packages and could not find them. The connector was also deleted from the database. Running feed cleanup also did nothing. In short, I could find no evidence of a problem that would persist after a restart, so I restarted the server Proget ran on and after restart it no longer pulled in packages from the deleted remote. I have proget version: Version 3.7.5 (Build 3)

Which API are you calling, the SOAP or the JSON API? And which method in the API are you trying to call? The value for the API key can be any text, and for the JSON API, would be passed in as: http://buildmaster-server/api/json/Method_Name?API_Key=yourKey&Argument_1=value1&Argument_2=value2 The easiest way to go about your issue is to create a URL-Triggered Build. Note the screenshots are a bit out of date but the information is the same.

It does not, it will require a custom action or script. If you can output the current revision to a file, you can use the "Set Variable From File" action to something like $SvnRevision, then reference that later in your build/deployment plan.

ProGet can host a Bower repo, but a Bower repo is really nothing more than a name/url mapping that points to a Git repo. The packages themselves remain stored in a Git repo. To proxy everything, you'd need to set up a local Git repository and change the ProGet package URL for that package to refer to the local copy.

For the database, that should work fine. If you have packages stored on the local filesystem of the server, they'll have to be migrated over and kept in the same structure, otherwise the feed storage paths would have to be updated. If the database PackagesRootPath is configured to a UNC path or mapped drive, then as long as that path is accessible from the new server you should be good to go.

Though the error message isn't very clear, that error means you are not authorized to view the particular server selected for the SCM provider or the action. If you have changed privileges recently, try invalidating the privilege cache on the Admin > Privileges page.

what a pain in the butt. many of the urls are bound to the page using knockout. These are my rewrite rules I've configured for IIS Rewrite Module with good luck so far. <rewrite> <rules> <rule name="Reverse Proxy to Proget" stopProcessing="true"> <match url="^proget(.*)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget Resources" stopProcessing="true"> <match url="^Resources(.*)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/Resources{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget Alerts" stopProcessing="true"> <match url="^alerts$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/alerts" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget nuget feed" stopProcessing="true"> <match url="^nuget(.+)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/nuget/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget feeds" stopProcessing="true"> <match url="^feeds(.+)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/feeds/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget package" stopProcessing="true"> <match url="^package/(.+)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/package/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget packages" stopProcessing="true"> <match url="^packages/(.+)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/packages/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget administration" stopProcessing="true"> <match url="^administration(.+)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/administration/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget 0x44" stopProcessing="true"> <match url="^0x44(.+)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/0x44/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> </rules> <outboundRules> <rule name="ProGet outbound rewrite" stopProcessing="true"> <match filterByTags="A, Form, Img, Link, Script" pattern="^/(.*)$" /> <action type="Rewrite" value="http://man09120fs/proget/{R:1}" /> </rule> <!-- 302 Redirects (for the login page, e.g.) need to be rewritten. --> <rule name="ProGet Redirect" preCondition="IsRedirect"> <match serverVariable="RESPONSE_LOCATION" pattern="/(.*)" /> <action type="Rewrite" value="http://man09120fs/proget/{R:1}" /> </rule> <preConditions> <preCondition name="IsHTML"> <add input="{RESPONSE_CONTENT_TYPE}" pattern="^text/html" /> </preCondition> <preCondition name="IsRedirect"> <add input="{RESPONSE_STATUS}" pattern="302" /> </preCondition> </preConditions> </outboundRules> </rewrite>

Hi Tod, sorry my falled your workaround is working thx

I'm not sure what you mean, are you saying all the servers on the Server Overview page are shown as "checking"? The best bet is to restart the BuildMaster service and web application if it's "stuck", but otherwise, upgrading BuildMaster should also resolve that since it no longer pulls the status directly from the DB as of v4.1

Thank you for the report - this will be resolved in v4.7.5

Here are the commands/switches that would be run ... https://github.com/Inedo/bmx-nuget/blob/master/CreatePackage.cs#L83]

Please see ProGet Features By Edition for more information.

Hm, anything is possible, but I have seen a custom API endpoint causing problems, and a one without privileges set for an API key. Perhaps you can explore the code a little, to see what might be an issue? It's basically just simple HTTP calls to various URLS using Basic HTTP authentication: https://github.com/Inedo/bmx-jenkins/blob/master/JenkinsClient.cs

See: http://inedo.com/support/tutorials/performing-a-deployment-rollback-with-buildmaster