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

Create notification on Product & Community Registries Check nightly run #1255

Closed
2 tasks
Tracked by #1272
thepetk opened this issue Sep 14, 2023 · 6 comments · Fixed by devfile/alizer#43
Closed
2 tasks
Tracked by #1272

Create notification on Product & Community Registries Check nightly run #1255

thepetk opened this issue Sep 14, 2023 · 6 comments · Fixed by devfile/alizer#43
Assignees
Labels
area/alizer Enhancement or issue related to the alizer repo area/ci

Comments

@thepetk
Copy link
Contributor

thepetk commented Sep 14, 2023

Which area/kind this issue is related to?

/area ci
/area alizer

Issue Description

The nightly run which checks the starter projects of all stacks inside product and community registry should have an alerting mechanism in order to notify people for the status of the job. As a result a notification should be added after every run, as a message to the appropriate team channel so people can monitor easier the results of this job.

Acceptance Criteria

  • Every nightly run should send a message to team channel with the result of the task.
  • The message should follow the following format:
    * Status: [{red light emoji} failure | {green light emoji} success]
    * Severity: [for failure - medium | for success low]
    * In case of failure mention @ app-devfile in order to take action.
    * Title: Product & Community Registries Check
    * Description: Mention Branch and Commit, add a short message and link to logs
@openshift-ci openshift-ci bot added area/ci area/alizer Enhancement or issue related to the alizer repo labels Sep 14, 2023
@thepetk thepetk moved this to Backlog in Devfile Project Sep 14, 2023
@thepetk
Copy link
Contributor Author

thepetk commented Sep 14, 2023

Currently blocked from #1248

@feloy
Copy link
Contributor

feloy commented Sep 22, 2023

Similar to #1061

@feloy feloy moved this from Backlog to To Do 📝 in Devfile Project Sep 22, 2023
@feloy feloy moved this from To Do 📝 to Backlog in Devfile Project Oct 2, 2023
@thepetk
Copy link
Contributor Author

thepetk commented Oct 13, 2023

Blocked by #1026

@thepetk thepetk self-assigned this Jan 9, 2024
@thepetk thepetk moved this from Backlog to To Do 📝 in Devfile Project Jan 9, 2024
@thepetk thepetk moved this from To Do 📝 to In Progress 🚧 in Devfile Project Jan 15, 2024
@thepetk thepetk moved this from In Progress 🚧 to In Review 👀 in Devfile Project Jan 15, 2024
@thepetk
Copy link
Contributor Author

thepetk commented Jan 15, 2024

Removing blocked label as I don't think is relevant anymore

@thepetk
Copy link
Contributor Author

thepetk commented Jan 16, 2024

Putting item back to "in review" cause I'm still looking for a proper way to test the related PR

@thepetk thepetk moved this from In Review 👀 to In Progress 🚧 in Devfile Project Jan 16, 2024
@thepetk thepetk moved this from In Progress 🚧 to In Review 👀 in Devfile Project Jan 17, 2024
@thepetk
Copy link
Contributor Author

thepetk commented Jan 17, 2024

PR devfile/alizer#43 is now ready for review

@github-project-automation github-project-automation bot moved this from In Review 👀 to Done ✅ in Devfile Project Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/alizer Enhancement or issue related to the alizer repo area/ci
Projects
Status: Done ✅
Development

Successfully merging a pull request may close this issue.

2 participants