Dev channel builds failing on Travis CI
jasonrudolph opened this issue · 3 comments
Description
When a package's build runs on Travis CI, and the build matrix includes the dev channel, Travis CI fails while installing Atom.
For example, the atom/ci README refers to atom/wrap-guide as an example of how to atom/ci is intended to be used. But when Travis CI attempts to run CI for atom/wrap-guide, it fails while trying to install the Atom dev release:
dpkg-deb: error: archive 'atom-amd64.deb' has premature member 'control.tar.xz' before 'control.tar.gz', giving up
We first observed this issue in the Teletype nightly build, but it appears to affect any Atom package that attempts to run CI against the Atom dev channel release. For example, we can see the same failure in atom/wrap-guide's build: https://travis-ci.org/atom/wrap-guide/jobs/551945689#L509
At the moment, my best guess is that this issue is somehow related to the recent changes in atom/atom#19597, in which the dev channel build of atom/atom is now served from Azure Pipelines instead of Travis CI. Teletype's nightly builds were fine prior to when atom/atom#19597 was merged, and they started failing after atom/atom#19597 was merged. This seems unlikely to be just a coincidence. 🤔
My plan is to upgrade to Ubuntu 16 on all of our package builds.
- About - bundled
- Archive View - builds on macOS
- AutoComplete Atom API builds on macOS
- AutoComplete CSS - builds on macOS
- AutoComplete HTML - builds on macOS
- AutoComplete+ - builds on macOS
- AutoComplete Snippets - builds on macOS
- AutoFlow - builds on macOS
- AutoSave - builds on macOS
- Background Tips - atom/background-tips#45
- Bookmarks - builds on macOS
- Bracket Matcher - atom/bracket-matcher#387
- Command Palette - builds on macOS
- Deprecation Cop - builds on macOS
- Dev Live Reload - bundled
- Encoding Selector - builds on macOS
- Exception Reporting - builds on macOS
- Find and Replace
- Fuzzy Finder
- GitHub - builds on Azure Pipelines
- Git Diff - bundled
- Go to Line - bundled
- Grammar Selector - bundled
- Image View - builds on macOS
- Incompatible Packages - bundled
- Keybinding Resolver - builds on macOS
- Line Ending Selector - bundled
- Link - bundled
- Markdown Preview - builds on macOS
- Metrics - builds on macOS
- Notifications - builds on macOS
- Open on GitHub - builds on macOS
- Package Generator - builds on macOS
- Settings View - builds on macOS
- Snippets - builds on macOS
- Spell Check - builds on macOS
- Status Bar - builds on macOS
- Styleguide - builds on macOS
- Symbols View - builds on macOS
- Tabs - builds on macOS
- Teletype - atom/teletype#463
- Timecop - builds on macOS
- Tree View - builds on macOS
- Update Package Dependencies - builds on macOS
- Welcome - builds on macOS
- Whitespace - builds on macOS
- Wrap Guide - atom/wrap-guide#84
Okay, I've audited all of our packages. Most of them don't build on Linux or are bundled. I upgraded the few that build on Linux to Xenial to avoid any issues on the next release, because that will cause artifacts from Azure Pipelines to be on the stable channel for the first time. We should be good to go.