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

VERSION Column on Mysql is too small

    Details

    • Similar Issues:

      Description

      mysql ddl contains:

      VERSION varchar(56) NOT NULL,

      However, per definition, Maven versions can be up to 100 characters long (in hsql, ist VARCHAR(256) btw).

      Since we encode branch names in our version, we break that 56 character boundry.

      This column should conform to Maven rules for versions.

        Attachments

          Activity

          Hide
          pauxus Stephan Pauxberger added a comment -

          Neither was I, but I got an Exception citing exactly this limit. Therefore a clipped my branch names - with a quick check, however, I was not able to reproduce the issue nor to find the source of the exception. Unfortunately, I did not copy the stacktrace, so it might also have been a plugin, but the message clearly stated that Maven versions must not be longer than 100 characters. I will keep looking.

          Show
          pauxus Stephan Pauxberger added a comment - Neither was I, but I got an Exception citing exactly this limit. Therefore a clipped my branch names - with a quick check, however, I was not able to reproduce the issue nor to find the source of the exception. Unfortunately, I did not copy the stacktrace, so it might also have been a plugin, but the message clearly stated that Maven versions must not be longer than 100 characters. I will keep looking.
          Hide
          cleclerc Cyrille Le Clerc added a comment -

          I have successfully tested the following fix on "MySQL 8.0.13" and on "MySQL 5.6.10 / Amazon Aurora 1.17.7"

          ALTER TABLE MAVEN_ARTIFACT MODIFY COLUMN VERSION varchar(100);
          UPDATE VERSION SET VERSION = 12;
          

          I am investigating, I think that I tried a while ago on a version of MySQL that didn't support such a long index IDX_MAVEN_ARTIFACT based on (GROUP_ID, ARTIFACT_ID, VERSION, TYPE)

          Show
          cleclerc Cyrille Le Clerc added a comment - I have successfully tested the following fix on "MySQL 8.0.13" and on "MySQL 5.6.10 / Amazon Aurora 1.17.7" ALTER TABLE MAVEN_ARTIFACT MODIFY COLUMN VERSION varchar (100); UPDATE VERSION SET VERSION = 12; I am investigating, I think that I tried a while ago on a version of MySQL that didn't support such a long index IDX_MAVEN_ARTIFACT based on (GROUP_ID, ARTIFACT_ID, VERSION, TYPE)
          Hide
          cleclerc Cyrille Le Clerc added a comment -

          Fixed in pipeline-maven-3.6.8-beta-1 , Stephan Pauxberger can you please test?

          Release and release notes:
          https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.8-beta-1

          Show
          cleclerc Cyrille Le Clerc added a comment - Fixed in pipeline-maven-3.6.8-beta-1 , Stephan Pauxberger can you please test? Release and release notes: https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.8-beta-1
          Hide
          cleclerc Cyrille Le Clerc added a comment -

          fixed in 3.6.8

          Show
          cleclerc Cyrille Le Clerc added a comment - fixed in 3.6.8
          Hide
          pauxus Stephan Pauxberger added a comment -

          Thanks and sorry for not answering, last weeks were pretty full...

          Show
          pauxus Stephan Pauxberger added a comment - Thanks and sorry for not answering, last weeks were pretty full...

            People

            • Assignee:
              cleclerc Cyrille Le Clerc
              Reporter:
              pauxus Stephan Pauxberger
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: