[jitsi-dev] Bring more visibility to changes that break the jitsi-meet build


#1

There have been a few times recently where someone has made a change in jitsi-meet which causes npm install to fail or the browserify build to fail. Would anyone be opposed to setting up a TravisCI build on pushes to the repo? That way there's more visibility to changes in the client code that break the build.

One of my coworkers has done most of the work: https://github.com/jitsi/jitsi-meet/compare/master...pstros:ci-work

Devin

This email message is for the sole use of the intended recipient(s) and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, copying, disclosure or dissemination is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.


#2

Hi,

we already have Jenkins running for the project which also creates the
debian packages and runs the tests (torture) using a deployment with
the newest packages. Results of CI on every project goes to the
cruisecontrol mailinglist.
We just added a make command to the current jitsi-meet job in order to
fail when a problem comes.

Regards
damencho

···

On Thu, Aug 13, 2015 at 9:59 AM, Devin Wilson <devin.wilson@readytalk.com> wrote:

There have been a few times recently where someone has made a change in
jitsi-meet which causes npm install to fail or the browserify build to fail.
Would anyone be opposed to setting up a TravisCI build on pushes to the
repo? That way there’s more visibility to changes in the client code that
break the build.

One of my coworkers has done most of the work:
https://github.com/jitsi/jitsi-meet/compare/master...pstros:ci-work

Devin

This email message is for the sole use of the intended recipient(s) and may
contain information that is privileged, confidential, and exempt from
disclosure under applicable law. Any unauthorized review, use, copying,
disclosure or dissemination is prohibited. If you are not the intended
recipient, please contact the sender by reply email and destroy all copies
of the original message.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#3

Sorry about that last one, by the way.

Boris

···

On 13/08/15 09:59, Devin Wilson wrote:

There have been a few times recently where someone has made a change in
jitsi-meet which causes npm install to fail or the browserify build to
fail.


#4

That makes sense. Thanks for adding the make command. And Boris, it happens to the best of us.

Devin

···

-----Original Message-----
From: dev [mailto:dev-bounces@jitsi.org] On Behalf Of Boris Grozev
Sent: Friday, August 14, 2015 10:55 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Bring more visibility to changes that break the jitsi-meet build

On 13/08/15 09:59, Devin Wilson wrote:

There have been a few times recently where someone has made a change
in jitsi-meet which causes npm install to fail or the browserify build
to fail.

Sorry about that last one, by the way.

Boris

From: dev [mailto:dev-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: Friday, August 14, 2015 10:32 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Bring more visibility to changes that break the jitsi-meet build

Hi,

we already have Jenkins running for the project which also creates the debian packages and runs the tests (torture) using a deployment with the newest packages. Results of CI on every project goes to the cruisecontrol mailinglist.
We just added a make command to the current jitsi-meet job in order to fail when a problem comes.

Regards
damencho

On Thu, Aug 13, 2015 at 9:59 AM, Devin Wilson <devin.wilson@readytalk.com> wrote:

There have been a few times recently where someone has made a change
in jitsi-meet which causes npm install to fail or the browserify build to fail.
Would anyone be opposed to setting up a TravisCI build on pushes to
the repo? That way there’s more visibility to changes in the client
code that break the build.

One of my coworkers has done most of the work:
https://github.com/jitsi/jitsi-meet/compare/master...pstros:ci-work

Devin

This email message is for the sole use of the intended recipient(s)
and may contain information that is privileged, confidential, and
exempt from disclosure under applicable law. Any unauthorized review,
use, copying, disclosure or dissemination is prohibited. If you are
not the intended recipient, please contact the sender by reply email
and destroy all copies of the original message.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev
This email message is for the sole use of the intended recipient(s) and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, copying, disclosure or dissemination is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.