New "make check" job for Ceph pull requests

New "make check" job for Ceph pull requests

[Alfredo Deza]

Hi all,

As of yesterday (Tuesday Dec 22nd) we have the "make check" job
running within our CI infrastructure, working very similarly as the
previous check with a few differences:

* there are no longer comments added to the pull requests
* notifications of success (or failure) are done inline in the same
notification box for "This branch has no conflicts with the base
branch"
* All members of the Ceph organization can trigger a job with the
following comment:
    test this please

Changes to the job should be done following our new process: anyone can open
a pull request against the "ceph-pull-requests" job that configures/modifies
it. This process is fairly minimal:

1) *Jobs no longer require to make changes in the Jenkins UI*, they
are rather plain text YAML files that live in the ceph/ceph-build.git
repository and have a specific structure. Job changes (including
scripts) are made directly on that repository via pull requests.

2) As soon as a PR is merged the changes are automatically pushed to
Jenkins. Regardless if this is a new or old job. All one needs for a
new job to appear is a directory with a working YAML file (see links
at the end on what this means)

Below, please find a list to resources on how to make changes to a
Jenkins Job, and examples on how mostly anyone can provide changes:

* Format and configuration of YAML files are consumed by JJB (Jenkins
Job builder), full docs are here:
http://docs.openstack.org/infra/jenkins-job-builder/definition.html
* Where does the make-check configuration lives?
https://github.com/ceph/ceph-build/tree/master/ceph-pull-requests
* Full documentation on Job structure and configuration:
https://github.com/ceph/ceph-build#ceph-build
* Everyone has READ permissions on jenkins.ceph.com (you can 'login'
with your github account), current admin members (WRITE permissions)
are: ktdreyer, alfredodeza, gregmeno, dmick, zmc, andrewschoen,
ceph-jenkins, dachary, ldachary

If you have any questions, we can help and provide guidance and feedback. We
highly encourage contributors to take ownership on this new tool and make it
awesome!

Thanks,


Alfredo

Re: New "make check" job for Ceph pull requests

[Loic Dachary]

[-- Attachment #1: Type: text/plain, Size: 2787 bytes --]

Hi,

For the record the pending issues that prevent the "make check" job (https://jenkins.ceph.com/job/ceph-pull-requests/) from running can be found at http://tracker.ceph.com/issues/14172

Cheers

On 23/12/2015 21:05, Alfredo Deza wrote:
> Hi all,
> 
> As of yesterday (Tuesday Dec 22nd) we have the "make check" job
> running within our CI infrastructure, working very similarly as the
> previous check with a few differences:
> 
> * there are no longer comments added to the pull requests
> * notifications of success (or failure) are done inline in the same
> notification box for "This branch has no conflicts with the base
> branch"
> * All members of the Ceph organization can trigger a job with the
> following comment:
>     test this please
> 
> Changes to the job should be done following our new process: anyone can open
> a pull request against the "ceph-pull-requests" job that configures/modifies
> it. This process is fairly minimal:
> 
> 1) *Jobs no longer require to make changes in the Jenkins UI*, they
> are rather plain text YAML files that live in the ceph/ceph-build.git
> repository and have a specific structure. Job changes (including
> scripts) are made directly on that repository via pull requests.
> 
> 2) As soon as a PR is merged the changes are automatically pushed to
> Jenkins. Regardless if this is a new or old job. All one needs for a
> new job to appear is a directory with a working YAML file (see links
> at the end on what this means)
> 
> Below, please find a list to resources on how to make changes to a
> Jenkins Job, and examples on how mostly anyone can provide changes:
> 
> * Format and configuration of YAML files are consumed by JJB (Jenkins
> Job builder), full docs are here:
> http://docs.openstack.org/infra/jenkins-job-builder/definition.html
> * Where does the make-check configuration lives?
> https://github.com/ceph/ceph-build/tree/master/ceph-pull-requests
> * Full documentation on Job structure and configuration:
> https://github.com/ceph/ceph-build#ceph-build
> * Everyone has READ permissions on jenkins.ceph.com (you can 'login'
> with your github account), current admin members (WRITE permissions)
> are: ktdreyer, alfredodeza, gregmeno, dmick, zmc, andrewschoen,
> ceph-jenkins, dachary, ldachary
> 
> If you have any questions, we can help and provide guidance and feedback. We
> highly encourage contributors to take ownership on this new tool and make it
> awesome!
> 
> Thanks,
> 
> 
> Alfredo
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]