From d6e43568d82b1d3adaf7a120b9178ba75cf989e7 Mon Sep 17 00:00:00 2001 From: Tom Clegg Date: Tue, 8 Mar 2016 16:37:42 -0500 Subject: [PATCH] 8491: move files from arvados-dev into their new places --- Makefile | 7 + build/COPYING | 2 - build/README | 30 - build/agpl-3.0.txt | 661 ------------------ .../create-plot-data-from-log.sh | 0 build/git/hooks/coding-standards.sh | 128 ---- build/install/easy-docker-install.sh | 87 --- build/jenkins/run-cwl-tests.sh | 218 ------ build/jenkins/run-deploy.sh | 266 ------- build/jenkins/run-diagnostics-suite.sh | 86 --- build/jenkins/run-performance-suite.sh | 88 --- build/jenkins/run-tapestry-tests.sh | 54 -- build/jenkins/run_upload_packages.py | 273 -------- build/{jenkins => }/libcloud-pin | 0 .../package-build-dockerfiles/.gitignore | 0 .../package-build-dockerfiles/Makefile | 0 .../package-build-dockerfiles/README | 0 .../build-all-build-containers.sh | 0 .../centos6/Dockerfile | 0 .../debian7/Dockerfile | 0 .../debian8/Dockerfile | 0 .../ubuntu1204/Dockerfile | 0 .../ubuntu1404/Dockerfile | 0 .../centos6/Dockerfile | 0 .../centos6/localrepo.repo | 0 .../debian7/Dockerfile | 0 .../debian8/Dockerfile | 0 .../ubuntu1204/Dockerfile | 0 .../ubuntu1404/Dockerfile | 0 .../package-testing/common-test-packages.sh | 0 .../deb-common-test-packages.sh | 0 .../test-package-arvados-api-server.sh | 0 .../test-package-arvados-node-manager.sh | 0 .../test-package-arvados-sso-server.sh | 0 .../test-package-arvados-workbench.sh | 0 ...st-package-python27-python-arvados-fuse.sh | 0 ...e-python27-python-arvados-python-client.sh | 0 .../package-testing/test-packages-centos6.sh | 0 .../package-testing/test-packages-debian7.sh | 0 .../package-testing/test-packages-debian8.sh | 0 .../test-packages-ubuntu1204.sh | 0 .../test-packages-ubuntu1404.sh | 0 .../rails-package-scripts/README.md | 0 .../arvados-api-server.sh | 0 .../arvados-sso-server.sh | 0 .../arvados-workbench.sh | 0 .../rails-package-scripts/postinst.sh | 0 .../rails-package-scripts/postrm.sh | 0 .../rails-package-scripts/prerm.sh | 0 .../rails-package-scripts/step2.sh | 0 .../{jenkins => }/run-build-docker-images.sh | 0 .../run-build-docker-jobs-image.sh | 0 .../run-build-packages-all-targets.sh | 0 .../run-build-packages-one-target.sh | 0 build/{jenkins => }/run-build-packages-sso.sh | 0 build/{jenkins => }/run-build-packages.sh | 0 build/{jenkins => }/run-library.sh | 0 build/{jenkins => }/run-tests.sh | 0 58 files changed, 7 insertions(+), 1893 deletions(-) create mode 100644 Makefile delete mode 100644 build/COPYING delete mode 100644 build/README delete mode 100644 build/agpl-3.0.txt rename build/{jenkins => }/create-plot-data-from-log.sh (100%) delete mode 100755 build/git/hooks/coding-standards.sh delete mode 100755 build/install/easy-docker-install.sh delete mode 100755 build/jenkins/run-cwl-tests.sh delete mode 100755 build/jenkins/run-deploy.sh delete mode 100755 build/jenkins/run-diagnostics-suite.sh delete mode 100755 build/jenkins/run-performance-suite.sh delete mode 100755 build/jenkins/run-tapestry-tests.sh delete mode 100755 build/jenkins/run_upload_packages.py rename build/{jenkins => }/libcloud-pin (100%) rename build/{jenkins => }/package-build-dockerfiles/.gitignore (100%) rename build/{jenkins => }/package-build-dockerfiles/Makefile (100%) rename build/{jenkins => }/package-build-dockerfiles/README (100%) rename build/{jenkins => }/package-build-dockerfiles/build-all-build-containers.sh (100%) rename build/{jenkins => }/package-build-dockerfiles/centos6/Dockerfile (100%) rename build/{jenkins => }/package-build-dockerfiles/debian7/Dockerfile (100%) rename build/{jenkins => }/package-build-dockerfiles/debian8/Dockerfile (100%) rename build/{jenkins => }/package-build-dockerfiles/ubuntu1204/Dockerfile (100%) rename build/{jenkins => }/package-build-dockerfiles/ubuntu1404/Dockerfile (100%) rename build/{jenkins => }/package-test-dockerfiles/centos6/Dockerfile (100%) rename build/{jenkins => }/package-test-dockerfiles/centos6/localrepo.repo (100%) rename build/{jenkins => }/package-test-dockerfiles/debian7/Dockerfile (100%) rename build/{jenkins => }/package-test-dockerfiles/debian8/Dockerfile (100%) rename build/{jenkins => }/package-test-dockerfiles/ubuntu1204/Dockerfile (100%) rename build/{jenkins => }/package-test-dockerfiles/ubuntu1404/Dockerfile (100%) rename build/{jenkins => }/package-testing/common-test-packages.sh (100%) rename build/{jenkins => }/package-testing/deb-common-test-packages.sh (100%) rename build/{jenkins => }/package-testing/test-package-arvados-api-server.sh (100%) rename build/{jenkins => }/package-testing/test-package-arvados-node-manager.sh (100%) rename build/{jenkins => }/package-testing/test-package-arvados-sso-server.sh (100%) rename build/{jenkins => }/package-testing/test-package-arvados-workbench.sh (100%) rename build/{jenkins => }/package-testing/test-package-python27-python-arvados-fuse.sh (100%) rename build/{jenkins => }/package-testing/test-package-python27-python-arvados-python-client.sh (100%) rename build/{jenkins => }/package-testing/test-packages-centos6.sh (100%) rename build/{jenkins => }/package-testing/test-packages-debian7.sh (100%) rename build/{jenkins => }/package-testing/test-packages-debian8.sh (100%) rename build/{jenkins => }/package-testing/test-packages-ubuntu1204.sh (100%) rename build/{jenkins => }/package-testing/test-packages-ubuntu1404.sh (100%) rename build/{jenkins => }/rails-package-scripts/README.md (100%) rename build/{jenkins => }/rails-package-scripts/arvados-api-server.sh (100%) rename build/{jenkins => }/rails-package-scripts/arvados-sso-server.sh (100%) rename build/{jenkins => }/rails-package-scripts/arvados-workbench.sh (100%) rename build/{jenkins => }/rails-package-scripts/postinst.sh (100%) rename build/{jenkins => }/rails-package-scripts/postrm.sh (100%) rename build/{jenkins => }/rails-package-scripts/prerm.sh (100%) rename build/{jenkins => }/rails-package-scripts/step2.sh (100%) rename build/{jenkins => }/run-build-docker-images.sh (100%) rename build/{jenkins => }/run-build-docker-jobs-image.sh (100%) rename build/{jenkins => }/run-build-packages-all-targets.sh (100%) rename build/{jenkins => }/run-build-packages-one-target.sh (100%) rename build/{jenkins => }/run-build-packages-sso.sh (100%) rename build/{jenkins => }/run-build-packages.sh (100%) rename build/{jenkins => }/run-library.sh (100%) rename build/{jenkins => }/run-tests.sh (100%) diff --git a/Makefile b/Makefile new file mode 100644 index 0000000000..921eb02f5f --- /dev/null +++ b/Makefile @@ -0,0 +1,7 @@ +export WORKSPACE?=$(shell pwd) +test: + build/run-tests.sh ${TEST_FLAGS} +packages: + build/run-build-packages-all-targets.sh ${PACKAGES_FLAGS} +test-packages: + build/run-build-packages-all-targets.sh --test-packages ${PACKAGES_FLAGS} diff --git a/build/COPYING b/build/COPYING deleted file mode 100644 index af63e41e01..0000000000 --- a/build/COPYING +++ /dev/null @@ -1,2 +0,0 @@ -This code is licenced under the GNU Affero General Public License version 3 -(see agpl-3.0.txt) diff --git a/build/README b/build/README deleted file mode 100644 index b076f0bfd2..0000000000 --- a/build/README +++ /dev/null @@ -1,30 +0,0 @@ -Welcome to Arvados! - -This is the arvados-dev source tree. It contains scripts that can be useful -if you want to hack on Arvados itself. - -If you are interested in using Arvados or setting up your own Arvados -installation, you most likely do not need this source tree. - -For the Arvados source code, check out the git repository at - https://github.com/curoverse/arvados - -The main Arvados web site is - https://arvados.org - -The Arvados public wiki is located at - https://arvados.org/projects/arvados/wiki - -The Arvados public bug tracker is located at - https://arvados.org/projects/arvados/issues - -For support see - http://doc.arvados.org/user/getting_started/community.html - -Installation documentation is located at - http://doc.arvados.org/install - -If you wish to build the documentation yourself, follow the instructions in -doc/README to build the documentation, then consult the "Install Guide". - -See COPYING for information about Arvados Free Software licenses. diff --git a/build/agpl-3.0.txt b/build/agpl-3.0.txt deleted file mode 100644 index dba13ed2dd..0000000000 --- a/build/agpl-3.0.txt +++ /dev/null @@ -1,661 +0,0 @@ - GNU AFFERO GENERAL PUBLIC LICENSE - Version 3, 19 November 2007 - - Copyright (C) 2007 Free Software Foundation, Inc. - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The GNU Affero General Public License is a free, copyleft license for -software and other kinds of works, specifically designed to ensure -cooperation with the community in the case of network server software. - - The licenses for most software and other practical works are designed -to take away your freedom to share and change the works. By contrast, -our General Public Licenses are intended to guarantee your freedom to -share and change all versions of a program--to make sure it remains free -software for all its users. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -them if you wish), that you receive source code or can get it if you -want it, that you can change the software or use pieces of it in new -free programs, and that you know you can do these things. - - Developers that use our General Public Licenses protect your rights -with two steps: (1) assert copyright on the software, and (2) offer -you this License which gives you legal permission to copy, distribute -and/or modify the software. - - A secondary benefit of defending all users' freedom is that -improvements made in alternate versions of the program, if they -receive widespread use, become available for other developers to -incorporate. Many developers of free software are heartened and -encouraged by the resulting cooperation. However, in the case of -software used on network servers, this result may fail to come about. -The GNU General Public License permits making a modified version and -letting the public access it on a server without ever releasing its -source code to the public. - - The GNU Affero General Public License is designed specifically to -ensure that, in such cases, the modified source code becomes available -to the community. It requires the operator of a network server to -provide the source code of the modified version running there to the -users of that server. Therefore, public use of a modified version, on -a publicly accessible server, gives the public access to the source -code of the modified version. - - An older license, called the Affero General Public License and -published by Affero, was designed to accomplish similar goals. This is -a different license, not a version of the Affero GPL, but Affero has -released a new version of the Affero GPL which permits relicensing under -this license. - - The precise terms and conditions for copying, distribution and -modification follow. - - TERMS AND CONDITIONS - - 0. Definitions. - - "This License" refers to version 3 of the GNU Affero General Public License. - - "Copyright" also means copyright-like laws that apply to other kinds of -works, such as semiconductor masks. - - "The Program" refers to any copyrightable work licensed under this -License. Each licensee is addressed as "you". "Licensees" and -"recipients" may be individuals or organizations. - - To "modify" a work means to copy from or adapt all or part of the work -in a fashion requiring copyright permission, other than the making of an -exact copy. The resulting work is called a "modified version" of the -earlier work or a work "based on" the earlier work. - - A "covered work" means either the unmodified Program or a work based -on the Program. - - To "propagate" a work means to do anything with it that, without -permission, would make you directly or secondarily liable for -infringement under applicable copyright law, except executing it on a -computer or modifying a private copy. Propagation includes copying, -distribution (with or without modification), making available to the -public, and in some countries other activities as well. - - To "convey" a work means any kind of propagation that enables other -parties to make or receive copies. Mere interaction with a user through -a computer network, with no transfer of a copy, is not conveying. - - An interactive user interface displays "Appropriate Legal Notices" -to the extent that it includes a convenient and prominently visible -feature that (1) displays an appropriate copyright notice, and (2) -tells the user that there is no warranty for the work (except to the -extent that warranties are provided), that licensees may convey the -work under this License, and how to view a copy of this License. If -the interface presents a list of user commands or options, such as a -menu, a prominent item in the list meets this criterion. - - 1. Source Code. - - The "source code" for a work means the preferred form of the work -for making modifications to it. "Object code" means any non-source -form of a work. - - A "Standard Interface" means an interface that either is an official -standard defined by a recognized standards body, or, in the case of -interfaces specified for a particular programming language, one that -is widely used among developers working in that language. - - The "System Libraries" of an executable work include anything, other -than the work as a whole, that (a) is included in the normal form of -packaging a Major Component, but which is not part of that Major -Component, and (b) serves only to enable use of the work with that -Major Component, or to implement a Standard Interface for which an -implementation is available to the public in source code form. A -"Major Component", in this context, means a major essential component -(kernel, window system, and so on) of the specific operating system -(if any) on which the executable work runs, or a compiler used to -produce the work, or an object code interpreter used to run it. - - The "Corresponding Source" for a work in object code form means all -the source code needed to generate, install, and (for an executable -work) run the object code and to modify the work, including scripts to -control those activities. However, it does not include the work's -System Libraries, or general-purpose tools or generally available free -programs which are used unmodified in performing those activities but -which are not part of the work. For example, Corresponding Source -includes interface definition files associated with source files for -the work, and the source code for shared libraries and dynamically -linked subprograms that the work is specifically designed to require, -such as by intimate data communication or control flow between those -subprograms and other parts of the work. - - The Corresponding Source need not include anything that users -can regenerate automatically from other parts of the Corresponding -Source. - - The Corresponding Source for a work in source code form is that -same work. - - 2. Basic Permissions. - - All rights granted under this License are granted for the term of -copyright on the Program, and are irrevocable provided the stated -conditions are met. This License explicitly affirms your unlimited -permission to run the unmodified Program. The output from running a -covered work is covered by this License only if the output, given its -content, constitutes a covered work. This License acknowledges your -rights of fair use or other equivalent, as provided by copyright law. - - You may make, run and propagate covered works that you do not -convey, without conditions so long as your license otherwise remains -in force. You may convey covered works to others for the sole purpose -of having them make modifications exclusively for you, or provide you -with facilities for running those works, provided that you comply with -the terms of this License in conveying all material for which you do -not control copyright. Those thus making or running the covered works -for you must do so exclusively on your behalf, under your direction -and control, on terms that prohibit them from making any copies of -your copyrighted material outside their relationship with you. - - Conveying under any other circumstances is permitted solely under -the conditions stated below. Sublicensing is not allowed; section 10 -makes it unnecessary. - - 3. Protecting Users' Legal Rights From Anti-Circumvention Law. - - No covered work shall be deemed part of an effective technological -measure under any applicable law fulfilling obligations under article -11 of the WIPO copyright treaty adopted on 20 December 1996, or -similar laws prohibiting or restricting circumvention of such -measures. - - When you convey a covered work, you waive any legal power to forbid -circumvention of technological measures to the extent such circumvention -is effected by exercising rights under this License with respect to -the covered work, and you disclaim any intention to limit operation or -modification of the work as a means of enforcing, against the work's -users, your or third parties' legal rights to forbid circumvention of -technological measures. - - 4. Conveying Verbatim Copies. - - You may convey verbatim copies of the Program's source code as you -receive it, in any medium, provided that you conspicuously and -appropriately publish on each copy an appropriate copyright notice; -keep intact all notices stating that this License and any -non-permissive terms added in accord with section 7 apply to the code; -keep intact all notices of the absence of any warranty; and give all -recipients a copy of this License along with the Program. - - You may charge any price or no price for each copy that you convey, -and you may offer support or warranty protection for a fee. - - 5. Conveying Modified Source Versions. - - You may convey a work based on the Program, or the modifications to -produce it from the Program, in the form of source code under the -terms of section 4, provided that you also meet all of these conditions: - - a) The work must carry prominent notices stating that you modified - it, and giving a relevant date. - - b) The work must carry prominent notices stating that it is - released under this License and any conditions added under section - 7. This requirement modifies the requirement in section 4 to - "keep intact all notices". - - c) You must license the entire work, as a whole, under this - License to anyone who comes into possession of a copy. This - License will therefore apply, along with any applicable section 7 - additional terms, to the whole of the work, and all its parts, - regardless of how they are packaged. This License gives no - permission to license the work in any other way, but it does not - invalidate such permission if you have separately received it. - - d) If the work has interactive user interfaces, each must display - Appropriate Legal Notices; however, if the Program has interactive - interfaces that do not display Appropriate Legal Notices, your - work need not make them do so. - - A compilation of a covered work with other separate and independent -works, which are not by their nature extensions of the covered work, -and which are not combined with it such as to form a larger program, -in or on a volume of a storage or distribution medium, is called an -"aggregate" if the compilation and its resulting copyright are not -used to limit the access or legal rights of the compilation's users -beyond what the individual works permit. Inclusion of a covered work -in an aggregate does not cause this License to apply to the other -parts of the aggregate. - - 6. Conveying Non-Source Forms. - - You may convey a covered work in object code form under the terms -of sections 4 and 5, provided that you also convey the -machine-readable Corresponding Source under the terms of this License, -in one of these ways: - - a) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by the - Corresponding Source fixed on a durable physical medium - customarily used for software interchange. - - b) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by a - written offer, valid for at least three years and valid for as - long as you offer spare parts or customer support for that product - model, to give anyone who possesses the object code either (1) a - copy of the Corresponding Source for all the software in the - product that is covered by this License, on a durable physical - medium customarily used for software interchange, for a price no - more than your reasonable cost of physically performing this - conveying of source, or (2) access to copy the - Corresponding Source from a network server at no charge. - - c) Convey individual copies of the object code with a copy of the - written offer to provide the Corresponding Source. This - alternative is allowed only occasionally and noncommercially, and - only if you received the object code with such an offer, in accord - with subsection 6b. - - d) Convey the object code by offering access from a designated - place (gratis or for a charge), and offer equivalent access to the - Corresponding Source in the same way through the same place at no - further charge. You need not require recipients to copy the - Corresponding Source along with the object code. If the place to - copy the object code is a network server, the Corresponding Source - may be on a different server (operated by you or a third party) - that supports equivalent copying facilities, provided you maintain - clear directions next to the object code saying where to find the - Corresponding Source. Regardless of what server hosts the - Corresponding Source, you remain obligated to ensure that it is - available for as long as needed to satisfy these requirements. - - e) Convey the object code using peer-to-peer transmission, provided - you inform other peers where the object code and Corresponding - Source of the work are being offered to the general public at no - charge under subsection 6d. - - A separable portion of the object code, whose source code is excluded -from the Corresponding Source as a System Library, need not be -included in conveying the object code work. - - A "User Product" is either (1) a "consumer product", which means any -tangible personal property which is normally used for personal, family, -or household purposes, or (2) anything designed or sold for incorporation -into a dwelling. In determining whether a product is a consumer product, -doubtful cases shall be resolved in favor of coverage. For a particular -product received by a particular user, "normally used" refers to a -typical or common use of that class of product, regardless of the status -of the particular user or of the way in which the particular user -actually uses, or expects or is expected to use, the product. A product -is a consumer product regardless of whether the product has substantial -commercial, industrial or non-consumer uses, unless such uses represent -the only significant mode of use of the product. - - "Installation Information" for a User Product means any methods, -procedures, authorization keys, or other information required to install -and execute modified versions of a covered work in that User Product from -a modified version of its Corresponding Source. The information must -suffice to ensure that the continued functioning of the modified object -code is in no case prevented or interfered with solely because -modification has been made. - - If you convey an object code work under this section in, or with, or -specifically for use in, a User Product, and the conveying occurs as -part of a transaction in which the right of possession and use of the -User Product is transferred to the recipient in perpetuity or for a -fixed term (regardless of how the transaction is characterized), the -Corresponding Source conveyed under this section must be accompanied -by the Installation Information. But this requirement does not apply -if neither you nor any third party retains the ability to install -modified object code on the User Product (for example, the work has -been installed in ROM). - - The requirement to provide Installation Information does not include a -requirement to continue to provide support service, warranty, or updates -for a work that has been modified or installed by the recipient, or for -the User Product in which it has been modified or installed. Access to a -network may be denied when the modification itself materially and -adversely affects the operation of the network or violates the rules and -protocols for communication across the network. - - Corresponding Source conveyed, and Installation Information provided, -in accord with this section must be in a format that is publicly -documented (and with an implementation available to the public in -source code form), and must require no special password or key for -unpacking, reading or copying. - - 7. Additional Terms. - - "Additional permissions" are terms that supplement the terms of this -License by making exceptions from one or more of its conditions. -Additional permissions that are applicable to the entire Program shall -be treated as though they were included in this License, to the extent -that they are valid under applicable law. If additional permissions -apply only to part of the Program, that part may be used separately -under those permissions, but the entire Program remains governed by -this License without regard to the additional permissions. - - When you convey a copy of a covered work, you may at your option -remove any additional permissions from that copy, or from any part of -it. (Additional permissions may be written to require their own -removal in certain cases when you modify the work.) You may place -additional permissions on material, added by you to a covered work, -for which you have or can give appropriate copyright permission. - - Notwithstanding any other provision of this License, for material you -add to a covered work, you may (if authorized by the copyright holders of -that material) supplement the terms of this License with terms: - - a) Disclaiming warranty or limiting liability differently from the - terms of sections 15 and 16 of this License; or - - b) Requiring preservation of specified reasonable legal notices or - author attributions in that material or in the Appropriate Legal - Notices displayed by works containing it; or - - c) Prohibiting misrepresentation of the origin of that material, or - requiring that modified versions of such material be marked in - reasonable ways as different from the original version; or - - d) Limiting the use for publicity purposes of names of licensors or - authors of the material; or - - e) Declining to grant rights under trademark law for use of some - trade names, trademarks, or service marks; or - - f) Requiring indemnification of licensors and authors of that - material by anyone who conveys the material (or modified versions of - it) with contractual assumptions of liability to the recipient, for - any liability that these contractual assumptions directly impose on - those licensors and authors. - - All other non-permissive additional terms are considered "further -restrictions" within the meaning of section 10. If the Program as you -received it, or any part of it, contains a notice stating that it is -governed by this License along with a term that is a further -restriction, you may remove that term. If a license document contains -a further restriction but permits relicensing or conveying under this -License, you may add to a covered work material governed by the terms -of that license document, provided that the further restriction does -not survive such relicensing or conveying. - - If you add terms to a covered work in accord with this section, you -must place, in the relevant source files, a statement of the -additional terms that apply to those files, or a notice indicating -where to find the applicable terms. - - Additional terms, permissive or non-permissive, may be stated in the -form of a separately written license, or stated as exceptions; -the above requirements apply either way. - - 8. Termination. - - You may not propagate or modify a covered work except as expressly -provided under this License. Any attempt otherwise to propagate or -modify it is void, and will automatically terminate your rights under -this License (including any patent licenses granted under the third -paragraph of section 11). - - However, if you cease all violation of this License, then your -license from a particular copyright holder is reinstated (a) -provisionally, unless and until the copyright holder explicitly and -finally terminates your license, and (b) permanently, if the copyright -holder fails to notify you of the violation by some reasonable means -prior to 60 days after the cessation. - - Moreover, your license from a particular copyright holder is -reinstated permanently if the copyright holder notifies you of the -violation by some reasonable means, this is the first time you have -received notice of violation of this License (for any work) from that -copyright holder, and you cure the violation prior to 30 days after -your receipt of the notice. - - Termination of your rights under this section does not terminate the -licenses of parties who have received copies or rights from you under -this License. If your rights have been terminated and not permanently -reinstated, you do not qualify to receive new licenses for the same -material under section 10. - - 9. Acceptance Not Required for Having Copies. - - You are not required to accept this License in order to receive or -run a copy of the Program. Ancillary propagation of a covered work -occurring solely as a consequence of using peer-to-peer transmission -to receive a copy likewise does not require acceptance. However, -nothing other than this License grants you permission to propagate or -modify any covered work. These actions infringe copyright if you do -not accept this License. Therefore, by modifying or propagating a -covered work, you indicate your acceptance of this License to do so. - - 10. Automatic Licensing of Downstream Recipients. - - Each time you convey a covered work, the recipient automatically -receives a license from the original licensors, to run, modify and -propagate that work, subject to this License. You are not responsible -for enforcing compliance by third parties with this License. - - An "entity transaction" is a transaction transferring control of an -organization, or substantially all assets of one, or subdividing an -organization, or merging organizations. If propagation of a covered -work results from an entity transaction, each party to that -transaction who receives a copy of the work also receives whatever -licenses to the work the party's predecessor in interest had or could -give under the previous paragraph, plus a right to possession of the -Corresponding Source of the work from the predecessor in interest, if -the predecessor has it or can get it with reasonable efforts. - - You may not impose any further restrictions on the exercise of the -rights granted or affirmed under this License. For example, you may -not impose a license fee, royalty, or other charge for exercise of -rights granted under this License, and you may not initiate litigation -(including a cross-claim or counterclaim in a lawsuit) alleging that -any patent claim is infringed by making, using, selling, offering for -sale, or importing the Program or any portion of it. - - 11. Patents. - - A "contributor" is a copyright holder who authorizes use under this -License of the Program or a work on which the Program is based. The -work thus licensed is called the contributor's "contributor version". - - A contributor's "essential patent claims" are all patent claims -owned or controlled by the contributor, whether already acquired or -hereafter acquired, that would be infringed by some manner, permitted -by this License, of making, using, or selling its contributor version, -but do not include claims that would be infringed only as a -consequence of further modification of the contributor version. For -purposes of this definition, "control" includes the right to grant -patent sublicenses in a manner consistent with the requirements of -this License. - - Each contributor grants you a non-exclusive, worldwide, royalty-free -patent license under the contributor's essential patent claims, to -make, use, sell, offer for sale, import and otherwise run, modify and -propagate the contents of its contributor version. - - In the following three paragraphs, a "patent license" is any express -agreement or commitment, however denominated, not to enforce a patent -(such as an express permission to practice a patent or covenant not to -sue for patent infringement). To "grant" such a patent license to a -party means to make such an agreement or commitment not to enforce a -patent against the party. - - If you convey a covered work, knowingly relying on a patent license, -and the Corresponding Source of the work is not available for anyone -to copy, free of charge and under the terms of this License, through a -publicly available network server or other readily accessible means, -then you must either (1) cause the Corresponding Source to be so -available, or (2) arrange to deprive yourself of the benefit of the -patent license for this particular work, or (3) arrange, in a manner -consistent with the requirements of this License, to extend the patent -license to downstream recipients. "Knowingly relying" means you have -actual knowledge that, but for the patent license, your conveying the -covered work in a country, or your recipient's use of the covered work -in a country, would infringe one or more identifiable patents in that -country that you have reason to believe are valid. - - If, pursuant to or in connection with a single transaction or -arrangement, you convey, or propagate by procuring conveyance of, a -covered work, and grant a patent license to some of the parties -receiving the covered work authorizing them to use, propagate, modify -or convey a specific copy of the covered work, then the patent license -you grant is automatically extended to all recipients of the covered -work and works based on it. - - A patent license is "discriminatory" if it does not include within -the scope of its coverage, prohibits the exercise of, or is -conditioned on the non-exercise of one or more of the rights that are -specifically granted under this License. You may not convey a covered -work if you are a party to an arrangement with a third party that is -in the business of distributing software, under which you make payment -to the third party based on the extent of your activity of conveying -the work, and under which the third party grants, to any of the -parties who would receive the covered work from you, a discriminatory -patent license (a) in connection with copies of the covered work -conveyed by you (or copies made from those copies), or (b) primarily -for and in connection with specific products or compilations that -contain the covered work, unless you entered into that arrangement, -or that patent license was granted, prior to 28 March 2007. - - Nothing in this License shall be construed as excluding or limiting -any implied license or other defenses to infringement that may -otherwise be available to you under applicable patent law. - - 12. No Surrender of Others' Freedom. - - If conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot convey a -covered work so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you may -not convey it at all. For example, if you agree to terms that obligate you -to collect a royalty for further conveying from those to whom you convey -the Program, the only way you could satisfy both those terms and this -License would be to refrain entirely from conveying the Program. - - 13. Remote Network Interaction; Use with the GNU General Public License. - - Notwithstanding any other provision of this License, if you modify the -Program, your modified version must prominently offer all users -interacting with it remotely through a computer network (if your version -supports such interaction) an opportunity to receive the Corresponding -Source of your version by providing access to the Corresponding Source -from a network server at no charge, through some standard or customary -means of facilitating copying of software. This Corresponding Source -shall include the Corresponding Source for any work covered by version 3 -of the GNU General Public License that is incorporated pursuant to the -following paragraph. - - Notwithstanding any other provision of this License, you have -permission to link or combine any covered work with a work licensed -under version 3 of the GNU General Public License into a single -combined work, and to convey the resulting work. The terms of this -License will continue to apply to the part which is the covered work, -but the work with which it is combined will remain governed by version -3 of the GNU General Public License. - - 14. Revised Versions of this License. - - The Free Software Foundation may publish revised and/or new versions of -the GNU Affero General Public License from time to time. Such new versions -will be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - - Each version is given a distinguishing version number. If the -Program specifies that a certain numbered version of the GNU Affero General -Public License "or any later version" applies to it, you have the -option of following the terms and conditions either of that numbered -version or of any later version published by the Free Software -Foundation. If the Program does not specify a version number of the -GNU Affero General Public License, you may choose any version ever published -by the Free Software Foundation. - - If the Program specifies that a proxy can decide which future -versions of the GNU Affero General Public License can be used, that proxy's -public statement of acceptance of a version permanently authorizes you -to choose that version for the Program. - - Later license versions may give you additional or different -permissions. However, no additional obligations are imposed on any -author or copyright holder as a result of your choosing to follow a -later version. - - 15. Disclaimer of Warranty. - - THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY -APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT -HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY -OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, -THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM -IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF -ALL NECESSARY SERVICING, REPAIR OR CORRECTION. - - 16. Limitation of Liability. - - IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS -THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY -GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE -USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF -DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD -PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), -EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF -SUCH DAMAGES. - - 17. Interpretation of Sections 15 and 16. - - If the disclaimer of warranty and limitation of liability provided -above cannot be given local legal effect according to their terms, -reviewing courts shall apply local law that most closely approximates -an absolute waiver of all civil liability in connection with the -Program, unless a warranty or assumption of liability accompanies a -copy of the Program in return for a fee. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -state the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - - Copyright (C) - - This program is free software: you can redistribute it and/or modify - it under the terms of the GNU Affero General Public License as published by - the Free Software Foundation, either version 3 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU Affero General Public License for more details. - - You should have received a copy of the GNU Affero General Public License - along with this program. If not, see . - -Also add information on how to contact you by electronic and paper mail. - - If your software can interact with users remotely through a computer -network, you should also make sure that it provides a way for users to -get its source. For example, if your program is a web application, its -interface could display a "Source" link that leads users to an archive -of the code. There are many ways you could offer source, and different -solutions will be better for different programs; see section 13 for the -specific requirements. - - You should also get your employer (if you work as a programmer) or school, -if any, to sign a "copyright disclaimer" for the program, if necessary. -For more information on this, and how to apply and follow the GNU AGPL, see -. diff --git a/build/jenkins/create-plot-data-from-log.sh b/build/create-plot-data-from-log.sh similarity index 100% rename from build/jenkins/create-plot-data-from-log.sh rename to build/create-plot-data-from-log.sh diff --git a/build/git/hooks/coding-standards.sh b/build/git/hooks/coding-standards.sh deleted file mode 100755 index d4e4c719df..0000000000 --- a/build/git/hooks/coding-standards.sh +++ /dev/null @@ -1,128 +0,0 @@ -#!/usr/bin/env ruby - -# This script can be installed as a git update hook. - -# It can also be installed as a gitolite 'hooklet' in the -# hooks/common/update.secondary.d/ directory. - -# NOTE: this script runs under the same assumptions as the 'update' hook, so -# the starting directory must be maintained and arguments must be passed on. - -$refname = ARGV[0] -$oldrev = ARGV[1] -$newrev = ARGV[2] -$user = ENV['USER'] - -def blacklist bl - all_revs = `git rev-list #{$oldrev}..#{$newrev}`.split("\n") - all_revs.each do |rev| - bl.each do |b| - if rev == b - puts "Revision #{b} is blacklisted, you must remove it from your branch (possibly using git rebase) before you can push." - exit 1 - end - end - end -end - -blacklist ['26d74dc0524c87c5dcc0c76040ce413a4848b57a'] - -# Only enforce policy on the master branch -exit 0 if $refname != 'refs/heads/master' - -puts "Enforcing Policies... \n(#{$refname}) (#{$oldrev[0,6]}) (#{$newrev[0,6]})" - -$regex = /\[ref: (\d+)\]/ - -$broken_commit_message = /Please enter a commit message to explain why this merge is necessary/ -$wrong_way_merge_master = /Merge( remote-tracking)? branch '([^\/]+\/)?master' into/ -$merge_master = /Merge branch '[^']+'((?! into)| into master)/ -$pull_merge = /Merge branch 'master' of / -$refs_or_closes_or_no_issue = /(refs #|closes #|fixes #|no issue #)/i - -# enforced custom commit message format -def check_message_format - all_revs = `git rev-list --first-parent #{$oldrev}..#{$newrev}`.split("\n") - merge_revs = `git rev-list --first-parent --min-parents=2 #{$oldrev}..#{$newrev}`.split("\n") - # single_revs = `git rev-list --first-parent --max-parents=1 #{$oldrev}..#{$newrev}`.split("\n") - broken = false - no_ff = false - - merge_revs.each do |rev| - message = `git cat-file commit #{rev} | sed '1,/^$/d'` - if $wrong_way_merge_master.match(message) - puts "\n[POLICY] Only non-fast-forward merges into master are allowed. Please" - puts "reset your master branch:" - puts " git reset --hard origin/master" - puts "and then merge your branch with the --no-ff option:" - puts " git merge your-branch --no-ff\n" - puts "Remember to add a reference to an issue number in the merge commit!\n" - puts "\n******************************************************************\n" - puts "\nOffending commit: #{rev}\n" - puts "\nOffending commit message:\n" - puts message - puts "\n******************************************************************\n" - puts "\n\n" - broken = true - no_ff = true - elsif $pull_merge.match(message) - puts "\n[POLICY] This appears to be a git pull merge of remote master into local" - puts "master. In order to maintain a linear first-parent history of master," - puts "please reset your branch and remerge or rebase using the latest master.\n" - puts "\n******************************************************************\n" - puts "\nOffending commit: #{rev}\n" - puts "\nOffending commit message:\n\n" - puts message - puts "\n******************************************************************\n" - puts "\n\n" - broken = true - elsif not $merge_master.match(message) and not - puts "\n[POLICY] This does not appear to be a merge of a feature" - puts "branch into master. Merges must follow the format" - puts "\"Merge branch 'feature-branch'\".\n" - puts "\n******************************************************************\n" - puts "\nOffending commit: #{rev}\n" - puts "\nOffending commit message:\n\n" - puts message - puts "\n******************************************************************\n" - puts "\n\n" - broken = true - end - end - - all_revs.each do |rev| - message = `git cat-file commit #{rev} | sed '1,/^$/d'` - if $broken_commit_message.match(message) - puts "\n[POLICY] Rejected broken commit message for including boilerplate" - puts "instruction text.\n" - puts "\n******************************************************************\n" - puts "\nOffending commit: #{rev}\n" - puts "\nOffending commit message:\n\n" - puts message - puts "\n******************************************************************\n" - puts "\n\n" - broken = true - end - - # Do not test when the commit is a no_ff merge (which will be rejected), because - # this test will complain about *every* commit in the merge otherwise, obscuring - # the real reason for the rejection (the no_ff merge) - if not no_ff and not $refs_or_closes_or_no_issue.match(message) - puts "\n[POLICY] All commits to master must include an issue using \"refs #\" or" - puts "\"closes #\", or specify \"no issue #\"\n" - puts "\n******************************************************************\n" - puts "\nOffending commit: #{rev}\n" - puts "\nOffending commit message:\n\n" - puts message - puts "\n******************************************************************\n" - puts "\n\n" - broken = true - end - end - - if broken - exit 1 - end -end - -check_message_format diff --git a/build/install/easy-docker-install.sh b/build/install/easy-docker-install.sh deleted file mode 100755 index fe6e186c84..0000000000 --- a/build/install/easy-docker-install.sh +++ /dev/null @@ -1,87 +0,0 @@ -#!/usr/bin/env bash - -# This script is intended to make Arvados installation easy. It will download the -# latest copy of the Arvados docker images as well as the arvdock command. It -# then uses arvdock to spin up Arvados on this computer. -# -# The latest version of this script is available at http://get.arvados.org, so that this -# command does the right thing: -# -# $ \curl -sSL http://get.arvados.org | bash -# -# Prerequisites: working docker installation. Run this script as a user who is a member -# of the docker group. - -COLUMNS=80 - -fail () { - title "$*" - exit 1 -} - -title () { - printf "\n%*s\n\n" $(((${#title}+$COLUMNS)/2)) "********** $1 **********" -} - -docker_pull () { - $DOCKER pull $* - - ECODE=$? - - if [[ "$ECODE" != "0" ]]; then - title "$DOCKER pull $* failed" - exit $ECODE - fi -} - -main () { - - \which which >/dev/null 2>&1 || fail "Error: could not find 'which' command." - - # find the docker binary - DOCKER=`which docker.io` - - if [[ "$DOCKER" == "" ]]; then - DOCKER=`which docker` - fi - - if [[ "$DOCKER" == "" ]]; then - fail "Error: you need to have docker installed. Could not find the docker executable." - fi - - echo - echo "If necessary, this command will download the latest Arvados docker images." - echo "The download can take a long time, depending on the speed of your internet connection." - echo "When the images are downloaded, it will then start an Arvados environment on this computer." - echo - docker_pull arvados/workbench - docker_pull arvados/doc - docker_pull arvados/keep - docker_pull arvados/shell - docker_pull arvados/sso - docker_pull arvados/compute - docker_pull arvados/keep - docker_pull arvados/keepproxy - docker_pull arvados/api - docker_pull crosbymichael/skydns - docker_pull crosbymichael/skydock - - # Now download arvdock and start the containers - echo - echo Downloading arvdock - echo - \curl -sSL https://raw.githubusercontent.com/curoverse/arvados/master/docker/arvdock -o arvdock - chmod 755 arvdock - - echo - echo Starting the docker containers - echo - ./arvdock start - - echo To stop the containers, run - echo - echo ./arvdock stop - echo -} - -main diff --git a/build/jenkins/run-cwl-tests.sh b/build/jenkins/run-cwl-tests.sh deleted file mode 100755 index 53c0538efd..0000000000 --- a/build/jenkins/run-cwl-tests.sh +++ /dev/null @@ -1,218 +0,0 @@ -#!/bin/bash - -read -rd "\000" helpmessage <&2 "Fatal: $* (encountered in ${FUNCNAME[1]} at ${BASH_SOURCE[1]} line ${BASH_LINENO[0]})" - exit 1 -} - -trap clear_temp INT EXIT - -# Set up temporary install dirs (unless existing dirs were supplied) -for tmpdir in VENVDIR -do - if [[ -n "${!tmpdir}" ]]; then - leave_temp[$tmpdir]=1 - else - eval $tmpdir=$(mktemp -d) - fi -done - - -while [[ -n "$1" ]] -do - arg="$1"; shift - case "$arg" in - --help) - echo >&2 "$helpmessage" - echo >&2 - exit 1 - ;; - --debug) - DEBUG=1 - ;; - --upload-pypi) - UPLOAD_PYPI=1 - ;; - --upload-docker) - UPLOAD_DOCKER=1 - ;; - --leave-temp) - leave_temp[VENVDIR]=1 - ;; - *=*) - eval export $(echo $arg | cut -d= -f1)=\"$(echo $arg | cut -d= -f2-)\" - ;; - *) - echo >&2 "$0: Unrecognized option: '$arg'. Try: $0 --help" - exit 1 - ;; - esac -done - -# Sanity check -if ! [[ -n "$WORKSPACE" ]]; then - echo >&2 "$helpmessage" - echo >&2 - echo >&2 "Error: WORKSPACE environment variable not set" - echo >&2 - exit 1 -fi - -if [[ "$DEBUG" != 0 ]]; then - echo "Workspace is $WORKSPACE" -fi - -virtualenv --setuptools "$VENVDIR" || fatal "virtualenv $VENVDIR failed" -. "$VENVDIR/bin/activate" - -handle_python_package () { - # This function assumes the current working directory is the python package directory - if [[ "$UPLOAD_PYPI" != 0 ]]; then - # Make sure only to use sdist - that's the only format pip can deal with (sigh) - if [[ "$DEBUG" != 0 ]]; then - python setup.py sdist upload - else - python setup.py -q sdist upload - fi - else - # Make sure only to use sdist - that's the only format pip can deal with (sigh) - if [[ "$DEBUG" != 0 ]]; then - python setup.py sdist - else - python setup.py -q sdist - fi - fi -} - -# Make all files world-readable -- jenkins runs with umask 027, and has checked -# out our git tree here -chmod o+r "$WORKSPACE" -R - -# Now fix our umask to something better suited to building and publishing -# gems and packages -umask 0022 - -if [[ "$DEBUG" != 0 ]]; then - echo "umask is" `umask` -fi - -# Python packages -if [[ "$DEBUG" != 0 ]]; then - echo - echo "Python packages" - echo -fi - -cd "$WORKSPACE" - -if test -d cwltool ; then - (cd cwltool - git fetch - git reset --hard origin/master - ) -else - git clone git@github.com:common-workflow-language/cwltool.git - (cd cwltool - git config user.email "sysadmin@curoverse.com" - git config user.name "Curoverse build bot" - ) -fi - -(cd cwltool - python setup.py install - python setup.py test - ./build-node-docker.sh -) - -./run_test.sh RUNNER=cwltool/cwltool/main.py DRAFT=draft-2 -./run_test.sh RUNNER=cwltool/cwltool/main.py DRAFT=draft-3 - -(cd cwltool - handle_python_package -) - -(cd cwltool/cwl-runner - handle_python_package -) - -(cd cwltool - ./build-cwl-docker.sh -) - -if [[ "$UPLOAD_DOCKER" != 0 ]]; then - docker push commonworkflowlanguage/cwltool_module - docker push commonworkflowlanguage/cwltool - docker push commonworkflowlanguage/nodejs-engine -fi - -if test -d common-workflow-language.github.io ; then - (cd common-workflow-language.github.io - git fetch - git reset --hard origin/master - ) -else - git clone git@github.com:common-workflow-language/common-workflow-language.github.io.git - (cd common-workflow-language.github.io - git config user.email "sysadmin@curoverse.com" - git config user.name "Curoverse build bot" - ) -fi - -python -mcwltool --outdir=$PWD/common-workflow-language.github.io site/cwlsite.cwl site/cwlsite-job.json - -(cd common-workflow-language.github.io - git add --all - git diff-index --quiet HEAD || git commit -m"Build bot" - git push -) diff --git a/build/jenkins/run-deploy.sh b/build/jenkins/run-deploy.sh deleted file mode 100755 index 1b06c6580a..0000000000 --- a/build/jenkins/run-deploy.sh +++ /dev/null @@ -1,266 +0,0 @@ -#!/bin/bash - -DEBUG=0 -SSH_PORT=22 - -function usage { - echo >&2 - echo >&2 "usage: $0 [options] " - echo >&2 - echo >&2 " Arvados cluster name" - echo >&2 - echo >&2 "$0 options:" - echo >&2 " -p, --port SSH port to use (default 22)" - echo >&2 " -d, --debug Enable debug output" - echo >&2 " -h, --help Display this help and exit" - echo >&2 - echo >&2 "Note: this script requires an arvados token created with these permissions:" - echo >&2 ' arv api_client_authorization create_system_auth \' - echo >&2 ' --scopes "[\"GET /arvados/v1/virtual_machines\",' - echo >&2 ' \"GET /arvados/v1/keep_services\",' - echo >&2 ' \"GET /arvados/v1/keep_services/\",' - echo >&2 ' \"GET /arvados/v1/groups\",' - echo >&2 ' \"GET /arvados/v1/groups/\",' - echo >&2 ' \"GET /arvados/v1/links\",' - echo >&2 ' \"GET /arvados/v1/collections\",' - echo >&2 ' \"POST /arvados/v1/collections\",' - echo >&2 ' \"POST /arvados/v1/links\"]"' - echo >&2 -} - -# NOTE: This requires GNU getopt (part of the util-linux package on Debian-based distros). -TEMP=`getopt -o hdp: \ - --long help,debug,port: \ - -n "$0" -- "$@"` - -if [ $? != 0 ] ; then echo "Use -h for help"; exit 1 ; fi -# Note the quotes around `$TEMP': they are essential! -eval set -- "$TEMP" - -while [ $# -ge 1 ] -do - case $1 in - -p | --port) - SSH_PORT="$2"; shift 2 - ;; - -d | --debug) - DEBUG=1 - shift - ;; - --) - shift - break - ;; - *) - usage - exit 1 - ;; - esac -done - -IDENTIFIER=$1 - -if [[ "$IDENTIFIER" == '' ]]; then - usage - exit 1 -fi - -EXITCODE=0 - -COLUMNS=80 - -PUPPET_AGENT=' -now() { date +%s; } -let endtime="$(now) + 600" -while [ "$endtime" -gt "$(now)" ]; do - puppet agent --test --detailed-exitcodes - agent_exitcode=$? - if [ 0 = "$agent_exitcode" ] || [ 2 = "$agent_exitcode" ]; then - break - else - sleep 10s - fi -done -exit ${agent_exitcode:-99} -' - -title () { - date=`date +'%Y-%m-%d %H:%M:%S'` - printf "$date $1\n" -} - -function run_puppet() { - node=$1 - return_var=$2 - - title "Running puppet on $node" - TMP_FILE=`mktemp` - if [[ "$DEBUG" != "0" ]]; then - ssh -t -p$SSH_PORT -o "StrictHostKeyChecking no" -o "ConnectTimeout 5" root@$node -C bash -c "'$PUPPET_AGENT'" | tee $TMP_FILE - else - ssh -t -p$SSH_PORT -o "StrictHostKeyChecking no" -o "ConnectTimeout 5" root@$node -C bash -c "'$PUPPET_AGENT'" > $TMP_FILE 2>&1 - fi - - ECODE=${PIPESTATUS[0]} - RESULT=$(cat $TMP_FILE) - - if [[ "$ECODE" != "255" && ! ("$RESULT" =~ 'already in progress') && "$ECODE" != "2" && "$ECODE" != "0" ]]; then - # Ssh exits 255 if the connection timed out. Just ignore that. - # Puppet exits 2 if there are changes. For real! - # Puppet prints 'Notice: Run of Puppet configuration client already in progress' if another puppet process - # was already running - echo "ERROR running puppet on $node: exit code $ECODE" - if [[ "$DEBUG" == "0" ]]; then - title "Command output follows:" - echo $RESULT - fi - fi - if [[ "$ECODE" == "255" ]]; then - title "Connection timed out" - ECODE=0 - fi - if [[ "$ECODE" == "2" ]]; then - ECODE=0 - fi - rm -f $TMP_FILE - eval "$return_var=$ECODE" -} - -function run_command() { - node=$1 - return_var=$2 - command=$3 - - title "Running '$command' on $node" - TMP_FILE=`mktemp` - if [[ "$DEBUG" != "0" ]]; then - ssh -t -p$SSH_PORT -o "StrictHostKeyChecking no" -o "ConnectTimeout 5" root@$node -C "$command" | tee $TMP_FILE - else - ssh -t -p$SSH_PORT -o "StrictHostKeyChecking no" -o "ConnectTimeout 5" root@$node -C "$command" > $TMP_FILE 2>&1 - fi - - ECODE=$? - RESULT=$(cat $TMP_FILE) - - if [[ "$ECODE" != "255" && "$ECODE" != "0" ]]; then - # Ssh exists 255 if the connection timed out. Just ignore that, it's possible that this node is - # a shell node that is down. - title "ERROR running command on $node: exit code $ECODE" - if [[ "$DEBUG" == "0" ]]; then - title "Command output follows:" - echo $RESULT - fi - fi - if [[ "$ECODE" == "255" ]]; then - title "Connection timed out" - ECODE=0 - fi - rm -f $TMP_FILE - eval "$return_var=$ECODE" -} - -title "Updating API server" -SUM_ECODE=0 -run_puppet $IDENTIFIER.arvadosapi.com ECODE -SUM_ECODE=$(($SUM_ECODE + $ECODE)) -if [ ! "$IDENTIFIER" = "c97qk" ] -then - run_command $IDENTIFIER.arvadosapi.com ECODE "dpkg -L arvados-mailchimp-plugin 2>/dev/null && apt-get install arvados-mailchimp-plugin --reinstall || echo" - SUM_ECODE=$(($SUM_ECODE + $ECODE)) -fi - -if [[ "$SUM_ECODE" != "0" ]]; then - title "ERROR: Updating API server FAILED" - EXITCODE=$(($EXITCODE + $SUM_ECODE)) - exit $EXITCODE -fi - -title "Loading ARVADOS_API_HOST and ARVADOS_API_TOKEN" -if [[ -f "$HOME/.config/arvados/$IDENTIFIER.arvadosapi.com.conf" ]]; then - . $HOME/.config/arvados/$IDENTIFIER.arvadosapi.com.conf -else - title "WARNING: $HOME/.config/arvados/$IDENTIFIER.arvadosapi.com.conf not found." -fi -if [[ "$ARVADOS_API_HOST" == "" ]] || [[ "$ARVADOS_API_TOKEN" == "" ]]; then - title "ERROR: ARVADOS_API_HOST and/or ARVADOS_API_TOKEN environment variables are not set." - exit 1 -fi - -title "Locating Arvados Standard Docker images project" - -JSON_FILTER="[[\"name\", \"=\", \"Arvados Standard Docker Images\"], [\"owner_uuid\", \"=\", \"$IDENTIFIER-tpzed-000000000000000\"]]" -DOCKER_IMAGES_PROJECT=`ARVADOS_API_HOST=$ARVADOS_API_HOST ARVADOS_API_TOKEN=$ARVADOS_API_TOKEN arv --format=uuid group list --filters="$JSON_FILTER"` - -if [[ "$DOCKER_IMAGES_PROJECT" == "" ]]; then - title "Warning: Arvados Standard Docker Images project not found. Creating it." - - DOCKER_IMAGES_PROJECT=`ARVADOS_API_HOST=$ARVADOS_API_HOST ARVADOS_API_TOKEN=$ARVADOS_API_TOKEN arv --format=uuid group create --group "{\"owner_uuid\":\"$IDENTIFIER-tpzed-000000000000000\", \"name\":\"Arvados Standard Docker Images\", \"group_class\":\"project\"}"` - ARVADOS_API_HOST=$ARVADOS_API_HOST ARVADOS_API_TOKEN=$ARVADOS_API_TOKEN arv link create --link "{\"tail_uuid\":\"$IDENTIFIER-j7d0g-fffffffffffffff\", \"head_uuid\":\"$DOCKER_IMAGES_PROJECT\", \"link_class\":\"permission\", \"name\":\"can_read\" }" - if [[ "$?" != "0" ]]; then - title "ERROR: could not create standard Docker images project Please create it, cf. http://doc.arvados.org/install/create-standard-objects.html" - exit 1 - fi -fi - -title "Found Arvados Standard Docker Images project with uuid $DOCKER_IMAGES_PROJECT" -GIT_COMMIT=`ssh -o "StrictHostKeyChecking no" $IDENTIFIER cat /usr/local/arvados/src/git-commit.version` - -if [[ "$?" != "0" ]] || [[ "$GIT_COMMIT" == "" ]]; then - title "ERROR: unable to get arvados/jobs Docker image git revision" - exit 1 -else - title "Found git commit for arvados/jobs Docker image: $GIT_COMMIT" -fi - -run_command shell.$IDENTIFIER ECODE "ARVADOS_API_HOST=$ARVADOS_API_HOST ARVADOS_API_TOKEN=$ARVADOS_API_TOKEN /usr/local/rvm/bin/rvm-exec default arv keep docker" |grep -q $GIT_COMMIT - -if [[ "$?" == "0" ]]; then - title "Found latest arvados/jobs Docker image, nothing to upload" -else - title "Installing latest arvados/jobs Docker image" - ssh -o "StrictHostKeyChecking no" shell.$IDENTIFIER "ARVADOS_API_HOST=$ARVADOS_API_HOST ARVADOS_API_TOKEN=$ARVADOS_API_TOKEN /usr/local/rvm/bin/rvm-exec default arv keep docker --pull --project-uuid=$DOCKER_IMAGES_PROJECT arvados/jobs $GIT_COMMIT" - if [[ "$?" -ne 0 ]]; then - title "'git pull' failed exiting..." - exit 1 - fi -fi - -title "Gathering list of shell and Keep nodes" -SHELL_NODES=`ARVADOS_API_HOST=$ARVADOS_API_HOST ARVADOS_API_TOKEN=$ARVADOS_API_TOKEN arv virtual_machine list |jq .items[].hostname -r` -KEEP_NODES=`ARVADOS_API_HOST=$ARVADOS_API_HOST ARVADOS_API_TOKEN=$ARVADOS_API_TOKEN arv keep_service list |jq .items[].service_host -r` - -title "Updating workbench" -SUM_ECODE=0 -if [[ `host workbench.$ARVADOS_API_HOST |cut -f4 -d' '` != `host $ARVADOS_API_HOST |cut -f4 -d' '` ]]; then - # Workbench runs on a separate host. We need to run puppet there too. - run_puppet workbench.$IDENTIFIER ECODE - SUM_ECODE=$(($SUM_ECODE + $ECODE)) -fi - -if [[ "$SUM_ECODE" != "0" ]]; then - title "ERROR: Updating workbench FAILED" - EXITCODE=$(($EXITCODE + $SUM_ECODE)) - exit $EXITCODE -fi - -for n in manage switchyard $SHELL_NODES $KEEP_NODES; do - ECODE=0 - if [[ $n =~ $ARVADOS_API_HOST$ ]]; then - # e.g. keep.qr1hi.arvadosapi.com - node=$n - else - # e.g. shell - node=$n.$ARVADOS_API_HOST - fi - - # e.g. keep.qr1hi - node=${node%.arvadosapi.com} - - title "Updating $node" - run_puppet $node ECODE - if [[ "$ECODE" != "0" ]]; then - title "ERROR: Updating $node node FAILED: exit code $ECODE" - EXITCODE=$(($EXITCODE + $ECODE)) - exit $EXITCODE - fi -done diff --git a/build/jenkins/run-diagnostics-suite.sh b/build/jenkins/run-diagnostics-suite.sh deleted file mode 100755 index 015a0539c8..0000000000 --- a/build/jenkins/run-diagnostics-suite.sh +++ /dev/null @@ -1,86 +0,0 @@ -#!/bin/bash - -EXITCODE=0 - -INSTANCE=$1 -REVISION=$2 - -if [[ "$INSTANCE" == '' ]]; then - echo "Syntax: $0 [revision]" - exit 1 -fi - -if [[ "$REVISION" == '' ]]; then - # See if there's a configuration file with the revision? - CONFIG_PATH=/home/jenkins/configuration/$INSTANCE.arvadosapi.com-versions.conf - if [[ -f $CONFIG_PATH ]]; then - echo "Loading git revision from $CONFIG_PATH" - . $CONFIG_PATH - REVISION=$ARVADOS_GIT_REVISION - fi -fi - -if [[ "$REVISION" != '' ]]; then - echo "Git revision is $REVISION" -else - echo "No valid git revision found, proceeding with what is in place." -fi - -# Sanity check -if ! [[ -n "$WORKSPACE" ]]; then - echo "WORKSPACE environment variable not set" - exit 1 -fi - -title () { - txt="********** $1 **********" - printf "\n%*s%s\n\n" $((($COLUMNS-${#txt})/2)) "" "$txt" -} - -timer_reset() { - t0=$SECONDS -} - -timer() { - echo -n "$(($SECONDS - $t0))s" -} - -source /etc/profile.d/rvm.sh -echo $WORKSPACE - -title "Starting diagnostics" -timer_reset - -cd $WORKSPACE - -if [[ "$REVISION" != '' ]]; then - git checkout $REVISION -fi - -cp -f /home/jenkins/diagnostics/arvados-workbench/$INSTANCE-application.yml $WORKSPACE/apps/workbench/config/application.yml - -cd $WORKSPACE/apps/workbench - -HOME="$GEMHOME" bundle install --no-deployment - -if [[ ! -d tmp ]]; then - mkdir tmp -fi - -RAILS_ENV=diagnostics bundle exec rake TEST=test/diagnostics/pipeline_test.rb - -ECODE=$? - -if [[ "$REVISION" != '' ]]; then - git checkout master -fi - -if [[ "$ECODE" != "0" ]]; then - title "!!!!!! DIAGNOSTICS FAILED (`timer`) !!!!!!" - EXITCODE=$(($EXITCODE + $ECODE)) - exit $EXITCODE -fi - -title "Diagnostics complete (`timer`)" - -exit $EXITCODE diff --git a/build/jenkins/run-performance-suite.sh b/build/jenkins/run-performance-suite.sh deleted file mode 100755 index 2944bda5ed..0000000000 --- a/build/jenkins/run-performance-suite.sh +++ /dev/null @@ -1,88 +0,0 @@ -#!/bin/bash - -EXITCODE=0 - -INSTANCE=$1 -REVISION=$2 - -if [[ "$INSTANCE" == '' ]]; then - echo "Syntax: $0 [revision]" - exit 1 -fi - -if [[ "$REVISION" == '' ]]; then - # See if there's a configuration file with the revision? - CONFIG_PATH=/home/jenkins/configuration/$INSTANCE.arvadosapi.com-versions.conf - if [[ -f $CONFIG_PATH ]]; then - echo "Loading git revision from $CONFIG_PATH" - . $CONFIG_PATH - REVISION=$ARVADOS_GIT_REVISION - fi -fi - -if [[ "$REVISION" != '' ]]; then - echo "Git revision is $REVISION" -else - echo "No valid git revision found, proceeding with what is in place." -fi - -# Sanity check -if ! [[ -n "$WORKSPACE" ]]; then - echo "WORKSPACE environment variable not set" - exit 1 -fi - -title () { - txt="********** $1 **********" - printf "\n%*s%s\n\n" $((($COLUMNS-${#txt})/2)) "" "$txt" -} - -timer_reset() { - t0=$SECONDS -} - -timer() { - echo -n "$(($SECONDS - $t0))s" -} - -source /etc/profile.d/rvm.sh -echo $WORKSPACE - -title "Starting performance test" -timer_reset - -cd $WORKSPACE - -if [[ "$REVISION" != '' ]]; then - git checkout $REVISION -fi - -cp -f /home/jenkins/diagnostics/arvados-workbench/$INSTANCE-application.yml $WORKSPACE/apps/workbench/config/application.yml - -cd $WORKSPACE/apps/workbench - -HOME="$GEMHOME" bundle install --no-deployment - -if [[ ! -d tmp ]]; then - mkdir tmp -fi - -mkdir -p tmp/cache - -RAILS_ENV=performance bundle exec rake test:benchmark - -ECODE=$? - -if [[ "$REVISION" != '' ]]; then - git checkout master -fi - -if [[ "$ECODE" != "0" ]]; then - title "!!!!!! PERFORMANCE TESTS FAILED (`timer`) !!!!!!" - EXITCODE=$(($EXITCODE + $ECODE)) - exit $EXITCODE -fi - -title "Performance tests complete (`timer`)" - -exit $EXITCODE diff --git a/build/jenkins/run-tapestry-tests.sh b/build/jenkins/run-tapestry-tests.sh deleted file mode 100755 index 851a81dc58..0000000000 --- a/build/jenkins/run-tapestry-tests.sh +++ /dev/null @@ -1,54 +0,0 @@ -#!/bin/bash - -EXITCODE=0 - -COLUMNS=80 - -title () { - printf "\n%*s\n\n" $(((${#title}+$COLUMNS)/2)) "********** $1 **********" -} - -source /etc/profile.d/rvm.sh - -# This shouldn't really be necessary... but the jenkins/rvm integration seems a -# bit wonky occasionally. -rvm use ree - -echo $WORKSPACE - -# Tapestry -title "Starting tapestry tests" -cd "$WORKSPACE" - -# There are a few submodules -git submodule init && git submodule update - -# Use sqlite for testing -sed -i'' -e "s:mysql:sqlite3:" Gemfile - -# Tapestry is not set up yet to use --deployment -#bundle install --deployment -bundle install - -rm -f config/database.yml -rm -f config/environments/test.rb -cp $HOME/tapestry/test.rb config/environments/ -cp $HOME/tapestry/database.yml config/ - -export RAILS_ENV=test - -bundle exec rake db:drop -bundle exec rake db:create -bundle exec rake db:setup -bundle exec rake test - -ECODE=$? - -if [[ "$ECODE" != "0" ]]; then - title "!!!!!! TAPESTRY TESTS FAILED !!!!!!" - EXITCODE=$(($EXITCODE + $ECODE)) -fi - -title "Tapestry tests complete" - -exit $EXITCODE diff --git a/build/jenkins/run_upload_packages.py b/build/jenkins/run_upload_packages.py deleted file mode 100755 index 04e6c801a5..0000000000 --- a/build/jenkins/run_upload_packages.py +++ /dev/null @@ -1,273 +0,0 @@ -#!/usr/bin/env python3 - -import argparse -import functools -import glob -import logging -import os -import pipes -import shutil -import subprocess -import sys -import time - -class TimestampFile: - def __init__(self, path): - self.path = path - self.start_time = time.time() - - def last_upload(self): - try: - return os.path.getmtime(self.path) - except EnvironmentError: - return -1 - - def update(self): - os.close(os.open(self.path, os.O_CREAT | os.O_APPEND)) - os.utime(self.path, (time.time(), self.start_time)) - - -class PackageSuite: - NEED_SSH = False - - def __init__(self, glob_root, rel_globs): - logger_part = getattr(self, 'LOGGER_PART', os.path.basename(glob_root)) - self.logger = logging.getLogger('arvados-dev.upload.' + logger_part) - self.globs = [os.path.join(glob_root, rel_glob) - for rel_glob in rel_globs] - - def files_to_upload(self, since_timestamp): - for abs_glob in self.globs: - for path in glob.glob(abs_glob): - if os.path.getmtime(path) >= since_timestamp: - yield path - - def upload_file(self, path): - raise NotImplementedError("PackageSuite.upload_file") - - def upload_files(self, paths): - for path in paths: - self.logger.info("Uploading %s", path) - self.upload_file(path) - - def post_uploads(self, paths): - pass - - def update_packages(self, since_timestamp): - upload_paths = list(self.files_to_upload(since_timestamp)) - if upload_paths: - self.upload_files(upload_paths) - self.post_uploads(upload_paths) - - -class PythonPackageSuite(PackageSuite): - LOGGER_PART = 'python' - - def __init__(self, glob_root, rel_globs): - super().__init__(glob_root, rel_globs) - self.seen_packages = set() - - def upload_file(self, path): - src_dir = os.path.dirname(os.path.dirname(path)) - if src_dir in self.seen_packages: - return - self.seen_packages.add(src_dir) - # NOTE: If we ever start uploading Python 3 packages, we'll need to - # figure out some way to adapt cmd to match. It might be easiest - # to give all our setup.py files the executable bit, and run that - # directly. - # We also must run `sdist` before `upload`: `upload` uploads any - # distributions previously generated in the command. It doesn't - # know how to upload distributions already on disk. We write the - # result to a dedicated directory to avoid interfering with our - # timestamp tracking. - cmd = ['python2.7', 'setup.py'] - if not self.logger.isEnabledFor(logging.INFO): - cmd.append('--quiet') - cmd.extend(['sdist', '--dist-dir', '.upload_dist', 'upload']) - subprocess.check_call(cmd, cwd=src_dir) - shutil.rmtree(os.path.join(src_dir, '.upload_dist')) - - -class GemPackageSuite(PackageSuite): - LOGGER_PART = 'gems' - - def upload_file(self, path): - cmd = ['gem', 'push', path] - push_proc = subprocess.Popen(cmd, stdout=subprocess.PIPE) - repushed = any(line == b'Repushing of gem versions is not allowed.\n' - for line in push_proc.stdout) - # Read any remaining stdout before closing. - for line in push_proc.stdout: - pass - push_proc.stdout.close() - if (push_proc.wait() != 0) and not repushed: - raise subprocess.CalledProcessError(push_proc.returncode, cmd) - - -class DistroPackageSuite(PackageSuite): - NEED_SSH = True - REMOTE_DEST_DIR = 'tmp' - - def __init__(self, glob_root, rel_globs, target, ssh_host, ssh_opts): - super().__init__(glob_root, rel_globs) - self.target = target - self.ssh_host = ssh_host - self.ssh_opts = ['-o' + opt for opt in ssh_opts] - if not self.logger.isEnabledFor(logging.INFO): - self.ssh_opts.append('-q') - - def _build_cmd(self, base_cmd, *args): - cmd = [base_cmd] - cmd.extend(self.ssh_opts) - cmd.extend(args) - return cmd - - def _paths_basenames(self, paths): - return (os.path.basename(path) for path in paths) - - def _run_script(self, script, *args): - # SSH will use a shell to run our bash command, so we have to - # quote our arguments. - # self.__class__.__name__ provides $0 for the script, which makes a - # nicer message if there's an error. - subprocess.check_call(self._build_cmd( - 'ssh', self.ssh_host, 'bash', '-ec', pipes.quote(script), - self.__class__.__name__, *(pipes.quote(s) for s in args))) - - def upload_files(self, paths): - cmd = self._build_cmd('scp', *paths) - cmd.append('{self.ssh_host}:{self.REMOTE_DEST_DIR}'.format(self=self)) - subprocess.check_call(cmd) - - -class DebianPackageSuite(DistroPackageSuite): - FREIGHT_SCRIPT = """ -cd "$1"; shift -DISTNAME=$1; shift -freight add "$@" "apt/$DISTNAME" -freight cache "apt/$DISTNAME" -rm "$@" -""" - TARGET_DISTNAMES = { - 'debian7': 'wheezy', - 'debian8': 'jessie', - 'ubuntu1204': 'precise', - 'ubuntu1404': 'trusty', - } - - def post_uploads(self, paths): - self._run_script(self.FREIGHT_SCRIPT, self.REMOTE_DEST_DIR, - self.TARGET_DISTNAMES[self.target], - *self._paths_basenames(paths)) - - -class RedHatPackageSuite(DistroPackageSuite): - CREATEREPO_SCRIPT = """ -cd "$1"; shift -REPODIR=$1; shift -rpmsign --addsign "$@"