[JIRA] [disk-usage-plugin] (JENKINS-26496) Trying to get the DateFormat as build ID
Martin Beller commented on JENKINS-26496 Trying to get the DateFormat as build ID I installed the PR build from https://jenkins.ci.cloudbees.com/job/plugins/job/disk-usage-plugin/75/org.jenkins-ci.plugins$disk-usage/ as proposed by Daniel. This solves the problem 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.
[JIRA] [disk-usage-plugin] (JENKINS-26496) Trying to get the DateFormat as build ID
Martin Beller commented on JENKINS-26496 Trying to get the DateFormat as build ID Download disk-usage-0.25-SNAPSHOT.hpi from the URL mentioned above. Go to the Plugin Manager and click on Advanced. Select the downloaded file below the text You can upload a .hpi file to install a plugin from outside the central plugin repository.. Upload the plugin. I hope this helps. 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.
[JIRA] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Martin Beller commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration @Daniel: Do you get the same Warning (label assignment is using legacy '_.assignedLabelString') when pressing the Save/Apply button? Did you verify that the config.xml file of the related job is updated properly: assignedNodebuildServer/assignedNode canRoamfalse/canRoam 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.
[JIRA] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Martin Beller updated JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration screenshot before pressing the Apply or Save button Change By: Martin Beller (23/Nov/14 9:08 AM) Attachment: MBeTestConfig[Jenkins].png 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.
[JIRA] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Martin Beller
commented on JENKINS-25533
Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
dan...@beckweb.net: Please find attached the screenshot {{MBeTest Config Jenkins.png}} before I press the Save or Apply button. The result is the WARNING: label assignment is using legacy '_.assignedLabelString' and the config.xml of the related job is not updated properly.
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.
[JIRA] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Martin Beller edited a comment on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Daniel Beck: Please find attached the screenshot MBeTest Config Jenkins.png before I press the Save or Apply button. The result is the WARNING: label assignment is using legacy '_.assignedLabelString' and the config.xml of the related job is not updated properly. 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.
[JIRA] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Martin Beller commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration I tested with Jenkins 1590 and the problem is still not solved (as indicated by Andreas above). Here are the logs in case the job configuration is saved: Nov 22, 2014 10:34:06 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.tasks.LogRotator Nov 22, 2014 10:34:06 AM hudson.model.AbstractProject submit WARNING: label assignment is using legacy '_.assignedLabelString' Nov 22, 2014 10:34:06 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.plugins.build_timeout.impl.AbsoluteTimeOutStrategy Nov 22, 2014 10:34:06 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.plugins.build_timeout.operations.FailOperation Nov 22, 2014 10:34:06 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.tasks.Shell Nov 22, 2014 10:34:06 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.plugins.warnings.WarningsPublisher Nov 22, 2014 10:34:06 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.tasks.Mailer Any other information I could provide to track down the 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 -- 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] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Martin Beller commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration An here are the logs if I do the same operation with Jenkins 1588 (problem does not occur): Nov 22, 2014 10:51:00 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.tasks.LogRotator Nov 22, 2014 10:51:00 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.plugins.build_timeout.impl.AbsoluteTimeOutStrategy Nov 22, 2014 10:51:00 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.plugins.build_timeout.operations.FailOperation Nov 22, 2014 10:51:00 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.tasks.Shell Nov 22, 2014 10:51:00 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.plugins.warnings.WarningsPublisher Nov 22, 2014 10:51:00 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON WARNING: 'stapler-class' is deprecated: hudson.tasks.Mailer Nov 22, 2014 10:52:07 AM hudson.slaves.SlaveComputer tryReconnect 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.
[JIRA] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Martin Beller
commented on JENKINS-25533
Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
I could reproduce the issue with a Freestyle test project. Here is the submitted JSON (Firefox 33.1.1):
{"name": "MBeTest", "description": "", "": ["", "0"], "logrotate": false, "buildDiscarder": {"stapler-class": "hudson.tasks.LogRotator", "daysToKeepStr": "", "numToKeepStr": "", "artifactDaysToKeepStr": "", "artifactNumToKeepStr": ""}, "properties": {"stapler-class-bag": "true", "hudson-model-ParametersDefinitionProperty": {}, "org-jenkinsci-plugins-envinject-EnvInjectJobProperty": {}}, "disable": false, "concurrentBuild": false, "hasSlaveAffinity": true, "label": "buildServer", "hasCustomQuietPeriod": false, "quiet_period": "5", "hasCustomScmCheckoutRetryCount": false, "scmCheckoutRetryCount": "0", "blockBuildWhenUpstreamBuilding": false, "blockBuildWhenDownstreamBuilding": false, "hasCustomWorkspace": false, "customWorkspace": "", "displayNameOrNull": "", "scm": {"value": "0"}, "core:apply": "true"}
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.
[JIRA] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Martin Beller commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration We upgraded from 1.588 to 1.589 and see this behaviour with the newest version. A downgrade to 1.588 solves the problem. 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.
