+1, makes sense
Romain Manni-Bucau @rmannibucau <https://x.com/rmannibucau> | .NET Blog <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> Javaccino founder (Java/.NET service - contact via linkedin) Le lun. 1 juin 2026, 21:30, Slawomir Jaranowski <[email protected]> a écrit : > Hi, > > I see that many of our jobs at Jenkins [1] are unstable ... > Looks like software on jenkins agents are not updated without a > separate issue for the infra team. > Examples jenkins use > - Maven 3.9.11 - there is 3.9.16, > - JDK 11 in version 11.0.24 - there is 11.0.31 > and so on ... > > We use Jenkins to deploy a snapshot version of projects and publish > content for the main site. > > Jenkins can not be used for verification of PR from fork repo. > Jenkins build status requires authorization. > > We have more of our builds on GitHub with PR verification. > We have some automation jobs implemented on GitHub actions [2] > It looks like ATR [3] is also based on GitHub actions. > > So I would like to start discussion about switching all CI jobs to > GitHub Actions. > > It will be easier to maintain one environment. > > Next step we can ask infra for dedicated GitHub runners instead of > Jenkins runners to increase stability. > > [1] https://ci-maven.apache.org/job/Maven/job/maven-box/ > [2] https://github.com/apache/maven-gh-actions-shared > [3] https://release-test.apache.org/ > > -- > Sławomir Jaranowski > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
