Hi, > During office hours Oleg said that students are welcome to work on both > new UI and students’ own suggested areas. If the latter is more preferred I > would be glad to focus on it, although, in my view, there are many > interesting core pages, which are already touched by Gus and Tom. >
Yes, students are welcome to propose their own projects or projects based on ideas. In the first case it's highly recommended to find a potential mentor before the application. Org admins will help with it, but it may be complicated if you propose something narrow specific. Kirill's idea regarding credentials UI/UX improvements is definitely interesting. It also fits well into the 2.0 UX scope. But the final decision on the project to apply for is on you. Whatever project you select, we will try to find mentors and to allocate the project slot. Regarding the Travis functionality, there are similar features in Jenkins plugins: - https://wiki.jenkins-ci.org/display/JENKINS/Line+Numbers+Plugin - https://wiki.jenkins-ci.org/display/JENKINS/Rebuild+Plugin - https://wiki.jenkins-ci.org/display/JENKINS/Collapsing+Console+Sections+Plugin - https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin All this stuff can be improved, of course :) BR, Oleg суббота, 12 марта 2016 г., 21:57:48 UTC+3 пользователь Samat Davletshin написал: > > Hello, Kirill! > > Thank you very much for the attention and the feedback! So would you > advise not to touch on the new UI changes? During office hours Oleg said > that students are welcome to work on both new UI and students’ own > suggested areas. If the latter is more preferred I would be glad to focus > on it, although, in my view, there are many interesting core pages, which > are already touched by Gus and Tom. > > > Yes, I would love to work on areas suggested by you! Considering that I am > new to Jenkins, I appreciate pointing to areas to work at. > > > I took a look at *credentials plugin* at "Manage Jenkins" -> "Manage > Credentials". I found this page layout similar to the one of other > configuration pages. So does it have something in common with new > Configuration > page overhaul proposed by Gus in his video > <https://youtu.be/A_lu-P0OhNQ?t=4m53s>? Or do you talk about different > type of change? > > > <https://lh3.googleusercontent.com/-QHM4J0tcpQc/VuRiH31G-1I/AAAAAAAAAMo/3T2v1zsstrI6sj1iqjAjwej6gCenYO9xg/s1600/manage%2Bcredentials.jpg>And > > I am sorry I did not quite get what did you mean in your example. > > Do you mean preselected type of credentials as shown on the first picture? > But what is is the credentials button if front of which selector? I am > sorry for silly questions, just did not use the plugin before. :) > > > > > > > > > > > > > > > > > I took a loot at Travis *build log page*, by building a simple app there. > I think there are indeed a few features that could be useful to Jenkins > users as well. I shown below, I liked the following interface elements: > > <https://lh3.googleusercontent.com/-gdDGvCb99jA/VuRhPnnZFDI/AAAAAAAAAMg/4axC389RcncRSjpO_5txlVgHoMctcQyMA/s1600/travis%2Bbuild%2Blog.jpg>1. > > Numbering the lines (personally, I think this is more convenient than > identifying rows by time stamps as at TeamCity). > 2. Collapsing similar information into one block (I would love this > feature) > 3. Allowing see the row output (what may be liked by those who are used to > Jenkins original interface) > 4. Adding a button to go to the end of the log (as it is often what you > need to do) > 5. Allowing to restart build from the log itself (I personally, while > Jenkins by tutorial, remember myself going back and forth many times to > rebuild a job and then see what went wrong). > > What do you think about it? Is this what you meant? Or there are other > ideas that you had? > > > Please tell me more about what you think could be useful for me to work > at. I want take a closer look at this issues and maybe try improve it in > code. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/08f37877-15ca-4f69-b08c-ce473a6bb6a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
