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

It's fairly rare to have 2 config files with the same name assigned to the same deployable, and when they are under 2 different deployables, an action within an action group in the context of a deployable will only show the single config file in the dropdown.

Thanks. Removing \SQLEXPRESS fixed it. -Michael

Upgraded to 3.7.4 and the problem is fixed. Thanks.

Thanks Dean, I modded the regex inline to get around the validation issue. Thanks for getting back to us on this.

Yes, most definitely. See KB#1072 - ProGet vs. NuGet.Server

It's not possible to add a new feed type via the SDK, but it's for sure on our roadmap.

We'll fix this in ProGet 3.7.4. For now, you can mark the feed as inactive to disable it. If you need to delete it, I can send you a patch to fix your installation.

Maven connectors need to be indexed before they can be used from ProGet. If you go to the Admin->Scheduled Tasks page, you should see an entry for a MavenConnectorIndexing job, and you should be able to see a log of the last several attempts. Did it appear to complete successfully? Also, you may want to try actually performing a search for the Maven artifacts. When browsing, we only display local artifacts, but connectors are displayed when you search as well.