I have set up an experimental installation of CloudBees validated merge [1] on jenkins.ci.cloudbees.com for Jenkins core [2]. This lets you have Jenkins test your commit(s) before pushing them upstream.
If you are a Jenkins committer and would like to try this service, please let me know (off list) what your user ID on this server is (typically an email address), and I can add you to a security group in order to be allowed to push here. If you are not a Jenkins committer, or are but prefer to use pull requests to get feedback, then this service is irrelevant since PRs are already validated. The point is being able to offload testing to CI for commits not associated with any PR. Validated merge also supports commit --amend, so if your commit causes a minor test failure you can just patch it up and try again. (Since we do not yet have SSH service into DEV@cloud, and I could not figure out command-line Git’s HTTP authentication, for now this uses a secret push URL per user. Keep your .git/config secure if you used git remote add.) [1] http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/validated-merge.html [2] https://jenkins.ci.cloudbees.com/job/core/job/jenkins_main_trunk/repo.git/ -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
