Replies inlined. On Fri, Jul 21, 2017 at 12:27 PM, Sahil Takiar <[email protected]> wrote:
> On Fri, Jul 21, 2017 at 6:43 AM, Olivier Lamy <[email protected]> wrote: > > > Hi > > > > On 21 July 2017 at 05:44, Sahil Takiar <[email protected]> wrote: > > > > > -gobblin-users, -user > > > > > > Few questions: > > > > > > * What is the "Migration of Travis CI to use the Apache infrastructure" > > > going to entail? I'm guessing builds will happen on Apache Jenkins > > > instances, how about pre-commit checks? Is there a plan to add > pre-commit > > > checks, using tools such as YETUS? > > > > > > > we can have a pull request builder if it's what you're looking for? > > Not sure what you want to do with Yetus? > > > > > Yeah, any type of pre-commit job. Could be a Pull Request builder. Other > Apache projects like Hadoop and HBase use YETUS to run a pre-commit job, > and the results are pasted as a comment on the JIRA. The nice thing about > YETUS is that it can run a bunch of test in the pre-commit job, as well as > other tools such as checkstyles, FindBugs, etc. > So will this be complimentary to the findbugs we already run with each build? or just an alternative? (I haven't explored Yetus yet though, so my question might be naive) > > > > > > * I think there is a way in Github to completely remove the Issues > > section, > > > other projects (such as Spark) have done this > > > > > > > As long as the project will be under apache org github issues are > disabled > > :-) > > > > > > > * Maybe good to follow Sparks format for opening PRs - title of each PR > > > > contains the JIRA and component, and each PR has a section summarizing > what > > > was changed and how it was tested > > > > > > > If we use jenkins there is some tooling parsing commit message to detect > > jira issue (pattern such GOBBLIN-xxx) and update jira issue with build > > result. > > Is it what you want? > > > > > Yeah, I think that would help keep things more organized. > > Yes, will love to enable this. Wrote it down as a step while setting up Jenkins on the migration wiki. > > > > > > > > > --Sahil > > > > > > On Wed, Jul 19, 2017 at 3:14 PM, Abhishek Tiwari < > > > [email protected]> wrote: > > > > > > > Hey all, > > > > > > > > As part of the Gobblin project's recent move to Apache, we are > > migrating > > > > the mailing lists to Apache infrastructure as well, so that *the > > existing > > > > Google groups will become read-only* at some point in the near > future. > > > > > > > > To keep receiving updates about Gobblin or to participate in > > development > > > > discussions, please *subscribe* to the following lists: > > > > > > > > [email protected] -- for usage questions, help and > > > > announcements. [Subscribe <user-subscribe@gobblin. > incubator.apache.org > > >] > > > [ > > > > Archives > > > > <http://mail-archives.apache.org/mod_mbox/incubator-gobblin-user/>] > > > > [email protected] -- for people who want to > contribute > > > > code to Gobblin. [Subscribe <dev-subscribe@gobblin. > > incubator.apache.org > > > >] > > > > [Archives > > > > <http://mail-archives.apache.org/mod_mbox/incubator-gobblin-dev/>] > > > > [email protected] -- for people who want to > > > contribute > > > > code to Gobblin. [Subscribe > > > > <[email protected]>] [Archives > > > > <http://mail-archives.apache.org/mod_mbox/incubator-gobblin-commits/ > >] > > > > > > > > Additionally, the Gobblin Gitter chat rooms: [Gobblin Lobby > > > > <https://gitter.im/gobblin/Lobby>] [Gobblin Cluster > > > > <https://gitter.im/gobblin/gobblin-cluster>] is where many Gobblin > > > > developers and users hang out to answer questions and chat. > > > > > > > > *The other infrastructure and process changes with Apache migration > > are: > > > * > > > > > > > > 1) Migration of linkedin/gobblin code base to Apache's Git > repository. > > > [In > > > > Progress] > > > > 2) Migration of Google groups mailing list (this list) to Apache > > mailing > > > > lists. [In Progress] > > > > 3) Migration of Travis CI to use the Apache infrastructure. > [Scheduled] > > > > 4) Migration of Wiki to Apache Confluence wiki. [Scheduled] > > > > 5) Migration of Github Issues to Apache JIRA. [Done] > > > > 6) Migration of all existing pull requests to the Apache Github > mirror > > > > repository. [Scheduled] > > > > > > > > We will track the progress of the above items on Gobblin's Apache > > mailing > > > > lists. > > > > > > > > *What you should do:* > > > > > > > > * Sign up for the Apache user, dev and commits mailing list (as > > described > > > > above) > > > > * Sign up for an Apache JIRA account and open any issues that you > care > > > > about in Apache Gobblin JIRA project (https://issues.apache.org/ > > > > jira/browse/GOBBLIN) > > > > * Sign up for an Apache Confluence account ( > https://cwiki.apache.org/ > > > > confluence/display/GOBBLIN) > > > > * Stop creating GitHub issues immediately. Create new problem reports > > as > > > > JIRAs now. > > > > > > > > Regards, > > > > Abhishek > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups > > > > "gobblin-users" group. > > > > To unsubscribe from this group and stop receiving emails from it, > send > > an > > > > email to [email protected]. > > > > To post to this group, send email to [email protected]. > > > > To view this discussion on the web visit > https://groups.google.com/d/ > > > > msgid/gobblin-users/CAFjTMnwyPbd1ngGa7JX% > > 3DUKHkPwJ1YhJtA-ZN8xxDZjJbu1v% > > > > 2BXw%40mail.gmail.com > > > > <https://groups.google.com/d/msgid/gobblin-users/ > CAFjTMnwyPbd1ngGa7JX% > > > 3DUKHkPwJ1YhJtA-ZN8xxDZjJbu1v%2BXw%40mail.gmail.com?utm_ > > > medium=email&utm_source=footer> > > > > . > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > > > > > > > -- > > > Sahil Takiar > > > Software Engineer at Cloudera > > > [email protected] | (510) 673-0309 > > > > > > > > > > > -- > > Olivier Lamy > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > > > > > -- > Sahil Takiar > Software Engineer at Cloudera > [email protected] | (510) 673-0309 >
