Re: Travis integration working from individual project forks

Am 15.11.2017 um 00:46 schrieb Werner Keil: > So Travis works while Jenkins builds for the same artifacts keep failing? I've only integrated the main project incubator-tamaya, since all other projects have compilation/test failures after the SPI changes. It was only meant as a prototype ;-)

Re: Travis integration working from individual project forks

Am 15.11.2017 um 01:25 schrieb Anatole Tresch: > Wow, cool! > > If we add the travis file they should also end up in the Github mirror, I > suggest. Does that not work then? No, I've added the file to the main incubator-tamaya project, but you need a travis account, which is linked to a Github

Fwd: [jira] [Resolved] (INFRA-15493) Configure redirect from http to https

Hi, just fyi - I don't really get why SSL as default is not wanted Cheers, Phil Weitergeleitete Nachricht Betreff: [jira] [Resolved] (INFRA-15493) Configure redirect from http to https Datum: Wed, 15 Nov 2017 01:41:00 + (UTC) Von: Greg Stein (JIRA)

Jenkins build is unstable: Tamaya-Extensions-Master #1156

See

Jenkins build is back to normal : Tamaya-Sandbox-Master » Apache Tamaya Modules - Validation #1136

See

Jenkins build is back to stable : Tamaya-Sandbox-Master » Apache Tamaya Modules - JMX Support #1136

See

Jenkins build is back to normal : Tamaya-Sandbox-Master » Apache Tamaya Modules - Consul #1136

See

Re: Travis integration working from individual project forks

Wow, cool! If we add the travis file they should also end up in the Github mirror, I suggest. Does that not work then? 2017-11-15 0:11 GMT+01:00 P. Ottlinger : > Hi, > > Travis integration seems to be working fine :-) > At least the first build went through successfully

Jenkins build is back to normal : Tamaya-Sandbox-Master » Apache Tamaya Modules - etcd PropertySource #1136

See

Build failed in Jenkins: Tamaya-Extensions-Master #1155

See -- Started by upstream project "Tamaya-Master-branch" build number 1272 originally caused by: Started by timer Started by upstream project "Tamaya-Master-branch" build

Jenkins build is unstable: Tamaya-Extensions-Master-with-Coverage #187

See

[jira] [Commented] (TAMAYA-300) Provide a Tamaya integration module for OSGI ConfigAdmin

[ https://issues.apache.org/jira/browse/TAMAYA-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252715#comment-16252715 ] ASF subversion and git services commented on TAMAYA-300: Commit

Build failed in Jenkins: Tamaya-Extensions-Master #1154

See Changes: [anatole] TAMAYA-300 Added additional tests, fixed absolute key issue. -- Started by an SCM change [EnvInject] - Loading node environment variables.

Re: Travis integration working from individual project forks

So Travis works while Jenkins builds for the same artifacts keep failing? Am 15.11.2017 00:11 schrieb "P. Ottlinger" : > Hi, > > Travis integration seems to be working fine :-) > At least the first build went through successfully in contrast to the > current situation on

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Modules - Validation #1135

See -- [INFO] [INFO]

Jenkins build is still unstable: Tamaya-Sandbox-Master » Apache Tamaya Modules - JMX Support #1135

See

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Modules - etcd PropertySource #1135

See -- [INFO] [INFO]

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Modules - Consul #1135

See -- [INFO] [INFO]

Build failed in Jenkins: Tamaya-Sandbox-Master #1135

See -- [...truncated 644.25 KB...] [INFO] Will parse SCM ignores for exclusions... [INFO] Finished adding exclusions from SCM ignore files. [INFO] 61 implicit excludes (use -debug

Travis integration working from individual project forks

Hi, Travis integration seems to be working fine :-) At least the first build went through successfully in contrast to the current situation on Jenkins Not sure if you guys see the result, but it is GREEN: https://travis-ci.org/ottlinger/incubator-tamaya Does anyone know if INFRA can enable

Build failed in Jenkins: Tamaya-Extensions-Master-with-Coverage #186

See -- [...truncated 730.47 KB...] 11:10:40 PM PIT >> FINE : Running 2 units stdout : Installing PIT agent stderr : 11:10:41 PM PIT >> FINE : Running mutation

Build failed in Jenkins: Tamaya-Extensions-Master #1153

See -- Started by upstream project "Tamaya-Master-branch" build number 1271 originally caused by: Started by an SCM change Started by upstream project "Tamaya-Master-branch"

Build failed in Jenkins: Tamaya-Branch-Master-with-Coverage #94

See Changes: [pottlinger] Try-out integration with travis -- [...truncated 4.19 MB...] stderr : Nov 14, 2017 11:06:51 PM

Build failed in Jenkins: Tamaya-Site-Master #686

See Changes: [pottlinger] Try-out integration with travis -- [...truncated 84.20 KB...] Generating

Build failed in Jenkins: Tamaya-Extensions-Master-with-Coverage #185

See -- [...truncated 343.24 KB...] [INFO] Installing

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Modules - etcd PropertySource #1134

See -- [INFO] [INFO]

Jenkins build is back to normal : Tamaya-Sandbox-Master » Apache Tamaya Modules - PropertySources #1134

See

Build failed in Jenkins: Tamaya-Sandbox-Master #1134

See -- [...truncated 636.14 KB...] [INFO] Exclude: **/*banner.txt [INFO] Exclude: banner.txt [INFO] Exclude: .git [INFO] Exclude: derby.log [INFO] Exclude: **/bootstrap-* [INFO]

Jenkins build became unstable: Tamaya-Sandbox-Master » Apache Tamaya Modules - JMX Support #1134

See

Jenkins build is back to normal : Tamaya-Sandbox-Master » Apache Tamaya Modules - Hazelcast PropertySource #1134

See

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Modules - Validation #1134

See -- [INFO] [INFO]

Jenkins build is back to normal : Tamaya-Sandbox-Master » Apache Tamaya Modules - Metamodel #1134

See

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Modules - Consul #1134

See -- [INFO] [INFO]

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Modules - PropertySources #1133

See -- [INFO] [INFO]

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Modules - Consul #1133

See -- [INFO] [INFO]

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Modules - Hazelcast PropertySource #1133

See -- [INFO] [INFO]

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Modules - etcd PropertySource #1133

See -- [INFO] [INFO]

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Modules - Metamodel #1133

See -- [INFO] [INFO]

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Modules - Validation #1133

See -- [INFO] [INFO]

Build failed in Jenkins: Tamaya-Extensions-Master-with-Coverage #184

See -- [...truncated 344.13 KB...] [INFO] Installing to

Build failed in Jenkins: Tamaya-Extensions-Master #1152

See -- Started by upstream project "Tamaya-Master-branch" build number 1270 originally caused by: Started by an SCM change Started by upstream project "Tamaya-Master-branch"

Build failed in Jenkins: Tamaya-Branch-Master-with-Coverage #93

See Changes: [anatole] TAMAYA-274 Made isScannable a default method, fixed javadocs. [anatole] TAMAYA-318 Moved spi-support as API base implementation package to [anatole] TAMAYA-318 Moved

Build failed in Jenkins: Tamaya-Site-Master #685

See Changes: [anatole] TAMAYA-274 Made isScannable a default method, fixed javadocs. [anatole] TAMAYA-318 Moved spi-support as API base implementation package to [anatole] TAMAYA-318 Moved spi-support as API

Build failed in Jenkins: Tamaya-Extensions-Master #1151

See Changes: [anatole] TAMAYA-274 Added Java 8 supplier based methods. [anatole] TAMAYA-274 Fixed javadocs. [anatole] TAMAYA-260 Added MP styled configuration builder. [anatole] TAMAYA-318 Moved

Build failed in Jenkins: Tamaya-Extensions-Master-with-Coverage #183

See Changes: [anatole] TAMAYA-274 Added Java 8 supplier based methods. [anatole] TAMAYA-274 Fixed javadocs. [anatole] TAMAYA-260 Added MP styled configuration builder. [anatole]

[jira] [Commented] (TAMAYA-318) Move the SPI Support from Extensions to API

[ https://issues.apache.org/jira/browse/TAMAYA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251149#comment-16251149 ] ASF subversion and git services commented on TAMAYA-318: Commit

[jira] [Commented] (TAMAYA-318) Move the SPI Support from Extensions to API

[ https://issues.apache.org/jira/browse/TAMAYA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251145#comment-16251145 ] ASF subversion and git services commented on TAMAYA-318: Commit

[jira] [Commented] (TAMAYA-318) Move the SPI Support from Extensions to API

[ https://issues.apache.org/jira/browse/TAMAYA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251147#comment-16251147 ] ASF subversion and git services commented on TAMAYA-318: Commit

[jira] [Commented] (TAMAYA-274) Switching to Java8

[ https://issues.apache.org/jira/browse/TAMAYA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251143#comment-16251143 ] ASF subversion and git services commented on TAMAYA-274: Commit

[jira] [Commented] (TAMAYA-318) Move the SPI Support from Extensions to API

[ https://issues.apache.org/jira/browse/TAMAYA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251146#comment-16251146 ] ASF subversion and git services commented on TAMAYA-318: Commit

[jira] [Commented] (TAMAYA-318) Move the SPI Support from Extensions to API

[ https://issues.apache.org/jira/browse/TAMAYA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251150#comment-16251150 ] ASF subversion and git services commented on TAMAYA-318: Commit

[jira] [Commented] (TAMAYA-260) Implement Microprofile.io Config API

[ https://issues.apache.org/jira/browse/TAMAYA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251144#comment-16251144 ] ASF subversion and git services commented on TAMAYA-260: Commit

[jira] [Commented] (TAMAYA-274) Switching to Java8

[ https://issues.apache.org/jira/browse/TAMAYA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251142#comment-16251142 ] ASF subversion and git services commented on TAMAYA-274: Commit

[jira] [Commented] (TAMAYA-274) Switching to Java8

[ https://issues.apache.org/jira/browse/TAMAYA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251129#comment-16251129 ] ASF subversion and git services commented on TAMAYA-274: Commit

[jira] [Commented] (TAMAYA-318) Move the SPI Support from Extensions to API

[ https://issues.apache.org/jira/browse/TAMAYA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251133#comment-16251133 ] ASF subversion and git services commented on TAMAYA-318: Commit

[jira] [Commented] (TAMAYA-318) Move the SPI Support from Extensions to API

[ https://issues.apache.org/jira/browse/TAMAYA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251134#comment-16251134 ] ASF subversion and git services commented on TAMAYA-318: Commit

[jira] [Commented] (TAMAYA-318) Move the SPI Support from Extensions to API

[ https://issues.apache.org/jira/browse/TAMAYA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251130#comment-16251130 ] ASF subversion and git services commented on TAMAYA-318: Commit

[jira] [Commented] (TAMAYA-318) Move the SPI Support from Extensions to API

[ https://issues.apache.org/jira/browse/TAMAYA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251132#comment-16251132 ] ASF subversion and git services commented on TAMAYA-318: Commit

[jira] [Commented] (TAMAYA-318) Move the SPI Support from Extensions to API

[ https://issues.apache.org/jira/browse/TAMAYA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251131#comment-16251131 ] ASF subversion and git services commented on TAMAYA-318: Commit

Re: automatic redirect http->https

Hi, Am 13.11.2017 um 08:23 schrieb P. Ottlinger: > any objections to configure an automatic redirect from http to https for > our project webpages? I've filed https://issues.apache.org/jira/browse/INFRA-15493 to configure a permanent redirect to SSL. Cheers, Phil