RFR: GitHub Actions [v2]

[Magnus Ihse Bursie]

I'd like to see some mention of the fickleness of the GHA testing. That 
it is prone to breakage that is not caused by changes in the JDK, but in 
the GHA runtime environment. And some emphasis that we do not control 
this environment, and that debugging this is hard. (Perhaps a 
recommendation that if any error pops up in GHA, that you try to 
reproduce it on an environment where you have better control; both if 
there is an actual bug, since it is easier to debug, and to verify if it 
really is an issue with the code and not the GHA environment.)

Or, to phrase it differently: by all means let people know how to enable 
it, but help them set reasonable expectations -- not just for how much 
(or rather, how little) is tested, but also for how stable the testing is.

/Magnus

On 2022-05-06 02:42, Jesper Wilhelmsson wrote:
>> Encouraging developers to enable GHA on their personal forks.
> Jesper Wilhelmsson has updated the pull request incrementally with one additional commit since the last revision:
>
>    Fix
>
> -------------
>
> Changes:
>    - all: https://git.openjdk.java.net/guide/pull/80/files
>    - new: https://git.openjdk.java.net/guide/pull/80/files/c52f302d..d2df771a
>
> Webrevs:
>   - full: https://webrevs.openjdk.java.net/?repo=guide&pr=80&range=01
>   - incr: https://webrevs.openjdk.java.net/?repo=guide&pr=80&range=00-01
>
>    Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod
>    Patch: https://git.openjdk.java.net/guide/pull/80.diff
>    Fetch: git fetch https://git.openjdk.java.net/guide pull/80/head:pull/80
>
> PR: https://git.openjdk.java.net/guide/pull/80