generic-library/webrtc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
46d83fa26c
webrtc/tools/.gitignore

46 lines
860 B
Plaintext
Raw Normal View History

Try server and buildbot scripts now using Chromium scripts. - compatible with depot_tools try commands. - old build master is converted to use Chromium scripts, according to http://www.chromium.org/developers/testing/chromium-build-infrastructure/getting-the-buildbot-source/forking-your-buildbot - slaves can now be run out of a plain checkout, no local configuration needed. Also added files to make it possible to use tools as a separate checkout. BUG=None TEST=Runs on local machine with remote slaves. I've successfully submitted try jobs with both git try and gcl try commands. Review URL: https://webrtc-codereview.appspot.com/449011 git-svn-id: http://webrtc.googlecode.com/svn/trunk@1945 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-03-27 17:57:30 +02:00
*.failed
*.pyc
*~
.*.sw?
.DS_Store
.code_review_password
.cproject
.metadata
.project
.pydevproject
.settings
.status_password
/continuous_build/depot_tools
Disabling HTTP status push on Build master since we're not using it Also updated .gitignore BUG=None TEST=Tested on local master and production master. Review URL: https://webrtc-codereview.appspot.com/539005 git-svn-id: http://webrtc.googlecode.com/svn/trunk@2147 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-04-30 11:56:57 +02:00
/third_party/bloat
Try server and buildbot scripts now using Chromium scripts. - compatible with depot_tools try commands. - old build master is converted to use Chromium scripts, according to http://www.chromium.org/developers/testing/chromium-build-infrastructure/getting-the-buildbot-source/forking-your-buildbot - slaves can now be run out of a plain checkout, no local configuration needed. Also added files to make it possible to use tools as a separate checkout. BUG=None TEST=Runs on local machine with remote slaves. I've successfully submitted try jobs with both git try and gcl try commands. Review URL: https://webrtc-codereview.appspot.com/449011 git-svn-id: http://webrtc.googlecode.com/svn/trunk@1945 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-03-27 17:57:30 +02:00
/third_party/gaeunit
Rewired the oath2 symlink and updated tgrid_parser to the new Build Bot version's tgrid syntax. Added back the gviz_api to the tools deps - will remove it from the main project DEPS in a different patch. Rewired those symlinks too. Made the build status loader algorithm more scalable. It read in the whole database on each load which is probably unsustainable in the long run. Also, it will now forget bots that have offline for more than ~5 revisions. Fixed a bug in the coverage tracker. BUG= TEST= Review URL: https://webrtc-codereview.appspot.com/486002 git-svn-id: http://webrtc.googlecode.com/svn/trunk@2039 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-04-17 10:49:10 +02:00
/third_party/google-visualization-python
Disabling HTTP status push on Build master since we're not using it Also updated .gitignore BUG=None TEST=Tested on local master and production master. Review URL: https://webrtc-codereview.appspot.com/539005 git-svn-id: http://webrtc.googlecode.com/svn/trunk@2147 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-04-30 11:56:57 +02:00
/third_party/oauth2
/third_party/webtreemap
Try server and buildbot scripts now using Chromium scripts. - compatible with depot_tools try commands. - old build master is converted to use Chromium scripts, according to http://www.chromium.org/developers/testing/chromium-build-infrastructure/getting-the-buildbot-source/forking-your-buildbot - slaves can now be run out of a plain checkout, no local configuration needed. Also added files to make it possible to use tools as a separate checkout. BUG=None TEST=Runs on local machine with remote slaves. I've successfully submitted try jobs with both git try and gcl try commands. Review URL: https://webrtc-codereview.appspot.com/449011 git-svn-id: http://webrtc.googlecode.com/svn/trunk@1945 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-03-27 17:57:30 +02:00
# Buildbot creates these files:
Libvpx buildbot waterfall. I think I found a decent way to avoid duplicating the whole configuration for the libvpx waterfall. It's not perfect but it works. I still haven't figured out what the best way to manage the slaves would be however, since they will need to know which master to connect to, or they'll pick the default they're configured for in slaves.cfg, which is the WebRTC waterfall (can be overridden with the TESTING_MASTER property, but that's only to be used for development and testing. BUG=None TEST=Tested on local master and slaves. Review URL: https://webrtc-codereview.appspot.com/595005 git-svn-id: http://webrtc.googlecode.com/svn/trunk@2310 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-05-29 08:23:42 +02:00
*.new
Try server and buildbot scripts now using Chromium scripts. - compatible with depot_tools try commands. - old build master is converted to use Chromium scripts, according to http://www.chromium.org/developers/testing/chromium-build-infrastructure/getting-the-buildbot-source/forking-your-buildbot - slaves can now be run out of a plain checkout, no local configuration needed. Also added files to make it possible to use tools as a separate checkout. BUG=None TEST=Runs on local machine with remote slaves. I've successfully submitted try jobs with both git try and gcl try commands. Review URL: https://webrtc-codereview.appspot.com/449011 git-svn-id: http://webrtc.googlecode.com/svn/trunk@1945 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-03-27 17:57:30 +02:00
.manhole
Libvpx buildbot waterfall. I think I found a decent way to avoid duplicating the whole configuration for the libvpx waterfall. It's not perfect but it works. I still haven't figured out what the best way to manage the slaves would be however, since they will need to know which master to connect to, or they'll pick the default they're configured for in slaves.cfg, which is the WebRTC waterfall (can be overridden with the TESTING_MASTER property, but that's only to be used for development and testing. BUG=None TEST=Tested on local master and slaves. Review URL: https://webrtc-codereview.appspot.com/595005 git-svn-id: http://webrtc.googlecode.com/svn/trunk@2310 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-05-29 08:23:42 +02:00
bg_gradient.jpg
Try server and buildbot scripts now using Chromium scripts. - compatible with depot_tools try commands. - old build master is converted to use Chromium scripts, according to http://www.chromium.org/developers/testing/chromium-build-infrastructure/getting-the-buildbot-source/forking-your-buildbot - slaves can now be run out of a plain checkout, no local configuration needed. Also added files to make it possible to use tools as a separate checkout. BUG=None TEST=Runs on local machine with remote slaves. I've successfully submitted try jobs with both git try and gcl try commands. Review URL: https://webrtc-codereview.appspot.com/449011 git-svn-id: http://webrtc.googlecode.com/svn/trunk@1945 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-03-27 17:57:30 +02:00
changes.pck
changes.pck.old
dropin.cache
events_*
http.log
master.cfg.sample
Libvpx buildbot waterfall. I think I found a decent way to avoid duplicating the whole configuration for the libvpx waterfall. It's not perfect but it works. I still haven't figured out what the best way to manage the slaves would be however, since they will need to know which master to connect to, or they'll pick the default they're configured for in slaves.cfg, which is the WebRTC waterfall (can be overridden with the TESTING_MASTER property, but that's only to be used for development and testing. BUG=None TEST=Tested on local master and slaves. Review URL: https://webrtc-codereview.appspot.com/595005 git-svn-id: http://webrtc.googlecode.com/svn/trunk@2310 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-05-29 08:23:42 +02:00
robots.txt
Try server and buildbot scripts now using Chromium scripts. - compatible with depot_tools try commands. - old build master is converted to use Chromium scripts, according to http://www.chromium.org/developers/testing/chromium-build-infrastructure/getting-the-buildbot-source/forking-your-buildbot - slaves can now be run out of a plain checkout, no local configuration needed. Also added files to make it possible to use tools as a separate checkout. BUG=None TEST=Runs on local machine with remote slaves. I've successfully submitted try jobs with both git try and gcl try commands. Review URL: https://webrtc-codereview.appspot.com/449011 git-svn-id: http://webrtc.googlecode.com/svn/trunk@1945 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-03-27 17:57:30 +02:00
state.sqlite
state.sqlite-shm
state.sqlite-wal
twistd.log*
twistd.pid
# Chrome buildbot scripts
/continuous_build/build
# Buildbot slave log directories:
Libvpx buildbot waterfall. I think I found a decent way to avoid duplicating the whole configuration for the libvpx waterfall. It's not perfect but it works. I still haven't figured out what the best way to manage the slaves would be however, since they will need to know which master to connect to, or they'll pick the default they're configured for in slaves.cfg, which is the WebRTC waterfall (can be overridden with the TESTING_MASTER property, but that's only to be used for development and testing. BUG=None TEST=Tested on local master and slaves. Review URL: https://webrtc-codereview.appspot.com/595005 git-svn-id: http://webrtc.googlecode.com/svn/trunk@2310 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-05-29 08:23:42 +02:00
/continuous_build/build_internal/masters/master.libvpx/*/
/continuous_build/build_internal/masters/master.webrtc/*/
/continuous_build/build_internal/masters/master.tryserver.webrtc/*/
# Public HTML folder is also a subdirectory, make sure it's not ignored:
!public_html
Reference in New Issue Copy Permalink