Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-810

Make update center build logs available

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Component/s: ci
    • Labels:
      None
    • Similar Issues:

      Description

      With the recent infra refactorings, the update center job was moved into the secured Jenkins instance.

      While I totally understand the reasons, in that case this makes helping plugin developers harder, almost impossible actually.

      The typical question we have, as you know, is "I released my plugin and it's not available, did something go wrong?".

      Before, we were available to crawl the UC build logs to find out if, say, it was ignored because of a missing wiki page, and so on.

      Today, we're unable to analyse it and have to bother one of the admins to know more about that.

      I'm not (necessarily) asking for access to that private Jenkins instance, but more of any way we could make those logs securely accessible for everybody (to let people find out the solution by themselves, granted we document how to do it w/ the wiki).

      Thanks!

        Attachments

          Issue Links

            Activity

            batmat Baptiste Mathus created issue -
            Hide
            slide_o_mix Alex Earl added a comment -

            One thing to look out for on this is that some people (not me in this case) may raise a ruckus that infra for an open source project is not available to the community.

            Show
            slide_o_mix Alex Earl added a comment - One thing to look out for on this is that some people (not me in this case) may raise a ruckus that infra for an open source project is not available to the community.
            Hide
            rtyler R. Tyler Croy added a comment -

            Baptiste Mathus if there are tools or suggestions you would have to [r]sync job data from one Jenkins master to another, that would be relatively easy to set up.

            I have considered just making a "Trusted" folder on ci.jenkins.io and rsyncing jobs marked as disabled, and their console output there. If there's something that prevents some shell scripting on my part, that is reliable, that would definitely be nice.

            Show
            rtyler R. Tyler Croy added a comment - Baptiste Mathus if there are tools or suggestions you would have to [r] sync job data from one Jenkins master to another, that would be relatively easy to set up. I have considered just making a "Trusted" folder on ci.jenkins.io and rsyncing jobs marked as disabled, and their console output there. If there's something that prevents some shell scripting on my part, that is reliable, that would definitely be nice.
            rtyler R. Tyler Croy made changes -
            Field Original Value New Value
            Assignee R. Tyler Croy [ rtyler ]
            rtyler R. Tyler Croy made changes -
            Rank Ranked higher
            Hide
            batmat Baptiste Mathus added a comment -

            Setting up an ES server might be overkill I guess, even more if only for that? Cause if not we could probably push the logs using the Jenkins Logstash plugin?

            Show
            batmat Baptiste Mathus added a comment - Setting up an ES server might be overkill I guess, even more if only for that? Cause if not we could probably push the logs using the Jenkins Logstash plugin?
            Hide
            rtyler R. Tyler Croy added a comment -

            Setting up an ES server might be overkill I guess, even more if only for that? Cause if not we could probably push the logs using the Jenkins Logstash plugin?

            I believe Azure might offer some kind of turn-key solution here. I wouldn't want to implement this as a one-off just for the update center job, but I would be interested in making all build logs across all clusters searchable via Kibana.

            Do you have an idea of what kind of effort that would be?

            Show
            rtyler R. Tyler Croy added a comment - Setting up an ES server might be overkill I guess, even more if only for that? Cause if not we could probably push the logs using the Jenkins Logstash plugin? I believe Azure might offer some kind of turn-key solution here. I wouldn't want to implement this as a one-off just for the update center job, but I would be interested in making all build logs across all clusters searchable via Kibana. Do you have an idea of what kind of effort that would be?
            Hide
            batmat Baptiste Mathus added a comment -

            Depends on what your question relates to exactly.
            We have set up a RELK (Redis in front + ELK) installation in my current company for logs aggregation. We didn't fine tune anything, but I have used and configured logstash quite a few times (that cluster receives around 20 millions of lines of logs a week).

            I suppose that if Azure offers that solution, the only thing that would be left to us would be pushing the logs, right? In that case, I guess using logstash for that would be a no-brainer. Possibly, we would even want to use filebeat as it's designed to be lighter than logstash in terms of (memory, mostly) footprint.

            Show
            batmat Baptiste Mathus added a comment - Depends on what your question relates to exactly. We have set up a RELK (Redis in front + ELK) installation in my current company for logs aggregation. We didn't fine tune anything, but I have used and configured logstash quite a few times (that cluster receives around 20 millions of lines of logs a week). I suppose that if Azure offers that solution, the only thing that would be left to us would be pushing the logs, right? In that case, I guess using logstash for that would be a no-brainer. Possibly, we would even want to use filebeat as it's designed to be lighter than logstash in terms of (memory, mostly) footprint.
            integer Kanstantsin Shautsou made changes -
            Priority Minor [ 4 ] Blocker [ 1 ]
            Hide
            integer Kanstantsin Shautsou added a comment - - edited

            I would say it blocker as it doesn't allow plugin developers to have CD and understand even documented case https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter (keeping in mind wiki enforcement and other things).

            Show
            integer Kanstantsin Shautsou added a comment - - edited I would say it blocker as it doesn't allow plugin developers to have CD and understand even documented case https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter (keeping in mind wiki enforcement and other things).
            Hide
            rtyler R. Tyler Croy added a comment -

            Kanstantsin Shautsou, I agree that this is important. Are you volunteering to help or just setting the priorities for other contributors?

            Show
            rtyler R. Tyler Croy added a comment - Kanstantsin Shautsou , I agree that this is important. Are you volunteering to help or just setting the priorities for other contributors?
            Hide
            integer Kanstantsin Shautsou added a comment - - edited

            I can't debug why plugin is missing (though it seems missing only in root `update-center.json`), the same development blocking case may have anybody.

            As i mentioned in email (that in moderating queue) you can simply push logs with long existing jenkins feature https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs .

            Filebeat replaced logstash. In FOSS i see only ELK and graylog2 as good usable things. You would need to make clusters replicated for HA of course (with anti-affinity).

            Show
            integer Kanstantsin Shautsou added a comment - - edited I can't debug why plugin is missing (though it seems missing only in root `update-center.json`), the same development blocking case may have anybody. As i mentioned in email (that in moderating queue) you can simply push logs with long existing jenkins feature https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs . Filebeat replaced logstash. In FOSS i see only ELK and graylog2 as good usable things. You would need to make clusters replicated for HA of course (with anti-affinity).
            rtyler R. Tyler Croy made changes -
            Priority Blocker [ 1 ] Major [ 3 ]
            rtyler R. Tyler Croy made changes -
            Link This issue depends on INFRA-947 [ INFRA-947 ]
            danielbeck Daniel Beck made changes -
            Assignee Daniel Beck [ danielbeck ]
            rtyler R. Tyler Croy made changes -
            Rank Ranked higher
            Hide
            danielbeck Daniel Beck added a comment -

            Given that the need for this has largely been obsoleted since we got rid of the link to the wiki, I think we don't need this anymore. It's been a while since anyone asked about plugin availability.

            Show
            danielbeck Daniel Beck added a comment - Given that the need for this has largely been obsoleted since we got rid of the link to the wiki, I think we don't need this anymore. It's been a while since anyone asked about plugin availability.
            danielbeck Daniel Beck made changes -
            Resolution Won't Fix [ 2 ]
            Status Open [ 1 ] Closed [ 6 ]

              People

              Assignee:
              danielbeck Daniel Beck
              Reporter:
              batmat Baptiste Mathus
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: