Details

    • Type: Story Story
    • Status: Closed
    • Priority: Major Major
    • Resolution: Completed
    • Affects Version/s: 6.1.0 CE RC1, 6.2.0 CE M2
    • Fix Version/s: 6.1.0 CE RC1
    • Component/s: WCM
    • Labels:
    • Similar Issues:
      Show 5 results 

      Description

      When inspecting a customer or user's system, it is useful to know exactly which build they have, in case we need to do source-level debugging using a stack trace or other information from the system.

      It would be nice to have a stamp on each and every build so that we know when it was created and the exact source code revision from which the binaries were produced.

      The following information would be useful:

      Date and time of build
      Liferay version
      git revision information
      svn revision information
      Java compiler information

      Basically, as much information about the build as possible, to aid in debugging or identifying the Liferay build the customer has.

      This would be generated during the build, and could be placed in a text file in the distro, separate from the generated .WAR files.

        Activity

        Hide
        James Falkner added a comment -

        Yeah I think this is sorely missing - no way to know how to map a customer system to our source.

        There's also the problem of fix packs that will alter the binaries, but the patching system has a separate way of identifying which fixpacks have been applied.

        Show
        James Falkner added a comment - Yeah I think this is sorely missing - no way to know how to map a customer system to our source. There's also the problem of fix packs that will alter the binaries, but the patching system has a separate way of identifying which fixpacks have been applied.
        Hide
        Kiyoshi Lee added a comment -

        FAILED Manual Testing using the following steps:

        1. Open MANIFEST.MF in portal-impl.jar, util-bridges.jar,
          util-java.jar, util-taglib.jar
        2. Assert that build information is recorded

        Failed on:
        Tomcat 7.0 + MySQL 5. 6.1.x GIT ID: 70469e2e3ec0f73064e55d509e7675a85395c2bd.
        Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 9e0865d52edc0f3b2fa3e4c97dece7f7ed4296f2.

        Liferay-Portal-Build-Revision is not recorded in any of the files, all other info is recorded as expected.

        Show
        Kiyoshi Lee added a comment - FAILED Manual Testing using the following steps: Open MANIFEST.MF in portal-impl.jar, util-bridges.jar, util-java.jar, util-taglib.jar Assert that build information is recorded Failed on: Tomcat 7.0 + MySQL 5. 6.1.x GIT ID: 70469e2e3ec0f73064e55d509e7675a85395c2bd. Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 9e0865d52edc0f3b2fa3e4c97dece7f7ed4296f2. Liferay-Portal-Build-Revision is not recorded in any of the files, all other info is recorded as expected.
        Hide
        Raymond Auge added a comment -

        Mike this has actually been implemented. Can you move this along?

        Show
        Raymond Auge added a comment - Mike this has actually been implemented. Can you move this along?
        Hide
        Michael Saechang added a comment -

        Yup - will get Kiyoshi to retest.

        Thanks

        Show
        Michael Saechang added a comment - Yup - will get Kiyoshi to retest. Thanks
        Hide
        Kiyoshi Lee added a comment -

        PASSED Manual Testing following the steps in the above comment.

        Fixed on:
        Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: ef9dad2fdec1063a3f0a3b7cc9da248231983d9b.

        Show
        Kiyoshi Lee added a comment - PASSED Manual Testing following the steps in the above comment. Fixed on: Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: ef9dad2fdec1063a3f0a3b7cc9da248231983d9b.

          People

          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development

                Structure Helper Panel