first commit

Author: DeepOchhane

.github/workflows/first-actions.yml

@@ -0,0 +1,28 @@
+name: My First GitHub Actions
+
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        python-version: [3.8, 3.9]
+
+    steps:
+    - uses: actions/checkout@v3
+    - name: Set up Python
+      uses: actions/setup-python@v2
+      with:
+        python-version: ${{ matrix.python-version }}
+
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install pytest
+
+    - name: Run tests
+      run: |
+        cd src
+        python -m pytest addition.py

README.md

@@ -0,0 +1,20 @@
+# GitHub-Actions-Zero-to-Hero
+Repository to kick start your journey with GitHub Actions
+
+## Comparing with Jenkins 
+
+### Advantages of GitHub Actions over Jenkins
+
+- Hosting: Jenkins is self-hosted, meaning it requires its own server to run, while GitHub Actions is hosted by GitHub and runs directly in your GitHub repository.
+
+- User interface: Jenkins has a complex and sophisticated user interface, while GitHub Actions has a more streamlined and user-friendly interface that is better suited for simple to moderate automation tasks.
+
+- Cost: Jenkins can be expensive to run and maintain, especially for organizations with large and complex automation needs. GitHub Actions, on the other hand, is free for open-source projects and has a tiered pricing model for private repositories, making it more accessible to smaller organizations and individual developers.
+
+### Advantages of Jenkins over GitHub Actions
+
+- Integration: Jenkins can integrate with a wide range of tools and services, but GitHub Actions is tightly integrated with the GitHub platform, making it easier to automate tasks related to your GitHub workflow.
+
+In conclusion, Jenkins is better suited for complex and large-scale automation tasks, while GitHub Actions is a more cost-effective and user-friendly solution for simple to moderate automation needs.
+
+

examples/deploy-java-with-maven-sonar-k8s.yml

@@ -0,0 +1,50 @@
+name: End to End CI/CD workflow for Java Applicaton with Maven, Sonar and k8s Intergation
+
+on:
+  push:
+    branches:
+      - main
+
+env:
+  KUBECONFIG: ${{ secrets.KUBECONFIG }}
+  SONAR_TOKEN: ${{ secrets.SONAR_TKN }}
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v2
+
+    - name: Java jdk setup
+      uses: actions/setup-java@v1
+      with:
+        java-version: 12
+
+    - name: maven target # change accordingly
+      run: mvn clean install
+
+    - name: Perform analysis on Sonar Qube
+      uses: sonarsource/sonarcloud-github-action@v1
+      with:
+        sonarcloud.organization: <name of your org>
+        sonarcloud.projectKey: <key>
+        sonarcloud.projectName: <name>
+        sonarcloud.token: ${{ env.SONAR_TKN }}
+        sonarcloud.scannerVersion: "4.2.0.1873"
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v2
+
+    - name: Deploy to k8s
+      uses: stefanzweifel/k8s-action@v2.0.0
+      with:
+        args: apply -f kubernetes/
+      env:
+        KUBECONFIG: ${{ env.KUBECONFIG }}

examples/deploy-to-k8s.yml

@@ -0,0 +1,29 @@
+name: Deploy to k8s
+
+on:
+  push:
+    branches:
+      - main
+
+env:
+  KUBECONFIG: ${{ secrets.KUBECONFIG }}
+
+jobs:
+  deploy:
+    runs-on: kubernetes
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v2
+
+    - name: Create Docker Image
+      uses: docker/build-push-action@v2
+      with:
+        context: .
+        push: true
+
+    - name: Deploy to k8s
+      uses: appleboy/kubectl-action@v1.0.0
+      with:
+        args: apply -f deployment.yaml
+        env:
+          KUBECONFIG: ${{ env.KUBECONFIG }}

examples/deploy-to-swarm.yml

@@ -0,0 +1,36 @@
+name: Deploy to Swarm (Docker Swarm)
+
+on:
+  push:
+    branches:
+      - main
+
+env:
+  DOCKER_HOST: tcp://<ip-address-of-your-swarm-manager>:2376
+  DOCKER_REGISTRY_USER: <username>
+  DOCKER_REGISTRY_PASS: ${{ secrets.DOCKER_REGISTRY_PASS }}
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v2
+
+    - name: Create Docker Image
+      uses: docker/build-push-action@v2
+      with:
+        context: .
+        push: true
+        tags: <registry-username>/<image-name>:${{ env.GITHUB_SHA }}
+        username: ${{ env.DOCKER_REGISTRY_USER }}
+        password: ${{ env.DOCKER_REGISTRY_PASS }}
+
+    - name: Deploy to swarm
+      run: |
+        echo "$DOCKER_REGISTRY_PASS" | docker login --username "$DOCKER_REGISTRY_USER" --password-stdin
+        docker stack deploy -c stack.yaml <stack-name>
+      env:
+        DOCKER_HOST: ${{ env.DOCKER_HOST }}
+        DOCKER_TLS_CERTDIR: "/certs"

src/addition.py

@@ -0,0 +1,8 @@
+# app.py
+# This is a test commit
+def add(a, b):
+    return a + b
+
+def test_add():
+    assert add(1, 2) == 3
+    assert add(1, -1) == 0