lp:~jocave/checkbox/+git/support

Owned by Jonathan Cave
Get this repository:
git clone https://git.not.enabled/~jocave/checkbox/+git/support
Only Jonathan Cave can upload to this repository. If you are Jonathan Cave please log in for upload directions.

Branches

Name Last Modified Last Commit
print-exception 2021-11-11 10:52:38 UTC
Change: print all exceptions

Author: Jonathan Cave
Author Date: 2021-11-11 10:52:38 UTC

Change: print all exceptions

use-requestBuildsCall 2021-11-09 09:30:43 UTC
Change: use new requestsBuilds API

Author: Jonathan Cave
Author Date: 2021-11-09 09:30:43 UTC

Change: use new requestsBuilds API

Allows not specifying series/arch and hence builders infer from
snapcraft.yaml which allows use of ESM repos

use-python3 2021-09-08 11:16:34 UTC
Change: use python3 in all scripts

Author: Jonathan Cave
Author Date: 2021-09-08 11:13:25 UTC

Change: use python3 in all scripts

dont-limit-snapcraft-channels 2021-08-20 08:47:46 UTC
Change: allow passing full track/risk/branch

Author: Jonathan Cave
Author Date: 2021-08-20 08:47:46 UTC

Change: allow passing full track/risk/branch

Snaps channels grew support for tracks and branches which
snapcraft is no using. Don't limit choices available to accomadate
any possible combination.

limit-output-to-pastebin 2021-04-21 09:49:05 UTC
Change: limit amount of output sent to pastebin

Author: Jonathan Cave
Author Date: 2021-04-21 09:49:05 UTC

Change: limit amount of output sent to pastebin

If the output file gets to large then the attempt to send to the
pastebin will fail and we get no info. Limit to some reasonable
number of lines.

test-lxc-focal 2020-05-22 11:07:15 UTC
test-in-lxc: add focal to target list

Author: Jonathan Cave
Author Date: 2020-05-22 11:07:15 UTC

test-in-lxc: add focal to target list

use-snapcraft-snap 2020-01-28 10:56:14 UTC
lp-snap-build: use snapcraft snap for builds

Author: Jonathan Cave
Author Date: 2020-01-28 10:56:14 UTC

lp-snap-build: use snapcraft snap for builds

Currently it is necessary to specify use of the snapcraft snap
when triggering using lplib even when this is set in the builder
ui. lp:1791269

always-push-to-ssh 2019-09-25 13:57:01 UTC
release_content_snap: push to git+ssh scheme

Author: Jonathan Cave
Author Date: 2019-09-24 17:20:14 UTC

release_content_snap: push to git+ssh scheme

url-mod-only-on-ssh 2019-09-24 15:41:24 UTC
release_content_snap: add user only on git+ssh

Author: Jonathan Cave
Author Date: 2019-09-24 15:41:24 UTC

release_content_snap: add user only on git+ssh

Only modify the target URL for tag pushes when the scheme is
git+ssh.

parts-in-private-proj 2019-09-11 10:31:44 UTC
release_content_snap: support push to private part

Author: Jonathan Cave
Author Date: 2019-09-10 16:28:02 UTC

release_content_snap: support push to private part

Some snaps have parts (usually providers) that are in private
projects. A complete url is needed including username to be
able to push the tags created back there.

ignore-librealsense-part 2019-09-06 15:46:05 UTC
release_content_snap: ignore librealsense

Author: Jonathan Cave
Author Date: 2019-09-06 15:46:05 UTC

release_content_snap: ignore librealsense

request-exact-branch 2019-09-04 17:09:47 UTC
lp-propose-merge: only match exact branch name

Author: Jonathan Cave
Author Date: 2019-09-04 17:09:47 UTC

lp-propose-merge: only match exact branch name

Only trigger a merge when the target-branch and propsed-branch
are specified exactly in the arguments i.e. dont treat the
args as substrings

support-project-snap-release 2019-08-29 09:43:30 UTC
release: reduce path operations in release script

Author: Jonathan Cave
Author Date: 2019-08-29 09:33:38 UTC

release: reduce path operations in release script

Make it easier to follow the script by doing the path operations
during init

print-similarities 2017-06-13 08:37:29 UTC
Print id clashes

Author: Jonathan Cave
Author Date: 2017-06-13 08:37:29 UTC

Print id clashes

114 of 14 results
This repository contains Public information 
Everyone can see this information.

Subscribers