On Wed, 5 Jun 2019 00:03:01 +0200
Miroslav Vadkerti <mvadkert(a)redhat.com> wrote:
Hi,
On Tue, Jun 4, 2019 at 8:13 PM Johnny Bieren <jbieren(a)redhat.com>
wrote:
>
>
> On Tue, Jun 4, 2019 at 10:16 AM Jan Pazdziora
> <jpazdziora(a)redhat.com> wrote:
>
>>
>> Hello,
>>
>> I have run fedora-rawhide-build-pipeline
>>
>>
>>
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/je...
>>
>> that failed in the
>>
>> cloud-image-compose
>>
>> stage, something which (I believe) have very little control over.
>>
> I do agree that this failure does not appear to be due to anything
> you did. It appears (to me) to be:
> *13:09:06* process apparently never started in
> /workDir/workspace/fedora-rawhide-build-pipeline@tmp/durable-3b02e0b5
> @Bruno Goncalves <bgoncalv(a)redhat.com> what is the proper way to
> retrigger tests for the build pipeline? I could manually restart the
> jenkins build, but I am not sure if there is a more official way to
> do it
Unfortunately, afaik, currently only people with login access to the
openshift cluster have ability to rebuild (as OSCI we can do it),
basically we are missing jenkins to be kerberized with Fedora's
kerberos, so we can give this ability to the end users ...
As I recall, the infra folks don't want Fedora's kerberos to be used
for anything beyond koji. I do not recall the details behind that,
though and it's possible that things could have changed.
That being said, there is support for Fedora OAuth logins in Jenkins as
shown in this template:
https://pagure.io/fedora-infra-jenkins/
That support does allow restricting functions to FAS groups:
https://pagure.io/fedora-infra-jenkins/blob/master/f/s2i/jenkins/master/c...
Tim
<snip>