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 8 of 105 (20 questions out of 2087)
1
replies

I tried to push a nuget that uses SemVer 2.0.0

nuget push Services.0.2.0-pre.1.nupkg

ProGet rejects this (500):
An error occurred processing a PUT request to http://dev1:81/nuget/shared/: Invalid version number.

Is SemVer 2.0.0 supported?

Product: ProGet
Version: 4.7.13

5
replies

Hi,

I am working upon Artifactory extension Promote Build operation. When I try to run the concerned application, I get the below error:
"ERROR: 404 Cannot find target repository by the key '<Some target repository name>'."

I tried with using "" before/after the repository name thinking that it might be asking for the path, but nothing was of any help. Please help me get through this error.

Product: BuildMaster
Version: 5.7.2

2
replies

Hi
I want to update my existing ProGet servers from 3.8.0 Basic to 4.7.13 Enterprise. Is it a straight upgrade to change to a different edition?

Thanks,
Joel

Product: ProGet
Version: 4.7.13

3
replies

Is NuGet v3 supported now? Some packages are requiring NuGet v3 to restore, e.g.: Newtonsonft v10, aka, the most used nuget package in .NET ecosystem.

This is a dealbreaker for builds running on ProGet.

Product: ProGet
Version: 4.7.13

3
replies

Hi,

We have been trying to implement docker image publish to our ProGet installation but the process fails with the following error:

error parsing HTTP 400 response body: invalid character 'B' looking for beginning of value: "Bad Request"

It authenticates with success, then tries to push the image and fails with that error. Don't have any sort of similar error with NuGet, Maven, NPM.

Any thoughts?

Thanks!

Product: ProGet
Version: 4.7.13

3
replies

Hi
I have created deployment plan in BuildMaster and need to trigger the create release and deployment activity through TFS (if possible) or web api. I am trying to use api endpoints for release and deployment api like below but no use:
http://buildmaster/post/api/releases/create?applicationName=DeployWWMapping&releaseNumber=1.1.3&pipelineName=TriggerTFSBuildDeploy&key=5WRTeJcctiY32u2bEqTb4Q==
Can you please help how we can use the api to trigger release and deployment from api. Also is there a way to do same using TFS?

Product: BuildMaster
Version: 5.6.11

1
replies

Hi,

I am working upon Retrieve All Build Artifacts operation. When I run the concerned application, I get the below error:
"ERROR: 404 Could not find any build artifacts for build 'builds.json' number '1.2.4'."

builds.json is the build file I have uploaded to the jFrog Artifactory and 1.2.4 is the build number.
Now, in the Artifact library of jFrog, there is an artifact file named "Artifact4.txt" in which I have added properties as - build: builds.json and number: 1.2.4, but I am still getting the error.

Please suggest why is it not able to find any artifact against the builds.json.

Product: BuildMaster
Version: 5.7.2

1
replies

I downloaded the Free Version of ProGet and activated it.

According to this the Free Version doesn't have Package Promition and Vulnerability Scanning.

But I can use both of these Features in my Free Version. Not that I'm complaining, but... is that in purpose?

Product: ProGet
Version: 4.7.13

1
replies

Background:
I had an issue with the collection stage of PSDsc failing if powershell is not at least version 5 on the target machine. I can partially solve this with some custom assets to collect and configure powershell 5 installation via PSEnsure.

I've set up the powershell 5 installation as part of a server role that is a dependency of all other server roles.

Problem:
It seems that for a base role B and a dependent role D, that the order of execution will be

  • B (Collect)
  • D (Collect)
  • B (Configure)
  • D (Configure)

but this will not work for me because without B being configured the D collection will fail, which also then blocks the B configuration

Is there some way to abort/defer dependent roles until the base roles are properly configured?

Am I tackling this problem in a reasonable way?

Product: Otter
Version: 1.6.2

1
replies

Are build master creates a new release every time we push the current release to production. The biggest issue is that we have a 3 part release number and we want the 3rd number to be for patches and the second number to be what increments for normal releases. We do not want to create a patch release until we know we need one and build master is automatically creating it each time. Can this be stopped or at least configure how it does it? If wall we can do is stop it that is fine as we do not mind creating the release manually.

Product: BuildMaster
Version: 5.6.8

1
replies

How do I setup applications to iterate the first release digit e.g. 1.0.0 --> 2.0.0, instead of the default 0.0.1 --> 0.0.2?

Product: BuildMaster
Version: 5.7.2

0
replies

Background:
I'm running the latest ProGet docker container, which might make a difference.

