设为首页 收藏本站
查看: 1359|回复: 0

[软件发布] Gerrit 2.11.4 发布,代码评审工具

[复制链接]
累计签到:1 天
连续签到:1 天
发表于 2015-11-2 12:01:10 | 显示全部楼层 |阅读模式
欢迎加入运维网交流群:263444886   DSC0000.jpg
DSC0001.png   Gerrit 2.11.4 发布,此版本主要是 bug 修复:
Bug 修复

  •   Fix NullPointerException in ls-project command with --has-acl-for option.
      Using the --has-acl-for option for external groups (e.g. LDAP groups) wascausing a NullPointerException.
  •   Issue 3328:Allow to push a tag that points to a non-commit object.
      When pushing a tag that points to a non-commit object, likev2.6.11 on linux-stable which points to a tree, orspearce-gpg-pub on jgit which points to a blob, Gerrit rejected the push withthe error message missing object(s).
      Note: This was previously fixed in Gerrit version 2.11.1, but was inadvertentlyreverted in 2.11.2 and 2.11.3.
  •   Issue 2817:Insert Change-Id footer into access right changes.
      When modifications of access rights were saved for review, the changedid not have a Change-Id footer in the commit message.

  •   Fix duplicated log lines after>
      If a plugin was>
  •   Remove --recheck-mergeable option from reindex command documentation.
      The --recheck-mergeable option was removed in Gerrit version 2.11.
  •   Use the correct validation policy for commits created by Gerrit.
      Commits created by Gerrit were being validated in the same way as commitsreceived from users.
  •   Issue 3557:Disallow invalid reference patterns in project configuration.
      When editing a project configuration by using the UI or by submitting a changeto refs/meta/config, it was possible to add a permission to an invalidreference pattern. This caused the project to be unavailable and the ls-projectscommand to fail whenever this project was encountered.
  •   Issue 3574:Fix review labels with AnyWithBlock function.
      The review labels with AnyWithBlock with 0 and +1 values blocked submit whenreviewers were added.
  •   Fix ref in tag list for signed/annotated tags.
      The tag name from the header was used, rather than the ref name. In some casesthis resulted in the wrong tag ref being listed.
  •   Prevent user from bypassing ref-update hook through gerrit-created commits.
      If the user used the cherry-pick ability in the UI or via the REST API, theycould put a commit on a branch that bypassed the requirements of the ref-updatehook (such as that certain branches require QA-tickets to be referenced in thecommit message).
  •   Allow InternalUsers to see drafts.
      According to the documentation, InternalUsers should have full read access.This was not true, since InternalUsers could not see drafts.
  •   Issue 2683:Fix non-ASCII password authentication failure under tomcat (LDAP).
      The authentication with LDAP failed when the password contained non-ASCIIcharacters such as ä, ö, Ä, and Ö.
  •   Do not double decode the login URL token.
      The login URL token used to redirect from the login servlet to the target pageis already decoded and should not be decoded again.
  •   Issue 3020:Include approvals specified on push in change message.
      When using the %l option to apply a review label on uploaded changes orpatch sets, the applied label was not mentioned in the change message.
  •   Fire the comment-added hook for approvals specified on push.
      When using the %l option to apply a review label on uploaded changes orpatch sets, the comment-added hook was not being fired.
  •   Issue 3602:Use uploader for approvals specified on push, not the committer.
      When using the %l option to apply a review label on uploaded changes orpatch sets, the review label was in some cases applied as the committer ratherthan the uploader.
  •   Issue 3531:Fix internal server error on unified diff screen for anonymous users.
  •   Issue 2414:Improve detection of requiring sign-in.
      Some queries, such as the has:* operators, require the user to be signed in.
      Also, when handling a REST API failure, detect Invalid authentication responsesas also requiring a new session.
  •   Issue 3052:Fix Conflicts With list for merge commits.
      The Conflicts List was not being populated correctly if the change being viewedwas a merge commit, or if the change being viewed conflicted with an open mergecommit.
插件修复

  •   singleusergroup: Allow to add a user to a project’s ACL using user/username.
      A user could not be added to a project’s ACL unless the user already had READpermission in the project’s ACL.
  •   replication: Add waiting time and number of retries to replication log.
      Only the replication execution time was printed in the replication completedlog statement. The waiting time and retry count is added, to help debugreplication delays.
  下载:https://gerrit-releases.storage.googleapis.com/gerrit-2.11.4.war。
  Gerrit 是一个免费、开放源代码的代码审查软件,使用网页界面。利用网页浏览器,同一个团队的软件程序员,可以相互审阅彼此修改后的程序代码,决定是否能够提交,退回或者继续修改。它使用 Git 作为底层版本控制系统。它分支自Rietveld,作者为Google公司的Shawn Pearce,原先是为了管理Android计划而产生。这个软件的名称,来自于荷兰设计师赫里特·里特费尔德(Gerrit Rietveld)。最早它是由Python写成,在第二版后,改成用Java与SQL。使用Google Web Toolkit来产生前端的JavaScript。
  评审问题列表页面:
  
DSC0002.jpg

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.iyunv.com/thread-134062-1-1.html 上篇帖子: D 2.069.0 Beta 发布,初步支持 Objective 下篇帖子: CoreOS 845.0.0 Alpha 发布,服务器操作系统
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表