[JIRA] (JENKINS-14491) HTML Publisher Plugin Add button broken after 1.474 upgrade
Lothar Werzinger commented on JENKINS-14491 HTML Publisher Plugin Add button broken after 1.474 upgrade Is there any update if this is a core problem or if it needs fixing in the plugin? I use Jenkins from the Linux package management and I can't simply install an older version like 1.473 P.S. If there's a way to fix this in the plugin itself, should it not be done in any case? 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
[JIRA] (JENKINS-12263) Button Don't keep this build forever doesn't work on a multi-configuration build when its next build is partial
Lothar Werzinger commented on JENKINS-12263 Button Dont keep this build forever doesnt work on a multi-configuration build when its next build is partial I don't see why the user should not be able to force the deletion of a build (even if the N+1 build is partial). Especially while developing a matrix build (adding more steps incrementally) it's very useful to just zap all the old (obsolete) builds regardless of the state of the N+1 build. 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
[JIRA] (JENKINS-12263) Button Don't keep this build forever doesn't work on a multi-configuration build when its next build is partial
Lothar Werzinger edited a comment on JENKINS-12263 Button Dont keep this build forever doesnt work on a multi-configuration build when its next build is partial I don't see why the user should not be able to force the deletion of a build (even if the N+1 build is partial). Especially while developing a matrix build (adding more steps incrementally) it's very useful to just zap all the old (obsolete) builds regardless of the state of the N+1 build. Especially as even failed builds are marked as "Keep this build forever" if N+1 is partial. 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
[JIRA] (JENKINS-12797) Don't Keep this build forever button doesn't work on some matrix job and prevent removing old build
Lothar Werzinger commented on JENKINS-12797 Dont Keep this build forever button doesnt work on some matrix job and prevent removing old build I'm seeing the same issue 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
[JIRA] (JENKINS-12797) Don't Keep this build forever button doesn't work on some matrix job and prevent removing old build
Lothar Werzinger edited a comment on JENKINS-12797 Dont Keep this build forever button doesnt work on some matrix job and prevent removing old build I'm seeing the same issue (Jenkins ver. 1.474) 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
[JIRA] (JENKINS-12797) Don't Keep this build forever button doesn't work on some matrix job and prevent removing old build
Lothar Werzinger edited a comment on JENKINS-12797 Dont Keep this build forever button doesnt work on some matrix job and prevent removing old build I'm seeing the same issue (Jenkins ver. 1.474) I have a 2x3 matrix with a touchstone build 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
[JIRA] (JENKINS-10580) Can't use ${ENV_VAR} in branch specifier
Lothar Werzinger
commented on JENKINS-10580
Cant use ${ENV_VAR} in branch specifier
I have a similar problem, where I would like to use a parameter from the Release Plugin and the git plugin does not pick it up.
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
[JIRA] (JENKINS-8563) REOPEN -Can't use parameters in git plugin Branches to build configuration
Lothar Werzinger commented on JENKINS-8563 REOPEN -Cant use parameters in git plugin Branches to build configuration It unfortunately also fails when trying to use a parameter from the Release Plugin. 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
[JIRA] (JENKINS-8225) Additional confiuguration files to back up
Lothar Werzinger commented on JENKINS-8225 Additional confiuguration files to back up +1 for user editable patterns 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
[JIRA] (JENKINS-8225) Additional confiuguration files to back up
Lothar Werzinger edited a comment on JENKINS-8225 Additional confiuguration files to back up +1 for user editable patterns (multiple) 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
