Difference between revisions of "Jenkins Projects (aka Jobs) for GitHub"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) |
||
| Line 22: | Line 22: | ||
That should be enough to try to build the project with a Jenkins job. | 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, | ||
| + | |||
| + | [[File:JenkinsGitHubSourceCodeManagement.png|1000px]] | ||
| + | |||
| + | 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 [[GitHub/Jenkins:_Setting_up_Webhooks#Webhook_on_the_GitHub_repository|webhook]]. | ||
| + | |||
| + | [[File:JenkinsGitHubBuildTriggers.png|1000px]] | ||
| + | |||
| + | ''Back to the [[Continuous_Integration_procedure_(2019) | CI guide]].'' | ||
| + | |||
| + | [[Category:Continuous_Integration]] | ||
Revision as of 00:27, 1 December 2019
gCube GitHub Project Template
The easiest way to create a new project is to clone the gCubeGitHubProjectTemplate project.
1. In the Jenkins interface (Jenkins interface is available at https://jenkins.d4science.org/), select New Item from the options on the left panel:
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 gCubeGitHubProjectTemplate 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 GitHub 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,
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.
