[jira] [Commented] (TEZ-4064) Integrate Tez with Github
[ https://issues.apache.org/jira/browse/TEZ-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17249087#comment-17249087 ] Jonathan Turner Eagles commented on TEZ-4064: - Created email account and github account email: tezyetus at gmail dot com github: tez-yetus at github dot com > Integrate Tez with Github > - > > Key: TEZ-4064 > URL: https://issues.apache.org/jira/browse/TEZ-4064 > Project: Apache Tez > Issue Type: New Feature >Reporter: Jonathan Turner Eagles >Assignee: Jonathan Turner Eagles >Priority: Major > > According to HADOOP-16035, steps are as follows. > - an account that can read Github > - Apache Yetus 0.9.0+ > - a Jenkinsfile that uses the above -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEZ-4064) Integrate Tez with Github
[ https://issues.apache.org/jira/browse/TEZ-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17248191#comment-17248191 ] Jonathan Turner Eagles commented on TEZ-4064: - Also, if there are any gotcha's for granting PMCs access or creating secrets for github account. These would all be useful. > Integrate Tez with Github > - > > Key: TEZ-4064 > URL: https://issues.apache.org/jira/browse/TEZ-4064 > Project: Apache Tez > Issue Type: New Feature >Reporter: Jonathan Turner Eagles >Assignee: Jonathan Turner Eagles >Priority: Major > > According to HADOOP-16035, steps are as follows. > - an account that can read Github > - Apache Yetus 0.9.0+ > - a Jenkinsfile that uses the above -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEZ-4064) Integrate Tez with Github
[ https://issues.apache.org/jira/browse/TEZ-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17248181#comment-17248181 ] Jonathan Turner Eagles commented on TEZ-4064: - [~ste...@apache.org], when creating the gmail account, should I create one 1) for myself or 2) to manage my business? > Integrate Tez with Github > - > > Key: TEZ-4064 > URL: https://issues.apache.org/jira/browse/TEZ-4064 > Project: Apache Tez > Issue Type: New Feature >Reporter: Jonathan Turner Eagles >Assignee: Jonathan Turner Eagles >Priority: Major > > According to HADOOP-16035, steps are as follows. > - an account that can read Github > - Apache Yetus 0.9.0+ > - a Jenkinsfile that uses the above -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEZ-4064) Integrate Tez with Github
[ https://issues.apache.org/jira/browse/TEZ-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16824496#comment-16824496 ] Steve Loughran commented on TEZ-4064: - +create a gmail account and then use that to create a github a/c; the ASF email mechanism to create a list doesn't quite work for the github world and its easiest to roll your own alias > Integrate Tez with Github > - > > Key: TEZ-4064 > URL: https://issues.apache.org/jira/browse/TEZ-4064 > Project: Apache Tez > Issue Type: New Feature >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Major > > According to HADOOP-16035, steps are as follows. > - an account that can read Github > - Apache Yetus 0.9.0+ > - a Jenkinsfile that uses the above -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-4064) Integrate Tez with Github
[ https://issues.apache.org/jira/browse/TEZ-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823469#comment-16823469 ] Allen Wittenauer commented on TEZ-4064: --- The Yetus 0.9.0 robot feature added a bunch of autodetection for a wide variety of things to reduce the amount of CLI parameters. Part of that was support for the Jenkins' github multibranch plugin. So that Jenkinsfile "just works" because Yetus is now smart enough to preconfigure a lot of things. A lot of the extra stuff outside of the main block is just to configure Jenkins extras (e.g., artifacting) or to deal with bugs in Jenkins itself. 0.10.0 is undergoing vote presently and fixes a critical bug in findbugs. Additionally, I'm prepping another blog post on effectivemachines.com to go with it that goes into a more complex case than the part 1 post. So I'd recommend waiting a bit before going to production, but one can certainly start playing with it now. > Integrate Tez with Github > - > > Key: TEZ-4064 > URL: https://issues.apache.org/jira/browse/TEZ-4064 > Project: Apache Tez > Issue Type: New Feature >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Major > > According to HADOOP-16035, steps are as follows. > - an account that can read Github > - Apache Yetus 0.9.0+ > - a Jenkinsfile that uses the above -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-4064) Integrate Tez with Github
[ https://issues.apache.org/jira/browse/TEZ-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823221#comment-16823221 ] Jonathan Eagles commented on TEZ-4064: -- [~ste...@apache.org], [~aw], I would like to add github PR pre-commit build for Tez. Currently Tez uses Yetus 0.8.0 to build. Found HADOOP-16035, but not sure I fully grasp the steps. Yetus documentation https://yetus.apache.org/documentation/0.9.0/precommit-robots/ points to some capabilities that seem relevant here. Can either of you shed some light on the Yetus github pre-commit integration process? > Integrate Tez with Github > - > > Key: TEZ-4064 > URL: https://issues.apache.org/jira/browse/TEZ-4064 > Project: Apache Tez > Issue Type: New Feature >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Major > > According to HADOOP-16035, steps are as follows. > - an account that can read Github > - Apache Yetus 0.9.0+ > - a Jenkinsfile that uses the above -- This message was sent by Atlassian JIRA (v7.6.3#76005)
