Hi, does anyone know if it is somehow possible to to have job using GitHub pull request builder plugin for Pull Requests testing. BUT configure the job in a way that no "output" will be shown in GitHub PR? (no status updates, no "Can one of the admins verify this patch?" messages, ...) I've not found any option for this. Is there any?
I am using a new job for testing new jobs configuration (I want it to act the same as "normal" job), but no output should be visible in GH (the new job configuration may not work properly).
I managed to solve this in my Jenkins by using 'auth-id:' which can't write a repository.
Would it be possible to add such credential in CentOS CI Jenkins? (github token for centos user with 'read:org' permission - it is needed because job can be triggered by all members in GH organization)
Thanks, Marek
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 09/03/17 10:06, Marek Skalický wrote:
Hi, does anyone know if it is somehow possible to to have job using GitHub pull request builder plugin for Pull Requests testing. BUT configure the job in a way that no "output" will be shown in GitHub PR? (no status updates, no "Can one of the admins verify this patch?" messages, ...) I've not found any option for this. Is there any?
what happens if you dont give ci-centos user permissions to post ?
- -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
On Mar 09 12:24, Karanbir Singh wrote:
On 09/03/17 10:06, Marek Skalický wrote:
Hi, does anyone know if it is somehow possible to to have job using GitHub pull request builder plugin for Pull Requests testing. BUT configure the job in a way that no "output" will be shown in GitHub PR? (no status updates, no "Can one of the admins verify this patch?" messages, ...) I've not found any option for this. Is there any?
what happens if you dont give ci-centos user permissions to post ?
^ This is what you should do. You can set up the webhooks just like in in Mode 2: https://wiki.centos.org/QaWiki/CI/GithubIntegration BUT skip entirely the part about adding centos-ci as a collaborator. That will trigger your jobs without any updates to the PR.
-- Brian
Brian Stinson píše v Čt 09. 03. 2017 v 07:24 -0600:
On Mar 09 12:24, Karanbir Singh wrote:
On 09/03/17 10:06, Marek Skalický wrote:
Hi, does anyone know if it is somehow possible to to have job using GitHub pull request builder plugin for Pull Requests testing. BUT configure the job in a way that no "output" will be shown in GitHub PR? (no status updates, no "Can one of the admins verify this patch?" messages, ...) I've not found any option for this. Is there any?
what happens if you dont give ci-centos user permissions to post ?
^ This is what you should do. You can set up the webhooks just like in in Mode 2: https://wiki.centos.org/QaWiki/CI/GithubIntegration BUT skip entirely the part about adding centos-ci as a collaborator. That will trigger your jobs without any updates to the PR.
But I would like to have 2 jobs for the same repository.
- One job that normally do CI for every PR (job scripts are tested and works good - so the results should be visible for users)
- And I would like to have a second job for the same repository, where I want to "test" new versions of job scripts (that should do the same, but do it in new, for example more efficient, way). And I would like to test them first without showing possible wrong results to user (I will check results directly in Jenkins).
If I understand it right, not adding centos-ci as a collaborator would break the first (non-testing) job. Or not?
-- Brian _______________________________________________ Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
On Fri, Mar 10, 2017, at 03:31 AM, Marek Skalický wrote:
Brian Stinson píše v Čt 09. 03. 2017 v 07:24 -0600:
- One job that normally do CI for every PR (job scripts are tested and
works good - so the results should be visible for users)
- And I would like to have a second job for the same repository, where
I want to "test" new versions of job scripts (that should do the same, but do it in new, for example more efficient, way). And I would like to test them first without showing possible wrong results to user (I will check results directly in Jenkins).
This is a problem that we solved with https://github.com/jlebon/redhat-ci which does it in the same way Travis does: your job definition lives in the git repository, and when you do a pull request, the job definition from the pull request is used.
This lets you test changes naturally.
See for example:
https://github.com/ostreedev/ostree/pull/630
There's some open discussion about having this project be an optional frontend "happy path" for Github PR testing using CentOS CI as a backend.
Colin Walters píše v Pá 10. 03. 2017 v 09:00 -0500:
On Fri, Mar 10, 2017, at 03:31 AM, Marek Skalický wrote:
Brian Stinson píše v Čt 09. 03. 2017 v 07:24 -0600:
- One job that normally do CI for every PR (job scripts are tested
and works good - so the results should be visible for users)
- And I would like to have a second job for the same repository,
where I want to "test" new versions of job scripts (that should do the same, but do it in new, for example more efficient, way). And I would like to test them first without showing possible wrong results to user (I will check results directly in Jenkins).
This is a problem that we solved with https://github.com/jlebon/redha t-ci which does it in the same way Travis does: your job definition lives in the git repository, and when you do a pull request, the job definition from the pull request is used.
This lets you test changes naturally.
See for example:
https://github.com/ostreedev/ostree/pull/630
There's some open discussion about having this project be an optional frontend "happy path" for Github PR testing using CentOS CI as a backend.
Thanks.
But this would require to change my current CI for 15+ repositories. And it does not worth effort - because being able to test new settings of jobs before using it in "production" testing is only for my feeling of safety when doing some improvements.
Someone, please would it be possible to generate github auth token for centos-ci user with only read:org scope. And add this token as credential to CentOS CI Jenkins for Github Pull Request builder plugin?
Thanks, Marek
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-
Brian Stinson -
Colin Walters -
Karanbir Singh -
Marek Skalický