2019-02-09 Geb and Spock Workshop 18 Meeting notes

• Added Bob's email to Geb and Spock workshop invitations.

• Using IntelliJ Idea, created Geb and Spock tests that ran in a local browser.

• Checked the automated tests into the tssgTech git repository

• Refactored the automated tests to be data driven.

• Configured the automated tests to utilize our Selenium Grid of browser nodes.

• Created a Jenkins project that runs the automated tests using our Selenium Grid.

• Created a Jenkins project to deploy the source to the Dev environment (tssgTechMultipage endpoint).

• Created a git server post-receive hook that triggers the Jenkins build and deployment to the Dev environment.

• Configured the Jenkins automated tests to automatically run after the source is successfully deployed to the Dev environment.

Create a Jenkins project to deploy the QA environment to tssgTechStagedMaster

• Deployment will be triggered manually when needed.
• Disabled the 5 minute cron job that was running in root@s14

Upgrade the servers' OS

s14

• sys.upgrade
• sudo reboot now
• technologynursery.start
• Verify no containers have exited recently

  docker ps -a | grep Exit

a13

• sys.upgrade
• sudo reboot now
• jira.start
• Verify no containers have exited recently

  docker ps -a | grep Exit

h3

• sys.upgrade
• sudo reboot now
• Verify no containers have exited recently

  docker ps -a | grep Exit

Verify services are running

technologynursery.org

confluence.technologynursery.org  

jira.technologynursery.org

jira.nejug.technologynursery.org

jira.web.technologynursery.org

jira.mobile.technologynursery.org

jenkins.technologynursery.org

• Verify project deploy to dev

  Noticed that build fails due to pre-requisite tools not installed.

• Added a script to /var/jenkins_home/bin that installs the necessary tools.
• In s14:bin/technologynursery.start: Triggered the tools installation into ncjenkins after the container starts.
• Verified that project deploys to dev successfully.