An introduction to Gulp Build System

What is Gulp?

Just like Grunt, which is a build tool for front-end web development, Gulp is a new block that runs predefined tasks on static files such as CSS, HTML, Javascript, images. Some of these tasks includes:

  • minimise files size
  • watch file changes and automate the deployment

What is the major difference between Grunt and Gulp?

  • Grunt plug-ins often perform multiple tasks where as Gulp plug-ins are designed to do one thing only; it is clean and neat.
  • Grunt requires plug-ins for basic functionality such as file watching; Gulp has them built-in.
  • Grunt uses JSON-like data configuration files; Gulp uses leaner, simpler JavaScript code. You don’t create multiple configuration files in Gulp for each task like in Grunt.

How to use Gulp?

I have recorded a video about that explains you about:

  1. How to Install Gulp
  2. How to Install Gulp Plugins
  3. How to find Plugins
  4. How to define Gulp tasks
  5. How to execute bunch of tasks
  6. How to watch changes in static resources and execute tasks automatically.








ITIL: Change Management Process

Change Management Process


The purpose of this process is “to control the lifecycle of all changes, enabling beneficial changes to be made with minimum disruption to IT services.

  • Keep abreast of the changes that happen in the business environment.
  • Ensure that changes are recorded and evaluated, and that authorized changes are prioritized, planned, tested, implemented, documented and reviewed in a controlled manner.
  • To control the items recorded in the configuration management system (CMS).
  • Optimize risk for the business.


The scope of this process covers everything that require changes, from the architecture and infrastructure to the processes, documentation, metrics, and tools that support your services, as well as changes to IT services and configuration items.

This scope covers changes that are required to run IT Services. However, it can exclude some changes:

  • Minor operational changes that need to be done as part of day-to-day management of the infrastructure may also excluded from the change management process.
  • You don’t need to enter a change request record if you are performing troubleshooting steps to restore normal service in response to an incident.
  • Restarting a client machine not require any change request. However, if an application server requires a reboot, then the action of rebooting may have an effect on large user population and requires a change request.

Type of changes

  • Standard changes: All those changes that has a pre-authorized approach to its execution. These changes are well-known and clearly understood risk. Because the procedures are known and risk is low; there is no steering committee approval is required; refer Change Management Process.
  • Emergency Changes: This type of change is in response to or in order to prevent a business-critical error. Emergency change advisory board (ECAB) should be given same rights as Change Advisory board.
  • Normal Changes: Where the request has came through Service Desk. The Seven Rs of assessment should be followed:

Who raised the change? What is the reason for the change? What is the return required from the change? What are the risks involved in the change? What resources are required to deliver the change? Who is responsible for the build, test and implementation of the change? What is the relationship between this change and other changes?


Documents from Change Management:

The change schedule can be updated.

The projected schedule outage document can be updated.

The remediation plan should be in place to restore service back to normal; in case of change failure.