Problem:
When I try to publish a PowerShell module (this happens with all modules, but in this example I'm publishing Plaster) to our feed, I get a 400 error. If I specify an incorrect apikey, I get a 403 as expected.

Register-PSRepository -Name proget-psgallery`
                      -SourceLocation http://192.168.1.230/nuget/proget-psgallery `
                      -PublishLocation http://192.168.1.230/nuget/proget-psgallery `
                      -InstallationPolicy Trusted `
                      -Verbose
Publish-Module -Name Plaster `
               -Repository proget-psgallery `
               -NuGetApiKey 'Admin:Admin' `
               -Verbose

I get the following error message and haven't been successful at hunting it down for why:

VERBOSE: Performing the operation "Publish-Module" on target "Version '1.0.1' of module 'Plaster'".
Publish-PSArtifactUtility : Failed to publish module 'Plaster': 'Response status code does not indicate success: 400 (Bad Request).
'.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.1.3.1\PSModule.psm1:1260 char:17
+ ...             Publish-PSArtifactUtility @PublishPSArtifactUtility_Param ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : FailedToPublishTheModule,Publish-PSArtifactUtility

Product: ProGet
Version: 4.7.13

1
replies

When can we expect support for Semantic versioning 2.0.0 ?

When publishing a package that has version number that follows semver 2.0.0 it fails with the fallowing error:

"System.Net.Http.HttpRequestException: Response status code does not indicate success: 500 (There was an error processing the request: Invalid version number.)."

Product: ProGet
Version: 4.3.1

2
replies

I'm using Maven Connector on Proget.

1 .When i try to search on the Maven Feed

no segments* file found in Lucene.Net.Store.SimpleFSDirectory@C:\ProgramData\ProGet\Packages.maven2\C31 lockFactory=Lucene.Net.Store.NativeFSLockFactory: files:

When i run the "Scheduled Task" on the Admin Panel

Creating C:\ProgramData\ProGet\Packages.maven2\I22 if necessary.
Opening C:\ProgramData\ProGet\Packages.maven2\I22\next-index.gz to write feed index.
Writing local artifact info to feed index.
Writing connector http://xcdeveljees2:8081/artifactory/repo artifacts to feed index.
Unabled to open Lucene index for connector 31

What are we doing wrong?

Regards

Product: ProGet
Version: 4.7.13

3
replies

We are trying to migrate from Artifactory to Inedo Proget (Maven feed). There are any massive approach to do this?

Regards

Product: ProGet
Version: 4.7.13

1
replies

Hi
I am using IIS::Ensure-Application to create application in IIS. I need to assign App Pool to the newly created application but there is no such option here to provide App Pool data. Please let me know how to assign App pool to an application in IIS using BuildMaster?

Product: BuildMaster
Version: 5.6.11

1
replies

Extensions won't install. I tried a custom extension as well as the provided extensions (Amazon, Azure..). Here are my settings:

I have added some more keys out of sheer desperation since the Administration Overview page keeps telling me that I need to set ExtensionsPath and ExtensionsTempPath.

Extensions packages are downloaded, but D:\ProGet\ExtensionsTemp is empty after several restarts, as is the Installed Extensions list. Both directories have the same permission settings. Interactively running the service didn't shed any light on the problem.

How can I convince the service to load extensions?

Product: ProGet
Version: 4.7.13

1
replies

We would like to allow active directory computer accounts to authenticate to Proget to pull packages (processes running as SYSTEM, which use the computer account over the network) - this always returns a 401, even when the accounts are in the correct group for access.

I assume there is a filter applied on the object type when authorising (for users only) - can this please be extended to computers? (Think it should be a simple change)!?

If I'm not correct can you advise how we can permit this?

Thanks

James

Product: ProGet
Version: 4.7.9

2
replies

Hi All,

I am trying to create a release that coordinates the deployment of packages from multiple applications. I have created a global pipeline with a global plan. I plan to use the deploy-package function. When I select the ${EnvironmentName} as the from and to stages in the pipeline filter (to target a particular environment), the deployment does not ever recognise the environment as the furthest stage, even if it is. If i dont specify the to and from values, the plan wants to promote and deploy all un-deployed environments instead of the one i want.

I would like to use the $EnvironmentName variable as i want to be able to use the same plan for all environments to ensure consistency.

Is this achievable?

Thanks,

Clint

Product: BuildMaster
Version: 5.7.1

2
replies

Hi,

I set up ProGet with LDAP and Integrated Authentication disabled.
The NuGet feed works without problem but npm throws a 401 when trying to download the package. Getting the correct version though works.

I added the API endpoint URL to my local computer and also the correct user via "npm login". When I add the group anonymous to the "View and Download Packages" right it works.

Any idea what I need to change so it works?

Product: ProGet
Version: 4.7.13

Ask A Question
Page: 1 2 3 4 5 6 8 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 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 102 103 104 105