I am new to Jenkins and looking to download Clearcase plugin for it.
I downloaded the clearcase plugin files from
http://updates.jenkins-ci.org/download/plugins/
But I noticed that .hpi files are missing in them.Where do i get the .hpi files for those?
Here is a place where you can Download the HPI file for Jenkins Plugins. You will see a folder for Clearcase.
Just use the Update Center in Jenkins. In your Jenkins instance, click on manage Jenkins and then update plugins, there are several tabs in the update jenkins page. One of them is called available plugins, click on that tab, and search for the plugin you need in the list of plugins that is displayed.
Related
after a couple of hours trying and reading a number of tutorials, I can't fix the following problem: I have a remote server running a git repository. From eclipse (neon.2 and egit) I pushed several maven projects, each with its own pom.xml to this repository. When a friend of mine, who wants to co-develop tries to setup his environment, also using Eclipse Neon.2 and egit, we are not able to reproduce the setup in the Package Explorer. We get all the sources but in one project. The original maven projects are all nested in this one project. This wrong setup results in a couple of problems when trying to compile or run the projects.
We used File-> Import-> Git-> Projects from Git-> Clone URI. In Source Git Repository we pointed the Repository path to /home/git/workspace.git. In the Branch Selection dialog we can then only see the master. In the following Local Destination dialog we checked the Clone submodules checkbox. We played around with the following options to run wizards which were all failing, so we ended up with this one project option in the bottom of the three options in the dialog.
What is not happening, is the import projects dialog as explained here https://wiki.eclipse.org/EGit/User_Guide/Remote#Import_Projects
(but this seems to be a former version, since the Clone submodules checkbox is missing in the dialog before on this web page)
Can anybody please tell us how to extract the maven projects as top elements in eclipse, linked to the existing git repository, such that we can work as a team?
Should you need any additional information, please let me know.
Thank you in advance.
I would advise you to always put all Eclipse configuration files to the repository when creating projects. What you should do is add all necessary maven integration related files to the repository (.project, .classpath, .settings/*m2e.core.prefs or better yet entire .settings). If you have done so, you are fine. If not, add them and pull changes on your colleague's machine.
On target machine remove the project from workspace, but do not delete contents. In Eclipse Git repositories view select your repository and expand to see Working tree. Right click it and select Import projects. This will trigger the flow you pointed our at Eclipse wiki. From there it should be straightforward - Eclipse will try to detect projects and will import them, so that they have Maven nature and are managed by EGit.
If you don't want to or cannot share maven configuration in the repository, have a look at this answer which tries to describe how to achieve that without Eclipse configuration files.
I have forked my own repo of a Jenkins plugin on Github (and made some changes), and I have downloaded it as .zip file. How can I install this onto Jenkins? I assume I need to convert the .zip contents into a .hpi, but not sure how to do this?
I worked this out by creating a Maven project in Eclipse then running the maven command "package" against the pom.xml, this is what produces the .hpi file.
I'm part of a team working on a game project and we just moved our project to using Gradle. I can pull, commit, merge and push normally with Git GUI in Windows Explorer, but other members of the team can also pull in Eclipse by right-clicking the Gradle-project folder in Project Explorer view, choosing Team-menu and then Pull. However, in my Eclipse the "Team" settings only give me options to "Apply Patch" and "Share Project.." the whole team has tried to find a solution for this to no avail so far.
Before the project was built on Gradle, I was also able to pull in Eclipse by using the aforementioned method. We're using Git repository.
Any suggestions on where to look for the cause of this malfunction?
Thank you.
I assume then you don't store the Eclipse project files/settings in your Git repository but create them locally using gradle eclipse.
Then after importing the project into Eclipse (be sure not to copy it to the workspace) you can use the Share project... option under Team in the context menu. Then choose Git. Eclipse EGit will automatically detect if your project resides in an existing repository (it should be listed on the next wizard page) and set up the corresponding association.
The term Share project maybe is a bit confusing, as you also do it for projects that already are under version control.
I have an android project in my eclipse workspace. However, it uses source imported from another location - I dragged the folder onto the project and selected "Link to files and folders". The sources itself exists in a mercurial repo but the project does not. How can I get eclipse to give me a team menu for mercurial sources, is it possible? (I have installed MercurialEclipse plugin) The only thing I can see it offers me is when I right click the project to create a new mercurial repo which is not what I want.
Thanks in advance
Stephen
The normal solution would be to reference your second set of source as a subrepo.
But since May 2010, issue 11871 shows that subrepos aren't properly recognized by the MercurialEclipse plugin.
Its target resolution is for MercurialEclipse1.9. We are currently at MercurialEclipse1.7.1.
So the other solution would be to make a separate project, referencing directly (and only) your second set of sources, and setup a "project dependency" between your first project and your second Eclipse project.
That second project would include a second Mercurial repo and could be shared easily with MercurialEclipse.
I have a Eclipse installed to work with BIRT reports. What files in the workspace should be committed to the repository and what files should not?
Basically, any file able to help a developer checkout the repo and (almost) immediately open the project to work on it.
That should include at least eclipse files like .project, .classpath, and some IDE settings.
They might be some BIRT-specific settings as well.
See also:
Do you keep your project files under version control?
When working with Eclipse, should I add the workspace to the source control?