questions on SCM and pipe

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

questions on SCM and pipe

Stefano Tranquillini
Hi all,

I'm new to jenkins and I've rather a complex setup. I did it via pipe and diffrent stages, but there are things not yet clear to me.
Overall my setup is this

- push the code to git
- jenkins automatically pull the code (there's a webhook for that)
- copy env files (i'm usin python and django)
- run docker-compose to spin posgres and other services
- run the test
- take down the compose

Now, I've diffrent branches in the git, namely develop, master, feature/*, hotfix/*
and I would like to have rather different logic for each branch, how should I do that?
I saw that the SCM checkout can specify branch, but how does it work? if I pull from master and develop, will jenkins runt he pipe twice? or what?

Othe questions that I've:
- Is jenkins/SCM plugin able to run the pipe only if there are new commits?
- is it possile to always run a stage? I want always to take down the docker-compose containers even if other stage fails.
- is there a place with good examples of how people use jenkins? i found the documentation ragther limited, I would prefere to see how people use jenkins in practice, so I can learn from that.


--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d4559d54-4c99-4f3b-bc33-a9bfcaca2467%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: questions on SCM and pipe

stephenconnolly
Pipeline multibranch is what you want.

Each branch can have its own Jenkinsfile and that will describe the behaviour for that branch...

Or you can use a common Jenkinsfile and use conditions for some steps based on the branch name

HTH

On 20 March 2017 at 10:33, Stefano Tranquillini <[hidden email]> wrote:
Hi all,

I'm new to jenkins and I've rather a complex setup. I did it via pipe and diffrent stages, but there are things not yet clear to me.
Overall my setup is this

- push the code to git
- jenkins automatically pull the code (there's a webhook for that)
- copy env files (i'm usin python and django)
- run docker-compose to spin posgres and other services
- run the test
- take down the compose

Now, I've diffrent branches in the git, namely develop, master, feature/*, hotfix/*
and I would like to have rather different logic for each branch, how should I do that?
I saw that the SCM checkout can specify branch, but how does it work? if I pull from master and develop, will jenkins runt he pipe twice? or what?

Othe questions that I've:
- Is jenkins/SCM plugin able to run the pipe only if there are new commits?
- is it possile to always run a stage? I want always to take down the docker-compose containers even if other stage fails.
- is there a place with good examples of how people use jenkins? i found the documentation ragther limited, I would prefere to see how people use jenkins in practice, so I can learn from that.


--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d4559d54-4c99-4f3b-bc33-a9bfcaca2467%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMy_DO4WSm4YmdAOHjM_Qr%3D-n9y70Zd4yph72Z1t%3DjvEPA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: questions on SCM and pipe

Stefano Tranquillini
thanks. any pinpoint that i can use? 

btw right now i'm testing  a default build (no pipeline) to have coverage and other plugins. 


Il giorno lun 20 mar 2017 alle 14:06 Stephen Connolly <[hidden email]> ha scritto:
Pipeline multibranch is what you want.

Each branch can have its own Jenkinsfile and that will describe the behaviour for that branch...

Or you can use a common Jenkinsfile and use conditions for some steps based on the branch name

HTH

On 20 March 2017 at 10:33, Stefano Tranquillini <[hidden email]> wrote:
Hi all,

I'm new to jenkins and I've rather a complex setup. I did it via pipe and diffrent stages, but there are things not yet clear to me.
Overall my setup is this

- push the code to git
- jenkins automatically pull the code (there's a webhook for that)
- copy env files (i'm usin python and django)
- run docker-compose to spin posgres and other services
- run the test
- take down the compose

Now, I've diffrent branches in the git, namely develop, master, feature/*, hotfix/*
and I would like to have rather different logic for each branch, how should I do that?
I saw that the SCM checkout can specify branch, but how does it work? if I pull from master and develop, will jenkins runt he pipe twice? or what?

Othe questions that I've:
- Is jenkins/SCM plugin able to run the pipe only if there are new commits?
- is it possile to always run a stage? I want always to take down the docker-compose containers even if other stage fails.
- is there a place with good examples of how people use jenkins? i found the documentation ragther limited, I would prefere to see how people use jenkins in practice, so I can learn from that.


--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/dffVcbboIjM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMy_DO4WSm4YmdAOHjM_Qr%3D-n9y70Zd4yph72Z1t%3DjvEPA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
Stefano - Sent with my thumbs

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPQ1%3DkAgKU-NLuCDtC%2Bwdr1BnQNbzvoRfiHk9aU%2BSjghuP0mLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Loading...