Hi, We are running unit tests and functional tests on ci.centos.org[1][2] for container-pipeline-service[3] repository. Both the jobs are set to be triggered on PR raised on the repository.
Now whenever a PR is raised, both jobs runs and overrides the check status for each other. So, we can see status of only one check at one time.
Is there a way we can show both the checks on github UI, with their status?
[1]https://ci.centos.org/view/Container/job/centos-container-pipeline-service-c... [2]https://ci.centos.org/view/Container/job/centos-container-pipeline-service-c... [3]https://github.com/CentOS/container-pipeline-service
Regards Bamacharan Kundu
Hi,
you have to set unique "status context" for GitHub PR plugin, see for example [1]. Then you will see multiple checks in GitHub UI [2].
Regards, Pavol
[1] https://github.com/openshiftio/openshiftio-cico-jobs/blob/master/devtools-ci... [2] https://github.com/openshiftio/saas-openshiftio/pull/1038
On Fri, Sep 7, 2018 at 1:06 PM Bamacharan Kundu bkundu@redhat.com wrote:
Hi, We are running unit tests and functional tests on ci.centos.org[1][2] for container-pipeline-service[3] repository. Both the jobs are set to be triggered on PR raised on the repository.
Now whenever a PR is raised, both jobs runs and overrides the check status for each other. So, we can see status of only one check at one time.
Is there a way we can show both the checks on github UI, with their status?
[1] https://ci.centos.org/view/Container/job/centos-container-pipeline-service-c... [2] https://ci.centos.org/view/Container/job/centos-container-pipeline-service-c... [3]https://github.com/CentOS/container-pipeline-service
Regards Bamacharan Kundu _______________________________________________ Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Thanks Pavol,
On 09/07/2018 06:32 PM, Pavol Pitonak wrote:
Hi,
you have to set unique "status context" for GitHub PR plugin, see for example [1]. Then you will see multiple checks in GitHub UI [2].
We have multicheck enabled now :)
https://github.com/CentOS/container-pipeline-service/pull/624
Regards Bamacharan Kundu
Regards, Pavol
[1] https://github.com/openshiftio/openshiftio-cico-jobs/blob/master/devtools-ci... [2] https://github.com/openshiftio/saas-openshiftio/pull/1038
On Fri, Sep 7, 2018 at 1:06 PM Bamacharan Kundu <bkundu@redhat.com mailto:bkundu@redhat.com> wrote:
Hi, We are running unit tests and functional tests on ci.centos.org <http://ci.centos.org>[1][2] for container-pipeline-service[3] repository. Both the jobs are set to be triggered on PR raised on the repository. Now whenever a PR is raised, both jobs runs and overrides the check status for each other. So, we can see status of only one check at one time. Is there a way we can show both the checks on github UI, with their status? [1]https://ci.centos.org/view/Container/job/centos-container-pipeline-service-ci-pr-openshift [2]https://ci.centos.org/view/Container/job/centos-container-pipeline-service-ci-pr-unittests [3]https://github.com/CentOS/container-pipeline-service Regards Bamacharan Kundu _______________________________________________ Ci-users mailing list Ci-users@centos.org <mailto:Ci-users@centos.org> https://lists.centos.org/mailman/listinfo/ci-users
On 09/07/2018 09:02 AM, Pavol Pitonak wrote:
you have to set unique "status context" for GitHub PR plugin, see for example [1]. Then you will see multiple checks in GitHub UI [2].
[1] https://github.com/openshiftio/openshiftio-cico-jobs/blob/master/devtools-ci... [2] https://github.com/openshiftio/saas-openshiftio/pull/1038
Greetings!
Today I tried to follow this example:
https://github.com/fedora-infra/bodhi/compare/7a5e16a...2aa0079
However, I believe I have something wrong and I know very little about Jenkins. I see the new jobs showing up here (for example, bodhi-bodhi-unit-f28):
But, they don't seem to be triggering on pull requests. I made a test pull request here:
https://github.com/fedora-infra/bodhi/pull/2585
Can anybody spot what I'm missing to get it running those new jobs?
On Sep 13 18:24, Randy Barlow wrote:
On 09/07/2018 09:02 AM, Pavol Pitonak wrote:
you have to set unique "status context" for GitHub PR plugin, see for example [1]. Then you will see multiple checks in GitHub UI [2].
[1] https://github.com/openshiftio/openshiftio-cico-jobs/blob/master/devtools-ci... [2] https://github.com/openshiftio/saas-openshiftio/pull/1038
Greetings!
Today I tried to follow this example:
https://github.com/fedora-infra/bodhi/compare/7a5e16a...2aa0079
However, I believe I have something wrong and I know very little about Jenkins. I see the new jobs showing up here (for example, bodhi-bodhi-unit-f28):
But, they don't seem to be triggering on pull requests. I made a test pull request here:
https://github.com/fedora-infra/bodhi/pull/2585
Can anybody spot what I'm missing to get it running those new jobs?
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Looks like a syntax error. This job is run when you commit new stuff to your jjb template, which then updates the job in jenkins:
https://ci.centos.org/job/cico/job/bodhi-service-job/lastFailedBuild/console
I can take a peek later, but the logs are there if someone beats me to it.
--Brian
On 09/13/2018 08:00 PM, Brian Stinson wrote:
Looks like a syntax error. This job is run when you commit new stuff to your jjb template, which then updates the job in jenkins:
https://ci.centos.org/job/cico/job/bodhi-service-job/lastFailedBuild/console
I can take a peek later, but the logs are there if someone beats me to it.
I had actually discovered the syntax error, but not some other errors, and thanks to you for reminding me how to see my service job because it helped me fix those. I seem to have jobs running now (and hopefully they actually work!):
https://github.com/fedora-infra/bodhi/pull/2591
Thanks so much for the pointer, I think I'm on the path to glory now.
-
Bamacharan Kundu -
Brian Stinson -
Pavol Pitonak -
Randy Barlow