Re: [onap-tsc] Request to alter sdnc/oam project's history
Here are the commits with those files (multiple jar files + some tar archives): https://gerrit.onap.org/r/c/sdnc/oam/+/461 https://gerrit.onap.org/r/c/sdnc/oam/+/2913 Jess On Mon, Jul 24, 2023 at 1:09 PM wrote: > Can someone please provide the names of the files? > > > > *From:* Jessica Gonzalez > *Sent:* Monday, July 24, 2023 12:31 PM > *To:* onap-tsc ; TIMONEY, DAN ; > David McBride ; Kenny Paul < > kp...@linuxfoundation.org> > *Cc:* Matt Watkins ; Kevin Sandi < > ksa...@contractor.linuxfoundation.org> > *Subject:* Request to alter sdnc/oam project's history > > > > Dear TSC members and Dan > > > > While addressing some work on ONAP's GitHub mirror, we noticed some issues > > attempting to replicate https://github.com/onap/sdnc-oam > > > > This repo has had some history of large (100+ MB) jar artifacts being > merged back in 2017 > > which are preventing the GitHub mirror from getting replicated as these > artifacts are still present > > in the history even though they were removed a while back. > > > > > *We are requesting the TSC's permission to alter sdnc/oam by removing the > existenceof these binaries from the repo history permanently to allow the > mirror replication tohappen. This change will affect anyone with a clone of > sdnc-oam which can be resolvedby re-cloning the repo and the old history of > these artifacts will no longer exist.* > > > > Since now we have added INFO.yaml verify workflow in GitHub Actions for > all projects, having > > mirror replication issues will block new INFO.yaml changes in sdnc/oam > going forward. > > Please let us know if we can proceed with the removal of these artifacts > from history. > > > > Thank you so much! > Jess > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9374): https://lists.onap.org/g/onap-tsc/message/9374 Mute This Topic: https://lists.onap.org/mt/100336401/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-tsc] Request to alter sdnc/oam project's history
Can someone please provide the names of the files? From: Jessica Gonzalez Sent: Monday, July 24, 2023 12:31 PM To: onap-tsc ; TIMONEY, DAN ; David McBride ; Kenny Paul Cc: Matt Watkins ; Kevin Sandi Subject: Request to alter sdnc/oam project's history Dear TSC members and Dan While addressing some work on ONAP's GitHub mirror, we noticed some issues attempting to replicate https://github.com/onap/sdnc-oam This repo has had some history of large (100+ MB) jar artifacts being merged back in 2017 which are preventing the GitHub mirror from getting replicated as these artifacts are still present in the history even though they were removed a while back. We are requesting the TSC's permission to alter sdnc/oam by removing the existence of these binaries from the repo history permanently to allow the mirror replication to happen. This change will affect anyone with a clone of sdnc-oam which can be resolved by re-cloning the repo and the old history of these artifacts will no longer exist. Since now we have added INFO.yaml verify workflow in GitHub Actions for all projects, having mirror replication issues will block new INFO.yaml changes in sdnc/oam going forward. Please let us know if we can proceed with the removal of these artifacts from history. Thank you so much! Jess -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9373): https://lists.onap.org/g/onap-tsc/message/9373 Mute This Topic: https://lists.onap.org/mt/100336401/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[onap-tsc] Request to alter sdnc/oam project's history
Dear TSC members and Dan While addressing some work on ONAP's GitHub mirror, we noticed some issues attempting to replicate https://github.com/onap/sdnc-oam This repo has had some history of large (100+ MB) jar artifacts being merged back in 2017 which are preventing the GitHub mirror from getting replicated as these artifacts are still present in the history even though they were removed a while back. *We are requesting the TSC's permission to alter sdnc/oam by removing the existenceof these * *binaries from the repo history permanently to allow the mirror replication tohappen. This change will affect anyone with a clone of sdnc-oam which can be resolvedby re-cloning the repo and the old history of these artifacts will no longer exist.* Since now we have added INFO.yaml verify workflow in GitHub Actions for all projects, having mirror replication issues will block new INFO.yaml changes in sdnc/oam going forward. Please let us know if we can proceed with the removal of these artifacts from history. Thank you so much! Jess -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9372): https://lists.onap.org/g/onap-tsc/message/9372 Mute This Topic: https://lists.onap.org/mt/100336401/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
