Chad, thanks a lot for the quick and helpful response. Yes, currently to
deal with optional artifacts I create "wrapping" folders and put them there
(luckily GoCD can collect an empty artifact folder). It's just that while
doing this yet again I thought that if the purpose of this was only to fool
It's a reasonable question. Possible different way of thinking about this:
When you have varying numbers of artifacts that are related to one another,
put them in a directory together and artifact the whole directory as a
single artifact (on the upload side). That way it is not dependent on any
Can we come back to this point in 2024? Optional artifacts is a valid and
natural case and are common in other CI systems. For example, when running
tests I want to collect core dumps if they occur. Another example is a job
which depending on its input parameters produces a varying number of
