| Name | Modified | Size |
|---|---|---|
| .. | ||
| configure-nfs.sh | 9 years ago | 401 B |
| create-group_commander.sh | 9 years ago | 81 B |
| create-user_ecagent_centos6.sh | 9 years ago | 90 B |
| create-user_hwsbuild_centos6.sh | 9 years ago | 762 B |
| install_build_dependencies-centos.sh | 9 years ago | 217 B |
| install_build_dependencies.sh | 9 years ago | 180 B |
| install_jdk-centos.sh | 9 years ago | 61 B |
| install_jdk.sh | 10 years ago | 53 B |
| install_jenkins.sh | 10 years ago | 3 KB |
| install_nginx.sh | 10 years ago | 880 B |
| install_perforce-server_ubuntu.sh | 9 years ago | 723 B |
| install_ruby.sh | 10 years ago | 142 B |
| install_rvm.sh | 9 years ago | 266 B |
| install_rvm_jenkins.sh | 10 years ago | 546 B |
| setup-perforce-package-repo_centos6.sh | 9 years ago | 290 B |
| set_omnibus_perms.sh | 10 years ago | 125 B |
| update.sh | 10 years ago | 25 B |
| Change | User | Description | Committed |
|---|---|---|---|
| 19442 | tjuricek | Add steps to configure the p4tickets file for EC agent usage. | 9 years ago |
| 19430 | tjuricek | Revise the CentOS 6.7 VM to be deployable as new infrastructure. I seem to be running i...nto DNS issues, which seems to be causing EC to completely ignore my host. So this *might not* be completely ironed out. « |
9 years ago |
| 17189 | tjuricek | More cleanup of infrastructure no longer needed. | 9 years ago |
| 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. « |
10 years ago |
| 15634 | tjuricek | Add rules for setting up and running Centos 6. There's a strange problem coming back ar...ound with package tests again, not everything's 100% « |
10 years ago |
| 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. « |
10 years ago |