Hi all, Sorry about the spam, I opened a PR to try and improve the build flow for james documentation to try and get the staged documentation published automatically after each build of james project.
Unfortunately the Jenkinsfile currently in the staging branch of james-site is out of date (the JDK name has changed) and It took me these 5 tries to realize that none of the changes I was making to the Jenkinsfile were accounted for because: ‘Jenkinsfile’ has been modified in an untrusted revision I'm not sure what the best way to proceed is : this limitation can be disabled (would be easiest since I may have further adjustments to make), or an official apache committer can push to an alternate PR to get it to build with the changes. Note that in this change I have also changed the email notifications to only notify the list for the live and staging branches and notify the requester for other branches. best regards jean On Thu, Apr 1, 2021 at 9:43 PM Apache Jenkins Server < [email protected]> wrote: > BUILD-UNSTABLE: Job 'james/ApacheJames-Website/PR-3 [PR-3] [5]': > > Check console output at "<a href=" > https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/PR-3/5/";>james/ApacheJames-Website/PR-3 > [PR-3] [5]</a>" > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected]
