[JIRA] (JENKINS-39765) freeStyleJob should support an update argument to specify if you want or not override

2017-02-08 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon commented on  JENKINS-39765  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: freeStyleJob should support an update argument to specify if you want or not override   
 

  
 
 
 
 

 
 Well, at least it avoids the DSL seed job to be overwritten. It is a good point. But : 
 
In this specific case, it should be the default behavior 
The job is still SUCCESS, though it has not done at all what it is supposed to do. 
The console log does not help to quickly understand goes wrong. 
And worst, the job page shows something which is clearly wrong :   It looks like something has been generated though it is absolutely (and fortunately) not the case. 
 So, this option is less than sufficient. I would say that it is not suitable for such a control. Unless you know use cases where it is useful that a seed job generates a job that overwrite its seed job (something like a burn after reading use case ?), IMHO the default behavior for a seed job should be to fail if the seed job generated something that overwrites itself. I understand that in a real world, the DSL job will create several jobs among which the seed can be hidden... To discover it before the generation (and fails it) could be less than obvious. And so, if it is discovered on the fly, the job will fail, but should the whole generation be thrown up, or the other generated jobs be preserved... not sure of the good choice.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  

[JIRA] (JENKINS-39765) freeStyleJob should support an update argument to specify if you want or not override

2017-02-08 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39765  
 
 
  freeStyleJob should support an update argument to specify if you want or not override   
 

  
 
 
 
 

 
Change By: 
 jlpinardon  
 
 
Attachment: 
 screenshot-1.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38268) Parallel step and closure scope

