Dear Apache ResilientDB (Incubating) Community, I hope this message finds you well. I’m excited to inform you about the latest Continuous Integration and Continuous Deployment (CI/CD) changes we’ve implemented across several ResilientDB projects. These enhancements aim to streamline our development workflows, ensure code quality, and keep our packages and documentation up-to-date.
*1. ResContract* • *npm-publish Workflow* - Automatically pushes the latest changes to the npm package whenever a pull request is updated. *• Test Workflow* - Installs all dependencies and runs sanity tests on the CLI tool to ensure functionality and stability. *2. Smart-Contracts-GraphQL* *• Test Workflow* - Performs comprehensive tests on the server after installation to verify that all components work correctly following any changes. *3. ResDB-ORM* *• Test-Publish Workflow* - Executes predefined tests on the resdb_orm Python package. - Only publishes the package to PyPi if all tests pass successfully, ensuring reliability for end-users. *4. ResilientDB Quickstart* • *Build-Deploy Workflow* - Runs the update_contributor script to refresh the list of ResilientDB contributors, commits these changes, and displays them on the website. - Executes the fetch_readmes script to collect README files from various ResilientEcosystem applications, incorporating them into the repository and website. - Deploys the updated documentation to the Quickstart website using GitHub Pages, making the latest information readily available. To complement this update, I recently presented and demonstrated some of these features in a video titled “Enhancing Usability and Accessibility in ResilientDB <https://www.youtube.com/watch?v=-G2AhZB7qCE&ab_channel=ExpoLabatUCDavis>”. I encourage you to watch the presentation to get a deeper understanding of the recent improvements and their impact on our workflows. These CI/CD updates are part of our ongoing efforts to enhance collaboration and efficiency within our community. By automating these processes, we aim to reduce manual overhead and minimize the potential for errors, allowing us all to focus more on innovation and development. Your feedback is invaluable. If you have any questions, suggestions, or run into any issues with these new workflows, please don’t hesitate to reach out. Thank you for your continued contributions to the ResilientDB project. Best regards, Gopal Nambiar
