Closed mitsudome-r closed 1 year ago
This pull request has been automatically marked as stale because it has not had recent activity.
@kasperornmeck My understanding is that Ito-san was able to confirm that Autoware Universe can be run in multiple (monolithic) containers orchestrated by K3s, so for CI/CD what's the next step?
@LalithVipulananthan When this issue was created, the idea wasn't to run a single container multiple times. We now know that this is a more difficult task than expected. I don't know if the TSC has made a decision how to proceed, i.e., if we wish to use Bloom to release ROS packages, see https://docs.google.com/presentation/d/1ICa6bl1q38jR9peueNOL0ycyT16U9M4RKD-pM-pLbGU/edit?usp=sharing.
Setting to "Blocked" until there's a decision from the TSC regarding the Autoware release proposal mentioned in Kasper's comment above.
This pull request has been automatically marked as stale because it has not had recent activity.
@BonoloAWF - I suggest we close this issue as it won't go anywhere and the issues this issue tries to solve is addressed in the DevOps Dojos.
Description
Github based CI/CD that is hosted on AWS. This is a followup of: https://gitlab.com/autowarefoundation/autoware.auto/AutowareAuto/-/issues/1353 proposed for after the initial 1.0.0 release.
Purpose
Cloud based continuous integration and deployment (see the discussion topics proposed by Kasper and Tanzawa from ASWG Meeting https://gitlab.com/autowarefoundation/autoware-foundation/-/issues/166)
Step 2 and step 3 require configuration changes in the CI/CD which must be designed and implemented in Github.
Desired Behavior
CI/CD pipeline for Autoware.Auto running in AWS
Definition of Done