recentpopularlog in

ci

« earlier   
peaceiris/actions-hugo: GitHub Actions for Hugo ⚡️ Setup Hugo quickly and build your site fast. Hugo extended and Hugo Modules are supported.
GitHub Actions for Hugo ⚡️ Setup Hugo quickly and build your site fast. Hugo extended and Hugo Modules are supported. - peaceiris/actions-hugo
github  hugo  actions  integration  continuous  ci 
22 hours ago by jschoolcraft
How to Design Services for Continuous Deployment: 3 Best Practices - CircleCI
Any service that we run in production might be terminated at any time, and the danger is that a service might consume a message from a message queue, and be shut down before it has a chance to take the required action. This has the same effect as the message being lost. To account for this, we defer acknowledging the receipt of messages until we have performed the required action.

In the case of running a build, this means that we dequeue a message, create a record in a database to represent the build, and then acknowledge receipt of the message. The danger now is that the service might be terminated after creating the record in the database, but before acknowledging the message. If this occurs, RabbitMQ will re-enqueue the message and attempt delivery again, to a different consumer of the queue.

We use the following patterns when consuming from RabbitMQ:

1. We make sure that all exchanges and queues are declared as durable and we disable auto-delete.
2. We ensure that messages as marked as persistent.
3. We disable auto-acknowledgement of messages in our queue consumers, and instead opt to manually ack or nack messages.
4. We add a unique ID or idempotency key to messages, so that the consumer can de-dupe messages where required.
5. Passing the responsibility for de-duping messages as far downstream as possible keeps our services as simple as possible.
rabbitmq  circleci  ci  kubernetes  k8s  architecture  idempotency  microservices 
2 days ago by hellsten
An Unintentionally Comprehensive Introduction to GitHub Actions CI
We're currently approaching GitHub Actions v2 shipping publicly for everyone to use. I'm personally super excited about this because it means I don't need to configure an external service to run my CI – I can slap in some YAML, and I'm off with a cross-platform (!) CI system with multiple versions of Node.js installed.
github  actions  ci  tutorials 
2 days ago by spaceninja
Dapr - Portable, event-driven, serverless runtime.
A portable, event-driven runtime that makes it easy for developers to build resilient, microservice stateless and stateful applications that run on the cloud and edge and embraces the diversity of languages and developer frameworks. By Microsoft.
Kubernetes  event-driven  deployment  automation  microservices  build  ci  opensource 
5 days ago by liqweed

Copy this bookmark:





to read