Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-37721

msi installer and winsw disagree about the service name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • packaging
    • None

      For custom distributions that use the packaging files and set a different ARTIFACTNAME from CamelArtifactName the MSI installer will create the service but jenkins will not be able to restart it as the service id in the winsw.xml file will not match what was installed.

      Ontop of this the name of the service should really be taken from the branding file as it exists.

      The windows service should be using ARTIFACTNAME but in order to keep upgrades working and given the service was installed with CamelArtifactName we need to keep using CamelArtifactName but make sure the service.xml file is changed appropriatly so that it matches.
      It looks like nothing actually attempts to change this and that it is doing this is an accident - and it is only working as the windows registry is case insensitive.

            Unassigned Unassigned
            teilo James Nord
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: