[JIRA] (JENKINS-57224) Plugin Failed to Initialize after Jenkins restart

2 views
Skip to first unread message

sivakrishnabora@gmail.com (JIRA)

unread,
Apr 29, 2019, 12:23:02 PM4/29/19
to jenkinsc...@googlegroups.com
siva bora created an issue
 
Jenkins / Task JENKINS-57224
Plugin Failed to Initialize after Jenkins restart
Issue Type: Task Task
Assignee: Unassigned
Attachments: copyartifact_plugin.PNG
Components: copyartifact-plugin
Created: 2019-04-29 16:22
Priority: Minor Minor
Reporter: siva bora

Hi, I could see all my copy artifact configurations no longer exist in job configuration. After checking logs, i found the copy artifact plugin did not initialize properly after restart. Please see attached log. After restarting jenkins service, plugin showed back in UI. From logs in could not find any root cause. Is these kind of initialization issues happen? If so, what might be general cause for this.

 

SEVERE: Failed Initializing plugin copyartifact

Copy Artifact Plugin version - 1.30

Jenkins version - v2.121.3

 

Please let me know for any additional information.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

devld@ikedam.jp (JIRA)

unread,
May 10, 2019, 11:40:02 PM5/10/19
to jenkinsc...@googlegroups.com
ikedam updated Task JENKINS-57224
 

Actually, the root cause of this issue is unknown at last.
It looks related to processing of Jenkins core in boot time, and cannot be reproduce in my environment.
Though, I updated the implementation looking related to this issue in copyartifact-1.39 and should be fixed.
https://github.com/jenkinsci/copyartifact-plugin/commit/946f9e47059cede6a6b50934f86efca42b574e05#diff-a1fdcd3da2dbec876fd20075be0d4108

You’re using a really old version of copyartifact, and please update to the latest and see the problem is resolved.

Change By: ikedam
Status: Open Fixed but Unreleased
Assignee: siva bora
Resolution: Fixed
Released As: copyartifact-1.39
Reply all
Reply to author
Forward
0 new messages