Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
We critically need a test bot to be able to proceed effectively with big refactors as WSCCI involves.
Who should I talk to? Initiative owner, Larry? Sam Boyer and the Git team? The infrastructure team?
Comments
Comment #1
tamasd CreditAttribution: tamasd commentedsubscribing
Comment #2
Crell CreditAttribution: Crell commentedI will reiterate this need in the Initiative Owner scrum call this week. It would require work by the infra/git team to make it happen.
Comment #3
sunThe problem here is that PIFT is only able to test branches that have a release node associated.
As of now, the most simple proposal heard in IRC was to allow development snapshot releases for sandboxes, but don't allow them to be published.
Comment #4
Crell CreditAttribution: Crell commentedMarking postponed until the infra team figures out what to do here. :-/ For the time being, open a core issue, make a huge mega patch, and post it there. Then throw out the issue (eventually). That's the best we can do for now.
Comment #5
webchickPer catch, and blessed by Larry, moving this and all other WSCCI issues to the Drupal core queue.
Comment #6
sunRe-classifying.
Comment #7
jhedstromThis doesn't seem like a core issue.
Comment #8
tvn CreditAttribution: tvn commentedNot Infra.d.o issue either.
Comment #9
jthorson CreditAttribution: jthorson commentedNot compatible with the current PIFR architecture (based on release_id references, and sandboxes can't have release_ids).
We can look at working around this in the next generation product.
Comment #10
MixologicComment #11
andypostWorking on core proposal https://www.drupal.org/sandbox/jhodgdon/2369943 it screams to allow testing patches within sandbox
Comment #12
jhodgdonYes please! In this sandbox, anydpost, some other people, and I are working on a Core proposal for a new experimental module #2920309: Add experimental module for Help Topics
It makes a lot of sense (for this project) to have a Sandbox with its own issue queue to work on this. But when we post patches to issues, they don't get tested, meaning we either have to update the Core patch on the master issue and see what happens, or run the tests manually ourselves. Neither is a huge deal, but it would be faster/easier for us if the Sandbox could have auto testing of patches.