Re: Travis-CI builds need to be turned back on

Hmm, is there any way someone can get notified when a build is turned off? I get notifications when a build fails, so perhaps there’s a similar option for when it’s turned off?

—Michiel

On Thu, Mar 1, 2018, at 1:52 PM, Michael Cooper wrote:
> It's not that it's not activated yet, it's that somebody turned it off 
> *again*. I've turned back on builds for my repos twice now in the past; 
> I just now turned practices back on again. It seems we'll need to adopt 
> a more regular practice of sharing "it happened again" on this list 
> until we figure out how to stop this from happening. Michael
> 
> 
> On 01/03/2018 8:08 AM, Michiel Bijl wrote:
> > Michael,
> >
> > It seems that the aria-practices repo is not activated yet. I don’t have admin privileges but guess you do have those.
> >
> > Could you activate it/or assign admin privileges?
> >
> > https://travis-ci.org/w3c/aria-practices
> >
> > Talk soon,
> > Michiel Bijl
> >
> > On Sat, Jan 20, 2018, at 12:27 AM, Michael Cooper wrote:
> >> If you use Travis-CI for W3C specifications, you will need to turn the
> >> builds back on. Sometime in the past 24 hours, all W3C repository builds
> >> seem to have been turned off. I don't know why this was done, but I find
> >> right now only 4 repositories with active builds besides my own that I
> >> just turned back on, so I believe it was blanket for all W3C.
> >>
> >> To re-enable Travis, I think you need to have owner access to the w3c
> >> GitHub organization, mainly Team. Go to:
> >>
> >> https://travis-ci.org/profile/w3c
> >>
> >> find your repository(ies), and flip the switch back to on.
> >>
> >> Michael
> >>
> >>
> 
>

Received on Thursday, 1 March 2018 13:59:30 UTC