Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Automated Jenkins job creation #970

Merged
merged 5 commits into from
Jan 20, 2016
Merged

Automated Jenkins job creation #970

merged 5 commits into from
Jan 20, 2016

Conversation

bilke
Copy link
Member

@bilke bilke commented Jan 19, 2016

This PR adds functionality to automatically create Jenkins jobs for a given git repository and then automatically build all branches when pushed (i.e. pull request testing before submitting the pull request). The only thing to be done is to mark a repo to be tested (see my repo and the ufz repo).

For the moment these tests will be run in addition to other tests as I am using the Jenkins Pipeline-functionality which still misses some features. Also the tests are a little bit slow because they are run on an old machine.

Starting point is the Jenkinsfile which loads the gcc.groovy where the actual job config is given:

  • builds inside a docker container
  • runs testrunner and ctest
  • publishes test results
  • scans console output for error and warnings

@ogsbot
Copy link
Member

ogsbot commented Jan 19, 2016

Jenkins: OGS-6/Linux-PRs failed: https://svn.ufz.de:8443/job/OGS-6/job/Linux-PRs/1041/

@chleh
Copy link
Collaborator

chleh commented Jan 20, 2016

I like the idea, but there is one thing:

automatically build all branches when pushed

Can that behaviour be changed s.t. only a branch with a specific name or only a specific tag (like jenkins-test-this) is built upon push? Because I don't want Jenkins to build all of my branches (especially since some of them are in a nonfunctional state).

@bilke
Copy link
Member Author

bilke commented Jan 20, 2016

Yes we can set regexes for branch inclusion and exclusion (based on branch name). I propose to use a postfix, e.g. my-feature-test or my-feature-jenkins.

@ogsbot
Copy link
Member

ogsbot commented Jan 20, 2016

Jenkins: OGS-6/Linux-PRs failed: https://svn.ufz.de:8443/job/OGS-6/job/Linux-PRs/1042/

@ogsbot
Copy link
Member

ogsbot commented Jan 20, 2016

Jenkins: OGS-6/Linux-PRs failed: https://svn.ufz.de:8443/job/OGS-6/job/Linux-PRs/1043/

@ogsbot
Copy link
Member

ogsbot commented Jan 20, 2016

Jenkins: OGS-6/Linux-PRs failed: https://svn.ufz.de:8443/job/OGS-6/job/Linux-PRs/1044/

@ogsbot
Copy link
Member

ogsbot commented Jan 20, 2016

Jenkins: OGS-6/Linux-PRs failed: https://svn.ufz.de:8443/job/OGS-6/job/Linux-PRs/1045/

@endJunction
Copy link
Member

Postfix jenkins +1

@endJunction
Copy link
Member

It seems not break the current builds and looks clean. ⏩

bilke added a commit that referenced this pull request Jan 20, 2016
@bilke
Merge pull request #970 from bilke/jenkins-tests
b517151 
Automated Jenkins job creation
@bilke bilke merged commit b517151 into ufz:master Jan 20, 2016
@bilke bilke deleted the jenkins-tests branch January 20, 2016 12:51
@ogsbot
Copy link
Member

ogsbot commented Jun 19, 2020

OpenGeoSys development has been moved to GitLab.

See this pull request on GitLab.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Complete test and QA environment.
Development

Successfully merging this pull request may close these issues.
4 participants
@bilke @ogsbot @chleh @endJunction