Rebuilding with a specific version

Support

AI-generated summary

Rebuilding with a Specific Version. csmu asked how to rebuild Discourse with a specific version for testing purposes. pfaffman suggested editing app.yml with a Git commit ID or a version ID. However, csmu encountered issues using a commit ID, but successfully rebuilt using a version tag (v2.4.0.beta1). pfaffman confirmed that beta tags are a viable alternative.

1

Context: I’m setting up a staging site and I want to have the same version on staging as production so I can test the next update on staging before applying the update to production.

How do you ask/get launcher to rebuild with a specific version of discourse?

2

In app.yml where it says version: you can put a Git commit id or a version ID.

It’s a bit more tricky to keep the plugins all tied to the same commit ID.

3

Thanks for the heads up :slight_smile:

4

The commit id 6515dc3582309ce58427f57aa1248c3e32877d6e

commit 6515dc3582309ce58427f57aa1248c3e32877d6e
Author: Sam Saffron <sam.saffron@gmail.com>
Date:   Tue Jun 18 16:14:38 2019 +1000

    DEV: bump dependencies
    
    - new ImageMagick
    - new NGINX moved to stable from mailine
    - new Redis
    - new PNG Quant
    - updated libjemalloc

failed but using version v2.4.0.beta1 worked!
Thanks Jay @pfaffman :slight_smile:

5

Hmm. I’m pretty sure that I’ve used a commit id, but the beta tags are likely just as good.