Hello! i build c++ software on a debian virtual maschine. Jenkins is running on a Windows Server 2008 R2 VM. The debian virtual maschine uses the Java slave agent.
In the past i used the Mercurial plugin the get the source code from the SCM server, due to new requirements for the build i had to make the checkout with a script, because i added a manifestfile for checkout each repository by changeset (the build needs to checkout about 11 repos! Not all tip!) The build is running by Make and is without problems! ##Here my problem: When i want now to make a deb package i get a acess right violation! wron acess rights 777 or earlyer 700! so fare so clear i had to adjust the rights to 755 for the fimewarefile! I did this! but ...problem is still there!!! I don't know what the prloblem exaktly is, don't get these acess violation, when i call the scripts direct from shell... Here is a part of the log with the error message (in german in know... sorry!) ... Creating Product ... ============================================================= dpkg-deb: Control-Verzeichnis hat falsche Zugriffsrechte 777 (muss >=0755 und <=0775 sein) dpkg-deb: Paket »Product« wird in »Product.deb« gebaut. chmod: Zugriff auf „Product.deb“ nicht möglich: Datei oder Verzeichnis nicht gefunden Creating installation application (arm-linux-gnueabi-g++) ... ============================================================= OK ... Does anyone had this experiance in the past, that Jenkins and shell have different rights? But run as same user? We checked it of course with: echo "running whoami" & whoami echo "running groups" & groups ... Please help! Thank you all! -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
