Yesterday I migrate my project from TravisCI to Github Actions, with all other code untouched, but never passed then. The cause is that, docker-compose exec -T container command unexpectly echo the exit code of command to its stderr, messing my code detecting the stderr. Here I made a simple repo with only two files to ..
Tag : github-actions
I would like prepare my old project to work wiith separate environments, e.g. for Development, Staging and Productions. I would like hear about your experience or listen your suggestion. Project is hosted on Github and CI/CD will be running by Github Actions. I would like prepare 3 stages: development: used by developers on own local ..
I want to run docker containers on Google Cloud Run that act as GitHub Self Hosted Runners, but I’m having problems when deploying the container to CloudRun as it complaining about the port. The error is like: Container failed to start. Failed to start and then listen on the port defined by the PORT environment ..
I have setup a kubernetes cluster on AWS using kops. I am trying to automate deployment with github actions. name: Build and Deploy on: push: branches: – develop jobs: build_docker_image: – uses: actions/[email protected] – name: Build the tagged Docker image run: docker build –target dev -t org/customer-service-backend:la push_docker_image_to_github-packages: – uses: docker/[email protected] with: username: ${{ github.actor ..
I’m trying to use GitHub actions to build and deploy my Java app to an EC2 instance using CodeDeploy. There are 7 steps in my yml file. All but the last step which uses sourcetoad/[email protected] to upload to S3 keeps failing. GitHub Actions doesn’t state the reason why the step fails, so after spending some ..
I have built a docker image that when run, it registers itself as a GitHub Runner. This runner will, amongst other things, be used to build and push images to GitHub Container Registry. I don’t want to deploy the containers to GKE or Compute, as I don’t want the overhead of managing those resources. I ..
I’m working on a Spring Boot application that should be packaged into a OCI container using Cloud Native Build Packs / Paketo.io. I build it with GitHub Actions, where my workflow build.yml looks like this: name: build on: [push] jobs: build-with-paketo-push-2-dockerhub: runs-on: ubuntu-latest steps: – uses: actions/[email protected] – name: Login to DockerHub Container Registry run: ..
I’m working on a Spring Boot application that should be packaged into a OCI container using Cloud Native Build Packs / Paketo.io. I build it with GitHub Actions, where my workflow build.yml looks like this: name: build on: [push] jobs: build-with-paketo-push-2-dockerhub: runs-on: ubuntu-latest steps: – uses: actions/[email protected] – name: Login to DockerHub Container Registry run: ..

I would like to know why its taking so long to deploy a container image using the official Azure Function GitHub Action when its basically just downloading the image from the registry. The deployment takes twice as long as my build. This is what my GitHub workflow looks like. I am just building the Spring ..
Problem I have a multistage (two stages) docker build for my container, lets name it cont, that I want so automate via GitHub Actions. The first stage/docker-image of the build-process does seldomly change and takes very long to build; lets call this cont-build. I want to to reduce build duration by not building cont-build every ..