In order to speed up builds on our CI infrastructure when we spin up new machines, I would like to share binaries of all the libraries built by stack. What's the best/recommended way of doing that?
If you're using the same user and directory structure, you can simply copy your ~/.stack directory around. This is essentially what Travis's caching does.
On Sat, Nov 5, 2016 at 11:59 AM, Arnaud Bailly <[hidden email]> wrote:
Hello,
In order to speed up builds on our CI infrastructure when we spin up new machines, I would like to share binaries of all the libraries built by stack. What's the best/recommended way of doing that?
Thanks Michael. Yes, that's mostly the case, or I could ensure this is the case. This needs to be same user because some components inside .stack are using absolut paths, right?
On Mon, Nov 7, 2016 at 7:33 AM, Michael Snoyman <[hidden email]> wrote:
If you're using the same user and directory structure, you can simply copy your ~/.stack directory around. This is essentially what Travis's caching does.
On Sat, Nov 5, 2016 at 11:59 AM, Arnaud Bailly <[hidden email]> wrote:
Hello,
In order to speed up builds on our CI infrastructure when we spin up new machines, I would like to share binaries of all the libraries built by stack. What's the best/recommended way of doing that?
Yes. I think that simply setting STACK_ROOT would allow you to successfully do this with different users since it will ensure consistent filepaths.
On Mon, Nov 7, 2016, 9:07 AM Arnaud Bailly <[hidden email]> wrote:
Thanks Michael. Yes, that's mostly the case, or I could ensure this is the case. This needs to be same user because some components inside .stack are using absolut paths, right?
On Mon, Nov 7, 2016 at 7:33 AM, Michael Snoyman <[hidden email]> wrote:
If you're using the same user and directory structure, you can simply copy your ~/.stack directory around. This is essentially what Travis's caching does.
On Sat, Nov 5, 2016 at 11:59 AM, Arnaud Bailly <[hidden email]> wrote:
Hello,
In order to speed up builds on our CI infrastructure when we spin up new machines, I would like to share binaries of all the libraries built by stack. What's the best/recommended way of doing that?
On Mon, Nov 7, 2016 at 8:10 AM, Michael Snoyman <[hidden email]> wrote:
Yes. I think that simply setting STACK_ROOT would allow you to successfully do this with different users since it will ensure consistent filepaths.
On Mon, Nov 7, 2016, 9:07 AM Arnaud Bailly <[hidden email]> wrote:
Thanks Michael. Yes, that's mostly the case, or I could ensure this is the case. This needs to be same user because some components inside .stack are using absolut paths, right?
On Mon, Nov 7, 2016 at 7:33 AM, Michael Snoyman <[hidden email]> wrote:
If you're using the same user and directory structure, you can simply copy your ~/.stack directory around. This is essentially what Travis's caching does.
On Sat, Nov 5, 2016 at 11:59 AM, Arnaud Bailly <[hidden email]> wrote:
Hello,
In order to speed up builds on our CI infrastructure when we spin up new machines, I would like to share binaries of all the libraries built by stack. What's the best/recommended way of doing that?
On Mon, Nov 7, 2016 at 8:10 AM, Michael Snoyman <[hidden email]> wrote:
Yes. I think that simply setting STACK_ROOT would allow you to successfully do this with different users since it will ensure consistent filepaths.
On Mon, Nov 7, 2016, 9:07 AM Arnaud Bailly <[hidden email]> wrote:
Thanks Michael. Yes, that's mostly the case, or I could ensure this is the case. This needs to be same user because some components inside .stack are using absolut paths, right?
On Mon, Nov 7, 2016 at 7:33 AM, Michael Snoyman <[hidden email]> wrote:
If you're using the same user and directory structure, you can simply copy your ~/.stack directory around. This is essentially what Travis's caching does.
On Sat, Nov 5, 2016 at 11:59 AM, Arnaud Bailly <[hidden email]> wrote:
Hello,
In order to speed up builds on our CI infrastructure when we spin up new machines, I would like to share binaries of all the libraries built by stack. What's the best/recommended way of doing that?
Locked
