Support Q & A Home

Ask A Question

Anyone can ask or answer a question here, but our support engineers actively monitor your questions; we typically answer within a day or two.

Filter
Viewing Page 53 of 103 (20 questions out of 2054)
1
replies

Hi,

I'd like to trigger a test runner (SoapUI REST API testing) after BM completes a deployment. I can set it up where BM start the testrunner by running a command in powershell script. Once the testrunner finishes and generates JUnit-Style reports, is it possible to have BM to interpret the results and send out notifications? What is the best practice solution for this scenario? Sales team at SoapUI suggested we can use JUnit extension for this purpose. I installed it in our BM but not sure what to do with it next. Please advise. Thanks,
Alex

Product: BuildMaster
Version: 4.8.3

1
replies

Can privileges also be assigned per package (ID) or just per NuGet feed?

Product: ProGet
Version: 3.8.1

1
replies

I have created new feed and added a connector (which is feed from another Proget resource). I do not see a download all package (which pulls packages to proget) option next to connector.

This option is available in 3.1.7 (Build3)

Product: BuildMaster
Version: 3.5.8

3
replies

Given:

  • A package containing a containing dll's and pdb's targeting both net35 and net40. The package includes source files as well.
  • A Feed i ProGet that has the Symbols Server setting defined as: "Enabled, and strip symbol files from package downloads"

The problem:
When the package is pushed to a feed, one of the pdb files are NOT being indexed (and is therefore not available on the symbols server).

Please provide any hints to what the issue might be.

Thanks!

Product: ProGet
Version: 3.8.0

3
replies

Hi,

We setup a Proget environment and secured this with LDAP authentication. The downside is that for retrieving any package, we need to login (including our build server).

Is it possible not to secure the retrieval of packages? Actually we only want to login when we maintain packages.

thanks,
Jeroen

Product: ProGet
Version: 3.7.6

2
replies

I did the following in my effort to evaluate ProGet:

  • created a fresh VM of Windows Server 2012
  • installed IIS
  • installed the latest ProGet (as of 9/9/2015)

I used the SQL Server Express option and chose port 80 (though I suspected this would conflict with the existing, default IIS site). Otherwise I left the default install settings.

Everything seemed to install successfully. Upon launching, the browser went to localhost/ and gave me the default IIS page (understandably since it was already on port 80). I went into IIS configuration and saw the new ProGet site and saw that it was stopped (again, no surprise there). I stopped the Default Web Site, and started the ProGet site. Refresh browser.

Now I'm getting a 500.19 server error:

Config Error: This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".

Config File:
\?\C:\Program Files\ProGet\WebApp\web.config

Config Source:

33:     </security>
34:     <handlers>
35:       <remove name="rules-ISAPI-4.0_64bit" />

Line 34 is the highlighted line.

