This would automate reviews for most style issues and provide instant PR feedback to contributors, as well as automate some project configuration processes in capable IDE's. (I don't have much context yet on how this runs in prod). In production waiting 30000ms for Mongo to notify that connection has failed might be too long, if we can fail faster then that might be a good thing. It's possible we'd want to apply a more aggressive timeout more generally than just the tests but that decision probably requires a bit more thought. Maybe something like test containers could help here, or even using docker-compose to wrap the test execution and spin up Mongo as a dependency. Or alternatively, and maybe preferably, change how we use Mongo in the tests so it's available before the Mongo client is created. Please let me know if you're happy for me to create a PR for this?Īs the tests are using an in memory database controlled by the tests, longer term it may be worth thinking about how we either change the Mongo connection code to occur later in the application life-cycle so the database is already available. I think as a quick win this could be a good change to improve the speed of the test run improving the feedback loop. We could probably reduce this more but that's as far as I've gone for now, thought it was worth getting some feedback first. Reactor Summary for adoptopenjdk-api-v3 3.0.0-SNAPSHOT: Update Watcher for AdoptOpenJDK - uses the API to automatically manage the JDK installations on an individual's machine.Gradle - the Gradle project defaults to use the API for its toolchains feature.AdoptOpenJDK Docker Images - the API is used during the creation of the various official & unofficial Docker images.AdoptOpenJDK Website - the API drives the release listings on the AdoptOpenJDK website allowing individuals to download the JDK distribution of their choice.The following list highlights a small subset of consumers and their use-cases: The AdoptOpenJDK API has served over 200 million downloads by a wide variety consumers, from individuals to organisations.Ĭheck the Download Statistics Dashboard for the latest numbers. The open api definition for this can be viewed at openapi.įor more information, including example queries, please look at STRUCTURE.md Who's using the AdoptOpenJDK API? The swagger documentation can be viewed at: swagger-ui. To learn more about how we build & run the API, check out CONTRIBUTING.md and the FAQs. Sign up to the mailing list where major API updates will be announced, and visit to find out more about the community. The AdoptOpenJDK API provides a way to consume JSON information about the AdoptOpenJDK releases and nightly builds. If you are using v2 please move to the latest version (documented below) as soon as possible. NOTICE: AdoptOpenJDK API v2 has been deprecated and will be removed. If you are using v1 please move to the latest version (documented below) as soon as possible. NOTICE: AdoptOpenJDK API v1 has now been removed. NOTE: This repo is now deprecated/archived as /adoptium/ runs both and using vendor properties as a filter to do the correct thing on each domain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |