Check if there is already a .tx folder and run tx --init only if
there is none. The horizon repo currently has one and thus the job fails
to build.
Change-Id: Ifa3115943c49550f3d72007484e9343f7de1d8ca
This was used when transitioning to ZUUL_URL from the calling
environment, and is no longer required by any calls to the script.
Change-Id: Ie3e1740a6cc3d67bd306b5d6c258002d51eaffe8
Currently the periodic job manuals-propose-translation-update runs
three times on the same repository instead of running once each for
api-site, openstack-manuals and operations-guide.
Also, manuals-upstream-translation-update does not handle the api-site
repo.
* Change the scripts so that they handle all three repositories.
* Update the jenkins configuration to call the scripts with repository name
as parameter. This needs new job-templates.
* Create a job-group
* Use job-group for each repository.
* Adjust Zuul for new jobs using a template.
* Update manual jobs in zuul to check for just "master" as branch
instead of using a regex.
Change-Id: I755730ea43ad05a373704ab2fb7e5b55f1c8aeee
Closes-Bug: #1291844
Maintaining transifix in git causes some problems, we're removing it
now from openstack-manuals and thus need to initialize it here.
The manuals change at https://review.openstack.org/#/c/79859 is waiting
for this to go in.
Change-Id: I1bc1e1ae0f25ce5d88a70cdbab2541c8a52ddd78
Jenkins needs to sudo as stack and tempest to properly run devstack jobs
and may need to act on behalf of other users in the future. Rather than
listing root,stack,tempest in the sudoer file just let jenkins sudo as
any user.
Fixes-bug: 1290669
Change-Id: I4a5c6b7ead717475d6334a7ef3121271aca83f5a
the script has a set -e mid way through which is now defeating
the explanation parts of the script. Remove this to actually
come back to our normally scheduled program.
Change-Id: I53b5888f44083731b60e03a833f6d8e7769e0e47
Add script and job to push the 4 Horizon translation source files
(4 English po files) to Transifex.
Since Horizon has two "locale" folders in different position,
it's not able to levarage the existing upstream_translation.sh
and have to add a new upstream_translation_horizon.sh.
Change-Id: I7a42365414a6a5dcde276bc10761b08e3e756931
Create a new version-properties.sh script that will be used on slave
hosts to determine version information from git. This is mostly a copy
of the maven-properties.sh script. The reason we are not simply renaming
is that this commit must be merged then all slave images updated before
we change our jenkins jobs to use the new script. Renaming doesn't allow
us to do that.
Change-Id: I37c0b7cc3ca034addf32897a5a8c6501dedf00b0
This reverts commit dea3bdb050a55d56a1913e50e59cf176d70d3eb7.
This revert is necessary because it changed jenkins jobs before the
slave images could be rebuilt. We need to update the slave images first
then update the jenkins jobs in a pair of changes that can be merged one
at a time.
Change-Id: Iae4abf8c2dd8ad67ad008c57bbd17ba1304134c6
Initially maven-properties.sh was intended to make maven projects use git versioning,
that's how it got the name. However this filename is inappropriate because it's just a
generic script that retrieves git version info to allow builds to version their artifacts.
version-properties.sh is a much more appropriate name for this script.
Change-Id: I3ffc3e9e29bb626f4af5449f0413608a30ee79a0
Add check, gate, post and release jobs to PHP/Laravel based openstackid
project. Extend precise node with php5-mcrypt package required for
build process.
Change-Id: If7858412d5c3425aab20c0d11a92cab4c86f47dd
This way we can start with the file in place on all single-use
slaves, and then remove the file at the beginning of jobs that
should not be able to sudo (for example, unit test jobs).
Change-Id: I37aabdba89d00b45365126c8f776ae6ef8357c8f
Makes it easier to diagnose when we look at logs if it shows
if we using the internal mirror or not.
Change-Id: I61945e742dc7dcb021ed20cbace4196b32d192c4
When proposing requirement update changes ensure that the proper branch
can be checked out if the branch isn't master. To do this checkout
origin/$BRANCH instead of just branch. Additonally, don't git review -d
an existing change as it may have merge conflicts with the target
branch. Instead make changes against the target branch, push them to the
existing change as a new patchset, and ignore failures of git review
when there are no new changes.
This allows changes to the requirements files to happen out of band from
these automated change proposals.
Closes-Bug: 1274251
Change-Id: I7b81b87a90639a66dce5502cded5e37d96abd1f7
The OpenStack CI systems like things that run in virtualenvs. This moves
the first stab at running javascript unittests from custom in-tree scripts
to being based on tox and nodeenv. Additionally, it publishes the dist
dir from the tree to docs-draft, because the dist contents should be the
compiled, minified and fully-functional web code, and it should be directly
verifiable on a passing commit.
Change-Id: Id48ee2524d846b5e08ca94f485f8d67abbd3681a
When putting the alphabetize script into slave_scripts, we run the risk
of bugs entering the script without being tested before they are rolled
live and become part of the gate. This just recently happened. Instead,
move it to the tools dir, which makes it easy for a dev to run, and also
which makes changes to the script self-gating.
Change-Id: Ia5e1870f84b0cbc0c6f172b6982263440af5575e
The previous patch moved " PROJECTS_LIST=$OLDPWD/modules/..." before
the pushd call. But pushd changes the path and thus OLDPWD as well.
So, there are two possible fixes: Either remove the OLDPWD variable from
the if and set PROJECTS_LIST in another way with a full path or
move the pushd call before the if.
Change-Id: If47ab0cfb0078d5e570057c974e3d1f0367d4e0a
We're about to rename projects.yaml from review.projects.yaml.erb to
review.projects.yaml and this script needs to know about that.
Change-Id: I84f2caee8aeccb7816c9d367557f3bd0e8315ecf
Added $OLDPWD/ to the beginning of the path to
review.projects.yaml.erb. Hopefully the script can find the file
now and the job will run successfully.
Change-Id: I32ed800d79a39e47ae20c54147f2e4db2725c97b
Merging with git can cause git to want to pop you into an editor. That's
not cool in a script. Supply --no-edit to cause the commit to just work.
Change-Id: Ic70d74c28d1ca16ae21b2a6c141b26d4e68b21f0
It checks that projects.yaml alphabetized and prints list of projects
that should be sorted. Additionally, it adds new job as non-voting to
the openstack-infra/config project.
Change-Id: I9c0eb5072a5b1446ee654296e60c1f8587a3a7ad
* propose_requirements_update.sh: Look before we leap. Don't descend
into the project repository and try to check out a branch without
first making sure it exists on the origin.
Change-Id: Ib4de5bdf8bf5cf134e3307755617456f282d790d
Specify that git should diff against HEAD when diffing in the
propose_requirements_update.sh script. Replace --quiet with --exit-code
so that we can verbosely see what differences there are.
Change-Id: I0d194151db457f7eb56e010c94b20562d0221e34
Use git commit --amend when updating an preexisting requirements
proposal update change. Otherwise multiple changes are proposed causing
git review to run interactively and fail (and if it didn't fail multiple
dependent changes would be proposed which we don't want either).
Change-Id: Ic5a173d671ebe25e2bcf2b4972e39879992d3bdf
Shallow (--depth=1) clone raises some problems with git review tool.
Here is the part of the failed propose-requirements-update job logs:
+ git clone --depth=1 ssh://jenkins@review.openstack.org:29418/openstack/cinder.git
+ pushd cinder
+ git review -s
+ git review -d I2d8f240009d2f847b321baa011880f753783be83
Downloading refs/changes/69/60969/1 from gerrit into review/jenkins/openstack/requirements
fatal: unresolved deltas left after unpacking
fatal: unpack-objects failed
Change-Id: Ie69261fde73c18134906f3edd1263479830005c4
Some of our things, like new upstream gerrit, may have submodules
in them. In order to make sure that they, you know, work. We should
run some submodules update commands.
Change-Id: I7c47dd71a49108e79e27b5ba69fa09da638b3764
If testr ran zero tests treat that as a failing job. At least one test
should run in every Jenkins Job running testr. Failure to do that is a
job Failure.
Change-Id: I414def2db856d48f24cdc7f61437a66543e28258
The openstack/requirements repo maintains a list of projects that have
opted in to receiving automatic updates. Those projects clearly want to
be beholden to the mirror as well, so consume that for mirror choice
instead of trying to figure it out via rules based on name.
Change-Id: I5c65287fabe43fc3e6dec315b29c13788bd3c1ea
Apparently we needed to use the magical ZUUL_REF job variable to get the
branch info from a change in the Zuul post pipeline. Use it and only
propose requirements updates to the branches that were updated.
Closes-bug: 1246249
Change-Id: I7adfd19e502846d3a07cde1808fdc79164c061a9
