Search the Community
Showing results for tags 'continous integration'.
Found 1 result
-
I'm using GitLab CI for continuous integration right now. Other people might use something like Travis CI. For the frontend part things are pretty easy: image: node:6.10.3 cache: paths: - node_modules/ build: script: - npm install - node_modules/.bin/gulp build Now I could extend my setup to run tests or whatever I want. It just works. In this post I'm not interested into finding out how I could go about testing and stuff. I just want to know how I could accomplish the equivalent to the above setup task for ProcessWire. It doesn't seem to be too easy to me since the installation process is running in the browser asking you a lot of stuff. How could I go about it using the CLI? That's what I currently have: git clone git@github.com:processwire/processwire.git cd processwire mv site-blank site rm .gitignore git submodule add -b develop git@gitlab.local:path/to/MyModule.git site/modules/MyModule From here on I'm stuck. The only possible solution I see is maintaining a super repository including a database dump that has it's module dependencies defined in a .gitmodules file. This could then be installed using: git clone --recursive git@... Once that's completed all that needs to be done would be to create the database using the dump. Probably that's a pretty solid solution but it adds the overhead of having to maintain an additional repository + database dump. I'm trying to find an alternative that's using the original processwire repository. That way I could just rerun my build once a new version get's merged into master and see if everything would be still working as well. I'm looking forward to your replies. Thanks!
