Questions regarding ProGet Usage

[arunkrishnasaamy.balasundaram_4161]

I have installed ProGet Free version and analysed the tools. Below are my queries

1. Group repo and Proxy repo can be created but task FullMavenConnectorIndex has to be executed everytime to pull latest data from another feed/maven external repo through connector. Is there an option to auto enable it?
2. Context path cannot be set as per documentation. is our understanding correct?
3. Does Group repo holds any data? if so then will it not increase the space or data redundancy?.
4. Is it possible to block certain artifacts like log4j and particular versions through routing rules that are based on regular expressions?
5. What is the configuration required for 2k feeds and 100k upload/downloads per day?
6. The metadata of artifact doesn't display who published the artifact. any feature needs to be enabled?
7. There is no generic search option to search for an artifact and its presence in the feeds. is there a common search box available other than going into each feed?
8. Is there a cleanup policy option available?
9. How to generate support zip file?
10. How to migrate data from one of our existing artifact repository to ProGet? We have tried existing import option from different artifact server but it was unsuccessful
11. Is there a DR capability?
12. Is High availability option available on on-prem and AWS?

Kindly let me know if the above queries are addressed in ProGet tool.

Thanks,
Arun

[stevedennis]

Hi @arunkrishnasaamy-balasundaram_4161,

I'll do my best to answer these!

1. You can configure the FullMavenConnectorIndex job to run a routine basis under Admin > Scheduled tasks; it's not enabled by default because the MavenCentral Index is very large

2. I'm not sure what "Context path" means?

3. I'm not sure what you mean by "Group" repo?

4. The way to handle this in ProGet is by using Policies & Rules to define noncompliant artifacts; certain versions of log4j would be considered noncompliant because it has that severe vulnerability

5. We do not recommend 2000 feeds in any scenario; I wonder i there's a disconnect between what a "Feed" is and what you're looking for. A feed is place where you store all of the artifacts for a division/group of projects. The volume isn't a problem, but even a massive organization should have dozens of feeds at most

6. This should show on the "History" page

7. There is the "Packags" page at the top that can do some cross-feed searching

8. Yes; see https://docs.inedo.com/docs/proget/administration/retention-rules

9. I'm not sure what a support zip file is.

10. In general you would follow the migration guides we've published; however, your existing artifact server may not be configured to allow importing. If you're running into issues, best to open a new thread on the forums and we can review/investigate

11. Yes; see https://docs.inedo.com/docs/proget/replication-feed-mirroring/proget-howto-utilize-feed-replication-for-disaster-recovery

12. Yes.; see https://docs.inedo.com/docs/installation/high-availability-load-balancing/high-availability-load-balancing

Hope this helps point you in the right direction,

Steve

[arunkrishnasaamy.balasundaram_4161]

1. if i configure FullMavenConnectorIndex to run once a day and if new artifact added to the external repository in after the task completion for the day. do i have to wait to access that artifact till the execution of the task next day?
2. "Context path" is what mention in the bas url post / like www.google.com/search. heare search is the context path
3. "Group" repo is a single feed which combines multiple feeds into one to ease the access
4. We are planning to have 2k feeds because we are going to store artifacts of multiple teams and needs to have seperate feeds in order to maintain the privacy of data
5. support zip file will have the logs and config of the instance that we can share with ProGet team incase if we run into some issue and the file can be used to debug it from ProGet perspective.

Thanks

[stevedennis]

Hi @arunkrishnasaamy-balasundaram_4161 ,

Thanks for clarifying!

[1] The MavenIndex file is not at all required to download artifacts from a remote Maven Repository nor to see the latest version of artifacts. In ProGet, all this allows you to do is browse remote artifact files in the ProGet UI which typically isn't very helpful.

[2] It's not possible to change this

[3] ProGet does not have "group repositories", but uses feeds with connectors. The model is different, and feeds with connectors will often cache packages
in a lot of organizations.

[4] It's likely you will be unsuccessful in your ProGet configuration with a setup like this or at least give your users a big headache and lots of pain/confusion. This is considered an "old mindset" the for configuring artifact repositories that were based on "files and folders on a share drive" not packages.

This "closed approach" will greatly slows down development, causes duplicate code, and lots of other problems. Modern development approaches do not use this level of highly-granular permission. Instead, they take a innersource model. You do not need to make everything available to everyone.

However, less than 1% of your 2k projects will contain sensitive IP or data that other teams can't access - those projects should be segregated into sensitive feeds. The logic is, "if everything is sensitive, then nothing is sensitive"

[5] ProGet does not generate a "support zip file"; if we require additional information when supporting users we ask for the specific information