Many developers think Bower is no longer necessary since we are able to download the same packages via NodeJs and I partially agree with them (especially when we install Bower via NPM), but that is another story and I am sure it would be an interesting topic to debate. Bowerīower is a front-end package manager.
In our case, we used NodeJs to install Bower, Gulp and other useful libraries to help us with the automation of CSS and JS related tasks. NodeJs lets us manage and install a great number of packages via its node package manager, NPM. It is also available from their site and the installation is quite simple too. This will ensure that git commands are available in the console window. You only need to make sure to check the option "Run Git from the Windows command prompt". The installation is quite easy and straightforward. It is directly available from the git website. Setupįirst of all, I had to install a series of tools on our build server so they can be used by TeamCity during the build process. In this article, I will start from the basis that this is all up and running on our local solution and explain the steps I had to follow to integrate our automatic front-end tasks with TeamCity. We decided to use Bower to manage our client components, and Gulp as our automation tool for our front-end tasks such us CSS and JS minification. Recently, we decided to make full use of task automation for a project and incorporate a task runner in our build process. We use it on our development server, deploying to a test website and creating a publish package for the live environment. It allows us to run a series of build steps, ensure the code compiles and deploy the website. TeamCity, Gulp, NodeJS, Bower, Continuous IntegrationĪt Vizioz we use TeamCity as our continuous integration server for our development projects.
0 kommentar(er)
