3 ms·
I could integrate my entire workflow with Jenkins and custom parameters and custom development of console applications ( creating automated versions of packages
by NicoJuicy 11y ago
I could integrate my entire workflow with Jenkins and custom parameters and custom development of console applications ( creating automated versions of packages ( npm / nuget / .. ), mostly with the use of the "build number")
It handles 3 situations:
- local ( not included in Jenkins, but is automated within the development tools -- eg. Visual Studio. It uses local databases and local paths)
- development
- beta
- live / production
So my entire workflow is automated now, the merging of branches and etc. is done by the developer. Testing is automated ( unit tests) ... Deploying is just a matter of minutes instead of 1,5 hours. And best of all, all related packages are updated automaticly with the correct tag ( development, beta, ..)
Another way would be using TeamCity ( instead of Jenkins)
- aalhour 11y agoThanks for writing this. We use Python virtual environments to make every app's dependencies in one place and not installed globally. Also, the frontend dependencies and code compilation is handled with npm, Gulp and Bower. The thing is the developer has to issue all these commands in order to "setup" the app locally and be able to run and troubleshoot it before doing actual work, and this is universal for all apps. Same thing goes for setting up apps on staging and production other than the pull-requests and branches-merging tasks which are all manual. And if a new developer comes in, they will have to install and configure their workstation before doing any actual manual setup which is also an overhead. This scenario would also happen if a developer comes back from a long holiday. Any ideas on this?