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 artifacts (optional debug files, logs, reports or similar). The necessity to make dummy artifacts in all such cases only to satisfy GoCD internal logic is troublesome and disturbing. Could you please consider adding an "optional" attribute of the artifact element?
четверг, 25 июня 2015 г. в 20:10:09 UTC+6, Aravind SV: > On Thu, Jun 25, 2015 at 7:19 AM, Pat McGrath <[email protected]> wrote: > >> So it seems unless you generate content the job will fail, is it possible >> to indicate that the artifact is optional ? >> > > No. :( The artifact declaration is a contract, something the downstream > pipelines can depend on. > > You can have a final task which creates dummy files, I suppose. But, that > feels like cheating. If a downstream pipeline uses it, then it will need to > validate that it is not a dummy file. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/aa2762ac-18e9-4fff-a7bc-37a7a92be694n%40googlegroups.com.
