Make it easy for anyone interested in this project to get the latest binaries (OpenAM war).
Solution
Attach the nightly tag to the build artifact and upload it to the openam-jp/openam/releases page.
Using GitHub-Actions cron triggers to rebuild the master branch source code every day.
Specifications Issues and Proposals
1. GitHub packages or source code
I think there are two options: "use the binaries in GitHub-Packages if they are available" and "build everything from source".
I selected "Build everything from source", because one of the important purposes of nightly build is to detect specification changes and situation changes of dependent libraries at an early stage, and easier to operate.
2. Dealing with http: protocol Maven repository URLs
Using the latest Maven, a build error will occur because the following two issues are unresolved.
By replacing http: where the problem occurs with https:, build errors can be avoided, so I implemented a simple ad-hoc patch.
I think it is appropriate to proceed with the above two issues after proper consideration.
Ad-hoc patches should be removed in the future when the root cause is resolved.
Analysis
257
Make it easy for anyone interested in this project to get the latest binaries (OpenAM war).
Solution
Attach the
nightly
tag to the build artifact and upload it to theopenam-jp/openam/releases
page. Using GitHub-Actions cron triggers to rebuild themaster
branch source code every day.Specifications Issues and Proposals
1. GitHub packages or source code
I think there are two options: "use the binaries in GitHub-Packages if they are available" and "build everything from source". I selected "Build everything from source", because one of the important purposes of nightly build is to detect specification changes and situation changes of dependent libraries at an early stage, and easier to operate.
2. Dealing with
http:
protocol Maven repository URLsUsing the latest Maven, a build error will occur because the following two issues are unresolved.
By replacing
http:
where the problem occurs withhttps:
, build errors can be avoided, so I implemented a simple ad-hoc patch. I think it is appropriate to proceed with the above two issues after proper consideration. Ad-hoc patches should be removed in the future when the root cause is resolved.