You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 16, 2023. It is now read-only.
There is no information regarding a limit to how many jobs can be analysed for conclusions, and as no limit is defined I suppose there's not supposed to be one?
We have 34 jobs that should be analysed, but information is only fetched for the 30 first ones and not the last ones...
We see this count : { total_count: 34, jobs: [ [Object], [Object], [Object], [Object] ] }
But the 'jobs' array only containts 30, and we get Conclusions: [ 'success', 'undefined' ], and Conclusion: success, even though we know that job nbr 33 failed...
To Reproduce:
Steps to reproduce the behavior:
Have a workflow with more than 30 jobs/actions (yml file)
Job number 31 should be a failing one (returning non-zero value)
Job number 32 should contain a check for conclusion of the previous jobs using your code
slackNotification:
Run the tests and check the results of jobs, conclusions and conclusion, if bug is reproduced the conclusion will be success and the 31st job won't be in the list of jobs.
Expected behavior:
When the check for jobs and their conclusion is done, they should check all the available jobs and not only the first 30 jobs. Also, if 'undefined' is in the conclusions array, the resulting conclusion shouldn't be 'success'
Screenshots:
Operating environment:
Version of software
OS: Ubuntu
Browser: -
etc.
Additional context:
We use your code to retrieve the conclusion of all the jobs, to verify whether a Slack notification should be sent or not. Since the last jobs are not checked by your code, no notification is sent despite jobs failing...
The text was updated successfully, but these errors were encountered:
Describe the bug:
There is no information regarding a limit to how many jobs can be analysed for conclusions, and as no limit is defined I suppose there's not supposed to be one?
We have 34 jobs that should be analysed, but information is only fetched for the 30 first ones and not the last ones...
We see this count : { total_count: 34, jobs: [ [Object], [Object], [Object], [Object] ] }
But the 'jobs' array only containts 30, and we get Conclusions: [ 'success', 'undefined' ], and Conclusion: success, even though we know that job nbr 33 failed...
To Reproduce:
Steps to reproduce the behavior:
slackNotification:
Expected behavior:
When the check for jobs and their conclusion is done, they should check all the available jobs and not only the first 30 jobs. Also, if 'undefined' is in the conclusions array, the resulting conclusion shouldn't be 'success'
Screenshots:
Operating environment:
Additional context:
We use your code to retrieve the conclusion of all the jobs, to verify whether a Slack notification should be sent or not. Since the last jobs are not checked by your code, no notification is sent despite jobs failing...
The text was updated successfully, but these errors were encountered: