1240018 - [taskcluster-vcs] Remove unnecessary cached repos

Status: RESOLVED FIXED

(Taskcluster :: General, defect)

Description

[Greg Arndt [:garndt]]

Currently there are a few source manifests that are being cached by tc-vcs but they have been failing for some time now.

IN bug 1238778 it was determined that dolphin-512 could be removed, however there are a few other ones that perhaps could be removed as well. 

I could not find these being used in production, but I might be overlooking something.  The ones used in the jobs I found on treeherder seemed to be using our in-tree manifests under b2g/config/<device>

https://raw.githubusercontent.com/mozilla-b2g/b2g-manifest/master/emulator-kk.xml
https://raw.githubusercontent.com/mozilla-b2g/b2g-manifest/master/emulator-l.xml
https://raw.githubusercontent.com/mozilla-b2g/b2g-manifest/master/emulator-jb.xml
https://raw.githubusercontent.com/mozilla-b2g/b2g-manifest/master/emulator.xml

Comment 1

[Greg Arndt [:garndt]]

Do you know if these are used anywhere?  Our caching jobs have been failing on them because of some issues with how large the entire repos are once sycned, so it makes me believe that things are not using it in production but I might be mistaken.

Comment 2

[Mahendra Potharaju [:mahe]]

Am not sure if these are in use or obsolete. I haven't had enough work with Emulators usage and their life cycle yet. 

Josh/Julie might be able to help.

Comment 3

[Edgar Chen [:edgar]]

Although we don't run any test on them, we still need them for building to ensue gecko compatibility with different AOSP HAL version.

Comment 4

[Greg Arndt [:garndt]]

I'm not proposing that remove them from the github repo, but currently they are not used in our production jhobs that I see on treeherder so I was wondering that if the for the time being we stopped trying to cache them as if they were used in production.

When they are used for building, how do they get used? Something locally? In production?

Comment 5

[Edgar Chen [:edgar]]

(In reply to Greg Arndt [:garndt] from comment #4)
> I'm not proposing that remove them from the github repo, but currently they
> are not used in our production jhobs that I see on treeherder so I was
> wondering that if the for the time being we stopped trying to cache them as
> if they were used in production.
> 
> When they are used for building, how do they get used? Something locally? In
> production?

They are used for building locally.

Comment 6

[Greg Arndt [:garndt]]

Spoke with Edgar on IRC, and I just wanted to clarify here that this doesn't mean the manifests would be removed from github.  This would only affect the use of tc-vcs for cloning repos.

For building locally, if tc-vcs is not used for checking out the sources, then this change would not matter.

The purpose of this bug was to determine if any production jobs that use tc-vcs are referencing one of the manifests in github, which it appears that it's not.  I vote that as far as tc-vcs is concerned, we stop looking at those manifests.

Comment 7

[Greg Arndt [:garndt]]

Attachment: tc-vcs PR 51

Please see comments in the bug regarding removing them from use with tc-vcs (it appears that these manifests are only used for building locally)

Comment 8

[[github robot]]

Commit pushed to master at https://github.com/taskcluster/taskcluster-vcs

https://github.com/taskcluster/taskcluster-vcs/commit/21d6b55d70c1f5435daf16c45095d7da95ff6567
Merge pull request #51 from taskcluster/gregarndt-patch-1

Bug 1240018 - Remove repos that cannot be cached