No instructions on how to repackage TB after creating new build

[OpenZSD]

Need to repackage TB after introducing some new features, but I don't know how to package a build that's built with Bazel with a bunch of symlinks in the output directory. In this particular case the target OS is centOS. Any chance a "how to repackage" could be added to docs.

[manivaradarajan]

That's a good idea. Would you mind describing what features you've added to TB? That would be helpful information.

[OpenZSD]

Not sure I can disclose that as it's particular to the research team. Basically I'm picking up work from a contractor that left a year prior. The issue I have is I'm stuck between a rock and a hard place as the servers are limited to what sources it can install from meaning Bazel can't be installed. So instructing the researchers to clone the branch and build is impractical. So the problem I have is I don't know how the whl file was produced for this project. The last contractor didn't leave instructions on producing it.

[nfelt]

You can run bazel run //tensorboard/pip_package:extract_pip_package to generate the .whl file and extract it to a temporary directory. See https://github.com/tensorflow/tensorboard/tree/master/tensorboard/pip_package for more details.

[manivaradarajan]

Here are instructions on generating a whl. We'll ensure there are instructions in a good place:

rm -rf /tmp/tb_pips
mkdir /tmp/tb_pips
bazel run //tensorboard/pip_package:extract_pip_package -- \
    /tmp/tb_pips
ls /tmp/tb_pips/*.whl

(Instructions mentioned in #3331)

[OpenZSD]

Thanks! That did the job. You guys are awesome! Should I close this, or will there be a task to add this to DEVELOPMENT.md?

[manivaradarajan]

Let's keep it open so I can update the documentation. Glad it worked out!