Hi Gergely,

I am also running into the same issue. The part I am confused about is that 
archiving and fingerprinting the timestamp.data in the parent project can 
only be a 'post build' action. So when the downstream project is configured 
to copy from upstream it will not find it since it wont be archived until 
Parent job 'build' phase is completed. How were you able to archive and 
fingerprint timestamp.data before the downstream projects were triggered. 
Please post the ink for your blog post if possible. Thanks

below is the error I get in the downstream project

*15:51:14* Unable to access upstream artifacts area 
/var/lib/jenkins/jobs/parent-job/builds/1686/archive. Does source project 
archive artifacts?
*15:51:14* ERROR: Failed to copy artifacts from parent-job with filter: 
timestamp.data




On Friday, September 18, 2015 at 8:32:19 AM UTC-4, Gergely Brautigam wrote:
>
> I understand now everything!! 
>
> It's working. And it's awesome. Thanks very much. It all became suddenly 
> so clear how this aggregate plug-in works. :) It makes sense now. I shall 
> write a blog post about it. 
>
> All I did was add an echo `date` > timestamp.data. Fingerprinted this 
> data, and on the downstream projects said => copy from upstream project. 
> And that made the link between the two clear and the aggregate test result 
> now has a build from which to gather data from. 
>
> What I did wrong was that, in the upstream job I waited for the 
> downstreams to finish. And that was wrong!
>
> Cheers!
> Gergely
>
> On Friday, 18 September 2015 08:54:44 UTC+2, Gergely Brautigam wrote:
>>
>> Btw. What did you mean by, simple artefact such as a timestamp? What's a 
>> timestamp as an artefact? :) 
>>
>> On Friday, 18 September 2015 07:05:00 UTC+2, Gergely Brautigam wrote:
>>>
>>> And that would be enough to create the connection between the two jobs? 
>>> Even though there are no tests performed on the timestamp? The connection 
>>> is enough? I'll try to do that once I get to work. Thank you very much for 
>>> the suggestion! :-) 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8f2152e2-7361-4535-89a5-b79ddef91dee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to