ESP-IDF Toolchain Integration Gitlab Expert

I am looking for a professional with extensive knowledge in selfhosted GitLabCE CI/CD, specifically in integrating the ESP-IDF toolchain. The successful candidate should have prior experience in setting up a selfhosted GitLabCE-runner, preferably with Docker. This task involves the establishment of a stable multi-version of ESP-IDF (the latest stable version and one previous version) to create a seamless CI/CD workflow. All local installations run preferably in docker containers to be reproducible also on local developer builds. You have never done a ESP-IDF CI in selfhosted GitLabCE? => stop here, you will not get the award! Key Responsibilities: - Integrate a multi-versioned ESP-IDF toolchain - Establish a selfhosted GitLabCE-runner using Docker - Ensure support for multiple targets including S3, C6, and H2 - Ensure support for multple ESP-IDF versions (see 1st req.) Desired Skills and Knowledge: - Comprehensive knowledge of the ESP-IDF toolchain - Previous experience setting up GitLab-runners - Skilled in Docker-based workflow implementation - Able to work with different ESP-IDF versions - A solid understanding of targets S3, C6 and H2 - Expert in GitLab CI/CD - preferably we use latest UBUNTU LTS for OSes on docker. The ideal candidate will have proven experience in similar projects and possess the ability to provide efficient solutions to any potential challenges that might arise during the integration process. you do not have a own selfhosted gitlabCE ? run on docker your local once [login to view URL] IMPORTANT: NO pushing of sources, or configurations and settings or project details to any public cloud (e.g. google-drive, [login to view URL], [login to view URL]) This is prohibitted MS1: - implement a selfhosted gitlab runner on our permise MS2: - implement a ESP-IDF project of your choice and build it on the new gitlab runner - you can use any ESP-IDF project for pushing to our gitlab MS3: - implement the rest of the named features (ESP multiversions and ESP multi-targets) Budget? will not be disclosed, place your best bid to get considered Payment? - you estimate in a WBS (optimistic, expected, pessimistic, where optimistic < expected < pessimistic) after getting the task - we discuss about clearances and effort - we mutually agree to effort - we assign you the task after mutually agreed - you provide us a delivery date - you implement, test and deliver - you provide also unit /integration tests to ensure code is always working - you document each required step to make interaction of systems to work - we test on our premise (you maybe help to fix issues) - we pay (basically the rules of freelancer) Closed book vs open book? We work only on open book. Closed book means you are unwilling to define a WBS for the work and you add only a price tag to the task. We are sorry we will not hire you in such a case! Deliveries? - in our on premise git (access will be granted to you) - full sources (.[login to view URL], script or markdown documents for installing gitlab runners) - libs, need prior confirm and we prefer to use mostly latest stable versions - your code is working on our end too - you may require to help us here on setup - we require, depending on availability and on complexity 2-4 weeks test time per milestone. Usually clearly less