Beginner interface to Jenkins plugin management

[Arun Gupta]

Downloaded the latest Jenkins and its amazing that is now version 598. I still remember the two digit build numbers :)

Found couple of usability issues regarding plugins:

- The default tab shown is "Updates" and is shown empty. I switched to Available tab, searched on "pipeline" and it showed no results and then switched back to Updates tab. Now there is a much bigger list of plugins shown that can be updated. This is a fresh install of Jenkins and run using "java -jar jenkins.war". How does it find out those updates are required?

The snapshot with the list of plugins is attached.

- I clicked on "All" and installed all the plugins. Seems like none of the plugins were existing earlier and now will be activated after Jenkins is restarted. This is shown in the second attachment. 

This seems rather intrusive.

If the expected flow is for the user to update all the plugins, a single button that enables all that would be useful.

- Now when I click on Available tabs and search for pipeline, it starts showing up. Why would I do "Install without restart"?

Cheers

Arun

[Ulli Hafner]

Am 04.02.2015 um 09:41 schrieb Arun Gupta <arun....@gmail.com>:

Downloaded the latest Jenkins and its amazing that is now version 598. I still remember the two digit build numbers :)

Found couple of usability issues regarding plugins:

You are right, the usability of the update manager could be improved. Feel free to create a new Jira issue with the label user-experience

- The default tab shown is "Updates" and is shown empty. I switched to Available tab, searched on "pipeline" and it showed no results and then switched back to Updates tab. Now there is a much bigger list of plugins shown that can be updated. This is a fresh install of Jenkins and run using "java -jar jenkins.war". How does it find out those updates are required?

The list of updates is created asynchronously, so you need to wait a while until something new is visible. 

The snapshot with the list of plugins is attached.

- I clicked on "All" and installed all the plugins. Seems like none of the plugins were existing earlier and now will be activated after Jenkins is restarted. This is shown in the second attachment. 

This seems rather intrusive.

If the expected flow is for the user to update all the plugins, a single button that enables all that would be useful.

I think there is already such a request. If not please create one. 

- Now when I click on Available tabs and search for pipeline, it starts showing up. Why would I do "Install without restart“?

I don’t follow you here, what should be improved here?

Cheers

Arun

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5d76a212-3bc4-4fc8-8575-7ca5063d7028%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Arun Gupta]

Wondering why there is a separate JIRA as opposed to github issues
itself? This feels disconnected.

> You received this message because you are subscribed to a topic in the

> Google Groups "Jenkins Users" group.

> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/G0q-f7yTXzA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to

> jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/jenkinsci-users/6B80B77A-540A-471B-8F5D-B61AE24AF76D%40gmail.com.

> For more options, visit https://groups.google.com/d/optout.

--
http://blog.arungupta.me
http://twitter.com/arungupta

[Daniel Beck]

On 05.02.2015, at 23:44, Arun Gupta <arun....@gmail.com> wrote:

> Wondering why there is a separate JIRA as opposed to github issues
> itself? This feels disconnected.

Off the top of my head:
- Jira allows reassigning components when it turns out that a bug is the responsibility of another component
- Jira is the one location users can go to report issues they experience for (almost) all plugins
- Use of Jira predates use of Github by the Jenkins project
- Jira allows use of a separate private project for reporting security issues that can still be linked to regular issues
- Jira allows issues to span multiple components
- Jira isn't a thousand separate trackers that make e.g. triaging incoming reports across a number of components, to ensure they have merit and aren't duplicates, almost impossible
- We still have plugins in Subversion that need an issue tracker as well
- There are even plugins that use neither Subversion nor Github to store their code but may want to integrate with Jenkins project's bug tracking

The only thing really wrong with the current system is that some plugins use Github issues (presumably due to personal preference, but I don't know) when it actually only hurts in the overall project context, as it disconnects that specific plugin from what most others are using.

[Arun Gupta]

Filed the issue:

https://issues.jenkins-ci.org/browse/INFRA-232

On Wed, Feb 4, 2015 at 3:37 AM, Ulli Hafner <ullrich...@gmail.com> wrote:
>

> You received this message because you are subscribed to a topic in the

> Google Groups "Jenkins Users" group.

> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/G0q-f7yTXzA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to

> jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/jenkinsci-users/6B80B77A-540A-471B-8F5D-B61AE24AF76D%40gmail.com.

> For more options, visit https://groups.google.com/d/optout.