Because GO forces the user to specify the *entire* pipeline path, it is easy to end-up with something like this: "ancestorPipeline3/ancestorPipeline2/ancestorPipeline1..." This has already been logged as an issue here: http://support.thoughtworks.com/entries/22153596-usability-issue-fetching-artifacts-from-ancestor-pipelines
One of the gotchas that can cause you to spend time debugging is that GO does not process backslashes in this case, they need to be forward slashes else you will get a "Pipeline...tries to fetch artifact from stage...which does not exist. It is used in stage..."
GO should properly handle back or forward slashes throughout the system without the user having to care.
Please sign in to leave a comment.