Difference between revisions of "Jenkins Projects (aka Jobs)"
From Gcube Wiki
Luca.frosini (Talk | contribs) |
Luca.frosini (Talk | contribs) |
||
| Line 7: | Line 7: | ||
[[File:Jenkins_newItem.png|200px]] | [[File:Jenkins_newItem.png|200px]] | ||
| − | Jenkins interface is available at [https://jenkins.d4science.org/] | + | Jenkins interface is available at [https://jenkins.d4science.org/ https://jenkins.d4science.org/] |
2. In the new item page, assign a name to the project | 2. In the new item page, assign a name to the project | ||
Revision as of 17:46, 6 June 2019
gCube Template Project
The easiest way to create a new project is to clone the gCubeTemplate project.
1. In the Jenkins interface, select New Item from the options on the left panel:
Jenkins interface is available at https://jenkins.d4science.org/
2. In the new item page, assign a name to the project
3. Scroll down until the bottom of the page and use the last option to create the new item from other existing. Insert gCubeTemplate as input (it should auto-complete).
and confirm with OK.
4. In the new project page, you need to:
- uncheck the "Disable this project" checkbox
- provide the URL to the Git repo to build
That should be enough to try to build the project with a Jenkins job.
Examples
Source Code Management and Poll Triggers
- set option to "Git",
- provide the URL to your repo (e.g. https://code-repo.d4science.org/gCubeSystem/gxRest.git),
- set the credentials to git.gcube,
- specify */master as branch to build,
- and in "Poll triggers" section check "Poll SCM" option with no schedule defined. This setup basically tells Jenkins to poll your Gitea repo only when requested via a webhook.
Back to the CI guide.
