Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-13304

w_2018_03 release isn't

    Details

      Description

      There's no `w_2018_03` tag at https://eups.lsst.codes/stack/src/tags/?C=M;O=D.

        Attachments

          Issue Links

            Activity

            Hide
            ktl Kian-Tat Lim added a comment -

            Seems to be due to:

             
            org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.time.chrono.ChronoLocalDate format java.time.format.DateTimeFormatter

            Show
            ktl Kian-Tat Lim added a comment - Seems to be due to:   org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.time.chrono.ChronoLocalDate format java.time.format.DateTimeFormatter
            Hide
            jhoblitt Joshua Hoblitt added a comment - - edited

            The weekly-release-cron build failed due to some java 8 data/time methods needed to be white listed in the groovy security sandbox.  Sadly, there is no  jenkins "user" interface to automate setting these up as they are discovered in a testing env, or even a way to pre-emptively white list them before they cause a groovy sandbox failure.  I thought this had been taken care of because nightly-release-cron was working but the tag generation is done slightly differently.

            I'm going to leave this issue open until an upstream jenkins ticket has been opened requesting that the java8 date/time methods be added to the default whitelist.

            There is also a problem with the saved state from tarball construction that can result in a subsequent build [re]pushing eups distrib tags from another build.

            Show
            jhoblitt Joshua Hoblitt added a comment - - edited The weekly-release-cron build failed due to some java 8 data/time methods needed to be white listed in the groovy security sandbox.  Sadly, there is no  jenkins "user" interface to automate setting these up as they are discovered in a testing env, or even a way to pre-emptively white list them before they cause a groovy sandbox failure.  I thought this had been taken care of because nightly-release-cron was working but the tag generation is done slightly differently. I'm going to leave this issue open until an upstream jenkins ticket has been opened requesting that the java8 date/time methods be added to the default whitelist. There is also a problem with the saved state from tarball construction that can result in a subsequent build [re] pushing eups distrib tags from another build.
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            TL;DR - w_2018_03 went out yesterday afternoon.

            Show
            jhoblitt Joshua Hoblitt added a comment - TL;DR - w_2018_03 went out yesterday afternoon.
            Hide
            swinbank John Swinbank added a comment -

            Thanks for looking into this Josh!

            Show
            swinbank John Swinbank added a comment - Thanks for looking into this Josh!
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            A separate issue has been opened for the eups tag republishing problem (DM-13348).

            The w_2018_03 release now "is".

            Show
            jhoblitt Joshua Hoblitt added a comment - A separate issue has been opened for the eups tag republishing problem ( DM-13348 ). The w_2018_03 release now "is".

              People

              • Assignee:
                jhoblitt Joshua Hoblitt
                Reporter:
                swinbank John Swinbank
                Watchers:
                Eli Rykoff, John Swinbank, Joshua Hoblitt, Kian-Tat Lim
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: