[JIRA] (JENKINS-49073) build job propagate true propagates FAIL when state is UNSTABLE

2020-04-17 Thread philippjung2...@live.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Jung commented on  JENKINS-49073  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: build job propagate true propagates FAIL when state is UNSTABLE   
 

  
 
 
 
 

 
 Thanks for clearing that up.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187899.1516619705000.13112.1587126180312%40Atlassian.JIRA.


[JIRA] (JENKINS-49073) build job propagate true propagates FAIL when state is UNSTABLE

2020-04-15 Thread philippjung2...@live.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Jung commented on  JENKINS-49073  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: build job propagate true propagates FAIL when state is UNSTABLE   
 

  
 
 
 
 

 
 I can reproduce this again on both our Jenkins instances: with Build-Step 2.12 and Pipeline Groovy 2.80. Here is a minimal example: The second part of the "unstable -> success"  stage is never executed. 

 

// Parent Job
node(){
def stage_map = [:]
stage_map['success'] = trigger('SUCCESS')
stage_map['unstable -> success']= {trigger('UNSTABLE').call(); trigger('SUCCESS').call()} // The second SUCCESS step is never triggered

parallel(stage_map)
}

def trigger(status){
return {
def result = build job:
'test_child',
parameters: [
string(name: 'status', value: status)
]
}
}
 

 

 

// Child Job
node(){
  properties([
parameters([string(name: 'status', defaultValue: 'SUCCESS')])
]) 
currentBuild.result = params.status
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received 

[JIRA] (JENKINS-61737) Parallel Build job propagates FAIL while running when child job UNSTABLE

2020-03-30 Thread philippjung2...@live.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Jung created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61737  
 
 
  Parallel Build job propagates FAIL while running when child job UNSTABLE   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 after_run.png, during_run.png  
 
 
Components: 
 blueocean-plugin, pipeline-build-step-plugin, workflow-cps-plugin  
 
 
Created: 
 2020-03-30 08:26  
 
 
Environment: 
 pipeline-build-step 2.12  workflow-cps 2.80  blueocean 1.22.0  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Philipp Jung  
 

  
 
 
 
 

 
 I have two Jenkins jobs, a parent job that triggers a child job with different configurations and runs these stages in parallel. When a child job has an UNSTABLE state, the parent job reports this stage as failed as long as the parent job is still running. When the parent job is finished all results are propagated as expected. Example to reproduce: 

 

// Parent job
// With three stages with SUCCESS, UNSTABLE and FAILED stages

node(''){
def stage_map = [:]
stage_map['success'] = trigger('SUCCESS')
stage_map['unstable'] = trigger('UNSTABLE')
stage_map['failed'] = trigger('FAILED')
stage_map['sleep'] = trigger('SUCCESS', true)

parallel(stage_map)
}

def trigger(status, sleep = false){
return {
build job:
'test_child',
parameters: [
string(name: 'status', value: status),
booleanParam(name: 'sleep', value: sleep)
]
}
}
 
   

[JIRA] (JENKINS-53919) SVN: Repository URL parameterized stopped working

2020-03-27 Thread philippjung2...@live.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Jung commented on  JENKINS-53919  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SVN: Repository URL parameterized stopped working   
 

  
 
 
 
 

 
 Version 2.13.1 does not work for us as well. We have downgraded to 2.11.1 for now but would really like to update soon.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194517.153873170.1294.1585323780164%40Atlassian.JIRA.


[JIRA] (JENKINS-53919) SVN: Repository URL parameterized stopped working

2020-03-27 Thread philippjung2...@live.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Jung edited a comment on  JENKINS-53919  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SVN: Repository URL parameterized stopped working   
 

  
 
 
 
 

 
 I have the same issue. The much larger checkouts when disabling this option is  a  real problem for us.Has anyone tested this on 2.13.1?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194517.153873170.1192.1585308720222%40Atlassian.JIRA.


[JIRA] (JENKINS-53919) SVN: Repository URL parameterized stopped working

2020-03-27 Thread philippjung2...@live.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Jung commented on  JENKINS-53919  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SVN: Repository URL parameterized stopped working   
 

  
 
 
 
 

 
 I have the same issue. The much larger checkouts when disabling this option is real problem for us. Has anyone tested this on 2.13.1?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194517.153873170.1180.1585307820179%40Atlassian.JIRA.


[JIRA] (JENKINS-42369) agent docker parameters do not honor the current environment

2019-11-26 Thread philippjung2...@live.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Jung commented on  JENKINS-42369  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: agent docker parameters do not honor the current environment   
 

  
 
 
 
 

 
 Same issue here. Any chance to change the priority?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179270.1488278418000.7075.1574766120658%40Atlassian.JIRA.