Re: External CI Service Limitations
Azure pipeline vas the big plus of supporting Linux Windows and macos nodes And i think you can add you nodes to the pools Jeff Le mer. 3 juil. 2019 à 08:04, Allen Wittenauer a écrit : > > > On Jul 2, 2019, at 10:21 PM, Greg Stein wrote: > > > > We'll keep this list apprised of anything we find. If anybody knows of, > > and/or can recommend a similar type of outsourced build service ... we > > *absolutely* would welcome pointers. > > FWIW, we’ve been collecting them bit by bit into Apache Yetus ( > http://yetus.apache.org/documentation/in-progress/precommit-robots/ ): > > * Azure Pipelines > * Circle CI > * Cirrus CI > * Gitlab CI > * Semaphore CI > * Travis CI > > They all have some pros and cons. I’m not going to rank them or > anything. > > I will say, however, it really feels like Gitlab CI is the best > bet to pursue since one can add their own runners to the Gitlab CI > infrastructure dedicated to their own projects. That ultimately means that > replacing Jenkins slaves is a very real possibility. > > (Also, I’ve requested access to the Github Actions beta, but > haven’t received anything yet. I have a hunch that the reworking of the > OAuth permission model is related, which may make some of these more viable > for the ASF.)
Re: Build cache for Gradle: making builds and PR testing faster
You should use Jenkins to cache between builds Jeff Le sam. 28 déc. 2019 à 21:19, Vladimir Sitnikov a écrit : > Hi, > > Does anybody know if there's a Build Cache server for Gradle available in > ASF infrastructure? > > --- > > The use case is as follows: the server saves build artifacts (e.g. jars, > javadocs, etc), and > it helps to save build times on the repeated inputs. > > For instance, in a multi-module project, we could save time on rebuilding > non-modified modules. > In the same way, we don't need to verify code style if we have already > verified it for the same set of input files. > In the same way, we don't need to execute unit tests if we have already > executed tests for the same source base. > > The build cache would speedup build after a clean checkout, and it could > save developer's time (and PR testing time). > > --- > > There's a free implementation available > https://docs.gradle.com/build-cache-node/ (it is a Docker image) > > The suggested workflow is: > 1) Build cache is writable only from ASF infrastructure (e.g. from ASF > Jenkins job). > In other words, ASF Jenkins builds the project and updates the cache > 2) Everybody uses the cache in read-only mode, so they don't spend time on > what was already built by CI server. > > Vladimir >
Re: Build cache for Gradle: making builds and PR testing faster
Trying to get the use case Le dim. 29 déc. 2019 à 07:52, Vladimir Sitnikov a écrit : > >You should use Jenkins to cache between builds > > I want to reuse the same cache at developers' machines and at Travis / > GitHub Actions. > > Caching between Jenkins runs is not enough. > > Vladimir >
Job never schedules
Hello, I had a problem on one of my Jenkins job (MINA-trunk-jdk1.7-ubuntu) whose cause wa related to Maven installation on the slave. But since, the job is not more scheduled even if new commits have been pushed to Git ( https://builds.apache.org/job/MINA-trunk-jdk1.7-ubuntu/scmPollLog) Thanks Jeff -- Jeff MAURY "Legacy code" often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
Re: PDFBox not getting built automatically
Seems a lot of Apache jobs are not scheduled. Seems to be liked to SCM polling not done anymore. Jeff On Mon, May 19, 2014 at 6:05 PM, Tilman Hausherr wrote: > Hello, > > PDFBox is no longer getting built automatically. The last build is from > 14.5, my PMC chair triggered a manual build today. > > A look at https://builds.apache.org/computer/ shows a lot of red, and a > lot of build servers doing nothing. One build has been running for 16 hours. > > Tilman > > > -- Jeff MAURY "Legacy code" often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
[jira] [Created] (BUILDS-20) git tag randomly fails
Jeff MAURY created BUILDS-20: Summary: git tag randomly fails Key: BUILDS-20 URL: https://issues.apache.org/jira/browse/BUILDS-20 Project: Infra Build Platform Issue Type: Bug Components: Jenkins Reporter: Jeff MAURY We have a number of Jenkins job that have the option to create a Git tab when run. They randomly fail when the git tag command is run. See https://builds.apache.org/job/MINA-2.0.X-jdk1.5-ubuntu/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-20) git tag randomly fails
[ https://issues.apache.org/jira/browse/BUILDS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135174#comment-14135174 ] Jeff MAURY commented on BUILDS-20: -- Seems to be related to the Jenkins slave (appears when slave is on Jenkins cloud) > git tag randomly fails > -- > > Key: BUILDS-20 > URL: https://issues.apache.org/jira/browse/BUILDS-20 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins > Reporter: Jeff MAURY > Labels: git, jenkins, tag > > We have a number of Jenkins job that have the option to create a Git tab when > run. They randomly fail when the git tag command is run. > See https://builds.apache.org/job/MINA-2.0.X-jdk1.5-ubuntu/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (BUILDS-41) latest1.8 JDK fails to install on Windows
Jeff MAURY created BUILDS-41: Summary: latest1.8 JDK fails to install on Windows Key: BUILDS-41 URL: https://issues.apache.org/jira/browse/BUILDS-41 Project: Infra Build Platform Issue Type: Bug Components: Jenkins Reporter: Jeff MAURY I create a new job in order to compile latest MINA code on Windows and JDK 1.8. So I choose 'latest1.8' as the JDK. My job is available at https://builds.apache.org/view/M-R/view/MINA/job/MINA-trunk-jdk1.8-windows You can see the console log at: https://builds.apache.org/view/M-R/view/MINA/job/MINA-trunk-jdk1.8-windows/1/console -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-41) latest1.8 JDK fails to install on Windows
[ https://issues.apache.org/jira/browse/BUILDS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246532#comment-14246532 ] Jeff MAURY commented on BUILDS-41: -- I'm still getting errors. I understood Jenkins would have been restarted this week-end, has it been done ? > latest1.8 JDK fails to install on Windows > - > > Key: BUILDS-41 > URL: https://issues.apache.org/jira/browse/BUILDS-41 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins >Reporter: Jeff MAURY >Assignee: Andrew Bayer > Labels: jdk8, jenkins, windows > > I create a new job in order to compile latest MINA code on Windows and JDK > 1.8. So I choose 'latest1.8' as the JDK. My job is available at > https://builds.apache.org/view/M-R/view/MINA/job/MINA-trunk-jdk1.8-windows > You can see the console log at: > https://builds.apache.org/view/M-R/view/MINA/job/MINA-trunk-jdk1.8-windows/1/console -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-41) latest1.8 JDK fails to install on Windows
[ https://issues.apache.org/jira/browse/BUILDS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247976#comment-14247976 ] Jeff MAURY commented on BUILDS-41: -- Looks fine for me now, you can close the issue > latest1.8 JDK fails to install on Windows > - > > Key: BUILDS-41 > URL: https://issues.apache.org/jira/browse/BUILDS-41 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins > Reporter: Jeff MAURY >Assignee: Andrew Bayer > Labels: jdk8, jenkins, windows > > I create a new job in order to compile latest MINA code on Windows and JDK > 1.8. So I choose 'latest1.8' as the JDK. My job is available at > https://builds.apache.org/view/M-R/view/MINA/job/MINA-trunk-jdk1.8-windows > You can see the console log at: > https://builds.apache.org/view/M-R/view/MINA/job/MINA-trunk-jdk1.8-windows/1/console -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (BUILDS-65) No more space on Windows slaves
Jeff MAURY created BUILDS-65: Summary: No more space on Windows slaves Key: BUILDS-65 URL: https://issues.apache.org/jira/browse/BUILDS-65 Project: Infra Build Platform Issue Type: Bug Components: Jenkins Reporter: Jeff MAURY Jenkins builds jobs are failing because of no more space left on Windows slaves. See https://builds.apache.org/job/MINA-trunk-jdk1.7-windows/377 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-65) No more space on Windows slaves
[ https://issues.apache.org/jira/browse/BUILDS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375773#comment-14375773 ] Jeff MAURY commented on BUILDS-65: -- Build is failing now but for another reason: see https://builds.apache.org/job/MINA-trunk-jdk1.7-windows/382 > No more space on Windows slaves > --- > > Key: BUILDS-65 > URL: https://issues.apache.org/jira/browse/BUILDS-65 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins > Reporter: Jeff MAURY > > Jenkins builds jobs are failing because of no more space left on Windows > slaves. > See https://builds.apache.org/job/MINA-trunk-jdk1.7-windows/377 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
