OK, looks l forgot to copy some dependencies. I just added some more. Try it
again and see if it works or there are new errors.
On 11/22/19, 11:41 AM, "Carlos Rovira" <carlosrov...@apache.org> wrote:
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
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624802842&sdata=BJ5910IacaunwKbzt1eKiiztlD%2FhXCX6aYrmhbtFLew%3D&reserved=0
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
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Frepository.apache.org%2Fsnapshots&data=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624812838&sdata=xhVIDs9lydPLwtFTNjs73jsD6DtA7aSI8B7e%2F1dmDX8%3D&reserved=0
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]
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Release_Step_001%2F10%2Fconsole&data=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624812838&sdata=KlAKy4PzkngLvql3hH%2FNwhjqqT7qrUZnb0iuRXt0ZBQ%3D&reserved=0
El vie., 22 nov. 2019 a las 2:54, Alex Harui (<aha...@adobe.com.invalid>)
escribió:
> Due to this bug:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FSCM-921&data=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624812838&sdata=0hJg3AhN3Iu0OqS4VGoTo0%2FFLk3HtgbaDIclDBUnjj4%3D&reserved=0
> 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" <carlosrov...@apache.org> 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, <apacheroyal...@gmail.com> 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%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624812838&sdata=A7A3I58qJufZKuh%2FApoj1yefxDvhWb34PzV9YO8iwBU%3D&reserved=0
>
>
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C1a2678c85cee422a6c6908d76f83e74a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637100484624812838&sdata=A7A3I58qJufZKuh%2FApoj1yefxDvhWb34PzV9YO8iwBU%3D&reserved=0
