[JIRA] (JENKINS-61134) Unable to select all plugins for update

22 views
Skip to first unread message

chig@dickinson.edu (JIRA)

unread,
Feb 18, 2020, 2:45:03 PM2/18/20
to jenkinsc...@googlegroups.com
Allan C created an issue
 
Jenkins / Improvement JENKINS-61134
Unable to select all plugins for update
Issue Type: Improvement Improvement
Assignee: Unassigned
Components: core
Created: 2020-02-18 19:44
Environment: (Jenkins 2.204.2)

The following variables are available to shell scripts

BRANCH_NAME
    For a multibranch project, this will be set to the name of the branch being built, for example in case you wish to deploy to production from master but not from feature branches; if corresponding to some kind of change request, the name is generally arbitrary (refer to CHANGE_ID and CHANGE_TARGET).
CHANGE_ID
    For a multibranch project corresponding to some kind of change request, this will be set to the change ID, such as a pull request number, if supported; else unset.
CHANGE_URL
    For a multibranch project corresponding to some kind of change request, this will be set to the change URL, if supported; else unset.
CHANGE_TITLE
    For a multibranch project corresponding to some kind of change request, this will be set to the title of the change, if supported; else unset.
CHANGE_AUTHOR
    For a multibranch project corresponding to some kind of change request, this will be set to the username of the author of the proposed change, if supported; else unset.
CHANGE_AUTHOR_DISPLAY_NAME
    For a multibranch project corresponding to some kind of change request, this will be set to the human name of the author, if supported; else unset.
CHANGE_AUTHOR_EMAIL
    For a multibranch project corresponding to some kind of change request, this will be set to the email address of the author, if supported; else unset.
CHANGE_TARGET
    For a multibranch project corresponding to some kind of change request, this will be set to the target or base branch to which the change could be merged, if supported; else unset.
BUILD_NUMBER
    The current build number, such as "153"
BUILD_ID
    The current build ID, identical to BUILD_NUMBER for builds created in 1.597+, but a YYYY-MM-DD_hh-mm-ss timestamp for older builds
BUILD_DISPLAY_NAME
    The display name of the current build, which is something like "#153" by default.
JOB_NAME
    Name of the project of this build, such as "foo" or "foo/bar".
JOB_BASE_NAME
    Short Name of the project of this build stripping off folder paths, such as "foo" for "bar/foo".
BUILD_TAG
    String of "jenkins-${JOB_NAME}-${BUILD_NUMBER}". All forward slashes ("/") in the JOB_NAME are replaced with dashes ("-"). Convenient to put into a resource file, a jar file, etc for easier identification.
EXECUTOR_NUMBER
    The unique number that identifies the current executor (among executors of the same machine) that’s carrying out this build. This is the number you see in the "build executor status", except that the number starts from 0, not 1.
NODE_NAME
    Name of the agent if the build is on an agent, or "master" if run on master
NODE_LABELS
    Whitespace-separated list of labels that the node is assigned.
WORKSPACE
    The absolute path of the directory assigned to the build as a workspace.
JENKINS_HOME
    The absolute path of the directory assigned on the master node for Jenkins to store data.
JENKINS_URL
    Full URL of Jenkins, like http://server:port/jenkins/ (note: only available if Jenkins URL set in system configuration)
BUILD_URL
    Full URL of this build, like http://server:port/jenkins/job/foo/15/ (Jenkins URL must be set)
JOB_URL
    Full URL of this job, like http://server:port/jenkins/job/foo/ (Jenkins URL must be set)
GIT_COMMIT
    The commit hash being checked out.
GIT_PREVIOUS_COMMIT
    The hash of the commit last built on this branch, if any.
GIT_PREVIOUS_SUCCESSFUL_COMMIT
    The hash of the commit last successfully built on this branch, if any.
GIT_BRANCH
    The remote branch name, if any.
GIT_LOCAL_BRANCH
    The local branch name being checked out, if applicable.
GIT_URL
    The remote URL. If there are multiple, will be GIT_URL_1, GIT_URL_2, etc.
GIT_COMMITTER_NAME
    The configured Git committer name, if any, that will be used for FUTURE commits from the current workspace. It is read from the Global Config user.name Value field of the Jenkins Configure System page.
GIT_AUTHOR_NAME
    The configured Git author name, if any, that will be used for FUTURE commits from the current workspace. It is read from the Global Config user.name Value field of the Jenkins Configure System page.
GIT_COMMITTER_EMAIL
    The configured Git committer email, if any, that will be used for FUTURE commits from the current workspace. It is read from the Global Config user.email Value field of the Jenkins Configure System page.
