Hi @Tony and welcome to the community!
The path that you mentioned is the clone directory. Pipelines builds run in Docker containers. For every step of your pipeline, a Docker container starts, the repo is cloned in that container in the path /opt/atlassian/pipelines/agent/build/, and then the commands of the step's script are executed in that directory. When the commands finish successfully, or if a certain command fails, then the Docker container gets destroyed. The clone directory is exposed in the variable BITBUCKET_CLONE_DIR.
If you want to see a file generated during the build:
1) You can use the following pipe in the step that generates this file, in order to upload it to the Downloads page of the repository:
You can then download the file from the Downloads page.
Please keep in mind though that if a subsequent build generates and uploads a file with the same name, the existing file will get overwritten. You can work around this by giving give a unique name to the file in each build e.g. by including the build number in the file name (exposed in the variable BITBUCKET_BUILD_NUMBER) or you could upload the file to an external storage solution.
2) You can use a cat command in your yml file in order to view the content of the file in the Pipelines build log.
3) We have a test reporting feature in Pipelines that shows test results in a separate tab in the Pipelines build log, if they include a fail. Please note that this only works currently with JUnit and Maven Surefire XML formats, regardless of the language they are written in, and the xml files need to be generated in specific directories. You can find more details here:
If you have any questions, please feel free to let me know.
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.