Obsolete
Status Update
Comments
da...@gmail.com <da...@gmail.com> #2
To me, it's not only the very natural next step to make checks plugin a core plugin, but I would go even further and consider to promote checks plugin to a pure core feature, by internalizing the whole code to be a part of core Gerrit. This should significantly simplify (or even make first possible) the usage of core Gerrit infrastructure, like secondary index, NoteDb Schema migration facilities, better, while native UI integration etc.
A number of current design limitations in checks plugins are coming from its nature being a plugin and not a pure gerrit core feature.
See for examplehttps://crbug.com/gerrit/11474 raised by OpenStack's infra team (that I totally agreed with) about missing multi repository checkers support; or this design documentation for adding sub checks feature: [1], that would probably also benefit from promoting checks plugin to core Gerrit feature (while it would certainly require some kind of NoteDb schema migration for check persistence layer).
[1]https://gerrit-review.googlesource.com/c/homepage/+/235693
A number of current design limitations in checks plugins are coming from its nature being a plugin and not a pure gerrit core feature.
See for example
[1]
da...@gmail.com <da...@gmail.com> #4
> Adding it as a core feature was already rejected [1] [2] but maybe it's time to revisit that.
It was rejected before ESC was established. So my call is to bring the question again to the ESC to decision and re-visit CI-support as native feature in gerrit.
Making CI support a first class citizen in Gerrit is a crucial core feature that should be natively supported in Gerrit core.
It was rejected before ESC was established. So my call is to bring the question again to the ESC to decision and re-visit CI-support as native feature in gerrit.
Making CI support a first class citizen in Gerrit is a crucial core feature that should be natively supported in Gerrit core.
da...@gmail.com <da...@gmail.com> #5
We discussed this in yesterday's ESC. Conclusion for now is to not make it a core feature (i.e. keep it as a plugin) until it's more mature. We will revisit this in the next quarter.
br...@google.com <br...@google.com> #6
I think this is obsolete, because we are not planning to invest anymore into this plugin.
[Deleted User] <[Deleted User]> #7
What is replacing/superseding the functionality to make it obsolete?
ek...@google.com <ek...@google.com> #9
[Monorail components: SteeringCommittee]
ek...@google.com <ek...@google.com> #10
[Monorail components: -ESC]
is...@google.com <is...@google.com> #11
Edits were made to reflect the following in Monorail: auto-CCs.
Description