Hi Alex, I updated the pom to exactly the same we had for JGIT, with the 1.11.2-SNAPSHOT. But is failing [1]
[WARNING] The POM for org.apache.maven.scm:maven-scm-api:jar:1.11.2-SNAPSHOT is missing, no dependency information available [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:branch (default-cli) on project royale-compiler-parent: Execution default-cli of goal org.apache.maven.plugins:maven-release-plugin:2.5.3:branch failed: Plugin org.apache.maven.plugins:maven-release-plugin:2.5.3 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 -> org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: Failed to read artifact descriptor for org.apache.maven.scm:maven-scm-provider-jgit:jar:1.11.2-SNAPSHOT: Failure to find org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT in http://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced -> [Help 1] Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure to find org.apache.maven.scm:maven-scm-providers-git:pom:1.11.2-SNAPSHOT in http://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced Don't know why it's not capapble to find that SNAPSHOT version. I look for some snapshot repo removed but didn't found. Another separate issue I finding is that I need to restart Jenkins many times due to the process failing to not find Java8. Restarting solves the issue, but don't understand why it needs to be restart so many times in short periods of time. [1] http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001/10/console El vie., 22 nov. 2019 a las 2:54, Alex Harui (<[email protected]>) escribió: > Due to this bug: https://issues.apache.org/jira/browse/SCM-921 > I think you have to use 1.11.2-SNAPSHOT which I installed on the VM. > > If you look at the console output, it looks like the commit happened, but > it didn't happen which is why the git status still shows modified files. > > I also changed the developbranchname in build.properties. > > -Alex > > On 11/21/19, 3:56 PM, "Carlos Rovira" <[email protected]> wrote: > > Hi, > > restarting Jenkins make Java8 work again mysteriously. > Now, following this steps from Remote Desktop in CI Server, I'm having > trouble and don't know what to do. Any suggestions? This the output in > CMD: > > > cd C:\jenkins\workspace\Royale_Release_Step_001 > > git push > > fatal: The current branch release/0.9.7 has no upstream branch. > To push the current branch and set the remote as upstream, use > > git push --set-upstream origin release/0.9.7 > > Thanks > > El vie., 22 nov. 2019 a las 0:13, <[email protected]> escribió: > > > Log in to the server, open a command prompt, change directory to > > C:\jenkins\workspace\Royale_Release_Step_001 and run the following > commands: > > git push > > git checkout release/0.9.7 > > git push -u origin release/0.9.7 > > > > You will need your Apache/Github username and 2FA token. > > > > -- > Carlos Rovira > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc46ddf8a48f84d65d54c08d76ede77b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637099774084757226&sdata=xCzKIudmOHpvJoP26sEiUgLG1nIjiJ5NpMvGCowX2ac%3D&reserved=0 > > > -- Carlos Rovira http://about.me/carlosrovira
