Sonatype Nexus Lifecycle Onboarding and Policy Grandfathering
What are your impressions of the application onboarding and policy grandfathering features?
The application onboarding and Policy Grandfathering features are new and quite useful because they allow you to focus on what you're currently working on and the stuff that's grandfathered can go in your backlog. It's another feature that helps organize your workload.View full review »
The onboarding and policy grandfathering are quite useful, to keep in mind what we have already discussed around parts of the application, and to identify our own parts of the application which are not discovered by Nexus Lifecycle of course.View full review »
The application onboarding and policy grandfathering features are good.View full review »
The grandfathering mode allows us to add legacy applications which we know we're not going to change or refactor for some time. New developments can be scanned separately and we can obviously resolve those vulnerabilities where there are new applications developed. The grandfathering is a good way to separate what can be factored now, versus long-term technical debt. In most cases, these legacy applications are simply retired, so to refactor them wouldn't make sense. Most of them go through a rewrite cycle or are replaced by something have purchased.View full review »
The application's onboarding and policy grandfathering features are very easy to use. Most developers who I have given access have picked it up easily. The documentation is fantastic. I've never had a reason to contact support or asked a question, as most of the answers are available.
It can even grandfather certain components, because in a real world scenarios we cannot always take the time to go and update something because it's not backward compatible.View full review »