I know my step produces artifacts. I know they are located here:
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
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:
@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.
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events