Se ho un checkout di discourse_docker alla revisione A, eseguo launcher bootstrap web_only seguito da launcher run web_only al tempo T1 e poi, al tempo T2, eseguo gli stessi comandi esatti, otterrò esattamente lo stesso software in esecuzione a T1 e T2?
Cioè, l’ID del commit di discourse_docker più qualsiasi stato presente nei file YAML costituisce lo stato completo che genera l’artefatto in esecuzione?
Sospetto di no, poiché sembra che Discourse stia recuperando dati da remotes git durante la compilazione e l’avvio, ma vorrei solo verificare con la comunità.
It depends on what branch you are pulling. If it’s tests-passed, then you are likely to get a different version at every rebuild /bootstrap. You could or either a beta version or a commit id there to see that things stay the same.
If you want paid support to get your larger problem solved and have a budget, my contact info is in my profile.
thanks @pfaffman . Quick clarification. By branch do you mean the branch of discourse_docker or is there another setting that can lock the main discourse to a certain branch? Just to be clear, in my example, I am not deliberately pulling new code for either discourse_docker or discourse . I’m getting the feeling that discourse_docker does either one, or both behind the scenes. Ideally I would want to disable this behaviour so I can get a repeatable build. Is this possible?
Launcher will pull the version of Discourse specified by the params: version: key in web_only.yml. As described in that file, the default is tests-passed.
In addition, plugins will normally update unless you pin a version in their git clone.