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.

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

Jump to bottom

Create an example of packit workflow using temporalio #2233

Open
4 tasks
majamassarini opened this issue Oct 19, 2023 · 0 comments
Open
4 tasks

Create an example of packit workflow using temporalio #2233

majamassarini opened this issue Oct 19, 2023 · 0 comments
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/low This issue impacts only a few users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@majamassarini
Copy link
Member

majamassarini commented Oct 19, 2023 •
edited
Loading

Description

This is a follow-up card for packit/research#204
We decided to start implementing a real code example of a packit workflow using temporalio.

Things to do:

  • setup temporalio - probably I would do this in docker/podman compose
  • write a simple workflow - probably I would choose the RPM and SRPM dependency without database handling or corner cases just to see how temporalio works with making tasks sleep and making tasks communicate.

Benefit

No response

Importance

No response

What is the impacted category (job)?

General

Workaround

  • There is an existing workaround that can be used until this feature is implemented.

Participation

  • I am willing to submit a pull request for this issue. (Packit team is happy to help!)
@majamassarini majamassarini added kind/feature New feature or a request for enhancement. area/general Related to whole service, not a specific part/integration. labels Oct 19, 2023
@majamassarini majamassarini added impact/low This issue impacts only a few users. gain/low This doesn't bring that much value to users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. complexity/single-task Regular task, should be done within days. and removed kind/feature New feature or a request for enhancement. labels Oct 23, 2023
@majamassarini majamassarini moved this from new to backlog in Packit Kanban Board Oct 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/low This issue impacts only a few users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Packit Kanban Board
Status: backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@majamassarini