[jira] [Created] (BUILDS-98) https://builds.apache.org unreachable
Daan Hoogland created BUILDS-98: --- Summary: https://builds.apache.org unreachable Key: BUILDS-98 URL: https://issues.apache.org/jira/browse/BUILDS-98 Project: Infra Build Platform Issue Type: Bug Components: Jenkins Reporter: Daan Hoogland since a while only the default ubuntu apache http is reachable on port 80 at builds.a.o no 443 and no jenkins -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (BUILDS-98) https://builds.apache.org unreachable
[ https://issues.apache.org/jira/browse/BUILDS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Bayer reassigned BUILDS-98: -- Assignee: Andrew Bayer > https://builds.apache.org unreachable > - > > Key: BUILDS-98 > URL: https://issues.apache.org/jira/browse/BUILDS-98 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins >Reporter: Daan Hoogland >Assignee: Andrew Bayer > > since a while only the default ubuntu apache http is reachable on port 80 at > builds.a.o > no 443 and no jenkins -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-98) https://builds.apache.org unreachable
[ https://issues.apache.org/jira/browse/BUILDS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633218#comment-14633218 ] Andrew Bayer commented on BUILDS-98: Puppet seems to have broken stuff. Working on it. > https://builds.apache.org unreachable > - > > Key: BUILDS-98 > URL: https://issues.apache.org/jira/browse/BUILDS-98 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins >Reporter: Daan Hoogland >Assignee: Andrew Bayer > > since a while only the default ubuntu apache http is reachable on port 80 at > builds.a.o > no 443 and no jenkins -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (BUILDS-98) https://builds.apache.org unreachable
[ https://issues.apache.org/jira/browse/BUILDS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Bayer resolved BUILDS-98. Resolution: Fixed And we're back. > https://builds.apache.org unreachable > - > > Key: BUILDS-98 > URL: https://issues.apache.org/jira/browse/BUILDS-98 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins >Reporter: Daan Hoogland >Assignee: Andrew Bayer > > since a while only the default ubuntu apache http is reachable on port 80 at > builds.a.o > no 443 and no jenkins -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-98) https://builds.apache.org unreachable
[ https://issues.apache.org/jira/browse/BUILDS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633248#comment-14633248 ] Daan Hoogland commented on BUILDS-98: - tnx Andrew > https://builds.apache.org unreachable > - > > Key: BUILDS-98 > URL: https://issues.apache.org/jira/browse/BUILDS-98 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins >Reporter: Daan Hoogland >Assignee: Andrew Bayer > > since a while only the default ubuntu apache http is reachable on port 80 at > builds.a.o > no 443 and no jenkins -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (BUILDS-98) https://builds.apache.org unreachable
[ https://issues.apache.org/jira/browse/BUILDS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland closed BUILDS-98. --- works like a charm (if those work at all anything like builds.a.o) > https://builds.apache.org unreachable > - > > Key: BUILDS-98 > URL: https://issues.apache.org/jira/browse/BUILDS-98 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins >Reporter: Daan Hoogland >Assignee: Andrew Bayer > > since a while only the default ubuntu apache http is reachable on port 80 at > builds.a.o > no 443 and no jenkins -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (BUILDS-99) Working copy in kafka Jenkins PR job needs merge
Ismael Juma created BUILDS-99: - Summary: Working copy in kafka Jenkins PR job needs merge Key: BUILDS-99 URL: https://issues.apache.org/jira/browse/BUILDS-99 Project: Infra Build Platform Issue Type: Task Reporter: Ismael Juma All builds are failing because the working copy has an unresolved conflict. For example: https://builds.apache.org/job/kafka-trunk-git-pr/18/ It would be good to fix the working copy, but even better would be to change the config so that this kind of issue doesn't happen again (if possible). It seems like this issue was triggered by this pull request that tries to merge `trunk` into `0.8.1`: https://github.com/apache/kafka/pull/42 Seems like an accidental pull request. We can't close it and the author is unresponsive. Any chance you can close it? Or do I need to file a separate INFRA issue for that? Thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (BUILDS-99) Working copy in kafka Jenkins PR job needs merge
[ https://issues.apache.org/jira/browse/BUILDS-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Bayer reassigned BUILDS-99: -- Assignee: Andrew Bayer > Working copy in kafka Jenkins PR job needs merge > > > Key: BUILDS-99 > URL: https://issues.apache.org/jira/browse/BUILDS-99 > Project: Infra Build Platform > Issue Type: Task >Reporter: Ismael Juma >Assignee: Andrew Bayer > > All builds are failing because the working copy has an unresolved conflict. > For example: > https://builds.apache.org/job/kafka-trunk-git-pr/18/ > It would be good to fix the working copy, but even better would be to change > the config so that this kind of issue doesn't happen again (if possible). > It seems like this issue was triggered by this pull request that tries to > merge `trunk` into `0.8.1`: > https://github.com/apache/kafka/pull/42 > Seems like an accidental pull request. We can't close it and the author is > unresponsive. Any chance you can close it? Or do I need to file a separate > INFRA issue for that? > Thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-99) Working copy in kafka Jenkins PR job needs merge
[ https://issues.apache.org/jira/browse/BUILDS-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633631#comment-14633631 ] Andrew Bayer commented on BUILDS-99: I've wiped out the workspace and set the job up to always do that and force a fresh clone. And I've closed that PR. > Working copy in kafka Jenkins PR job needs merge > > > Key: BUILDS-99 > URL: https://issues.apache.org/jira/browse/BUILDS-99 > Project: Infra Build Platform > Issue Type: Task >Reporter: Ismael Juma >Assignee: Andrew Bayer > > All builds are failing because the working copy has an unresolved conflict. > For example: > https://builds.apache.org/job/kafka-trunk-git-pr/18/ > It would be good to fix the working copy, but even better would be to change > the config so that this kind of issue doesn't happen again (if possible). > It seems like this issue was triggered by this pull request that tries to > merge `trunk` into `0.8.1`: > https://github.com/apache/kafka/pull/42 > Seems like an accidental pull request. We can't close it and the author is > unresponsive. Any chance you can close it? Or do I need to file a separate > INFRA issue for that? > Thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-99) Working copy in kafka Jenkins PR job needs merge
[ https://issues.apache.org/jira/browse/BUILDS-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633633#comment-14633633 ] Ismael Juma commented on BUILDS-99: --- Awesome. Thanks so much for the fast reaction. :) > Working copy in kafka Jenkins PR job needs merge > > > Key: BUILDS-99 > URL: https://issues.apache.org/jira/browse/BUILDS-99 > Project: Infra Build Platform > Issue Type: Task >Reporter: Ismael Juma >Assignee: Andrew Bayer > > All builds are failing because the working copy has an unresolved conflict. > For example: > https://builds.apache.org/job/kafka-trunk-git-pr/18/ > It would be good to fix the working copy, but even better would be to change > the config so that this kind of issue doesn't happen again (if possible). > It seems like this issue was triggered by this pull request that tries to > merge `trunk` into `0.8.1`: > https://github.com/apache/kafka/pull/42 > Seems like an accidental pull request. We can't close it and the author is > unresponsive. Any chance you can close it? Or do I need to file a separate > INFRA issue for that? > Thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (BUILDS-99) Working copy in kafka Jenkins PR job needs merge
[ https://issues.apache.org/jira/browse/BUILDS-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Bayer resolved BUILDS-99. Resolution: Fixed > Working copy in kafka Jenkins PR job needs merge > > > Key: BUILDS-99 > URL: https://issues.apache.org/jira/browse/BUILDS-99 > Project: Infra Build Platform > Issue Type: Task >Reporter: Ismael Juma >Assignee: Andrew Bayer > > All builds are failing because the working copy has an unresolved conflict. > For example: > https://builds.apache.org/job/kafka-trunk-git-pr/18/ > It would be good to fix the working copy, but even better would be to change > the config so that this kind of issue doesn't happen again (if possible). > It seems like this issue was triggered by this pull request that tries to > merge `trunk` into `0.8.1`: > https://github.com/apache/kafka/pull/42 > Seems like an accidental pull request. We can't close it and the author is > unresponsive. Any chance you can close it? Or do I need to file a separate > INFRA issue for that? > Thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Triggering CI rebuilds for GitHub pull requests
Hi, At Kafka, we intend to change our contribution flow to be based on GitHub pull requests. An important part of this flow is running CI builds on pull requests. The basics are now working[1] thanks to Andrew Bayer's help. I have a few questions that I could not find an answer for (if this is information is already available somewhere, a reference is appreciated) and I was hoping that someone here could help: 1. Is it possible to trigger a rebuild with "retest this please"? 2. Who is allowed to trigger a rebuild? Is it any committer or only those with access to Jenkins? 3. Can we use "add to whitelist" to add another user to the authorised list? 4. Out of curiosity, are we using https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin or something custom? Normally, I would just figure it out by trying these things, but I am not a committer and I don't have access to Jenkins, which makes things a bit harder! Thanks, Ismael [1] https://builds.apache.org/job/kafka-trunk-git-pr/
[jira] [Commented] (BUILDS-85) Could not generate DH keypair / peer not authenticated
[ https://issues.apache.org/jira/browse/BUILDS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633900#comment-14633900 ] Dennis Lundberg commented on BUILDS-85: --- I am not proposing to disable forward secrecy completely. Only the ciphers that are now deemed less secure. If you disable the TLS_DHE_* ciphers on the SSL proxy, you will disable some ciphers that support forward secrecy, but not all of them. You still have the TLS_ECDHE_* ciphers enabled that modern clients will use. > Could not generate DH keypair / peer not authenticated > --- > > Key: BUILDS-85 > URL: https://issues.apache.org/jira/browse/BUILDS-85 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins >Reporter: Andreas Lehmkühler >Assignee: Geoffrey Corey > Attachments: SSLPoke.java > > > We're getting this since june 10th: > [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ pdfbox-parent --- > Downloading:https://repository.apache.org/content/repositories/snapshots/org/apache/pdfbox/pdfbox-parent/1.8.10-SNAPSHOT/maven-metadata.xml > [WARNING] Could not transfer metadata > org.apache.pdfbox:pdfbox-parent:1.8.10-SNAPSHOT/maven-metadata.xml from/to > apache.snapshots.https > (https://repository.apache.org/content/repositories/snapshots): Error > transferring file: java.lang.RuntimeException: Could not generate DH keypair > and this: > [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ pdfbox-parent > --- > Downloading:https://repository.apache.org/content/repositories/snapshots/org/apache/pdfbox/pdfbox-parent/2.0.0-SNAPSHOT/maven-metadata.xml > [WARNING] Could not transfer metadata > org.apache.pdfbox:pdfbox-parent:2.0.0-SNAPSHOT/maven-metadata.xml from/to > apache.snapshots.https > (https://repository.apache.org/content/repositories/snapshots): peer not > authenticated > The issue seems to be jdk related as only those builds using java 1.6.0_37 > (unlimited security) are failing. I've reconfigured the trunk build to use > java 7 and everything works fine, as well as our jdk7 based branch build. > Any ideas? Maybe a plugin update which doesn't work with java6? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BUILDS-86) Provide a recent 1.7 or 1.8 jdk with unlimited security
[ https://issues.apache.org/jira/browse/BUILDS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633985#comment-14633985 ] Andreas Lehmkühler commented on BUILDS-86: -- Any update on this? I'd like to remove the limitation to ubuntu3. > Provide a recent 1.7 or 1.8 jdk with unlimited security > --- > > Key: BUILDS-86 > URL: https://issues.apache.org/jira/browse/BUILDS-86 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins >Reporter: Andreas Lehmkühler > > PDFBox can't use the 1.6 based jdk with unlimited security any more (see > BUILDS-85). The installed 1.7.0_79 version isn't available on all host (at > least not on ubuntu) > Please provide either a recent JDK 1.7 or 1.8 including unlimited security on > ubuntu. > I'm happy to help if necessary/possible -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Potential Power loaner hardware for CI purposes
So to followup on this. I met with Lance from OSUOSL last night. OSUOSL currently has power and cooling capacity to take on additional Power nodes - but not in our existing racks. They are currently running a small private cloud with Power, and offered that they could essentially take hardware, allocate a quota to us, and just provide us with API access rather than us having to manage hardware and manage a new arch (a cost that OSUOSL staffers have already paid), we can then consume that compute capacity via the API. On Tue, Jun 16, 2015 at 3:54 PM, David Nalley wrote: > I'll need to reach out to OSU and see what we have available in terms > of cooling/power available (frankly I don't know that we have much > left). Hadoop sounds like an interested party. > > > > On Mon, Jun 15, 2015 at 3:48 PM, Sam Ruby wrote: >> IBM has loaner hardware that could be targeted towards that CI >> infrastructure, assuming the ASF has sufficient floor space/cooling/etc. >> and are willing to integrate Power into our CI infrastructure. >> >> If there is interest, let me know and I will connect the right parties >> together to discuss the details. >> >> - Sam Ruby
