Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [birt-dev] Build Infrastructure
  • From: Wim Jongman <wim.jongman@xxxxxxxxxxxxxxxxxx>
  • Date: Thu, 4 Mar 2021 10:44:31 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wyn3Rwza9GxYhG0aJIfdzNEDe3gZQ0Kba3mBYVxgqH0=; b=PDHGW8G4/5FMWTcLdiIZwYlSa71I+3zOCfOQ5KSNElOE5MoALYB+ICqac8kOmSHdX9TY4XcbDfYQfDmstp0Jqm2u9pToRkRR0kNOGBT3661eCC9Cr2p6iBWttB80nzv7g90iZ3BgRj13oyUXSna+9HKRk2+DcfOEF4YZ7aDYdYU8wbbLiS3a4tO6Du4ivZ+l4OwaOI/SWeM1EbcnDtXev0Rz9bIT6EiRT6vL5WIQZXF8cts069lsjFZJnxTyBRl4t+LaVsxmYaFM0/tnZyuwsXrYQEVqNXxFJOMqqRa9YOSmUHhNl7USnNXCzhzyzTTXZDKZ1sfBcEaohijNrMoFeA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=h1qUOFt/HZ5orM8GQWIyPr5bTBVeeAnuAzV8QOmXJnxMW1l10/Qs3G85W3rfb29l7jegcZVDDNd3y1DP0t1T/YCinZoj4iGa53luEFFaXncT/VJ7xCCeZB7P8mEg+WBGJpmCMEzKwg74LUfIEkzIqUXhX7o4yBWX4OGUK0g4NZ5xA2J5iEte6KR1muFbn/Kc63Yb37DT1isEBMZNrgwrZZb7LwzaEbi4AntBglM9baVutYNwqzPePiiYceqpq5rj1uDT4+HZF1bCf90cCliB80p03RNNYBTIFVVt+Bdu4C4kDddoSJzmFPFwySBrpExq/zPhIFcKS64C0TrjDMRYOA==
  • Delivered-to: birt-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Thread-index: AQHXEHnA0hlV5nqil0ez+8pBXskCmqpy5SQAgACIToCAADXbQA==
  • Thread-topic: [birt-dev] Build Infrastructure

I just looked into GitHub Actions and the BIRT JIPP. Seems I misunderstood how they work together (they don't). If we stay on JIPP for building we might need this to integrate with GitHub:

@Wim since you mentioned GitHub Actions: Did you suggest running two distinct build processes, one on JIPP and one on github? Shouldn't we stick to either?


Not distinct build processes but different engines running the same build. In the end, all it should take is


  mvn clean verify


to build. Whether this is local or Actions or Jenkins, it should not matter.


* move to a pom-less tycho build?

Pom-less depends on the shape of the repository. Sometimes pom-less can be confusing. I’m not against it but we should see what is the best fit for the repo.


* use a target platform definition file with tycho, which can be loaded into the IDE as well -> makes IDE and maven build consistent

Yes. The main build should work with the “latest” repositories for Platform, the release train, and Orbit.


How to go on from here? I would open issues for those points in github and create/reopen pull requests which address them.



Back to the top