Successfully exit upon path not existing

[minupalaniappan]

Love this tool; my hunch is that we can gracefully exit upon finding out that a path does not exist.

[jasonrudolph]

If the workflow instructs the action to look for the repository at a specific path using the repository-path input, and there is no directory at that location, that's almost certainly an error that the user would want to know about. I think we should continue to exit with a nonzero exit code here.

[jasonrudolph]

If I'm understanding the motivation correctly, you're hoping to gracefully handle the scenario where someone specifies multiple paths and some of those paths don't exist (as seen here).

But, there's no official support for specifying multiple paths. The path input is expected to contain exactly one path:

buildpulse-action/README.md

Lines 41 to 43 in c9db3ee

	### `path`
	**Required** The path to the XML file(s) for the test results. Can be a directory (e.g., `test/reports`), a single file (e.g., `reports/junit.xml`), or a glob (e.g., `app/*/results/*.xml`).

As seen in the error message in this build, the action terminated after discovering that the first path was nonexistent. It sounds like the user wants the action to continue on to process the remaining paths. If that is indeed the case, then changing the exit code here won't satisfy that goal. Instead, we'd need to enhance this action to explicitly support multiple paths.

To do that, we have a few options:

• Option 1: Iterate over the list of paths specified in the path input. For each path that exists on disk, invoke the buildpulse-test-reporter CLI with that path.
• Option 2: Copy all of the paths into a new shared location (e.g., /tmp/buildpulse-uploadables) and then invoke the buildpulse-test-reporter CLI with that single path.
• Option 3: Enhance the buildpulse-test-reporter to accept a list of paths instead of a single path.