Skip to main content

Github CICD Folder Upload Errors

  • Mar 9, 2024 6:09 PM UTC
  • 2 replies
  • 381 views
  • Translate All

Background: We have a github cicd on a self-runner host from AWS. In this workflow we build our daily software and upload to Box using below command. This has been working for the past 6 month.

Issue: Last couple of months, I am getting frequent errors that “item already exists”. (1) The problem is that files get uploaded correctly and when I check the box, I do see all the files. However, not sure why I am getting these errors. (2) It is not possible to have “same name” since each build has a unique github commit ID attached to our release target name. i.e, There are 3 different unique IDs concatenated together. Here is an example “0514.2_A_0.0.48_5b57cb4_0308”. Hence it is impossible to have same name.

What is going on here? I need support from Box Team. This is not something we can afford to constantly have errors for no apparent reason.

Error

Error: Unexpected API Response [409 Conflict | 4t6w1ehnkir5p8jc.0786afe948d834788dc1f0ba396b1cc64] item_name_in_use - Item with the same name already exists

Box Upload Command from Github workflow yml file.

Box folders:upload UniqueReleaseName --parent-folder=xxxxxx --verbose --json > CI_CD/create_folder_result.json

Here is the error - I can’t post the entire error but I can send the file to Box Support Team. I’ve masked out some hash keys with “xxx”

Error: Unexpected API Response [409 Conflict | xxxxxx.xxxxx] item_name_in_use - Item with the same name already exists
    at Object.buildResponseError (C:\Program Files\@boxcli\client\node_modules\box-node-sdk\lib\util\errors.js:119:41)
    at Object.buildUnexpectedResponseError (C:\Program Files\@boxcli\client\node_modules\box-node-sdk\lib\util\errors.js:150:21)
    at C:\Program Files\@boxcli\client\node_modules\box-node-sdk\lib\box-client.js:515:34
    at tryCatcher (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\promise.js:729:18)
    at Promise._fulfill (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\promise.js:673:18)
    at Promise._resolveCallback (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\promise.js:466:57)
    at Promise._settlePromiseFromHandler (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\promise.js:559:17)
    at Promise._settlePromise (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\promise.js:729:18)
    at Promise._fulfill (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\promise.js:673:18)
    at Promise._settlePromise (C:\Program Files\@boxcli\client\node_modules\bluebird\js\release\promise.js:617:21)
Error: Process completed with exit code 2.

2 replies

rbarbosa Box
Forum|alt.badge.img
  • Developer Advocate
  • Mar 11, 2024 10:28 PM UTC

Hi @LaithD , welcome back to the forum!

That is indeed strange and I would recommend you open a support case.

Is the error consistent, meaning does it always happen now?

Translate

  • Author
  • New Participant
  • Mar 12, 2024 2:23 PM UTC

Hi thank you for the reply.
No, it is not consistent, it happens infrequent and only it started in last couple of months. No updates on our workflow CI/CD code. There were couple of instances where the upload failed; after few files. It started to happen in Jan.
Thank you.
Laith

Translate