CI for Taskotron and Related Projects

[Tim Flink]

I've just re-started the CI on qadevel (the future one, not cloud) that
mkrizek set up a while back. It was destroyed when I started working on
replacing qadevel.cloud but never finished it.

The link is:

https://qadevel.fedoraproject.org/buildmaster/waterfall

Note that there will be ssl cert warnings since it's self signed. Once
the thing gets rebuilt for real, those ssl warnings will go away.

Tim

[Kamil Paral]

> I've just re-started the CI on qadevel (the future one, not cloud) that
> mkrizek set up a while back. It was destroyed when I started working on
> replacing qadevel.cloud but never finished it.
>
> The link is:
>
> https://qadevel.fedoraproject.org/buildmaster/waterfall

Great. Just to refresh my memory, will we receive some kind of a notification when some project fails to build?
> Note that there will be ssl cert warnings since it's self signed. Once
> the thing gets rebuilt for real, those ssl warnings will go away.

Not sure if it is intentional, but plain http does not work, the connection is refused. Not an issue, just saying.

[Martin Krizek]

----- Original Message -----
> From: "Kamil Paral" 
> To: "Fedora QA Development" 
> Sent: Wednesday, May 13, 2015 3:38:41 PM
> Subject: Re: CI for Taskotron and Related Projects
> > I've just re-started the CI on qadevel (the future one, not cloud) that
> > mkrizek set up a while back. It was destroyed when I started working on
> > replacing qadevel.cloud but never finished it.
> >
> > The link is:
> >
> > https://qadevel.fedoraproject.org/buildmaster/waterfall
>
> Great. Just to refresh my memory, will we receive some kind of a notification
> when some project fails to build?

IIRC it doesn't send notifications. We might enable sending e-mail to the
author of a commit that breaks tests (if possible). Thoughts?

Martin

[Kamil Paral]

> IIRC it doesn't send notifications. We might enable sending e-mail to the
> author of a commit that breaks tests (if possible). Thoughts?

That would be a great feature! :-)

I'd prefer to also CC qa-devel (might be obtrusive for subscribers) or sysadmin-qa-members, just to be sure we're informed when that commit author is not around for some time.

[Tim Flink]

On Wed, 13 May 2015 09:38:41 -0400 (EDT)
Kamil Paral  wrote:

<snip>
> > Note that there will be ssl cert warnings since it's self signed.
> > Once the thing gets rebuilt for real, those ssl warnings will go
> > away.
>
> Not sure if it is intentional, but plain http does not work, the
> connection is refused. Not an issue, just saying.

It's not quite intentional but only port 443 is open to that machine
and thus, https only.

I didn't think it was much of a problem, so I didn't ask for port 80 to
be opened but it occurs to me that we can't have http to https
redirection on that machine unless port 80 is open

Tim