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 11 of 101 (20 questions out of 2014)
3
replies

Hi,

I am planning to move a Proget Server version 4.50 build 25 to a new server and SQL server.
Unfortunately the SQL server version will be changing from SQL 2014 Express to SQL 2012 Enterprise.
I am aware that SQL databases cannot be restored to earlier versions using backup and restore.
Do you know of any other data export \ import methods that could help with the migration?

Thanks
Jason

Product: ProGet
Version: 4.5.0

1
replies

Hi Inedo,

I'm getting an exception when trying to download and install a universal package with upack.exe

I still receive the package, so it is working as intended, but the error still shows up in the error log

Message:
An error occurred processing a GET request to http://server:port/upack/feed/download/group.name/Package-Name?latest: Object reference not set to an instance of an object.

Stack:
System.NullReferenceException: Object reference not set to an instance of an object.
at Inedo.ProGet.WebApplication.SimpleHandlers.PackageDeploymentData.FromContext(HttpContext context)
at Inedo.ProGet.WebApplication.FeedEndpoints.Universal.UniversalRepositoryHandler.<RecordPackageDownloadAsync>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.WebApplication.FeedEndpoints.Universal.UniversalRepositoryHandler.<ProcessDownloadRequestAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler.FeedRequestHandler.<ProcessRequestAsync>d__8.MoveNext()

Product: ProGet
Version: 4.7.9

1
replies

I'm wondering if any documentation can be provided to explain Buildmaster deployables, especially in the context of managing multiple build artifacts and empowering users to deploy different artifacts according to selected build deployables (is this possible to configure?).

I don't note any documentation germane to deployables on the Inedo website, but I'm wondering how to correctly interact with deployables via a build plan.

Product: BuildMaster
Version: 5.6.11

3
replies

We are having issues with authentication with Active Directory Domain Forest. When we add users it shows the users FQDN but if windows authentication is enabled it logs us in with shortname of the domain for example domain name is DomainA.local it will add users as user1@domaina.local but log us in as user1@domaina and state we have no privileges. I have to manually add user1@domaina and then it works but we have the same issues with groups. If we add a group it detects users at FQDN vs shortname.

Product: ProGet
Version: 4.7.8

1
replies

Hello,

Is it possible to skip the "Create Package" option when creating a release? We have a scenario where we are using the Copy-Files function in a very simple plan and use release variables to set the parameters to the Copy-Files function. The "Create Package" step in the release is not needed and it adds an extra step in the deployment. Is there a way to automate the "Create Package" step at the same time "Create Release" is done or is there a way to skip the "Create Package" requirement.

Thanks for your help

Product: BuildMaster
Version: 5.6.8

1
replies

Hi please at TLS 1.2 support to ProGet Feeds and Connectors.

Image Text

Product: ProGet
Version: 4.7.9

1
replies

So I want to set up issue tracking using YouTrack in BuildMaster. I installed the YouTrack extension (v5.1.1). I then go to create an issue source, but I get a dialog that says there are no issue sources in any currently installed extensions. I can create a legacy issue tracking provider, but I can't figure out how to use it. When I try to configure an external source for my application, it says there are no issue sources in any currently installed extensions. I tried following the instructions for using YouTrack in BuildMaster, but they break down in Step 1 because there is no resource credential of type "YouTrack".

How do I configure BuildMaster to use YouTrack as an issue source?

Product: BuildMaster
Version: 5.6.11

3
replies

Are there any roadmap details surrounding Connectors for Docker and availability?

Product: ProGet
Version: 4.7.10

1
replies

After restricting all operations to the Admins only, I don't seem to be able to protect the Connectors page from Anon client browsers

Product: ProGet
Version: 4.7.9

4
replies

Hi,

After starting to target netstandard 1.4 and using a new build script(Cake), i no longer get symbols in ProGet (meaning no "Symbols and source files are available. [view]", and no pdb in downloaded package).

I have verified that the the package i pushed contains symbol information. nuget creates two packages: One with no pdb, and one with the same content + pdf (that it calls *.symbols.nupkg). I have tried pushing both and only pushing the .symbols.nupkg one.

I am using msbuild /t:pack (because i need to pass msbuild properties) and i am passing IncludeSymbols=true and IncludeSource=true.

When pushing i use Cake's NuGetPush with Source and ApiKey set. I also tried setting SymbolSource and SymbolApiKey. But so far no luck.

I would appreciate any pointers...

Product: ProGet
Version: 4.7.6

2
replies

Hello--

I'm trying to solve an issue with deploying to multiple servers in a server role. The issue is represented under the following circumstances:

Build Plan (pseudo-code):
1) On Server: Buildmaster, execute command, git clone $repo
2) Build Artifact
3) Deploy Artifact

Deploy to: web12 (web1, web2 servers);

What ends up happening is that Buildmaster is able to successfully execute the above plan from start to finish for web1, but upon attempting the git clone again for web2, the job fails since git clone requires an empty directory.

This issue emerges since build plans linked in pipelines are implicitly inside of a: for server in $pipeline_stage block, and the git clone is then executed twice in the same temporary directory.

I'm wondering:

  1. can buildmaster use a different temporary directory for each server?
    or 2) can buildmaster clear the temporary directory for each successful server build
    or 3) can I ask buildmaster to execute a build action outside of the server block loop

Any insight into this issue would be appreciated!

Product: BuildMaster
Version: 5.6.11

3
replies

Seeing this: http://inedo.com/proget/roadmap

And seeing the python support, we desperately need this functionality. We are on the precipice of purchasing and as part of this purchase, we are consolidating from Nexus 3 / Synopia to ProGet.

However we have a large project that needs Python packaging.

How soon is this going to be developed and released?
Is there a beta program we could partake in to get it early?

Please let us know!
Thanks - World Wide Technology

Product: ProGet
Version: 4.7.10

2
replies

I get this error message when i set the feed to S3, how do I resolve it?

Category: DropPathMonitor
Message: Error installing package: Assembly Amazon was not found. The extension may be out of date, have been deleted, or could not be loaded.

Product: ProGet
Version: 4.7.10

1
replies

I see that PyPI feed integration is on the roadmap, do you have any indication of when this may occur?

Product: ProGet
Version: 4.7.10

0
replies

Is there any way I can check the users dependent or total number of users connected to my ProGet server.
-I am using LDAP Configuration
-Windows 2008R2
-Having external database instance.

Product: ProGet
Version: 4.7.1

1
replies

I need to execute a power shell script that takes 2 parameters, the current directory and then the configuration name (Debug, Release). I am guessing that I can pass in $CurrentDirectory in some fashion. Here is how this script is executed as a pre-build step in Visual Studio:

powershell -file "$(ProjectDir)Resources/tools/PreBuild.ps1" -projectDir "$(ProjectDir) " -buildType $(ConfigurationName)

Product: BuildMaster
Version: 4.6.1

1
replies

I installed ProGet on a Windows 2012 R2 server. I selected SQL Express to be installed by the installer.
Even though IIS was installed and running, during the installation, I could not select IIS and could only select the ProGet web server.
Everything seemed to install fine. Once I opened up the firewall for port 81 traffic, the developer (and me) were able to get to the ProGet server (on port 81)
I shut the machine down (it is a virtual machine) to snap shot it after install. When i rebooted, the ProGet Service starts Automatically, but the ProGet Web Server does not. It is configured to Automatically start. If I start if via the Services console, it runs and is fine. If I change the service in any way, telling it to restart if it stops, or change it to start Automatic (Delayed Start) this causes the ProGet Service to not start on reboot as well.
Thoughts?

Product: ProGet
Version: 4.7.9

1
replies

Using windows "Sign Binary" (signtool) what value from an installed certificate should be placed in the "SubjectName" value to find the certificate? I've tried "Friendly Name" and "Subject Key Identifier" which I get this error:
SignTool Error: No certificates were found that met all the given criteria.
Signtool.exe returned exit code 1

Product: BuildMaster
Version: 5.6.11

1
replies

I am running the latest CE version of ProGet on Debian linux.

I am in a tough spot. I've setup ProGet on a server as part of our DevOps tool chain, but I can't use NuGet Push to push packages up to the server. Additionally, ProGet isn't checking the specified drop path for packages that are located there.

I have gone through as much of the documentation as I can, but I can't find a fix to this problem.

When I run a nuget push command I either get:

  1. Response status code does not indicate success: 403 (Forbidden)
  2. Response status code does not indicate success: 400 (Bad Request)

When I increase the verbosity of the nuget push command I get an error chain that shows that ProGet is throwing errors. I have included the error chain below for reference.

