[JIRA] (JENKINS-36496) Publish from pipeline
Title: Message Title Timo Ulich closed an issue as Duplicate Sorry, closing as duplicate of JENKINS-28335 Jenkins / JENKINS-36496 Publish from pipeline Change By: Timo Ulich Status: Open Closed Resolution: Duplicate 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-36496) Publish from pipeline
Title: Message Title Timo Ulich created an issue Jenkins / JENKINS-36496 Publish from pipeline Issue Type: New Feature Assignee: Mark Waite Components: git-plugin Created: 2016/Jul/07 12:41 PM Priority: Minor Reporter: Timo Ulich It would be nice to be able to use the git publisher features in a pipeline job, instead of issuing shell commands that create a tag / push it. This is especially useful because you can then re-use the git repository credentials that were used for the checkout. Right now this requires us to also have the SSH key on the machine, just for pushing... Add Comment
[JIRA] (JENKINS-36415) Stage is displayed as failed although it completed successfully after retrying
Title: Message Title
Timo Ulich updated an issue
Jenkins / JENKINS-36415
Stage is displayed as failed although it completed successfully after retrying
Change By:
Timo Ulich
We have implemented a retry mechanism in our pipeline and if the step fails in the first run, then is retried and then succeeds, the stage is still shown as failed, but the build is green.See the attached screenshot. The second stage in Build #124 is shown as failed which was retried once. To reproduce:{code}node {stage "1"stage "2"def counter = 0waitUntil {counter++try {if (counter == 1) {sh "false"}return true}catch (e) {return false}}stage "3"}{code}
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
[JIRA] (JENKINS-36415) Stage is displayed as failed although it completed successfully after retrying
Title: Message Title
Timo Ulich updated an issue
Jenkins / JENKINS-36415
Stage is displayed as failed although it completed successfully after retrying
Change By:
Timo Ulich
We have implemented a retry mechanism in our pipeline and if the step fails in the first run, then it is retried and then succeeds, the stage is still shown as failed, but the build is green.See the attached screenshot. The second stage is shown as failed which was retried once. To reproduce:{code}node {stage "1"stage "2"def counter = 0waitUntil {counter++try {if (counter == 1) {sh "false"}return true}catch (e) {return false}}stage "3"}{code}
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
[JIRA] (JENKINS-36415) Stage is displayed as failed although it completed successfully after retrying
Title: Message Title
Timo Ulich created an issue
Jenkins / JENKINS-36415
Stage is displayed as failed although it completed successfully after retrying
Issue Type:
Bug
Assignee:
Sam Van Oort
Attachments:
screenshot.png
Components:
pipeline-stage-view-plugin
Created:
2016/Jul/04 1:40 PM
Environment:
Jenkins 2.11 pipeline-stage-view-plugin 1.5
Priority:
Minor
Reporter:
Timo Ulich
We have implemented a retry mechanism in our pipeline and if the step fails in the first run, then is retried and then succeeds, the stage is still shown as failed, but the build is green. See the attached screenshot. The second stage in Build #124 is shown as failed which was retried once. To reproduce:
node {
stage "1"
stage "2"
def counter = 0
waitUntil {
counter++
try {
if (counter == 1) {
sh "false"
}
return true
}
catch (e) {
return false
}
}
stage "3"
}
[JIRA] [core] (JENKINS-25326) Throttle Concurrent Builds doesn't work when builds are in cloudbees folders
Timo Ulich commented on JENKINS-25326 Throttle Concurrent Builds doesnt work when builds are in cloudbees folders I am experiencing the same problem with jenkins 1.596.1 LTS, cloudbees folder plugin 4.7 and Throttle Concurrent Builds Plug-in 1.8.4 (Matrix Project Plugin is installed). This happens with newly created jobs and jobs that existed before restarting jenkins. Can I provide any other information? 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/d/optout.
