include: - ruby.ruby22 /opt/perforce: file.directory: - user: vagrant - group: vagrant - mode: 755 - makedirs: True /var/cache/omnibus: file.directory: - user: vagrant - group: vagrant - mode: 755 - makedirs: True vagrant-to-rvm: cmd.run: - name: usermod -a -G rvm vagrant - user: root require: - sls: ruby.ruby22 bundler: cmd.run: - name: gem install bundler - unless: rvm alias list | grep bundle - user: vagrant - require: - cmd: vagrant-to-rvm package-deps: pkg.installed: - pkgs: - libpq-dev bundle install: cmd.run: - name: bundle install - user: vagrant - cwd: /home/vagrant/p4ws require: - pkg: package-deps
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#6 | 13972 | tjuricek |
Removing old microservice implementations. The system is now mostly a monolith. Eventually there will be a websocket service. |
||
#5 | 13788 | tjuricek | Altering the bundler version on the buildmaster and build environments and adding new pillars to select the 'run as' user for RVM | ||
#4 | 13707 | tjuricek |
Infrastructure for including a "project management" React application. This attempts to create a fairly simple installer that creates a 'static' folder based on ui/static that gets hosted by the nginx front end. Right now, it's the only app, so the default page is this application. It was called "pws2" during a prototyping phase. Another prototype, "pws" and the related "project" module, is removed since that was a Sinatra-based approach that will be much more difficult to integrate into anything else. I'm running into a couple of issues with notifications setup, it's still not 100%, so I'm disabling this for now from the default 'god' configuration. (The service isn't 100% functional yet, anyway.) |
||
#3 | 13519 | tjuricek |
Added a 'buildmaster' environment. The 'buildmaster' sets up Ruby locally for doing some work via Rake. Additional steps are now being figured out in the README.md, which may end up being a bash script that executes on the master. |
||
#2 | 13518 | tjuricek | Revised the 'build' environment to not hard-code the vagrant user, and not assume we have the p4ws tree available for state.highstate. | ||
#1 | 13517 | tjuricek |
Revised Salt hierarchy to allow for CD clustering. Now, there are two main salt environments: 'build' and 'eval'. The 'eval' environment can be configured for testing or development by setting the Grain 'dev_pillar: True' or 'test_pillar: True'. The test modes may need a bit more effort to figure out exactly where I'll put the .deb files. The dev box passes p4_web_api tests. |