Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
<!-- Thanks for the contribution, this is awesome. --> # PR Details ## Description This PR removes CircleCI workflow configurations for automated release and arm image builds and replaces them with github actions. We now have 5 workflows: 1. build_php_docker_image: Builds and pushes docker image for php in arm and amd architectures. Runs on develop, master,release candidates and on pushed tags 2. build_port_drayage_docker_image: Builds and pushed docker image for port drayage webservice in arm and amd architectures .Runs on develop, master,release candidates and on pushed tags 3. build_v2xhub_docker_image: Builds and pushed docker image for v2xhub in arm and amd architectures .Runs on develop, master,release candidates and on pushed tags 4. pull_request: Builds all docker images in arm and amd (no push) architectures. Runs only on pull requests 5. sonar_scanner: Builds source code, runs unit tests and runs static analysis (sonar scanner) and pushes results. Runs on develop, master and on all open PRs. <!--- Describe your changes in detail --> ## Related Issue VH-1278 <!--- This project only accepts pull requests related to open issues --> <!--- If suggesting a new feature or change, please discuss it in an issue first --> <!--- If fixing a bug, there should be an issue describing it with steps to reproduce --> <!--- Please link to the issue here: --> ## Motivation and Context Remove CircleCI and use platform/architecture for docker images <!--- Why is this change required? What problem does it solve? --> ## How Has This Been Tested? @jwilliammartin Could you test the following on ARM devices. docker compose pull and run new images. Ensure no docker images crash on both V2X-Hub and Port Drayage web UI are accessible. <!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. --> ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Defect fix (non-breaking change that fixes an issue) - [x] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that cause existing functionality to change) ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I have added any new packages to the sonar-scanner.properties file - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [x] I have read the **CONTRIBUTING** document. [V2XHUB Contributing Guide](https://github.com/usdot-fhwa-OPS/V2X-Hub/blob/develop/Contributing.md) - [ ] I have added tests to cover my changes. - [ ] All new and existing tests passed.
- Loading branch information