Opened 8 months ago
Last modified 4 weeks ago
#9080 assigned task
Review Deployment Process
Reported by: | espellcaste | Owned by: | espellcaste |
---|---|---|---|
Milestone: | 15.0.0 | Priority: | low |
Severity: | normal | Version: | |
Component: | Build/Test Tools | Keywords: | |
Cc: |
Description
Review and see if there are improvements or benefit in moving some of those tasks into a Github Action.
Change History (9)
#1
@
8 months ago
- Component changed from Core to Build/Test Tools
- Milestone changed from Awaiting Review to Under Consideration
- Owner set to netweb
- Type changed from defect (bug) to enhancement
This ticket was mentioned in Slack in #buddypress by espellcaste. View the logs.
5 months ago
#6
@
4 months ago
Hi @espellcaste
The biggest painpoint is relative to releasing an "old" branch's tag (Eg: 11.x). This is due to the fact we then absolutely need to use nvm
to make sure to go back to a previous version of node to grunt build
.
Another part a bit annoying is updating the files on WP Plugin Directory SVN repo:
- maybe I'm making my life harder as I only update the files that have been modified (I could completely override all files)
- you absolutely need to
svn stat
to see the files needing to be added to the ones to be committed. When there's a lot of new files, it's pretty annoying as you need tosvn add
files one by one (maybe I'm missing something about SVN usage though).
And of course, we need to test the build before with a fresh WordPress (to test install) or an existing WordPress + BuddyPress (to test upgrade).
@imath I'm curious. As someone who perform those steps often, where do you think are the main painpoints or opportunities for automation?