Uploaded image for project: 'Jenkins Website'
  1. Jenkins Website
  2. WEBSITE-806

Update and release pipeline-metadata-utils

    XMLWordPrintable

Details

    Description

      As part of the GSoC code cleanup, we determined that it would be really useful for other projects to potentially use the power of the plugin manager without starting a whole Jenkins in other infra projects. There was an effort to pull out the code a few years ago, and this would be a great time to update and release an initial version. Then after this is updated, we can use it from the pipeline-steps-doc-generator.

      The existing repo: https://github.com/jenkins-infra/pipeline-metadata-utils

      At this time, it might be useful to make sure there's good documentation around the different classes for people who would be interested in this later.

      Definition of Done:

      • the repo updated with the most recent pluginmanager stuff
      • comments updated in the repo
      • release of the pipeline-metadata-utils package
      • update the pipeline-steps-doc-generator to use the new pipeline-metadata-utils

       

      Edit (7th July 2022):

      The first release was done successfully, and the artifact can be found on the Jenkins maven artifactory.

      To do:

      • Enabling CD
      • Adding tests
      • Clean build command in Jenkinsfile

      Attachments

        Activity

          vihaanthora Vihaan Thora added a comment - - edited

          We can use incrementalify to publish the artifact to repo.jenkins-ci.org as an incremental.

          This will require us to inherit from the parent pom first. After doing so, there seems to be an error in running mvn install in the MockJenkins.java and MockExtensionLists.java files (perhaps due to the difference in the Java versions 8 –> 11). So, we first need to work on fixing this error.

           

          vihaanthora Vihaan Thora added a comment - - edited We can use incrementalify to publish the artifact to repo.jenkins-ci.org as an incremental . This will require us to inherit from the parent pom first. After doing so, there seems to be an error in running mvn install in the MockJenkins.java and MockExtensionLists.java files (perhaps due to the difference in the Java versions 8 –> 11). So, we first need to work on fixing this error.  
          vihaanthora Vihaan Thora added a comment -

          It is better to move the entire pipeline steps generator codebase to Java 11.

           

          vihaanthora Vihaan Thora added a comment - It is better to move the entire pipeline steps generator codebase to Java 11.  
          vihaanthora Vihaan Thora added a comment - PR and tasks at https://github.com/jenkins-infra/pipeline-metadata-utils/pull/1  
          vihaanthora Vihaan Thora added a comment - Added tests in https://github.com/jenkins-infra/pipeline-metadata-utils/pull/14

          People

            vihaanthora Vihaan Thora
            kwhetstone Kristin Whetstone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: