Skip to content
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.

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

More documentation for the template issues for tag releases and redelivering containers. #91

Closed
MichaelClifford opened this issue Oct 5, 2021 · 4 comments · Fixed by aicoe-aiops/project-template#46
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@MichaelClifford
Copy link

Is your feature request related to a problem? Please describe.

Not sure if this issue should be tracked here or in https://github.com/aicoe-aiops/project-template. However, the template issues that are included in each of our projects through the template repo that are designed to interact with Thoth's build pipelines need more documentation to clarify use, expectations and differentiation between them. Specifically, major-release.md, minor-release.md, patch-release.md and redeliver_contianer_image.md. For user's unfamiliar with Thoth, there is no indication of how these issues will aid the user in delivering content images.

High-level Goals
Additional instructions and explanation within each issue template explaining to users which build pipeline will be kicked off by opening the issue and how to track its progress.

@MichaelClifford MichaelClifford added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 5, 2021
@pacospace pacospace self-assigned this Oct 13, 2021
@pacospace
Copy link

pacospace commented Oct 13, 2021

Hey @MichaelClifford thanks for this issue!

I opened this issue to describe the templates but it might be too verbose: aicoe-aiops/project-template#46. Maybe we need another place for something more detailed. let me know what you think.

Regarding the track of the progress of the pipelines, we need to find another solution, maybe opening an issue in the user repo if the pipeline fails or succeeds (in this case the issue seems weird, maybe a comment in the previous issue opened, or close that issue only when the image is really on the image registry, not sure if we have already an issue to look for this solution) cc @harshad16

@pacospace
Copy link

@MichaelClifford should we have another issue for brainstorming on how to provide a tracking link to the build pipeline?

@MichaelClifford
Copy link
Author

Sure @pacospace
Looks like @erikerlandson already started the discussion here: thoth-station/core#316
Shall we continue it there?

@pacospace
Copy link

Sure @pacospace Looks like @erikerlandson already started the discussion here: thoth-station/core#316 Shall we continue it there?

Sounds good!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants