For Kerby I just rely on GitHub Actions for the build, I don't really
need to use Jenkins:
https://github.com/apache/directory-kerby/blob/trunk/.github/workflows/pull-request-build.yaml

Colm.

On Thu, Oct 30, 2025 at 7:14 PM Shawn McKinney <[email protected]> wrote:
>
> Sorry, just now getting back to this. I must confess a general lack in 
> expertise in the automated builds. Stefan setup the Fortress builds for 
> ApacheDS and OpenLDAP, and I've been keeping them going. If we can carve off 
> a slice of this for me to work on, I'm willing to give er a go. Could be 
> getting project builds working with later JVMs. Let me know. Perhaps we hop 
> on the slack channel for a working sessions.
>
> Of course anyone else (hint someone other than you and me) who wants to jump 
> in is welcome. Especially someone with devops experience.
>
> On Thu, Oct 16, 2025 at 11:29 AM Emmanuel Lecharny <[email protected]> 
> wrote:
>>
>> Hi Shawn,
>>
>>
>> For LDAP API: we build for Java 11 and 17 (although 11 is failing due to
>> the checkstyle plugin that require a more recent version)
>>
>> For ApacheDS: Java 8, 11 and 17
>>
>> For Apache Mavibot: Java 8, 11 and 17
>>
>> For Apache Directory Studio: Java 11 and 17
>>
>> There is no Jenkinsfile for the other project (although it would be a
>> good idea to add them for Kerby, Scim and Fortress). And also fix the
>> failing ones plus add Java 21 and 25 too...
>>
>>
>>
>> On 10/16/25 15:53, Shawn McKinney wrote:
>> >
>> >> On Oct 16, 2025, at 7:14 AM, Emmanuel Lecharny <[email protected]> 
>> >> wrote:
>> >>
>> >> Hi !
>> >> This mail from the builds team will hit us deeply. We need to evaluate 
>> >> the possible impact on our projects, and act accordingly.
>> >>
>> >> Sadly, this is quite short notice, because it's before the end of october.
>> >>
>> > Does feel like short notice.
>> >
>> >> We have to check what is going to be the impact in teh coming days.
>> >>
>> > We need a list of affected projects. Once we know, perhaps divide it up 
>> > between us.
>> >
>> >> Thanks!
>> >>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to