Topics created by michal.roszak_0767

Hi @michal-roszak_0767 , 401/403 are not logged, so you won't see a server side event. 403 means authentication was successful but the permissions are not OK My guess is that the wrong feed or credentials are being specified. Like maybe using an API key? Thanks, Alana

Hi @michal-roszak_0767, Can you please post what the fix was? Thanks, Rich

@atripp This Log is mess! I'm trying to list log for particular Key /administration/api-keys/access-logs?apiKeyId=27 and list is.... I don't know from what! This is list of all requests. Looks familiar? Cheers, Michal

@michal-roszak_0767 it wouldn't hurt to start a new topic about it, but it's design decision so you'd have to make a good use case for it :) I can't find the discussion (maybe it was internal), but the idea is that "generic website connectors" for Asset Directories are a poor solution for "offline" environments. A "generic proxy" like ngnix will always be better in every way.

Hi @michal-roszak_0767, Oh that's a whole lot of connectors and this is most definitely going to cause some performance issues. Remember that ProGet needs to forward every request you make to all 10 of those servers, and some of these repositories will not respond very quickly. Like JCenter was deprecated/retired a few years ago, and I can't imagine is performant at all. Especially for things like metadata requests. Maven is not a very patient client and will time out while waiting for ProGet. There is really no way around this. You'll need to use less connectors. -- Dean

@michal-roszak_0767 said in Pull Maven artifacts - invalid version: Next victim: https://repo1.maven.org/maven2/org/springframework/data/spring-data-releasetrain/ jeeze, what a mess! Well, there goes any hope of using v[0-9]+ -- they just straight up use random strings as version numbers. https://repo1.maven.org/maven2/org/springframework/data/spring-data-releasetrain/. https://repo1.maven.org/maven2/org/springframework/data/spring-data-releasetrain/Neumann-SR9/ Open to ideas, but based on the URLs alone... I don't see a good way to identify one of these as an artifact and the other as a version of an artifact.

@michal-roszak_0767 those are also invalid versions and you should never upload them to a feed (repository) directly; see https://docs.inedo.com/docs/proget/feeds/maven#snapshot-versions The code has already been fixed and the maintenance release is scheduled for next week. We could get you a prerelease, but I don't think your developers are manually uploading artifacts using the Web UI? If you want to upload artifacts with bad versions now you can just use the maven client (e.g. maven-deploy) or just do a basic PUT of the file to the desired group/artifact-id.

Hi, @rhessinger Works like a charm :) Thanks. Regards, Michal

Hi @michal-roszak_0767 , Thanks for letting us know! Unfortunately the Feed Wizard seems to have some quirky behavior when configuring certain combinations of options, as you've noticed. We are actually in the process of rewriting the new feed wizard to be a bit more simpler (esapecially behind-the-scenes), hopefully in the next couple weeks it'll be in a new maintenance release. In the meantime, if you encounter these errors... I would just create the connectors on the MAnage Feed page. Which it sounds like you've done :) -- Dean

@michal-roszak_0767 currently maven2 is a workaround, so it will continue to warm. In ProGet 2025, Maven will create the expected feed type.

Hi @michal-roszak_0767, This is what I meant by the Security API -- a combination of HTTP Endpoints and pgutil commands. We will consider them for our ProGet 2026 roadmap. So until then you'll need to use the Native API; At this time the Native API is the option. You can also check out @steviecoaster 's PowerShell module, which has some modules that can help https://github.com/steviecoaster/InedoOps Thanks, Alana

Hi @michal-roszak_0767 , Just as an update, we've added this to our roadmap planning for ProGet 2026. We will begin that process later this year, after ProGet 2025 has been released (see road to ProGet 2025). Cheers, Alana

Hi @michal-roszak_0767, Ah, that must have been an oversight; trivial change but best we don't change it until ProGet 2025. I think you can use maven2 as the type for now, it's the internal identifier. Later on, we will make it maven and mavenlegacy Thanks, Alana

Hi @michal-roszak_0767 , This is a third-party / community plugin and we have no plans to maintain it ourselves. I hear it still works, but is a bit outdated. HOWEVER, the former owner very recently "handed it over" to another community member. So this may mean we'll see some "new life" or changes -- I think they're still figuring out how to actually publish a new version, or something like that: https://github.com/jenkinsci/inedo-proget-plugin Thanks, Alana

@atripp Done: https://forums.inedo.com/topic/5347/feature-request-feed-other-settings-editor Michal