Is there a way for Jenkins to build a job only when a Gitlab merge request is merged?
up vote
0
down vote
favorite
I know that there are a lots of material indicating that a Jenkins build is triggered, immediately after the code is pushed, but my requirement is little beyond that step.
I have 3 branches - master > will hit the Prod server, staging > will hit the testing server and Dev > will hit the dev server.
Whenever there is a feature branch that gets merge request raised and later merged to the Dev branch, I do a manual deployment to the dev server
Similarly to the other environments too where dev branch is merged with the staging and later staging is merged with the master.
I am now looking a way to integrate Jenkins to do this deployment as soon as the branch is merged. Is this possible? Do I need to write some Groovy script?
git jenkins gitlab integration
add a comment |
up vote
0
down vote
favorite
I know that there are a lots of material indicating that a Jenkins build is triggered, immediately after the code is pushed, but my requirement is little beyond that step.
I have 3 branches - master > will hit the Prod server, staging > will hit the testing server and Dev > will hit the dev server.
Whenever there is a feature branch that gets merge request raised and later merged to the Dev branch, I do a manual deployment to the dev server
Similarly to the other environments too where dev branch is merged with the staging and later staging is merged with the master.
I am now looking a way to integrate Jenkins to do this deployment as soon as the branch is merged. Is this possible? Do I need to write some Groovy script?
git jenkins gitlab integration
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I know that there are a lots of material indicating that a Jenkins build is triggered, immediately after the code is pushed, but my requirement is little beyond that step.
I have 3 branches - master > will hit the Prod server, staging > will hit the testing server and Dev > will hit the dev server.
Whenever there is a feature branch that gets merge request raised and later merged to the Dev branch, I do a manual deployment to the dev server
Similarly to the other environments too where dev branch is merged with the staging and later staging is merged with the master.
I am now looking a way to integrate Jenkins to do this deployment as soon as the branch is merged. Is this possible? Do I need to write some Groovy script?
git jenkins gitlab integration
I know that there are a lots of material indicating that a Jenkins build is triggered, immediately after the code is pushed, but my requirement is little beyond that step.
I have 3 branches - master > will hit the Prod server, staging > will hit the testing server and Dev > will hit the dev server.
Whenever there is a feature branch that gets merge request raised and later merged to the Dev branch, I do a manual deployment to the dev server
Similarly to the other environments too where dev branch is merged with the staging and later staging is merged with the master.
I am now looking a way to integrate Jenkins to do this deployment as soon as the branch is merged. Is this possible? Do I need to write some Groovy script?
git jenkins gitlab integration
git jenkins gitlab integration
edited Nov 12 at 23:06
halfer
14.2k758106
14.2k758106
asked Nov 11 at 11:21
krishna chaitanya
61
61
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248208%2fis-there-a-way-for-jenkins-to-build-a-job-only-when-a-gitlab-merge-request-is-me%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown