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 25 of 99 (20 questions out of 1979)
1
replies

Hi,
I recently upgraded to Proget 4.4.1.
Earlier I could see the prerelease(beta) packages also on the webpage on ticking a checkbox. That seems to have gone now.
How do I enable the option to see the prerelease packages too?

Regards
PK

Product: ProGet
Version: 4.4.1

1
replies

Hi, we recently upgraded from 3.x to 4.4.1 to evaluate for a full license. We have noticed that the 'prerelease' checkbox has been removed from package searches. If the package doesn't have a release package yet, we cant find that package via search now.

If it does have a release, we can find it from the show all versions tab on the search results but we dont see that on a first time RC package

Cheers,
pete

Product: ProGet
Version: 4.4.2

1
replies

Is there a summary page in the BuildMaster web interface that displays upcoming scheduled releases? For example, if I wanted to know all the scheduled jobs that will run tonight, where could I see this information?

Product: BuildMaster
Version: 5.3.5

2
replies

Is it possible to have both a NPM feed and a Nuget feed enabled on the same server. We are using LDAP Integrated authentication for Nuget and that seems to be blocking our ability to publish to NPM.

Product: ProGet
Version: 4.4.2

1
replies

ProGet 4.4.1 displays the wrong package source URL on the detail screen of chocolatey packages.

The source URL for my chocolatey feed is http://<servername>/nuget/<reponame>, but ProGet displays http://<servername>/chocolatey/<reponame>. This causes issues for those who are copy/pasting the install command.

How can this be rectified?

Product: ProGet
Version: 4.4.1

1
replies

hi,

I have an issue with the github provider. I have several repositories in my personal github account. When I test the provider the connection, it connects ok but pulls down the first repository it finds.

When I try and get a specific repository, it always throws an error (invalid repository)

My Get-Latest-Source script is as follows:

Get-Latest-Source
(
    Provider: GitHub,
    SourcePath: first-place-processing.git
);

MSBuild::Build-Project fpp.sln
(
    Configuration: Release,
    Platform: x86,
    To: $src
);

Product: BuildMaster
Version: 5.2.3

1
replies

We are busy moving from an old server to two new servers, in two data centers. We have a single Enterprise license and purchasing an additional license for the second machine.
How do I transfer the existing license to the new server and can I temporarily have the license active on both servers for a week?

Product: ProGet
Version: 4.4.2

1
replies

I would like to use some of the functions under the Windows SDK that pre-5 BuildMaster did have. I know BM doesn't have these actions directly being used but I was wondering if there is someway to call them?
For example I need to use the Install to GAC function but now in 5.x I cannot seem to call it.

Thanks,
Jon

Product: BuildMaster
Version: 5.4.2

1
replies

I have a Perform-ManualOperation in stage 1. And there's an approval gate at stage 2.

If manual operation is cancelled, stage 1 failed, the approval for stage 2 should not be activated and no email notification should be sent.

However currently even stage 1 fails, approval notification for stage 2 is still being sent out. This behavior confuses me because it's asking to approve something that is already failed.

Product: BuildMaster
Version: 5.4.2

1
replies

When an error occurs, how do I get this specific error message? Does it stores this information somewhere? What I need is a try catch block that will send out an e-mail with the specific error message.

Also, how do I stop the next action from being executed when the current action within a block fails?

Thanks.

Product: BuildMaster
Version: 5.4.2

3
replies

I am trying to publish a PowerShell module to the new PowerShell feed. I keep receiving the below manifest error. The test-mod has a manifest file and Ive Run New-ModuleManifest.
I also downloaded a module from the PowerShell Gallery and tried to post that and i received the same error.

<div markdown="1" style="background-color:lightgray;color:red" > Publish-Module : Module 'Test-Mod' cannot be published because it does not have a module manifest file. Run New-ModuleManifest -Path <PathName> to create a module manifest with metadata before publishing. </div>

Any suggestions or help would be so awesome, this is driving me bananas!

Publish-Module -Repository MyCompFeed -Path Test-Mod -NuGetApiKey api:key -v -Confirm:$false

ProGet Version 4.3.1(Build 5)
Get-PackageSource MyCompFeed PSModule True True False http://nuget.MyCompFeed
Get-PackageProvider PSModule 1.0.0.0
PackageManagement is at version 1.0.0.0
NuGet Version: 3.4.4.1321
$PSVersionTable
PSVersion 5.0.10514.6
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.42000
BuildVersion 10.0.10514.6
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion 2.3

Product: BuildMaster
Version: 5.4.2

3
replies

Is there a way to programatically flag a package version to not be deleted by the cleanup policy?

Product: ProGet
Version: 3.8.6

3
replies

Hi

We have issue with NPM publish new package.
When publishing from npm (npm publish) returns 500 error, but using upload file from site package added.

Product: ProGet
Version: 4.4.0

1
replies

When I Edit the "View Application" task, the checkbox for "Configure BuildMaster" under Administration is checked. Is this a bug? Why would the View Application task grant the ability to configure buildmaster?

Product: BuildMaster
Version: 5.3.5

1
replies

Hi

We have problem with some npm packages like: @angular/core
Looks like connector of ProGet npm do not download (indexing) scoped packages

Can you please help?

Product: ProGet
Version: 4.4.0

1
replies

Hi, we have an old server with some nuget packages on them. We want to move those packages to our new proget server. We can easily add the old server as a feed connector to the new feed on the new server but the old server is horribly slow.

I know that feed connectors will cache the packages but is there a way to tell it to permanently store them so that after they are all moved we can disconnect the feed connector?

Product: ProGet
Version: 4.4.1

1
replies

There is a new feed replication behavior that popped up in version 4.4.1.

Server A serves as a feed replication point, and Server B replicates feeds from server A. In a previous version of ProGet, the replication URL for a certain feed used to be:

Replication URL: http://tpnuget/api/feed-replication/Default

After I loaded 4.4.1, the replication URL shows instead as:

Replication URL: http://tpnugetapi/feed-replication/Default

When I use this replication URL in server B, server B starts showing the error:

4:35 PM Unhandled exception: The remote name could not be resolved: 'tpnugetapi'

There is no server tpnugetapi, the server is tpnuget, and it appears that a \ separator was removed from the display result of the replication feed URL.

If I go into server B configuration and manually insert the \ back in the URL, so the replication feed once again shows:
Replication URL: http://tpnuget/api/feed-replication/Default
The errors go away and things start working again. The Server A replication URL is still display wrong, however.

Product: ProGet
Version: 4.4.1

4
replies

I have current nuget.server that I would like to migrate from to proget.
Currently I see Proget appending the name of the feed to every feed I create.
For example standard: http://localhost/nuget/Default
I need to have http://localhost/nuget to match the default feed.
This is needed to migrate smoothly betweeen the systems.
Is it possible?

Product: ProGet
Version: 4.4.1

1
replies

Hi, I've just noticed that the dependency list of a nuget package isn't shown correctly when the .nuspec contains multiple groups for different targetFramework.

You can compare the official nuget feed

Image Text

vs what is shown in a Proget Nuget feed:

Image Text

Are you planning on changing the dependencies view to acommodate for multi target packages?

Thanks!

Product: ProGet
Version: 4.4.1

1
replies

I have a network with both linux and windows boxes. I have several monitors that I deploy to each of these systems. I am using otter to check that the monitors are configured correctly.

I am currently monitoring a splunkforwarder and a nagios agent. I have 1 role that just handles splunk on windows and 1 that handles nagios on windows. I was going to make one to handle splunk on linux and 1 to handle nagios on linux. These would make sure the system points to the variables in the Environment, and each machine would have 2 roles.

Is this considered a best practice, or would it be better to have one role for splunk that handles both linux and windows... or better to bundle both agent into a single role?

I have been assuming that the smaller roles would be easier to maintain and debug as well as easier to add a new role rather than incrementally modify an existing larger role.

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 25 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