From matzew at apache.org Fri Dec 2 05:05:10 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 2 Dec 2016 11:05:10 +0100 Subject: [aerogear-dev] Updating APNs to HTTP/2 usage (AGPUSH-1452) - some questions about authentification with Apple Message-ID: Hey guys, we are planing the estimates and amount of work needed to bring our APNs API calls to latest and greatest. Besides the HTTP/2 stuff, Apple has some other interesting changes: * AGPUSH-1482 one certificate for push * AGPUSH-1900 Token based authentification I think this naturally leads to a few questions - AGPUSH-1482 With this Apple removes the need for different certificates for the different stages (PROD/DEV). But what about backwards compatiblity? We could deprecate the "old" Variant type, and create a new variant, just having one certificate, but still keeping the choice of PROD/DEV, because they still have different APIs to call in, for PROD and DEV. But they just don't worry about the type of the certificate anymore. Implementation wise this means the one cert is applied regardless of the chosen stage. Also, changing the stage in the UI, does NOT require to update the certificate anymore. - AGPUSH-1900 Should we just ignore the "one certificate" thing and just do token based auth? Not sure... perhaps some shops are still 'relying' on the certificate based solution. So, the token-based auth could result into a new iOS variant (JWT token flavor'd). The DEV/PROD stage is a thing here as well ;-) My suggestion is: * deprecate current iOS type in the UI, and QUICKLY remove it * add "one certificate style auth" variant for iOS * add "Token auth" variant for iOS What do folks generally feel about this topic? Greetings, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161202/81023fd9/attachment.html From matzew at apache.org Fri Dec 2 06:32:07 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 2 Dec 2016 12:32:07 +0100 Subject: [aerogear-dev] UPS: Make push setup simpler ? Message-ID: Hello community members! we are wondering, what can we make to have the setup of Push more simplified ? Sure, we can't do too much on the 3rd party factors (APNS/FCM), but perhaps there is something that we could try to implmement. Happy to hear your story / pain points :) Thanks! -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161202/3b36ed80/attachment.html From vivek.pandey at pinelabs.com Fri Dec 2 06:56:31 2016 From: vivek.pandey at pinelabs.com (Vivek Pandey) Date: Fri, 2 Dec 2016 17:26:31 +0530 Subject: [aerogear-dev] UPS: Make push setup simpler ? In-Reply-To: References: Message-ID: <011001d24c93$1fc4a450$5f4decf0$@pinelabs.com> It would certainly make setting up Aerogear applications/variants simpler if there was a way to import/export applications and its variants. An import/export should not change the ids and secrets. From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: Friday, December 2, 2016 5:02 PM To: AeroGear Developer Mailing List; aerogear-users at lists.jboss.org Subject: [aerogear-dev] UPS: Make push setup simpler ? Hello community members! we are wondering, what can we make to have the setup of Push more simplified ? Sure, we can't do too much on the 3rd party factors (APNS/FCM), but perhaps there is something that we could try to implmement. Happy to hear your story / pain points :) Thanks! -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161202/65554d09/attachment-0001.html From mm at napp.dk Fri Dec 2 10:11:23 2016 From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=) Date: Fri, 2 Dec 2016 15:11:23 +0000 Subject: [aerogear-dev] UPS: Make push setup simpler ? In-Reply-To: References: Message-ID: <9F322D8C-2B32-4BE9-9263-C07FBB0B2EC4@napp.dk> Hi there, I think its mostly about upgrading the complexity comes in. I don?t see a clear documentation on how to update the source code, and migrate the database to the newest changes. So much more documentation would be great. Im a very big fan of how the PHP framework Laravel writes documentation and upgrade guides: https://laravel.com/docs/5.3/upgrade BEST REGARDS __________________ MADS M?LLER TECHNICAL PARTNER Napp A/S T: +45 42 42 80 60 M: +45 20 28 20 26 E: mm at napp.dk W: https://napp.dk __________________ From: on behalf of Matthias Wessendorf Reply-To: AeroGear Developer Mailing List Date: Friday 2 December 2016 at 12:32 To: AeroGear Developer Mailing List , "aerogear-users at lists.jboss.org" Subject: [aerogear-dev] UPS: Make push setup simpler ? Hello community members! we are wondering, what can we make to have the setup of Push more simplified ? Sure, we can't do too much on the 3rd party factors (APNS/FCM), but perhaps there is something that we could try to implmement. Happy to hear your story / pain points :) Thanks! -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161202/65830136/attachment.html From mziccard at redhat.com Mon Dec 5 10:13:04 2016 From: mziccard at redhat.com (Massimiliano Ziccardi) Date: Mon, 5 Dec 2016 15:13:04 +0000 Subject: [aerogear-dev] Replacing notnoop with pushy Message-ID: Hi guys, I'm currently working on replacing the notnoop library used in https://github.com/aerogear/aerogear-unifiedpush-server/blob/a58e0948741cf03f82131c7f2d8ecd70d1f5198f/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java with the pushy library. However looks like the pushy library does not supports the 'url-args' field( https://github.com/relayrides/pushy/issues/373). Any idea ? Thank you, Massimiliano -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161205/dd728648/attachment.html From matzew at apache.org Mon Dec 5 10:29:01 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 5 Dec 2016 16:29:01 +0100 Subject: [aerogear-dev] Replacing notnoop with pushy In-Reply-To: References: Message-ID: Hello Massimo, thanks for looking into this. This "only" is relevant for Safari, and therefore is not a real blocker, IMO. We can do the following: * file a AGPUSH JIRA for adding this to pushy later * directly send a PR for this against push But I have no major concerns in ignoring this for a bit. @luke: ok w/ you too ? -Matthias On Mon, Dec 5, 2016 at 4:13 PM, Massimiliano Ziccardi wrote: > Hi guys, > I'm currently working on replacing the notnoop library used in > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/ > a58e0948741cf03f82131c7f2d8ecd70d1f5198f/push/sender/src/ > main/java/org/jboss/aerogear/unifiedpush/message/sender/ > APNsPushNotificationSender.java > > > with the pushy library. > > However looks like the pushy library does not supports the 'url-args' > field(https://github.com/relayrides/pushy/issues/373). > > Any idea ? > > Thank you, > Massimiliano > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161205/9036cf98/attachment.html From matzew at apache.org Mon Dec 5 15:29:46 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 5 Dec 2016 21:29:46 +0100 Subject: [aerogear-dev] load testing FCM connections Message-ID: Hi, in order to load test our FCM connector, it's needed to replace the actual FCM backend w/ some bogus code/mock written in any language. I've started on this to be able to change the FCM URLs: https://github.com/matzew/aerogear-unifiedpush-server/commit/08d782ae52c04a5e693da0f87b77e2d11de24cf0 Now, besides just System properties, I think it would be handy to have this on our docker image as a ENV as well, so it's easy to spin up testing containers and use other container for the dummy load. any thoughts ? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161205/1d76f3fe/attachment-0001.html From Romain.Javornik at saint-gobain.com Fri Dec 9 10:04:08 2016 From: Romain.Javornik at saint-gobain.com (Javornik, Romain) Date: Fri, 9 Dec 2016 15:04:08 +0000 Subject: [aerogear-dev] Problem in Activity log Message-ID: <144EA958C5BCB144849B6DF3DD05867CA73E24@EXMB1EU12.za.if.atcsg.net> Hello, when going in Activity log the status was blocked on pending, I investigate and the problem was coming from the table variant_metric_info. Here is the line where issue come from (everything was back to normal when deleted) : '29213adf-26a5-4d97-906c-f7b2caf16216', '1', NULL, '974', '6f790194-c7b7-446e-99b2-f2eb060c177e', 'b92724e3-eb52-4ef5-a788-edab9c68b980', '1', '1', '0' Did anyone has this error before ? I don't see anything in my JBoss logs (6.4). Best Regards, Romain Javornik -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161209/4079284b/attachment.html From matzew at apache.org Fri Dec 9 10:52:54 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 9 Dec 2016 16:52:54 +0100 Subject: [aerogear-dev] Problem in Activity log In-Reply-To: <144EA958C5BCB144849B6DF3DD05867CA73E24@EXMB1EU12.za.if.atcsg.net> References: <144EA958C5BCB144849B6DF3DD05867CA73E24@EXMB1EU12.za.if.atcsg.net> Message-ID: Hi Romain, thanks for contacting us! a few questions: - blocked on pending? what exactly did you notice ? I recently fixed a bug w/ one job is "pending", the UI is polling server every second (ouch) - deleting? What exactly did you delete? One entry on the variant_metric_info table ? If yes, sounds like for some reason, there was a bogus/wrong entry Mind sharing some more data? I dont mind following up offline, if needed Happy weekend, folks! Matthias On Fri, Dec 9, 2016 at 4:04 PM, Javornik, Romain < Romain.Javornik at saint-gobain.com> wrote: > Hello, > > > > when going in Activity log the status was blocked on pending, I > investigate and the problem was coming from the table variant_metric_info. > > Here is the line where issue come from (everything was back to normal when > deleted) : > > '29213adf-26a5-4d97-906c-f7b2caf16216', '1', NULL, '974', > '6f790194-c7b7-446e-99b2-f2eb060c177e', 'b92724e3-eb52-4ef5-a788-edab9c68b980', > '1', '1', '0' > > > > Did anyone has this error before ? > > I don?t see anything in my JBoss logs (6.4). > > > > Best Regards, > > Romain Javornik > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161209/37437653/attachment.html From Romain.Javornik at saint-gobain.com Fri Dec 9 11:16:38 2016 From: Romain.Javornik at saint-gobain.com (Javornik, Romain) Date: Fri, 9 Dec 2016 16:16:38 +0000 Subject: [aerogear-dev] Problem in Activity log In-Reply-To: References: <144EA958C5BCB144849B6DF3DD05867CA73E24@EXMB1EU12.za.if.atcsg.net> Message-ID: <144EA958C5BCB144849B6DF3DD05867CA73E8E@EXMB1EU12.za.if.atcsg.net> Hello, Yes my scenario was the same, the UI was polling the server constantly, I deleted the row previously sent in variant_metric_info table to fixed the issue. Actually the row was : '29213adf-26a5-4d97-906c-f7b2caf16216', '1', NULL, '974', '6f790194-c7b7-446e-99b2-f2eb060c177e', 'b92724e3-eb52-4ef5-a788-edab9c68b980', '2', '3', '0' Then I changed it to : '29213adf-26a5-4d97-906c-f7b2caf16216', '1', NULL, '974', '6f790194-c7b7-446e-99b2-f2eb060c177e', 'b92724e3-eb52-4ef5-a788-edab9c68b980', '1', '1', '0' Which solved the issue, I delete it because it seems irrelevant. What data do you need ? Best Regards, Romain Javornik De : aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] De la part de Matthias Wessendorf Envoy? : vendredi 9 d?cembre 2016 16:53 ? : AeroGear Developer Mailing List Cc : Marek, Sebastien; Bourillon, Matthias Objet : Re: [aerogear-dev] Problem in Activity log Hi Romain, thanks for contacting us! a few questions: - blocked on pending? what exactly did you notice ? I recently fixed a bug w/ one job is "pending", the UI is polling server every second (ouch) - deleting? What exactly did you delete? One entry on the variant_metric_info table ? If yes, sounds like for some reason, there was a bogus/wrong entry Mind sharing some more data? I dont mind following up offline, if needed Happy weekend, folks! Matthias On Fri, Dec 9, 2016 at 4:04 PM, Javornik, Romain > wrote: Hello, when going in Activity log the status was blocked on pending, I investigate and the problem was coming from the table variant_metric_info. Here is the line where issue come from (everything was back to normal when deleted) : '29213adf-26a5-4d97-906c-f7b2caf16216', '1', NULL, '974', '6f790194-c7b7-446e-99b2-f2eb060c177e', 'b92724e3-eb52-4ef5-a788-edab9c68b980', '1', '1', '0' Did anyone has this error before ? I don?t see anything in my JBoss logs (6.4). Best Regards, Romain Javornik _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161209/c15a91b2/attachment-0001.html From matzew at apache.org Fri Dec 9 11:28:50 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 9 Dec 2016 17:28:50 +0100 Subject: [aerogear-dev] Problem in Activity log In-Reply-To: <144EA958C5BCB144849B6DF3DD05867CA73E8E@EXMB1EU12.za.if.atcsg.net> References: <144EA958C5BCB144849B6DF3DD05867CA73E24@EXMB1EU12.za.if.atcsg.net> <144EA958C5BCB144849B6DF3DD05867CA73E8E@EXMB1EU12.za.if.atcsg.net> Message-ID: On Fri, Dec 9, 2016 at 5:16 PM, Javornik, Romain < Romain.Javornik at saint-gobain.com> wrote: > Hello, > > > > Yes my scenario was the same, the UI was polling the server constantly, I > deleted the row previously sent in variant_metric_info table to fixed the > issue. > https://github.com/aerogear/aerogear-unifiedpush-server/commit/44fcefc6bd223fe897476c190b853e39d2a6e01b Now the UI is only polling, until the LAST job is pending; Did the polling cause any uptime issues for you? Sorry for the issue > > > Actually the row was : '29213adf-26a5-4d97-906c-f7b2caf16216', '1', NULL, > '974', '6f790194-c7b7-446e-99b2-f2eb060c177e', 'b92724e3-eb52-4ef5-a788-edab9c68b980', > '2', '3', '0' > > Then I changed it to : '29213adf-26a5-4d97-906c-f7b2caf16216', '1', NULL, > '974', '6f790194-c7b7-446e-99b2-f2eb060c177e', 'b92724e3-eb52-4ef5-a788-edab9c68b980', > '1', '1', '0' > > Which solved the issue, I delete it because it seems irrelevant. > > > makes sense > What data do you need ? > where you able to reproduce it ? I wonder why there is incorrect data... perhaps spmething is not right on the message bus, for the metric tasks > > > Best Regards, > > Romain Javornik > > > > > > *De :* aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces@ > lists.jboss.org] *De la part de* Matthias Wessendorf > *Envoy? :* vendredi 9 d?cembre 2016 16:53 > *? :* AeroGear Developer Mailing List > *Cc :* Marek, Sebastien; Bourillon, Matthias > *Objet :* Re: [aerogear-dev] Problem in Activity log > > > > Hi Romain, > > > > thanks for contacting us! > > > > a few questions: > > - blocked on pending? what exactly did you notice ? I recently fixed a bug > w/ one job is "pending", the UI is polling server every second (ouch) > > - deleting? What exactly did you delete? One entry on the > variant_metric_info table ? If yes, sounds like for some reason, there was > a bogus/wrong entry > > > > Mind sharing some more data? I dont mind following up offline, if needed > > > > Happy weekend, folks! > > Matthias > > > > On Fri, Dec 9, 2016 at 4:04 PM, Javornik, Romain < > Romain.Javornik at saint-gobain.com> wrote: > > Hello, > > > > when going in Activity log the status was blocked on pending, I > investigate and the problem was coming from the table variant_metric_info. > > Here is the line where issue come from (everything was back to normal when > deleted) : > > '29213adf-26a5-4d97-906c-f7b2caf16216', '1', NULL, '974', > '6f790194-c7b7-446e-99b2-f2eb060c177e', 'b92724e3-eb52-4ef5-a788-edab9c68b980', > '1', '1', '0' > > > > Did anyone has this error before ? > > I don?t see anything in my JBoss logs (6.4). > > > > Best Regards, > > Romain Javornik > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161209/05b72572/attachment.html From jgallaso at redhat.com Tue Dec 13 09:56:44 2016 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Tue, 13 Dec 2016 15:56:44 +0100 Subject: [aerogear-dev] New automated test-suite for UPS Message-ID: Hi, Me and @ziccardi just started working on a new automated test-suite for the UPS. On that regards we should have a repo where push all this stuff. So far we have introduced a mocked server (WireMock) so that we can make whatever request and send whatever push message without FCM banning us. Cheers, -- *Jose Miguel Gallas Olmedo* Associate QE at Mobile Team, *Red Hat* +34 618 488 633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/eb832368/attachment.html From matzew at apache.org Tue Dec 13 10:13:58 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 13 Dec 2016 16:13:58 +0100 Subject: [aerogear-dev] New automated test-suite for UPS In-Reply-To: References: Message-ID: Hello Josemi! On Tue, Dec 13, 2016 at 3:56 PM, Jose Miguel Gallas Olmedo < jgallaso at redhat.com> wrote: > Hi, > > Me and @ziccardi just started working on a new automated test-suite for > the UPS. On that regards we should have a repo where push all this stuff. > happy to see this started. I'd vote to not (yet?) use the existing repo: https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests But, perhaps a new one, like "ups-test-suite" ? or some other name ? > > So far we have introduced a mocked server (WireMock) so that we can make > whatever request and send whatever push message without FCM banning us. > that remoinds me I need to PR that change, actually fisrt, to UPS :) > > Cheers, > > -- > *Jose Miguel Gallas Olmedo* > Associate QE at Mobile Team, *Red Hat* > > +34 618 488 633 <+34%20618%2048%2086%2033> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/96527a14/attachment-0001.html From wtrocki at redhat.com Tue Dec 13 12:19:46 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Tue, 13 Dec 2016 17:19:46 +0000 Subject: [aerogear-dev] Review process for aerogear PR's Message-ID: Hi Aerogear Developers :) Do you guys think that we can use github squash or merge option as default action for aerogear digger repos (or even every aerogear repository)? Aerogear contribution guide doesn't state how tickets are reviewed etc. but I see that most of the opensource projects use squashing option after merging to master - this would still allow us to push as many commits as we want. Squashing would be performed before merge to master on github. This would make our git logs clean and would simplify releases etc. I do not want to start some holly war here, but I would just like to keep things clean and avoid some commits to repo without actual meaning or simply incomplete. When checking changes on the master multiple commits can make things difficult. It would be hard to provide some release notes basing on that etc. Regards -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/84f203f0/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/84f203f0/attachment.png From wtrocki at redhat.com Tue Dec 13 12:33:17 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Tue, 13 Dec 2016 17:33:17 +0000 Subject: [aerogear-dev] [digger-jenkins] Bulding digger clients on Travis Message-ID: What do you guys think about building our clients on Travis? I already created some provisional ticket to gather some requirements and opinions directly in jira. Feel free to comment directly on the ticket https://issues.jboss.org/browse/AGDIGGER-90 Regards -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/d55573a9/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/d55573a9/attachment-0001.png From wtrocki at redhat.com Tue Dec 13 12:44:03 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Tue, 13 Dec 2016 17:44:03 +0000 Subject: [aerogear-dev] Review process for aerogear PR's In-Reply-To: References: Message-ID: TL;DR - Suggested options: ?EXPLANATION: Allow squash merging - Default option used for most of the cases Allow rebase merging - Use when you want to integrate changes with multiple commits On Tue, Dec 13, 2016 at 5:19 PM, Wojciech Trocki wrote: > Hi Aerogear Developers :) > > Do you guys think that we can use github squash or merge option as default > action for aerogear digger repos (or even every aerogear repository)? > > Aerogear contribution guide doesn't state how tickets are reviewed etc. > but I see that most of the opensource projects use squashing option after > merging to master - this would still allow us to push as many commits as we > want. Squashing would be performed before merge to master on github. This > would make our git logs clean and would simplify releases etc. > > I do not want to start some holly war here, but I would just like to keep > things clean and avoid some commits to repo without actual meaning or > simply incomplete. When checking changes on the master multiple commits can > make things difficult. It would be hard to provide some release notes > basing on that etc. > > Regards > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/7697281f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/7697281f/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-12-13 at 5.41.56 PM.png Type: image/png Size: 99209 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/7697281f/attachment-0003.png From scm.blanc at gmail.com Tue Dec 13 12:54:56 2016 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 13 Dec 2016 18:54:56 +0100 Subject: [aerogear-dev] Review process for aerogear PR's In-Reply-To: References: Message-ID: Why don't keep following what is defined here https://aerogear.org/docs/guides/GitHubWorkflow/ ? On Tue, Dec 13, 2016 at 6:44 PM, Wojciech Trocki wrote: > TL;DR - Suggested options: > > > ?EXPLANATION: > > Allow squash merging - Default option used for most of the cases > > Allow rebase merging - Use when you want to integrate changes with > multiple commits > > > On Tue, Dec 13, 2016 at 5:19 PM, Wojciech Trocki > wrote: > >> Hi Aerogear Developers :) >> >> Do you guys think that we can use github squash or merge option as >> default action for aerogear digger repos (or even every aerogear >> repository)? >> >> Aerogear contribution guide doesn't state how tickets are reviewed etc. >> but I see that most of the opensource projects use squashing option after >> merging to master - this would still allow us to push as many commits as we >> want. Squashing would be performed before merge to master on github. This >> would make our git logs clean and would simplify releases etc. >> >> I do not want to start some holly war here, but I would just like to keep >> things clean and avoid some commits to repo without actual meaning or >> simply incomplete. When checking changes on the master multiple commits can >> make things difficult. It would be hard to provide some release notes >> basing on that etc. >> >> Regards >> >> -- >> Wojciech Trocki >> Software Engineer, Red Hat Mobile >> >> > > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/23a27d29/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/23a27d29/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-12-13 at 5.41.56 PM.png Type: image/png Size: 99209 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/23a27d29/attachment-0003.png From wtrocki at redhat.com Tue Dec 13 13:20:02 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Tue, 13 Dec 2016 18:20:02 +0000 Subject: [aerogear-dev] Review process for aerogear PR's In-Reply-To: References: Message-ID: Thanks Sebi. I wasn't aware of this document. It actually matches my suggestion. Recently github added 2 different options for PR's so suggestion here is to also use this options more to automate merges. Git workflow should not be affected. On Tue, Dec 13, 2016 at 5:54 PM, Sebastien Blanc wrote: > Why don't keep following what is defined here https://aerogear.org/ > docs/guides/GitHubWorkflow/ ? > > On Tue, Dec 13, 2016 at 6:44 PM, Wojciech Trocki > wrote: > >> TL;DR - Suggested options: >> >> >> ?EXPLANATION: >> >> Allow squash merging - Default option used for most of the cases >> >> Allow rebase merging - Use when you want to integrate changes with >> multiple commits >> >> >> On Tue, Dec 13, 2016 at 5:19 PM, Wojciech Trocki >> wrote: >> >>> Hi Aerogear Developers :) >>> >>> Do you guys think that we can use github squash or merge option as >>> default action for aerogear digger repos (or even every aerogear >>> repository)? >>> >>> Aerogear contribution guide doesn't state how tickets are reviewed etc. >>> but I see that most of the opensource projects use squashing option after >>> merging to master - this would still allow us to push as many commits as we >>> want. Squashing would be performed before merge to master on github. This >>> would make our git logs clean and would simplify releases etc. >>> >>> I do not want to start some holly war here, but I would just like to >>> keep things clean and avoid some commits to repo without actual meaning or >>> simply incomplete. When checking changes on the master multiple commits can >>> make things difficult. It would be hard to provide some release notes >>> basing on that etc. >>> >>> Regards >>> >>> -- >>> Wojciech Trocki >>> Software Engineer, Red Hat Mobile >>> >>> >> >> >> -- >> Wojciech Trocki >> Software Engineer, Red Hat Mobile >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/413fea73/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-12-13 at 5.41.56 PM.png Type: image/png Size: 99209 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/413fea73/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/413fea73/attachment-0003.png From matzew at apache.org Tue Dec 13 13:29:10 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 13 Dec 2016 19:29:10 +0100 Subject: [aerogear-dev] Review process for aerogear PR's In-Reply-To: References: Message-ID: for large PRs, we tend to have lot's of commits for review, and tend to manually squash/rebase before final push On Tue, Dec 13, 2016 at 7:20 PM, Wojciech Trocki wrote: > Thanks Sebi. I wasn't aware of this document. > It actually matches my suggestion. > Recently github added 2 different options for PR's so suggestion here is > to also use this options more to automate merges. > Git workflow should not be affected. > > > On Tue, Dec 13, 2016 at 5:54 PM, Sebastien Blanc > wrote: > >> Why don't keep following what is defined here https://aerogear.org/docs >> /guides/GitHubWorkflow/ ? >> >> On Tue, Dec 13, 2016 at 6:44 PM, Wojciech Trocki >> wrote: >> >>> TL;DR - Suggested options: >>> >>> >>> ?EXPLANATION: >>> >>> Allow squash merging - Default option used for most of the cases >>> >>> Allow rebase merging - Use when you want to integrate changes with >>> multiple commits >>> >>> >>> On Tue, Dec 13, 2016 at 5:19 PM, Wojciech Trocki >>> wrote: >>> >>>> Hi Aerogear Developers :) >>>> >>>> Do you guys think that we can use github squash or merge option as >>>> default action for aerogear digger repos (or even every aerogear >>>> repository)? >>>> >>>> Aerogear contribution guide doesn't state how tickets are reviewed >>>> etc. but I see that most of the opensource projects use squashing option >>>> after merging to master - this would still allow us to push as many commits >>>> as we want. Squashing would be performed before merge to master on github. >>>> This would make our git logs clean and would simplify releases etc. >>>> >>>> I do not want to start some holly war here, but I would just like to >>>> keep things clean and avoid some commits to repo without actual meaning or >>>> simply incomplete. When checking changes on the master multiple commits can >>>> make things difficult. It would be hard to provide some release notes >>>> basing on that etc. >>>> >>>> Regards >>>> >>>> -- >>>> Wojciech Trocki >>>> Software Engineer, Red Hat Mobile >>>> >>>> >>> >>> >>> -- >>> Wojciech Trocki >>> Software Engineer, Red Hat Mobile >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/4918680c/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-12-13 at 5.41.56 PM.png Type: image/png Size: 99209 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/4918680c/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161213/4918680c/attachment-0003.png From corinnekrych at gmail.com Wed Dec 14 02:36:57 2016 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 14 Dec 2016 08:36:57 +0100 Subject: [aerogear-dev] Review process for aerogear PR's In-Reply-To: References: Message-ID: +1 Wojciech Rather than saying don't use merge button, let's make it match the recommendation in contributor guide. On 13 December 2016 at 19:29, Matthias Wessendorf wrote: > for large PRs, we tend to have lot's of commits for review, and tend to > manually squash/rebase before final push > > On Tue, Dec 13, 2016 at 7:20 PM, Wojciech Trocki > wrote: > >> Thanks Sebi. I wasn't aware of this document. >> It actually matches my suggestion. >> Recently github added 2 different options for PR's so suggestion here is >> to also use this options more to automate merges. >> Git workflow should not be affected. >> >> >> On Tue, Dec 13, 2016 at 5:54 PM, Sebastien Blanc >> wrote: >> >>> Why don't keep following what is defined here https://aerogear.org/docs >>> /guides/GitHubWorkflow/ ? >>> >>> On Tue, Dec 13, 2016 at 6:44 PM, Wojciech Trocki >>> wrote: >>> >>>> TL;DR - Suggested options: >>>> >>>> >>>> ?EXPLANATION: >>>> >>>> Allow squash merging - Default option used for most of the cases >>>> >>>> Allow rebase merging - Use when you want to integrate changes with >>>> multiple commits >>>> >>>> >>>> On Tue, Dec 13, 2016 at 5:19 PM, Wojciech Trocki >>>> wrote: >>>> >>>>> Hi Aerogear Developers :) >>>>> >>>>> Do you guys think that we can use github squash or merge option as >>>>> default action for aerogear digger repos (or even every aerogear >>>>> repository)? >>>>> >>>>> Aerogear contribution guide doesn't state how tickets are reviewed >>>>> etc. but I see that most of the opensource projects use squashing option >>>>> after merging to master - this would still allow us to push as many commits >>>>> as we want. Squashing would be performed before merge to master on github. >>>>> This would make our git logs clean and would simplify releases etc. >>>>> >>>>> I do not want to start some holly war here, but I would just like to >>>>> keep things clean and avoid some commits to repo without actual meaning or >>>>> simply incomplete. When checking changes on the master multiple commits can >>>>> make things difficult. It would be hard to provide some release notes >>>>> basing on that etc. >>>>> >>>>> Regards >>>>> >>>>> -- >>>>> Wojciech Trocki >>>>> Software Engineer, Red Hat Mobile >>>>> >>>>> >>>> >>>> >>>> -- >>>> Wojciech Trocki >>>> Software Engineer, Red Hat Mobile >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Wojciech Trocki >> Software Engineer, Red Hat Mobile >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161214/2b83df07/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2016-12-13 at 5.41.56 PM.png Type: image/png Size: 99209 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161214/2b83df07/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161214/2b83df07/attachment-0003.png From matzew at apache.org Wed Dec 14 04:34:43 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 14 Dec 2016 10:34:43 +0100 Subject: [aerogear-dev] New automated test-suite for UPS In-Reply-To: References: Message-ID: Ok, repo created: https://github.com/aerogear/ups-test-suite On Tue, Dec 13, 2016 at 4:13 PM, Matthias Wessendorf wrote: > Hello Josemi! > > On Tue, Dec 13, 2016 at 3:56 PM, Jose Miguel Gallas Olmedo < > jgallaso at redhat.com> wrote: > >> Hi, >> >> Me and @ziccardi just started working on a new automated test-suite for >> the UPS. On that regards we should have a repo where push all this stuff. >> > > happy to see this started. I'd vote to not (yet?) use the existing repo: > https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests > > But, perhaps a new one, like "ups-test-suite" ? or some other name ? > > >> >> So far we have introduced a mocked server (WireMock) so that we can make >> whatever request and send whatever push message without FCM banning us. >> > > that remoinds me I need to PR that change, actually fisrt, to UPS :) > > > > >> >> Cheers, >> >> -- >> *Jose Miguel Gallas Olmedo* >> Associate QE at Mobile Team, *Red Hat* >> >> +34 618 488 633 <+34%20618%2048%2086%2033> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161214/149ac2e0/attachment.html From wtrocki at redhat.com Wed Dec 14 08:44:34 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Wed, 14 Dec 2016 13:44:34 +0000 Subject: [aerogear-dev] OpenShift Jenkins Build Farm Message-ID: Hi everyone In the AeroGear community we started working on a Jenkins based server solution, powered by Openshift. The project is still in early stage, but of course everybody is more than welcome to contribute. *You can contribute in may ways:*- Create issues with ideas and improvements - Help to improve documentation - Share info with the world - Design mascot for the project ;) *What's is supported at the moment:*- Android build pipelines - Jenkins running on openshift - Java and node.js clients *Main goal for the next sprint:* - IOS build pipelines - Adding additional Jenkins plugins etc. High Level Demo: *https://drive.google.com/open?id=0B0tpDHMFhIOkZU9hVFlhdmFzTUU * *Project on github :* https://github.com/aerogear/digger-jenkins *Public jira: *https://issues.jboss.org/projects/AGDIGGER/issues/ For more, feel free to chat on our aerogear-dev list. Regards -- Wojciech Trocki -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161214/aef46bbf/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161214/aef46bbf/attachment-0001.png From wtrocki at redhat.com Fri Dec 16 05:56:58 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Fri, 16 Dec 2016 10:56:58 +0000 Subject: [aerogear-dev] [Question] Name for digger jenkins node js client Message-ID: Hi Aerogear team is looking for name for our jenkins node.js client. Names are important to avoid confusion between different generations of the build farm and also to simplify documentation etc. *My recommendation:* - Keep simple name and use it (or parts of it) as repo name, npm package name, executable name, project name or in documentation etc. to avoid confusion - Avoid '-', '_' characters in executable name (this is mostly command line client) *Suggestions:* *digkins-node* for repository name *digkins* as executable name Use digkins everywhere needed to denote that this would mean "node.js command line client" *What we have at the moment* *Repo*: https://github.com/aerogear/digger-node It's not denoting in the name that we talking here about new version of the digger so better to change it or add some number etc. *Executable*: digkins (digger + jenkins) PS: Please check if name is available on npm Sprint :P -- Wojciech Trocki -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161216/ae51b327/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161216/ae51b327/attachment.png From lrossett at redhat.com Fri Dec 16 07:12:10 2016 From: lrossett at redhat.com (Leonardo Rossetti) Date: Fri, 16 Dec 2016 10:12:10 -0200 Subject: [aerogear-dev] [Question] Name for digger jenkins node js client In-Reply-To: References: Message-ID: I prefer to use digkins in npm/cli name to avoid user confusion since we already have a digger-cli using the "digger". Also +1 for using digkins-node as repository/project name. On Fri, Dec 16, 2016 at 8:56 AM, Wojciech Trocki wrote: > Hi > > Aerogear team is looking for name for our jenkins node.js client. > Names are important to avoid confusion between different generations of > the build farm > and also to simplify documentation etc. > > *My recommendation:* > - Keep simple name and use it (or parts of it) as repo name, npm package > name, executable name, project name or in documentation etc. to avoid > confusion > - Avoid '-', '_' characters in executable name (this is mostly command > line client) > > *Suggestions:* > *digkins-node* for repository name > *digkins* as executable name > > Use digkins everywhere needed to denote that this would mean "node.js > command line client" > > *What we have at the moment* > > *Repo*: https://github.com/aerogear/digger-node > > It's not denoting in the name that we talking here about new version of > the digger so better to change it or add some number etc. > > *Executable*: digkins (digger + jenkins) > > PS: Please check if name is available on npm > > Sprint :P > -- > Wojciech Trocki > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Leonardo Rossetti lrossett at redhat.com +55 11 99703 0621 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161216/8eb7825f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161216/8eb7825f/attachment-0001.png From matzew at apache.org Fri Dec 16 07:16:15 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Dec 2016 13:16:15 +0100 Subject: [aerogear-dev] [Question] Name for digger jenkins node js client In-Reply-To: References: Message-ID: +1 what Leo said (digkins and repo: digkins-node) -M On Fri, Dec 16, 2016 at 1:12 PM, Leonardo Rossetti wrote: > I prefer to use digkins in npm/cli name to avoid user confusion since we > already have a digger-cli using the "digger". > > Also +1 for using digkins-node as repository/project name. > > On Fri, Dec 16, 2016 at 8:56 AM, Wojciech Trocki > wrote: > >> Hi >> >> Aerogear team is looking for name for our jenkins node.js client. >> Names are important to avoid confusion between different generations of >> the build farm >> and also to simplify documentation etc. >> >> *My recommendation:* >> - Keep simple name and use it (or parts of it) as repo name, npm package >> name, executable name, project name or in documentation etc. to avoid >> confusion >> - Avoid '-', '_' characters in executable name (this is mostly command >> line client) >> >> *Suggestions:* >> *digkins-node* for repository name >> *digkins* as executable name >> >> Use digkins everywhere needed to denote that this would mean "node.js >> command line client" >> >> *What we have at the moment* >> >> *Repo*: https://github.com/aerogear/digger-node >> >> It's not denoting in the name that we talking here about new version of >> the digger so better to change it or add some number etc. >> >> *Executable*: digkins (digger + jenkins) >> >> PS: Please check if name is available on npm >> >> Sprint :P >> -- >> Wojciech Trocki >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Leonardo Rossetti > lrossett at redhat.com > +55 11 99703 0621 <+55%2011%2099703-0621> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161216/874114d0/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161216/874114d0/attachment.png From jgallaso at redhat.com Fri Dec 16 08:05:12 2016 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Fri, 16 Dec 2016 14:05:12 +0100 Subject: [aerogear-dev] [Question] Name for digger jenkins node js client Message-ID: So, finally replying, *digkins* is a hell of a name! And for the repo I would better say digger-jenkins-node but digkins-node is nice as well. Cheeerrrssss -- *Jose Miguel Gallas Olmedo* Associate QE at Mobile Team, *Red Hat* +34 618 488 633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161216/b5495684/attachment.html From matzew at apache.org Fri Dec 16 08:13:57 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Dec 2016 14:13:57 +0100 Subject: [aerogear-dev] [Question] Name for digger jenkins node js client In-Reply-To: References: Message-ID: +1 On Fri, Dec 16, 2016 at 2:05 PM, Jose Miguel Gallas Olmedo < jgallaso at redhat.com> wrote: > So, finally replying, *digkins* is a hell of a name! > > And for the repo I would better say digger-jenkins-node but digkins-node > is nice as well. > > Cheeerrrssss > > -- > *Jose Miguel Gallas Olmedo* > Associate QE at Mobile Team, *Red Hat* > > +34 618 488 633 <+34%20618%2048%2086%2033> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161216/c2d3a1ed/attachment-0001.html From lholmqui at redhat.com Fri Dec 16 09:13:35 2016 From: lholmqui at redhat.com (Luke Holmquist) Date: Fri, 16 Dec 2016 09:13:35 -0500 Subject: [aerogear-dev] [Question] Name for digger jenkins node js client In-Reply-To: References: Message-ID: +1 to digkin On Fri, Dec 16, 2016 at 8:13 AM, Matthias Wessendorf wrote: > +1 > > On Fri, Dec 16, 2016 at 2:05 PM, Jose Miguel Gallas Olmedo < > jgallaso at redhat.com> wrote: > >> So, finally replying, *digkins* is a hell of a name! >> >> And for the repo I would better say digger-jenkins-node but digkins-node >> is nice as well. >> >> Cheeerrrssss >> >> -- >> *Jose Miguel Gallas Olmedo* >> Associate QE at Mobile Team, *Red Hat* >> >> +34 618 488 633 <+34%20618%2048%2086%2033> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161216/21872707/attachment.html From wtrocki at redhat.com Tue Dec 20 05:28:38 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Tue, 20 Dec 2016 10:28:38 +0000 Subject: [aerogear-dev] Fastline as first class citizen in buildfarm jenkins Message-ID: Hi I was thinking (and investigating) about using fastline ( https://fastlane.tools) in buildfarm2 on jenkins. Fastline is extremely popular tool and it would save us lots of troubles when building mobile apps. *Why we want this:* - It would be easier to build sample IOS pipelines using fastline. Most of the problems we would need to deal with are already resolved in that tool. Fastline offers different ways of obtaining provisioning certificates etc. See: https://github.com/fastlane/fastlane/tree/master/gym#readme https://github.com/fastlane/fastlane/tree/master/sigh#readme - Making it available would allow developers to use it. Tooling is extremely popular and most of the mobile dev's using it on daily basis. *How we want to do this:* - Add fastline tool into the android and IOS slave (5 minutes job) - Use fastline in pipelines (maybe we can have separate repo with more advanced pipeline experiments?) We can do that later! I created issue to cover all comments and manage discussion https://issues.jboss.org/browse/AGDIGGER-93 -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161220/9a17101c/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161220/9a17101c/attachment.png From jgallaso at redhat.com Tue Dec 20 06:25:41 2016 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Tue, 20 Dec 2016 12:25:41 +0100 Subject: [aerogear-dev] Fastline as first class citizen in buildfarm jenkins In-Reply-To: References: Message-ID: Awesome! On 20 December 2016 at 11:28, Wojciech Trocki wrote: > Hi > > I was thinking (and investigating) about using fastline ( > https://fastlane.tools) in buildfarm2 on jenkins. > Fastline is extremely popular tool and it would save us lots of troubles > when building mobile apps. > > *Why we want this:* > - It would be easier to build sample IOS pipelines using fastline. > Most of the problems we would need to deal with are already resolved in > that tool. > Fastline offers different ways of obtaining provisioning certificates etc. > > See: https://github.com/fastlane/fastlane/tree/master/gym#readme > https://github.com/fastlane/fastlane/tree/master/sigh#readme > > - Making it available would allow developers to use it. > Tooling is extremely popular and most of the mobile dev's using it on > daily basis. > > *How we want to do this:* > - Add fastline tool into the android and IOS slave (5 minutes job) > - Use fastline in pipelines (maybe we can have separate repo with more > advanced pipeline experiments?) We can do that later! > > I created issue to cover all comments and manage discussion > > https://issues.jboss.org/browse/AGDIGGER-93 > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- *Jose Miguel Gallas Olmedo* Associate QE at Mobile Team, *Red Hat* +34 618 488 633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161220/fa023c4d/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161220/fa023c4d/attachment-0001.png From lgriffin at redhat.com Tue Dec 20 09:32:39 2016 From: lgriffin at redhat.com (Leigh Griffin) Date: Tue, 20 Dec 2016 14:32:39 +0000 Subject: [aerogear-dev] [feedhenry-dev] Fastline as first class citizen in buildfarm jenkins In-Reply-To: References: Message-ID: This looks very useful Wojciech and looks to be low cost to add in. Certainly worth trying it out and anything that helps with tooling, particularly for our mobile devs, would be a welcome addition to the platform and one which we could lean upon. Great job on the initial research and for bringing this to the teams attention. Leigh On Tue, Dec 20, 2016 at 10:28 AM, Wojciech Trocki wrote: > Hi > > I was thinking (and investigating) about using fastline ( > https://fastlane.tools) in buildfarm2 on jenkins. > Fastline is extremely popular tool and it would save us lots of troubles > when building mobile apps. > > *Why we want this:* > - It would be easier to build sample IOS pipelines using fastline. > Most of the problems we would need to deal with are already resolved in > that tool. > Fastline offers different ways of obtaining provisioning certificates etc. > > See: https://github.com/fastlane/fastlane/tree/master/gym#readme > https://github.com/fastlane/fastlane/tree/master/sigh#readme > > - Making it available would allow developers to use it. > Tooling is extremely popular and most of the mobile dev's using it on > daily basis. > > *How we want to do this:* > - Add fastline tool into the android and IOS slave (5 minutes job) > - Use fastline in pipelines (maybe we can have separate repo with more > advanced pipeline experiments?) We can do that later! > > I created issue to cover all comments and manage discussion > > https://issues.jboss.org/browse/AGDIGGER-93 > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- Leigh Griffin Engineering Manager, Red Hat Mobile, Communications House Cork Road Waterford X91NY33 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161220/20c3080d/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161220/20c3080d/attachment.png