June 2017 - aerogear-dev - Jboss List Archives

by Bruno Oliveira

Good morning, just to let you know we released today the bits for digital signatures and some bug fixes. Have a happy new year sweet hearts. -- abstractj

4 years, 1 month

2
1
0 / 0

Re: [aerogear-dev] AeroGear Digger Logo

by Ali Ok

Hello, According to the voting, logo #6 is the most favorite one. Here is the summary: [image: Inline image 1] I am delighted to present you AeroGear Digger's logo: [image: Inline image 2] Cheers, Ali On Mon, Jun 19, 2017 at 10:40 AM, Ali Ok <aliok(a)redhat.com> wrote: > Hello, > > We would like to pick a logo for the new AeroGear module, Digger [1]. > > James Cobb has already prepared some great designs and now we vote to pick > the best one [2]. > > We have prepared a Google poll (no login required) here: > https://goo.gl/forms/WdUoHecQtrshMkBg1 > > The poll will be open for 10 days (until June 29th 10:00 AM UTC). > > > [1] : https://github.com/aerogear/digger-jenkins > [2] : https://issues.jboss.org/browse/DESIGN-943 > > Cheers, > Ali >

8 years, 9 months

4
3
0 / 0

GSoC Project Blogs

by Polina Koleva

Hey :) Me and Dimitra have decided to create blogs where we can share our experience working on the project so that everyone interested can see our progress. Moreover, a blog can make the initiative GSoC more popular because it is a pity that some students are not familiar with it. My blog <https://polinankoleva.github.io/> is already set up and my first intro post <https://polinankoleva.github.io/personal/2017/06/12/me-the-intro.html> is waiting for you to read it. Soon I plan to add an article about the project itself. Excited to hear your feedback. Stay tuned. Polina -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/GSoC-Project-Blogs-tp13020.html Sent from the aerogear-dev mailing list archive at Nabble.com.

8 years, 11 months

1
1
0 / 0

digger-jenkins repo and dockerhub

by Leonardo Rossetti

Hello, We currently have the following in our digger-jenkins repo[1]: - android-sdk docker image (which includes androidctl cli); - jenkins android slave image; - openshift templates; - some osx related scripts; I wanted to automatically build/push the docker images to dockerhub after a PR is merged but I believe dockerhub has a "per repo" integration, which means that both images would be built/pushed every time we send a pr/commit into this repo. Does anyone know if we can create a "per folder" integration where it detects Dockerfile changes per folder (if we change android-sdk dockerfile it should only build this image) and not re-build and re-push both images on every commit? Other options would be: - Move those images to their own repo; - Create/host a jenkins instance somewhere so we can automate this workflow with custom scripts. Regards, [1] - https://github.com/aerogear/digger-jenkins -- LEONARDO ROSSETTI SOFTWARE ENGINEER Red Hat SP <https://www.redhat.com/> lrossett(a)redhat.com M: 11997030621 <https://red.ht/sig>

9 years

3
7
0 / 0

AeroGear Android Authz 3.1.1

by Daniel Passos

Hi, I just release a new version of Authz (3.1.1). It will be available on Maven Central in 2 days. Bug - AGDROID-602 <https://issues.jboss.org/browse/AGDROID-602> - OAuth2 deleteAccount does not remove the account from memory -- -- Passos

9 years

1
0
0 / 0

GSOC First month update

by Polina Koleva

Hey :) This first month of GSOC is almost finished. The integration of Kafka in UPS is 90% done. We now have our first consumer and producer in the project. The next step is working on Java EE programming model for Kafka. Matthias has already implemented a library kafka-cdi <https://github.com/matzew/kafka-cdi>which provides some basic functionality, so we can extend it if we need something more in the UPS. Another topic that we will work on during the next month is Kafka Security, Kafka Streams and Kafka on Openshift. We are still in process of defining more concrete tasks for these epics. We have done some pull requests and we will be really happy if we receive your feedback so we can improve the code and merge them as soon as possible so we can continue our work. 1) First Kafka consumer <https://github.com/aerogear/aerogear-unifiedpush-server/pull/853> - an addition of first Kafka consumer. It updates metrics how many times the app was opened because of push notification. 2) Set up Kafka test environment <https://github.com/aerogear/aerogear-unifiedpush-server/pull/848> - add really simple Kafka producer/consumer test cases 3) Add Kafka CDI library dependency <https://github.com/aerogear/aerogear-unifiedpush-server/pull/855> - include the library for Kafka CDI in the project 4) Add first Kafka producer <https://github.com/aerogear/aerogear-unifiedpush-server/pull/841> - add a first producer that writes to a topic how many times an app was opened because of a push notification (metrics update) 5) Describe installation of Kafka <https://github.com/aerogear/aerogear-unifiedpush-server/pull/838> - write readme file about the installation of Kafka and how to integrate it with UPS Thanks in advance. Polina

9 years

3
2
0 / 0

Refactoring push-network-proxies

by Jose Miguel Gallas Olmedo

Hi all, I recently create a Docker image of our push FCM proxy, made with Wiremock. Since we are no longer using the FCM proxy in https://github.com/aerogear/push-network-proxies (even the Dockerfile there only consider APNs) I think we could remove it from there and refactor the repository like this: push-network-proxies/ fcm/ Dockerfile ... apns/ Dockerfile ... push-network-proxies-template.yml So that we have everything in the same place. I also made a template for Openshift so that we can setup a testing environment for UPS quickly. I think that's the ultimate point of having the mocks together. WDYT? -- JOSE MIGUEL GALLAS OLMEDO ASSOCIATE QE, mobile Red Hat <https://www.redhat.com/> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/> <https://red.ht/sig>

9 years

2
6
0 / 0

Test email, please ignore

by Dmytro Lisnichenko

Hello, I am sending this email to see the traces in the logs and see how fast it will be delivered. Please ignore it. Thnx.

9 years

1
0
0 / 0

Fwd: [Aerogear-users] AeroGear Digger Logo

by Matthias Wessendorf

---------- Forwarded message ---------- From: Ali Ok <aliok(a)redhat.com> Date: Mon, Jun 19, 2017 at 9:40 AM Subject: [Aerogear-users] AeroGear Digger Logo To: aerogear-users(a)lists.jboss.org Hello, We would like to pick a logo for the new AeroGear module, Digger [1]. James Cobb has already prepared some great designs and now we vote to pick the best one [2]. We have prepared a Google poll (no login required) here: https://goo.gl/forms/WdUoHecQtrshMkBg1 The poll will be open for 10 days (until June 29th 10:00 AM UTC). [1] : https://github.com/aerogear/digger-jenkins [2] : https://issues.jboss.org/browse/DESIGN-943 Cheers, Ali _______________________________________________ Aerogear-users mailing list Aerogear-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf

9 years

1
0
0 / 0

WildFly 11

by Matthias Wessendorf

Hi, while WF 11.0 is not yet release, I'd like to see us getting on to WF 11 on the master branch http://wildfly.org/downloads/ I think that our master branch should be exclusively target the latest from WF stable, which is 11 in the future. So getting to know what's problematic w/ the WF 11-alpha series is a good thing. Comments ? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf

9 years

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

aerogear-dev June 2017