Message ID | 20181129001055.14944-1-joel@jms.id.au |
---|---|
Headers | show |
Series | Travis updates | expand |
Joel Stanley <joel@jms.id.au> writes: > Joel Stanley (2): > opal-ci: Use ubuntu:rolling for Ubuntu latest image > travis: Coverity fixed their SSL cert Thanks! We should possibly rename the 'latest' files in opal-ci/ and go for 'rolling' instead? I'm kind of tempted to put them on the allowed to fail list too, just so that when we go back to tagged skiboots for updates we don't suddenly jump a few years forward. i.e. keep the travis as something you'd always expect to pass. THoughts? Series merged to master as of 42fa2c4e472f566c4c8d922f902e23f9c9032cfc anyway :)
On Thu, 29 Nov 2018 at 14:38, Stewart Smith <stewart@linux.ibm.com> wrote: > > Joel Stanley <joel@jms.id.au> writes: > > Joel Stanley (2): > > opal-ci: Use ubuntu:rolling for Ubuntu latest image > > travis: Coverity fixed their SSL cert > > Thanks! > > We should possibly rename the 'latest' files in opal-ci/ and go for > 'rolling' instead? I'm kind of tempted to put them on the allowed to > fail list too, just so that when we go back to tagged skiboots for > updates we don't suddenly jump a few years forward. i.e. keep the travis > as something you'd always expect to pass. THoughts? We could make an argument either way. The other argument is when we do a stable release we want to make sure that developers will be able to build the ancient release with their current development system, which might mean backporting build fixes for newer toolchains. Renaming wouldn't hurt, although I find rolling to be a confusing name. It's not rolling in the sense that Debian unstable or Rawhide is; it's the latest release. Cheers, Joel