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

Battle tests on Top 5k Ruby Projects and review policy results #353

Closed
cfabianski opened this issue Jan 9, 2023 · 2 comments · Fixed by #391
Closed

Battle tests on Top 5k Ruby Projects and review policy results #353

cfabianski opened this issue Jan 9, 2023 · 2 comments · Fixed by #391
Assignees
Labels
CI Improving continuous integration sytstem
Milestone

Comments

@cfabianski
Copy link
Collaborator

We have the battle tests that we used to check the stats on the top 5k repositories per language.
It is being triggered by this workflow

Now that we have the policies in place, we would like to update the battle tests a bit to allow it to run the policies and to send the output of the policies on S3 (so that we can review the results).

NB: This means only run it on the Ruby projects only

@cfabianski cfabianski assigned cfabianski and spdawson and unassigned cfabianski Jan 9, 2023
@gotbadger gotbadger added the CI Improving continuous integration sytstem label Jan 10, 2023
@spdawson
Copy link
Contributor

@cfabianski It looks like the existing battle test runner is generating a stats report. Do we want to retain this alongside the policies report?

Also, do we have an existing S3 bucket that is suitable for this data? Or should we create a new one?

@cfabianski
Copy link
Collaborator Author

@cfabianski It looks like the existing battle test runner is generating a stats report. Do we want to retain this alongside the policies report?

If we can keep both, that would be great.
The battle tests is using the binary but maybe we could use the linux package (now that we are building it)

Also, do we have an existing S3 bucket that is suitable for this data? Or should we create a new one?

We don't, it's preferable to create a new one, let me know once you are there so that I can assist.

@gotbadger gotbadger mentioned this issue Jan 18, 2023
19 tasks
@gotbadger gotbadger added this to the Milestone 1 milestone Jan 18, 2023
@gotbadger gotbadger assigned cfabianski and gotbadger and unassigned spdawson Jan 26, 2023
@cfabianski cfabianski removed their assignment Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Improving continuous integration sytstem
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants