[
https://issues.apache.org/jira/browse/SOLR-15321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Houston Putman resolved SOLR-15321.
-----------------------------------
Resolution: Implemented
Ok I have an almost-fully automated setup working now! (only manual step is
done through the release wizard)
Basically after a release vote succeeds, the ReleaseWizard has a step to
create/update the released Dockerfile in https://github.com/apache/solr-docker.
It won't create a PR, it will merely commit to main (after the release manager
inspects the changes) and push.
The repo has a GitHub Action workflow that is triggered on any pushes to
{{main}}, but only on paths that would affect the official-images repo (like
Dockerfiles, generate-stack-brew.sh, etc). So when the release manager makes
this push, the GitHub Action workflow is triggered to automatically create a PR
to update the docker-library/official-images entry for Solr. It will tag the
necessary approvers, and the DockerHub team will merge whenever they see fit.
This PR branch lives in the docker-solr/official-images fork, since ASF infra
does not support forks in the apache/ organization.
You can see an example of this automated PR here:
https://github.com/docker-solr/official-images/pull/5
Note: In order for the GitHub workflow in the apache/solr-docker repo to have
write access to the docker-solr/official-images repository, we are using the
dockersolrbuild user account in Github. I created a Personal Access Token and
emailed root @ apache to have this token added as a GitHub Action Secret in the
apache/solr-docker repository. You can see it being used in the Github Actions
Workflow with the name {{DOCKER_SOLR_BUILD_PAT}}.
End result: Release Managers won't have to know anything about the official
images docker process to do the release!
> Flesh out process for managing/storing "official" Dockerfiles used by
> docker-library
> ------------------------------------------------------------------------------------
>
> Key: SOLR-15321
> URL: https://issues.apache.org/jira/browse/SOLR-15321
> Project: Solr
> Issue Type: Sub-task
> Components: Docker
> Reporter: Chris M. Hostetter
> Assignee: Houston Putman
> Priority: Blocker
> Fix For: 9.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Assuming we (the Apache Solr TLP) do want to be the maintainer of "official"
> {{_/solr}} docker images moving forward, we need to flesh out how/where
> exactly we plan on storing/managing/maintaining the Dockerfiles that should
> be pointed to by the docker-library manifest file for solr...
> [https://github.com/docker-library/official-images/blob/master/library/solr]
> ie:
> * what replaces [https://github.com/docker-solr/docker-solr.git]
> * what process do we use to update/manage this?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
