Hi,
the default build is broken since the 17th of october. Anynone feels responsible to fix it after the merge?
Build results can be seen here[1]. It probably has to with enabling sysmobts support but not direct PDCH queue access.
holger
[1] http://jenkins.osmocom.org/jenkins/job/osmo-pcu/label=linux_i386_debian_sque...
Hi Holger,
Is there a way to receive fails of this build job to e-mail?
On Sat, Jan 19, 2013 at 10:04 PM, Holger Hans Peter Freyther holger@freyther.de wrote:
Hi,
the default build is broken since the 17th of october. Anynone feels responsible to fix it after the merge?
Build results can be seen here[1]. It probably has to with enabling sysmobts support but not direct PDCH queue access.
holger
[1] http://jenkins.osmocom.org/jenkins/job/osmo-pcu/label=linux_i386_debian_sque...
Hi Alexander,
On Sun, Jan 20, 2013 at 10:26:13PM +0400, Alexander Chemeris wrote:
Is there a way to receive fails of this build job to e-mail?
I'm not sure of that, but you can subscribe a RSS feed: http://jenkins.osmocom.org/jenkins/job/osmo-pcu/rssFailed
On Sun, Jan 20, 2013 at 11:47 PM, Harald Welte laforge@gnumonks.org wrote:
Hi Alexander,
On Sun, Jan 20, 2013 at 10:26:13PM +0400, Alexander Chemeris wrote:
Is there a way to receive fails of this build job to e-mail?
I'm not sure of that, but you can subscribe a RSS feed: http://jenkins.osmocom.org/jenkins/job/osmo-pcu/rssFailed
Thanks! Though I prefer e-mails for notifications, as I check RSS not very often. I know Jenkins could send e-mails - we had such a setup at my previous company. So it's a question to Holger whether we configured this or not.
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
On Sun, Jan 20, 2013 at 10:26:13PM +0400, Alexander Chemeris wrote:
Hi,
Is there a way to receive fails of this build job to e-mail?
yes, I would need to setup a MTA on this domain. Do you want emails to this list? Another list? I am using the RSS feature of Jenkins to see the build failures.
holger
On Sun, Jan 20, 2013 at 11:55 PM, Holger Hans Peter Freyther hfreyther@sysmocom.de wrote:
On Sun, Jan 20, 2013 at 10:26:13PM +0400, Alexander Chemeris wrote:
Is there a way to receive fails of this build job to e-mail?
yes, I would need to setup a MTA on this domain. Do you want emails to this list? Another list? I am using the RSS feature of Jenkins to see the build failures.
A special list for this would be perfect. Smth like osmocom-pcu-build@ or osmocom-pcu-jenkins@
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
Hi Alexander,
On Mon, Jan 21, 2013 at 12:23:02AM +0400, Alexander Chemeris wrote:
yes, I would need to setup a MTA on this domain. Do you want emails to this list? Another list? I am using the RSS feature of Jenkins to see the build failures.
A special list for this would be perfect. Smth like osmocom-pcu-build@ or osmocom-pcu-jenkins@
I think given the low traffic on this list, it would be best to simply send the mails here. Only build failure reports should be sufficient, build success is supposedly a normal event that needs no reporting here.
On Mon, Jan 21, 2013 at 2:04 PM, Harald Welte laforge@gnumonks.org wrote:
Hi Alexander,
On Mon, Jan 21, 2013 at 12:23:02AM +0400, Alexander Chemeris wrote:
yes, I would need to setup a MTA on this domain. Do you want emails to this list? Another list? I am using the RSS feature of Jenkins to see the build failures.
A special list for this would be perfect. Smth like osmocom-pcu-build@ or osmocom-pcu-jenkins@
I think given the low traffic on this list, it would be best to simply send the mails here. Only build failure reports should be sufficient, build success is supposedly a normal event that needs no reporting here.
I'm strongly against mixing human generated traffic and computer generated traffic at the same mailing list.
Given the expected low traffic and low number of users, maintaining a mailing list should not be a problem. If it's hard to host it at lists.osmocom.org, I could host it on our domain, though having it at the same domain as this mailing list looks more logical.
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
Hi Alexander,
On Mon, Jan 21, 2013 at 02:22:23PM +0400, Alexander Chemeris wrote:
On Mon, Jan 21, 2013 at 2:04 PM, Harald Welte laforge@gnumonks.org wrote:
I think given the low traffic on this list, it would be best to simply send the mails here. Only build failure reports should be sufficient, build success is supposedly a normal event that needs no reporting here.
I'm strongly against mixing human generated traffic and computer generated traffic at the same mailing list.
While I disagree, I respect your request (and will configure my incoming mail filter to file both lists into the same folder).
Given the expected low traffic and low number of users, maintaining a mailing list should not be a problem. If it's hard to host it at lists.osmocom.org, I could host it on our domain, though having it at the same domain as this mailing list looks more logical.
It is not a problem to set up another list, takes about 1 minute. It just means that people will have know about two lists and subscribe to two lists. But well, as indicated, I have no strong feelings about it.
Regards, Harald
On Mon, Jan 21, 2013 at 2:30 PM, Harald Welte laforge@gnumonks.org wrote:
Hi Alexander,
On Mon, Jan 21, 2013 at 02:22:23PM +0400, Alexander Chemeris wrote:
On Mon, Jan 21, 2013 at 2:04 PM, Harald Welte laforge@gnumonks.org wrote:
I think given the low traffic on this list, it would be best to simply send the mails here. Only build failure reports should be sufficient, build success is supposedly a normal event that needs no reporting here.
I'm strongly against mixing human generated traffic and computer generated traffic at the same mailing list.
While I disagree, I respect your request (and will configure my incoming mail filter to file both lists into the same folder).
Thank you, I appreciate this.
Given the expected low traffic and low number of users, maintaining a mailing list should not be a problem. If it's hard to host it at lists.osmocom.org, I could host it on our domain, though having it at the same domain as this mailing list looks more logical.
It is not a problem to set up another list, takes about 1 minute. It just means that people will have know about two lists and subscribe to two lists. But well, as indicated, I have no strong feelings about it.
Let me elaborate a bit more - not to start an argument, just to make my point to look less selfish. :)
I believe that only few active developers are interested in receiving Jenkins traffic. Other "users" or less active developers will consider this as a spam. And I don't want our list to be even nearly considered as spammed. Using two lists is an "opt in" way, which is far more friendly.
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
Hi, Holger
Yes, you are right, building without enabling sysmobts is ok.
2013/1/19 Holger Hans Peter Freyther holger@freyther.de
Hi,
the default build is broken since the 17th of october. Anynone feels responsible to fix it after the merge?
Build results can be seen here[1]. It probably has to with enabling sysmobts support but not direct PDCH queue access.
holger
[1] http://jenkins.osmocom.org/jenkins/job/osmo-pcu/label=linux_i386_debian_sque...
osmocom-net-gprs@lists.osmocom.org
-
Alexander Chemeris -
Harald Welte -
Holger Hans Peter Freyther -
Holger Hans Peter Freyther -
Ivan Kluchnikov