Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable synchronization of labels #7

Open
fraga opened this issue Mar 1, 2014 · 4 comments
Open

Enable synchronization of labels #7

fraga opened this issue Mar 1, 2014 · 4 comments

Comments

@fraga
Copy link
Owner

fraga commented Mar 1, 2014

implement labels synchronization

@fraga
Copy link
Owner Author

fraga commented Jul 10, 2014

moved to 1.1.3

@fraga fraga modified the milestones: Version 1.1.3, Version 1.1.2 Jul 10, 2014
@fraga
Copy link
Owner Author

fraga commented Mar 25, 2015

This one is tough in a sense that today when developing in a team, the label gets created when code is checked in on the server.

Trying to check if git hooks could work

@weedgarden
Copy link

At the moment we thought about resolving this issue using separate label id limits. Anyway, that's not the transparent solution you would probably like to achieve - needs setting of every client app to avoid collision.

@fraga
Copy link
Owner Author

fraga commented Mar 25, 2015

Yeah good solution.

Imagine that if we have a designated build server it could serve label
id values.

Did you create objects (parameters, etc) to support that range in each box
and are your labels being merged and working?
On Mar 25, 2015 5:58 AM, "Vit Zahradka" [email protected] wrote:

At the moment we thought about resolving this issue using separate label
id limits. Anyway, that's not the transparent solution you would probably
like to achieve - needs setting of every client app to avoid collision.


Reply to this email directly or view it on GitHub
#7 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants