[xwiki-devs] [ANN] Contrib Parent 7.4-3 has been releases
I just released a new version of the Contrib parent poms which add support for automatic close and release on Nexus repository. See https://github.com/xwiki-contrib/parent. -- Thomas Mortagne
Hi, What is the purpose of having staging Nexus repositories if we provide build setups that automatically close and release them to the main repo? Why not use the main repo instead for the release process? Re staging repos, AFAIK we have pretty much never used them correctly (i.e. committers closing and releasing the staging repo taking the builds and testing them locally before they proceed) and specially now that contrib users can close and release themselves (correct me if I`m wrong on this one), this becomes more and more of a cumbersome step that, IMO, we should remove. The only advantage of releasing to a different repo than the main one would be to validate that the released artefact has the right groupID before automatically pushing it into the main repo (if that is possible with Nexus), but I`m just guessing here. Thanks, Eduard On Mon, Jun 13, 2016 at 1:00 PM, Thomas Mortagne <[email protected]> wrote:
I just released a new version of the Contrib parent poms which add support for automatic close and release on Nexus repository.
See https://github.com/xwiki-contrib/parent.
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Tue, Jun 14, 2016 at 10:20 AM, Eduard Moraru <[email protected]> wrote:
Hi,
What is the purpose of having staging Nexus repositories if we provide build setups that automatically close and release them to the main repo? Why not use the main repo instead for the release process?
This is just the default behavior when you user those parent pom but: * you can disable it for your project if you want * you might not want to give release right just yet to some junior release manager (in which case the staging repository is closed and wait for release from another user) Plus I'm really not motivated enough to start a discussion about wether or not we should completely ditch staging, I know I don't need staging in my use cases and I'm tired of going to the UI every time so I provided a helper :)
Re staging repos, AFAIK we have pretty much never used them correctly (i.e. committers closing and releasing the staging repo taking the builds and testing them locally before they proceed) and specially now that contrib users can close and release themselves (correct me if I`m wrong on this one), this becomes more and more of a cumbersome step that, IMO, we should remove.
The only advantage of releasing to a different repo than the main one would be to validate that the released artefact has the right groupID before automatically pushing it into the main repo (if that is possible with Nexus), but I`m just guessing here.
One thing we are supposed to do and still never did is to use Nexus validation possibility to enforce some rules on deployed contrib extensions during close.
Thanks, Eduard
On Mon, Jun 13, 2016 at 1:00 PM, Thomas Mortagne <[email protected]> wrote:
I just released a new version of the Contrib parent poms which add support for automatic close and release on Nexus repository.
See https://github.com/xwiki-contrib/parent.
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
participants (2)
-
Eduard Moraru -
Thomas Mortagne