[jira] [Updated] (MSCMPUB-18) publish-scm can fail with many files on linux

["Sylwester Lachiewicz (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MSCMPUB-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylwester Lachiewicz updated MSCMPUB-18:
----------------------------------------
    Labels: close-pending  (was: )

> publish-scm can fail with many files on linux
> ---------------------------------------------
>
>                 Key: MSCMPUB-18
>                 URL: https://issues.apache.org/jira/browse/MSCMPUB-18
>             Project: Maven SCM Publish Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.1
>         Environment: Fedora 19+ (and certainly many of linux distro)
>            Reporter: Charlie Mordant
>            Priority: Minor
>              Labels: close-pending
>
> Hi,
> I have a pretty complete site to publish to a git repository.
> I'm unable to publish it because linux limits command arguments to ARG_MAX kernel argument (unmodifiable): http://unix.stackexchange.com/questions/38955/argument-list-too-long-for-ls
> And for sure, the command is veeeeeery long (more than two or three Jenkins console pages).
>  
> This bug is at least blocker for my concern.
> The exact error:
> The error: Cannot run program "/bin/sh" (in directory "/var/lib/jenkins/jobs/OsgiliathEF-Site-Deploy/workspace/target/scmpublish-checkout"): error=7, Liste d'arguments trop longue 
> An alternative could be either to pass a shell file containing arguments, either simply automate this task (what I'm doing now):
> * edit .gitignore and unignore target/staging directory
> * git add target/staging && git commit -m "Initial dist subtree commit"
> * git subtree push --prefix target/staging origin gh-pages
> * rollback and delete last revision :)
> There are maybe best alternatives such as using xargs or make scalable equivalents of the command:
> http://www.gnu.org/software/coreutils/faq/coreutils-faq.html#Argument-list-too-long
> Best regards
> Charlie



--
This message was sent by Atlassian Jira
(v8.3.4#803005)