I have additionally gone through and adjusted settings for the package drop folder so that packages dropped in the folder will overwrite preexisting packages. I also increased the checking frequency to 30 seconds. Even with these changes, packages are not added from the drop path. ProGet is installed as root, so I have gone through to make sure that all folders have the correct permission.

I will have a viable solution with ProGet if packages can be added via nuget push or from drop path. Until then, ProGet isn't a viable solution for us.

Your help is greatly appreciated.

-------- Attempted NuGet Commands ----------

C:\nuget.exe push .\Company.Feature.Database.1.0.0.nupkg user:user -Verbosity detailed -NonInteractive -Source http://proget-server/nuget/feed-name

C:\nuget.exe push .\Company.Feature.Database.1.0.0.nupkg -Verbosity detailed -NonInteractive -ApiKey user:user -Source http://proget-server/nuget/feed-name

Attempted with Key Specified for Feed

C:\nuget.exe push .\Company.Feature.Database.1.0.0.nupkg -Verbosity detailed -NonInteractive -ApiKey A -Source http://proget-server/nuget/feed-name

C:\nuget.exe push .\Company.Feature.Database.1.0.0.nupkg A -Verbosity detailed -NonInteractive -Source http://proget-server/nuget/feed-name

-------- Error Chain (Bad Request) ----------

System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: Response status cod
e does not indicate success: 400 (Bad Request).
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at NuGet.Protocol.Core.Types.PackageUpdateResource.<>c.<PushPackageToServer>b__19_1(HttpResponseMessage response)
at NuGet.Protocol.HttpSource.<ProcessResponseAsync>d__141.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackageToServer>d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackageCore>d__13.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackage>d__12.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<Push>d__8.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Commands.PushRunner.<Run>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.CommandLine.PushCommand.<ExecuteCommandAsync>d__28.MoveNext() --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at NuGet.CommandLine.Command.Execute() at NuGet.CommandLine.Program.MainCore(String workingDirectory, String[] args) ---> (Inner Exception #0) System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (B ad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at NuGet.Protocol.Core.Types.PackageUpdateResource.<>c.<PushPackageToServer>b__19_1(HttpResponseMessage response) at NuGet.Protocol.HttpSource.<ProcessResponseAsync>d__141.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackageToServer>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackageCore>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackage>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.Protocol.Core.Types.PackageUpdateResource.<Push>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.Commands.PushRunner.<Run>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.CommandLine.PushCommand.<ExecuteCommandAsync>d__28.MoveNext()<---

-------- Error Chain (Forbidden) ----------

System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: Response status cod
e
does not indicate success: 403 (Forbidden).
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at NuGet.Protocol.Core.Types.PackageUpdateResource.<>c.<PushPackageToServer>b__19_1(HttpResponseMessage response)
at NuGet.Protocol.HttpSource.<ProcessResponseAsync>d__141.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackageToServer>d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackageCore>d__13.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackage>d__12.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<Push>d__8.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Commands.PushRunner.<Run>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.CommandLine.PushCommand.<ExecuteCommandAsync>d__28.MoveNext() --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at NuGet.CommandLine.Command.Execute() at NuGet.CommandLine.Program.MainCore(String workingDirectory, String[] args) ---> (Inner Exception #0) System.Net.Http.HttpRequestException: Response status code does not indicate success: 403 (F orbidden). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at NuGet.Protocol.Core.Types.PackageUpdateResource.<>c.<PushPackageToServer>b__19_1(HttpResponseMessage response) at NuGet.Protocol.HttpSource.<ProcessResponseAsync>d__141.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackageToServer>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackageCore>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackage>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.Protocol.Core.Types.PackageUpdateResource.<Push>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.Commands.PushRunner.<Run>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.CommandLine.PushCommand.<ExecuteCommandAsync>d__28.MoveNext()<---

Product: ProGet
Version: 4.7.9

1
replies

We are trying to deploy stored procedures through Buildmaster's SQL Change Script feature. The beginning of all of our stored procedures use a line like "Use [OurDatabaseName]". Since these database names vary based on the deployment environment (i.e., integration, testing, production), is there a way to use a Buildmaster variable in the SQL script so that we do not have to manually change the text of the Change Script depending on the environment to which we are trying to deploy?

Feel free to just point me to documentation on this if you have any, I couldn't find it.

Product: BuildMaster
Version: 5.6.4

Ask A Question
Page: 1 2 3 4 5 6 7 8 9 11 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 52 53 54 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