[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cbi-dev] Building maven artifacts for Eclipse SUMO
|
We cannot run the containers as root for security reasons. If you want to add additional tools, you need to define your own image, push it to some registry (e.g. docker hub or quay.io) and use it instead of the stock ubuntu image.
Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation 🐦 @mikbarbero
Thank you – I tried and with your help, we are now able to clone the repository. I was also able to use ubuntu:20.04 as a custom image. My next move was to install the compiler tools (apt-get update && apt-get install cmake gcc …). Unfortunately, that fails with: [Pipeline] sh + apt-get update Reading package lists... E: List directory /var/lib/apt/lists/partial is missing. - Acquire (13: Permission denied) [Pipeline] } I read that you are running the docker images without root privileges – how can we install the compilers and necessary libraries to the stock ubuntu image? Thanks for any pointers, Robert Hi Robert, see my answers inline. the Eclipse SUMO project is currently hosted on GitHub, based on C++ and built with GitHub actions & cmake. As part of our build process, we also create jars (java-bindings for an interface to SUMO – see: https://github.com/orgs/eclipse/packages?repo_name=sumo), which we would like to make publicly available for maven builds. Unfortunately, GitHub Packages require an access token to consume maven artifacts which is a show stopper for other projects relying on our packages. Therefore, we decided to use the Eclipse infrastructure and opened a bug to havehttps://repo.eclipse.org/content/repositories/sumo/ created for us. So far so good … Unfortunately, we cannot push the artifacts from the GitHub actions build tohttp://repo.eclipse.org, because upload from external sources is currently not possible. Therefore, our only options seems to be to also build SUMO on Jenkins (in addition to the GitHub actions) and to publish the artifacts from the Jenkins build. - Is our approach ok? Is there a better way to achieve our goal?
This approach is perfectly fine.
-
- How can we successfully clone the repo in the container infrastructure? Yes – the repo of SUMO has grown to a repo size of 750MB over the years …
-
- How can we use an ubuntu image with cmake and gcc to build SUMO (instead of maven:alpine)?
-
- How can we configure the infrastructure to trigger the Jenkins build based on tagged commits to the GitHub Repository master branch only?
Manager — Release Engineering and Technology | Eclipse Foundation _______________________________________________cbi-dev mailing listcbi-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cbi-dev
|
Attachment:
signature.asc
Description: Message signed with OpenPGP