{"action":"opened","issue":{"url":"https://api.github.com/repos/eclipse/openj9/issues/1395","repository_url":"https://api.github.com/repos/eclipse/openj9","labels_url":"https://api.github.com/repos/eclipse/openj9/issues/1395/labels{/name}","comments_url":"https://api.github.com/repos/eclipse/openj9/issues/1395/comments","events_url":"https://api.github.com/repos/eclipse/openj9/issues/1395/events","html_url":"https://github.com/eclipse/openj9/issues/1395","id":303627071,"number":1395,"title":"Jenkins: parse JOB_NAME to set SPEC and SDK_VERSION variables","user":{"login":"AdamBrousseau","id":6430052,"avatar_url":"https://avatars0.githubusercontent.com/u/6430052?v=4","gravatar_id":"","url":"https://api.github.com/users/AdamBrousseau","html_url":"https://github.com/AdamBrousseau","followers_url":"https://api.github.com/users/AdamBrousseau/followers","following_url":"https://api.github.com/users/AdamBrousseau/following{/other_user}","gists_url":"https://api.github.com/users/AdamBrousseau/gists{/gist_id}","starred_url":"https://api.github.com/users/AdamBrousseau/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AdamBrousseau/subscriptions","organizations_url":"https://api.github.com/users/AdamBrousseau/orgs","repos_url":"https://api.github.com/users/AdamBrousseau/repos","events_url":"https://api.github.com/users/AdamBrousseau/events{/privacy}","received_events_url":"https://api.github.com/users/AdamBrousseau/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-08T20:51:05Z","updated_at":"2018-03-08T20:51:05Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Currently, we have Pipeline files which are essentially copy/pasted several times per SPEC and SDK_VERSION. It has been proposed that we just have a \"generic\" file that takes parameters for these 2 values. The issue with using parameters is they can be changed \"on-the-fly\" and since we have different jobs for each SPEC and SDK_VERSION, we do not want these to change from build to build.\r\n\r\nSince we have a standard naming convention for our job names, another idea would be to write a function that sets the SPEC and SDK_VERSION based on the Jenkins JOB_NAME. I have prototyped this feature and it appears to work in the pipeline build. I wanted to open an issue to discuss this approach more. What would the limitations of this be? I can see difficulty arising when trying to debug a build. For example, I currently have a debug copy of a build and the SPEC and SDK in the job name doesn't always match the build I'm testing (I often change the JenkinsFile that is loaded). The other thing is we would need to maintain 2 more variables in the variables file which would be arrays of SPECS and SDK_VERSIONS. We may be able reuse these new variable arrays in the Build-Test-All pipeline?\r\n\r\n\r\nNote: There is also hardcoded TEST_TARGET in the PR pipelines but I think we should ignore that for now because the test story may be changing."}}
{"actor":{"display_login":"AdamBrousseau"}}