bitbucket_pipelines.yml:
https://bitbucket.org/snippets/gdmacmillan/EMj8zg
create_doc.sh
https://bitbucket.org/snippets/gdmacmillan/kA6Ed7
I know my step produces artifacts. I know they are located here:
/opt/atlassian/pipelines/agent/build/doc/master/master
from using command `echo "$(realpath $1/$1)"`
confirmed with ls `$1/$1`
They aren't showing up in the artifacts tab in the UI. They show up in the artifacts tab when i just comment everything below `cd doc && make html 2>&1`
The create_doc file was adapted from a reference implementation for travis
EDIT:
my issue appears related to how the artifacts spec is parsed in the yaml. The artifacts tab shows up if i explicitly set branch name like:
artifacts:
- doc/master/master/**
@gdmacmillan , I can't guarantee that my answer is 100% correct, but the reason for such behavior might be that some libraries and tools don't expand bash variables when evaluating glob patterns. So basically your doc/$BITBUCKET_BRANCH/** doesn't expand to doc/master/<whatever> when you define an artifact. I can envision a simple workaround with using only a doc/** as an artifact definition. In that case there is no expansion needed and artifacts will still be present. Let me know if this works for you.
That actually did it. I could have sworn i tried that before but oh well. Many thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Alexander Zhukov I know you helped me with a previous question, hopefully you can help solve this as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.