eclipse-jdt/eclipse.jdt.core

Add aggregator build as github validation step

Open

#1,917 opened on Jan 26, 2024

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Java (183 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (233 stars)
PR merge metrics
 (PR metrics pending)

Description

See comment from @laeubi on https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/issues/1750#issuecomment-1911818888

Tycho uses a (quick) build of the aggregator to catch > issues early, maybe JDT can use similar to be aware of such unanticipated changes when compiler is fixed, but its just an idea, total > runtime is about 17 minutes.

The idea is: new github action could be added to JDT PR validation workflow at github. The action would run SDK aggregator build with latest ecj state from PR. This would allow contributors see if the change in compiler "breaks" SDK build before actual nightly SDK build fails.

Contributions are welcome.

Contributor guide

Research direction
Set up a GitHub Actions workflow that runs the SDK aggregator build with the latest ECJ state from the PR. Look at the existing Tycho workflow for reference.
Tech stack
java
Domain
ci cdbuild systemdevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitHub ActionsMaven
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50