Show proper error message on UI and in logs when re-run of an older version of a pipeline fails due to change in configuration

[pravds]

Steps to Reproduce

1. Create a pipeline which fetches artifact from ancestor pipeline and run it once (Run 1).
2. Now change pipeline configuration such that artifact is now fetched from different ancestor pipeline and run again (Run 2).
3. Go to Run 1 of pipeline and re-run stage.

Stack trace:

ERROR [92@MessageListener for WorkFinder] JMSMessageListenerAdapter:54 - Exception thrown in message handling by listener com.thoughtworks.cruise.server.messaging.scheduling.WorkFinder@17924f73
java.lang.NullPointerException
    at com.thoughtworks.cruise.server.service.builders.FetchTaskBuilder.resolveTargetJob(FetchTaskBuilder.java:76)
    at com.thoughtworks.cruise.server.service.builders.FetchTaskBuilder.createBuilder(FetchTaskBuilder.java:29)
    at com.thoughtworks.cruise.server.service.builders.FetchTaskBuilder.createBuilder(FetchTaskBuilder.java:25)
    at com.thoughtworks.cruise.server.service.builders.BuilderFactory.builderFor(BuilderFactory.java:47)
    at com.thoughtworks.cruise.server.service.builders.BuilderFactory.buildersForTasks(BuilderFactory.java:41)
    at com.thoughtworks.cruise.server.service.BuildAssignmentService$2.surrounding(BuildAssignmentService.java:188)
    at com.thoughtworks.cruise.server.transaction.TransactionTemplate.transactionSurrounding(TransactionTemplate.java:55)
    at com.thoughtworks.cruise.server.service.BuildAssignmentService.createWork(BuildAssignmentService.java:175)
    at com.thoughtworks.cruise.server.service.BuildAssignmentService.assignWorkToAgent(BuildAssignmentService.java:99)
    at com.thoughtworks.cruise.server.messaging.scheduling.BuildAssignmentServiceAssigner.assignWorkToAgent(BuildAssignmentServiceAssigner.java:28)
    at com.thoughtworks.cruise.server.messaging.scheduling.WorkFinder.onMessage(WorkFinder.java:34)
    at com.thoughtworks.cruise.server.messaging.scheduling.WorkFinder.onMessage(WorkFinder.java:13)
    at com.thoughtworks.cruise.server.messaging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessageListenerAdapter.java:49)
    at com.thoughtworks.cruise.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:34)
    at java.lang.Thread.run(Thread.java:662)

Actual Result

No message displayed on UI to indicate why pipeline did not trigger.

Expected Result

Proper error message should be displayed on UI and logs to indicate why pipeline did not trigger.

[stale]

This issue has been automatically marked as stale because it has not had activity in the last 90 days.
If you can still reproduce this error on the master branch using local development environment or on the latest GoCD Release, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.