Re: Jenkins queue blockage
Am I reading this correctly? Nothing built on websites agent for 12 hrs: https://builds.apache.org/computer/websites/builds On 2020/01/14 11:24:44, Zoran Regvart wrote: > Hi builders, > could it have something to do with some builds tied to the `master` node[1]? > > I thought it was a bad practice to tie the executors on `master` node... > > zoran > > [1] https://builds.apache.org/computer/(master)/builds > > On Tue, Jan 14, 2020 at 7:12 AM Mike Jumper wrote: > > > Hi all, > > > > Is there a known issue currently affecting Jenkins? The build queue at the > > moment stands at 419 jobs and growing, yet it doesn't look like there are > > enough things running to account for the blockage. > > > > Checking the load statistics graph for Jenkins, it looks like things > > suddenly took a turn at around 23:00 UTC, with queue size increasing > > despite available executors going up and busy executors going down: > > > > https://builds.apache.org/load-statistics > > > > Thanks, > > > > - Mike > > > > > -- > Zoran Regvart >
Re: [ci-builds] - New Project Folder requests
Please create a folder for "Groovy". Thanks, Paul. On Sat, Jul 18, 2020 at 8:12 PM Gavin McDonald wrote: > Hi All, > > The Migrations thread is getting a bit large, so please any > new requests for Project Folder requests please either open > a new INFRA jira ticket or reply to this new thread > > Thanks > > -- > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team >
Re: [IMPORTANT] - Migration to ci-builds.a.o
I just tried the 'git-websites' label for Groovy. Worked without a glitch: https://ci-builds.apache.org/job/Groovy/job/Groovy%20dev%20website/1/ but about half the speed of before: https://builds.apache.org/view/E-G/view/Groovy/job/Groovy%20dev%20website/130/ Is that to be expected? It's not impacting us for this particular build but good to know in terms of expectations when we convert over some of the other builds. Cheers, Paul. On Wed, Jul 22, 2020 at 6:17 AM Roy Lenferink wrote: > The new build environment uses a so called ‘floating agent’ for deploying > websites. It is shared over different masters (ci-builds being one of them) > and will become available when using the ‘git-websites’ label. > > I already tested this for Celix and it works. > > See for examples: > - https://ci-builds.apache.org/job/Celix/job/site/job/master/4/console > - https://github.com/apache/celix-site/blob/master/Jenkinsfile#L22 > > Op di 21 jul. 2020 om 22:09 schreef Zoran Regvart > > > On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan > wrote: > > > I'm pushing to staging. > > > It should work for live I guess. > > > Have you tried and failed? > > > > > > > > > https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/live/3/console > > > > I did not, I was wondering if website nodes were missing so I would > > hold off until those were online. That build ran on ubuntu node, which > > on builds.a.o did not have the necessary credentials to push to git. > > > > zoran > > -- > > Zoran Regvart > > >
Re: Failure with Github Actions from outside of the organization (out of a sudden!)
Just picking out one point below. On Wed, Dec 30, 2020 at 12:47 PM Greg Stein wrote: > On Tue, Dec 29, 2020 at 8:08 PM Brennan Ashton > wrote: > [...] > TBH I don't see how the threat surface here is that much different > > than pulling down > > packages from pypi to npm at build time. > > > And that is why those packages should be pinned and checksums verified, > too. Do people do that? Nope. Should they? Yup. (and Infra falls into the > "we could do better, too"; not casting stones) > Not for npm packages, but rather Maven repo artifacts, we have just started using Gradle's dependency verification mechanism[1]. It allows you to check checksums and signatures of all downloaded artifacts against an accepted list. You can think of this as double accounting to verify artifacts that make their way into our builds. Other projects using Gradle (version 6.2 and above) might also like to consider using that. Cheers, Paul. [1] https://docs.gradle.org/current/userguide/dependency_verification.html
Re: Migration of Develocity to develocity.apache.org
Seems like the DEVELOCITY_ACCESS_KEY secret isn't set up? Or do projects need to request access to that (separate to GE_ACCESS_KEY access)? Cheers, Paul. On Fri, Jan 10, 2025 at 1:50 AM Clay Johnson wrote: > > Hi all, > > The Develocity server at ge.apache.org will be migrated to a new server > with a new URL, develocity.apache.org. This cutover is planned for January > 14th. > > Once the server is ready to accept new Build Scans on that day, we plan to > issue pull requests to all projects publishing Build Scans to migrate them > to the new URL. > > Thanks, > > Clay Johnson > Lead Solutions Engineer > Gradle > W. gradle.com > > -- > * > CONFIDENTIALITY NOTICE*: The contents of this email message, and any > attachments, are intended solely for the addressee(s) and may contain > confidential, proprietary and/or privileged information legally protected > from disclosure. If you are not the intended recipient of this > communication, or if you received this communication by mistake, please > notify the sender immediately and delete this message and any attachments. > If you are not the intended recipient, you are hereby notified that any > use, retransmission, dissemination, copying or storage of this message or > its attachments is strictly prohibited.
Re: Migration of Develocity to develocity.apache.org
Yes, indeed once merged, all seems great! On Wed, Jan 15, 2025 at 9:17 AM Clay Johnson wrote: > > I responded to the comment on your PR, but just so that all can see: The > PRs come from forks that cannot access the secret. We've verified on a few > repos now that the secret is accessible and properly authenticates to > develocity.apache.org. > > > Clay Johnson > Lead Solutions Engineer > Gradle > W. gradle.com > > > On Tue, Jan 14, 2025 at 4:26 PM Paul King wrote: > > > Seems like the DEVELOCITY_ACCESS_KEY secret isn't set up? Or do > > projects need to request access to that (separate to GE_ACCESS_KEY > > access)? > > > > Cheers, Paul. > > > > On Fri, Jan 10, 2025 at 1:50 AM Clay Johnson wrote: > > > > > > Hi all, > > > > > > The Develocity server at ge.apache.org will be migrated to a new server > > > with a new URL, develocity.apache.org. This cutover is planned for > > January > > > 14th. > > > > > > Once the server is ready to accept new Build Scans on that day, we plan > > to > > > issue pull requests to all projects publishing Build Scans to migrate > > them > > > to the new URL. > > > > > > Thanks, > > > > > > Clay Johnson > > > Lead Solutions Engineer > > > Gradle > > > W. gradle.com > > > > > > -- > > > * > > > CONFIDENTIALITY NOTICE*: The contents of this email message, and any > > > attachments, are intended solely for the addressee(s) and may contain > > > confidential, proprietary and/or privileged information legally protected > > > from disclosure. If you are not the intended recipient of this > > > communication, or if you received this communication by mistake, please > > > notify the sender immediately and delete this message and any > > attachments. > > > If you are not the intended recipient, you are hereby notified that any > > > use, retransmission, dissemination, copying or storage of this message or > > > its attachments is strictly prohibited. > > > > -- > * > CONFIDENTIALITY NOTICE*: The contents of this email message, and any > attachments, are intended solely for the addressee(s) and may contain > confidential, proprietary and/or privileged information legally protected > from disclosure. If you are not the intended recipient of this > communication, or if you received this communication by mistake, please > notify the sender immediately and delete this message and any attachments. > If you are not the intended recipient, you are hereby notified that any > use, retransmission, dissemination, copying or storage of this message or > its attachments is strictly prohibited.
[jira] [Reopened] (BUILDS-78) Creation of a Windows CI build agent for TeamCity
[ https://issues.apache.org/jira/browse/BUILDS-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul King reopened BUILDS-78: - > Creation of a Windows CI build agent for TeamCity > - > > Key: BUILDS-78 > URL: https://issues.apache.org/jira/browse/BUILDS-78 > Project: Infra Build Platform > Issue Type: Task > Components: Jenkins >Reporter: Paul King >Assignee: Gavin >Priority: Minor > > Groovy currently has a TeamCity CI server[1] (sponsored by JetBrains). It > performs builds of the codebase whenever changes are committed or pull > requests (PRs) are made on github. It runs on a linux server and supports > numerous JVM versions which are tested across the different Groovy branches. > We would like to add an additional build agent (a windows OS agent) into the > CI mix as well. Perhaps there is an INFRA box available that meets the > necessary criteria[2] that we could use for this purpose? Is this possible? > [1] http://ci.groovy-lang.org/?guest=1 > [2] > https://confluence.jetbrains.com/display/TCD8/Setting+up+and+Running+Additional+Build+Agents -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-78) Creation of a Windows CI build agent for TeamCity
[ https://issues.apache.org/jira/browse/BUILDS-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651177#comment-14651177 ] Paul King commented on BUILDS-78: - We use TeamCity not Jenkins. So I guess you don't have anything for us and we'll need to do that externally for the time being? > Creation of a Windows CI build agent for TeamCity > - > > Key: BUILDS-78 > URL: https://issues.apache.org/jira/browse/BUILDS-78 > Project: Infra Build Platform > Issue Type: Task > Components: Jenkins >Reporter: Paul King >Assignee: Gavin >Priority: Minor > > Groovy currently has a TeamCity CI server[1] (sponsored by JetBrains). It > performs builds of the codebase whenever changes are committed or pull > requests (PRs) are made on github. It runs on a linux server and supports > numerous JVM versions which are tested across the different Groovy branches. > We would like to add an additional build agent (a windows OS agent) into the > CI mix as well. Perhaps there is an INFRA box available that meets the > necessary criteria[2] that we could use for this purpose? Is this possible? > [1] http://ci.groovy-lang.org/?guest=1 > [2] > https://confluence.jetbrains.com/display/TCD8/Setting+up+and+Running+Additional+Build+Agents -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (BUILDS-78) Creation of a Windows CI build agent for TeamCity
[ https://issues.apache.org/jira/browse/BUILDS-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651177#comment-14651177 ] Paul King edited comment on BUILDS-78 at 8/2/15 9:33 PM: - We currently use TeamCity not Jenkins. So I guess you don't have anything for us and we'll need to do that externally for the time being? Also, is there a link for setting up Jenkins - we could set up a subset of our build on Jenkins in parallel with our TeamCity build for the time being. Are you aware of any projects which have set up automatic testing of PRs on Github on Apache's Jenkins setup? was (Author: paulk): We use TeamCity not Jenkins. So I guess you don't have anything for us and we'll need to do that externally for the time being? > Creation of a Windows CI build agent for TeamCity > - > > Key: BUILDS-78 > URL: https://issues.apache.org/jira/browse/BUILDS-78 > Project: Infra Build Platform > Issue Type: Task > Components: Jenkins >Reporter: Paul King >Assignee: Gavin >Priority: Minor > > Groovy currently has a TeamCity CI server[1] (sponsored by JetBrains). It > performs builds of the codebase whenever changes are committed or pull > requests (PRs) are made on github. It runs on a linux server and supports > numerous JVM versions which are tested across the different Groovy branches. > We would like to add an additional build agent (a windows OS agent) into the > CI mix as well. Perhaps there is an INFRA box available that meets the > necessary criteria[2] that we could use for this purpose? Is this possible? > [1] http://ci.groovy-lang.org/?guest=1 > [2] > https://confluence.jetbrains.com/display/TCD8/Setting+up+and+Running+Additional+Build+Agents -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-78) Creation of a Windows CI build agent for TeamCity
[ https://issues.apache.org/jira/browse/BUILDS-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653358#comment-14653358 ] Paul King commented on BUILDS-78: - replied on that thread > Creation of a Windows CI build agent for TeamCity > - > > Key: BUILDS-78 > URL: https://issues.apache.org/jira/browse/BUILDS-78 > Project: Infra Build Platform > Issue Type: Task > Components: Jenkins >Reporter: Paul King >Assignee: Gavin >Priority: Minor > > Groovy currently has a TeamCity CI server[1] (sponsored by JetBrains). It > performs builds of the codebase whenever changes are committed or pull > requests (PRs) are made on github. It runs on a linux server and supports > numerous JVM versions which are tested across the different Groovy branches. > We would like to add an additional build agent (a windows OS agent) into the > CI mix as well. Perhaps there is an INFRA box available that meets the > necessary criteria[2] that we could use for this purpose? Is this possible? > [1] http://ci.groovy-lang.org/?guest=1 > [2] > https://confluence.jetbrains.com/display/TCD8/Setting+up+and+Running+Additional+Build+Agents -- This message was sent by Atlassian JIRA (v6.3.4#6332)
