https://pharo.fogbugz.com/f/cases/21615/Separate-bootstrap-process-in-to-distinct-stages

https://github.com/pharo-project/pharo/pull/1127

This does the first step of breaking the bootstrap process in to
distinct phases and moving all the downloads to the start (e.g.
allowing a test VM to be substituted for the build stage).

Once this is integrated I can submit a PR that modifies Jenkinsfile to
use the new shell scripts, removing code duplication.

On 16 March 2018 at 14:38, tesonep@gmail.com <tesonep@gmail.com> wrote:
> Hi,
>�� �� �� sorry my mistake when updating the scripts. As the bootstrap.sh is not
> executed during the Jenkins process it has not been validated (locally I'm
> not using that script, because is trying to download each time the VM and
> the bootstraping process image)

There are also scripts to snapshot and restore the bootstrap state,
avoiding the need to do the multiple downloads.

Just to be clear again: This is intended to complement and help with
the goal of moving the bootstrap process to pure Pharo code.�� Each of
the shell scripts can eventually be replaced by a call to the
equivalent Pharo code.

Thanks!
Alistair