zipkin-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [incubator-zipkin-website] jcchavezs commented on issue #5: fix: reenables the zipkin-api filter.
Date Sat, 27 Apr 2019 09:34:55 GMT
jcchavezs commented on issue #5: fix: reenables the zipkin-api filter.
URL: https://github.com/apache/incubator-zipkin-website/pull/5#issuecomment-487271090
 
 
   Makes sense. My experience with triggering other jobs over jenkins hasn’t
   been great but it is fair to say I only dealt with manual created jobs and
   an old version of Jenkins. I will give it a try over the weekend.
   
   lør. 27. apr. 2019 kl. 11:08 skrev Zoltán Nagy <notifications@github.com>:
   
   > Yeah, agree putting a component in between two Jenkins jobs seems
   > unnecessary, Jenkins jobs can trigger each other. I don't have a strong
   > preference between "Jenkins/api triggers Jenkins/website" and "Jenkins/api
   > pushes into GitHub/website", both are slightly clunky.
   >
   > —
   > You are receiving this because you authored the thread.
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/incubator-zipkin-website/pull/5#issuecomment-487269422>,
   > or mute the thread
   > <https://github.com/notifications/unsubscribe-auth/AAXOYARSG7V7VJ3BHFIVGKTPSQJXNANCNFSM4HIUUUFQ>
   > .
   >
   --
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message