Deployment 6 Submission

Jenkinsfile

@@ -0,0 +1,36 @@
+pipeline {
+  agent {
+    label 'agent2'
+  }
+  stages {
+    stage ('Build') {
+      steps {
+      sh 'rm -rf ./cypress2'
+      sh '''
+        npm install
+        npm run build
+        sudo npm install -g serve
+        serve -s build &
+        '''
+      }
+    }
+    stage ('Second') {
+      agent {
+        label 'agent3'
+      }
+      steps {
+      sh ''' 
+        npm install cypress
+        npm install mocha
+        npx cypress run --spec ./cypress/integration/test.spec.js
+        '''
+      }
+      post {
+        always {
+          junit 'results/cypress-report.xml'
+        }
+
+      }
+    }
+  }
+} 

README.md

@@ -1,16 +1,68 @@
-# DEPLOY6_FE
-<h1 align=center>Deployment 6</h1>
-
-Welcome to deployment 6, for this deployment you will need to follow the directions in the deployment6.pdf.    
-
-- Be sure to include the following below in your pull request: 
-
-***Requirements:*** 
-- [x]Document issues and anything you decided to do different..
-- [x]Generate a failed and passed test.
-- [x]Take a screenshots of your failed and passed test.
-- [x]Locate and upload cypress's screenshot and video of the headless browser test. 
-
-👉Link to deployment instructions: [here](https://github.com/kura-labs-org/DEPLOY6_FE/blob/main/Deployment%236.pdf)  
-
-![image](https://i.morioh.com/210507/ac11056f.webp)
+This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
+
+## Available Scripts
+
+In the project directory, you can run:
+
+### `npm start`
+
+Runs the app in the development mode.<br>
+Open [http://localhost:3000](http://localhost:3000) to view it in the browser.
+
+The page will reload if you make edits.<br>
+You will also see any lint errors in the console.
+
+### `npm test`
+
+Launches the test runner in the interactive watch mode.<br>
+See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.
+
+### `npm run build`
+
+Builds the app for production to the `build` folder.<br>
+It correctly bundles React in production mode and optimizes the build for the best performance.
+
+The build is minified and the filenames include the hashes.<br>
+Your app is ready to be deployed!
+
+See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.
+
+### `npm run eject`
+
+**Note: this is a one-way operation. Once you `eject`, you can’t go back!**
+
+If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.
+
+Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
+
+You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
+
+## Learn More
+
+You can learn more in the [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started).
+
+To learn React, check out the [React documentation](https://reactjs.org/).
+
+### Code Splitting
+
+This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
+
+### Analyzing the Bundle Size
+
+This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
+
+### Making a Progressive Web App
+
+This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
+
+### Advanced Configuration
+
+This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
+
+### Deployment
+
+This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
+
+### `npm run build` fails to minify
+
+This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify

cypress.json

@@ -0,0 +1,10 @@
+{
+  "reporter": "junit",
+  "reporterOptions": {
+    "mochaFile": "results/cypress-report.xml",
+    "toConsole": true
+  },
+  "integrationFolder":"./cypress/integration",
+   "testFiles":"**.spec.js"
+
+}

cypress/integration/test.spec.js

@@ -0,0 +1,10 @@
+describe('Heading', () => {
+    it('has the right title', () => {
+        cy.visit('http://3.86.50.174:5000/example-1')
+
+        cy.get('h1')
+            .invoke('text')
+            .should("equal", "My Awesome Web Application")
+    });
+
+});

docs.md

@@ -0,0 +1,3 @@
+# Overview
+
+When it came to having Jenkins serve our website so that we could test it, we needed to know the IP address of the node serving the website. We initially had the build step set to `any agent`. This meant that the IP could be either one of the 3 nodes we had set up. Our test stage was set so that the third node would do the testing. We knew the IP of each of our nodes, but because `any agent` was used, we didn't know until Jenkins started running, which agent would be used. A neat way to do this would be to have those IP addresses saved in some global resource table or something of that like so that Jenkins could simply refer to that table and look through the IPs. Instead, what was done, was setting the build step to be done by the second agent, and hard coding the second agent's IP address.