jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "Oakathon May 2019" by MarcelReutegger
Date Wed, 15 May 2019 15:41:50 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The "Oakathon May 2019" page has been changed by MarcelReutegger:
https://wiki.apache.org/jackrabbit/Oakathon%20May%202019?action=diff&rev1=31&rev2=32

  
  Further progress/work is tracked in https://issues.apache.org/jira/browse/JCR-4435
  
+ == CI/CD ==
+ 
+ One option for running additional non-Apache integration tests would be to fork the Jackrabbit
Oak GitHub mirror, create feature branches and work on those branches until a change is ready.
Then a PR back to the fork could trigger additional integration tests that act as an additional
quality gate until the change is committed back to the Apache SVN. The last step would still
be manual. The development workflow can potentially be simplified if the Oak code base was
on GitHub. Then it might be possible to further automate the process by automatically triggering
a PR against the Oak origin on GitHub when the fork applied a validated PR with the additional
external integration tests. The final PR obviously would still have to pass all Oak unit and
integration tests.
+ 
+ Moving the code base to GitHub seems to make it easier for a developer even if there are
some manual steps needed to get a change into Oak. It would make the use of git-svn obsolete.

+ 

Mime
View raw message