Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Travis] Set dist to trusty #109

Merged
merged 1 commit into from
Aug 9, 2019
Merged

[Travis] Set dist to trusty #109

merged 1 commit into from
Aug 9, 2019

Conversation

mnocon
Copy link
Member

@mnocon mnocon commented Aug 8, 2019

Question Answer
JIRA issue n/a
Type Misc
Target version 1.7, same as #98
BC breaks no
Doc needed no

Travis switched the default dist from trusty to xenial:
https://travis-ci.org/ezsystems/ezplatform-xmltext-fieldtype/builds/567807165 - uses trusty
https://travis-ci.org/ezsystems/ezplatform-xmltext-fieldtype/builds/569339518 - uses xenial

This is causing the builds in #98 to fail.

Setting the dist excplicitly as it is done in 1.8 branch: https://github.com/ezsystems/ezplatform-xmltext-fieldtype/blob/1.8/.travis.yml#L1

@mnocon mnocon changed the base branch from master to 1.7 August 8, 2019 13:51
@mnocon mnocon changed the title [WIP] [Travis] Set dist to trusty [Travis] Set dist to trusty Aug 8, 2019
@mnocon mnocon requested review from andrerom and vidarl August 8, 2019 14:28
@andrerom
Copy link
Contributor

andrerom commented Aug 9, 2019

I didn't fully intend to keep on supporting 1.7 branch, but if we need to fix something for 1.7LTS users (1.8 requires 1.13.6) it's anyway good that 1.7 branch is green.

@mnocon
Copy link
Member Author

mnocon commented Aug 9, 2019

Yea, I'm not really sure where this bundle version is used, it's just that contributions for 1.7 are coming (#96, #98) and are not rejected, so I guess we can unblock Travis for them as well 😉

@andrerom andrerom merged commit 68a365c into ezsystems:1.7 Aug 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants