Publish built test images for each new PR

Open
#1,893 3 comments 0 reactions 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, python
Domain
ci-cd, devops, release

Research direction

Start by tracing the repository's current flow for building and publishing official Docker containers, then compare how master changes and releases are handled. Done means pull requests produce usable testing images for feedback while release versions continue to produce the official release images.

Written by the indexing model from the issue text.

Description

enhancement

Currently the master repository is pushing out any changes to the official docker containers, however no real testing is being done in the wild and these are decoupled from the official releases.

I propose we change the flow that a PR to the master builds a testing container, which people can use to give feedback. Then when releases are released, the release versions are built.

Dominant language
Python
Stars
6.5k
Forks
1.3k
Avg merge
5d 6h
Merged PRs (30d)
4

Contributor guide

Open the 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 OpenDroneMap/ODM

All issues in OpenDroneMap/ODM

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.