Lukas Blakk [:lsblakk] use ?needinfo Reporter
	Description • 14 years ago

Esp. with more project branches coming, users should be able to push to try and specify a url of the hg repo to use.

	bhearsum@mozilla.com (:bhearsum)
	Comment 1 • 14 years ago

Why can't they just push their user repo to ssh://hg.mozilla.org/try?

	Lukas Blakk [:lsblakk] use ?needinfo Reporter
	Comment 2 • 14 years ago

Fixing the summary, there was some misunderstanding of what the intent of this feature is.

	Justin Wood (:Callek)
	Comment 3 • 13 years ago

(In reply to Lukas Blakk [:lsblakk] from comment #2)
> Fixing the summary, there was some misunderstanding of what the intent of
> this feature is.

Can you try explaining it better (for me) if this is still valid?

(In reply to Ben Hearsum [:bhearsum] from comment #1)
> Why can't they just push their user repo to ssh://hg.mozilla.org/try?

I would think pushing to try from a user repo would still suffice.

	bhearsum@mozilla.com (:bhearsum)
	Comment 4 • 13 years ago

I'm still not sure why people can't just push to try.

	Aki Sasaki (not active)
	Comment 5 • 13 years ago

We currently don't have a way to make Try anywhere near performant over time; this would avoid the whole "try is slow again" set of bugs.

	Lukas Blakk [:lsblakk] use ?needinfo Reporter
	Comment 6 • 13 years ago

(In reply to Justin Wood (:Callek) from comment #3)
> Can you try explaining it better (for me) if this is still valid?
> 
 As Aki mentions, the difference is in the push/pull.  Users can already push the contents of their user repo to try but that does run up against the 'try is slow' issue that comes up once every couple of months due to accumulation of heads.  Being able to ask the try builders to *pull* from a user-specified repo that is _not_ the hg.m.o/try repo is the goal of this bug.

	Justin Wood (:Callek)
	Comment 7 • 13 years ago

(In reply to Lukas Blakk [:lsblakk] from comment #6)
> (In reply to Justin Wood (:Callek) from comment #3)
> > Can you try explaining it better (for me) if this is still valid?
> > 
>  As Aki mentions, the difference is in the push/pull.  Users can already
> push the contents of their user repo to try but that does run up against the
> 'try is slow' issue that comes up once every couple of months due to
> accumulation of heads.  Being able to ask the try builders to *pull* from a
> user-specified repo that is _not_ the hg.m.o/try repo is the goal of this
> bug.

Do we have some sort of design doc/plan for how this would look from the user-perspective side of this coin. I really suspect that anything other than "push to try" would be restrictive to our users. We used to have a web-app that handled this concept, but we retired it in favor of the current method when it was deemed much better.

I wonder if we can get around the "try is slow" problem much better by designing a weekly-run builder that closes old heads on try, if they haven't had a push on them in 1month prior, or something....

	Aki Sasaki (not active)
	Comment 8 • 13 years ago

(In reply to Justin Wood (:Callek) from comment #7)
> Do we have some sort of design doc/plan for how this would look from the
> user-perspective side of this coin. I really suspect that anything other
> than "push to try" would be restrictive to our users. We used to have a
> web-app that handled this concept, but we retired it in favor of the current
> method when it was deemed much better.
> 
> I wonder if we can get around the "try is slow" problem much better by
> designing a weekly-run builder that closes old heads on try, if they haven't
> had a push on them in 1month prior, or something....

Patches accepted.

Also, this nicely works around the MAX_BROKER_REFS "feature" by avoiding spinning up new twigs for things that can be handled by running try builds on a user repo.

	Armen [:armenzg]
	Comment 9 • 13 years ago

With talos.json I managed to specify a step on the fly.

If we had a json file to indicate which user repos to look for changes we could have a multi repo poller that triggers build on just one buildbot branch.
We have a MultiLocalePoller that reads which locales from all-locales on the fly.

I hope it helps.

	Lukas Blakk [:lsblakk] use ?needinfo Reporter
	Comment 10 • 13 years ago

(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #9)
> With talos.json I managed to specify a step on the fly.
> 
> If we had a json file to indicate which user repos to look for changes we
> could have a multi repo poller that triggers build on just one buildbot
> branch.
> We have a MultiLocalePoller that reads which locales from all-locales on the
> fly.
> 
> I hope it helps.

I'm thinking more that this could be another extension of trychooser syntax where you can specify an hg.mozilla.org repo and (optionally) an ftp upload dir (otherwise builds end up in the try-builds default dir).

	bhearsum@mozilla.com (:bhearsum)
	Comment 11 • 11 years ago

Does anyone still care about this?

	Aki Sasaki (not active)
	Comment 12 • 11 years ago

It would allow us to reduce/get rid of the Try repo with its head pruning issues.

	Chris Cooper [:coop] (he/him)
	Comment 13 • 10 years ago

There's also an initiative now to get rid of user repos.