[GitHub] [syncope] mmoayyed commented on a change in pull request #182: NOJIRA - Switch Travis CI to AMD64 Bionic Distro
mmoayyed commented on a change in pull request #182: URL: https://github.com/apache/syncope/pull/182#discussion_r419509630 ## File path: pom.xml ## @@ -2530,6 +2530,7 @@ under the License. **/*.json **/banner.txt **/target/** +**/install-jdk.sh Review comment: Ah, that's much better. I'll see if I can fetch it into the temp directory. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [syncope] ilgrosso commented on a change in pull request #182: NOJIRA - Switch Travis CI to AMD64 Bionic Distro
ilgrosso commented on a change in pull request #182: URL: https://github.com/apache/syncope/pull/182#discussion_r419514983 ## File path: pom.xml ## @@ -2530,6 +2530,7 @@ under the License. **/*.json **/banner.txt **/target/** +**/install-jdk.sh Review comment: maybe `~/bin` as it used to be? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [syncope] ilgrosso commented on pull request #182: NOJIRA - Switch Travis CI to AMD64 Bionic Distro
ilgrosso commented on pull request #182: URL: https://github.com/apache/syncope/pull/182#issuecomment-623469331 @mmoayyed it seems that installing other JDKs is failing, I tried to restart the related steps several times, no luck. Any idea? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [syncope] mmoayyed opened a new pull request #182: NOJIRA - Switch Travis CI to AMD64 Bionic Distro
mmoayyed opened a new pull request #182: URL: https://github.com/apache/syncope/pull/182 The Travis CI trusty image is deprecated. This change switches the distro to Bionic which builds against Ubuntu 18. PS. I also experimented with arm-based builds which are super fast to startup (less than 10 seconds) but they are not as packed as others (No maven, Java installed, etc) and the cache seems somewhat suspicious with those. Bionic should do fine for now. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [syncope] ilgrosso commented on a change in pull request #182: NOJIRA - Switch Travis CI to AMD64 Bionic Distro
ilgrosso commented on a change in pull request #182: URL: https://github.com/apache/syncope/pull/182#discussion_r419503248 ## File path: pom.xml ## @@ -2530,6 +2530,7 @@ under the License. **/*.json **/banner.txt **/target/** +**/install-jdk.sh Review comment: I think we should avoid this. Isn't enough to fetch the `install-jdk` script into a different location, not placed in the checkout directory, to avoid RAT failing? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Still Failing: mmoayyed/syncope#73 (travis - 603f266)
Build Update for mmoayyed/syncope - Build: #73 Status: Still Failing Duration: 9 mins and 39 secs Commit: 603f266 (travis) Author: Misagh Moayyed Message: fetch install-jdk script View the changeset: https://github.com/mmoayyed/syncope/compare/04f3a562a87bbcb40d9238b99500f2618e47ec58...603f26664a85821e20a33e4c58919b98dcfeaf3d View the full build log and details: https://travis-ci.org/github/mmoayyed/syncope/builds/682962065?utm_medium=notification_source=email -- You can unsubscribe from build emails from the mmoayyed/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=23286604_medium=notification_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Re: [DISCUSS] Troubles with release:prepare
On 04/05/20 14:50, Francesco Chicchiriccò wrote: > Thanks Misagh for your reply. > > In my case I've run the command on the same exact platform (e.g. my own > laptop) as I did other times including the last one before this one, e.g. > 2.1.5 / 2.0.14. > > To ensure the SCM section was not causing the issue, anyway, I made this > change on a branch of my own fork: > > https://github.com/ilgrosso/syncope/commit/009b3f8c760cdad1defaa0a8056f1afd221884cd > > Same exact error: release:prepare generated source-release zip for > 2.1.7-SNAPSHOT, not for 2.1.7.ilgrosso as it was instructed to. > > I can spot the problem because a simple > > diff pom.xml pom.xml.releaseBackup > > returns no diff, meaning that pom.xml was not changed. > > I am going to pose the question to Maven user@ list. FTR: https://lists.apache.org/thread.html/a4e00db99a094ff1e06ab19774a00413604cc22a2d8701c76c1ef9f0%40%3Cusers.maven.apache.org%3E As you can read there, my further investigation pointed the skipTests profile guilty, let's see if we can get some support there. Regards. > On 04/05/20 12:23, Misagh Moayyed wrote: >> I have run into this before, but only when: >> >> 1. Running a command-prompt on windows. >> 2. Running a bash on windows, using the likes mingw or babun >> >> In my case, this was caused by a number of things: >> >> 1. Bad ssh-agent that could not communicate correctly with git. >> 2. Somehow, the release plugin thought I was not running commands from the >> project working directory. >> 3. Very old versions of git. >> 4. Weird shell issues. >> >> I could never truly figure out if the issue was windows-specific with maven, >> or some other combination of things. >> >> --Misagh >> >> - Original Message - >>> From: "Francesco Chicchiriccò" >>> To: "dev" >>> Sent: Sunday, May 3, 2020 4:26:01 PM >>> Subject: Re: [DISCUSS] Troubles with release:prepare >>> On 03/05/20 11:20, Jean-Baptiste Onofre wrote: Hi Francesco, Is scm section up to date ? >>> Yes, it is based on gitbox.apache.org and has not actually changed since >>> 2.1.5 / >>> 2.0.14, e.g. last time that release:prepare worked as usual. >>> >>> Regards. >>> > Le 3 mai 2020 à 09:50, Francesco Chicchiriccò a > écrit : > > Hi all, > during the recent release process for 2.0.15 and 2.1.6 I have been > following the > steps in [1] as usual. > > Unfortunately, when I arrived to launch the release:prepare step, I could > not > move forward as the Maven Release plugin, after asking for version to > release > and next development version to set, was not effectively advancing the POM > files. > > The execution of > > mvn -P apache-release release:prepare -Darguments="-P all,docker > -DbuildNumber=syncope-2.1.6" > > left the source files set to 2.1.6-SNAPSHOT and thus produced all > artifacts with > such version, not 2.1.6. (Same happened with 2.0.15). > > After struggling for some time, I finally came to decision to manually > replicate > the various steps normally performed by release:prepare [2]: fortunately, > this > approach was effective, and I could also continue following [1], > including the > release:perform step. > > I took some notes of the manual process in [3]. > > Now I was wondering: what could possibly be the reason of the bad > functioning of > release:prepare? I even tried with older Release plugin and Maven > versions: no > luck. > > As last resort we can always adjust [1] with content from [3], but I'd > rather > give release:prepare a chance. > > WDYT? > Regards. > > [1] http://syncope.apache.org/release-process > [2] > http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html > [3] https://gist.github.com/ilgrosso/b2abd6674290d6fe144704dffbeda418 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Still Failing: mmoayyed/syncope#72 (travis - c2291d3)
Build Update for mmoayyed/syncope - Build: #72 Status: Still Failing Duration: 25 mins and 29 secs Commit: c2291d3 (travis) Author: Misagh Moayyed Message: Update .travis.yml View the changeset: https://github.com/mmoayyed/syncope/compare/36a94d24f889e21a17d9dd576387187ac8dbbaf3...c2291d3c4381177e7634ae0f1ceeb9cce7136807 View the full build log and details: https://travis-ci.org/github/mmoayyed/syncope/builds/682895976?utm_medium=notification_source=email -- You can unsubscribe from build emails from the mmoayyed/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=23286604_medium=notification_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Re: [DISCUSS] Troubles with release:prepare
Thanks Misagh for your reply. In my case I've run the command on the same exact platform (e.g. my own laptop) as I did other times including the last one before this one, e.g. 2.1.5 / 2.0.14. To ensure the SCM section was not causing the issue, anyway, I made this change on a branch of my own fork: https://github.com/ilgrosso/syncope/commit/009b3f8c760cdad1defaa0a8056f1afd221884cd Same exact error: release:prepare generated source-release zip for 2.1.7-SNAPSHOT, not for 2.1.7.ilgrosso as it was instructed to. I can spot the problem because a simple diff pom.xml pom.xml.releaseBackup returns no diff, meaning that pom.xml was not changed. I am going to pose the question to Maven user@ list. Regards. On 04/05/20 12:23, Misagh Moayyed wrote: > I have run into this before, but only when: > > 1. Running a command-prompt on windows. > 2. Running a bash on windows, using the likes mingw or babun > > In my case, this was caused by a number of things: > > 1. Bad ssh-agent that could not communicate correctly with git. > 2. Somehow, the release plugin thought I was not running commands from the > project working directory. > 3. Very old versions of git. > 4. Weird shell issues. > > I could never truly figure out if the issue was windows-specific with maven, > or some other combination of things. > > --Misagh > > - Original Message - >> From: "Francesco Chicchiriccò" >> To: "dev" >> Sent: Sunday, May 3, 2020 4:26:01 PM >> Subject: Re: [DISCUSS] Troubles with release:prepare >> On 03/05/20 11:20, Jean-Baptiste Onofre wrote: >>> Hi Francesco, >>> >>> Is scm section up to date ? >> Yes, it is based on gitbox.apache.org and has not actually changed since >> 2.1.5 / >> 2.0.14, e.g. last time that release:prepare worked as usual. >> >> Regards. >> Le 3 mai 2020 à 09:50, Francesco Chicchiriccò a écrit : Hi all, during the recent release process for 2.0.15 and 2.1.6 I have been following the steps in [1] as usual. Unfortunately, when I arrived to launch the release:prepare step, I could not move forward as the Maven Release plugin, after asking for version to release and next development version to set, was not effectively advancing the POM files. The execution of mvn -P apache-release release:prepare -Darguments="-P all,docker -DbuildNumber=syncope-2.1.6" left the source files set to 2.1.6-SNAPSHOT and thus produced all artifacts with such version, not 2.1.6. (Same happened with 2.0.15). After struggling for some time, I finally came to decision to manually replicate the various steps normally performed by release:prepare [2]: fortunately, this approach was effective, and I could also continue following [1], including the release:perform step. I took some notes of the manual process in [3]. Now I was wondering: what could possibly be the reason of the bad functioning of release:prepare? I even tried with older Release plugin and Maven versions: no luck. As last resort we can always adjust [1] with content from [3], but I'd rather give release:prepare a chance. WDYT? Regards. [1] http://syncope.apache.org/release-process [2] http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html [3] https://gist.github.com/ilgrosso/b2abd6674290d6fe144704dffbeda418 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [DISCUSS] Troubles with release:prepare
I have run into this before, but only when: 1. Running a command-prompt on windows. 2. Running a bash on windows, using the likes mingw or babun In my case, this was caused by a number of things: 1. Bad ssh-agent that could not communicate correctly with git. 2. Somehow, the release plugin thought I was not running commands from the project working directory. 3. Very old versions of git. 4. Weird shell issues. I could never truly figure out if the issue was windows-specific with maven, or some other combination of things. --Misagh - Original Message - > From: "Francesco Chicchiriccò" > To: "dev" > Sent: Sunday, May 3, 2020 4:26:01 PM > Subject: Re: [DISCUSS] Troubles with release:prepare > On 03/05/20 11:20, Jean-Baptiste Onofre wrote: >> Hi Francesco, >> >> Is scm section up to date ? > > Yes, it is based on gitbox.apache.org and has not actually changed since > 2.1.5 / > 2.0.14, e.g. last time that release:prepare worked as usual. > > Regards. > >>> Le 3 mai 2020 à 09:50, Francesco Chicchiriccò a écrit >>> : >>> >>> Hi all, >>> during the recent release process for 2.0.15 and 2.1.6 I have been >>> following the >>> steps in [1] as usual. >>> >>> Unfortunately, when I arrived to launch the release:prepare step, I could >>> not >>> move forward as the Maven Release plugin, after asking for version to >>> release >>> and next development version to set, was not effectively advancing the POM >>> files. >>> >>> The execution of >>> >>> mvn -P apache-release release:prepare -Darguments="-P all,docker >>> -DbuildNumber=syncope-2.1.6" >>> >>> left the source files set to 2.1.6-SNAPSHOT and thus produced all artifacts >>> with >>> such version, not 2.1.6. (Same happened with 2.0.15). >>> >>> After struggling for some time, I finally came to decision to manually >>> replicate >>> the various steps normally performed by release:prepare [2]: fortunately, >>> this >>> approach was effective, and I could also continue following [1], including >>> the >>> release:perform step. >>> >>> I took some notes of the manual process in [3]. >>> >>> Now I was wondering: what could possibly be the reason of the bad >>> functioning of >>> release:prepare? I even tried with older Release plugin and Maven versions: >>> no >>> luck. >>> >>> As last resort we can always adjust [1] with content from [3], but I'd >>> rather >>> give release:prepare a chance. >>> >>> WDYT? >>> Regards. >>> >>> [1] http://syncope.apache.org/release-process >>> [2] >>> http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html >>> [3] https://gist.github.com/ilgrosso/b2abd6674290d6fe144704dffbeda418 > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/
