You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Karl Heinz Marbaise <kh...@gmx.de> on 2018/09/14 05:40:11 UTC

https://issues.apache.org/jira/browse/MNG-6311

Hi Sylwester,

as you wrote the IT's are fine and now you can merge that branch back to 
master. Just to be sure check the master if something has came into 
master ...and make a rebase against master...(I expect that you don't 
get something).

If you get something new to the rebase and make a push with a 
--force-with-lease to your branch and let the CI check this new 
state..afterwards redo the loop from the beginning...

And finally you should get a simple fast forward while merging into 
master...

And afterwards you can close the ticket as done (delete the remote 
branch and your local one). Best would be to add the reference to the 
git commit within the ticket.

Kind regards
Karl Heinz Marbaise

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: https://issues.apache.org/jira/browse/MNG-6311

Posted by Sylwester Lachiewicz <sl...@gmail.com>.
First merge, and first failed build ;-)

Jenkins - Run ITs Linux Java 8 :
remote file operation failed:
/home/jenkins/jenkins-slave/workspace/maven-box_maven_master-DVEN5KAF4FLE3WDK7SWFNYUY4YZ7X45JVWYY6FZT5ZEB3CLWABVQ/test
at hudson.remoting.Channel@f03fce5:H27: java.nio.file.FileSystemException:
/home/jenkins/jenkins-slave/workspace/maven-box_maven_master-DVEN5KAF4FLE3WDK7SWFNYUY4YZ7X45JVWYY6FZT5ZEB3CLWABVQ/test:
No space left on device

Another thing about build - I see errors like: [windows-jdk8]
java.lang.IllegalArgumentException: Cannot relativize
'C:\mvn-it-0.tmp\core-it-support\core-it-plugins\maven-it-plugin-plexus-utils-new\target\maven-it-plugin-plexus-utils-new-2.1-SNAPSHOT.jar'
relatively to '/mvn-it-0.tmp'

If all Jenkins Windows workspaces are on disk C, I think that change [1]
can solve the problem. Can anyone check?

Best regards,
Sylwester

[1]
https://github.com/apache/maven/commit/0e7a8531ddc77a4b85ada49a74092c68b1a46f8f


pt., 14 wrz 2018 o 07:40 użytkownik Karl Heinz Marbaise <kh...@gmx.de>
napisał:

> Hi Sylwester,
>
> as you wrote the IT's are fine and now you can merge that branch back to
> master. Just to be sure check the master if something has came into
> master ...and make a rebase against master...(I expect that you don't
> get something).
>
> If you get something new to the rebase and make a push with a
> --force-with-lease to your branch and let the CI check this new
> state..afterwards redo the loop from the beginning...
>
> And finally you should get a simple fast forward while merging into
> master...
>
> And afterwards you can close the ticket as done (delete the remote
> branch and your local one). Best would be to add the reference to the
> git commit within the ticket.
>
> Kind regards
> Karl Heinz Marbaise
>