Currently I have travis-ci setup such that it tests any new branch that appears on github. It will also test on any merge or commit on master. If we can achieve that functionality with YETUS, LETUS use it. waka waka waka.
On Wed, Jun 1, 2016 at 10:50 AM, Josh Elser <[email protected]> wrote: > IMO, I see Yetus as a more "patch testing" workflow whereas Jenkins is > just "build the code" (e.g. `mvn verify`). You can likely accomplish much > of the same between the two, but Yetus is very nice for the ASF > contribution-oriented workflow. > > A sample report from Yetus might speak to more lengths than I can > https://issues.apache.org/jira/browse/HADOOP-13171?focusedCommentId=15310302&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15310302 > > Sean might also be able to give a better elevator pitch on it, or if you > have any more targeted questions, I can try to answer. > > Edward Capriolo wrote: > >> What does yetis so that jenkins can not? >> >> On Saturday, May 28, 2016, Josh Elser<[email protected]> wrote: >> >> On May 28, 2016 9:40 AM, "Edward Capriolo"<[email protected] >>> <javascript:;>> wrote: >>> >>>> Besides and code issues we want to tackle I think we need to handle a >>>> few >>>> things. >>>> >>>> 1) Currently the project uses travis-ci. After changes it runs the >>>> build/test process and reports its finding to github. >>>> What do we need to do to achieve that in Apache land, jenkins etc? >>>> >>> Apache Yetus is a good starting point for doing precommit builds with >>> patches on jira or pull requests via ASF jenkins, and you can use the >>> same >>> Jenkins build for timed/post-commit builds. I think I have karma to >>> create >>> jobs once we figure out what is desired. >>> >>> 2) Currently the release process releases maven artifacts to a sonatype >>>> repo (owned by me group:teknek.io) >>>> What do we need to do to achieve that in Apache land? >>>> >>> Set Gossip's parent pom to be the Apache pom and that should be it. The >>> maven-release-plugin will be configured to stage artifacts to the ASF >>> Nexus >>> instance which you can use to stage/release artifacts. >>> >>> 3) Lets repackage from com.googlecode to org.apache.gossip. I will make a >>>> jira ticket for this. It is low hanging fruit and would be a good get >>>> >>> your >>> >>>> feet wet type issue. >>>> >>>> Thanks all, >>>> Edward >>>> >>> >> >>
