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

Update Jenkinsfiles in libraries to use infra.runMaven() with Azure settings

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Many components implement Maven builds on their own at the moment. It leads to performance degradation, e.g. when Azure mirror settings are not used or timeouts are not defined. It would be great to migrate all these calls to a standard implementation based on infra.runMaven(). INFRA-1459 can be also used

        Attachments

          Issue Links

            Activity

            oleg_nenashev Oleg Nenashev created issue -
            oleg_nenashev Oleg Nenashev made changes -
            Field Original Value New Value
            Epic Link INFRA-2401 [ 203830 ]
            oleg_nenashev Oleg Nenashev made changes -
            Description Many components implement Maven builds on their own at the moment. It leads to performance degradation, e.g. when Azure mirror settings are not used or timeouts are not defined. It would be great to migrate all these calls to a standard implementation
            oleg_nenashev Oleg Nenashev made changes -
            Description Many components implement Maven builds on their own at the moment. It leads to performance degradation, e.g. when Azure mirror settings are not used or timeouts are not defined. It would be great to migrate all these calls to a standard implementation Many components implement Maven builds on their own at the moment. It leads to performance degradation, e.g. when Azure mirror settings are not used or timeouts are not defined. It would be great to migrate all these calls to a standard implementation 
            oleg_nenashev Oleg Nenashev made changes -
            Description Many components implement Maven builds on their own at the moment. It leads to performance degradation, e.g. when Azure mirror settings are not used or timeouts are not defined. It would be great to migrate all these calls to a standard implementation  Many components implement Maven builds on their own at the moment. It leads to performance degradation, e.g. when Azure mirror settings are not used or timeouts are not defined. It would be great to migrate all these calls to a standard implementation based on infra.runMaven(). INFRA-1459 can be also used
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is related to INFRA-1459 [ INFRA-1459 ]
            oleg_nenashev Oleg Nenashev made changes -
            Component/s winstone-jetty [ 20645 ]
            Component/s pipeline-library [ 23622 ]
            Key INFRA-2403 JENKINS-60606
            Workflow classic default workflow [ 241232 ] JNJira + In-Review [ 241236 ]
            Project Infrastructure [ 10301 ] Jenkins [ 10172 ]
            oleg_nenashev Oleg Nenashev made changes -
            Component/s remoting [ 15489 ]
            Show
            oleg_nenashev Oleg Nenashev added a comment - Examples: https://github.com/jenkinsci/remoting/pull/364 https://github.com/jenkinsci/winstone/pull/85

              People

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

                Dates

                Created:
                Updated: