[jira] [Assigned] (SYNCOPE-1583) For members part of a Dynamic Group, but cannot access group attributes in member mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-1583: --- Assignee: Francesco Chicchiriccò > For members part of a Dynamic Group, but cannot access group attributes in > member mapping > - > > Key: SYNCOPE-1583 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1583 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.15, 2.1.6 > Environment: Red Hat Linux, 2.1.7-SNAPSHOT syncope >Reporter: Arun Kumar >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.16, 2.1.7, 3.0.0 > > > We have users U1, U2 ..etc and Other AnyType Classes as well. We created a > group G1 associated to resource R1 as a dynamic group with rule to > dynamically make Users/AnyObjects based on a schema attribute on the > respective type. When we provision members on G1 and then verify membership > by going to 'members' option on G1, we can see the membership established for > U1. > > But when we have a mapping on a resource R1 with internal attribute - > _groups[G1].schemaAttribute_ mapped to any external attribute example > _groupname_, the groupname always comes through as empty. We see the > membership established in syncope but the group schema attribute value does > not flow as per mapping. > The same above mapping works if G1 is a static group and U1 is made a member > of G1 then we can see the mapping value for _groups[G1].schemaAttribute_ > flow into _groupname_ and thus allow scripts to perform any action based on > the mapped group attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1583) For members part of a Dynamic Group, but cannot access group attributes in member mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1583: Fix Version/s: 3.0.0 2.1.7 2.0.16 > For members part of a Dynamic Group, but cannot access group attributes in > member mapping > - > > Key: SYNCOPE-1583 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1583 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.15, 2.1.6 > Environment: Red Hat Linux, 2.1.7-SNAPSHOT syncope >Reporter: Arun Kumar >Priority: Major > Fix For: 2.0.16, 2.1.7, 3.0.0 > > > We have users U1, U2 ..etc and Other AnyType Classes as well. We created a > group G1 associated to resource R1 as a dynamic group with rule to > dynamically make Users/AnyObjects based on a schema attribute on the > respective type. When we provision members on G1 and then verify membership > by going to 'members' option on G1, we can see the membership established for > U1. > > But when we have a mapping on a resource R1 with internal attribute - > _groups[G1].schemaAttribute_ mapped to any external attribute example > _groupname_, the groupname always comes through as empty. We see the > membership established in syncope but the group schema attribute value does > not flow as per mapping. > The same above mapping works if G1 is a static group and U1 is made a member > of G1 then we can see the mapping value for _groups[G1].schemaAttribute_ > flow into _groupname_ and thus allow scripts to perform any action based on > the mapped group attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1583) For members part of a Dynamic Group, but cannot access group attributes in member mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1583: Component/s: core > For members part of a Dynamic Group, but cannot access group attributes in > member mapping > - > > Key: SYNCOPE-1583 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1583 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.1.7 > Environment: Red Hat Linux, 2.1.7-SNAPSHOT syncope >Reporter: Arun Kumar >Priority: Major > > We have users U1, U2 ..etc and Other AnyType Classes as well. We created a > group G1 associated to resource R1 as a dynamic group with rule to > dynamically make Users/AnyObjects based on a schema attribute on the > respective type. When we provision members on G1 and then verify membership > by going to 'members' option on G1, we can see the membership established for > U1. > > But when we have a mapping on a resource R1 with internal attribute - > _groups[G1].schemaAttribute_ mapped to any external attribute example > _groupname_, the groupname always comes through as empty. We see the > membership established in syncope but the group schema attribute value does > not flow as per mapping. > The same above mapping works if G1 is a static group and U1 is made a member > of G1 then we can see the mapping value for _groups[G1].schemaAttribute_ > flow into _groupname_ and thus allow scripts to perform any action based on > the mapped group attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1583) For members part of a Dynamic Group, but cannot access group attributes in member mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1583: Affects Version/s: (was: 2.1.7) 2.0.15 2.1.6 > For members part of a Dynamic Group, but cannot access group attributes in > member mapping > - > > Key: SYNCOPE-1583 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1583 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.15, 2.1.6 > Environment: Red Hat Linux, 2.1.7-SNAPSHOT syncope >Reporter: Arun Kumar >Priority: Major > > We have users U1, U2 ..etc and Other AnyType Classes as well. We created a > group G1 associated to resource R1 as a dynamic group with rule to > dynamically make Users/AnyObjects based on a schema attribute on the > respective type. When we provision members on G1 and then verify membership > by going to 'members' option on G1, we can see the membership established for > U1. > > But when we have a mapping on a resource R1 with internal attribute - > _groups[G1].schemaAttribute_ mapped to any external attribute example > _groupname_, the groupname always comes through as empty. We see the > membership established in syncope but the group schema attribute value does > not flow as per mapping. > The same above mapping works if G1 is a static group and U1 is made a member > of G1 then we can see the mapping value for _groups[G1].schemaAttribute_ > flow into _groupname_ and thus allow scripts to perform any action based on > the mapped group attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1583) For members part of a Dynamic Group, but cannot access group attributes in member mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162584#comment-17162584 ] ASF subversion and git services commented on SYNCOPE-1583: -- Commit ecf2975e13a21a32c59a2614e2e2b61379f41832 in syncope's branch refs/heads/2_1_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=ecf2975 ] [SYNCOPE-1583] Fix > For members part of a Dynamic Group, but cannot access group attributes in > member mapping > - > > Key: SYNCOPE-1583 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1583 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.15, 2.1.6 > Environment: Red Hat Linux, 2.1.7-SNAPSHOT syncope >Reporter: Arun Kumar >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.16, 2.1.7, 3.0.0 > > > We have users U1, U2 ..etc and Other AnyType Classes as well. We created a > group G1 associated to resource R1 as a dynamic group with rule to > dynamically make Users/AnyObjects based on a schema attribute on the > respective type. When we provision members on G1 and then verify membership > by going to 'members' option on G1, we can see the membership established for > U1. > > But when we have a mapping on a resource R1 with internal attribute - > _groups[G1].schemaAttribute_ mapped to any external attribute example > _groupname_, the groupname always comes through as empty. We see the > membership established in syncope but the group schema attribute value does > not flow as per mapping. > The same above mapping works if G1 is a static group and U1 is made a member > of G1 then we can see the mapping value for _groups[G1].schemaAttribute_ > flow into _groupname_ and thus allow scripts to perform any action based on > the mapped group attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1583) For members part of a Dynamic Group, but cannot access group attributes in member mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162586#comment-17162586 ] ASF subversion and git services commented on SYNCOPE-1583: -- Commit 89628f33d37fa0a8855d6813880430692d9d2cab in syncope's branch refs/heads/2_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=89628f3 ] [SYNCOPE-1583] Fix > For members part of a Dynamic Group, but cannot access group attributes in > member mapping > - > > Key: SYNCOPE-1583 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1583 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.15, 2.1.6 > Environment: Red Hat Linux, 2.1.7-SNAPSHOT syncope >Reporter: Arun Kumar >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.16, 2.1.7, 3.0.0 > > > We have users U1, U2 ..etc and Other AnyType Classes as well. We created a > group G1 associated to resource R1 as a dynamic group with rule to > dynamically make Users/AnyObjects based on a schema attribute on the > respective type. When we provision members on G1 and then verify membership > by going to 'members' option on G1, we can see the membership established for > U1. > > But when we have a mapping on a resource R1 with internal attribute - > _groups[G1].schemaAttribute_ mapped to any external attribute example > _groupname_, the groupname always comes through as empty. We see the > membership established in syncope but the group schema attribute value does > not flow as per mapping. > The same above mapping works if G1 is a static group and U1 is made a member > of G1 then we can see the mapping value for _groups[G1].schemaAttribute_ > flow into _groupname_ and thus allow scripts to perform any action based on > the mapped group attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1583) For members part of a Dynamic Group, but cannot access group attributes in member mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162585#comment-17162585 ] ASF subversion and git services commented on SYNCOPE-1583: -- Commit b96970ce7c3511d990b6a0ca7e871ff21e156ce3 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=b96970c ] [SYNCOPE-1583] Fix > For members part of a Dynamic Group, but cannot access group attributes in > member mapping > - > > Key: SYNCOPE-1583 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1583 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.15, 2.1.6 > Environment: Red Hat Linux, 2.1.7-SNAPSHOT syncope >Reporter: Arun Kumar >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.16, 2.1.7, 3.0.0 > > > We have users U1, U2 ..etc and Other AnyType Classes as well. We created a > group G1 associated to resource R1 as a dynamic group with rule to > dynamically make Users/AnyObjects based on a schema attribute on the > respective type. When we provision members on G1 and then verify membership > by going to 'members' option on G1, we can see the membership established for > U1. > > But when we have a mapping on a resource R1 with internal attribute - > _groups[G1].schemaAttribute_ mapped to any external attribute example > _groupname_, the groupname always comes through as empty. We see the > membership established in syncope but the group schema attribute value does > not flow as per mapping. > The same above mapping works if G1 is a static group and U1 is made a member > of G1 then we can see the mapping value for _groups[G1].schemaAttribute_ > flow into _groupname_ and thus allow scripts to perform any action based on > the mapped group attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1583) For members part of a Dynamic Group, but cannot access group attributes in member mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1583. - Resolution: Fixed > For members part of a Dynamic Group, but cannot access group attributes in > member mapping > - > > Key: SYNCOPE-1583 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1583 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.15, 2.1.6 > Environment: Red Hat Linux, 2.1.7-SNAPSHOT syncope >Reporter: Arun Kumar >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.16, 2.1.7, 3.0.0 > > > We have users U1, U2 ..etc and Other AnyType Classes as well. We created a > group G1 associated to resource R1 as a dynamic group with rule to > dynamically make Users/AnyObjects based on a schema attribute on the > respective type. When we provision members on G1 and then verify membership > by going to 'members' option on G1, we can see the membership established for > U1. > > But when we have a mapping on a resource R1 with internal attribute - > _groups[G1].schemaAttribute_ mapped to any external attribute example > _groupname_, the groupname always comes through as empty. We see the > membership established in syncope but the group schema attribute value does > not flow as per mapping. > The same above mapping works if G1 is a static group and U1 is made a member > of G1 then we can see the mapping value for _groups[G1].schemaAttribute_ > flow into _groupname_ and thus allow scripts to perform any action based on > the mapped group attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Errored: apache/syncope#6718 (2_0_X - 89628f3)
Build Update for apache/syncope - Build: #6718 Status: Errored Duration: 18 mins and 50 secs Commit: 89628f3 (2_0_X) Author: Francesco Chicchiriccò Message: [SYNCOPE-1583] Fix View the changeset: https://github.com/apache/syncope/compare/54e1ecfb5b8d...89628f33d37f View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/710660692?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Broken: apache/syncope#6716 (2_1_X - ecf2975)
Build Update for apache/syncope - Build: #6716 Status: Broken Duration: 35 mins and 26 secs Commit: ecf2975 (2_1_X) Author: Francesco Chicchiriccò Message: [SYNCOPE-1583] Fix View the changeset: https://github.com/apache/syncope/compare/7289af6ea39a...ecf2975e13a2 View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/710660669?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Broken: apache/syncope#6719 (master - 4a3d7eb)
Build Update for apache/syncope - Build: #6719 Status: Broken Duration: 37 mins and 50 secs Commit: 4a3d7eb (master) Author: Francesco Chicchiriccò Message: Fixing SRA Docker image generation View the changeset: https://github.com/apache/syncope/compare/b96970ce7c35...4a3d7eb2a8a9 View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/710671416?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
[jira] [Commented] (SYNCOPE-1583) For members part of a Dynamic Group, but cannot access group attributes in member mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162684#comment-17162684 ] ASF subversion and git services commented on SYNCOPE-1583: -- Commit 2786609b4e47e2371cca187e0f14299a258ae65f in syncope's branch refs/heads/2_1_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=2786609 ] [SYNCOPE-1583] Fix IT run > For members part of a Dynamic Group, but cannot access group attributes in > member mapping > - > > Key: SYNCOPE-1583 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1583 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.15, 2.1.6 > Environment: Red Hat Linux, 2.1.7-SNAPSHOT syncope >Reporter: Arun Kumar >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.16, 2.1.7, 3.0.0 > > > We have users U1, U2 ..etc and Other AnyType Classes as well. We created a > group G1 associated to resource R1 as a dynamic group with rule to > dynamically make Users/AnyObjects based on a schema attribute on the > respective type. When we provision members on G1 and then verify membership > by going to 'members' option on G1, we can see the membership established for > U1. > > But when we have a mapping on a resource R1 with internal attribute - > _groups[G1].schemaAttribute_ mapped to any external attribute example > _groupname_, the groupname always comes through as empty. We see the > membership established in syncope but the group schema attribute value does > not flow as per mapping. > The same above mapping works if G1 is a static group and U1 is made a member > of G1 then we can see the mapping value for _groups[G1].schemaAttribute_ > flow into _groupname_ and thus allow scripts to perform any action based on > the mapped group attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1583) For members part of a Dynamic Group, but cannot access group attributes in member mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162685#comment-17162685 ] ASF subversion and git services commented on SYNCOPE-1583: -- Commit 04b107b2353bbe93cdaccf59c8c136ac3b7e46e1 in syncope's branch refs/heads/2_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=04b107b ] [SYNCOPE-1583] Fix IT run > For members part of a Dynamic Group, but cannot access group attributes in > member mapping > - > > Key: SYNCOPE-1583 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1583 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.15, 2.1.6 > Environment: Red Hat Linux, 2.1.7-SNAPSHOT syncope >Reporter: Arun Kumar >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.16, 2.1.7, 3.0.0 > > > We have users U1, U2 ..etc and Other AnyType Classes as well. We created a > group G1 associated to resource R1 as a dynamic group with rule to > dynamically make Users/AnyObjects based on a schema attribute on the > respective type. When we provision members on G1 and then verify membership > by going to 'members' option on G1, we can see the membership established for > U1. > > But when we have a mapping on a resource R1 with internal attribute - > _groups[G1].schemaAttribute_ mapped to any external attribute example > _groupname_, the groupname always comes through as empty. We see the > membership established in syncope but the group schema attribute value does > not flow as per mapping. > The same above mapping works if G1 is a static group and U1 is made a member > of G1 then we can see the mapping value for _groups[G1].schemaAttribute_ > flow into _groupname_ and thus allow scripts to perform any action based on > the mapped group attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Migration to new ci-builds.a.o
FYI all seems to be working: https://ci-builds.apache.org./job/Syncope/ Regards. On 21/07/20 09:15, Francesco Chicchiriccò wrote: > Hi all, > the news stroke me by surprise but according to the mailing list thread [1], > we have to migrate all our Jenkins jobs to the new ci-builds.a.o server(s). > > I have created a ticket for establishing Apache Syncope folder [2] and will > try to migrate as many jobs as I can, but I would very likely need an > assistance with the release / publishing jobs, please let me know if someone > could help me with that. > > Thanks! > > [1] > https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E > [2] https://issues.apache.org/jira/browse/INFRA-20567 -- 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/
Passed: apache/syncope#6721 (2_0_X - 04b107b)
Build Update for apache/syncope - Build: #6721 Status: Passed Duration: 19 mins and 3 secs Commit: 04b107b (2_0_X) Author: Francesco Chicchiriccò Message: [SYNCOPE-1583] Fix IT run View the changeset: https://github.com/apache/syncope/compare/89628f33d37f...04b107b2353b View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/710691385?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Fixed: apache/syncope#6720 (2_1_X - 2786609)
Build Update for apache/syncope - Build: #6720 Status: Fixed Duration: 37 mins and 25 secs Commit: 2786609 (2_1_X) Author: Francesco Chicchiriccò Message: [SYNCOPE-1583] Fix IT run View the changeset: https://github.com/apache/syncope/compare/ecf2975e13a2...2786609b4e47 View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/710691383?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Broken: apache/syncope#6719 (master - 4a3d7eb)
Build Update for apache/syncope - Build: #6719 Status: Broken Duration: 21 mins and 22 secs Commit: 4a3d7eb (master) Author: Francesco Chicchiriccò Message: Fixing SRA Docker image generation View the changeset: https://github.com/apache/syncope/compare/b96970ce7c35...4a3d7eb2a8a9 View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/710671416?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Failed: apache/syncope#6723 (master - 589c1c0)
Build Update for apache/syncope - Build: #6723 Status: Failed Duration: 35 mins and 3 secs Commit: 589c1c0 (master) Author: Francesco Chicchiriccò Message: Upgrading Camel View the changeset: https://github.com/apache/syncope/compare/4a3d7eb2a8a9...589c1c0675a4 View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/710713741?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Errored: apache/syncope#6723 (master - 589c1c0)
Build Update for apache/syncope - Build: #6723 Status: Errored Duration: 1 hr, 4 mins, and 31 secs Commit: 589c1c0 (master) Author: Francesco Chicchiriccò Message: Upgrading Camel View the changeset: https://github.com/apache/syncope/compare/4a3d7eb2a8a9...589c1c0675a4 View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/710713741?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Errored: apache/syncope#6723 (master - 589c1c0)
Build Update for apache/syncope - Build: #6723 Status: Errored Duration: 21 mins and 26 secs Commit: 589c1c0 (master) Author: Francesco Chicchiriccò Message: Upgrading Camel View the changeset: https://github.com/apache/syncope/compare/4a3d7eb2a8a9...589c1c0675a4 View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/710713741?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Errored: apache/syncope#6724 (2_0_X - f628671)
Build Update for apache/syncope - Build: #6724 Status: Errored Duration: 20 mins and 12 secs Commit: f628671 (2_0_X) Author: Francesco Chicchiriccò Message: Upgrading maven-archetype-plugin View the changeset: https://github.com/apache/syncope/compare/7ace71ceca19...f62867113a68 View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/710796397?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Failed: apache/syncope#6725 (master - 8ec564f)
Build Update for apache/syncope - Build: #6725 Status: Failed Duration: 1 hr, 9 mins, and 44 secs Commit: 8ec564f (master) Author: Francesco Chicchiriccò Message: Upgrading maven-archetype-plugin View the changeset: https://github.com/apache/syncope/compare/589c1c0675a4...8ec564fb2b64 View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/710796404?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
Passed: apache/syncope#6725 (master - 8ec564f)
Build Update for apache/syncope - Build: #6725 Status: Passed Duration: 39 mins and 11 secs Commit: 8ec564f (master) Author: Francesco Chicchiriccò Message: Upgrading maven-archetype-plugin View the changeset: https://github.com/apache/syncope/compare/589c1c0675a4...8ec564fb2b64 View the full build log and details: https://travis-ci.org/github/apache/syncope/builds/710796404?utm_medium=notification&utm_source=email -- You can unsubscribe from build emails from the apache/syncope repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=3236582&utm_medium=notification&utm_source=email. Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email. Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
