Continuous integration in WordPress plugin development
Manner, Patric (2020)
Åbo Akademi
2020
Julkaisu on tekijänoikeussäännösten alainen. Teosta voi lukea ja tulostaa henkilökohtaista käyttöä varten. Käyttö kaupallisiin tarkoituksiin on kielletty.
Julkaisun pysyvä osoite on
http://urn.fi/URN:NBN:fi-fe2020052138577
http://urn.fi/URN:NBN:fi-fe2020052138577
Tiivistelmä
Continuous integration is an agile software development practice that enables teams
to work efficiently together. It is first and foremost a mindset, which encourages de-
velopers to integrate often to transform historically time and resource consuming soft-
ware integrations into quick and smooth tasks. Over the years, however, tools have
been developed that make the integrations even more effective. In this thesis, continu-
ous integration was introduced as a part of the development of a WordPress plugin,
Aucor Core, through a pipeline, where many of the tools, such as unit tests, integration
tests and a remote integration server, were used to enhance the process by providing
automation and fail-safes. A thorough analysis of the subject matter was done in the
context of the company producing the plugin. The analysis, then, formed the base
for the practical implementation of the pipeline. The implementation was divided into
three stages: extending the local development environment to include testing, writing
the tests for the plugin’s features and setting up a remote integration server using Travis
CI. The purpose was to reduced risks during development, increased confidence in the
plugin and favor a more active development of it.
to work efficiently together. It is first and foremost a mindset, which encourages de-
velopers to integrate often to transform historically time and resource consuming soft-
ware integrations into quick and smooth tasks. Over the years, however, tools have
been developed that make the integrations even more effective. In this thesis, continu-
ous integration was introduced as a part of the development of a WordPress plugin,
Aucor Core, through a pipeline, where many of the tools, such as unit tests, integration
tests and a remote integration server, were used to enhance the process by providing
automation and fail-safes. A thorough analysis of the subject matter was done in the
context of the company producing the plugin. The analysis, then, formed the base
for the practical implementation of the pipeline. The implementation was divided into
three stages: extending the local development environment to include testing, writing
the tests for the plugin’s features and setting up a remote integration server using Travis
CI. The purpose was to reduced risks during development, increased confidence in the
plugin and favor a more active development of it.