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/**
+
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/**
+
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?
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
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/**
+
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:
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
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:
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
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
10 matches
Mail list logo
