Skip to content

Update obsolete topics #460

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Watson1978 merged 1 commit into from
Jan 8, 2026
+9 −14
Merged

Update obsolete topics #460

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 9 additions & 14 deletions MAINTAINING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,10 +3,9 @@ How to use and maintain this project

All operations are automated as much as possible.

- [Travis CI][3] is used only for tests.
- Generation of each `Dockerfile` and its context is automated via `Makefile`.


- Maintain vX.Y branch for LTS
- Deploy container images via GitHub Actions (except Windows container images)

## Updating

Expand All @@ -24,12 +23,7 @@ To update versions of images following steps are required:
```bash
make src-all
```
5. If `Dockerfile`s layout was changed somehow (major version change, for
example), you should check [build triggers on Docker Hub][2] and
[Travis CI configuration](.travis.yml), modify them as required
BEFORE push to `master` branch.
6. Push changes to `master` branch.

5. Push changes to `master` branch.

### Image versioning convensions

Expand All @@ -50,9 +44,11 @@ To update versions of images following steps are required:
2. Set `DOCKER_HUB_ORGS`, `DOCKER_HUB_REPOSITORY`, `DOCKER_HUB_USERNAME` and `DOCKER_HUB_ACCESS_TOKEN` as GitHub repository secrets.
(e.g. `DOCKER_HUB_ORGS=fluent`, `DOCKER_HUB_REPOSITORY=fluentd` and so on)

3. Create tag to release it! (e.g. v1.18.0-1.0 for alpine,amd64,arm64 and armhf)
3. Create tag to release it! (e.g. v1.18.0-1.0 for amd64,arm64 and armhf)
1. If you deploy all images, tag `v<Fluentd version>-<image major version>.<image minor version>` (e.g. v1.19.1-1.0).
2. If you deploy specific architecture image, tag `v<Fluentd version>-debian-[arm64(for aarch64 image)]-<image major version>.<image minor version>` (e.g. v1.19.1-debian-arm64-1.0).

Built tags for debian and alpine images will be published at [TAGS page](https://hub.docker.com/r/fluent/fluentd/tags).
Built tags for debian images will be published at [TAGS page](https://hub.docker.com/r/fluent/fluentd/tags).

### Build and Publish Windows Server Core images

Expand Down Expand Up @@ -109,13 +105,12 @@ make release-all
```

It will build all existing `Dockerfile`s, tag them with proper tags
([as `README.md` requires][4]) and push them to Docker Hub.
([as `README.md` requires][3]) and push them to Docker Hub.





[1]: https://hub.docker.com/r/fluent/fluentd/tags
[2]: https://hub.docker.com/r/fluent/fluentd/~/settings/automated-builds
[3]: https://travis-ci.org/fluent/fluentd-docker-image
[4]: README.md#supported-tags-and-respective-dockerfile-links
[3]: README.md#supported-tags-and-respective-dockerfile-links