date:20190623

[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin

2019-06-23 Thread kshettih...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 hhkkss edited a comment on  JENKINS-58112  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Triggering multibranch pipeline from jira-trigger-plugin   
 

  
 
 
 
 

 
 I agree with you on following {color:#ff}points{color}. but the thing is, in that case I have to create individual upstream projects for all my pipeline projects. :(. or let me know if there is any workaround to manage from single upstream job.  {color:#ff}Perhaps your best bet here is to get your branch triggered by an upstream project:{color} * {color:#ff}deploy in uat job: configured with jira-trigger-plugin{color} * {color:#ff}multibranch pipeline job: configured with upstream trigger to "deploy in uat job" (see: [https://stackoverflow.com/questions/36825103/jenkins-trigger-multi-branch-pipeline-on-upstream-change]){color}  {color:#172b4d} Regarding the {color }{color :#ffab00} {color:#172b4d}{color:#ff8b00} below  {color} comment, what I was trying to tell you is my pipeline is same for all the branches in the project. but it has WHEN condition's defined already. thus, deployment handle only from release branch. meaning, development branch is only to commit day to day changes. whenever, developers are ready to move the changes into SIT, then they have to merge the changes into release branch and then only entire pipeline is triggered. any triggers from development branch will not handle any deployment and it will run the build and unit testing only, so developers know that they do not have any compilation errors on the code.{color} {color}  {color:#172b4d}   {color} its simply like below: {code:java} { stage ('SIT Deployment'){  when { branch 'release' }    steps {      script {"my deployment". {code} {color:#ff8b00}To be honest I'm not really sure if Multibranch job is really appropriate in your use case either, what I'm hearing is:{color}  * {color:#ff8b00}release branch: sit deployment, uat deployment, prod deployment{color} * {color:#ff8b00}other branches: scm checkout, build, unit testing, packaging{color}{color:#ff8b00}It sounds like they are an entirely different jobs that sharing one Jenkinsfile might not be appopriate?{color}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira

[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin

2019-06-23 Thread kshettih...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 hhkkss edited a comment on  JENKINS-58112  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Triggering multibranch pipeline from jira-trigger-plugin   
 

  
 
 
 
 

 
 I agree with you on following {color:#ff}points{color}. but the thing is, in that case I have to create individual upstream projects for all my pipeline projects. :(. or let me know if there is any workaround to manage from single upstream job.  {color:#ff}Perhaps your best bet here is to get your branch triggered by an upstream project:{color} * {color:#ff}deploy in uat job: configured with jira-trigger-plugin{color} * {color:#ff}multibranch pipeline job: configured with upstream trigger to "deploy in uat job" (see: [https://stackoverflow.com/questions/36825103/jenkins-trigger-multi-branch-pipeline-on-upstream-change]){color} Regarding the {color:#ffab00}below comment, what I was trying to tell you is my pipeline is same for all the branches in the project. but it has WHEN condition's defined already. thus, deployment handle only from release branch. meaning, development branch is only to commit day to day changes. whenever, developers are ready to move the changes into SIT, then they have to merge the changes into release branch and then only entire pipeline is triggered. any triggers from development branch will not handle any deployment and it will run the build and unit testing only, so developers know that they do not have any compilation errors on the code.{color}   its simply like below:  {code:java} { stage ('SIT Deployment'){  when { branch 'release' }    steps {      script {"my deployment". {code}       {color:#ff8b00}  To be honest I'm not really sure if Multibranch job is really appropriate in your use case either, what I'm hearing is: {color}   * {color:#ff8b00}release branch: sit deployment, uat deployment, prod deployment{color} * {color:#ff8b00}other branches: scm checkout, build, unit testing, packaging{color}{color:#ff8b00}It sounds like they are an entirely different jobs that sharing one Jenkinsfile might not be appopriate?{color}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin

2019-06-23 Thread kshettih...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 hhkkss edited a comment on  JENKINS-58112  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Triggering multibranch pipeline from jira-trigger-plugin   
 

  
 
 
 
 

 
 I agree with you on following {color:# FF ff }points{color}. but the thing is, in that case I have to create individual upstream projects for all my pipeline  jobs  projects . :(. or let me know if there is any workaround to manage from single upstream job.  {color:# FF ff }Perhaps your best bet here is to get your branch triggered by an upstream project:{color} * {color:# FF ff }deploy in uat job: configured with jira-trigger-plugin{color} * {color:# FF ff }multibranch pipeline job: configured with upstream trigger to "deploy in uat job" (see: [https://stackoverflow.com/questions/36825103/jenkins-trigger-multi-branch-pipeline-on-upstream-change]){color} Regarding the {color:#ffab00}below  {color:#172b4d} comment, what I was trying to tell you is my pipeline is same for all the branches in the project. but it has WHEN condition's defined already. thus, deployment handle only from release branch. meaning, development branch is only to commit day to day changes. whenever, developers are ready to move the changes into SIT, then they have to merge the changes into release branch and then only entire pipeline is triggered. any triggers from development branch will not handle any deployment and it will run the build and unit testing only, so developers know that they do not have any compilation errors on the code.{color} {color}  its simply like below: {code:java} { stage ('SIT Deployment'){  when { branch 'release' }    steps {      script {"my deployment". {code}    {color:#ff8b00}   To be honest I'm not really sure if Multibranch job is really appropriate in your use case either, what I'm hearing is: {color}     * {color:#ff8b00}release branch: sit deployment, uat deployment, prod deployment{color} * {color:#ff8b00}other branches: scm checkout, build, unit testing, packaging{color}{color:#ff8b00}It sounds like they are an entirely different jobs that sharing one Jenkinsfile might not be appopriate?{color}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira

[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin

2019-06-23 Thread kshettih...@gmail.com (JIRA)

Title: Message Title

hhkkss commented on JENKINS-58112

Re: Triggering multibranch pipeline from jira-trigger-plugin

I agree with you on following points. but the thing is, in that case I have to create individual upstream projects for all my pipeline jobs. . or let me know if there is any workaround to manage from single upstream job. Perhaps your best bet here is to get your branch triggered by an upstream project:

deploy in uat job: configured with jira-trigger-plugin
multibranch pipeline job: configured with upstream trigger to "deploy in uat job" (see: https://stackoverflow.com/questions/36825103/jenkins-trigger-multi-branch-pipeline-on-upstream-change)
Regarding the below comment, what I was trying to tell you is my pipeline is same for all the branches in the project. but it has WHEN condition's defined already. thus, deployment handle only from release branch. meaning, development branch is only to commit day to day changes. whenever, developers are ready to move the changes into SIT, then they have to merge the changes into release branch and then only entire pipeline is triggered. any triggers from development branch will not handle any deployment and it will run the build and unit testing only, so developers know that they do not have any compilation errors on the code. its simply like below:

{ stage ('SIT Deployment'){
when { branch 'release' }
steps {
script {"my deployment"
.

To be honest I'm not really sure if Multibranch job is really appropriate in your use case either, what I'm hearing is:

release branch: sit deployment, uat deployment, prod deployment
other branches: scm checkout, build, unit testing, packaging
It sounds like they are an entirely different jobs that sharing one Jenkinsfile might not be appopriate?

51 matches

Mail list logo