WIP: Add script to manage FTBFS/FTI bugs #9443
No reviewers
Labels
No labels
after freeze
automation
backlog
blocked
change-ack
change-nak
change-noreleng
changes
Closed As
Can't Fix
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Get back later
Closed As
Grooming
Closed As
Insufficient data
Closed As
Invalid
Closed As
It's all good
Closed As
taiga
Closed As
upstream
day-to-day
dev
docs
easyfix
epel
f26
f27
f28
f29
f30
f31
f32
f33
f34
f35
f36
f37
f38
f39
f40
f41
f42
f43
f44
f45
fedora
groomed
high-gain
high-trouble
in-progress
in-review
investigation
legal
low-gain
low-trouble
mass rebuild
medium-gain
medium-trouble
meeting
mini-initiative
new_artifact
ops
pdc_retirement
rawhide
RCA
review
script
sidetarget
sprint-0
sprint-1
sprint-2
sprint-3
sprint-4
sprint-5
unfrozen
waiting on external
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
releng/tickets!9443
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ftbfs-fti"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Running script is fairly trivial:
Missing things are:
1 new commit added
fixup! Add script to manage FTBFS/FTI bugsrebased onto 22720a3f760287da7c95865a7b18452e1bf2eeea
1 new commit added
fixup! Add script to manage FTBFS/FTI bugs1 new commit added
fixup! Add script to manage FTBFS/FTI bugs1 new commit added
fixup! Add script to manage FTBFS/FTI bugs1 new commit added
ftbfs-fti: Do not close bugs if they block any other important tracker5 new commits added
ftbfs-fti: Do not close bugs if they block any other important trackerfixup! Add script to manage FTBFS/FTI bugsfixup! Add script to manage FTBFS/FTI bugsfixup! Add script to manage FTBFS/FTI bugsAdd script to manage FTBFS/FTI bugs5 new commits added
ftbfs-fti: Do not close bugs if they block any other important trackerfixup! Add script to manage FTBFS/FTI bugsfixup! Add script to manage FTBFS/FTI bugsfixup! Add script to manage FTBFS/FTI bugsAdd script to manage FTBFS/FTI bugs5 new commits added
ftbfs-fti: Do not close bugs if they block any other important trackerfixup! Add script to manage FTBFS/FTI bugsfixup! Add script to manage FTBFS/FTI bugsfixup! Add script to manage FTBFS/FTI bugsAdd script to manage FTBFS/FTI bugs1 new commit added
fixup! ftbfs-fti: Do not close bugs if they block any other important trackerrebased onto 2e03dc91abaac743bb51f462d14dfce6bcb4c8d8
2 new commits added
ftbfs-fti: Move bugkeeping to the separate functionftbfs-fti: Show more information about dates1 new commit added
ftbfs-fti: Improve wording for new bugs1 new commit added
ftbfs-fti: Improve messaging when closing bug to handle retired packages4 new commits added
ftbfs-fti: Ignore ON_QA bugsftbfs-fti: Add support for opening bugs against non-rawhideftbfs-fti: Truncate summary if neededftbfs-fti: Fix crash after asking for second needinfo2 new commits added
ftbfs-fti: Do not bother opening bugs for orphaned packagesftbfs-fti: Ignore only MODIFIED/ON_QA bugs if they have bodhi update for appropriate releaserebased onto c1163ab3170eab2ea4bcc7701d0048f9453bc551
1 new commit added
ftbfs-fti: Close bugs with WORKSFORME instead of RAWHIDE1 new commit added
ftbfs-fti: Create bugs for a specific release instead of rawhide1 new commit added
ftbfs-fti: Improve output a bit1 new commit added
ftbfs-fti: Drop F30 trackers, those are EOL anyway3 new commits added
ftbfs-fti: Try to be smarter when dealing bugzilla wrt flag settingfixup! ftbfs-fti: Create bugs for a specific release instead of rawhideActually send second needinforebased onto 6fb308df9db07916c431711eaace12d25679cc00
2 new commits added
ftbfs-fti: Print closing/unblocking message to the stdoutftbfs-fti: Improve debuggning messages20 new commits added
ftbfs-fti: Print closing/unblocking message to the stdoutftbfs-fti: Improve debuggning messagesftbfs-fti: Try to be smarter when dealing bugzilla wrt flag settingActually send second needinfoftbfs-fti: Drop F30 trackers, those are EOL anywayftbfs-fti: Improve output a bitftbfs-fti: Create bugs for a specific release instead of rawhideftbfs-fti: Close bugs with WORKSFORME instead of RAWHIDEftbfs-fti: Do not bother opening bugs for orphaned packagesftbfs-fti: Ignore only MODIFIED/ON_QA bugs if they have bodhi update for appropriate releaseftbfs-fti: Ignore ON_QA bugsftbfs-fti: Add support for opening bugs against non-rawhideftbfs-fti: Truncate summary if neededftbfs-fti: Fix crash after asking for second needinfoftbfs-fti: Improve messaging when closing bug to handle retired packagesftbfs-fti: Improve wording for new bugsftbfs-fti: Move bugkeeping to the separate functionftbfs-fti: Show more information about datesftbfs-fti: Do not close bugs if they block any other important trackerAdd script to manage FTBFS/FTI bugs2 new commits added
ftbfs-fti: When closing bugs, ensure minor_updateftbfs-fti: Count time in orphaning process from the last relevant blocked tracker2 new commits added
ftbfs-fti: Exit early when skipping bugsftbfs-fti: If the FTI tracker was added at the creation time, use it1 new commit added
ftbfs-fti: Improve notifications messages1 new commit added
ftbfs-fti: All times should be in UTC2 new commits added
ftbfs-fti: Skip dummy test packagesftbfs-fti: Improve creation messagerebased onto c07b50b3835321e56a99981aba9d7712bfa57890
2 new commits added
ftbfs-fti: Fix typo in closing messageftbfs-fti: Update orphaned bugs with useful info and do not ask for needinforebased onto
740cfc7f8aI assume this is to just have a known place to run them from so if others do so it's all the same scripting?
Or did you want to look at us running this every day/week or whatever?
Pull-Request has been merged by kevin
@kevin Ideally you would run it every day, but I think for now it is more about having code somewhere soe that people can run it / inspire.
Sounds good. Thanks for writing it!