We released 0.9.6 using snapshot. I was told they would not look at my patch unless I added tests. I have not had time to figure out their test system. You are welcome to do that.
Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: Carlos Rovira <[email protected]> Sent: Sunday, November 24, 2019 3:00:43 AM To: [email protected] <[email protected]> Subject: Re: Release Step 001 Succeeded Hi Alex, If we rely on SNAPSHOT, then we'll not be able to release right? If the patch show in the ticket (SCM-921) solved the issue, why don't report it? They could bring a release working version that allow us to release right? Don't know how it worked in the past with a SNAPSHOT version since maven should not allow to release with SNAPSHOT included. Another issue is using our own patched version seems to me something that could bring problems since is something out the eye of everybody but the person(s) that knows about this particularity. thanks El dom., 24 nov. 2019 a las 6:24, Alex Harui (<[email protected]>) escribió: > I manually installed the other 1.11.2-SNAPSHOT maven artifacts in the > local maven repository on the CI server. > > -Alex > > On 11/23/19, 1:50 AM, "Carlos Rovira" <[email protected]> wrote: > > Thanks Alex, > I finally get the RS#1 finally complete. > About dependencies you mentioned, I didn't see any commit from you to > repo > to modify a pom, are you referring to some external dependencies, > maybe in > the windows machine? > Going with RS#2 > Thanks! > > El vie., 22 nov. 2019 a las 20:56, Alex Harui > (<[email protected]>) > escribió: > > > 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" <[email protected]> > 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%7Ca568ac087510493c93a208d770cd9793%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637101900658191131&sdata=9r4M9hpZlQNOPBFKUi7MPK74aLBs9Wwt3YbbyFEWHuo%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%7Ca568ac087510493c93a208d770cd9793%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637101900658191131&sdata=9r4M9hpZlQNOPBFKUi7MPK74aLBs9Wwt3YbbyFEWHuo%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%7Ca568ac087510493c93a208d770cd9793%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637101900658191131&sdata=z4DErf3y%2FjzaNcBUw5l4sPHq5Xl0sw%2FtTnaWKeJ%2FO18%3D&reserved=0 > > > > El vie., 22 nov. 2019 a las 2:54, Alex Harui > (<[email protected] > > >) > > 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%7Ca568ac087510493c93a208d770cd9793%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637101900658201126&sdata=Rs5RHNpSo612CfM0BD2pO0wmF5P9mjDyPRCnvY498lc%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" <[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%7Ca568ac087510493c93a208d770cd9793%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637101900658201126&sdata=ipF5ZtDpx4fwv9e34ixkh1TqeIcWMxhrdkYhJnK4hvQ%3D&reserved=0 > > > > > > > > > > > > > -- > > Carlos Rovira > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ca568ac087510493c93a208d770cd9793%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637101900658201126&sdata=ipF5ZtDpx4fwv9e34ixkh1TqeIcWMxhrdkYhJnK4hvQ%3D&reserved=0 > > > > > > > > -- > Carlos Rovira > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ca568ac087510493c93a208d770cd9793%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637101900658201126&sdata=ipF5ZtDpx4fwv9e34ixkh1TqeIcWMxhrdkYhJnK4hvQ%3D&reserved=0 > > > -- Carlos Rovira https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ca568ac087510493c93a208d770cd9793%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637101900658201126&sdata=ipF5ZtDpx4fwv9e34ixkh1TqeIcWMxhrdkYhJnK4hvQ%3D&reserved=0
