We made some progress this week and after some back and forths we managed to build and deploy Optaplanner and Kogito Runtimes.
Next week we will continue the release process with Kogito Apps. On 2024/08/19 20:37:46 Rodrigo Antunes wrote: > The Nexus credentials were added to Jenkins today. > > We finally got a success build and deploy of Drools to the staging repository > :) > > We are now discussing with Apache Infra the best approach to retrieve the > dependencies from the staging repository as we have projects that depend on > each other and the download of the dependencies does not work out of the box. > > There will be some manual intervention needed. We have to close the the > staging repository that holds the previous release job artifacts (Drools) > before triggering the next release job (Optaplanner). This will also apply to > all the other release jobs we have. > > I'll add this information to the Release procedure document once we have > everything sorted out. > > On 2024/08/15 20:15:05 Rodrigo Antunes wrote: > > Quick status update: > > > > Yesterday we found that we can't use the nexus credentials we have to > > publish the release artifacts, so we requested Apache Infra team to provide > > us a robot account that allows to publish the release artifacts to the > > staging nexus repository. > > > > They are working on it and the credentials will be available for us > > tomorrow. > > > > In the mean time we also fixed a number of issues we found when running > > drools release job. > > > > I expect that tomorrow we finally will have a better luck running the > > release jobs. > > > > On 2024/08/13 20:34:37 Rodrigo Antunes wrote: > > > Update: > > > > > > We tried to run Drools release pipeline today and we found some issues > > > regarding to the GPG Signing configurations, conflicts between env vars > > > and utility functions, etc. We have fixed most of them and we will give > > > it another try tomorrow. > > > > > > On 2024/08/13 17:25:37 Rodrigo Antunes wrote: > > > > @Jason Porter > > > > My understanding is that we are going to publish all the artifacts in > > > > the staging repositories, then we are going to verify and test them. If > > > > it's all good we call a vote. > > > > > > > > On 2024/08/13 16:54:43 Jason Porter wrote: > > > > > Is this a trial run, or do we need to call a vote for 10? > > > > > > > > > > On 2024/08/13 12:55:19 ricardo zanini fernandes wrote: > > > > > > Thank you Rodrigo! Sounds great! > > > > > > > > > > > > On Tue, Aug 13, 2024 at 3:31 AM Luca Molteni <[email protected]> > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 12 Aug 2024, at 22:05, Rodrigo Antunes <[email protected]> > > > > > > > > wrote: > > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > We think we are all set to start running the release automation > > > > > > > > jobs[1] > > > > > > > for the Apache KIE 10 release that are going to produce the first > > > > > > > release > > > > > > > candidate artifacts and push them to Apache staging repositories > > > > > > > (maven and > > > > > > > svn). > > > > > > > > > > > > > > > > We are going to start with Drools tomorrow morning and if > > > > > > > > everything > > > > > > > goes well we will proceed with the rest of the pipelines. > > > > > > > > > > > > > > > > Issues are expected due to the amount of changes we had to make > > > > > > > > in the > > > > > > > pipeline scripts but we will be fixing them as we run the jobs in > > > > > > > the same > > > > > > > way we did with the branching pipelines. > > > > > > > > > > > > > > > > [1] Release procedures document (Automation D): > > > > > > > https://docs.google.com/document/d/1t-08b970i9PMBy-TSM64x0RUH46pzwnIhEi-LVeL0lg > > > > > > > > > > > > > > Good news > > > > > > > > > > > > > > Thank you Rodrigo > > > > > > > > > > > > > > Luca > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [email protected] > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
