Closed AntonyRileyAtVerto closed 3 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I am seeing the same issue, is there a workaround for this?
I suspect I'm probably missing something, but essentially I'm trying to do something like this:
We're using multibranch pipeline and the default workspace names have this horrible habit of causing build failures, I can't seem to find a way to set customWorkspace unless you use node {} with a label, which prohibits declaratively setting the memory.