Temporary folder for action?

[Derek Perez]

Is there a way in bazel to create a random temporary folder that is deleted when a target is finished being built?

[Marcel Hlopko]

In a custom skylark rule? +Laurent Le Brun 

On Mon, Jul 31, 2017 at 5:18 AM Derek Perez <de...@perez.earth> wrote:

Is there a way in bazel to create a random temporary folder that is deleted when a target is finished being built?

--
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/CAD7-yft3VZ3G4F9wbVGvXshYW9HW3o6quEoQDbFqB3%2BVOx03bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

-- 

Marcel Hlopko | Software Engineer | hlo...@google.com | 

Google Germany GmbH | Erika-Mann-Str. 33  | 80636 München | Germany | Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle | Registergericht und -nummer: Hamburg, HRB 86891

[Dmitry Lomov]

On Mon, Jul 31, 2017 at 11:38 AM, 'Marcel Hlopko' via bazel-discuss <bazel-...@googlegroups.com> wrote:

In a custom skylark rule? +Laurent Le Brun 

On Mon, Jul 31, 2017 at 5:18 AM Derek Perez <de...@perez.earth> wrote:

Is there a way in bazel to create a random temporary folder that is deleted when a target is finished being built?

No. Why do you need that?

In general, every file a rule creates is declared using ctx.actions.declare_file.

Bazel keeps all intermediate files to be as incremental as it can.

--
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/CAD7-yft3VZ3G4F9wbVGvXshYW9HW3o6quEoQDbFqB3%2BVOx03bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

-- 

Marcel Hlopko | Software Engineer | hlo...@google.com | 

Google Germany GmbH | Erika-Mann-Str. 33  | 80636 München | Germany | Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle | Registergericht und -nummer: Hamburg, HRB 86891

--

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/CAFuL9Gkp%2BJMjmZR8Vs0-SLKpcBiGr746T-r5-EAoqOJR%3DgM%2BSw%40mail.gmail.com.

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

--

Google Germany GmbH

Erika-Mann-Straße 33, 80636 München, Germany

[Derek Perez]

I am using this http://www.benf.org/other/cfr/ which has an --outputdir flag that generates a subtree that mirrors the classes it finds in a given jar. I then want to zip those up into a single output artifact, but I don't need to keep the cfr output dir tree.

What is the best way to do this?

On Mon, Jul 31, 2017 at 4:03 AM Dmitry Lomov <dsl...@google.com> wrote:

On Mon, Jul 31, 2017 at 11:38 AM, 'Marcel Hlopko' via bazel-discuss <bazel-...@googlegroups.com> wrote:

In a custom skylark rule? +Laurent Le Brun 

On Mon, Jul 31, 2017 at 5:18 AM Derek Perez <de...@perez.earth> wrote:

Is there a way in bazel to create a random temporary folder that is deleted when a target is finished being built?

No. Why do you need that?

In general, every file a rule creates is declared using ctx.actions.declare_file.

Bazel keeps all intermediate files to be as incremental as it can.

--
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/CAD7-yft3VZ3G4F9wbVGvXshYW9HW3o6quEoQDbFqB3%2BVOx03bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

-- 

Marcel Hlopko | Software Engineer | hlo...@google.com | 

Google Germany GmbH | Erika-Mann-Str. 33  | 80636 München | Germany | Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle | Registergericht und -nummer: Hamburg, HRB 86891

--
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.

[Austin Schuh]

mktemp -d ?  Blow it away when you are done, though the sandbox should (or can be configured) to map a tmpfs to /tmp/ so it goes away automatically.

Austin

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAD7-yftCMa%2BOn9OrQT1x5-CFqCNv%3DhkvSrPMSVoz1mPg%3Dna2MQ%40mail.gmail.com.

[Derek Perez]

OK That should be fine, Just wasn't sure if we had a better strategy that was builtin. I'm noticing sandboxing on MacOS is resulting in the files surviving across builds without explicitly rming the dir.

[Austin Schuh]

That is expected with sandboxing disabled.  Probably best to create the temporary data in ${TMPDIR} to be OS agnostic rather than /tmp/.

Austin

[Dmitry Lomov]

On Tue, Aug 1, 2017 at 5:36 AM, Derek Perez <de...@perez.earth> wrote:

I am using this http://www.benf.org/other/cfr/ which has an --outputdir flag that generates a subtree that mirrors the classes it finds in a given jar. I then want to zip those up into a single output artifact, but I don't need to keep the cfr output dir tree.

What is the best way to do this?

Another avenue you can try is ctx.actions.declare_directory. 

On Mon, Jul 31, 2017 at 4:03 AM Dmitry Lomov <dsl...@google.com> wrote:

On Mon, Jul 31, 2017 at 11:38 AM, 'Marcel Hlopko' via bazel-discuss <bazel-discuss@googlegroups.com> wrote:

In a custom skylark rule? +Laurent Le Brun 

On Mon, Jul 31, 2017 at 5:18 AM Derek Perez <de...@perez.earth> wrote:

Is there a way in bazel to create a random temporary folder that is deleted when a target is finished being built?

No. Why do you need that?

In general, every file a rule creates is declared using ctx.actions.declare_file.

Bazel keeps all intermediate files to be as incremental as it can.

--
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/CAD7-yft3VZ3G4F9wbVGvXshYW9HW3o6quEoQDbFqB3%2BVOx03bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

-- 

Marcel Hlopko | Software Engineer | hlo...@google.com | 

Google Germany GmbH | Erika-Mann-Str. 33  | 80636 München | Germany | Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle | Registergericht und -nummer: Hamburg, HRB 86891

--
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/CAFuL9Gkp%2BJMjmZR8Vs0-SLKpcBiGr746T-r5-EAoqOJR%3DgM%2BSw%40mail.gmail.com.

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

--

Google Germany GmbH

Erika-Mann-Straße 33, 80636 München, Germany

[Konstantin Solomatov]

Another avenue you can try is ctx.actions.declare_directory. 

And how does it work? Documentation doesn't provide all explanations. I have the following questions:

• Can other rules write there?
• Do I understand correctly that all rules which depend on files inside of it, will depend on the rule?

Thanks,

Kostya