Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-8378

systemd should restart jenkins master process

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Continuous Integration
    • Labels:
      None

      Description

      There have been at least 3 instances in the last ~month where the production jenkins master instance has exiting without any output in the log. While this problem needs to be resolved, it can be largely mitigated by having a monitor restart the master process. It should be fairly simple to accomplish this by converting the existing sysv init script into a proper systemd service unit.

        Attachments

          Issue Links

            Activity

            Hide
            jhoblitt Joshua Hoblitt added a comment -

            This work was started on Dec 23rd but not properly tracked in Jira due to maintenance being performed on jira itself.

            Show
            jhoblitt Joshua Hoblitt added a comment - This work was started on Dec 23rd but not properly tracked in Jira due to maintenance being performed on jira itself.
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            The production jenkins development has been updated to use systemd to monitor both the jenkins master and the el7 slaves.

            Show
            jhoblitt Joshua Hoblitt added a comment - The production jenkins development has been updated to use systemd to monitor both the jenkins master and the el7 slaves.

              People

              • Assignee:
                jhoblitt Joshua Hoblitt
                Reporter:
                jhoblitt Joshua Hoblitt
                Watchers:
                Frossie Economou, Joshua Hoblitt
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: