Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3194

udi: lombok :: use fetch-artifacts for lombok jar

XMLWordPrintable

    • False
    • None
    • False
    • Not Required

      The UDI image includes lombok, which we build in a container in Jenkins and then publish to GH releases.

      https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-8/devspaces-udi/get-sources.sh

      These zips are then unpacked and simply copied into the target image:

      https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-8/devspaces-udi/Dockerfile

      Could use cachito w/o a package manager to simply fetch sources from the GH project (and a commit SHA) so that the sources are available in the downstream repo at build time.

      -https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-8/devspaces-udi/build/build_lombok.sh#L73-L86-

      ... but that looks like a lot of pain for a single small jar.

      Instead, we should switch to adding a fetch-artifacts-url.yaml file to the mid and downstream repos, per the docs

      https://osbs.readthedocs.io/en/latest/users.html#fetch-artifacts-url-yaml

      and simply reuse https://repository.jboss.org/nexus/service/local/repositories/central/content/org/projectlombok/lombok/1.18.22/lombok-1.18.22.jar (or newer pull from some other RH acceptable location like https://maven.repository.redhat.com/ga/org/projectlombok/lombok/index.html [which only has 1.18.12 right now])

      ... and attach sources too, if possible.

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Max Leonov Max Leonov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: