UI changes branch progress report Day 1

[Kohsuke Kawaguchi]

I'm going to spend the rest of the week focusing on working with Gus and Tom to get the proposed UI changes into a mergeable state.

The tasks are tracked in here during this three days.

We'll be on hangout from 1pm-5pm pacific time at http://bit.ly/1RSkY1i if anyone else is interested in chiming in.

So far I've done the following:

• Built Maven artifacts versions of Node.js and NPM, which is not a part of the build time dependency at here. This was originally done by James, I think.
• Tom had packaged various JavaScript libraries as Jenkins plugins. I've moved them over to here.
• The proposed WiP branch for config UI changes is moved to here so that we can all commit directly into this branch. I've made some changes so that this branch builds for me on Linux.
• I started looking at form taglibs and fix form submission problems. I've completed <f:optionalBlock> and that made a big difference.

As Tom was saying, it's good to write more tests for the form tag libs (they are in test/java/lib/form/*Test) in the master to capture the current behavior, and use them to verify that the branch didn't break this behaviour. I added one for <f:rowSet>

Then I discovered that unit tests fail left and right for the branch, and now it makes sense to me why he told me we need to upgrade htmlunit. I haven't looked into that yet, I'm hoping that Tom can make some progress before I wake up tomorrow.

There are still various UI glitches in this branch that Gus is tackling independently.

So that's the progress report of Day 1.

--

Kohsuke Kawaguchi

[Kanstantsin Shautsou]

Branch changes as PR https://github.com/jenkinsci/jenkins/pull/1772

Kohsuke, i also reviewed branches in jenkinsci and found:

1) https://github.com/jenkinsci/jenkins/tree/ui-changes - is ohtake still active? Could he join your work?

2) https://github.com/jenkinsci/jenkins/tree/grunt - is it still needed?

3) https://github.com/jenkinsci/jenkins/tree/yui3 - you really need it to keep?

4) https://github.com/jenkinsci/jenkins/commits/animated-build-queue

5) any other known ?

[Kanstantsin Shautsou]

On Thursday, July 23, 2015 at 5:45:06 PM UTC+3, Kohsuke Kawaguchi wrote:

The tasks are tracked in here during this three days.

I remember that you someday said that you want prohibit using GH issues/wiki for plugin developers.

Could you use jenkins infra (wiki/jira) so "Jenkins Project" and "Jenkins Community" will have history of UI redesign work when trello or google docs dead?

Hing: you can install additional plugins in jira.

Good example of well tracked work https://wiki.jenkins-ci.org/display/JENKINS/Designing+pre-tested+commit 

Thanks

[Kirill Merkushev]

can you build additional docker container or/and jenkins instance with ability to view configuration, but without ability to do build and save something for new UI changes? To view and test latest version?

четверг, 23 июля 2015 г., 17:45:06 UTC+3 пользователь Kohsuke Kawaguchi написал:

[Suckow, Thomas J]

Getting "The party is over"

From: <jenkin...@googlegroups.com>
Subject: UI changes branch progress report Day 1

We'll be on hangout from 1pm-5pm pacific time at http://bit.ly/1RSkY1i if anyone else is interested in chiming in.

--

Kohsuke Kawaguchi

[Suckow, Thomas J]

Nevermind, working now.

[Tom Fennelly]

What was the progress from last night guys? KK, did you come to any conclusions on HtmlUnit?

[Oleg Nenashev]

Could you use jenkins infra (wiki/jira) so "Jenkins Project" and "Jenkins Community" will have history of UI redesign work when trello or google docs dead?

+1. It should be enough if you put links to Trello and Google docs somewhere on Wiki.

пятница, 24 июля 2015 г., 9:41:16 UTC+3 пользователь Tom Fennelly написал:

[Kanstantsin Shautsou]

No, it shouldn't be enough, because all work activity will be lost and not saved in _project_ infra.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/tXgC5m-Ggz0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/eaeae81d-4433-468e-9332-c014e148ed4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.