Open GoogleCodeExporter opened 9 years ago
Original comment by steven.b...@gmail.com
on 24 Jul 2012 at 5:59
Original comment by lee.becker
on 17 Feb 2013 at 5:12
Here's a free option for continuous integration:
https://drone.io/
There would be a few more options if we were on GitHub:
https://buildhive.cloudbees.com/
http://about.travis-ci.org/
Original comment by steven.b...@gmail.com
on 19 Feb 2013 at 3:10
I'm working on getting this set up:
https://drone.io/bethard/cleartk
I still haven't been able to get the failure messages sent to
cleartk-developers yet:
https://drone.uservoice.com/forums/176976-feedback-for-drone-io/suggestions/3792
986-allow-notifications-to-be-sent-to-google-group
Original comment by steven.b...@gmail.com
on 28 Mar 2013 at 6:04
Original comment by steven.b...@gmail.com
on 29 Mar 2013 at 12:36
Original comment by steven.b...@gmail.com
on 3 May 2013 at 9:15
We should add https://drone.io/bethard/cleartk as a link to the wiki somewhere.
Original comment by phi...@ogren.info
on 24 Oct 2013 at 7:16
Philip will look into setting up a cleartk.org email which will forward error
notifications to cleartk-dev list.
Original comment by phi...@ogren.info
on 24 Oct 2013 at 7:19
I have set up build@cleartk.org to forward to
cleartk-developers@googlegroups.com. Please configure drone.io to forward
build failure notifications.
Original comment by phi...@ogren.info
on 25 Oct 2013 at 3:54
I added the link https://drone.io/bethard/cleartk to the front page.
Original comment by phi...@ogren.info
on 25 Oct 2013 at 3:56
Ok, I've set drone.io to mail to build@cleartk.org. I also temporarily set it
to sent a message on successful builds and launched a build, so hopefully if
everything is working, we'll get a message. Then I'll turn off the message on
successful builds (and only have a message for failed builds) and close this
ticket.
Original comment by steven.b...@gmail.com
on 25 Oct 2013 at 4:04
Well, the build succeeded, but I didn't see any email sent to the list. Is it
possible to see if it was received by cleartk.org?
Original comment by steven.b...@gmail.com
on 25 Oct 2013 at 5:25
I have the email build@cleartk.org set up as a "Forward" type email address
with it forwarding directly to the dev list. This seems to prevent me from
being able to open the webmail client for that email address provided by the
hosting service in order to see if an email from drone.io was received. I just
sent test5 to build@cleartk.org so it doesn't seem to be a problem with the
email address. I wonder does it work correctly if you put your own email
address in?
Original comment by phi...@ogren.info
on 26 Oct 2013 at 8:41
I put your and my email addresses in it and launched a build, and I received
the email okay. (I assume you did too.) Maybe Google is somehow still
recognizing that the email is coming from a cloud service and rejecting the
post from Google Groups? Is there anything more complicated than "Forward" that
might trick Google into allowing the post?
Original comment by steven.b...@gmail.com
on 27 Oct 2013 at 4:08
If I go to the cleartk-developers Google Group and try to add a member,
builds@drone.io (where the notification email comes from) I get a message "Some
addresses are groups, but groups may not be added to other groups" and it
doesn't allow me to add builds@drone.io.
If you sign up on drone.io, I can add you as an Admin, and you can try
modifying things more directly. If you want to do this, just send me your
drone.io account name.
Original comment by steven.b...@gmail.com
on 27 Oct 2013 at 4:24
I guess it is no surprise that Google Groups makes this a bit difficult. You
can imagine that an email that is a member of a group that it automatically
forwards emails to will create an infinite loop without intervention. Doesn't
seem insurmountable though!
I tried a bunch of things to get this to work this morning and didn't have any
success. I'll pick this up again later and perhaps try your suggestion.
Original comment by phi...@ogren.info
on 27 Oct 2013 at 7:22
Original comment by phi...@ogren.info
on 15 Mar 2014 at 5:43
Original issue reported on code.google.com by
pvogren@gmail.com
on 7 Jan 2011 at 9:36