In our scenario, we have multiple build process running on a build server that eventually have to put an artifact (RPM) into the repositor.io running on a different delivery server. At the moment that ist done by copying them to the remote host where repositor.io is running, then adding them and afterwards cleaning the upload folder.
scp artifact.rpm upload_user@repositorio.host:.
ssh upload_user@repositorio.host "flock . repositorio --repo=artifact_name --add=artifact.rpm"
ssh upload_user@repositorio.host "rm -f ${rpmkpg##*/}"
The flock . is used to circumvent #44 when multiple build process run in parallel.
It would be great to have a simple web service where you could POST or PUT the artifact via a single http request (with the file as Body and query parameters for the additional command parameters, or as multipart request).
This service should be runnable in parallel (#44) since one would not have the option for any self-made locking in this case.
In our scenario, we have multiple build process running on a build server that eventually have to put an artifact (RPM) into the repositor.io running on a different delivery server. At the moment that ist done by copying them to the remote host where repositor.io is running, then adding them and afterwards cleaning the upload folder.
The
flock .is used to circumvent #44 when multiple build process run in parallel.It would be great to have a simple web service where you could POST or PUT the artifact via a single http request (with the file as Body and query parameters for the additional command parameters, or as multipart request).
This service should be runnable in parallel (#44) since one would not have the option for any self-made locking in this case.