{"action":"created","issue":{"url":"https://api.github.com/repos/travis-ci/travis-ci/issues/5898","repository_url":"https://api.github.com/repos/travis-ci/travis-ci","labels_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/5898/labels{/name}","comments_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/5898/comments","events_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/5898/events","html_url":"https://github.com/travis-ci/travis-ci/issues/5898","id":147995253,"number":5898,"title":"Add job label/display name","user":{"login":"Snaipe","id":977973,"avatar_url":"https://avatars.githubusercontent.com/u/977973?v=3","gravatar_id":"","url":"https://api.github.com/users/Snaipe","html_url":"https://github.com/Snaipe","followers_url":"https://api.github.com/users/Snaipe/followers","following_url":"https://api.github.com/users/Snaipe/following{/other_user}","gists_url":"https://api.github.com/users/Snaipe/gists{/gist_id}","starred_url":"https://api.github.com/users/Snaipe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Snaipe/subscriptions","organizations_url":"https://api.github.com/users/Snaipe/orgs","repos_url":"https://api.github.com/users/Snaipe/repos","events_url":"https://api.github.com/users/Snaipe/events{/privacy}","received_events_url":"https://api.github.com/users/Snaipe/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/travis-ci/travis-ci/labels/feature-request","name":"feature-request","color":"009800"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-04-13T09:08:14Z","updated_at":"2016-07-26T08:26:33Z","closed_at":null,"body":"The build summary screen can become a hassle to read for projects with a complex build matrix.\r\n\r\nIt would be great if we could add names/labels to specific jobs in the matrix.\r\n\r\nThe visual result could be something like this:\r\n\r\n![travis-job-label-request](https://cloud.githubusercontent.com/assets/977973/14487767/d3fbf2e0-0164-11e6-82f9-82d1aa95629c.png)\r\n\r\nAnd the .travis.yml config, like so:\r\n\r\n```yaml\r\nmatrix:\r\n  include:\r\n  - name: Build with foo as bar\r\n```\r\n\r\nHaving no display name would simply blank out the relevant section.\r\n\r\nThis, if it were to be implemented:\r\n\r\n* Would allow developers to see at a glance which builds failed an succeeded -- currently, I have to count the index of the job or read its log to see that a job cross compiles for architecture X or Y.\r\n* Would allow developers to sum up the contents of the environment field to the right, which can become easily cluttered when you have 3+ variables defined in your matrix.\r\n* Would allow developers to make a distinction between otherwise visually identical builds (e.g. builds that only differ by a secure variable, like builds testing on two specialized remotes machines with credentials, or builds that have the same environment variables but use different apt packages).\r\n\r\nA possible workaround could be putting a `_` environment variable -- with the name as a value -- at the start of the environment list (not tested), but this is hardly convenient and is visually inconsistent."},"comment":{"url":"https://api.github.com/repos/travis-ci/travis-ci/issues/comments/235196354","html_url":"https://github.com/travis-ci/travis-ci/issues/5898#issuecomment-235196354","issue_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/5898","id":235196354,"user":{"login":"jayvdb","id":15092,"avatar_url":"https://avatars.githubusercontent.com/u/15092?v=3","gravatar_id":"","url":"https://api.github.com/users/jayvdb","html_url":"https://github.com/jayvdb","followers_url":"https://api.github.com/users/jayvdb/followers","following_url":"https://api.github.com/users/jayvdb/following{/other_user}","gists_url":"https://api.github.com/users/jayvdb/gists{/gist_id}","starred_url":"https://api.github.com/users/jayvdb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jayvdb/subscriptions","organizations_url":"https://api.github.com/users/jayvdb/orgs","repos_url":"https://api.github.com/users/jayvdb/repos","events_url":"https://api.github.com/users/jayvdb/events{/privacy}","received_events_url":"https://api.github.com/users/jayvdb/received_events","type":"User","site_admin":false},"created_at":"2016-07-26T08:26:33Z","updated_at":"2016-07-26T08:26:33Z","body":"As you are cross compiling, that should be in the Compiler column of Travis build matrix.  Currently it says \"gcc\", but that isnt really true.  The same is roughly true of multi-arch platforms.\r\n\r\nWrt [your config](https://github.com/Snaipe/Mimick/blob/master/.travis.yml) specifically, wouldnt it be enough if Travis build env column said \"CONFIGURATION=Debug, *i386-env\", in which case it is a minor change to the UI to better show complex yaml.  Then you could defined `x86_64-linux-debug` and it would appear as \"*x86_64-linux-debug\" in the env column -- at least then it isnt an arbitrary name; it is a defined name elsewhere in the yaml.\r\n\r\nAs for debug, on most languages, it is quite easily set with an env var.\r\nFor C/C++, it is CFLAGS and CXXFLAGS respectively, and the usual approach is to use `-g` or `-O2`.  autoconf understands those.  With direct clang invocation, I think `llvm-config` needs to be used, but I am rusty on that. The build script could still fiddle with those defaults env vars for project specific preferences wrt debug/release, but it isnt hard to have sane defaults which tease out bugs. (and then it would be possibly to add support for fancy config, such as building only debug versions by default for branches (so it is quicker), and enable release builds on master."}}
{"actor":{"display_login":"jayvdb"}}