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

Workflow Manager - Life cycle #109

Closed
3 tasks
Tracked by #107
saratvemulapalli opened this issue Jul 28, 2021 · 5 comments
Closed
3 tasks
Tracked by #107

Workflow Manager - Life cycle #109

saratvemulapalli opened this issue Jul 28, 2021 · 5 comments
Assignees

Comments

@saratvemulapalli
Copy link
Member

saratvemulapalli commented Jul 28, 2021

  • Investigate and Design - Figure out how to create orchestration workflow in Jenkins, how can multiple independent jobs be stitched under one id (and individual job ids), how can orchestration framework provide inputs for each jobs and trigger them, etc.
  • Coordinate with build automation team to define Manifest .
  • Build the orchestration layer that stitches together multiple independent jenkins jobs like integration, performance, upgrade testing. Publish logs to investigate failure scenarios
@setiah
Copy link
Contributor

setiah commented Jul 29, 2021

Updated w/ below sub-tasks

  • Investigate and Design - Figure out how to create orchestration workflow in Jenkins, how can multiple independent jobs be stitched under one id (and individual job ids), how can orchestration framework provide inputs for each jobs and trigger them, etc.
  • Coordinate with build automation team to define Manifest .
  • Build the orchestration layer that stitches together multiple independent jenkins jobs like integration, performance, upgrade testing. Publish logs to investigate failure scenarios

@dblock
Copy link
Member

dblock commented Aug 30, 2021

What do we do with this issue @saratvemulapalli?

@saratvemulapalli
Copy link
Member Author

Good question, @setiah I see most of these pieces are done except reporting the results and we have other issues to take care of that.
Do you have anything else to cover here or could we close this down?

@peternied
Copy link
Member

@saratvemulapalli Are you still working on this issue, or has this been rolled up into another change?

@saratvemulapalli
Copy link
Member Author

This is rolled up to #262 and #263.
Will close this, thanks guys!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants