GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — samples-java/docker/github at main · temporalio/samples-java

Expand file tree

/

github

/
Copy path

Directory actions

More options

More options

Directory actions

More options

More options

Latest commit

 

History

History
History
/

github

/
Copy path

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Dockerfile
Dockerfile
 
 
README.md
README.md
 
 
docker-compose.yaml
docker-compose.yaml
 
 

README.md

Outline

Using Github Actions

Github action simply runs Docker containers. So it is easy to perform the same build locally that Github will do. To handle this, there are two different docker-compose files: one for Github and one for local. The Dockerfile is the same for both.

Testing the build locally

To run the build locally, start from the root folder of this repo and run the following command:

docker-compose -f docker/github/docker-compose.yaml run unit-test

Note that Github action will run basically the same commands.

Testing the build in Github Actions

Creating a PR against the main branch will trigger the Github action.

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.