2017-01-04 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon commented on  JENKINS-38268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parallel step and closure scope   
 

  
 
 
 
 

 
 Same problem when trying to loop over a map of git repositories : def scmRepo = [ 'jobRepo': [ 'url': "." 'branch': "origin/master", 'credentialsId': '.', 'targetDir': 'src' ], 'envRepo': [ 'url': "." 'branch': "origin/master", 'credentialsId': '.', 'targetDir': 'src' ], 'srcRepo': [ 'url': "." 'branch': "origin/master", 'credentialsId': '.', 'targetDir': 'src' ] ] @NonCPS def runCheckOut(scmRepo) { def branches = [: ] scmRepo.each() { repoName, repoRef - > branches["$ {repoName} "] = { node { println "\nCheckout content from $ {repoRef.url} " //your logic there } } } parallel branches } When using runCheckOut, it runs but never ends. No error message is displayed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly

2016-12-19 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon commented on  JENKINS-39464  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline with parallel and no stages does not get visualised correctly   
 

  
 
 
 
 

 
 Thanks for the good news  I will try this as soon as possible. But concerning the display while running,the bad news is that it is still broken after several run.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly

2016-12-19 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon edited a comment on  JENKINS-39464  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline with parallel and no stages does not get visualised correctly   
 

  
 
 
 
 

 
 With the workaround, the display is indeed "correct". I mean it is exact. But I think (as far as it is feasible) that the sequential stuff within could be displayed as in the my proposed schema. At least for the first level.Nevertheless, the display during the build run is not correct as shown below : !Display During run.png|thumbnail!Parallel blocks are shown as running (which is correct) but stages within are all displayed sequentially after, and lokke like achieved (which is for sure totally wrong).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly

2016-12-19 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon edited a comment on  JENKINS-39464  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline with parallel and no stages does not get visualised correctly   
 

  
 
 
 
 

 
 With the workaround, the display is  indeed  "correct". I mean it is exact. But I think (as far as it is feasible) that the sequential stuff within could be  display  displayed as in the my proposed schema . At least for the first level.  Nevertheless, the display during the build run is not correct as shown below : !Display During run.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly

2016-12-19 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39464  
 
 
  Pipeline with parallel and no stages does not get visualised correctly   
 

  
 
 
 
 

 
Change By: 
 jlpinardon  
 
 
Attachment: 
 Display During run.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly

2016-12-19 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon commented on  JENKINS-39464  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline with parallel and no stages does not get visualised correctly   
 

  
 
 
 
 

 
 With the workaround, the display is "correct". I mean it is exact. But I think (as far as it is feasible) that the sequential stuff within could be display. At least for the first level. Nevertheless, the display during the build run is not correct as shown below :
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly

2016-12-19 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon commented on  JENKINS-39464  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline with parallel and no stages does not get visualised correctly   
 

  
 
 
 
 

 
 Here it is : 

 

env.sleepTime=10
node('MTS_RH6_X64') {
env.initialName='Level1'
// Initializing level 1
stage('Start') {
env.stageName=env.initialName
sh('''
#!/bn/bash
echo "Starting ${JOB_NAME}.${stageName} at $(date +'%s') on ${NODE_NAME}"
sleep $(( 1 + $RANDOM % ${sleepTime} )) 
''')
}

parallel 'MRS_LDB':{

node('ENODEB_MRS_LDB') {
env.stageName='configure'
stage ('configure') {
sh('''
#!/bn/bash
echo "Starting ${JOB_NAME}.${stageName} at $(date +'%s') on ${NODE_NAME}"
sleep $(( 1 + $RANDOM % ${sleepTime} )) 
''')
}
env.stageName='make'
stage ('make') {
sh('''
#!/bn/bash
echo "Starting ${JOB_NAME}.${stageName} at $(date +'%s') on ${NODE_NAME}"
sleep $(( 1 + $RANDOM % ${sleepTime} )) 
''')}
env.stageName='test'
stage ('test') {
sh('''
#!/bn/bash
echo "Starting ${JOB_NAME}.${stageName} at $(date +'%s') on ${NODE_NAME}"
sleep $(( 1 + $RANDOM % ${sleepTime} )) 
''')
}
}
   
}, 
'MTS_LRH5':{
node('MTS_LRH5') {
env.stageName='configure'
stage ('configure') {
sh('''
#!/bn/bash
echo "Starting ${JOB_NAME}.${stageName} at $(date +'%s') on ${NODE_NAME}"
sleep $(( 1 + $RANDOM % ${sleepTime} )) 
''')
}
env.stageName='make'
stage ('make') {
sh('''
#!/bn/bash
echo "Starting ${JOB_NAME}.${stageName} at $(date +'%s') on ${NODE_NAME}"
sleep $(( 1 + $RANDOM % ${sleepTime} )) 
''')}
env.stageName='test'
stage ('test') {
sh('''
#!/bn/bash
echo "Starting ${JOB_NAME}.${stageName} at $(date +'%s') on ${NODE_NAME}"
sleep $(( 1 + $RANDOM % ${sleepTime} )) 
''')
}
}
},
'LB': {
node('MTS_RH6_X64') {
env.stageName='configure'
stage ('configure') {
sh('''
#!/bn/bash
echo "Starting ${JOB_NAME}.${stageName} at $(date +'%s') on ${NODE_NAME}"
sleep $(( 1 + $RANDOM % ${sleepTime} )) 
''')
}
env.stageName='make'
stage ('make') {
sh('''
#!/bn/bash
echo "Starting ${JOB_NAME}.${stageName} at $(date +'%s') on ${NODE_NAME}"
sleep $(( 1 + $RANDOM % ${sleepTime} )) 
''')}
env.stageName='test'
stage ('test') {
sh('''
#!/bn/bash
echo "Starting ${JOB_NAME}.${stageName} at $(date +'%s') on ${NODE_NAME}"
sleep $(( 1 + $RANDOM % ${sleepTime} )) 
''')
}
}
}
env.stageName=env.initialName+'_Deploy'
stage('Deploy') {
sh('''
#!/bin/ba

[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly

2016-12-19 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon commented on  JENKINS-39464  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline with parallel and no stages does not get visualised correctly   
 

  
 
 
 
 

 
 Dear all, I made a trial  stagesNestedinParallel.xml  that is equivalent to the example given here. And, for sure, I felt into the same bug. Here is what it is displayed :I suggest that such a parallel pipeline (configure, make and test sequential stages run within several parallel "branches") could be displayed as :   Note that the "legacy" visualization is even unable to correctly display the duration of the stages :
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly

2016-12-19 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39464  
 
 
  Pipeline with parallel and no stages does not get visualised correctly   
 

  
 
 
 
 

 
Change By: 
 jlpinardon  
 
 
Attachment: 
 Legacy with duration error.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly

2016-12-19 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39464  
 
 
  Pipeline with parallel and no stages does not get visualised correctly   
 

  
 
 
 
 

 
Change By: 
 jlpinardon  
 
 
Attachment: 
 stagesNestedinParallel.xml  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly

2016-12-19 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39464  
 
 
  Pipeline with parallel and no stages does not get visualised correctly   
 

  
 
 
 
 

 
Change By: 
 jlpinardon  
 
 
Attachment: 
 AwaitedDisplay.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly

2016-12-19 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39464  
 
 
  Pipeline with parallel and no stages does not get visualised correctly   
 

  
 
 
 
 

 
Change By: 
 jlpinardon  
 
 
Attachment: 
 BrokenPipelineDisplay.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40412) The Env Inject plugin should contribute to pipeline in order to display environment variables

2016-12-13 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40412  
 
 
  The Env Inject plugin should contribute to pipeline in order to display environment variables   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 envinject-plugin  
 
 
Created: 
 2016/Dec/13 1:19 PM  
 
 
Environment: 
 Jenkins 2.7.20.X / Env Inject 1.93.1 / Last version of pipeline plugins  
 
 
Priority: 
  Major  
 
 
Reporter: 
 jlpinardon  
 

  
 
 
 
 

 
 On freestyle job build page, wen can easily display all "environment variables" sorted alphabetically, thanks to a link on the left menu. This is no more available for a build on a pipeline job. Could it be possible to have the same link that could display an array of the overall build common variables, and one array per stage showing variables that are new or have changed for each slave. And perhaps also a link within the pipeline stage view for each line where it is relevant (probably stage start and steps.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[JIRA] (JENKINS-39765) freeStyleJob should support an update argument to specify if you want or not override

2016-11-16 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon commented on  JENKINS-39765  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: freeStyleJob should support an update argument to specify if you want or not override   
 

  
 
 
 
 

 
 I think that the point here should not to control job's overriding overwriting in every cases, but only if one of the jobs (re)generated within a DSL script has the same name as the seed job. In other words,it should only control the case where the "tryDSL" seed job's DSL scripts tries to create a job named "tryDSL" in the same folder than the seed job. It is actually a security option, which should be activated by default and lead to a seed job failure if the case is encountered.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-30108) NumberFormatException when numBuilds is empty

2016-11-09 Thread jlpinar...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jlpinardon commented on  JENKINS-30108  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NumberFormatException when numBuilds is empty   
 

  
 
 
 
 

 
 It still occurs with jenkins 2.7.2 and plot 1.9.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [checkstyle-plugin] (JENKINS-24942) Trend graphs are not shown for some projects

2015-12-15 Thread jlpinar...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jlpinardon commented on  JENKINS-24942 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Trend graphs are not shown for some projects  
 
 
 
 
 
 
 
 
 
 
I confirm that upgrading from Findbugs 4.56 to Findbugs 4.60 we also observe that trends have disappeared. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [artifactory-plugin] (JENKINS-21235) Artifactory plugin is configured to run post-build, but actually runs pre-"Post-Steps"

2015-07-29 Thread jlpinar...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jlpinardon commented on  JENKINS-21235 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Artifactory plugin is configured to run post-build, but actually runs pre-"Post-Steps"  
 
 
 
 
 
 
 
 
 
 
This is still the case with 1.554.2.2 jenkins version with maven_integration 2.3 and artifactory 2.2.3. Really annoying because we would like to also store within artifactory interesting files generated outside maven during the post step. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [groovy] (JENKINS-15516) System groovy script file succeeds on build slave when script does not exist

2013-04-12 Thread jlpinar...@java.net (JIRA)














































jlpinardon
 commented on  JENKINS-15516


System groovy script file succeeds on build slave when script does not exist















Additionnally, there is no alert on log console, which is a really a mess to understand why ... nothing occurs.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 


[JIRA] [parameterized-trigger] (JENKINS-8916) Allowing same type of parameter for triggered build more than once seems redundant

2013-04-09 Thread jlpinar...@java.net (JIRA)














































jlpinardon
 commented on  JENKINS-8916


Allowing same type of parameter for triggered build more than once seems redundant















Dear all,

I support several teams for which it is really annoying to not be able to add several property files.
So please could you either :

	let the possibility to add several times property file type
	or have a single property file type but allow to give a comma separated list of files.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.