[JIRA] (JENKINS-14158) Change to build timeout job configuration not saved

mwebber created JENKINS-14158

Change to build timeout job configuration not saved

Issue Type:	Bug
Assignee:	Kohsuke Kawaguchi
Components:	build-timeout
Created:	20/Jun/12 10:14 AM
Description:	I edit a job configuration and check (select) either the "Fail the build" or "Writing the build description" options, and click save. If I go back and look at the configuration, my changes were not saved. This problem occurs in build-timeout 1.10.
Project:	Jenkins
Priority:	Major
Reporter:	mwebber

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

Adam PAPAI commented on JENKINS-14158

Change to build timeout job configuration not saved

Fail the build is only available if you select the "Likely stuck". The UI is a little bit confusing.

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

 

Adam PAPAI edited a comment on JENKINS-14158

Change to build timeout job configuration not saved

It is fixen in the HEAD.

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

 

Adam PAPAI edited a comment on JENKINS-14158

Change to build timeout job configuration not saved

It is fixed in the HEAD.

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

 

Adam PAPAI edited a comment on JENKINS-14158

Change to build timeout job configuration not saved

Hm right. Same here.

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

Adam PAPAI commented on JENKINS-14158

Change to build timeout job configuration not saved

It seems it's fixed in git, just not released.

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

mwebber commented on JENKINS-14158

Change to build timeout job configuration not saved

How do we prompt the plugin maintainer to release?

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

lukas rytz commented on JENKINS-14158

Change to build timeout job configuration not saved

I saw here http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-14158-Change-to-build-timeout-job-configuration-not-saved-td4632182.html that "Fail the build is only available if you select the Likely stuck". In the current version of the plugin, you can select "Fail the build" indeed only on the "Likely stuck" option. This annoying - I'd like to mark my builds as failed after an absolute timeout...

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

Geoff Cummings commented on JENKINS-14158

Change to build timeout job configuration not saved

I would also like to mark the build as failed after an absolute timeout.

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

Eric Engstrom commented on JENKINS-14158

Change to build timeout job configuration not saved

We also have been holding back on version 1.9 (one one of our servers) of this plug in since it properly fails the build after an absolute timer timeout. What's not clear from the discussion here is if the fix in the repo both fixes the configuration saving issue but also fixes the confusing/inappropriate placement of the "fail the build" checkbox only under the "Likely stuck" option.

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

[RexHuang]

I would like this bug been fix like "mark the build as failed after an absolute timeout."

sogabe assigned JENKINS-14158 to sogabe

Change to build timeout job configuration not saved

Change By:	sogabe (28/Oct/12 7:14 AM)
Assignee:	Kohsuke Kawaguchi sogabe

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

sogabe commented on JENKINS-14158

Change to build timeout job configuration not saved

The following pull[1] request will fix. I'll merge it and release as 1.11. [1]https://github.com/jenkinsci/build-timeout-plugin/commit/8ec9d9f541c55ddf31fe6ee850a5dfe930d1b451

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

sogabe resolved JENKINS-14158 as Fixed

Change to build timeout job configuration not saved

fixed in 1.11
Change By:	sogabe (28/Oct/12 7:32 AM)
Status:	Open Resolved
Resolution:	Fixed

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