exceptionfactory commented on pull request #5065: URL: https://github.com/apache/nifi/pull/5065#issuecomment-838950445
> @exceptionfactory > > > It may need to be a separate task, but the increased build time raises the question of more granular builds so that changes to NiFi Registry only result in building NiFi Registry. Of course changes to core components will necessitate complete builds. What do you think? > > Yeah, the increased build time really feels to be a genuine issue. However I'm afraid we would want at least one full clean build no matter what, just to be sure. > > Maybe it would work the other way around - _don't build registry_ if it hasn't change. > The reason being nifi depends on registry, not the other way around. So if the registry changes, we will need to build nifi for sure. Maybe this is not that apparent yet but there are plans to move some artifacts from registry to the _nifi-api_. > > But I'm not sure what would be the best course of action. Thanks for the reply @tpalfy. I agree that getting a successful build of your PR with Registry across all three environments sounds good. Perhaps a follow-on issue to update the GitHub workflow configuration, including both timeout adjustments and selective builds, is the best way to go. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
