Branch test

.eslintrc.js

@@ -2,11 +2,14 @@ module.exports = {
   "env": {
     "browser": true,
     "es6": true,
-    "jest/globals": true
+    "jest/globals": true,
+    "node": true
+
   },
   "extends": [
     "eslint:recommended",
-    "plugin:react/recommended"
+    "plugin:react/recommended",
+    "plugin:cypress/recommended"
   ],
   "parserOptions": {
     "ecmaFeatures": {
@@ -16,13 +19,13 @@ module.exports = {
     "sourceType": "module"
   },
   "plugins": [
-    "react", "jest"
+    "react", "jest", "cypress"
   ],
   "rules": {
     "indent": [
       "error",
-        2
-      ],
+      2
+    ],
     "linebreak-style": [
       "error",
       "unix"

.github/workflows/hello.yml

@@ -0,0 +1,22 @@
+name: Hello World!
+
+on:
+  push:
+    branches:
+      - master
+      # note that your "main" branch might be called main instead of master
+
+jobs:
+  hello_world_job:
+    runs-on: ubuntu-20.04
+    steps:
+      - name: Say hello
+        run: |
+          echo "Hello World!"
+      - name: Now it is
+        run: |
+          date
+
+      - name: Directory content
+        run: |
+          ls -l

.github/workflows/pipeline.yml

@@ -0,0 +1,67 @@
+
+  name: Deployment pipeline
+  on:
+    push:
+      branches:
+        - master
+    pull_request:
+      branches: [master]
+      types: [opened, synchronize]
+  jobs:
+    simple_deployment_pipeline:
+      runs-on: ubuntu-20.04
+      steps:
+        - uses: actions/checkout@v3
+        - uses: actions/setup-node@v3
+          with:
+            node-version: "16"
+        - name: Install dependencies
+          run: npm install
+        - name: Check style
+          run: npm run eslint
+        - name: Build
+          run: npm run build
+        - name: Test
+          run: npm test
+        - name: e2e tests
+          uses: cypress-io/github-action@v5
+          with:
+            command: npm run test:e2e
+            start: npm run start-prod
+            wait-on: http://localhost:5000
+        - name: Trigger deployment
+          if: ${{ github.event_name == 'push' }}          
+          run: curl https://api.render.com/deploy/srv-${{secrets.RENDER_SERVICE_ID}}?key=${{secrets.RENDER_API_KEY}}
+    tag_release:
+      needs: [simple_deployment_pipeline]
+      runs-on: ubuntu-20.04
+      permissions:
+        contents: write 
+      steps:
+
+        - name: Checkout Repository
+          uses: actions/checkout@v2   
+        - name: Bump version and push tag
+          if: ${{ github.event_name == 'push' }}   
+
+          uses: anothrNick/github-tag-action@8c8163ef62cf9c4677c8e800f36270af27930f42
+          env:
+            GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        - name: Notify Deployment Success
+          uses: rjstone/discord-webhook-notify@v1
+
+          if: github.event_name == 'push' &&  success()
+          with:
+            severity: info
+            text: A new version of pokedex deployed.
+            webhookUrl: ${{ secrets.DISCORD_WEBHOOK }}
+
+        - name: Notify Deployment Failure and Show Commit Info
+          uses: rjstone/discord-webhook-notify@v1 
+          if: failure()
+
+          with:
+            severity: error
+            text: Build failed!
+            webhookUrl: ${{ secrets.DISCORD_WEBHOOK }}
+

.github/workflows/schedule_healthcheck.yml

@@ -0,0 +1,19 @@
+# name: Periodic Health Check
+
+# on:
+#   schedule:
+#     - cron: '0 0 * * *' # Schedule the workflow to run every 24 hours
+
+# jobs:
+#   health_check:
+#     runs-on: ubuntu-latest
+#     steps:
+#       - name: 
+#         run : echo "This step will run on every one minute"
+#       - name: Perform Health Check
+#         uses: jtalk/url-health-check-action@v3
+#         with:
+#           url: 'https://full-stack-open-pokedex-7vtq.onrender.com'
+#           follow-redirect: false
+#           max-attempts: 3
+#           retry-delay: 5s

app.js

@@ -1,11 +1,17 @@
-const express = require("express");
-const app = express();
+/* eslint-disable no-console */
+const express = require('express')
+const app = express()
 
 // Heroku dynamically sets a port
-const PORT = process.env.PORT || 5000;
-
-app.use(express.static("dist"));
+const PORT = process.env.PORT || 5000
+app.get('/version', (req, res) => {
+  res.send('1') // change this string to ensure a new version deployed
+})
+app.get('/health', (req, res) => {
+  res.send('ok')
+})
+app.use(express.static('dist'))
 
 app.listen(PORT, () => {
-  console.log("server started on port 5000");
-});
+  console.log('server started on port 5000')
+})

cypress.config.js

@@ -0,0 +1,10 @@
+const { defineConfig } = require('cypress')
+
+module.exports = defineConfig({
+  e2e: {
+    // eslint-disable-next-line no-unused-vars
+    setupNodeEvents(on, config) {
+      // implement node event listeners here
+    },
+  },
+})

cypress/e2e/Pokedex.cy.js

@@ -0,0 +1,19 @@
+describe('Pokedex', function () {
+  it('front page can be opened', function () {
+    cy.visit('http://localhost:5000')
+    cy.contains('ivysaur')
+    cy.contains('Pokémon and Pokémon character names are trademarks of Nintendo.')
+  })
+})
+describe('Pokemon Page can be navigated to', () => {
+  it('Navigates to Ivysaur page and checks for chlorophyll ability', () => {
+    // Visit the main page
+    cy.visit('http://localhost:5000/')
+
+    // Find and click on the link for Ivysaur
+    cy.contains('ivysaur').click()
+
+    // Wait for the page to load and check for the presence of chlorophyll ability
+    cy.contains('chlorophyll')
+  })
+})

cypress/fixtures/example.json

@@ -0,0 +1,5 @@
+{
+  "name": "Using fixtures to represent data",
+  "email": "[email protected]",
+  "body": "Fixtures are a great way to mock data for responses to routes"
+}

cypress/support/commands.js

@@ -0,0 +1,25 @@
+// ***********************************************
+// This example commands.js shows you how to
+// create various custom commands and overwrite
+// existing commands.
+//
+// For more comprehensive examples of custom
+// commands please read more here:
+// https://on.cypress.io/custom-commands
+// ***********************************************
+//
+//
+// -- This is a parent command --
+// Cypress.Commands.add('login', (email, password) => { ... })
+//
+//
+// -- This is a child command --
+// Cypress.Commands.add('drag', { prevSubject: 'element'}, (subject, options) => { ... })
+//
+//
+// -- This is a dual command --
+// Cypress.Commands.add('dismiss', { prevSubject: 'optional'}, (subject, options) => { ... })
+//
+//
+// -- This will overwrite an existing command --
+// Cypress.Commands.overwrite('visit', (originalFn, url, options) => { ... })

cypress/support/e2e.js

@@ -0,0 +1,20 @@
+// ***********************************************************
+// This example support/e2e.js is processed and
+// loaded automatically before your test files.
+//
+// This is a great place to put global configuration and
+// behavior that modifies Cypress.
+//
+// You can change the location of this file or turn off
+// automatically serving support files with the
+// 'supportFile' configuration option.
+//
+// You can read more here:
+// https://on.cypress.io/configuration
+// ***********************************************************
+
+// Import commands.js using ES2015 syntax:
+import './commands'
+
+// Alternatively you can use CommonJS syntax:
+// require('./commands')

exercise1.md

@@ -0,0 +1,24 @@
+# `Exercise 1`
+
+`In a hypothetical scenario where a team of six is actively developing an application, let's consider a language like Python for the project.`
+
+## CI Steps in Python Ecosystem:
+
+1. Linting: For Python, flake8 and pylint are commonly used tools for code linting. These tools help maintain code quality by checking for style issues, errors, and potential bugs.
+   2.Testing: pytest and unittest are popular testing frameworks in Python. They allow developers to write and execute tests to ensure the application's functionality.
+2. Building: Python projects might use tools like setuptools or poetry to manage dependencies and package the application for distribution.
+
+## Alternatives to Jenkins and GitHub Actions:
+
+1. Travis CI: A cloud-based CI/CD service supporting various languages and offering ease of integration with GitHub repositories.
+2. CircleCI: Another cloud-based CI/CD platform providing flexibility in configuring pipelines and supporting Python projects among others.
+3. GitLab CI/CD: Integrated within GitLab, offering self-hosted and cloud-based options, enabling CI/CD pipelines for Python projects.
+
+## Self-hosted vs. Cloud-based CI Environment:
+
+1. Decision Factors: Considerations such as team expertise, infrastructure costs, scalability needs, and maintenance efforts.
+2. Self-hosted: Offers greater control over the CI environment, suitable for specialized requirements or strict security policies.
+3. Cloud-based: Provides ease of setup, scalability, and maintenance handled by the service provider, suitable for teams focusing on rapid development and deployment.
+
+`To decide between self-hosted or cloud-based CI, gather information on the team's expertise in managing infrastructure, budget constraints, security needs, and scalability requirements.
+A self-hosted setup might be beneficial for stringent security needs or specialized configurations, while a cloud-based environment might suit teams focusing on agility and cost-effectiveness.`