I have extensive experience with .NET and IIS application configuration and this one is throwing me off a bit. I did attempt a couple things:

  • created a default site sub directory application for ProGet (my ultimate goal)
  • switched the ProGet application pool to Integrated pipeline from Classic
  • commented out the offending configuration section (this resulted in error 403.14: can't list directory contents)

None of these had any effects. I can't imagine that my choice of port 80 or the default of 81 would cause any problems beyond those I expected and ultimately got, but fixed. So I'm now at a loss as to why this isn't working.

Product: ProGet
Version: 3.8.0

1
replies

Hi!

We have an internal ProGet server and want to enable our customers to access certain NuGet feeds. However, for security reasons, this server is not accessible from outside.

I thought about the following options:

  1. Move the server to the DMZ
  2. Setup a second server in the DMZ and synchronize only certain feeds.

I think moving the whole server to the DMZ, just to provide access for a few feeds is not worth the additional security risks.

Regarding the synchronization, I am aware of the connector feature, which would allow me to connect to the internal NuGet server. However, our IT policy does not allow access from the DMZ to the internal network.

Is there some way to push/synchronize certain feeds from the internal ProGet to the external ProGet server?
It seems like the MyGet synchronization is what I want. Does this only work for MyGet?

Best regards,

Martin

Product: ProGet
Version: 3.8.0

3
replies

Hi - we have a Proget server configured with a Maven connector that receives 403 responses when attempting to get a repository listing at https://repo1.maven.org/maven2.

This 403 response only ever occurs when the request originates from Proget itself; the same URL & listing works when viewed via a browser on the same machine that the Proget service is running on.

Just wondering if this is something that has been encountered before, and if it's a known issue, how do we work around it?

Product: ProGet
Version: 3.5.8

1
replies

I was looking at creating the "Configuration Files" for the applications I'm importing into BuildMaster and using the directions on the Getting a Simple Application Into BuildMaster article, I see the comment:

From this window we could also load the files from source control, load from a server registered in BuildMaster, or upload a file from our machine.

This Window it is referring to is the Edit Configuration window where you can paste in the text (in this example a web.config file. I do not see the options to load from source control, from a server, or upload a file.

Am I missing something?

Product: BuildMaster
Version: 4.8.3

3
replies

I have looked at the BeforeDownloadPackageAdapterBase and Users_ValidateLogin classes of the SDK but couldn't find a way to implement the following extension:
Check the provided username and password when there's an attempt to download a package and return an HTTP error or redirect to an error page.

Or will it be easier to implement a custom ASP.NET HttpModule and configure that in the ProGet web application's web.config? In that case I need to know when someone attempts to download any package and check the feed name, username and password.

Product: ProGet
Version: 3.6.1

4
replies

I am currently using the Enterprise trial and from the looks of it, we are going to purchase this as it allows all the functionality we need. There were some sticky points, and this question is the prime: We followed the online excercise for generating a TFS build and, unlike the article, it was not as automated as I expected. This was no problem; I simply created the steps for:

  • Create TFS Build
  • Create Artifact from TFS Build Output
  • Stop Application Pool
  • Deploy <Build-name> Artifact
  • Start Application Pool

This works, and is deployed to the Dev IIS because the Dev IIS was configured to follow the conventions of the Build Artifact and deploy location /_PublishedWebsites/ - In TFS we have a Team Project which has multiple solutions under it, and there is a builder for each of the solutions independently.

Now, normally I can manage the deployment output on my own through TFS in various manners (CopyDirectory step, modifying the build process itself, etc.) but I don't want to do this, I want to leverage BuildMaster to do this, but I was confused as to the best practice for this. On the web application Server we have:

(generalized)
\WebRoot\<projectgroup>\<websolution>\

For each project, so the _PublishedWebsites is usually avoided by a manual or build step to copy the subdirectory to the Projectgroup folder. What is the most automated (least input) way to create a deployment plan step for this. So far it looks like "Transfer/Synchronize Files" is the only solution. So from a simplified view:

  • Stop Application Pool
  • Transfer/Synchronize Files
  • Deploy Configuration File
  • Start Application Pool

Is this the best way? If so, are there variables that can be used to ease the copy and prevent continuous type-itis?

Product: BuildMaster
Version: 4.8.3

8
replies

Hi,

How can I list all the packages, versions, description and license URL's from a feed - but only for the packages that's are cached via proget and not all those in the connectors..

Ideally a CSV type list so can view in excel.

Many Thanks

Gary

Product: ProGet
Version: 3.8.0

1
replies

Is there a way to reset or restore password in BuildMaster?
I just get new clean install, enter username and password that I use during installation and get error - invalid credentials.

Product: BuildMaster
Version: 4.8.3

1
replies

We have a really old Proget instance in production. I want to stand up 3.8. What happens if I activate the old license key on the new instance?

Product: ProGet
Version: 3.8.0

5
replies

In older versions of ProGet, Windows Authentication just worked when LDAP was enabled. Now, Windows Authentication does not work. Forms works just fine, but not Windows Auth.

Product: ProGet
Version: 3.8.0

3
replies

Every time I attempt to login with Multiple AD auth, I get this error and am unable to actually get AD auth to work: An error occurred in the web application: Exception of type 'System.Web.HttpUnhandledException' was thrown.

Details:

URL: http://mriczelkeapt001/administration/security/change-directory?directoryId=3
Referrer: http://mriczelkeapt001/administration/security/change-directory?directoryId=3
User: Admin
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
Stack trace: at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

If I try LDAP, I get this error: An error occurred in the web application: The time limit for this request was exceeded.

Details:

URL: http://mriczelkeapt001/0x44/ProGet.WebApplication/Inedo.ProGet.WebApplication.Controls.PrincipalPicker/FindPrincipals?directoryId=2&filter=a&principalTypes=3&_=1441724871006
Referrer: http://mriczelkeapt001/administration/security/privileges/add?directoryId=2
User: Admin
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
Stack trace: at System.DirectoryServices.SearchResultCollection.ResultsEnumerator.MoveNext()
at Inedo.ProGet.WebApplication.Security.UserDirectory.LdapDirectory.FindUsers(String searchTerm)
at Inedo.ProGet.WebApplication.Security.UserDirectory.LdapDirectoryBase.FindPrincipals(String searchTerm)
at Inedo.ProGet.WebApplication.Controls.PrincipalPicker.FindPrincipals(Int32 directoryId, String filter, Int32 principalTypes)

Product: ProGet
Version: 3.8.0

4
replies

We had a working feed when using anonymous access, however we unable to make it authenticated. Proget (in the 'configuring npm' info) gives us these instructions:

  1. npm config set registry http://proget.crosspoint.nl/npm/accesspoint
  2. npm config set always-auth true
  3. npm adduser

but the output is a 404:

root@e6957740c653:/home# npm adduser --verbose
npm info it worked if it ends with ok
npm verb cli [ 'node', '/usr/bin/npm', 'adduser', '--verbose' ]
npm info using npm@2.14.2
npm info using node@v0.12.7
npm verb node symlink /usr/bin/node
Username: npm
Password:
Email: (this IS public) npm@crosspoint.nl
npm verb adduser before first PUT { _id: 'org.couchdb.user:npm',
npm verb adduser   name: 'npm',
npm verb adduser   password: 'XXXXX',
npm verb adduser   email: 'npm@crosspoint.nl',
npm verb adduser   type: 'user',
npm verb adduser   roles: [],
npm verb adduser   date: '2015-09-08T11:47:07.637Z' }
npm verb request uri http://proget.crosspoint.nl/npm/accesspoint/-/user/org.couchdb.user:npm
npm verb request new user, so can't send auth
npm info attempt registry request try #1 at 11:47:07
npm verb request id 24dce33e8ec5eb05
npm http request PUT http://proget.crosspoint.nl/npm/accesspoint/-/user/org.couchdb.user:npm
npm http 404 http://proget.crosspoint.nl/npm/accesspoint/-/user/org.couchdb.user:npm

(BTW: The user does exist and is created with the web interface so explained on this page: http://inedo.com/support/kb/1087/introducing-npm-support-for-proget

After searching on this page, I've allready seen this:

/-/user/org.couchdb.user[...]

or

/npm/[FEED]/-/user/org.couchdb.user[...]

and we get an response on the first one url, NOT the second. And thats the one npm is going right now.

The response on the first is: {
error: "MethodNotAllowed",
reason: "Only PUT is currently supported at this URL."
}, but it is expecting something on that address

Versions:
npm -v: 2.14.2
node -v: 0.12.7
proget: Version 3.8.0 (Build 20

Proget isn't behind some proxy and when using Fidder we don't see authentication headers send at all. What might be going wrong here ?

Product: ProGet
Version: 3.8.0

1
replies

we would like to keep the existing configuration and can manually delete old entries using the script given here:

link text

please can you advise if there is a tool or the appropriate method.

regards,

samuel

Product: BuildMaster
Version: 4.8.2

6
replies

I created a package with sources as described here: http://blog.davidebbo.com/2011/04/easy-way-to-publish-nuget-packages-with.html

If I push the symbol package to NuGet.org and SymbolServer.org as described in the post, Visual Studio 2015 Pro correctly downloads the PDB and the source to its symbol cache. However, when I push the same package to ProGet, I only get the PDB in the cache. No source. I check the NuGet package I'm uploading and the source is in there.

I have verified that neither the PDB as created during build or downloaded from ProGet contains a SRCSRV stream using pdbstr.exe. The PDB pulled from SymbolServer.org does contain this stream. So it seems that ProGet is not indexing the source in my NuGet package and updating the PDB. I do not have any errors showing in ProGet, indexing or otherwise.

What am I missing?

Product: ProGet
Version: 3.8.0

7
replies

Good afternoon,

Our team is having an issue with source code being seemingly unavailable for an installed package from our ProGet server (stepping into the code is not functioning). We have found that the symbol (pdb) files downloaded from ProGet do have indexed source files. However the target path is Http (example: http://{progetserver}/source-files/debug/...). We are going through an F5 which routes HTTPS traffic to HTTP. The latter is inaccessible directly. So, the URLS as they are do not work.

Is there some setting we can change so the paths in the symbol files to source are using HTTPS?

Product: ProGet
Version: 3.7.6

Ask A Question
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 53 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103