Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upNightlies #409
Nightlies #409
Conversation
Windows should wait on factories.py refactor to fix::
windows = ServoFactory([
# TODO: convert this to use DynamicServoFactory
# We need to run each command in a bash login shell, which breaks the
# heuristics used by DynamicServoFactory.make_step
steps.Compile(command=make_win_command("./mach build -d -v"),
env=envs.build_windows),
steps.Test(command=make_win_command("./mach test-unit"),
env=envs.build_windows),
# TODO: run lockfile_changed.sh and manifest_changed.sh scripts
])
Already added the credentials to /srv/pillar on the master.
|
Just woke up and haven't looked at this yet, but you must be psychic @edunham - I was about to open an issue/PR for this last night! This should also finish off/fix servo/servo#10339. |
| builderNames=[ | ||
| "android-nightly", | ||
| "linux-nightly", | ||
| "mac-nightly" |
This comment has been minimized.
This comment has been minimized.
aneeshusa
Jun 29, 2016
Member
nit: leave a comma at the end of this line to reduce future diff noise
|
I would prefer to use environment variables + This can be done by modifying the By the way - any reason we are using |
| mac-nightly: | ||
| - ./mach build --release | ||
| - ./mach package --release | ||
| - s3cmd -c ~/.s3cfg-servo put target/release/*.tar.gz s3://servo-developer-preview/nightly/`date +%Y`/ |
This comment has been minimized.
This comment has been minimized.
aneeshusa
Jun 29, 2016
Member
Two things:
- Prefer "$(command)" form to backticks - style guide.
- I believe that since make_step splits the command up into a list before passing it to Buildbot, Buildbot will exec the command directly, instead of through a shell, and the command substitution won't work. IMO it would be better to make a script for this in the servo repo in the
etc/cidirectory and call it from here.
This comment has been minimized.
This comment has been minimized.
cbrewster
Jun 29, 2016
Member
Also the mac package script now generates a .dmg instead of a .tar.gz and it is put in the target directory (not debug or release directories)
| - ./mach build --release | ||
| - ./mach package --release | ||
| - s3cmd -c ~/.s3cfg-servo put target/release/*.tar.gz s3://servo-developer-preview/nightly/`date +%Y`/ | ||
| - rm -rf target/ |
This comment has been minimized.
This comment has been minimized.
aneeshusa
Jun 29, 2016
Member
Why did you add the rm -rf lines? Buildbot will clean out the working directory at the start of each build IIRC (or I think maybe the git step does this), so it should not be necessary to have as a standalone step.
|
It may also be nice to set up a |
|
Is there a reason to continue to upload android builds to a Rust controlled bucket? Why don't we just dump everything in the servo bucket? |
|
servo-master1 builds get:
|
|
I think they need to be added here: |
|
I would rather not rush this PR too much, since we have some time before release and we can always make a build manually for release. @edunham if you want I can make a PR to your branch to implement passing credentials as environment variables. |
|
I'm not super excited about manual builds from user machines and would rather hold off on releasing binaries until we do it from machines that were at least originally installed from a clean state with only the dependencies we've documented & listed in salt. Maybe manual builds from those machines would make me feel less stressed, but publishing bits to the world from laptops the team has taken through security checkpoints in all sorts of interesting countries seems dubious :-) |
| gpg_passphrase = | ||
| guess_mime_type = True | ||
| host_base = s3.amazonaws.com | ||
| host_bucket = %(bucket)s.s3.amazonaws.com |
This comment has been minimized.
This comment has been minimized.
| gpg_passphrase = | ||
| guess_mime_type = True | ||
| host_base = s3.amazonaws.com | ||
| host_bucket = %(bucket)s.s3.amazonaws.com |
This comment has been minimized.
This comment has been minimized.
| use_https = True | ||
| use_mime_magic = True | ||
| verbosity = WARNING | ||
| website_endpoint = http://%(bucket)s.s3-website-%(location)s.amazonaws.com/ |
This comment has been minimized.
This comment has been minimized.
| use_https = True | ||
| use_mime_magic = True | ||
| verbosity = WARNING | ||
| website_endpoint = http://%(bucket)s.s3-website-%(location)s.amazonaws.com/ |
This comment has been minimized.
This comment has been minimized.
|
This will need servo/servo#11943 at the least, and then to use that script. |
…rsbergstrom Add linux and osx nightly builds Alternative to #409 that is more secure IMO. Requires servo/servo#11943. cc @larsbergstrom @edunham <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/410) <!-- Reviewable:end -->
…rsbergstrom Add linux and osx nightly builds Alternative to #409 that is more secure IMO. Requires servo/servo#11943. cc @larsbergstrom @edunham <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/410) <!-- Reviewable:end -->
|
|
edunham commentedJun 29, 2016
•
edited by larsbergstrom
2 separate config files because the Android upload to the servo-rust bucket in the Rust account, and the everything-else upload to the servo-developer-preview bucket in the Servo account, require different credentials. @aneeshusa, could you remind me of the right way to salt the near-identical files which end up with different pillar data and different names?
Windows nightly requires:
This change is