Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-1595

Pipeline Library: Create build steps for Custom WAR Packager

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      https://github.com/jenkinsci/remoting/pull/265 introduces a working flow for integration testing which uses Custom WAR Packager together with runPCT() and runATH(). I am also working on few other flows, e.g. for Stapler.

      It would be great to have a customWARPackager global variable which allows invoking particular steps we need.

      Acceptance criteria:

      • customWARPackager.with() wrapper which installs Custom WAR packager executable JAR to the environment
      • customWARPackager.build() step which does the build and publishes artifacts on-demand
      • configuration via Metadata YML so that we can use a single file for runPCT()/runATH() and packaging settings
      • No pom.xml needed to build Custom WARs (Custom WAR Packager Maven plugin is not used)

        Attachments

          Issue Links

            Activity

            Hide
            oleg_nenashev Oleg Nenashev added a comment -
            Show
            oleg_nenashev Oleg Nenashev added a comment - CC Raul Arabaolaza
            Hide
            rarabaolaza Raul Arabaolaza added a comment - - edited
            • Allow using custom maven settings (for accessing maven repos for example)
            • Default value for configuration so metadata file can be minimal
            • Ability to share a local maven repo or local sources (so if I have locally built some artifacts I can include them in the war file)
            • Ability to override the version of the war packager to use (In case I need to do some modifications on the packager itself)
            • No op if no configuration is found in the metadata file, so it will not fail if there is a configuration file with ATH or PCT conf but not packager conf
            Show
            rarabaolaza Raul Arabaolaza added a comment - - edited Allow using custom maven settings (for accessing maven repos for example) Default value for configuration so metadata file can be minimal Ability to share a local maven repo or local sources (so if I have locally built some artifacts I can include them in the war file) Ability to override the version of the war packager to use (In case I need to do some modifications on the packager itself) No op if no configuration is found in the metadata file, so it will not fail if there is a configuration file with ATH or PCT conf but not packager conf
            Hide
            rarabaolaza Raul Arabaolaza added a comment -
            • JEP-305 support also will be quite interesting, although I understand this is part of war packager itself
            Show
            rarabaolaza Raul Arabaolaza added a comment - JEP-305 support also will be quite interesting, although I understand this is part of war packager itself
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            https://github.com/jenkins-infra/pipeline-library/pull/57 addresses the most of the requirements.

            The only one missing is "No op if no configuration is found in the metadata file, so it will not fail if there is a configuration file with ATH or PCT conf but not packager conf", but likely it is a subject for INFRA-1617. WDYT Raul Arabaolaza?

            Show
            oleg_nenashev Oleg Nenashev added a comment - https://github.com/jenkins-infra/pipeline-library/pull/57 addresses the most of the requirements. The only one missing is "No op if no configuration is found in the metadata file, so it will not fail if there is a configuration file with ATH or PCT conf but not packager conf", but likely it is a subject for INFRA-1617 . WDYT Raul Arabaolaza ?
            Hide
            rarabaolaza Raul Arabaolaza added a comment -

            Oleg Nenashev Yeah, makes sense, will do another PR Review ASAP

            Show
            rarabaolaza Raul Arabaolaza added a comment - Oleg Nenashev Yeah, makes sense, will do another PR Review ASAP

              People

              Assignee:
              oleg_nenashev Oleg Nenashev
              Reporter:
              oleg_nenashev Oleg Nenashev
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: