[JIRA] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration

2014-11-26 Thread andreas.podskal...@siemens.com (JIRA)














































podskalsky
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















I can confirm that the ClearCase plugin is the problem.
I've uninstalled this plugin (I don't need it) and saving data is now OK.



























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

2014-11-25 Thread bkris...@ra.rockwell.com (JIRA)














































Brian Krische
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















I did quite a bit of testing an narrowed it down. The issue occurs in Jenkins versions 1.589 or greater when the ClearCase plugin is installed. I didn't test all of the plugins Reinhard Karbas had installed, but I first noticed it with the ClearCase plugin. Here are some steps to reproduce:


	Install Jenkins 1.589 or higher
	Configure a node (Ex. master) with a label of "test"
	Create a new Freestyle job and restrict it to the "test" node label
	Save the job
	Reopen the job's configure page and notice the node label restriction is gone.





























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

2014-11-25 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 assigned  JENKINS-25533 to Matthew Moore



Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
















Change By:


Jesse Glick
(25/Nov/14 6:25 PM)




Assignee:


MatthewMoore



























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

2014-11-25 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















Great find Brian!



Could the watchers please chime in?


	Do you have the ClearCase plugin installed?
	
		Does the issue disappear with the plugin disabled (if unused)?
	
	
	Please provide the list of plugins (+versions) if not.





























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

2014-11-25 Thread kuypers.d...@googlemail.com (JIRA)














































Dirk Kuypers
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















I can confirm that we use the ClearCase plugin in latest version 1.5.3.



























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

2014-11-25 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















I can reproduce the problem on a newly set up instance. Disable all bundled plugins, install ClearCase plugin, restart, and there it is.

label assignment is using legacy '_.assignedLabelString'



























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

2014-11-25 Thread dan...@beckweb.net (JIRA)












































 
Daniel Beck
 edited a comment on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
















I can reproduce the problem on a newly set up instance. Disable all bundled plugins, install ClearCase plugin, restart, and there it is.

label assignment is using legacy '_.assignedLabelString'

And here's the problem:
https://github.com/jenkinsci/clearcase-plugin/blob/4e1ac05ac09f17326e1fab4d6af7aa5fda297f94/src/main/resources/hudson/plugins/clearcase/viewstorage/ServerViewStorage/config.jelly#L28



























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

2014-11-24 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















As I wrote above, I'm sending almost exactly the same data, and it's processed correctly on the server, despite using 1.590. Uploading another screenshot of the same form field doesn't help (or I don't understand what it signifies, in that case, please explain).

Is anyone able to reproduce this issue on a pristine Jenkins instance? How about after installing all the plugins you have on your prod instance (in the same versions)? If it works out of the box but installing plugins results in a problem, try to determine which plugin is responsible by disabling/enabling them until you find the culprit.



























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

2014-11-24 Thread martin.bel...@alcatel-lucent.com (JIRA)














































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

2014-11-24 Thread reinhard.kar...@unify.com (JIRA)














































Reinhard Karbas
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















I see the same issue after upgrading from 1.588 to 1.590
I have the same plugins in both versions and it works with 1.588 and is broken in 1.590



























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

2014-11-24 Thread mweb...@java.net (JIRA)














































mwebber
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















Can I suggest that people who have this problem give a list of the plugins that they have.
Thanks



























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

2014-11-24 Thread reinhard.kar...@unify.com (JIRA)














































Reinhard Karbas
 updated  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
















Change By:


Reinhard Karbas
(24/Nov/14 10:14 PM)




Attachment:


Jenkins-plugins-rk.doc



























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

2014-11-24 Thread reinhard.kar...@unify.com (JIRA)














































Reinhard Karbas
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















Added my list of plugins as attachment (jenkins-plugins-rk.doc)



























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

2014-11-23 Thread martin.bel...@alcatel-lucent.com (JIRA)














































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

2014-11-23 Thread martin.bel...@alcatel-lucent.com (JIRA)














































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

2014-11-23 Thread martin.bel...@alcatel-lucent.com (JIRA)












































 
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

2014-11-23 Thread andreas.podskal...@siemens.com (JIRA)














































podskalsky
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















@Martin: thank you for your additional input and log files.
On my server I've downgraded to 1.588. So I'm not not able to generate these log files.




























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

2014-11-22 Thread martin.bel...@alcatel-lucent.com (JIRA)














































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

2014-11-22 Thread martin.bel...@alcatel-lucent.com (JIRA)














































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

2014-11-22 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















Martin Beller: What kind of project (Freestyle, Maven, Matrix/multiconfig, MultiJob, Build Flow, Workflow, ...) is that?

I now tried it on a regular instance with 1.590. Still cannot reproduce it with freestyle projects.



























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

2014-11-22 Thread martin.bel...@alcatel-lucent.com (JIRA)














































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

2014-11-22 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















To clarify, after you submit this, you click "Configure", and "Restrict where" is not checked, and/or the label _expression_ is empty? And submitting the form results in the warning?

Still cannot reproduce this (on ~1.592 again). My JSON is identical except for the presumably bogus {{"": , 0}} element, I even installed env-inject to get the empty property.



























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

2014-11-20 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















podskalsky: You edited your comment to include that information, so it seemed you considered that important for some reason.



























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

2014-11-20 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















I cannot reproduce this on a pristine Jenkins 1.592 SNAPSHOT (current development version) with either freestyle or Maven projects. Adding the restriction works, and subsequent edits of the form keep it unmodified. I can see no changes between 1.590 and my version.

Any further information you could provide under what circumstances the issue appears? Could someone maybe capture the form submit HTTP request of their browsr when configuring a test project, and provide the submitted form JSON?



























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

2014-11-17 Thread andreas.podskal...@siemens.com (JIRA)














































podskalsky
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















Bug still existing at Jenkins 1.590



























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

2014-11-17 Thread andreas.podskal...@siemens.com (JIRA)














































podskalsky
 updated  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
















Change By:


podskalsky
(17/Nov/14 9:32 AM)




Environment:


Jenkinsver.1.589
,1.590
LatestPluginsSolaris10Firefox+ChromeMavenBuildJob



























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

2014-11-17 Thread andreas.podskal...@siemens.com (JIRA)














































podskalsky
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















changes at config.xml after only pressing "Save/Apply":

$ diff config.xml config.ok
57c57,58
   canRoamtrue/canRoam

   assignedNodemaster/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

2014-11-17 Thread andreas.podskal...@siemens.com (JIRA)












































 
podskalsky
 edited a comment on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
















The "newline" of my config.xml is removed and alse the parameters assignedNode + canRoam ...


$ diff config.xml config.ok
Warning: missing newline at end of file config.xml
57c57,58
   canRoamtrue/canRoam

   assignedNodemaster/assignedNode
   canRoamfalse/canRoam
197c198
 /maven2-moduleset

 /maven2-moduleset






























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

2014-11-17 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















podskalsky: Jenkins does not add trailing newlines to XML files, I assume those are yours? (JENKINS-25628)



























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

2014-11-17 Thread andreas.podskal...@siemens.com (JIRA)














































podskalsky
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















The trailing newlines are not the problem (I've checked it) but the changed xml tag canRoam and the removed tag assignedNode !!!



























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

2014-11-11 Thread o.v.nenas...@gmail.com (JIRA)












































 
Oleg Nenashev
 edited a comment on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
















Related to JENKINS-25372, which has been caused by https://github.com/jenkinsci/jenkins/pull/1414. There were new fixes in 1.589.
Have you seen the issue on the previous versions? (it would be great to know this version)



























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

2014-11-11 Thread andreas.podskal...@siemens.com (JIRA)














































podskalsky
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















I've updated from Jenkins ver. 1.585 to 1.589 - before this update everything was OK!



























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

2014-11-11 Thread andreas.podskal...@siemens.com (JIRA)














































podskalsky
 updated  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
















Change By:


podskalsky
(11/Nov/14 9:44 AM)




Environment:


Jenkinsver.1.589LatestPluginsSolaris10Firefox+Chrome
MavenBuildJob



























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

2014-11-11 Thread andreas.podskal...@siemens.com (JIRA)














































podskalsky
 updated  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
















Change By:


podskalsky
(11/Nov/14 9:44 AM)




Attachment:


2014-11-1110_42_32-TicTacToe_Maven_externalConfig[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

2014-11-11 Thread andreas.podskal...@siemens.com (JIRA)














































podskalsky
 updated  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
















Change By:


podskalsky
(11/Nov/14 9:44 AM)




Environment:


Jenkinsver.1.589LatestPluginsSolaris10
Firefox+Chrome



























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

2014-11-11 Thread kuypers.d...@googlemail.com (JIRA)














































Dirk Kuypers
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















We updated from 1.588 and see this behaviour with the newest version. Downgrade will take another hour



























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

2014-11-11 Thread o.v.nenas...@gmail.com (JIRA)














































Oleg Nenashev
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















Added Matthew Moore to Cc



























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

2014-11-11 Thread martin.bel...@alcatel-lucent.com (JIRA)














































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.


[JIRA] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration

2014-11-11 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















What project types are affected?



























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

2014-11-10 Thread podskal...@java.net (JIRA)














































podskalsky
 created  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


11/Nov/14 7:34 AM



Description:


The host parameters for "Restrict where this project can be run" are disabled removed/disabled after Save/Apply of Job Configuration !!!

The builds are running on any host not at the specified ones 




Environment:


Jenkins ver. 1.589

Latest Plugins

Solaris 10




Project:


Jenkins



Priority:


Blocker



Reporter:


podskalsky

























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

2014-11-10 Thread andreas.podskal...@siemens.com (JIRA)














































podskalsky
 updated  JENKINS-25533


Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
















Change By:


podskalsky
(11/Nov/14 7:47 AM)




Description:


ThehostparametersforRestrictwherethisprojectcanberunare
disabled
removed/disabledafterSave/ApplyofJobConfiguration!!!Thebuildsarerunningonanyhostnotatthespecifiedones:-(



























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.