I was ok with moving code between the repos Sounds good, Having a hard time with the mixed python and java code from the single root pom.xml that is picked up by Jenkins jobs - It may not have been a good idea to mix the 2 technologies in a single repo. I'll work through the issues as I try to get code coverage working. Worst case I will just remove all the java code - store it until after the release and concentrate on the python code. /michael
-----Original Message----- From: Gildas Lanilis via RT [mailto:onap-helpd...@rt.linuxfoundation.org] Sent: Monday, April 30, 2018 6:20 PM To: Michael O'Brien <frank.obr...@amdocs.com> Cc: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org Subject: RE: [ONAP Helpdesk #55393] [LOG] New repo request for logging-analytics - add new java and python child repos Hi Michael, Currently for logging there is 1 repo labelled "logging-analytics". This repo can't be renamed. LF will need to create 2 new repo > Logging-analytics/java > Logging-analytics/python And you will need to move the code appropriately, then LF will need to lock the " logging-analytics" repo. In term of timing, I fear this is not the right time to do it before Beijing Sign-Off. Thoughts? Thanks, Gildas ONAP Release Manager 1 415 238 6287 -----Original Message----- From: Michael O'Brien [mailto:frank.obr...@amdocs.com] Sent: Sunday, April 29, 2018 5:43 PM To: onap-helpd...@rt.linuxfoundation.org Cc: Gildas Lanilis <gildas.lani...@huawei.com>; onap-disc...@lists.onap.org; onap-tsc@lists.onap.org Subject: RE: [ONAP Helpdesk #55393] [LOG] New repo request for logging-analytics - add new java and python child repos Yes, both issues are ok We can have just 2 top level repos - like you propose The history can be deleted if this makes it easier - if you can preserve it - preserve it on the repo where all the existing code will go - the java one. You can put everything on one side for now - as the python folder will need to be moved and a new root pom.xml for it. Anything to help out the transition - the goal is to have separate CSIT, CLM, Docker, Sonar jobs Thank you /michael -----Original Message----- From: Anil Belur via RT [mailto:onap-helpd...@rt.linuxfoundation.org] Sent: Sunday, April 29, 2018 8:39 PM To: Michael O'Brien <frank.obr...@amdocs.com> Cc: gildas.lani...@huawei.com; onap-disc...@lists.onap.org; onap-tsc@lists.onap.org Subject: [ONAP Helpdesk #55393] [LOG] New repo request for logging-analytics - add new java and python child repos On Sun Apr 29 19:28:26 2018, frank.obr...@amdocs.com wrote: > LF, Gildas, > We would like to split the current logging-analytics repo into > python and java. Currently the shared repo root pom.xml is causing > issues running both technologies both offline and with jobs running on > jenkins. > I would like to formally request 2 new repos. > > https://git.onap.org/logging-analytics/ > > Logging-analytics/java > Logging-analytics/python > > In the future we will likely add a "go" repo - but not until we have > some artifacts in that language. > > Thank you > /michael > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at https://www.amdocs.com/about/email-disclaimer > <https://www.amdocs.com/about/email-disclaimer> Hello Michael Please clarify the following to split the code into new repositories: 1. Do you need the git histroy preserved from the original repository, split into both the repos? 2. Can we rename the repositories as below, instead of have the repositories under separate folder `logging-analytics`? Doing this would be easier to maintain. logging-analytics-java logging-analytics-python Thanks, Anil This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer> _______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
