[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Lakshya Kapoor edited a comment on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins I ran into this right after upgrading to 2.164.2 today. Clearing the /caches folder and restarting Jenkins got rid of the error.*EDIT*: The error returns every time I reboot Jenkins after updating a plugin . Manually restarting the service (on Windows) fixes it until the next reboot for plugin updates ... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.197354.1549278137000.20141.1559594100713%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Lakshya Kapoor edited a comment on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins I ran into this right after upgrading to 2.164.2 today. Clearing the /caches folder and restarting Jenkins got rid of the error. *EDIT*: The error returns every time I reboot Jenkins. Manually restarting the service (on Windows) fixes it until the next reboot... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.197354.1549278137000.20111.1559593981354%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Lakshya Kapoor edited a comment on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins I ran into this right after upgrading to 2.164.2 today. Clearing the /caches folder and restarting Jenkins got rid of the error. *EDIT*: The error returns every time I reboot Jenkins. Manually restarting the service (on Windows) fixes it until the next reboot... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.197354.1549278137000.20109.1559593981274%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Lakshya Kapoor commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins I ran into this right after upgrading to 2.164.2 today. Clearing the /caches folder and restarting Jenkins got rid of the error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.197354.1549278137000.5755.1558394761429%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Lakshya Kapoor commented on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED I am also glad to confirm that currentBuild.currentResult in v1.3.7-beta1 works as it did in v1.3.4.1. Thanks again! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Lakshya Kapoor commented on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED Thanks, Andrew Bayer! I'll test 1.3.7-beta-1 on Monday and report back. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Lakshya Kapoor edited a comment on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED Thanks, [~abayer] and [~dnusbaum] ! I'll test 1.3.7-beta-1 on Monday and report back. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title
Lakshya Kapoor edited a comment on JENKINS-56402
Re: Declarative Pipeline shows SUCCESS even though job FAILED
@Philip{quote}The condition blocks are executed in the order shown below.{quote}Yea, I had a feeling it would be was that way, but wasn't sure. Thanks for pointing it out! :) @Devin - I like your idea for the new read-only variable.P.S. JIRA is giving me a "Communications Breakdown" error when I @ your usernames. Was getting it since yesterday afternoon, but just figured it out it is related to tagging people.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title
Lakshya Kapoor edited a comment on JENKINS-56402
Re: Declarative Pipeline shows SUCCESS even though job FAILED
@Philip {quote}The condition blocks are executed in the order shown below.{quote}Yea, I had a feeling it would be that way, but wasn't sure. Thanks for pointing it out! @Devin - I like your idea for the new read-only variable.P.S. JIRA is giving me a "Communications Breakdown" error when I @ your usernames.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title
Lakshya Kapoor edited a comment on JENKINS-56402
Re: Declarative Pipeline shows SUCCESS even though job FAILED
@Philip{quote}The condition blocks are executed in the order shown below.{quote}Yea, I had a feeling it would be that way, but wasn't sure. Thanks for pointing it out!@Devin - I like your idea for the new read-only variable.P.S. JIRA is giving me a "Communications Breakdown" error when I @ your usernames.Was getting it since yesterday afternoon, but just figured it out it is related to tagging people.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Lakshya Kapoor commented on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED The condition blocks are executed in the order shown below. Yea, I had a feeling it would be that way, but wasn't sure. Thanks for pointing it out! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Lakshya Kapoor updated an issue Jenkins / JENKINS-56402 Declarative Pipeline shows SUCCESS even though job FAILED Change By: Lakshya Kapoor Comment: Test. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Lakshya Kapoor commented on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED Test. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title
Lakshya Kapoor edited a comment on JENKINS-56402
Re: Declarative Pipeline shows SUCCESS even though job FAILED
Hi [~dnusbaum], my use case is similar to [~pzozobrado]'s. I am sending an email notification in my post step ({{always}}) and I am using {{currentBuild.currentResult}} to determine the font color for the build status and the subject line in the email:{code:java}def statusColor = colorCodeByStatus(currentBuild.currentResult) // $BUILD_STATUS font color...// Returns HEX code based on given build statusdef colorCodeByStatus(status) { if(status == 'SUCCESS') {'#28B463' // Green } else if(status == 'FAILURE') {'#DF0101' // Red } else { // Aborted or Unstable'#9E9E9E' // Gray }}{code}I am not sure if this violates any sort of best practices, but this could be a workaround for such use cases:{code:java}post { success { currentBuild.currentResult = 'SUCCESS' } unstable { currentBuild.currentResult = 'UNSTABLE' } failure { currentBuild.currentResult = 'FAILURE' } always {dir(path: 'report') { executePostSteps(JOB_NAME)} }} // post{code} I haven't had a chance to test it yet, so please feel free to critique it.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title
Lakshya Kapoor commented on JENKINS-56402
Re: Declarative Pipeline shows SUCCESS even though job FAILED
Hi Devin Nusbaum, my use case is similar to Philip Zozobrado's. I am sending an email notification in my post step (always) and I am using currentBuild.currentResult to determine the font color for the build status and the subject line in the email:
def statusColor = colorCodeByStatus(currentBuild.currentResult) // $BUILD_STATUS font color
...
// Returns HEX code based on given build status
def colorCodeByStatus(status) {
if(status == 'SUCCESS') {
'#28B463' // Green
} else if(status == 'FAILURE') {
'#DF0101' // Red
} else { // Aborted or Unstable
'#9E9E9E' // Gray
}
}
I am not sure if this violates any sort of best practices, but this could be a workaround for such use cases:
post {
success {
currentBuild.currentResult = 'SUCCESS'
}
unstable {
currentBuild.currentResult = 'UNSTABLE'
}
failure {
currentBuild.currentResult = 'FAILURE'
}
always {
dir(path: 'report') {
executePostSteps(JOB_NAME)
}
}
} // post
I haven't had a chance to test it yet, so please feel free to critique it.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Lakshya Kapoor commented on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED I investigated this issue and looks like it introduced by the Pipeline: Declarative plugin v1.3.5. The offending commit seems to be https://github.com/jenkinsci/pipeline-model-definition-plugin/commit/39c7ed1e153bc3ae10a8aaf77ccc3bc7da2dc93a. Downgrading to v1.3.4.1 is the workaround for now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title
Lakshya Kapoor edited a comment on JENKINS-56402
Re: Declarative Pipeline shows SUCCESS even though job FAILED
I'm experiencing the same. {{currentBuild.currentResult}} for all failed and aborted builds returns "SUCCESS". Same when using {{$BUILD_STATUS}} through the {{emailext}} plugin.Using Jenkins version 2.150.3 and Pipeline 2.6. All pipeline related plugins are at the latest version as well. *EDIT*: I investigated this issue and looks like it introduced by the {{Pipeline: Declarative}} plugin v1.3.5. The offending commit seems to be [https://github.com/jenkinsci/pipeline-model-definition-plugin/commit/39c7ed1e153bc3ae10a8aaf77ccc3bc7da2dc93a|https://github.com/jenkinsci/pipeline-model-definition-plugin/commit/39c7ed1e153bc3ae10a8aaf77ccc3bc7da2dc93a].{color:#00875a}*Downgrading to v1.3.4.1 is the workaround for now.*{color}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title
Lakshya Kapoor edited a comment on JENKINS-56402
Re: Declarative Pipeline shows SUCCESS even though job FAILED
I'm experiencing the same. {{currentBuild.currentResult}} for all failed and aborted builds returns "SUCCESS". Same when using {{$BUILD_STATUS}} through the {{emailext}} plugin.Using Jenkins version 2.150.3 and Pipeline 2.6. All pipeline related plugins are at the latest version as well. *EDIT*: I investigated this issue and looks like it introduced by the {{Pipeline: Declarative}} plugin v1.3.5. The offending commit seems to be [39c7ed1e153bc3ae10a8aaf77ccc3bc7da2dc93a|https://github.com/jenkinsci/pipeline-model-definition-plugin/commit/39c7ed1e153bc3ae10a8aaf77ccc3bc7da2dc93a].{color:#00875a}*Downgrading to v1.3.4.1 is the workaround for now.*{color}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title
Lakshya Kapoor edited a comment on JENKINS-56402
Re: Declarative Pipeline shows SUCCESS even though job FAILED
I'm experiencing the same. {{currentBuild.currentResult}} for all failed and aborted builds returns "SUCCESS". Same when using {{$BUILD_STATUS}} through the {{emailext}} plugin.Using Jenkins version 2.150.3 and Pipeline 2.6. All pipeline related plugins are at the latest version as well.*EDIT*: I investigated this issue and looks like it introduced by the {{Pipeline: Declarative}} plugin v1.3.5. The offending commit seems to be [ https://github.com/jenkinsci/pipeline-model-definition-plugin/commit/ 39c7ed1e153bc3ae10a8aaf77ccc3bc7da2dc93a|https://github.com/jenkinsci/pipeline-model-definition-plugin/commit/39c7ed1e153bc3ae10a8aaf77ccc3bc7da2dc93a].{color:#00875a}*Downgrading to v1.3.4.1 is the workaround for now.*{color}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Lakshya Kapoor commented on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED I'm experiencing the same. currentBuild.currentResult for all failed and aborted builds returns "SUCCESS". Same when using $BUILD_STATUS through the emailext plugin. Using Jenkins version 2.150.3 and Pipeline 2.6. All pipeline related plugins are at the latest version as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
