gradlew testClasses.Īs I described in this Twitter thread, I immediately encountered a Gradle issue that broke the build.Ī plugin from the eventuate-plugins-gradle project that ran a Git command failed to determine the current branch. Part 11 - The Eventuate Tram Customers and Orders example now runs on Arm/M1 MacBook!!Īfter running git clone on my M1 MacBook, I ran.Part 10 - Publishing a multi-architecture Docker image for the Eventuate CDC service.Part 9 - Publishing multi-architecture base images for services.Part 8 - Building a multi-architecture Docker image for Apache Kafka.Part 7 - Configuring CircleCI to build, test and publish multi-architecture images for Eventuate Common.Part 5 - Configuring CircleCI to publish a multi-architecture Docker image.Part 4 - Testing an Intel and Arm multi-architecture Docker image on CircleCI.Part 3 - Configuring a CircleCI-based pipeline to build multi-architecture Docker images.Part 2 - Building multi-architecture Docker images for Intel and ARM.Part 1 - My Apple M1 MacBook: lots of cores, memory and crashing containers.Later posts describe how I changed this project to build and publish multi-architecture images. Specifically, I describe how I was able to build a MySQL image and run the related tests. This post describes my experiences developing Eventuate Common on my M1/Arm MacBook. These libraries and images are used by the Eventuate examples including the Tram Customers and Orders example application I described in my first post on this topic. It’s a Gradle project that publishes some foundational Java libraries and some Eventuate-flavored Docker images for Zookeeper, MySQL, Postgres and SQL server. Developing the Eventuate Common library on an M1/Arm MacBookĪfter enhancing the microservicesio/plantuml project to publish a multi-architecture Docker image for Intel and Arm, I moved on to the eventuate-common project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |