The Grails Plugins site only seems to list the latest versions of all the Grails plugins. But what if I wanted to see a list of other available (older) versions for each plugin? Is there a Grails SDK command/target I can issue to see old plugins?
I ask because I'm using a plugin whose current latest release is broke and its version is "2.0-RC2". Since it's a release candidate, I'd like to know what the last stable (non-RC) version is.
You can see the plugins at the main repo site here. The site is referenced via grailsCentral() in the BuildConfig.groovy file which in turn references the repo site in the org.codehaus.groovy.grails.resolve.maven.aether.config.RepositoriesConfiguration.groovy file
There is no such command to see old plugins.
If you are referring to Spring Security Core plugin then corresponding github repository has two branches:
master referring to 2.0-RC2 and 1.x referring to the last stable release 1.2.7.3.
On a side note, if you want to see all installed plugins with their versions then below command can be issued:
grails list-plugins --installed
Related
After moving Jenkins to a new computer I cannot upgrade plugins since it thinks the new version is older than the installer.
I get the following message:
Some plugins could not be loaded due to unsatisfied dependencies. Fix these issues and restart Jenkins to re-enable these plugins.
Dependency errors:
Static Analysis Utilities (1.96)
Update required: Maven Integration plugin (2.12.1) to be updated to 2.17 or higher
Update required: Matrix Project Plugin (1.6) to be updated to 1.7.1 or higher
Update required: OWASP Markup Formatter Plugin (1.3) to be updated to 1.5 or higher
and several more.
I then try to upgarde Maven INtegration polugin (and alla others) it looks like the are installed and Jenkins is restarted. But I get the same error again.
When looking in the plugin folder I see that I have several version of the plugin. I try to remove the different folders and then detect that the old verision is still used even if the new version is available in the folder.
In the pluginmanager/installed the Maven Integration plugin is listed as version 2.12.1 and the possibility to DOWNGRADE to 3.8. 3.8 is the version that I upgrade to.
My conclusion is that during the move of the .jenkins folder to the new computer the dates of the old plugins are getting new values which confuses Jenkins. Is that a correct conclusion? How can I correct it?
Since the folder dates were changed long ago at the old computer I was not able to zip the old .jenkins folder with "correct" dates
However, I found a way forward anyway. I did like this:
Started with a newly installed Jenkins version.
Made sure I had all necessary plugins in the new Jenkins installation
Copied the following folders from the old computers .jenkins zip file:
jobs
nodes
secrets
users
workspace
Then I also moved the files in the .jenkins folder
I was working on jenkins and working fine but i don't know what happened Jenkins shows following errors and no jobs are visible to me after that:
I am new in jenkins please help me to solve this.
As I understand the problem it could happened in cause of downgrading jenkins version or updating plugins "Pipeline: Node and Processes".
You need to restore previous jenkins version or downgrade plugin.
Additionally you can configure jenkins to get plugins' versions which fit your jenkins version in "Manage Jenkins" -> "Manage plugins" -> "Advanced" -> "Update site" and set the version you are currently using (for example https://updates.jenkins.io/stable-2.176/update-center.json)
Jenkins plugins are dependent on Jenkins LTS versions in use. Best way is while installing the Jenkins take latest (but stable) version of plugins.
Since you are using 1.176 version and trying to upgrade the plugins, the latest plugins do not support the older version of Jenkins (since Jenkins follow Parallel incremental development).
You can resolve the problem in 2 ways.
1. Downgrade the plugins and keep the LTS Jenkins version as it is. (not preferred solution since you will not be able to use latest functionality of the plugins and using old plugins is not secured).
Downgrade of plugins will also be suggested by Manage Jenkins --> Manage Plugins --> Installed
2. Upgrade Jenkins version (LTS 2.24x.x)
It is time taking option, but if you are heavely using jenkins for your work it is more suggested to upgrade the version. Besides new plugins have more secured and vast functionalities.
You can check the Changelog and can decided which version is good for you.
Take a reference of Upgrading Jenkins link.
To understand plugins and Jenkins LTS version dependency, use Jenkins wiki(Confluence Page).
e.g. Pipeline:Node and Processes plugin wiki indicates that for version 2.29 you need to have Jenkins version 1.150.1 or higher.
Note: Latest Jenkins version supports HTTPS instead of HTTP URL for advanced proxy options under Manager Jenkins.
When installing a new Grails from Jenkins web UI, a user is given the choice of some versions - up to 2.4.4 and 3.0, but 2.4.5 and 2.5 are missed.
How to add 2.4.5 to that list?
P.S. Jenkins 1.598, Grails plugin 1.7 (latest)
There is an automated process within the Jenkins project infrastructure which updates the list of available versions daily.
Your Jenkins installation periodically downloads this file and uses it to populate the version list in the web UI.
Unfortunately, at the time of asking this question, that automated process was broken.
You can either wait for the bug to be fixed (it is now), or there should be the option to "Install from .zip/.tgz" instead of "Install from mirrors", where you can enter the URL to the Grails 2.4.5 zip file.
You have to go to "Manage Jenkins"/"Configure System"/"Grails installations" and put there the path where your installation is.
We are using solr-grails plugin for our website. And the most recent version of the plugin (grails-solr-plugin 0.2) uses solr 1.4, whereas the latest version of Solr is 3.5.
Is there any way I can update the Solr version without affecting the plugin?
Kindly help.
You could install the plugin, excluding the version of the Solr library therein, then explicitly include the more recent version. The details are described here in the context of another plugin.
Assuming you already have a plugin developer account, it would probably be easier to just download the plugin source code, upgrade the library and release a new version. FYI, a new plugin version can be released by anyone, not just the original plugin author. Your fellow Solr plugin users will thank you for this.
The plugin doesn't seem to be updated for almost a year now. There have been a number of forks from the original source code and some of them are updates for the 3.5 version - https://github.com/mbrevoort/grails-solr-plugin/network . You should try one of those.
I have recently started a new project using the maven grails archetype - at the time, (a few weeks ago), Grails 1.2.0 was the most recent release. Now that there's a newer release, what are the steps to upgrade? I would assume that since Grails dependencies are defined in the POM, that the POM will need to be updated? Are there any instructions on doing this? Does the maven-grails-plugin handle this? Is this documented anywhere?
Appreciate any pointers. Thanks!
According to this thread:
The recommended way of upgrading grails is simply "grails upgrade" in the project dir when you have downloaded the new version of Grails and set up your paths etc...
Note that I've seen at least one person reporting problems with version 1.2.1 (and the Hibernate plugin), see this thread. There is a workaround in the thread but maybe have a look at the Grails Jira first to see if there are any blocking issues with 1.2.1.
There is no "upgrade" target in the maven grails
plugin, so I'm still looking for information on doing this upgrade with maven.