GIT_AUTHOR_EMAIL
    The configured Git author email, if any, that will be used for FUTURE commits from the current workspace. It is read from the Global Config user.email Value field of the Jenkins Configure System page.
MERCURIAL_REVISION
    Full ID of revision checked out.
MERCURIAL_REVISION_SHORT
    Abbreviated ID of revision checked out.
MERCURIAL_REVISION_NUMBER
    Number of revision checked out (not portable across clones).
MERCURIAL_REVISION_BRANCH
    Branch of revision checked out, if not checking out by branch head.
MERCURIAL_REPOSITORY_URL
    URL of repository.
SVN_REVISION
    Subversion revision number that's currently checked out to the workspace, such as "12345"
SVN_URL
    Subversion URL that's currently checked out to the workspace.
Labels: jenkins user-experience newbie-friendly
Priority: Minor Minor
Reporter: Allan C

I am unable to update all the plugins all at once with "select all" function. This issues was  reported years ago and was fixed. It showed up again in the current Jenkins. Can someone replicate and confirm this problem?

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

chig@dickinson.edu (JIRA)

unread,
Feb 18, 2020, 2:46:02 PM2/18/20
to jenkinsc...@googlegroups.com
Allan C assigned an issue to Allan C
Change By: Allan C
Assignee: Allan C

chig@dickinson.edu (JIRA)

unread,
Feb 18, 2020, 2:46:02 PM2/18/20
to jenkinsc...@googlegroups.com
Allan C updated an issue
Change By: Allan C
Attachment: image.png

chig@dickinson.edu (JIRA)

unread,
Feb 18, 2020, 2:47:02 PM2/18/20
to jenkinsc...@googlegroups.com

dbeck@cloudbees.com (JIRA)

unread,
Feb 26, 2020, 6:21:03 AM2/26/20
to jenkinsc...@googlegroups.com

What happens instead? Note that the links are below the list, so you need to scroll down.

chig@dickinson.edu (JIRA)

unread,
Feb 26, 2020, 7:54:02 AM2/26/20
to jenkinsc...@googlegroups.com
Allan C commented on Improvement JENKINS-61134

Daniel Beck To update all the plugins, I need to manually select/check each of them and click "Download Now and install after restart," Am I missing something here?

dbeck@cloudbees.com (JIRA)

unread,
Feb 26, 2020, 10:28:07 AM2/26/20
to jenkinsc...@googlegroups.com

Scroll down on this page (possibly only when there are any available updates). There's a line below the table that says something like "Select All None Compatible" with clickable links.

chig@dickinson.edu (JIRA)

unread,
Feb 26, 2020, 10:37:03 AM2/26/20
to jenkinsc...@googlegroups.com
Allan C commented on Improvement JENKINS-61134

Daniel Beck Appreciate the instruction and sorry for not checking carefully. I am attaching a screenshot and closing this issue. Would it be nice to add a "select all" checkbox on top of the menu though?

chig@dickinson.edu (JIRA)

unread,
Feb 26, 2020, 10:37:03 AM2/26/20
to jenkinsc...@googlegroups.com
Allan C updated an issue
Change By: Allan C
Attachment: image-2020-02-26-10-36-41-292.png

chig@dickinson.edu (JIRA)

unread,
Feb 26, 2020, 10:38:05 AM2/26/20
to jenkinsc...@googlegroups.com
Allan C closed an issue as Not A Defect
 

Change By: Allan C
Status: Open Closed
Resolution: Not A Defect

dbeck@cloudbees.com (JIRA)

unread,
Feb 26, 2020, 10:56:03 AM2/26/20
to jenkinsc...@googlegroups.com

Would it be nice to add a "select all" checkbox on top of the menu though?

Potentially nontrivial from a UI standpoint, given how the tabs flow into the table header (I'm not much of a designer anyway). I think it might be more useful to add these to the floating pane perhaps at the bottom? If you want to try your hand at a proposal here, go for it

chig@dickinson.edu (JIRA)

unread,
Feb 26, 2020, 11:12:06 AM2/26/20
to jenkinsc...@googlegroups.com
Allan C commented on Improvement JENKINS-61134

I think it might be more useful to add these to the floating pane perhaps at the bottom?

 
Daniel Beck Thank you for the idea. I agree that moving the Select before "Download now and install after restart" button may make it more obvious. I will try looking into it. Do you know about any documentation about the core UI? Or should I reach out to someone? Thanks.

 

Reply all
Reply to author
Forward
0 new messages