I am trying to build Apache Nifi locally on my Windows machine by following instructions given here: https://nifi.apache.org/quickstart.html.
Running into the following issue:
Failed to execute goal on project nifi-snmp-nar: Could not resolve dependencies for project org.apache.nifi:nifi-snmp-nar:nar:0.7.0-SNAPSHOT: Could not find artifact org.apache.nifi:nifi-snmp-processors:jar:1.0.0-SNAPSHOT in apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1]
Did anyone come across the same and is there a way to by-pass this?
The SNMP bundle was added to the 0.x branch of Apache NiFi with the versions set at 1.0.0, which is the version on the master branch. I just pushed a commit to the 0.x branch to set the versions to 0.7.0. I was able to do a clean build with an empty Maven repository, let us know if this does not resolve the problem.
Related
Question 1:
i am trying to install Jenkins GitLab Plugin and Jenkins Git Plugin.But in my Jenkins version(2.210) it won't available to download .Can anybody explain any alternative way to download this ?
Question 2 :
I have successfully installed ruby plugin and but still getting same error ?i am configuring Jenkins with windows 10.
Dependency errors:
Some plugins could not be loaded due to unsatisfied dependencies. Fix these issues and restart Jenkins to restore the functionality provided by these plugins.
Gitlab Hook Plugin version 1.4.2
ruby-runtime version 0.12 is missing. To fix, install version 0.12 or later.[enter image description here][1]
I think Jenkins requires plugin https://plugins.jenkins.io/ruby-runtime last version
And you plugin require JRuby 1.7.18
Jenkins (on a Kubernetes node) is complaining it requires a newer version of Jenkins to run some of my plug-ins.
SEVERE: Failed Loading plugin Matrix Authorization Strategy Plugin
v2.4.2 (matrix-auth) java.io.IOException: Matrix Authorization
Strategy Plugin v2.4.2 failed to load.
- You must update Jenkins from v2.121.2 to v2.138.3 or later to run this plugin.
The same log file also complains farther down that it can't read my config file... I'm hoping this is just because of the version issue above, but I'm including it here in case it is a sign of deeper issues:
SEVERE: Failed Loading global config
java.io.IOException: Unable to read /var/jenkins_home/config.xml
I'd either like to disable the plug-ins that are causing the issue so I can see the Jenkins UI and manage the plug-ins from there, or I'd like to update Jenkins in a way that DOES NOT DELETE MY USER DATA AND JOB CONFIG DATA.
So far, I tried disabling ALL the plug-ins by adding .disabled files to the Jenkins plug-ins folder. That got rid of most of the errors, but it still complained about the plug-in above. So I removed the .disabled file for that, and now it's complaining about Jenkins not being a new enough version again (the error above).
Note: this installation of Jenkins is using a persistent storage volume, mounted with EFS. So that will probably help alleviate some of the restrictions around upgrading Jenkins, if that's what we need to do.
Finally, whatever we do with the plug-ins and Jenkins version, I need to make sure the change is going to persist if Kubernetes re-starts the node in the future. Unfortunately, I am pretty unfamiliar with Kubernetes, and I haven't discovered yet where these changes need to be made. I'm guessing the file that controls the Kubernetes deployment configuration?
This project is using Helm, in case that matters. But again, I hardly know anything about Helm, so I don't know what files you might need to see to make this question solvable. Please comment so I know what to include here to help provide the needed information.
We faced the same problem with our cluster, and we have a basic explanation about that, but not sure about it (The following fix works)
That error come with the fact that you have installed Jenkins via Helm, and their plugins through the Jenkins UI. It works if you decide to never reboot the pod, but if one day, jenkins have to make his initialization again, you will face that error.
Jenkins try to load plugins from the JENKINS_PLUGINS_DIR, which is empty, so the pod die.
To fix the current error, you should specify your plugin in the master.installPLugins parameter.
If you followed a normal install, just go on your cluster and
helm get values jenkins_release_name
So you may have something like that:
master:
enableRawHtmlMarkupFormatter: true
installPlugins:
- kubernetes:1.16.0
- workflow-job:2.32
By default, some values are "embedded" by helm to be sure that jenkins works, see here for more details: Github Helm Charts Jenkins
So, just copy it in a file with the same syntax and add your plugins with their versions. After, you have just to use the helm upgrade command with your file on your release:
helm upgrade [RELEASE] [CHART] -f your_file.yaml
Good luck !
I have jenkins job which is checking out the code from SVN repository and run the build but I am getting the multiple or different errors before its checking out the complete code.Please help me.
Error:
ERROR 1: svn: E155021: The path 'D:\Jenkins\workspace\Project1\branch-1.1' appears to be part of a Subversion 1.7 or greater
working copy. Please upgrade your Subversion client to use this
working copy.
org.tmatesoft.svn.core.SVNException: svn: E155021: The path 'D:\Jenkins\workspace\Project\branch-1.1' appears to be part of a Subversion 1.7 or greater
working copy. Please upgrade your Subversion client to use this
working copy.
Error 2:
D:\jenkins\workspace\project\branch.svn\wc.db: The process cannot access the file because it is being used by another process.
Please install Tortoise SVN (It has the cli interface) and add to Windows %PATH%.
I am trying to build my packages using TFS, already integrated with octopus server so that the package can be pulled to octopus server afterwards and get deployed automatically.Created a build definition to build db and windows packages. it goes successful for db however stuck in case of windows where it is supposed to create a release for its deployment.Error -:
There was a problem with your request.
- Release '20170808.12' already exists for this project. Please use a different version, or look at using a mask to auto-increment the number.
Error from Octopus server (HTTP 400 BadRequest)
Could anyone please help me on it....
Thanks in advance !!
You are attempting to a create an Octopus Deploy Release with a name which already exists.
You could adjust your version strategy through AssemblyInfo.cs or adjust Octopus Deploy to not use package names for Releases for under Octopus -> Project -> Settings
Please check if the Release '20170808.12' already exists.
According to the description in this article, it should be an Octopus Deploy issue.
Which version of Octopus Deploy do you use? If you are using the old version, just trying update to the latest version.
In addition, you can try to use below Create release options to check if that works:
--ignoreexisting If a release with the version number already
exists, ignore it
--force [Optional] If a project is configured to skip
packages with already-installed versions,
override this setting to force re-deployment
(flag, default false).
Also try to create a release with a specified release number:
octo create-release --project HelloWorld --version 1.0.3 --server http://octopus/ --apiKey API-ABCDEF123456
See creating-releases for more information.
I have a newly intalled jenkins v 2.36 on ubuntu 14.04 LTS. during the installation process jenkins installed all plugins except pipeline and got stuck on installation. After that i restarted jenkins with
service jenkins restart and was able to create new administrative user, Here is the screen shot of error on jenkins dashboard, the correct button doesnt fix this error.
what should i do to resolve this error ?
The error is
There are dependency errors loading some plugins:
Pipeline: Stage View Plugin v2.4
pipeline-rest-api v2.4 is missing. To fix, install v2.4 or later.
Pipeline v2.4
Pipeline: Stage View Plugin v2.4 failed to load. Fix this plugin first.
It is always good to install the plugin via "Manage Jenkins -> Plugin Manager" , so that the plugin will install its dependencies automatically.
But sometimes due to slow internet connection or other reasons, it fails to do automatically. In that case, we need to do it manually under the Manage Plugins -> Advances Option -> Upload plugin.
So, in your case, it is failing for the below two dependent plugins:
pipeline-rest-api v2.4 is missing. To fix, install v2.4 or later.
Please install the pipeline-rest-api plugin. Also, please install other dependent plugins too for safer side.
List of dependent plugins for any Jenkins plugin.:
https://plugins.jenkins.io/workflow-aggregator
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin
Helpful link jenkins_dependency_error that helped me solve this issue
Download the plugin from here latest pipeline.
Go to jenkins dashboard > Manage jenkins> Manage Plugin > [select Advanced Tab]
select upload plugin file (select the option "restart after installation" )