Page History

...

Automated tests ensures that your feature will not be regressed.  Anyone who submits a code change that breaks an existing automated test is responsible for fixing that automated test or revert the code change. 

Q&A

Q: I'm a contributor and not a committer.  How do I participate in this process?

A: We will attempt to add a way to pull the source code from github as well.  In the mean time, you should submit your changes as a patch via the review board.  A reviewer will start a branch, apply the patch, wait for CI to pass, and merge it in for you.

Q: Who is providing this jenkins?

A: Currently, the jenkins instance will be provided by Citrix, mainly because we're still working out an infrastructure testing lab in ASF.  When that is ready, Citrix is willing to donate the setup necessary to run continuous integration to ASF.

Q: I like to set this up in my own organization so that we can run CI on our own development branches.  Can I do this?

A: The setup itself is publicly available.  The people who made this possible: Amogh, Bharat, Santhosh, are all on the mailing list.  You can communicate with them via the mailing list and ask them help you with the setup.  We will try to document this setup as much as possible once it's available.

Q: I currently have a Jenkins slave that runs tests for my own code on every build.  Can you add my slave to your jenkins?

A: Currently, no.  There's a lot of issues involving jenkins in Citrix making call to outside of Citrix that really I'm not willing to go resolve.  For now, you just have to run that with the ASF jenkins.