I'm trying to stand up a Hudson CI server.
I'm following an article written here.
I've gotten the server to stand up successfully by itself, but when I go to install the plugins all the plugins fail to install.
This happens the second time I run
java -DHUDSON_HOME=data -jar hudson.war
when I have all my plugins in the /plugins folder.
The errors I'm getting are
No 'Plugin-Class' entry in the manifest of ...msbuild.hpi
No 'Plugin-Class' entry in the manifest of ...nunit.hpi
Dependency analysis-core doens't exist (related to task.hpi)
I grabbed the latest stable release of them, so I'm thinking it has something to do with how I set up my hudson instance. The only different thing that I have done from the article is that I set up the installation in C:\Hudson.
Does anyone know why these plugins are all failing?
The problem was that for some reason I downloaded version 1.1 of hudson. I'm not sure how that happened since I clicked on the latest link, but I went back and downloaded the real latest version and the plugins are installing fine now.
The tasks plugin still doesn't install, but I don't really have to have that one, I was just curious what it was.
Related
I'm looking to develop an application using gradle, groovy, maven other other products supported by sdkman. I'm using cygwin on a windows 10 machine. All seems good and updates most software packages that are needed. When I get to the point of installing gradle, sdk simply can't download ANY version of gradle. Is this a bug or am I missing something. Here's what I'm getting from my cygwin console.
Admin#Dale-PC ~
$ sdk install gradle
Downloading: gradle 2.14.1
In progress...
######################################################################## 100.0%
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of /home/Admin/.sdkman/archives/gradle-2.14.1.zip or
/home/Admin/.sdkman/archives/gradle-2.14.1.zip.zip, and cannot find /home/Admin/.sdkman/archives/gradle-2.14.1.zip.ZIP, period.
Stop! The archive was corrupt and has been removed! Please try installing again.
Admin#Dale-PC ~
It seems as though sdk thinks it knows where it is however when it goes to pull it down, it doesn't pull down. Then sdk goes to unpack it and it can't find it. Any advice would be appreciated. Btw, I'm not going through a proxy and everything else seems to install just fine. It is just gradle that has the issue. Also, why is it trying to pull down an old version of gradle (2.14.1)?
I've downloaded the v2.14.1-all version, renamed the file to be gradle-2.14.1.zip.zip and placed it in the /home/Admin/.sdkman/archives/ directory and then did the install for gradle again. This time it found it and installed it as though it had downloaded the correct version. It's a solution for now.
v2.14.1 is the newest version of gradle. See here and here (3 is currently in beta-ish)
The filename .zip.zip seems erroneous. Possibly a defect in sdkman. Unsure if it was you who reported this on github, but: https://github.com/sdkman/sdkman-cli/issues/445
I'm setting up a build on Teamcity that will build a XCode project, then create a release in Octopus and using Powershell copy the files into a server. However, I'm having an issue, while both steps (Teamcity and Octopus) work independently, currently Teamcity is telling me that my build agent does not complies with the requirement 'OctopusDeploy: Release'.
I've downloaded the plugin that is here, and have managed to put the zip file on the runner directory, and while Octopus restarted and seems to have installed it, it still doesn't show as one of the available Build runners.
Apparently you can't do this, or that's what it seems like. Installing the plugin on a fresh install of Teamcity ignored the Mac build agent, which means it's not compatible.
This makes sense because Octopus uses an exe wrapper so this could be the reason. If anybody finds something else, feel free to contribute.
I'm trying to comple the Apache Flex SDK mavenizer tool, I need this tool to convert the Apache Flex Sdks in package suitable for the Maven repository .
I downloaded the git repository from
https://git-wip-us.apache.org/repos/asf/flex-utilities.git
I followed the instruction in the README.txt that are similar to the Building the Mavenizer tutorial: I clone the repository, I entered in the mavenizer directory and I lunched mvn package.
The maven script ran without errors but I couldn't find any jar in the man target directory.
Each module were correctly built but not the main jar.
So I coulnd't execute the converter
java -jar [path-to-the-maveinzer-jar]/mavenizer.jar "[sdkhome]" "[fdktarget]"
Could someone help me? Has anyone run into the same problem?
I'm happy to share here the answer they gave me in the apache flex users forum.
Actually there was a problem!
Ups sorry for that ... I didn't update that page for quite some time.
The problem is that you checked out the old version. The new version
is in the develop branch. As soon as the mavenizer is officially
released, master will contain the updated version.
I did write down a little more detailed howto under:
https://cwiki.apache.org/confluence/display/FLEX/Quick+Start+Guide:+Building+Apache+Flex+applications+using+Maven
(I just re-checked and fixed one problem)
I Hope that it could be useful !
I am trying to configure Eclipse for Windows to meet my workplace's requirements, and in doing so the program ran out of memory and crashed. I am trying again with a fresh install (deleted all files I could find related to Eclipse and recopied).
I have a Git perspective available, but it is completely blank. Git is not listed in my current plugins, and not present in my plugins folder that I can find. If I try to install it, however, I am told it already exists.
Eclipse Version: 3.6.2
EGit Version: 1.1.0.201109151100-r
You can usually fix a lot of problems like this by doing a
$ eclipse -clean
You may have to add this to your eclipse.ini file.
If this doesn't work, start from a clean install (the eclipse directory & the workspace).
So after reading multiple Q&As here about why I should use Jenkins over Hudson, I went ahead and made the switch ... and now I'm regretting it. With Hudson (or at least with the Debian package I used to install Hudson), Git came "out of the box"; I didn't have to install any plug-ins or anything.
With Jenkins however, not only do I need a separate plug-in, but when I try to install that plug-in, it fails, repeatedly. I can find the plug-in in the list of available plug-ins, check it, and get a "success" message, but after I restart Hudson the plug-in isn't there (and it's once again on the available plug-ins list).
The problem might be the warning message under the plug-in's description:
Warning: This plugin is built for Jenkins 2.1.0 or newer. It may or
may not work in your Jenkins.
... except there is no 2.1.0 of Jenkins (or even a 2.anything), at least that I can find.
Has anyone else run in to this, and if so do you have any kind of workaround?
I wound up purging hudson/jenkins, then re-installing the jenkins package; this time the git plug-in installed successfully!