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.In D7, release packaging is now queued. We should test that queueing happens when any release is made, either dev or stable. And dev releases should be queued when a commit is made.
However they get in the queue, drush release-package-run should do that packaging.
Comments
Comment #1
marvil07 CreditAttribution: marvil07 commentedA link to implementation issue for reference: #1878418: Queue release packaging at git code arrival
Comment #2
drummRe-tagging. I'm not sure this can be automated all that well, the packaging queue is usually processed on cron, so we need to either automate kicking it off or wait a really long time.
Comment #3
eliza411 CreditAttribution: eliza411 commentedIt sounds like automating this is sub-optimal. If someone who knows how it is supposed to work writes a test plan (bdd-style or otherwise), it can be validly tested manually. If it's very clicky, I might run the automation with the long wait, but exclude it from the @ci run.
Comment #4
drummOnce a tagged release is created, the .tar.gz and .zip packages should appear when the cron_release-package-run_git7 Jenkins job runs, currently hourly. Commits to dev releases should trigger a repackaging on the same schedule.
We can speed up the schedule, production runs every 5 minutes. Even better would be moving to a Beanstalk/Supervisord queue for immediate process, but that's a post-launch task.
Comment #5
drummFixing priority since this has been manually tested.
Comment #6
eliza411 CreditAttribution: eliza411 commentedI'm thinking it would be worth adding an automated job that doesn't block other tests from running, but not sure if when I'll get to it or if I can even add jenkins jobs.
Comment #7
tvn CreditAttribution: tvn commentedUntagging, not a D7 launch blocker.
Comment #7.0
tvn CreditAttribution: tvn commentedSpeling