-
Notifications
You must be signed in to change notification settings - Fork 14
ci(ipa): automatic warning-level violation detection #905
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
Conversation
fi | ||
|
||
# Create detailed description | ||
DESCRIPTION="Warning-level violations were found during IPA validation. Please review and add exceptions if valid, or address false positives. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can link to the IPA wiki with the rollout process?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added! Let me know how it sounds
chmod +x .github/scripts/handle_warning_violations.sh | ||
.github/scripts/handle_warning_violations.sh "$WARNING_COUNT" "$TEAM_ID" "$JIRA_API_TOKEN" "$SLACK_BEARER_TOKEN" "$SLACK_CHANNEL_ID" "$SLACK_ONCALL_USER" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Q: Do we need the chmod +x
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might not need it, because I will already commit the execute permission. Let me remove and try that way
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, perhaps we can wait with enabling this since we currently have a lot of warning we're aware of. Could be good to enable after the current IPA projects are done
@lovisaberggren I commented out the "handle warning violations step" and we can turn it on when it is ready to use. Wdyt? I don’t think filtering and creating files will add much overhead |
SGTM! Can you create a ticket for enabling? |
Proposed changes
Jira ticket: CLOUDP-310539
This PR introduces automatic warning-level violation detection:
Would create Jira ticket with:
Would send Slack message:
Checklist
Changes to Spectral
Further comments