Due to it’s highly dynamic nature, there’s no fixed file path with static HTML or assets. You can access the rendered code via your browser’s developer tools. For instance, in Firefox navigate to the page and hit F12. This is all you will be able to see/access. Is there something in particular you were trying to find?
Hey Tony,
Sorry but unfortunately that’s not possible with Octopus. To better understand the problem you’re trying to solve, can you let me know what your use case is here?
Thanks,
Jeremy
I believe we actually already have this functionality built-in but it takes some slight setup. First, if you haven’t already, you will need to go to the Project in question and go to Variable->Library Sets, and include whichever sets you are wanting to reference in the release notes. Once you have done that and saved, you will then go to Settings inside the project and click “Release Notes Template”. In here you will place any text and variables that you want included in the release notes automatically. You will reference the variable by using this syntax #{VariableName} .
Please let me know if this implementation has the same functionality that you were looking to use, or if there was something extra or different than the above that you were looking to utilize.
I’ve pasted some screenshots of my reproduction below. First I went to the project itself and went to Variables->Library Sets and included the set I wanted to reference. I have made two variables, Test, and TestDupe. TestDupe will overlap with a project variable with the same name. This will show that Project variables take precedence over Library Set variables.
Finally, when creating a release I checked the output to make sure both variables are called and that the Project variable took precedence when there is a duplicate variable name.