Bug 1062114
Summary: | RFE Maven repository as content source | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Carsten Ringe <carsten> |
Component: | Content | Assignee: | Nobody <nobody> |
Status: | NEW --- | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | JON 3.1.1 | CC: | hrupp, shiocaltz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Carsten Ringe
2014-02-06 07:52:35 UTC
Hy people, I was also looking for a way to integrate nexus and JON as i am evaluating JON as an alternative to: http://www.xebialabs.com/deployit So thank you Carsten for this feature request :) One other thing, think about automated tests (Arquillian and it's Drone/Graphene extensions) and nightly builds, it would also be awesome to have a maven plugin that would provision/deploy the artifacts on the cluster administered by JON to run the tests. Having the nighlty bluids and the pre prod / prod environments managed by JON would allow us to promote the release, thus obtaining deployment pipelines almost seamless, if not 100% automated (if desired) Given the Maven's acceptance and usage and the Nexus repository or releases repositories in general, it would be a really strong point for JON to be integrated with Maven/Nexus. Cheers, Marian Hey guys, those RfEs sound good. I wonder if you could help us implementing those. Content Source (providers) are implemented as server side plugins. Have e.g. a look at https://git.fedorahosted.org/cgit/rhq/rhq.git/tree/modules/enterprise/server/plugins/url for a content source that uses an url for backend connections. That nexus one could perhaps even "inherit" from the url one. Marian: what exactly do you mean with that maven plugin? A RHQ-plugin that somehow leverages maven to lay down bits? Or a maven plugin that talks to RHQ so that RHQ can lay down the bits? |