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 15 of 103 (20 questions out of 2054)
3
replies

I am glad to see in 4.7.9 the catalog endpoint is allowed - however i believe there is a unnecessary restriction in the DockerAbsoluteUrlHandler class in the ProGet.WebApplication.dll - it appears the code requires that the User-Agent starts with "docker" (GetHttpHandler - method)

This is limiting - for example Octopus does not send this User-Agent when calling docker registry endpoints. I would recommend removing that restriction.

Product: ProGet
Version: 4.7.9

2
replies

When defining a plan, I noticed the templates and built-in operations available for selection. However, other plans are not available. Is this by design? Is it possible to call another plan within a plan?

What I'm trying to achieve is to define an application specific plan to call a global plan.

Product: BuildMaster
Version: 5.6.9

1
replies

Hi there,

Are there plans to port the Actions in the Azure extension to non-legacy versions? We're looking at Azure to deploy things, and just wondering how much effort it would be to setup in BuildMaster.

Thanks!

Product: BuildMaster
Version: 5.6.10

1
replies

Hi,

We migrated to new servers however after the the migration of Proget, we are experiencing this issue.

Getting metadata from https://registry.npmjs.org/-/all
Error processing JSON: System.Exception: uninclused
at Inedo.ProGet.ScheduledTasks.Npm.FullNpmConnectorIndexScheduledTask.<IndexConnectorAsync>d__1.MoveNext()

We have recreated the NPM connector and still getting the same error.

Product: ProGet
Version: 4.3.1

1
replies

We've installed our Free ProGet server for evaluation in an Azure virtual machine. It works all right so far, but we need to make sure only authorized people have access to the feeds. Is it possible to configure a feed to ask for a password when accessed?

Product: ProGet
Version: 4.7.8

4
replies

I'm unable to view newly added Docker Package in ProGet after successful push. I see the package name library\packagename but when clicking on the package link I get the following error.

An error occurred getting the package: Value cannot be null. Parameter name: packageVersion

here is my example:
sudo docker tag sonarqube:5.6 myprogetserver:443/mydocker/sonarqube:5.6
sudo docker push myprogetserver:443/mydocker/sonarqube:5.6

Product: ProGet
Version: 4.7.4

1
replies

How I will find out which version of ProGet my Organisation is using?

Product: ProGet
Version: 4.7.8

1
replies

Hi Support,

So, Proget is actually running on address "http://<oursite>:81/" and the proxy runs on "https://<oursite>". Proget still shows that it is running on Port 81 everywhere in the interface.

Is there a way to tell ProGet on what address it runs?

Thanks.

Jason

Product: ProGet
Version: 4.7.6

1
replies

Apologies for the vagueness of this but we, seemingly randomly, get the following error during our Build step across at least two of our plans:

DEBUG: Inheriting deployable (ID=0) from context.
DEBUG: Artifact "Project.SmokeTests" found (ApplicationId=80, ReleaseNumber=0.5, BuildNumber=51, DeployableId=0).
ERROR: Artifact file not found at expected path (D:\BuildMaster\Artifacts\A80\R525\B7615\Project.SmokeTests.zip). It may have been purged as part of a retention policy.

If we kick the build off again, it succeeds with no issues.

Incidence is pretty low (~1 in maybe 50 builds).

Any ideas what could cause this?

Product: BuildMaster
Version: 5.6.8

1
replies

Buenas tardes,

Actualmente tengo un problema en donde muestra el siguiente mensaje cada vez que intento cargar un paquete:

URL: http://localhost:81/packages/add-package/upload?feedId=1
Referrer: http://localhost:81/packages/add-package/upload?feedId=1
User: Admin
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36
Stack trace: en System.IO.Compression.ZipArchive.ReadEndOfCentralDirectory()
en System.IO.Compression.ZipArchive.Init(Stream stream, ZipArchiveMode mode, Boolean leaveOpen)
en System.IO.Compression.ZipArchive..ctor(Stream stream, ZipArchiveMode mode, Boolean leaveOpen)
en Inedo.ProGet.Feeds.NuGet.NuGetFeed.<InstallOrUpdatePackageAsync>d__40.MoveNext()
--- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
en Inedo.TaskExtensions.WaitAndUnwrapExceptions(Task task)
en Inedo.ProGet.WebApplication.Pages.NuGet.Packages.UploadPackagePage.<>c__DisplayClass9_0.<CreateChildControls>b__0()
en Inedo.Web.Controls.ButtonLinks.PostBackButtonLink.Inedo.Web.Controls.ISimplePostControl.ProcessValidPost()
en Inedo.Web.PageFree.SimplePageBase.ProcessPost(IEnumerable1 controls, Boolean isValid, IList1 validationResults, ISimplePostControl postbackTrigger, String eventName)
en Inedo.Web.PageFree.SimplePageBase.ProcessPost(IEnumerable1 controls, Boolean isValid, IList1 validationResults, ISimplePostControl postbackTrigger, String eventName)
en Inedo.Web.PageFree.SimplePageBase.ProcessPostBack()
en Inedo.Web.PageFree.SimplePageBase.<ProcessRequestAsync>d__48.MoveNext()
--- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
en System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar)
en System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
en System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Product: ProGet
Version: 4.7.8

2
replies

I'm having trouble getting npm to login to a Docker-hosted ProGet (4.7.8 on c1858e8f1d8bdb46ed493a937e61bf951d7c730549abb54cd579e09332169510)

npm client is on macOS, I'm using npm adduser --verbose

login to Docker-hosted ProGet 4.7.8:

npm info it worked if it ends with ok
npm verb cli [ '/usr/local/Cellar/node/6.7.0/bin/node',
npm verb cli   '/usr/local/bin/npm',
npm verb cli   'adduser',
npm verb cli   '--verbose' ]
npm info using npm@3.10.7
npm info using node@v6.7.0
npm verb config Skipping project config: /Users/msmiley/.npmrc. (matches userconfig)
Username: mike.smiley
Password: 
Email: (this IS public) mike.smiley@a2ius.com
npm verb adduser before first PUT { _id: 'org.couchdb.user:mike.smiley',
npm verb adduser   name: 'mike.smiley',
npm verb adduser   password: 'XXXXX',
npm verb adduser   email: 'mike.smiley@a2ius.com',
npm verb adduser   type: 'user',
npm verb adduser   roles: [],
npm verb adduser   date: '2017-03-28T18:07:06.431Z' }
npm verb request uri http://ambrose.a2ius.com/npm/npm/-/user/org.couchdb.user:mike.smiley
npm verb request new user, so can't send auth
npm info attempt registry request try #1 at 2:07:06 PM
npm verb request id a8741d4396644053
npm http request PUT http://ambrose.a2ius.com/npm/npm/-/user/org.couchdb.user:mike.smiley

same login to 4.7.8 on Windows yields the following (as expected):

npm info it worked if it ends with ok
npm verb cli [ '/usr/local/Cellar/node/6.7.0/bin/node',
npm verb cli   '/usr/local/bin/npm',
npm verb cli   'adduser',
npm verb cli   '--verbose' ]
npm info using npm@3.10.7
npm info using node@v6.7.0
npm verb config Skipping project config: /Users/msmiley/.npmrc. (matches userconfig)
Username: (mike.smiley) 
Password: (or leave unchanged) 
Email: (this IS public) (mike.smiley@a2ius.com) 
npm verb adduser before first PUT { _id: 'org.couchdb.user:mike.smiley',
npm verb adduser   name: 'mike.smiley',
npm verb adduser   password: 'XXXXX',
npm verb adduser   email: 'mike.smiley@a2ius.com',
npm verb adduser   type: 'user',
npm verb adduser   roles: [],
npm verb adduser   date: '2017-03-28T18:02:20.183Z' }
npm verb request uri http://ignatius/npm/npm/-/user/org.couchdb.user:mike.smiley
npm verb request new user, so can't send auth
npm info attempt registry request try #1 at 2:02:20 PM
npm verb request id 662c0fb6d51a661f
npm http request PUT http://ignatius/npm/npm/-/user/org.couchdb.user:mike.smiley
npm http 201 http://ignatius/npm/npm/-/user/org.couchdb.user:mike.smiley
npm verb headers { 'cache-control': 'private',
npm verb headers   'content-length': '13',
npm verb headers   'content-type': 'application/json; charset=utf-8',
npm verb headers   server: 'Microsoft-HTTPAPI/2.0',
npm verb headers   'x-aspnet-version': '4.0.30319',
npm verb headers   'x-ua-compatible': 'IE=edge',
npm verb headers   'x-proget-version': '4.7.8.4',
npm verb headers   date: 'Tue, 28 Mar 2017 18:02:22 GMT' }
npm verb request invalidating /Users/msmiley/.npm/ignatius/npm/npm/-/user/org.couchdb.user_3Amike.smiley on PUT
npm info adduser Authorized user mike.smiley
Logged in as mike.smiley on http://ignatius/npm/npm/.
npm verb exit [ 0, true ]
npm info ok 

I've tried different npm feed names as well as different user names. HTTP PUT reply never arrives, but connection remains open.

Product: ProGet
Version: 4.7.8

2
replies

I understand that PSCall has the ability to access output parameters from the script asset being called. What I don't understand is is how to define the script so that it has output parameters that will be accessible to PSCall.

I'm very familiar with powershell. I've tried creating a script asset parameter with a [ref] parameter but that didn't work the way I did it.

By the way, the docs for PSCall include a reference to an hdars script. It would be nice if the content of the hdars script was included in the docs for PSCall as well.

Product: BuildMaster
Version: 5.6.9

2
replies

I have Proget set up with a user called "Jenkins" which is in the group "Pushers" which has permissions for the default tasks of Publish Packages and Promote Packages. This succeeded once (at least I think so, I'm not 100% sure if it succeeded while it was just under password control), but then I wanted to change the password so I deleted and recreated the user and made sure everything was OK again. However, now all pushes fail with:

Upload http://172.23.121.218:8080/maven2/internalmaven/com/couchbase/lite/couchbase-lite-android/2.0.0-SNAPSHOT/couchbase-lite-android-2.0.0-20170328.002044-1-javadoc.jar
Could not transfer artifact com.couchbase.lite:couchbase-lite-android:jar:javadoc:2.0.0-20170328.002044-1 from/to remote (http://<user>:<pass>@172.23.121.218:8080/maven2/internalmaven): Could not write to resource 'com/couchbase/lite/couchbase-lite-android/2.0.0-SNAPSHOT/couchbase-lite-android-2.0.0-20170328.002044-1-javadoc.jar'

I have recreated the group and user numerous times, as well as giving permission explicitly to the user. None of these has solved the problem. If I add anonymous access, then both the password URL and the non-password URL work for pushing. Is there a way to find more information about what went wrong? Is HTTP Basic Auth the incorrect way to do this?

Product: ProGet
Version: 4.7.4

2
replies

I noticed that dependent roles are now available on roles (which is great!). I am struggling to figure out how to get that to actually influence the order in which roles are executed. Not matter what I do, that order is always the same (the order as the roles appear in the "Servers" tab).

I created a simple test scenario, where I have 3 roles, where RoleA (Dependent on RoleB), RoleB (Dependent on RoleC), and RoleC (no dependencies). Would expect the order to be RoleC executes 1st, RoleB executes second, and RoleA last. But I was unable to influence the order of the execution.

Product: Otter
Version: 1.5.5

1
replies

Hello,

I'm trying to get combination of Proget, Docker and OctopusDeploy running.
It works almost perfectly except I've to guess a lot of things in my configuration because api supplied to docker register is not enough, and octopus can't query my proget properly.

According to:
https://octopus.com/docs/deploying-applications/docker-containers/registries

Octopus supports docker registry without problem but there is a note:

"Note that as of the current version of ProGet (version 4.6.7 (Build 2)), their Docker Registry Feed does not expose the full Docker API and is missing the _catalog endpoint which is required to list the available packages for release selection. It has been indicated that this may change in a future release."

My question is when are you going to implement _catalog endpoint and other things required for OctopusDeploy to query docker registry?

Product: ProGet
Version: 4.7.8

1
replies

I have a proget site which need to upload the maven package . I need to keep the maven package as source. kindly let me know the details

Product: ProGet
Version: 4.7.8

1
replies

I'm trying to access the full HTTP response resulting from an HTTP post operation but I only get the first 100 characters.

It looks like HttpPostOperation inherits from HttpOperationBase which has a MaxResponseLength as seen below.

[Category("Options")]
[DefaultValue(1000)]
[DisplayName("Max response length")]
public int MaxResponseLength { get; set; } = 1000;

The definition of this property seems to explain why I only see the first 1000 characters of the response. This also leads me to believe that the HTTP post operation editor in the plan should allow me to edit a "Max response length" field under the options category but no such field exists in the editor under the Options category. I also tried to add the field in the text only mode but it has no effect on plan execution and it freaks out the editor.

I was running 5.6.8 so I went ahead and updated to 5.6.9 just in case that could fix something but it had no effect.

Product: BuildMaster
Version: 5.6.9

1
replies

Intuitively (and maybe wrongly), I expect all of the statements in a plan to execute on the effective servers.

I got stuck for an hour today because the HTTP POST statement seems to execute locally rather than on the effective server(s). I came to this conclusion based on the following...

  • Execute plan
  • Plan adds host file entry to target server
  • Plan posts to a URL and post produces a host name not found error
  • Manually added host file entry to the server BuildMaster runs on
  • Re-execute plan and now post to URL finds the host name

Should the HTTP POST statement work execute on the target server or am I thinking about this wrong.

Product: BuildMaster
Version: 5.6.8

2
replies

I get a System.Runtime.Serialization.SerializationException when I try to push a *.upack package that has a dependency package specified.

Using this upack.json, the package is pushed successfully:

{
 "name": "app",
 "version": "1.0.0",
 "description": "Dummy application"
}

But using this upack.json, I get the error:

{
 "name": "app",
 "version": "1.0.0",
 "description": "Dummy application",
 "dependencies": [ "base:1.0.0" ]
}

Note that a package called base with version 1.0.0 does already exist in the feed

Error details:

Unhandled exception: System.Runtime.Serialization.SerializationException: The data contract type 'ProGet.Client.PackageDependency' cannot be deserialized because the required data member 'package' was not found.
   at System.Runtime.Serialization.Json.XmlObjectSerializerReadContextComplexJson.ThrowMissingRequiredMembers(Object obj, XmlDictionaryString[] memberNames, Byte[] expectedElements, Byte[] requiredElements)
   at ReadPackageDependencyFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )
   at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
   at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
   at System.Runtime.Serialization.Json.XmlObjectSerializerReadContextComplexJson.ReadDataContractValue(DataContract dataContract, XmlReaderDelegator reader)
   at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
   at System.Runtime.Serialization.XmlObjectSerializerReadContextComplex.InternalDeserialize(XmlReaderDelegator xmlReader, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle, String name, String ns)
   at ReadPackageMetadataFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )
   at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
   at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
   at System.Runtime.Serialization.Json.XmlObjectSerializerReadContextComplexJson.ReadDataContractValue(DataContract dataContract, XmlReaderDelegator reader)
   at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
   at System.Runtime.Serialization.XmlObjectSerializerReadContextComplex.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)
   at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
   at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader)
   at ProGet.Client.Program.push(String package, String target, String user)

Product: ProGet
Version: 4.7.7

1
replies

Hi,

Is it possible to disable requiring api key or username pwd to push packages to proget server ?

Product: ProGet
Version: 4.7.7

Ask A Question
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 15 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