-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI #2
Comments
I'd need you to provide this. I'm not familiar with Azure Pipelines. Also, CI is expensive with Yocto. A minimal incremental build can easily take 15 minutes - a full build anywhere from 30 minutes to several hours. |
At a minimum your main build script would look something like
This won't build a complete image, so it will be faster than a full build, but it will start off by compiling the compiler and everything that needs. You'd need to add anything else that Azure Pipelines needs. |
And, of course, you really need to do the above script for each of the supported Yocto releases (rocko, sumo, thud and at some point warrior) |
Also, the CI server needs the following packages installed
We usually build within a container to make things easier. |
Yes, our team can help with getting this set up. It could be from a different service but we have some experience with Azure and it's pretty flexible and integrates well with GitHub.
If we can get it in the 30-90 minute range we should be OK. Here's an OpenDDS example: |
Created and merged pull request 17 to implement CI step of running yocto-check-layer |
Add script for Azure Pipelines CI (or similar) to validate the build.
The text was updated successfully, but these errors were encountered: