After a quick test: pushing to gitlab.com fails as well :-(. The error does not seem to be related to kitware specific configuration.
I think I'll abandon this approach an go for some NAS-based synchronization. -----Ursprüngliche Nachricht----- Von: Brad King <brad.k...@kitware.com> Gesendet: Freitag, 29. März 2019 14:02 An: Stuermer, Michael SP/HZA-ZSEP; CMake Developers Betreff: Re: AW: [cmake-developers] Pushing to gitlab.kitware.org from behind a ssl proxy On 3/29/19 8:51 AM, Stuermer, Michael SP/HZA-ZSEP wrote: > - pushing to kitware without 2FA fails > - pushing to kitware with 2FA fails Try using gitlab's own deployment on "gitlab.com". If that works then we can investigate differences. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
