克米亚sap论坛,最好的sap论坛,sap系统,sap培训,kemiya,克米亚,sap账号,sap ides,sap mm,sap hana,sap fico,sap pp

 找回密码
 注册
查看: 68|回复: 1

ABAP与Eclipse持续集成

[复制链接]
kmy 发表于 2019-3-22 09:07:52 | 显示全部楼层 |阅读模式
简短阅读     
  作为Eclipse中ABAP的插件,插件ABAP持续集成包含一些用于a。的特性   持续集成   环境。该插件可以从Eclipse Marketplace下载。  

  安装插件后,只有一个配置设置需要在Eclipse首选项(部分ABAP CI)中完成以启动并运行插件:  



  每次修改开发对象后,完成这些步骤后,所有添加到新视图"ABAP连续集成"的ABAP包都会自动执行。因此,无论您的上一次代码更改是否正确,您都会立即获得反馈。  

   

      长时间阅读     
  通过将ABAP集成到Eclipse中,可以在ABAP中开发最先进的开发环境。我仍然缺少的一件事是连续集成(CI)环境的工具。  

  单元测试可以通过点击一次额外的按钮来执行。但考虑到CI系统的主要特征之一应该是全自动化,这往往是一次点击太多。  

      你真的不断检查你所有的单元测试是否仍然是绿色的?     

  例如,可以使用每日检查所有ABAP单元测试   詹金斯   。但是,当代码更改破坏系统的核心功能时,通常对于获得即时反馈非常有价值。  

  因此,我开始创建一个Eclipse插件,除了一些其他功能外,每次更改一个开发对象时,它都会自动运行所有ABAP单元测试。  

  插件的安装非常简单。在Eclipse->帮助 - > Eclipse Marketplace中,您可以在ABAP持续集成下找到该插件 - 实际上是一个Beta版本,因此可以随时评论错误或想法。  

  如果你想看到更多的细节,可以在github上找到实际的源代码:   abapCI   。  

   



  安装插件后,只有一个配置设置需要在Eclipse首选项(部分ABAP CI)中完成以启动并运行插件:  



   

   

  在Eclipse首选项页面中实际设置的其他配置参数对于核心功能不是强制性的。建议选中"保存文件时运行ABAP单元测试"复选框,因为这会激活插件的核心功能。  

  插件成功安装后,再增加一个图标      在菜单栏中可以找到。单击此图标可打开附加视图 -  ABAP Continuous Integration  - 。  

  在第一次启动时,插件的视图将是空的。通过用鼠标右键点击视图的空白区域,可以打开一个上下文菜单,其中有四个选项。第三个菜单项是"Add new package",可以用来将ABAP包添加到每次更改后执行的测试运行中一个发展对象。  

  单元测试栏中显示了每个软件包的单元测试的实际状态。  

   

  单元测试列中的NOK表示失败的测试,并且可以选择更改Eclipse颜色主题。  

   

  在beta模式下已经实现了一些其他功能:  

  •    Jenkins作业的远程构建执行   
  •    测试运行中断时颜色主题的变化   
  •    如果没有开发对象改变,循环测试也运行   
  •    ...   


  但是一开始我给你留下了核心功能 - 希望你从中获得一些好处。  

英文原文

   Short read   As an add-on for ABAP in Eclipse the plugin ABAP Continuous Integration contains some features for a  Continuous Integration  environment. The plugin can be downloaded from the Eclipse Marketplace.
After installing the plugin there is only one configuration setting to be done in the Eclipse preferences (section ABAP CI) to get the plugin up and running:
In the first textbox (ABAP Development Project) the display name of your ABAP development system has to be inserted. The display name can be found in the Eclipse Package Explorer and has the form ___, e.g. A4H_001_developer_en.
After completing these steps each time when you modify a development object all ABAP packages added to the new view “ABAP Continous Integration” are automatically executed. Thus you get immediate feedback whether your last code changes are correct or not.

   Long read   With the integration of ABAP into Eclipse a state of the art development environment is available for developing in ABAP. One thing I am still missing is a tooling for a Continous Integration (CI) environment.
Unit tests can be performed with one additional button click. But taking into consideration that one of the main characteristics of a CI system should be full automation this is often one click too much.
   Do you really continuously check if all your unit tests are still green?  
A daily check of all ABAP unittests can be done for example with  Jenkins  . But often its really valuable to get an immediate feedback when a code change is breaking a core functionality of the system.
Therefore I started to create an Eclipse plugin which beside some other features runs automatically all ABAP unit tests each time one development object is changed.
The installation of the plugin is quite straightforward. In Eclipse->Help->Eclipse Marketplace you can find the plugin under ABAP Continuous Integration – well actually a Beta-Version, so feel free to comment bugs or ideas.
If you want to see some more details, the actual source code is available on github:  abapCI  .


After installing the plugin there is only one configuration setting to be done in the Eclipse preferences (section ABAP CI) to get the plugin up and running:
In the first textbox (ABAP Development Project) the display of your ABAP Development system has to be inserted. The display name can be found in the Eclipse Package Explorer and has the form ___, e.g. A4H_001_developer_en.


The other configuration parameters which can be set actually in the Eclipse preferences page are not mandatory for the core functionality. The check box “Run ABAP Unit tests when file saved” is recommended as this activates the core functionality of the plugin.
After the successful installation of the plugin an additional icon    in the menu bar can be found. Clicking this icon an additional view – ABAP Continuous Integration – is opened.
On the first start the view of the plugin will be empty. By clicking into the empty area of the view with the right mouse button a context menu is opened with four options.The third menu entry is “Add new package” which can be used to add ABAP packages to a test run performed after each change of a development object.
The actual state of the unit tests of each package is shown in the column Unit test.

A failed test is indicated with NOK in the column Unit test and optionally with a change of the Eclipse color theme.

There are already some other features realised, in beta mode:
  • Remote build execution for Jenkins jobs
  • Change of the color theme when a test run is broken
  • Cyclic test runs also in case no development objects are changed


But for the beginning I leave you with the core functionality – hoping that you get some benefit out of it.

本帖子中包含更多资源

您需要 登录 才可以下载或查看,没有帐号?注册

x
kevin9886 发表于 5 天前 | 显示全部楼层
sap abap
您需要登录后才可以回帖 登录 | 注册

本版积分规则

QQ|克米亚sap论坛,sap账号,sap系统,sap ides,sap学习机,sap练习环境 ( 渝ICP备18002525号-5 )

GMT+8, 2019-4-22 04:48

Powered by Discuz! X3.4

© 2001-2017 Comsenz Inc.

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