I am trying to configure the JIRA plugin with Jenkins but I am receiving the error
"This is a valid URL but it doesn't look like JIRA".
I am trying to connect to my company installation of JIRA studio which is http://[company].jira.com and I know this URL is correct as I have several projects using it successfully. Is there some setting I should enable in JIRA studio for this to work?
I had a similar issue and fixed it by setting our JIRA studio Title to "Atlassian JIRA".
You can change it by going to admin->general->account->account name->(change)
The plugin looks for one (or both) of those words, I forget which.
You might also have to enable "Accept Remote API Calls" in admin->issues->global settings->general configuration->options
Hope that works for you.
Related
I was using Hudson for doing my project builds and now planning to migrate to Jenkins.
The build server time is not in sync with the developer machines, and hence svn update does not work correctly. In Hudson, I was able to set the revision policy to HEAD, whereas its missing in Jenkins.
I searched a bit and saw that a Jira is created for this issue, but did not find a working solution for the problem.
I tried to manually install the Hudson subversion plugin in Jenkins, and the Revision policy option came up, but for some reason it caused an exception while setting the svn authentication info.
If anyone knows a solution to make this change in Jenkins, kindly reply.
Figured out. Append all SVN urls with #HEAD and svn update will happen from HEAD!
The plugin doesn't offer such feature but you might find useful this jira issue. There is a patch in the comments for that purpose. See Issue 1241.
I am using Eclipse Helios (3.6). I want to use Mercurial for version management of the program. I have take the help of the below link to find out the plugin but not got any success:
Mercurial Eclipse Plugin
Can any one please help to install Mercurial plugins inside my Eclipse and I also don't know how to use also. I have gone through the video also but not clear.
http://www.youtube.com/watch?v=9OBg6Zv0Tns
My question is that I want to use Mercurial in my project for version control. I know what Mercurial is, but don't know how to use it.
I want to know what is the initial setup that I have do if I want to use Mercurial set up in my project.
When I am trying to add new software It is giving me following error.
the 'Duplicate Location' error message in your screenshot would indicate that there is already an update site setup for that URL.
In the screen before doing the 'add repository' look at the list of current update sites and you may find one for Mercurial already. Make sure it is selected and a list of all the features for that update site will be listed for you. Then you can select the MercurialEclipse and MercurialBinaries features and install then in Eclipse
The Mercurial Eclipse homepage is here: http://javaforge.com/project/HGE.
They have installation instructions there:
[...] you can get the plugin easily using the Eclipse Update Manager, just click Help → Software Updates in Eclipse. The Eclipse Update Site for MercurialEclipse is available at this URL:
http://cbes.javaforge.com/update
If you are not familiar with getting new software and updates to Eclipse, please read this article.
I have installed and configured this plugin:
http://wiki.hudson-ci.org/display/HUDSON/JIRA+Plugin
In Jira I have turned ON option "accept api calls"
in Jira logs i can see that Hudson established connection
but nothing else happens, ive got test builds and they're failing but hudson doesnt report anything to jira
how to name job? how to name tests? do i need jiraID?
how to create issue that works with hudson?
how to actually tie hudson job with jira issue?
I recommend you to use this plugin: Marvelution JIRA Hudson Integration. With it I hope yo could solve your problem.
You have to install 2 different parts of the plugin, one in JIRA and another one in Jenkins (it enables a new API to allow JIRA to connect with Jenkins).
Then, you have to go to JIRA Administration, Hudson, Servers, Add Server, configure there your Jenkins server.
After that, go to Administration, Hudson, Associations, Add a Hudson Association and link your project in JIRA with your Jenkins task (a list of tasks will be shown).
Finally, you only have to go to your JIRA project's page and you'll see a Hudson tab in which you can see the integration that you need.
Jenkins cannot resolve Jira issues. It only can post comments.
Also Jenkins does not post comments in Jira issues named as tests or jobs or anything
in scans comments in commit to svn and if there is a Jira id then after build it posts comment.
This is too poor and basic functionality for me so I gave up.
I recently found this plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Jira+Issue+Updater+Plugin
but I'm in the middle of a project and dont want do test it now
If you want to create issues in Jira from e.g. failed tests in Jenkins, then the JiraTestResultReporter plugin will help you. See this link.
I am currently attempting to integrate Jenkins (version 1.53+) with JIRA (v5.2) to have the i) create jira issue and ii) update jira issue capabilities. My source control is SVN and my user is configured with CROWD
Currently, I am able to only update a JIRA issue from a post-build. The key is to have the latest SVN commit message begin with '-' as the format (i.e. 'PROJECT-3' denotes issue number 3 for jira project key = PROJECT)
See the overall plugin and configuration process at this link: http://blog.dominikschadow.de/?p=313
output of jenkins updates the JIRA issue (referenced in the svn commit message as I indicated) with:i) STATUS ii)jenkins job output link iii) svn commit message and file(s) changes / removed.
I want to deploy my application to glassvish v3 with asadmin deploy command however I get an error:
com.sun.enterprise.admin.cli.CommandException: remote failure: There is no installed container capable of handling this application com.sun.enterprise.deploy.shared.FileArchive#1c2a1c7
What can be the problem?
To me, the problem was coming from the fact that in /domains/domain/applications there was still the application I was trying to deploy again.
Another file access possibility I just ran into:
Service was started as root and the app undeployed/deployed. Then, as the correct limited rights user, undeploy/deploy. On deploy you'll receive this error, as the application files will still exist in he 'domains/yourdomain/applications' directory, and will be owned by root.
+1 to Keeg's comment on the awesome error messages we've all come to expect from Glassfish.
Hey I got the same error.In my case,I'd made a directory named "Web-INF",apparently the name of the folder has to be (mandatory) in upper-case i.e. "WEB-INF".
In short,check for spelling errors.
It solved my issue.So just wanted to share.I'm new to glassfish, so can't really tell you the exact solution.But what worked for me could be a solution for you as well.
Just in case someone else finds this question and the above answer doesn't match your case... Our problem was that the temporary area on the Glassfish server was full. Clearing some space let me redeploy the same application. Thank goodness for excellent error messages.
I had an ear project, where the ear package had different version number configured to maven pom.xml than the rest of the projects it contained. It searched sub-modules from version 1.x and the rest of the project was at 1.y version. I updated every pom to same version and that made the trick.
I'm looking at using the Hudson JIRA plugin to post a JIRA comment on each build. The SCM I'm using is perforce which is already linked to the JIRA tasks using perforce jobs. I can see that the JIRA story (e.g. PROJ-001) is visible through the perforce plugin when clicking on the changelist number in the build reports.
I'm having problems getting the Hudson JIRA plugin to work as it appears to expect the JIRA story in the change text rather than using the perforce job reference.
Note, manually adding the JIRA story into the changetext for every commit is not an option, but I was wondering whether any had any ideas short of extending the JIRA plugin itself.
Have you tried any of these???
http://wiki.hudson-ci.org/display/HUDSON/JIRA+Plugin
https://plugins.atlassian.com/plugin/details/11858
Why don't you use Marvelution JIRA Hudson Integration? I tried it and it worked perfect.