I got an idea for a workaround, just use previously released version of opendaylight-karaf-empty for SingleFeaturetest only, and hope the results are valid. https://git.opendaylight.org/gerrit/49188 See comments in pom.xml file.
As usual, no time to test that myself, feel free to test and improve. Vratko. -----Original Message----- From: odlparent-dev-boun...@lists.opendaylight.org [mailto:odlparent-dev-boun...@lists.opendaylight.org] On Behalf Of Robert Varga Sent: 5 December, 2016 17:22 To: Michael Vorburger <vorbur...@redhat.com>; Ryan Goulding <ryandgould...@gmail.com> Cc: controller-dev <controller-dev@lists.opendaylight.org>; odlparent-...@lists.opendaylight.org Subject: Re: [Odlparent-dev] [controller-dev] Question about opendaylight-karaf-empty On 12/05/2016 05:11 PM, Robert Varga wrote: > On 12/05/2016 04:55 PM, Michael Vorburger wrote: >> >> The thing is, opendaylight-karaf-empty zip is actually ~112 MB. >> This file is downloaded whenever we perform a singleFeatureTest (to >> my understanding), which probably puts a lot of stress on nexus, >> especially when not all the features are necessarily needed. Is >> this something we could disable and allow singleFeatureTest to run >> in a non-offline mode? I am not quite sure the implications of >> doing so, and that is why I decided to pose the question to these >> mailing lists. >> >> >> did you ever get any replies to this? I had raised a similar Q in >> "Move opendaylight-karaf-empty (and opendaylight-karaf-resources) to >> fixed version", although I came at it from another angle - I'm >> questioning why opendaylight-karaf-empty has to be a daily SNAPSHOT, >> and suggested to do something about that.. let me bump that thread and add >> you directly. > > The answer to this ... depends. karaf-empty is pulling in our > branding, which may be something which changes during a release. > > I think this would be doable if we had a karaf-packaging base project, > which would release on its own and would then be pulled into odlparent > -- that would achieve this without going for all of the version skew > induced by having an odlparent version bump going on... To add further details to this, to cover the 'snapshot download' question. This stems from how our Jenkins and Nexus are configured -- -merge jobs cannot publish to -release repo, that is something only -release jobs can do. This is not something we want to change, as all of .m2/repository assumes that released artifacts do not ever change, hence you need to make sure you record the release in SCM. Before anyone suggests it: performing 'partial' project releases is technically possible, but a sure way to wreck something down the line (developer sanity being one of the more obvious candidates). Regards, Robert _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
