-
Notifications
You must be signed in to change notification settings - Fork 47
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
Fix/packit service/1328 bis #2070
Fix/packit service/1328 bis #2070
Conversation
Build failed. ✔️ pre-commit SUCCESS in 2m 10s |
a9c2db9
to
0c670bc
Compare
Build succeeded. ✔️ pre-commit SUCCESS in 2m 06s |
0c670bc
to
a993411
Compare
Build succeeded. ✔️ pre-commit SUCCESS in 2m 10s |
a993411
to
e0576c0
Compare
Build failed. ✔️ pre-commit SUCCESS in 2m 06s |
e0576c0
to
e8167d7
Compare
Build failed. ✔️ pre-commit SUCCESS in 2m 13s |
e8167d7
to
3287aeb
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 55s |
3287aeb
to
34aa347
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 54s |
recheck |
This comment was marked as outdated.
This comment was marked as outdated.
Build failed. ❌ pre-commit FAILURE in 1m 37s |
34aa347
to
afcd9f2
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Build failed. ❌ pre-commit FAILURE in 1m 43s |
recheck |
afcd9f2
to
f015d2b
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 54s |
recheck |
Build failed. ✔️ pre-commit SUCCESS in 1m 43s |
recheck |
Build succeeded. ✔️ pre-commit SUCCESS in 1m 50s |
4546d9e
to
ebd0155
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 46s |
recheck |
Build failed. ❌ pre-commit FAILURE in 1m 57s |
Many ProjectEventModel(s) can work on the same AbstractProjectObjectDbType (as an example many pull request pushes can work on the same pull request object). We need to pass around the event, because we can not get an event from the object (we will end up with multiple events...).
The db_project_object is retrieved through the related db_project_event.
ebd0155
to
2462b30
Compare
Build succeeded. ✔️ pre-commit SUCCESS in 1m 43s |
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.
this is admirable work Maja!! 🚀
just a few notes, it would be nice to get this to staging and test it there
as for the migration, have you tested that with the production data?
alembic/versions/af00a7f19025_move_commit_sha_to_project_events.py
Outdated
Show resolved
Hide resolved
Build failed. ✔️ pre-commit SUCCESS in 2m 35s |
Yes, on my laptop with the production data the migration took more than half an hour but less than an hour. |
Co-authored-by: Laura Barcziová <49026743+lbarcziova@users.noreply.github.com>
Co-authored-by: Laura Barcziová <49026743+lbarcziova@users.noreply.github.com>
c23d56e
to
c5cec06
Compare
Build failed. ✔️ pre-commit SUCCESS in 2m 11s |
recheck |
Build succeeded. ✔️ pre-commit SUCCESS in 2m 07s |
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.
let's ship it!
thanks Maja for taking this complext issue!
Build succeeded (gate pipeline). ✔️ pre-commit SUCCESS in 1m 55s |
commit_sha has been moved to project_events table Merge after packit/packit-service#2070 Reviewed-by: Laura Barcziová
Fixes #1328 (point 3)
The new db diagram: