Change By: Jason Smiley (16/Sep/14 2:11 PM)
Description: Currently I use Jenkins to run and read reports from Cucumber Test Jobs.

between this and the multi-jobs plugin, this is really great. In my setup, I have a master job which kicks off all test jobs, and then pulls in all the reports from the different test jobs (using this plugin) and then displays the results. 

However, due to the limitations of Jenkins, if a test fails, I cannot just re-run the suite with the failure as the report generated by the master job would be out of date (information is updated on the downstream job, but not the upstream job).

It would be great if downstream jobs could update artifacts for upstream jobs to keep everything in sync.


Job A Triggers Jobs B-F as downstream jobs. After jobs B-F finish, Job A pulls the artifacts from Jobs B-F to give a single report (found in Job A).

If Job B fails, its easier to re-run just Job B than all the Jobs via Job A. However, Job A artifacts will not be updated if I just run Job B. I would like Job B to automatically trigger Job A to pull in the latest artifact. Or at least have Job B
 trigger  push  the updates  for  to  Job A. 
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to