I see what you mean. Though in this video the suffix is used for dev versions or release candidates. But I guess we could (ab)use this for branches.

Will try and see how it goes.

Thanks for the suggestion - I'd already thought of that. But (not having tried yet) I don't see how it would help.

The reason for wanting to use a four-part version number is this; Like most software companies we use a branch-merge strategy for product support. For each product support fix we create a branch and assign a version using the 4th number (e.g. 1.2.2.1) indicating revisions on the branch (to ensure all shipped components have distinct version numbers traceable back to the source code). When the branch is merged/closed the new trunk version will be assigned a 'normal' (3-part version number 1.2.3)

Correct me if I'm wrong, but if ProGet enforces SemVer2 versions for Universal Packages, then we won't be able to post two different versions of a component to a feed. In this case they would have the same package version, but different metadata. Does ProGet Allow that?

We are testing the Jenkins plugin to publish a Universal package to ProGet and it only allows versions in the format : x.x.x

From the documentation I see that NuGet feeds support two different version formats:
https://inedo.com/support/kb/1157/nuget-version-number-formatting-restrictions

From the upack command line reference and documentation it looks like Universal packages might also support longer versions. I cannot see any discussion about the version restrictions for universal packages.

This page indicates longer versions are allowed:

https://inedo.com/support/documentation/upack/universal-packages/package-identification

But there is no mention here:

https://inedo.com/support/documentation/upack/tools-and-libraries/upack-cli

Is this a bug (or limitation) in the Jenkins Inedo Proget plugin?

Product: ProGet
Version: 5.1.3

Just testing Proget upload to a new Proget install from a local Jenkins instance.

On Proget I have created a new Universal Package Feed, and configured a test project in Jenkins to push to this.

The Proget Adminstration page shows an error:

An error occurred processing a POST request to http://proget/upack/Test/upload: Value cannot be n...

And the details show:

Message:

An error occurred processing a POST request to http://proget/upack/Test/upload: Value cannot be null. Parameter name: target

Details:

System.ArgumentNullException: Value cannot be null.
Parameter name: target
at Inedo.ProGet.Feeds.MultiHasher.<CopyAndComputeHashesAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.Feeds.MultiHasher.<CopyAndComputeHashAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.Feeds.Universal.UniversalFeed.<InstallPackageInternalAsync>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.WebApplication.FeedEndpoints.Universal.UniversalRepositoryHandler.<ProcessUploadRequestAsync>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler.FeedRequestHandler.<ProcessRequestAsync>d__8.MoveNext()`

Product: ProGet
Version: 5.1.2

Hi guys,

we are evaluating ProGet 5.1 free - currently running using the built-in web server.

The install is on a Windows Server 2012 with multiple IP addresses assigned. I want to run the ProGet server on a specific IP address (not the default one), and on port 80.

But I cannot see how to change the configuration. When I use the inedo hub settings the entry field it won't accept any other values that the default.

I had also previously tried installing and using IIS - but could't get that to work at all.

Do you have any suggestions?

Dwight

Product: BuildMaster
Version: 6.0.6