In Travis CI - Test and Deploy with Confidence language: value generic is an alias for shell, using shell Which is incorrect , so I end up getting a wrong build system image as a result if I have build config validation enabled.

We have just shipped a fix that should address this issue.

Generic gives you shell but minimal is equivalent to all shells? [1] So they are the same? NO?! [2] Makes no sense at all. [1] https://docs.travis-ci.com/user/languages/minimal-and-generic/#aliases [2] https://docs.travis-ci.com/user/languages/minimal-and-generic/#minimal https://docs.travis-ci.co…

@SuperSandro2000 not sure what you’re talking about. This is a bug report. If you need documentation explained to you, you should probably create a new topic. language: generic and language: minimal images are different (at least, for os: linux). generic has more software preinstalled.

This build was wrongly converted to language: shell, we had Enable build config validation enabled. https://travis-ci.org/dmstr/cookie-consent/jobs/617610138/config After removing the validation the build runs as generic (like specified).

Thanks for the report. We are looking into fixing the config validation logic.

Since it’s confirmed that the validation works, I’ll give you your hard-earned tick and move the display issue into a separate topic!

`language: generic` is wrongly changed to `language: shell`

Early Releases Build Config Validation

Topic		Replies	Views
Support `language:generic` and `language:minimal` in Windows Feature Requests travis-build , windows	1	1037	December 12, 2019
Misspelled `language: minmal` doesn't fail Travis CI Discussions & Feedback	1	555	February 16, 2019
Generic language configuration Feature Requests	1	410	December 6, 2020
Build is stuck when `language` is set to `minimal` Windows	7	1235	November 7, 2018
Windows VM not booting for `language: generic` or `language: minimal` Windows bug , job-scheduler	10	2578	April 28, 2020

`language: generic` is wrongly changed to `language: shell`

Related topics