keep cache when switching branch

[jen...@google.com]

Can bazel keep cached builds and test results when switching between branches of a project?

It would speed up a lot workflow with multiple branches or for example continuous build of pull requests in jenkins.

Thanks,
Jan

[Kamal Marhubi]

I thought this was already the case, since action outputs depend on hashes of their inputs. Am I wrong?

--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/5d81acf8-a63d-4f89-9a59-cd07cfd906d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jonathan Coveney]

Perhaps the intent is more even if something is invalidated, keeping previous versions for when you switch batch

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAK-ZPenuD85etHwcwXBuAZ8aCEpV%2BP%3DAPVWu%2B0%2BSkbrOb6Fvjg%40mail.gmail.com.

[Brian Silverman]

I would also like some way to keep more than a single output for each action, but I don't think there is one right now.

As a workaround, if you use a different --output_base, it should cache independently. That will download external repositories etc separately too.

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAOMX%3DBveQwvm_vmVyTmL1zfusazVV-GLUU3j1eFDenPT9xg0GA%40mail.gmail.com.

[Damien Martin-guillerez]

For now, using Alpha's remote caching prototype (https://bazel-review.googlesource.com/#/c/2760/) could do the trick.

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAP01z6Kb3SHRhJyt-HMPdn0qNc2NbqYVGRAseywkzVC85yeoEQ%40mail.gmail.com.

[R.J. Aquino]

Is the remote caching functionality in a useable place? Or are you suggesting "once this is finished/released, you'll have what you need"?

- R.J.

On Thursday, April 28, 2016 at 1:06:15 AM UTC-7, Damien Martin-guillerez wrote:

For now, using Alpha's remote caching prototype (https://bazel-review.googlesource.com/#/c/2760/) could do the trick.

On Thu, Apr 28, 2016 at 5:19 AM Brian Silverman <bsilve...@gmail.com> wrote:

I would also like some way to keep more than a single output for each action, but I don't think there is one right now.

As a workaround, if you use a different --output_base, it should cache independently. That will download external repositories etc separately too.

On Wed, Apr 27, 2016 at 10:22 PM, 'Jonathan Coveney' via bazel-discuss <bazel-...@googlegroups.com> wrote:

Perhaps the intent is more even if something is invalidated, keeping previous versions for when you switch batch

El miércoles, 27 de abril de 2016, Kamal Marhubi <ka...@marhubi.com> escribió:

I thought this was already the case, since action outputs depend on hashes of their inputs. Am I wrong?

On Wed, Apr 27, 2016 at 7:09 PM jendap via bazel-discuss <bazel-discuss@googlegroups.com> wrote:

Can bazel keep cached builds and test results when switching between branches of a project?

It would speed up a lot workflow with multiple branches or for example continuous build of pull requests in jenkins.


Thanks,
Jan

--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discuss+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/5d81acf8-a63d-4f89-9a59-cd07cfd906d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discuss+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAK-ZPenuD85etHwcwXBuAZ8aCEpV%2BP%3DAPVWu%2B0%2BSkbrOb6Fvjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAOMX%3DBveQwvm_vmVyTmL1zfusazVV-GLUU3j1eFDenPT9xg0GA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Jan Prach]

The remote cache looks good. I will try it. Or look around at the implementation of the other strategies to figure how it works.

Thank you,

Jan

On Thu, Apr 28, 2016 at 11:02 AM, R.J. Aquino <r...@asana.com> wrote:

Is the remote caching functionality in a useable place? Or are you suggesting "once this is finished/released, you'll have what you need"?

- R.J.

On Thursday, April 28, 2016 at 1:06:15 AM UTC-7, Damien Martin-guillerez wrote:

For now, using Alpha's remote caching prototype (https://bazel-review.googlesource.com/#/c/2760/) could do the trick.

On Thu, Apr 28, 2016 at 5:19 AM Brian Silverman <bsilve...@gmail.com> wrote:

I would also like some way to keep more than a single output for each action, but I don't think there is one right now.

As a workaround, if you use a different --output_base, it should cache independently. That will download external repositories etc separately too.

On Wed, Apr 27, 2016 at 10:22 PM, 'Jonathan Coveney' via bazel-discuss <bazel-...@googlegroups.com> wrote:

Perhaps the intent is more even if something is invalidated, keeping previous versions for when you switch batch

El miércoles, 27 de abril de 2016, Kamal Marhubi <ka...@marhubi.com> escribió:

I thought this was already the case, since action outputs depend on hashes of their inputs. Am I wrong?

On Wed, Apr 27, 2016 at 7:09 PM jendap via bazel-discuss <bazel-...@googlegroups.com> wrote:

Can bazel keep cached builds and test results when switching between branches of a project?

It would speed up a lot workflow with multiple branches or for example continuous build of pull requests in jenkins.


Thanks,
Jan

--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/5d81acf8-a63d-4f89-9a59-cd07cfd906d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAK-ZPenuD85etHwcwXBuAZ8aCEpV%2BP%3DAPVWu%2B0%2BSkbrOb6Fvjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAOMX%3DBveQwvm_vmVyTmL1zfusazVV-GLUU3j1eFDenPT9xg0GA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.