Showing posts with label continuous delivery. Show all posts
Showing posts with label continuous delivery. Show all posts
Sunday, March 28, 2021

GitHub Actions: A first impression

›
I'm a regular user of GitHub. Recently I discovered GitHub also has a build-in CI/CD workflow solution called GitHub Actions. Curious ab...
Sunday, March 21, 2021

OWASP ZAP: A quick introduction

›
OWASP ZAP or Zed Attack Proxy is an open source dynamic application security testing ( DAST ) tool. It is available here  and has a website ...
Saturday, October 17, 2015

How to get most out of your PaaS solution

›
Many companies are starting to implement PaaS (platform as a service) solutions. There are obvious benefits such as easy patching, scaling, ...
Monday, August 24, 2015

SOA Suite 12c: Best practices for project structure and deployment

›
Efficient usage of version control has specific requirements to allow identification of versions and synchronous development on different br...
Saturday, July 11, 2015

Continuous delivery culture. Why do we do the things we do the way we do them?

›
Usually at first there is a problem to be solved. A solution is conjured and implemented. After a while, the solution is re-used and re-used...
Tuesday, December 9, 2014

Some thoughts on Continuous Delivery

›
Continuous Delivery is something a lot of companies strife for. It is a software development practice which allows quick (continuous) delive...
Saturday, April 26, 2014

Comparison of Jenkins and Hudson: Options for sharing configuration among projects

›
Continuous Delivery is a practice which follows from the principles behind the agile manifesto ( http://agilemanifesto.org/principles.html )...
Monday, March 31, 2014

The Jenkins Build and Delivery Pipeline plugins

›
Continuous Delivery (CD) is a design practice used in software development to automate and improve the process of software delivery ( http:/...