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

Auto-refresh build logs #1244

Open
g4s8 opened this issue Jan 26, 2018 · 19 comments
Open

Auto-refresh build logs #1244

g4s8 opened this issue Jan 26, 2018 · 19 comments
Labels
Milestone

Comments

@g4s8
Copy link
Contributor

g4s8 commented Jan 26, 2018

Let's add auto-refrsh feature for build logs, like in Travis

@0crat
Copy link
Collaborator

0crat commented Jan 26, 2018

@yegor256/z please, pay attention to this issue

@yegor256
Copy link
Owner

@g4s8 but it works exactly that way now. If you open log page, the text will be loaded in runtime, coming from the server. Or it doesn't?

@g4s8
Copy link
Contributor Author

g4s8 commented Feb 6, 2018

@yegor256 no, at moment you need to refresh the page manually to see new logs

tested on this log: http://www.rultor.com/t/13834-363483177
in two different browsers (Firefox and Chrome)
Rultor's version is 1.67

@yegor256 yegor256 added the bug label Feb 12, 2018
@0crat 0crat added the scope label Feb 12, 2018
@0crat
Copy link
Collaborator

0crat commented Feb 12, 2018

Job #1244 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Feb 12, 2018

The job #1244 assigned to @filfreire/z, here is why. The budget is 30 minutes, see §4. Please, read §8 and §9. If the task is not clear, read this and this.

@0crat
Copy link
Collaborator

0crat commented Feb 17, 2018

@filfreire/z this job was assigned to you 5 days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

@0crat
Copy link
Collaborator

0crat commented Feb 20, 2018

@filfreire/z this job was assigned to you 8 days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

@0crat
Copy link
Collaborator

0crat commented Feb 22, 2018

The user @filfreire/z resigned from #1244, please stop working

@0crat
Copy link
Collaborator

0crat commented Feb 22, 2018

Resigned on delay, see §8: -30 points just awarded to @filfreire/z, total is +525

@0crat
Copy link
Collaborator

0crat commented Apr 12, 2018

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

@0crat
Copy link
Collaborator

0crat commented Apr 17, 2018

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

@0crat
Copy link
Collaborator

0crat commented Apr 23, 2018

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

@yegor256
Copy link
Owner

@0crat out

@0crat
Copy link
Collaborator

0crat commented Apr 23, 2018

@0crat out (here)

@yegor256 GitHub issue is still open, won't close

@0crat
Copy link
Collaborator

0crat commented Apr 28, 2018

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented May 3, 2018

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@yegor256
Copy link
Owner

yegor256 commented May 6, 2018

@0crat out

@llorllale
Copy link

@yegor256 I'm wondering why you want to exclude this feature request from scope? Would be nice to have...

@0crat 0crat removed the scope label May 12, 2018
@0crat
Copy link
Collaborator

0crat commented May 12, 2018

@0crat out (here)

@yegor256 The job #1244 is now out of scope

@yegor256 yegor256 added this to the next milestone Nov 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants