I'm afraid you are simply producing invalid packages. Per the NuGet specification, a package id "may not contain spaces or characters that are not valid for a URL" ProGet could validate better on upload, but ultimately you need to stop producing invalid packages if you want to use them in TFS, VS, etc. Even if ProGet supported invalid packages, it's highly likely that those tools won't, and will stop working all of a sudden.

Thanks very much, Scott. You helped me by mentioning that the feeds themselves also need to support SemVer 2.0. I wasn't aware of that fact. So I just migrated our feeds an now everything works fine.

Yes, we're currently using dotnet nuget push to push packages. We're using the "legacy" *.symbols.nupkg format, though, to be safe.

This is also being discussed here; long story short, this is a bug in Microsoft's PowerShell Gallery (and in the packages) in that they have two conflicting version numbers, and sometimes one is used, sometimes the other is used. The docs have been updated for now: https://github.com/Inedo/inedo-docs/commit/10c42c3ad546ac2feb4748b7736db06567c7a6d6

Okay, I've resolved it. The problem was that I'd put in the project name without a path - so BuildMaster was assuming a default path. The message was really unclear. It would be beneficial to allow the user to populate that field with a 'browse' function to find the solution/project or, at the very least, have some validation on the input to ensure you've entered something which looks like a full file path.

That error is coming from the SSH library that BuildMaster uses to connect, and offhand I don't know the causes (aside from obvious). One possibility is that username/password isn't enough, and you need to send a certificate. Putty may already be configured to do this. But can you enable SSH logging on your Linux box? This way, you can see the problems of incoming connections and we can further help from there.

Hi Ryan, Sorry for the delay in getting back to you - we're planning to add this to ProGet 5.2, which currently has a release date of April 11. It should be included in Inedo SDK 1.1.2 (see tentantive spec here). Does that look like it will cover your situation?

I would try reinstalling it. I didn't have to create the site in IIS.

I'm not sure why that response says that (I believe it was written when ProGet was still in Beta), but it is in fact inaccurate. The rules for closed testing or DR instances is that a separate license is required as per the licensing agreement: https://inedo.com/proget/license-agreement In order to clarify this with some examples, I've added the following documentation that will release when 5.2 goes live: https://github.com/Inedo/inedo-docs/blob/proget-5.2/ProGet/administration/license.md#examples

The docker image is no longer in Beta, FYI.

update: we will be addressing this in Otter 2.2, and rafts will now only sync as needed. This will significantly reduce the time required.

Sorry on the delayed response; PG-1472 should fix the version selector failing for packages with partially missing snapshot metadata, like maven-archetype-plugin, which was used to test.

Those are handled at different abstraction layers; the agent code doesn't have any knowledge of the context its being run in (i.e. OtterScript, the Service, etc). That's the intent of that "with credentials" setup, to allow this information to pass down.

You can host ProGet in the cloud (AWS or Azure), but Inedo does not offer hosting of ProGet at this time. It is on our future roadmap, but there is very little interest it based on previous research.

Unfortunately we can't figure out any reason that Age would be returning an empty string. We're thinking there must be something else... can you share the entire NUSPEC file so we can reproduce it better.

We can't reproduce this; a more likely scenario is that the nuspec in question has an invalid item and is causing an otherwise unknown and unexpected error We would need to full nuspec and the reproduction instructions to better investigate.

Thanks for the suggestion, I've filed this to be done here: https://github.com/Inedo/inedox-inedocore/issues/112

The problem is that OtterScript attempts to parse those variables first. Just use quotes: set $foo = true; set $bar = true; set $foobar = $PSEval("$foo -and $bar"); Log-Information `$foobar = $foobar; # prints: $foobar = True

Adding for ideas: Will need cmdlets to create, edit, delete, start and stop configuration and orchestration work. Allow to accept pipeline input. That way I can schedule at that time, to run an orchestration job, pick the servers based on the results of the orchestration, and run a job at that time for those servers, environments, or roles that fit the criteria.

I will wait :) Thank you for your fast reaction Cdt Philippe