Automatic tests for docker-compose

Open
  • Is something wrong?
#16 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, docker-compose, shell
Domain
ci-cd, devops

Research direction

Start by comparing the existing Travis CI tests for the Dockerfile examples with the docker-compose examples. Identify how the compose binary is downloaded and how each example can be executed during Travis runs. Done means all docker-compose examples run automatically in Travis CI.

Written by the indexing model from the issue text.

Description

Enhancement

As already said in a PR, I want to increase the automatic testing.

So I do want to add Travis CI tests for all of the docker-compose examples. Like we have for the dockerfiles examples.

Therefore I have to download and execute the docker-compose binary on-the-fly during the Travis runs :-)

Dominant language
Shell
Stars
70
Forks
27
Avg merge
1h 7m
Merged PRs (30d)
1

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from friendica/docker

All issues in friendica/docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.