Closed Bug 1445593 Opened 7 years ago Closed 7 years ago

Factorize common functions defined in *script to scriptworker

Categories

(Release Engineering :: Release Automation: Other, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jlorenzo, Assigned: jlorenzo)

References

Details

Attachments

(12 files)

55 bytes, text/x-github-pull-request
jlorenzo
: review+
jlorenzo
: checked-in+
Details | Review
55 bytes, text/x-github-pull-request
jlorenzo
: review+
jlorenzo
: checked-in+
Details | Review
55 bytes, text/x-github-pull-request
jlorenzo
: review+
jlorenzo
: checked-in+
Details | Review
955 bytes, patch
jlorenzo
: checked-in+
Details | Diff | Splinter Review
55 bytes, text/x-github-pull-request
jlorenzo
: review+
Details | Review
1.51 KB, patch
jlorenzo
: review+
jlorenzo
: checked-in+
Details | Diff | Splinter Review
2.81 KB, patch
jlorenzo
: checked-in+
Details | Diff | Splinter Review
53 bytes, text/x-github-pull-request
jlorenzo
: review+
jlorenzo
: checked-in+
Details | Review
55 bytes, text/x-github-pull-request
jlorenzo
: review+
jlorenzo
: checked-in+
Details | Review
58 bytes, text/x-github-pull-request
jlorenzo
: review+
jlorenzo
: checked-in+
Details | Review
52 bytes, text/x-github-pull-request
jlorenzo
: review+
jlorenzo
: checked-in+
Details | Review
957 bytes, patch
jlorenzo
: checked-in+
Details | Diff | Splinter Review
This will reduce the boilerplate, when we create a new type of scriptwoker instance.
Depends on: 1445676
See Also: → 1443305
@JohanLorenzo Sorry to have stolen this but I wanted to give this a try since I had already `bouncerscript` context and I was working on adding more tests for the configurations. This sort-of was incoming anyway and would've blocked my work there. A word on `load_json`, I moved it from main scripts under tests since it's being used there, but I'll redo the tests to use integration tests instead of local files. You've set some good example in `shiptitscript` repo which I think is way better than what I currently have now. I filed https://github.com/mozilla-releng/bouncerscript/issues/14 to track this later on.
Attachment #8960030 - Flags: review?(jlorenzo)
Before I forget, adding the corresponding puppet patch. NB: Won't deploy this until it's properly tested on maple.
Attachment #8960032 - Flags: review?(jlorenzo)
Attachment #8960032 - Flags: review?(jlorenzo) → review+
Attachment #8960030 - Flags: review?(jlorenzo) → review+
Attachment #8960190 - Attachment is patch: true
Attachment #8960032 - Flags: checked-in+
Was r+'d by Callek at https://github.com/mozilla-releng/treescript/pull/17#pullrequestreview-103917935 Landed on master at https://github.com/mozilla-releng/treescript/commit/8344bcc6861264261da8bf1161c93315a6193481 I didn't release and deploy a new treescript version, because I saw some other changes were ongoing on the master branch. Callek, do you want me to deploy it? Or would you prefer to deal with it later?
Flags: needinfo?(bugspam.Callek)
Attachment #8960203 - Flags: review+
Attachment #8960203 - Flags: checked-in+
All *script were changed but: * addonscript: that's a brand new project which already benefits from the changes * balrogscript: that's a python2.7 project, which doesn't import scriptworker package (yet). Ben, is there a "upgrade to py3" bug that I can point to?
Flags: needinfo?(bhearsum)
(In reply to Johan Lorenzo [:jlorenzo] from comment #13) > Created attachment 8960203 [details] [review] > [treescript] PR: Use functions exposed by scriptwoker.client > > I didn't release and deploy a new treescript version, because I saw some > other changes were ongoing on the master branch. Callek, do you want me to > deploy it? Or would you prefer to deal with it later? Feel free to deploy [with a bumped version]. Thanks!
Flags: needinfo?(bugspam.Callek)
Every script that could be modified was. Let's now close this bug. Please reopen if you experience any issue.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Attachment #8960225 - Attachment is patch: true
(In reply to Johan Lorenzo [:jlorenzo] from comment #14) > All *script were changed but: > * addonscript: that's a brand new project which already benefits from the > changes > * balrogscript: that's a python2.7 project, which doesn't import > scriptworker package (yet). Ben, is there a "upgrade to py3" bug that I can > point to? I'm not really the owner of balrogscript, but I'm guessing it's py2 because it depends on cli.py, which is py2? If so, no bug that I'm aware of. My guess is that we'll end up rewriting cli.py and maybe balrogclient entirely at some point.
Flags: needinfo?(bhearsum)
Thanks! I left details and pointers in balrogscript#7
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: