Join GitHub today
Create a production-ready release artifact from master branch builds #6285
To better automate the release process, it would be helpful to create a production-ready release artifact from
More specifically, what I mean by "production-ready release artifact" is a copy of the plugin that's ready for commit to WordPress.org.
If we include this in the
To offer some ideas... I use DeployHQ for client projects to push a copy of the built code to my staging server. At the end of the push, DeployHQ runs
Another idea: we can use Circle CI exclusively for this process, to avoid consuming Travis builds.
This came up in the
I've written a script to run on a six hour cron on my server: https://gist.github.com/danielbachhuber/f5fc9caa03541698949af81e42130ad1
The nightly build can be installed with:
@WordPress/gutenberg-core Any interest in formalizing this in some way? I see a few different options:
referenced this issue
Sep 27, 2018
Some conversation in
Notably, from @Otto42 (specific to option 2):
And from @Clorith:
I'd be fine with leaving my current implementation (https://builds.danielbachhuber.com/gutenberg-nightly.zip) running for the next couple of months if we don't want to invest more time into it.
Oh, right, I'm sorry, I should have clarified:
I would consider SVN plugin trunk for releases and RCs, not development versions too. I don't see much value in pushing
But offering a "nightly"
I made a build process enhancement to: 1) bump to next version, 2) append
I've also blogged it here: https://danielbachhuber.com/2018/10/02/gutenberg-nightly-build/