SuperCollider incremental builds

[Scott Carver]

The SuperCollider build system on travis.ci
<https://travis-ci.org/supercollider/supercollider> is now archiving Mac
builds for every commit, tag, and branch.

The latest successful build for a branch is available here:

*
http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/{branch}-latest.html
<http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/%7Bbranch%7D-latest.html>*(where
{branch} is the name of the branch)


Builds for a specific tag are available here:

*
http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/{tag}.html
<http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/%7Btag%7D.html>*(where
{tag} is the name of the branch)


Individual commit builds are available here:

*
http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/SC-{commit}.zip
<http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/SC-%7Bcommit%7D.zip>*(where
{commit} is the sha hash of the commit)

Finally, tagged commits are posted as Releases on GitHub
<https://github.com/supercollider/supercollider/releases>. For developers,
this is a good way to capture before and after build snapshots over the
course of a major change.

For sc-users folks, this is a way to get a bleeding-edge build of SC 3.7
without building yourself. It's now been almost year since the last release
and there's been a lot of change.
You'll want this:
*
http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/master-latest.html
<http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/master-latest.html>*

I am open to suggestions on what else would be useful to archive on a
per-commit basis (logs? warning summary?) - especially on linux, since
we're currently building and then tossing the results.

Enjoy,
Scott Carver


((

Some tldr notes:

- Builds are constructed from a zipped version of the install folder after
'make install'
- Builds take even longer now. There are some optimizations and caching
that can be done, which I'll investigate eventually. Our commit volume is
low, so the slowness still isn't a big problem.

- Sorry for the corny redirecting-html / raw url business. It involved the
fewest moving parts, and stability/simplicity is the most important thing
at this point. If someone wants to build something nicer, I'd be glad to
help hook it up.

- Pull requests (sadly) don't post builds - since a PR can be initiated by
anyone, there are security concerns. If your PR requires a build for
non-developer testing, publish it as a branch and a build will spin
automatically.

))

[Daniel Mayer]

The SuperCollider build system on travis.ci is now archiving Mac builds for every commit, tag, and branch

Wow, haven't checked yet, but that sounds very useful.
Just built two days ago, but it rarely works immediately.
So I suppose it saves a lot of time for many people, thanks for that.

Greetings

Daniel

-----------------------------
www.daniel-mayer.at
-----------------------------


_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/

[felix]

Awesome !

Let's put up the links to those on supercollider.github.io

At least to:

*
http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/master-latest.html
<http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/master-latest.html>*


- Pull requests (sadly) don't post builds -

I wouldn't expect or want it to anyway.

Post by Scott Carver
The SuperCollider build system on travis.ci
<https://travis-ci.org/supercollider/supercollider> is now archiving Mac
builds for every commit, tag, and branch.
*
http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/{branch}-latest.html
<http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/%7Bbranch%7D-latest.html>*(where
{branch} is the name of the branch)
*
http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/{tag}.html
<http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/%7Btag%7D.html>*(where
{tag} is the name of the branch)
*
http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/SC-{commit}.zip
<http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/SC-%7Bcommit%7D.zip>*(where
{commit} is the sha hash of the commit)
Finally, tagged commits are posted as Releases on GitHub
<https://github.com/supercollider/supercollider/releases>. For
developers, this is a good way to capture before and after build snapshots
over the course of a major change.
For sc-users folks, this is a way to get a bleeding-edge build of SC 3.7
without building yourself. It's now been almost year since the last release
and there's been a lot of change.
*
http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/master-latest.html
<http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/master-latest.html>*
I am open to suggestions on what else would be useful to archive on a
per-commit basis (logs? warning summary?) - especially on linux, since
we're currently building and then tossing the results.
Enjoy,
Scott Carver
((
- Builds are constructed from a zipped version of the install folder after
'make install'
- Builds take even longer now. There are some optimizations and caching
that can be done, which I'll investigate eventually. Our commit volume is
low, so the slowness still isn't a big problem.
- Sorry for the corny redirecting-html / raw url business. It involved the
fewest moving parts, and stability/simplicity is the most important thing
at this point. If someone wants to build something nicer, I'd be glad to
help hook it up.
- Pull requests (sadly) don't post builds - since a PR can be initiated by
anyone, there are security concerns. If your PR requires a build for
non-developer testing, publish it as a branch and a build will spin
automatically.
))