CIDuty/How To/PyUp Dependency PR Updates - Revision history

Apop: added link to other doc

2019-04-26T02:17:49Z

added link to other doc

← Older revision		Revision as of 02:17, 26 April 2019
Line 68:		Line 68:
	In order to correct that we need to pin it, and that can be done providing a "\" after the hash of the package, [https://github.com/mozilla-releng/mozilla-version/pull/36/commits/d8049b0bdf5201b986fb83bd37d804c6598468b8 example].		In order to correct that we need to pin it, and that can be done providing a "\" after the hash of the package, [https://github.com/mozilla-releng/mozilla-version/pull/36/commits/d8049b0bdf5201b986fb83bd37d804c6598468b8 example].
	This situation can appear on both repositories and would be a good thing to ask around what can be pinned and what not.		This situation can appear on both repositories and would be a good thing to ask around what can be pinned and what not.

			See also : [[CIDuty/How_To/Update_Python_dependencies\|Update Python dependencies]]

Apop: removed repos

2019-04-26T01:31:26Z

removed repos

← Older revision		Revision as of 01:31, 26 April 2019
Line 26:		Line 26:
	# [https://github.com/mozilla-releng/mozilla-version/ Mozilla Version]		# [https://github.com/mozilla-releng/mozilla-version/ Mozilla Version]
	# [https://github.com/mozilla-releng/build-puppet/ Build Puppet]		# [https://github.com/mozilla-releng/build-puppet/ Build Puppet]
	~~# [https://github.com/mozilla-releng/treescript/ Treescript]~~
	~~# [https://github.com/mozilla-releng/addonscript/ Addonscript]~~

	== How To: Mozilla-Version ==		== How To: Mozilla-Version ==

Apop: Apop moved page Ciduty/How To/PyUp Dependency PR Updates to CIDuty/How To/PyUp Dependency PR Updates: corrected the name of team

2019-04-16T00:37:05Z

Apop moved page Ciduty/How To/PyUp Dependency PR Updates to CIDuty/How To/PyUp Dependency PR Updates: corrected the name of team

← Older revision	Revision as of 00:37, 16 April 2019
(No difference)

Apop: Apop moved page Buildduty/How To/PyUp Dependency PR Updates to Ciduty/How To/PyUp Dependency PR Updates: changed the name of the team

2019-04-16T00:35:52Z

Apop moved page Buildduty/How To/PyUp Dependency PR Updates to Ciduty/How To/PyUp Dependency PR Updates: changed the name of the team

← Older revision	Revision as of 00:35, 16 April 2019
(No difference)

Bcrisan: Added treescript + addonscript to the list of repositories which we need to activate on.

2018-11-28T10:04:01Z

Added treescript + addonscript to the list of repositories which we need to activate on.

← Older revision		Revision as of 10:04, 28 November 2018
Line 26:		Line 26:
	# [https://github.com/mozilla-releng/mozilla-version/ Mozilla Version]		# [https://github.com/mozilla-releng/mozilla-version/ Mozilla Version]
	# [https://github.com/mozilla-releng/build-puppet/ Build Puppet]		# [https://github.com/mozilla-releng/build-puppet/ Build Puppet]
			# [https://github.com/mozilla-releng/treescript/ Treescript]
			# [https://github.com/mozilla-releng/addonscript/ Addonscript]

	== How To: Mozilla-Version ==		== How To: Mozilla-Version ==

Bcrisan: no need to announce jlorenzo about PR

2018-10-24T14:26:43Z

no need to announce jlorenzo about PR

← Older revision		Revision as of 14:26, 24 October 2018
Line 37:		Line 37:
	# Implement the needed changes + commit them (you can do it via github webui). Wait for the test results to come (about 10-15 minutes)		# Implement the needed changes + commit them (you can do it via github webui). Wait for the test results to come (about 10-15 minutes)
	# Squash and Merge the PR.		# Squash and Merge the PR.
	~~# Announce JLorenzo that the weekly PR is complete.~~

	=== Common Issues ===		=== Common Issues ===
Line 49:		Line 48:
	ERROR: could not install deps [-rrequirements-test.txt]; v = InvocationError('/home/travis/build/mozilla-releng/mozilla-version/.tox/py27/bin/python -m pip install -rrequirements-test.txt (see /home/travis/build/mozilla-releng/mozilla-version/.tox/py27/log/py27-1.log)', 1)		ERROR: could not install deps [-rrequirements-test.txt]; v = InvocationError('/home/travis/build/mozilla-releng/mozilla-version/.tox/py27/bin/python -m pip install -rrequirements-test.txt (see /home/travis/build/mozilla-releng/mozilla-version/.tox/py27/log/py27-1.log)', 1)

	it means the hash=sha512 is wrong. Please contact JLorenzo for a fix/sha string.		it means the hash=sha512 is wrong. Please contact JLorenzo for a fix/sha string. A quick fix would be cloning the repository, take the old version of that package (copy it from the cloned repository) and use it to revert the changes by reverting the package.

	== How To: Build-Puppet ==		== How To: Build-Puppet ==
	After you are done with Mozilla-Version, its time for Build-Puppet!		After you are done with Mozilla-Version, its time for Build-Puppet!

Bcrisan: Added another common issue + fix

2018-09-29T14:14:13Z

Added another common issue + fix

← Older revision		Revision as of 14:14, 29 September 2018
Line 62:		Line 62:
	# Announce Bhearsum that the weekly PR is complete.		# Announce Bhearsum that the weekly PR is complete.
	=== Common Issues ===		=== Common Issues ===
	# Requirements of a dependency. Example: flake8 3.5.0 has requirement pycodestyle<2.4.0,>=2.0.0, but you have pycodestyle 2.4.0.		1.Requirements of a dependency. Example: flake8 3.5.0 has requirement pycodestyle<2.4.0,>=2.0.0, but you have pycodestyle 2.4.0.
	With this issue, you have to keep which deps you have to either manually revert back at the older version (keep in mind you need the old sha512!) or if you pin the version of the dependency.		With this issue, you have to keep which deps you have to either manually revert back at the older version (keep in mind you need the old sha512!) or if you pin the version of the dependency.

			2.Another common issue regarding package versions, is that the bot will try and update a package several times if it's not pinned, thus braking things every week if that package cannot be updated because has another unmet dependency .
			In order to correct that we need to pin it, and that can be done providing a "\" after the hash of the package, [https://github.com/mozilla-releng/mozilla-version/pull/36/commits/d8049b0bdf5201b986fb83bd37d804c6598468b8 example].
			This situation can appear on both repositories and would be a good thing to ask around what can be pinned and what not.

Dlabici: WIP - How to work with PyUp PRs

2018-09-13T12:21:46Z

WIP - How to work with PyUp PRs

New page

== Overview ==
PyUp is an automated service, that at it's most basic level, helps developers keep their Python Dependencies always Up-To-Date.
CiDuty will be helping RelOps/RelEng with this weekly actionable (every Wednesday) and making sure that the PR is all green, before merging.
This is an easy process that requires attention and knowledge on how pip is working.

== The 4 pillars of the Task ==
# Review and Fix possible conflicts in the PR.
# Make a list of critical dependencies and/or servers that will be affected.
# Communicate with the repository maintainer(s)
# Merge the PyUp PR and Monitor incoming Puppet mails for issues.

== Important notes to take into account ==
While working on a PyUp PR you always have to take notes and/or ask yourself the following questions:
- Did any signing-server (NOT scriptworkers!) requirements file(s) got changed?
= Yes? ANNOUNCE bhearsum because the signing servers might need to be restarted!
= We don't do merges till Ben gives the green light.
- Did any important deps. got updated?
= Example: Crypthograpy, certifi, anything to do with OAuth, etc.
- Did any MAC machines got requirements file(s) changed?
= Yes? ANNOUNCE bhearsum because the deps might need to be manually downloaded!
- Did any deps upgrades ask for lower version packages?
= Dependiong on which repo, you will have to talk with jlorenzo or bhearsum and see which packages get pinned (locked version)
- When everything is ready to be merged, ALWAYS "Squash and Merge".

== Repositories which we need to activate on ==
# [https://github.com/mozilla-releng/mozilla-version/ Mozilla Version]
# [https://github.com/mozilla-releng/build-puppet/ Build Puppet]

== How To: Mozilla-Version ==
We always start with this repository first because the repository itself is a dependency of Build-Puppet!
# Head to https://github.com/mozilla-releng/mozilla-version/pulls and check if any "Scheduled weekly dependency update for week X" is currently open.
# Verify if the tests are green. Keep in mind that all three checks need to be green:
## Travis CI PR
## Travis CI Push
## Coverage/Coveralls
# If tests are RED head to the build/test and look in the logs for problems.
# Implement the needed changes + commit them (you can do it via github webui). Wait for the test results to come (about 10-15 minutes)
# Squash and Merge the PR.
# Announce JLorenzo that the weekly PR is complete.

=== Common Issues ===
This repository usually has 2 distinct problems which will stop you from merging the PR:
# Requirements of a dependency. Example: flake8 3.5.0 has requirement pycodestyle<2.4.0,>=2.0.0, but you have pycodestyle 2.4.0.
With this issue, you have to keep which deps you have to either manually revert back at the older version (keep in mind you need the old sha512!) or if you pin the version of the dependency.

# Wrong Sha
When a error like this comes:

ERROR: could not install deps [-rrequirements-test.txt]; v = InvocationError('/home/travis/build/mozilla-releng/mozilla-version/.tox/py27/bin/python -m pip install -rrequirements-test.txt (see /home/travis/build/mozilla-releng/mozilla-version/.tox/py27/log/py27-1.log)', 1)

it means the hash=sha512 is wrong. Please contact JLorenzo for a fix/sha string.
== How To: Build-Puppet ==
After you are done with Mozilla-Version, its time for Build-Puppet!
# Head to https://github.com/mozilla-releng/build-puppet/pulls and check if any "Scheduled weekly dependency update for week X" is currently open.
# Verify if the tests are green. Keep in mind that all three checks need to be green:
## Travis CI PR
## Travis CI Push
## TaskCluster (pull_request)
# If tests are RED head to the build/test and look in the logs for problems. In taskcluster, usually the errors are at the bottom.
# Implement the needed changes + commit them (you can do it via github webui). Wait for the test results to come (about 40-60 minutes)
# Squash and Merge the PR.
# Announce Bhearsum that the weekly PR is complete.
=== Common Issues ===
# Requirements of a dependency. Example: flake8 3.5.0 has requirement pycodestyle<2.4.0,>=2.0.0, but you have pycodestyle 2.4.0.
With this issue, you have to keep which deps you have to either manually revert back at the older version (keep in mind you need the old sha512!) or if you pin the version of the dependency.