0

Our SAP MTA project fails to build since a day or 2 using the new cloud mta build tool option with the following strange error ( I have renamed our actual project name with 'xxx') :

11:00:22 (Executor) [2020-02-06 10:00:22]  INFO generating the MTA archive...
11:00:35 (Executor) [2020-02-06 10:00:35]  INFO the MTA archive generated at: /projects/xxx/mta_archives/xxx_cloud_v1_1.0.0.mtar
11:00:35 (Executor) [2020-02-06 10:00:35]  INFO cleaning temporary files...
11:00:35 (Executor) /usr/local/scripts/mbt/webide_mbt_build.sh: line 105: [: mta_archives/xxx_cloud_v1: binary operator expected
11:00:35 (Executor)     zip warning: name not matched: mta_archives/xxx_cloud_v1
11:00:35 (Executor)     zip warning: name not matched: true_1.0.0.mtar
11:00:35 (Executor) 
11:00:35 (Executor) zip error: Nothing to do! (try: zip -r mta_archives/mta_archives.zip . -i mta_archives/xxx_cloud_v1 true_1.0.0.mtar)
11:00:35 (Executor) ERROR:The build of project xxx_cloud_v1 true failed, (Error Code=12, Error Msg=Failed to compress the mta_archives/xxx_cloud_v1 true_1.0.0.mtar source file to the mta_archives/mta_archives.zip .zip file.)
11:00:35 (Executor) ERROR:Function call stack
11:00:35 (Executor)   exitOnError
11:00:35 (Executor)   zipFile
11:00:35 (Executor)   main`

It seems like it is confused about the name and adds a space and the value true in between .. causing the ZIP script command to faile.

I have rechecked our MTA.yaml file but don't see anything weird with it.

Other test projects build just fine so it has to be somethinig with either our project work space and/or the script ?

If I try to use the other older build tool option then I am getting a similar script issue:

11:19:56 (Executor) The "Task for mta build" process started.
11:19:59 (Executor) Starting process: "cd /projects/xxx_cloud_v1; webide_mta_build.sh"
11:19:59 (Executor) Incorrect command line syntax
11:19:59 (Executor) SAP Multitarget Application Archive Builder 1.1.20

We are on SAP Web IDE Full-Stack - Version: 200116. Production env.

Thanks,

Steven

4

1 回答 1

0

在过去的几天里，我一直在检查我们对该项目所做的所有更改，并找到了问题的潜在根源——尽管我无法解释为什么会发生这种情况。

所以为了将来参考 - 这是我发现的：

我们在文件中使用了相当多的属性，MTA.yaml并在其中添加了一些新属性。

所以

properties:
    XS_APP_LOG_LEVEL: debug
    CUSTOM_PROP_1: true
    CUSTOM_PROP_2: true

似乎这些属性之一导致了这个问题——尽管它并没有什么奇怪的，它也boolean像我们拥有的许多其他属性一样具有价值。

我首先认为它会太长或者组合长度会超过一些脚本变量......但我无法得出一个结论性的答案。

将与我们的 SAP 联系人核实以进一步澄清。

于 2020-02-06T12:23:23.100 回答