Vagrantfile #8 

Vagrant.configure(2) do |config|

  # These are old instances. 
  # Before bringing them back, reset the `vagrant` user to be `perforce` in the boxes.

  # # The build environment expects to be managed by the 'master' VM already
  # # configured.
  # config.vm.define 'build-ubuntu12' do |vagrant|
  #   vagrant.vm.hostname = 'build-ubuntu12'
  #   vagrant.vm.box = 'ubuntu-12-04-x64-vmware'
  #   vagrant.vm.box_url = 'boxes/ubuntu-12-04-x64-vmware.box'

  #   vagrant.vm.network :private_network, ip: '172.16.100.10'

  #   # Do not use a shared folder. We will fetch sources in other ways.
  #   vagrant.vm.synced_folder ".", "/vagrant", disabled: true

  #   vagrant.vm.provider 'vmware_fusion' do |v|
  #     v.gui = true
  #     v.vmx['memsize'] = '4096'
  #     v.vmx['numvcpus'] = '4'
  #   end

  #   vagrant.vm.provision :shell, path: "shell/install_build_dependencies.sh"
  #   vagrant.vm.provision :shell, path: "shell/install_perforce-server.sh"
  #   vagrant.vm.provision :shell, path: "shell/install_rvm.sh", args: "stable", privileged: false
  #   vagrant.vm.provision :shell, path: "shell/install_jdk.sh"
  #   vagrant.vm.provision :shell, path: "shell/create_ssh_key.sh", privileged: false
  # end

  # config.vm.define 'build-ubuntu14' do |vagrant|
  #   vagrant.vm.hostname = 'build-ubuntu14'
  #   vagrant.vm.box = 'ubuntu-14-04-x64-vmware'
  #   vagrant.vm.box_url = 'boxes/ubuntu-14-04-x64-vmware.box'

  #   vagrant.vm.network :private_network, ip: '172.16.100.11'

  #   # Do not use a shared folder. We will fetch sources in other ways.
  #   vagrant.vm.synced_folder ".", "/vagrant", disabled: true

  #   vagrant.vm.provider 'vmware_fusion' do |v|
  #     v.gui = true
  #     v.vmx['memsize'] = '4096'
  #     v.vmx['numvcpus'] = '4'
  #   end

  #   vagrant.vm.provision :shell, path: "shell/install_build_dependencies.sh"
  #   vagrant.vm.provision :shell, path: "shell/install_rvm.sh", args: "stable", privileged: false
  #   vagrant.vm.provision :shell, path: "shell/install_jdk.sh"
  #   vagrant.vm.provision :shell, path: "shell/create_ssh_key.sh", privileged: false
  # end

  config.vm.define 'build-centos6' do |vagrant|
    vagrant.ssh.username = 'perforce'
    vagrant.ssh.password = 'PASSWORD'

    vagrant.vm.hostname = 'build-centos6'
    vagrant.vm.box = 'centos-6-7-x64-vmware'
    vagrant.vm.box_url = 'boxes/centos-6-7-x64-vmware.box'

    vagrant.vm.network :private_network, ip: '172.16.100.12'

     # Do not use a shared folder. We will fetch sources in other ways.
    vagrant.vm.synced_folder ".", "/vagrant", disabled: true

    vagrant.vm.provider 'vmware_fusion' do |v|
      v.gui = true
      v.vmx['memsize'] = '2096'
      v.vmx['numvcpus'] = '2'
    end
    
    vagrant.vm.provision :shell, inline: 'iptables -F'
    vagrant.vm.provision :shell, path: "shell/setup-perforce-package-repo_centos6.sh"
    vagrant.vm.provision :shell, inline: 'yum update -y'
    vagrant.vm.provision :shell, path: "shell/install_build_dependencies-centos.sh"
    vagrant.vm.provision :shell, path: "shell/install_jdk-centos.sh"
    vagrant.vm.provision :shell, path: "shell/configure-nfs.sh"
    vagrant.vm.provision :shell, path: "shell/create-group_commander.sh"
    vagrant.vm.provision :shell, path: "shell/create-user_ecagent_centos6.sh"
    vagrant.vm.provision :shell, path: "shell/create-user_hwsbuild_centos6.sh"
  end

end
# Change User Description Committed
#8 19442 tjuricek Add steps to configure the p4tickets file for EC agent usage.
#7 19430 tjuricek Revise the CentOS 6.7 VM to be deployable as new infrastructure.

I seem to be running into DNS issues, which seems to be causing EC to completely ignore my host.
So this *might not* be completely ironed out.
#6 17189 tjuricek More cleanup of infrastructure no longer needed.
#5 17187 tjuricek A proposed single-machine build script

Also, a new configuration for running ubuntu14 machines locally that others can access
#4 15685 tjuricek Use GUIs for VMWare Fusion, and remove version string from installer file names.

If we show the UI for VMs launched by Vagrant, we can easily just drag and drop into vSphere. Which works quickly, actually.

We also do not want version strings in archived file names, since that makes it trickier to write scripts that just fetch these files and deploy them automatically.
#3 15661 tjuricek Add some basic email notification.

Note: the 'P4' Jenkins plugin doesn't seem to alter the workflow environment.
This means we don't really get access to the changelist we've synced.
I'm investigating, this would be nice to have.
#2 15634 tjuricek Add rules for setting up and running Centos 6.

There's a strange problem coming back around with package tests again, not everything's 100%
#1 15623 tjuricek Add infrastructure project.

This project should allow any team to setup a CD environment locally using VMWare products. A 'build' workflow will run tests, generate installers, etc, on a Jenkins instance configured with necessary plugins. A later 'release' workflow will initially push successful runs into the 'build/' directory of the branch in the workshop. (A 'production release' will use that data and push it into internal infrastructure for package signing and hosting.)

Documentation will be written. This is a large set of files, so I wanted to submit them where my connection to the workshop server is faster.