You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
depot_tools/.gitignore

99 lines
1.9 KiB
Plaintext

# Ignore any python bytecode.
*.pyc
# ignore cipd client files
/.cipd_bin/
/.cipd_bin_cros_python2
/.cipd_client*
/.cipd_client_cache/
/.versions/
# Ignore "disable auto update" sentinel file.
.disable_auto_update
# Ignore the batch files produced by the Windows bootstrapping.
/git-bash
/git.bat
/gitk.bat
/.pylint.d/
/python
/python.bat
/python3.bat
/ssh.bat
/ssh-keygen.bat
/svn
/svn.bat
/svnversion.bat
Revert "[win_tools] Use bundled Python CIPD packages." This reverts commit bf1446791e4b1c5b102559de9fb090ed5ba50cf5. Reason for revert: broke win bots http://o/410053 Original change's description: > [win_tools] Use bundled Python CIPD packages. > > Enable bundled Python CIPD packages in bleeding-edge mode. This > replaces the ZIP unpacking approach used before, and introduces > validation and management through the CIPD tool. The bleeding edge > version will only install if a sentinel file is present in the > "depot_tools" root; otherwise, default behavior will continue. > > This method adds a upgrade and downgrade path to/from ZIP and > CIPD installations. This is done by rewriting the "win_tools.bat" > process: > > 1) Ensure that a bootstrap Python is present. > 2) Use it to run "win_tools.py", which has the functionality of > "git_bootstrap.py" plus Python installation. > 3) Run "win_tools.py" with appropriate flags. > > Some tricks were employed to handle cases where there is an > already-running Python instance that uses the current Python > installation and executable. This happens on bots because the > system uses the same "depot_tools" checkout at multiple launch > layers. To this end, we use the "python.bat" as the "current Python" > authority and refrain from cleaning up old Python directories if their > "python.exe" binaries are currently in use. > > We change the Git bleeding edge file to share the same > sentinel file as Python, ".bleeding_edge". > > The new Python should have the same facilities as the original Python > bundle. > > BUG=chromium:740171 > TEST=local > > Change-Id: I1b3b7d31d47d1a37a9dba9114d31681bec558736 > Reviewed-on: https://chromium-review.googlesource.com/563036 > Commit-Queue: Daniel Jacques <dnj@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> TBR=iannucci@chromium.org,dnj@chromium.org Change-Id: I84574a01bbad6596912e4aaa34f019d24720b638 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:740171 Reviewed-on: https://chromium-review.googlesource.com/567009 Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
8 years ago
/.bleeding_edge
/.codereview_upload_cookies
/.gitconfig
/.git_bleeding_edge
/.git_cl_description_backup
/.last_codereview_email_address
/.ssh
/.subversion
# Ignore locations where third-party tools are placed during bootstrapping.
/bootstrap*_bin
/python*_bin
/python_bin_reldir.txt
/python3_bin_reldir.txt
[win_tools] Use bundled Python CIPD packages (#2). Re-land of bf1446791e4b1c5b102559de9fb090ed5ba50cf5. Enable bundled Python CIPD packages in bleeding-edge mode. This replaces the ZIP unpacking approach used before, and introduces validation and management through the CIPD tool. The bleeding edge version will only install if a sentinel file is present in the "depot_tools" root; otherwise, default behavior will continue. This method adds a upgrade and downgrade path to/from ZIP and CIPD installations. This is done by rewriting the "win_tools.bat" process: 1) Ensure that a bootstrap Python is present. 2) Use it to run "win_tools.py", which has the functionality of "git_bootstrap.py" plus Python installation. 3) Run "win_tools.py" with appropriate flags. Some tricks were employed to handle cases where there is an already-running Python instance that uses the current Python installation and executable. This happens on bots because the system uses the same "depot_tools" checkout at multiple launch layers. To this end, we use the "python.bat" as the "current Python" authority and refrain from cleaning up old Python directories if their "python.exe" binaries are currently in use. We change the Git bleeding edge file to share the same sentinel file as Python, ".bleeding_edge". The new Python should have the same facilities as the original Python bundle. BUG=chromium:740171 TEST=local Change-Id: I51ba6415c60b95c2aaba94b6e21bd9b3fc82f35d Reviewed-on: https://chromium-review.googlesource.com/568524 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
8 years ago
/win_tools*_bin
/git_bin
/git-*_bin
/svn_bin
/external_bin/
/win_toolchain/vs2013_files
/win_toolchain/vs_files
/win_toolchain/*.timestamps
/win_toolchain/.vspro
/win_toolchain/data.json
/win_toolchain/vs_files.ciopfs
# Ignore ctags/cscope index files
/TAGS
/cscope.files
/cscope.in.out
/cscope.out
/cscope.po.out
/tags
# Ignore unittest related files.
/testing_support/_infra
/testing_support/_rietveld
/tests/git-svn-submodule/
/tests/subversion_config/README.txt
/tests/subversion_config/auth
/tests/subversion_config/servers
/tests/svn/
/tests/svnrepo/
# Ignore intermediate isolate files
*.isolated
*.isolated.state
# Ignore recipe working directory.
/.recipe_deps
/infra/.recipe_deps
/recipes/.recipe_deps
# Ignore google AE downloaded for running testing only.
testing_support/google_appengine
# Ignore emacs / vim backup files.
*~
*.swp
# Ignore win/mac monitoring config. It is unique for each depot_tools checkout.
/metrics.cfg
/build_telemetry.cfg
# Ignore git traces produced by git push on git-cl upload.
/traces
# Ignore VsChromium configuration file.
/vs-chromium-project.txt
Report when vpython (Python 2) is run during presubmits While all Chromium PRESUBMIT.py scripts have been running on Python 2 for a long time they continue to invoke child scripts under Python 2. Part of the reason for slow progress on this transition is that it is not easy to tell that this is happening, and most developers probably assume that Python 3 presubmits implies a lack of Python 2. This change adds a warning when it detects Python 2 scripts being run. Typical output (edited for clarity) looks like this: git cl presubmit --files "chrome/updater/tools/*;ppapi/generators/*" ... Python 2 scripts were run during Python 3 presubmits. Please ask ??? if help is needed in preventing this. "depot_tools\pylint-1.5" --args-on-stdin from chrome\updater\tools \ "depot_tools\pylint-1.5" --args-on-stdin from chrome\updater\tools \ idl_tests.py from ppapi\generators If Python 2 scripts launch child scripts, especially if they use sys.executable, then they will not be reported. However this is a good thing because it means that the report focuses on the top-level scripts that drive Python 2 usage. This change works by modifying vpython.bat to write invocation information to a text file. The data in this text file is picked up by presubmit_support.py when it finishes running a set of presubmits. Bug: 1313804 Change-Id: Ic632b38eae07eca2e02e94358305cc9c998818e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/3699002 Reviewed-by: Gavin Mak <gavinmak@google.com> Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
3 years ago
# Ignore the file that logs Python 2 scripts run during presubmits.
/python2_usage.txt