My source code repo is hosted on GitHub and I'm wondering how to implement a CI/CD github actions pipeline for testing, build and deploy of my MERN application to DigitalOcean. I have admin_frontend, user_frontend, backend folders in the root. What…
I want to implement CI/CD for my application, so far I have managed to build and upload my image on docker hub with GitHub actions. Now I need a way to pull that image on my VPS and run the…
My Jest tests are passing, but Github actions workflow isn't completing. Here's my main.yaml. name: Jest Unit Tests on: push: branches: [ main ] pull_request: branches: [ main ] jobs: build: runs-on: ubuntu-latest strategy: matrix: node-version: [14.x, 16.x] mongodb-version: ['4.2',…
I am trying to connect to Postgres using docker in github actions. Here is my github actions file: name: Carbon Link backend server CI on: push: branches: [ 'develop', 'PC-3-setup-github-actions-on-pr-request' ] pull_request: branches: [ 'develop', 'PC-3-setup-github-actions-on-pr-request' ] jobs: # label…
I've recently started to learn swift and iOS development overall, since I've always been using GitHub to store my code, I decided to backup my little project there too and as I've done so, I found GitHub Actions, which immediately…
I'm trying to build my Docker image with GitHub action using the official docker/build-push-action action. The action provides secret GIT_AUTH_TOKEN for the build by default but I seem not to be able to use the token to read another private…
I would like to achieve the following CI pipeline with GitHub Actions workflow. Pull Request is merged -> GitHub action is being triggered -> docker image is being built with semantic version incremented by one or the version is based…
The step in my Docker file which reads RUN yarn install --frozen-lockfile is failing with the following error text when executed in a .github action. It reads as though there's a problem running git ls remote --tags --heads ssh://[email protected]/reach-sh/js-conflux-sdk.git which…
I'm building a new GitHub workflow (my first), which currently consists of 2 simple jobs: Build a Docker image for the Django application. Run our Django tests inside the Docker image that was just build. But I've run into a…
Here I have two workflows under a job. The only target we want to achieve is that, we want to reuse the container images by using cache or some other means. Similar way we do for node_modules jobs: build: name:…