You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use Gitlab-api to push incoming mmd-files. In this way, we may not need the file distributor which requires a local copy of the mmd-xml archive, and pushing of an updated copy at regular intervals (currently 1 hour).
The text was updated successfully, but these errors were encountered:
Is it correct that this was done because the local folder got full? Now we have another problem that commits take very long time - up to an hour to finish (40 minutes between 213d9f73 and 7705b10c for 4 new files). That apparently hampers the ability to merge in MRs. Two MRs (https://gitlab.met.no/mmd/mmd-xml-dev/-/merge_requests/21, and https://gitlab.met.no/mmd/mmd-xml-dev/-/merge_requests/23) are not possible to merge (on 19th January 2024). After pushing the merge button they just return to "ready to merge". Maybe better to revert to the old setup and make a large volume then..?
The problem was not only local storage, but how the git-pusher handled interruptions in the increasingly slow indexing of the whole archive everytime we wanted to push. This was to be solved by removing the slow indexing.
mortenwh
changed the title
Use Gitlab-api to push incoming mmd-files, instead of having a local copy of the mmd-xml archive and pushing an updated copy
Create a git distributor in dmci
Jan 25, 2024
Use Gitlab-api to push incoming mmd-files. In this way, we may not need the file distributor which requires a local copy of the mmd-xml archive, and pushing of an updated copy at regular intervals (currently 1 hour).
The text was updated successfully, but these errors were encountered: