Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Avoid multiple builds #5

Open
bguiz opened this issue Apr 15, 2015 · 1 comment
Open

Avoid multiple builds #5

bguiz opened this issue Apr 15, 2015 · 1 comment

Comments

@bguiz
Copy link

bguiz commented Apr 15, 2015

I have solved the problem that you describe here:

"One drawback of this is that if you have a build matrix that builds your project with multiple versions of your platform, you'll end up with the same number of pages builds. Which seems redundant."

Essentially, compare the build number to the job number, and allow only the first (or whichever index) to pass through. Example:

https://github.com/bguiz/plugin-registry/blob/59b0601d30ab8e75caaf9958aac4618277321cbd/.travis.yml#L17

Thanks for writing your blog post, BTW!
orbeckst added a commit to MDAnalysis/mdanalysis that referenced this issue Sep 12, 2015
@orbeckst
doc deployment fixes
cdb5f36 
- use subshells when using cd (should avoid not finding the deploy script)
  and should make the travis process more robust
- only run doc deployment if we are the first job in the build matrix (from
  @bguiz , see steveklabnik/automatically_update_github_pages_with_travis_example#5)
- configure almost everything through env vars in .travis.yml
@orbeckst orbeckst mentioned this issue Sep 12, 2015
Closed
5 tasks
orbeckst added a commit to MDAnalysis/mdanalysis that referenced this issue Sep 12, 2015
@orbeckst
doc deployment: build in place and only run if first job
3010863 
- As suggested by @kain88-de in #386, we let travis also build the libraries in place
  (with "python setup.py build_ext --inplace") so that sphinx can properly import
  the local build of MDAnalysis.
- use subshells when using cd (should avoid not finding the deploy script)
  and should make the travis process more robust
- only run doc deployment if we are the first job in the build matrix (from
  @bguiz , see steveklabnik/automatically_update_github_pages_with_travis_example#5)
- configure almost everything through env vars in .travis.yml
orbeckst added a commit to MDAnalysis/mdanalysis that referenced this issue Sep 13, 2015
@orbeckst
doc deployment: only run if first job
007c859 
- use subshells when using cd (otherwise deploy script is not found)
  and should make the travis process more robust
- only run doc deployment if we are the first job in the build matrix (from
  @bguiz , see steveklabnik/automatically_update_github_pages_with_travis_example#5)
- configure almost everything through env vars in .travis.yml
@jreyes33
Copy link

jreyes33 commented Oct 11, 2016 •
edited
Loading

Another way to accomplish this is using deploy with an on conditional as described in the third example here:
https://docs.travis-ci.com/user/deployment/#Examples-of-Conditional-Releases-using-on%3A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jreyes33 @bguiz