Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

Uploading from Jenkins Pipeline with larger files



  • Hi,

    I installed ProGet on a windows server, and it is up and running.

    I succesfully tried to archive an artifact from a Jenkins Pipeline script. This is now working for a zip file of 10MB.

    In a different pipeline script I am trying to archive a zip file of 70 MB. But the process is hanging.

    [ProGet] Packaging Artifacts
    [ProGet] Sending POST as user 'Admin' to http://localhost:8083/upack/test/upload
    (loading icon)

    Do you know what might be the issue here? the only difference is the file size from what i'm seeing.

    Product: ProGet
    Version: 4.7.9



  • I'm not quite sure off hand. I've seen multi-gigabyte files cause issues, but typically OutOfMemory type exceptions. IT's definitely not an issue on the ProGet end...

    Can you try to see if you can find any other issues?

    Alternatively you can always push with upack.exe as well, or a regular HTTP Post.



  • I tried using the upack executable, but i'm missing examples on how to use both pack and push commands after eachother.

    Pack is working, and it created a package with a name that is build from the json file.

    but if i want to push the package, i need the same name that is generated from the pack command.

    How do i get the package name? do i have to build the name myself from the json file?


  • inedo-engineer

    If you set --targetDirectory on the pack command to an empty or nonexistent directory, the .upack file will be the only file in there, and you can use myDirectory\*.upack to select the upack file for the push command.


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation