Also I am not good at jenkins job builder. So if any people is good at jenkins job builder and willing to help the community to convert those jobs to use jenkins job builder, that would be great.
- Sijie On Mon, Jul 31, 2017 at 2:37 PM, Sijie Guo <guosi...@gmail.com> wrote: > Hi all, > > I added one CI job 'bookkeeper-postcommit-publish-website' to > automatically generate and publish the content to > bookkeeper.apache.org/test/content when changes are merged into master. > > The job is created here: > > - https://builds.apache.org/view/BK/job/bookkeeper- > postcommit-publish-website/configure > - the script run by CI added by https://github.com/apache/ > bookkeeper/pull/332 > > At the same time, I propose to organize the existing CI jobs as below > > - development: the ci jobs runs for development purpose > * bookkeeper-master (used for development, run nightly, verifying the > tests) > - precommit: the ci jobs runs before commit. it happens on pull requests. > * bookkeeper-precommit-pullrequests > - postcommit: the ci jobs runs after commit. it happens when there are > commits to the master branch. > * bookkeeper-postcommit-publish-website > - release: the ci jobs runs for release purpose. currently I created one > job for deploying artifacts nightly. > * bookkeeper-release-nightly-snapshot > > I updated the wiki page with this proposal : https://cwiki.apache.org/ > confluence/display/BOOKKEEPER/Continuous+Integration+Setup > > Any thoughts? > > - Sijie >
