> So, what specifically needs to be done?

#1 from my perspective: We need support for build pipelines. In particular

```
var ide = buildIDEZip();
var testDist = buildTestDistributionZip();

var moduleSet = [ "platform", "ide", "hints1", "hints2" ];
var jdkSet = [ "jdk8", "jdk11", "jdk17", "jdk-latest" ];

new ForkJoinPool("many parallel executors") (module, jdk) {
   setup jdk

   unzip ide
   unzip testDist

   teste module  
}
```

Can that be implemented (easily) in Travis? Not likely. Can that be 
implemented easily in GitHub actions (that'd be great, but I doubt). Can that 
be implemented in `Jenkinsfile`? Probably.

Can somebody prototype it? That'd be great.
-jt


Dne neděle 26. září 2021 19:01:03 CEST, Eric Bresie napsal(a):
> I know there have been discussions in the past on CI builds issues like
> [1], [2]. [3], [4], [5], "Build Strategies" [6], and time on the builds [7]
> but...
> 
> It seems some build jobs are done on GitHub commits, Travis CI, Jenkins,
> etc.  Assume some of this is dependent on the type of jobs and tests (OS or
> capability focus), and the infrastructure and available resources involved
> (i.e. Apache CI-Jenkins across Apache projects, GitHub build [across apache
> projects], Travis CI [assume constrained in some way]).
> 
> So, what specifically needs to be done?
> 
> Do the types of jobs need to be grouped and run by intent/needs in an
> applicable CI environment?
> Do the types of jobs need to be migrated into a single place (i.e. Github,
> Travis, Jenkins, etc.)?
> 
> Eric Bresie
> ebre...@gmail.com
> 
> References
> [1]
> https://lists.apache.org/thread.html/r944d5e9e79b6abdf9337293f417c3b51229e8b
> 7d7989833028328359%40%3Cdev.netbeans.apache.org%3E [2]
> https://lists.apache.org/thread.html/rcddd3063fb087fb894eeea38b6c555c802c441
> 2e15a27ada1b4dccbe%40%3Cdev.netbeans.apache.org%3E [3]
> https://lists.apache.org/thread.html/r3d55f95ee5dc6383a4330ee2cf4cf98785149d
> f461063330bd1cb535%40%3Cdev.netbeans.apache.org%3E [4]
> https://lists.apache.org/thread.html/r7937df039aea7254d6d6f0847e47a1bb3f14ee
> 603d97bed58e8f7ccc%40%3Cdev.netbeans.apache.org%3E [5]
> https://lists.apache.org/thread.html/r22e89737af4b1c0808d6f06385e5fd00c37a6b
> 435e7a81cf06619501%40%3Cdev.netbeans.apache.org%3E [6]
> https://lists.apache.org/thread.html/rcdcb7a718c01fec2796bdb472e979a8900c346
> efb9aebcc6024e31b9%40%3Cdev.netbeans.apache.org%3E [7]
> https://lists.apache.org/thread.html/r8694f9ca65746542f1ee1c73c219f17acea5a5
> 27f5809d5c68394de6%40%3Cdev.netbeans.apache.org%3E
> 
> On Sat, Sep 25, 2021 at 1:52 AM Jaroslav Tulach <jaroslav.tul...@gmail.com>
> 
> wrote:
> > Dne pátek 24. září 2021 17:25:39 CEST, Eric Barboni napsal(a):
> > > Hi,
> > > 
> > > I juste retrieved an old mail for Jaroslav.
> > 
> > ;-)
> > 
> > > I'm a bit "irritated" because of
> > > CI. I'm haunted  by the "restart job button".
> > 
> > I can live with the "restart button", but I agree: Such frequent failures
> > aren't professional.
> > 
> > > Is a only Apache jenkins build + PR review something we can do ?
> > > or would we have some limitation and should rely also on GA or travis
> > 
> > too?
> > 
> > > Hector started something https://github.com/apache/netbeans/pull/2443
> > 
> > to do
> > 
> > > jenkins PR test.
> > > 
> > > BUT on jenkins
> > > This build trigger test error:
> > > https://ci-builds.apache.org/job/Netbeans/job/netbeans-linux/
> > > ant build test-platform build-nbms generate-uc-catalog build-source-zips
> > > => 1 issue on
> > > org.openide.filesystems.annotations.LayerBuilderTest.testSourcePath The
> > > same ant call on my ubuntu
> > > => 0 issue
> > > 
> > > Complicated to trust jenkins too.
> > > But I would like to see the CI issues tackled so Release
> > 
> > Manager,commiter,
> > 
> > > reviewers may have better life :D. ------
> > 
> > +1
> > 
> > My original may was however about "test distribution" - e.g. build the IDE
> > and
> > the test distribution once, and then use it for running the tests across
> > different nodes.
> > 
> > Yes, Jenkins pipelines (on Apache own infra) would be ideal for that I
> > think.
> > -jt
> > 
> > > -----Message d'origine-----
> > > De : Jaroslav Tulach <jaroslav.tul...@gmail.com>
> > > Envoyé : lundi 26 avril 2021 06:16
> > > À : dev@netbeans.apache.org
> > > Cc : Petr Zajac <petr.za...@gmail.com>
> > > Objet : Using test distribution & Apache's Jenkins pipelines was: Time
> > > it
> > > takes for Test PHP Cluster
> > > 
> > > Dne pátek 16. dubna 2021 18:53:31 CEST, Tomáš Procházka napsal(a):
> > > > I stareted conversion of other jobs
> > > > (https://github.com/apache/netbeans/pull/2708) but stopped given
> > > > current status of Github Actions
> > > > (https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+sta
> > > > tus)
> > > 
> > > Hello guys,
> > > maybe there is a time to improve the structure of build jobs and to
> > 
> > increase
> > 
> > > the throughput by eliminating duplicated tasks.
> > > 
> > > These days every job builds the IDE, builds the tests and then it
> > 
> > executes
> > 
> > > some tests. We can do better than that! There has been a "test
> > > distribution" in NetBeans for years and according to its creator Petr
> > > Zajac, it is still working!
> > > 
> > > It would be good to have one job that builds the ZIP of the IDE and
> > 
> > builds
> > 
> > > the ZIP for the test distribution. Only then other "testing" jobs are
> > > started, download the two ZIP files and use them to perform the tests
> > 
> > only.
> > 
> > > Btw. When at it, shouldn't we consider to use
> > 
> > https://ci-builds.apache.org/
> > 
> > > ? It is an infrastructure that fully runs on Apache's hardware - e.g. we
> > > aren't going to be influenced deals with external providers like Travis
> > 
> > or
> > 
> > > Azure. Moreover Jenkins supports pipelines to pass the ZIPs from one job
> > 
> > to
> > 
> > > another...
> > > 
> > > Together we can save the planet!
> > > -jt
> > > 
> > > 
> > > 
> > > 
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > > For additional commands, e-mail: dev-h...@netbeans.apache.org
> > > 
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > > 
> > > 
> > > 
> > > 
> > > 
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > > For additional commands, e-mail: dev-h...@netbeans.apache.org
> > > 
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.apache.org
> > 
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Reply via email to