[JIRA] [workflow-plugin] (JENKINS-26535) DescribableHelper does not handle wildcards well
Title: Message Title
Alex Ouzounis edited a comment on JENKINS-26535
Re: DescribableHelper does not handle wildcards well
trying to use properties in a MultiBranch Pipeline like so:{code:java}properties( [ $class: 'GithubProjectProperty', displayName: '', projectUrlStr: 'https:// git github . corp.adobe. com/ hoolihan xxx / lumberyard/ yyy ' ] ){code}but I get:{code:java}java.lang.UnsupportedOperationException: JENKINS-26535: do not know how to handle java.util.List{code}My understanding from http://stackoverflow.com/questions/35370810/how-do-i-use-jenkins-pipeline-properties-step#35471196 was that the properties syntax was working but maybe i am wrong.-Jenkins LTS 1.642.2 , Pipeline Branch 1.15
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [workflow-plugin] (JENKINS-26535) DescribableHelper does not handle wildcards well
Title: Message Title
Alex Ouzounis edited a comment on JENKINS-26535
Re: DescribableHelper does not handle wildcards well
trying to use properties in a MultiBranch Pipeline like so: ``` {code:java} properties( [ $class: 'GithubProjectProperty', displayName: '', projectUrlStr: 'https://git.corp.adobe.com/hoolihan/lumberyard/' ] ) ``` {code} but I get: ``` {code:java} java.lang.UnsupportedOperationException: JENKINS-26535: do not know how to handle java.util.List ``` {code} My understanding from http://stackoverflow.com/questions/35370810/how-do-i-use-jenkins-pipeline-properties-step#35471196 was that the properties syntax was working but maybe i am wrong.-Jenkins LTS 1.642.2 , Pipeline Branch 1.15
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [workflow-plugin] (JENKINS-26535) DescribableHelper does not handle wildcards well
Title: Message Title Alex Ouzounis commented on JENKINS-26535 Re: DescribableHelper does not handle wildcards well trying to use properties in a MultiBranch Pipeline like so: ``` properties( [ $class: 'GithubProjectProperty', displayName: '', projectUrlStr: 'https://git.corp.adobe.com/hoolihan/lumberyard/' ] ) ``` but I get: ``` java.lang.UnsupportedOperationException: JENKINS-26535: do not know how to handle java.util.List ``` My understanding from http://stackoverflow.com/questions/35370810/how-do-i-use-jenkins-pipeline-properties-step#35471196 was that the properties syntax was working but maybe i am wrong. Jenkins LTS 1.642.2 , Pipeline Branch 1.15 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Alex Ouzounis commented on JENKINS-30744 Re: multibranch issues if branch contains / Jesse Glick has this been released in the workflow (pipeline the past month) plugin Alex Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Alex Ouzounis edited a comment on JENKINS-30744 Re: multibranch issues if branch contains / [~jglick] has this been released in the workflow (pipeline the past month) plugin ? ;)Alex Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Alex Ouzounis commented on JENKINS-30744 Re: multibranch issues if branch contains / now this is pure genius! We will try this ASAP Also shows how flexible workflow is with the JenkinsFile definitions though. Many thanks Joost van der Griendt !! We owe you a beer ! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Alex Ouzounis commented on JENKINS-30744 Re: multibranch issues if branch contains / Jesse Glick So my understanding from the above is that for multi branch this is considered resolved but if we want to make use of multi branch with gitflow on Windows jenkins slaves where our git repo has branches like feature/XXX hotfix/XXX etc we have to either fork and hack this plugin or hope someone resolves it in the durable task ? I am just trying to understand the possible ways forward as we really like the workflow plugin but can't use it basically due to the above. Alex Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Alex Ouzounis commented on JENKINS-30744 Re: multibranch issues if branch contains / Joost van der Griendt works as expected, the problem has now gone away. many thanks for sharing your workaround Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ci-game-plugin] (JENKINS-3575) authenticated users can modify their own scores
Title: Message Title Alex Ouzounis commented on JENKINS-3575 Re: authenticated users can modify their own scores Nice! Can you submit a pull request? Alex Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-26771) Error when using Integrate to upstream upon successful build on branch project
Alex Ouzounis commented on JENKINS-26771 Error when using Integrate to upstream upon successful build on branch project Hi all, I had the same issues, it ended up being unresolved vars in the SVNUrl. I would suggest you use the script console to see the SVNUrl returned. Are you using the inheritance plugin by any chance? Alex 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] [ci-game-plugin] (JENKINS-3575) authenticated users can modify their own scores
Alex Ouzounis reopened JENKINS-3575 authenticated users can modify their own scores a user can inspect the element, remove the disabled="disabled" and readonly="readonly", edit the score and save! how can we make sure that someone cannot edit the score ? Change By: Alex Ouzounis (20/Jan/15 7:11 PM) Resolution: Fixed Status: Resolved Reopened 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] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node Pull request: https://github.com/jenkinsci/subversion-plugin/commit/6496d7fa3623408a7af571601deac75c8cc29dcb When comparing builds make sure the environment used is based on the system env vars otherwise the comparison is not fair. Use the incoming build's system environment variables. Please review and merge 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] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node My interpretation was slightly wrong. Its not the master and a slave being compared but its lastBuild and lastCompletetedBuild. While a build is running these two are not the same and if those two builds were executed in two different slaves with two different environments then the comparison is not fair. I updated the pull request such that when the two urls are compared the environment from lastBuild is used for both builds. That way if svn related vars are different, that will not affect the result of the comparison 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] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis updated JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node Change By: Alex Ouzounis (03/Sep/14 9:28 AM) Description: Theissueathandisthefollowing:Projectcontainsandsvnurloftheform:$SVN_ROOT_PATH/trunkEachnodesets$SVN_ROOT_PATHtotheSVNmirrorclosertothenodelocation.Thisallowsustohavefastcheckoutsetc.ProblemnowisthatJenkinsseems tothink thatthemasterevaluatedSVNURLisdifferentthantheworkspacecheckoutpathofaslaveandtriggersanewbuild.Thishappensuntilithappensthattheslavethatpicksthebuildisusingthesamemirrorasthemaster.Settingpollingtomasteronly(viathemagicproperty)doesnotfixtheissuesincetheproblemisnotpollingbutJenkinstryingtobesmartanddetectingthattheworkspacehasadifferentSVNURLthantheconfiguration.NotsurehowtotacklethisbutIamhavingalook. 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] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node It seems to me that this "feature" of detecting a configuration change or mismatch between config and last build during polling is not ideal. Maybe trying to resolve the master "raw" svn url using the environment of the last build is better than just looking for "$" and skipping the check altogether ? Alex 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] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis edited a comment on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node I am looking if we can detect such a condition (by the presence of a variable in the project configuration svn url) and skip this check if that is true. Bug exists in subversionSCM: compareRemoteRevisionWith() lines 1360 - 1375 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] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis edited a comment on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node Created pull request where if property hudson.scm.SubversionSCM.disableTriggerOnScmConfigMismatch is set to true, the comparison is skipped. Default is true to maintain existing behaviour. https://github.com/jenkinsci/subversion-plugin/pull/95 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] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node Indeed another way forward would be to use the same path on all nodes and setup a proxy or something on the physical machine the slave runs. The issue here is that setting up network routing for all nodes does not really scale so ideally the variables should work, and it does up to a point ;p since I do not care Jenkins detecting that the svn config url has changed and trigger a build I might just fork and delete those lines although I would prefer a solution in the original plugin Alex 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] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node I am looking if we can detect such a condition (by the presence of a variable in the project configuration svn url) and skip this check if that is 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] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis created JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node Issue Type: Bug Assignee: Unassigned Components: subversion Created: 03/Sep/14 9:25 AM Description: The issue at hand is the following: Project contains and svn url of the form: $SVN_ROOT_PATH/trunk Each node sets $SVN_ROOT_PATH to the SVN mirror closer to the node location. This allows us to have fast checkouts etc. Problem now is that Jenkins seems that the master evaluated SVN URL is different than the workspace checkout path of a slave and triggers a new build. This happens until it happens that the slave that picks the build is using the same mirror as the master. Setting polling to master only (via the magic property) does not fix the issue since the problem is not polling but Jenkins trying to be smart and detecting that the workspace has a different SVN URL than the configuration. Not sure how to tackle this but I am having a look. Project: Jenkins Priority: Major Reporter: Alex Ouzounis 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] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node Created pull request where is property hudson.scm.SubversionSCM.disableTriggerOnScmConfigMismatch is set to true, the comparison is skipped. Default is true to maintain existing behaviour. https://github.com/jenkinsci/subversion-plugin/pull/95 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Martin, Some good news. I noticed your recent changes and I pulled them to my fork ( https://github.com/alexouzounis/jenkins-inheritance-plugin ) which in turn is a fork of https://github.com/afitz/jenkins-inheritance-plugin because I need the changes for the SCM trigger etc. As a quick Sunday project I pulled your changes from https://github.com/i-m-c/jenkins-inheritance-plugin and apart from a few conflicts in the InheritanceGovernor the merge went fine. Rebooted Jenkins and it seems that now the Role Strategy plugins works as expected. Creating a role for some inheritance projects to have build rights works now as expected. As far as I am concerned the issue is now resolved from your latest changes and the ticket can be closed. It would be nice though for you to merge the changes from https://github.com/afitz/jenkins-inheritance-plugin ( I think there is a pull request from him already ) so that we can stop maintaining our own forks. Thanks, Alex 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration please ignore the above comment.. unfortunately I spoke too soon.. I just had a misconfiguration in the role strategies.. Well it was worth the try anyway.. 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis edited a comment on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Martin, Some good news. I noticed your recent changes and I pulled them to my fork ( https://github.com/alexouzounis/jenkins-inheritance-plugin ) which in turn is a fork of https://github.com/afitz/jenkins-inheritance-plugin because I need the changes for the SCM trigger etc. As a quick Sunday project I pulled your changes from https://github.com/i-m-c/jenkins-inheritance-plugin and apart from a few conflicts in the InheritanceGovernor the merge went fine. Rebooted Jenkins and it seems that now the Role Strategy plugins works as expected. Creating a role for some inheritance projects to have build rights works now as expected. As far as I am concerned the issue is now resolved from your latest changes and the ticket can be closed. It would be nice though for you to merge the changes from https://github.com/afitz/jenkins-inheritance-plugin ( I think there is a pull request from him already ) so that we can stop maintaining our own forks. Thanks, Alex == UPATE: see comment below, still it does not work 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis edited a comment on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration please ignore the above comment.. unfortunately I spoke too soon.. I just had a misconfiguration in the role strategies.. Well it was worth the try anyway.. All I get is: INFO: While serving http://JENKINS_HOME/job/JOB_TO_BUILD/build: hudson.security.AccessDeniedException2: USER is missing the Job/Build permission no exception or anything which is rather 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 -- 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration found the bug and fixed it in my fork. The problem was in the doBuild method of the InheritanceProject where you call the ACL to see if the user has permissions to build. Problem was you were not using the super method checkPermission from the AbstractItem but implementing your self. here is my commit: https://github.com/alexouzounis/jenkins-inheritance-plugin/commit/05263af27577387f8c4b014a60a11ec94a0a81ef As you can see, what was currently happening is: ACL acl = Jenkins.getInstance().getACL(); acl.checkPermission(BUILD); whereas the super.checkPermission does: Jenkins.getInstance().getAuthorizationStrategy().getACL(this).checkPermission(BUILD); The difference is that before the ROOT ACL was used (i.e. the global config) whereas not it also taken into account permissions available specify to that project. Feel free to merge back. Alex 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis edited a comment on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration found the bug and fixed it in my fork. The problem was in the doBuild method of the InheritanceProject where you call the ACL to see if the user has permissions to build. Problem was you were not using the super method checkPermission from the AbstractItem but implementing it your self. here is my commit: https://github.com/alexouzounis/jenkins-inheritance-plugin/commit/05263af27577387f8c4b014a60a11ec94a0a81ef As you can see, what was currently happening is: ACL acl = Jenkins.getInstance().getACL(); acl.checkPermission(BUILD); whereas the super.checkPermission does: Jenkins.getInstance().getAuthorizationStrategy().getACL(this).checkPermission(BUILD); The difference is that before the ROOT ACL was used (i.e. the global config) whereas not it also taken into account permissions available specify to that project. Feel free to merge back. Alex 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis edited a comment on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration found the bug and fixed it in my fork. The problem was in the doBuild method of the InheritanceProject where you call the ACL to see if the user has permissions to build. Problem was you were not using the super method checkPermission from the AbstractItem but implementing it your self. here is my commit: https://github.com/alexouzounis/jenkins-inheritance-plugin/commit/05263af27577387f8c4b014a60a11ec94a0a81ef As you can see, what was currently happening is: ACL acl = Jenkins.getInstance().getACL(); acl.checkPermission(BUILD); whereas the super.checkPermission does: Jenkins.getInstance().getAuthorizationStrategy().getACL(this).checkPermission(BUILD); The difference is that before the ROOT ACL was used (i.e. the global config) whereas now it also takes into account permissions available specifically for that project. Feel free to merge back. Alex 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-19764) Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist
Alex Ouzounis commented on JENKINS-19764 Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist experiencing the same issue here. progress ? 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-19764) Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist
Alex Ouzounis edited a comment on JENKINS-19764 Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist Hi Daniel, Thanks for looking into it. Just for the record I am using Jenkins 1.570 and the rename seems to correctly to rename the job but not all builds get moved over. It also throws the exception below though. java.io.IOException: failed to rename /jenkinsBuilds/TEST_rename/builds to /jenkinsBuilds/TEST_rename_test/builds at hudson.model.Job.renameTo(Job.java:621) at hudson.model.Job.doDoRename(Job.java:1403) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) Looking at the actual file system I see: jenkins@XXX:/jenkinsBuilds/TEST_rename$ cd builds/ jenkins@XXX:/jenkinsBuilds/TEST_rename/builds$ ls 1 19 2014-07-30_17-23-04 2014-07-31_09-56-51 2014-07-31_10-26-19 28 lastFailedBuild 10 22014-07-30_17-23-30 2014-07-31_09-57-16 2014-07-31_10-26-40 29 lastStableBuild 11 20 2014-07-30_17-24-08 2014-07-31_09-57-57 2014-07-31_11-12-08 3 lastSuccessfulBuild 12 2014-07-30_16-48-31 2014-07-30_17-24-54 2014-07-31_10-05-06 21 30 lastUnstableBuild 13 2014-07-30_17-07-42 2014-07-31_09-29-30 2014-07-31_10-08-27 22 4 lastUnsuccessfulBuild 14 2014-07-30_17-09-56 2014-07-31_09-30-18 2014-07-31_10-17-19 23 5 15 2014-07-30_17-11-57 2014-07-31_09-42-30 2014-07-31_10-19-40 24 6 16 2014-07-30_17-12-39 2014-07-31_09-51-33 2014-07-31_10-21-26 25 7 17 2014-07-30_17-14-08 2014-07-31_09-54-51 2014-07-31_10-22-25 26 8 18 2014-07-30_17-22-21 2014-07-31_09-55-25 2014-07-31_10-24-56 27 9 ... jenkins@XXX:/jenkinsBuilds$ cd TEST_rename_test/ jenkins@XXX:/jenkinsBuilds/TEST_rename_test$ ls builds jenkins@XXX:/jenkinsBuilds/TEST_rename_test$ cd builds/ jenkins@XXX:/jenkinsBuilds/TEST_rename_test/builds$ ls 28 30 lastFailedBuild lastStableBuild lastSuccessfulBuild lastUnstableBuild lastUnsuccessfulBuild It is fairly obvious something is going wrong. Manually copying the files sorts out the problem ofcourse. 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-19764) Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist
Alex Ouzounis commented on JENKINS-19764 Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist Hi Daniel, Thanks for looking into it. Just for the record I am using Jenkins 1.570 and the rename seems to correctly rename the job but not all builds get moved over. It also throws the exception below though. java.io.IOException: failed to rename /jenkinsBuilds/TEST_rename/builds to /jenkinsBuilds/TEST_rename_test/builds at hudson.model.Job.renameTo(Job.java:621) at hudson.model.Job.doDoRename(Job.java:1403) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) Looking at the actual file system I see: jenkins@XXX:/jenkinsBuilds/TEST_rename$ cd builds/ jenkins@XXX:/jenkinsBuilds/TEST_rename/builds$ ls 1 19 2014-07-30_17-23-04 2014-07-31_09-56-51 2014-07-31_10-26-19 28 lastFailedBuild 10 22014-07-30_17-23-30 2014-07-31_09-57-16 2014-07-31_10-26-40 29 lastStableBuild 11 20 2014-07-30_17-24-08 2014-07-31_09-57-57 2014-07-31_11-12-08 3 lastSuccessfulBuild 12 2014-07-30_16-48-31 2014-07-30_17-24-54 2014-07-31_10-05-06 21 30 lastUnstableBuild 13 2014-07-30_17-07-42 2014-07-31_09-29-30 2014-07-31_10-08-27 22 4 lastUnsuccessfulBuild 14 2014-07-30_17-09-56 2014-07-31_09-30-18 2014-07-31_10-17-19 23 5 15 2014-07-30_17-11-57 2014-07-31_09-42-30 2014-07-31_10-19-40 24 6 16 2014-07-30_17-12-39 2014-07-31_09-51-33 2014-07-31_10-21-26 25 7 17 2014-07-30_17-14-08 2014-07-31_09-54-51 2014-07-31_10-22-25 26 8 18 2014-07-30_17-22-21 2014-07-31_09-55-25 2014-07-31_10-24-56 27 9 ... jenkins@XXX:/jenkinsBuilds$ cd TEST_rename_test/ jenkins@XXX:/jenkinsBuilds/TEST_rename_test$ ls builds jenkins@XXX:/jenkinsBuilds/TEST_rename_test$ cd builds/ jenkins@XXX:/jenkinsBuilds/TEST_rename_test/builds$ ls 28 30 lastFailedBuild lastStableBuild lastSuccessfulBuild lastUnstableBuild lastUnsuccessfulBuild It is fairly obvious something is going wrong. Manually copying the files sorts out the problem ofcourse. 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-17265) Builds disappearing from history
Alex Ouzounis commented on JENKINS-17265 Builds disappearing from history Problem no longer present in the latest versions ie 1.570 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] [mantis] (JENKINS-23922) Regexp works only if one group exists.
Alex Ouzounis created JENKINS-23922 Regexp works only if one group exists. Issue Type: Bug Assignee: sogabe Components: mantis Created: 22/Jul/14 10:18 AM Description: The issue at hand is that Updater.java line 134: id = Integer.parseInt(matcher.group(1)); always goes for the first group. When using a pattern like: ((issues?):?(\s*(,|and)?\s*(\d+))+) parsing fails. It would be welcome to be able to define the _expression_ of the group the user wishes the matcher to match or define the group number. Project: Jenkins Priority: Major Reporter: Alex Ouzounis 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] [mantis] (JENKINS-23922) Regexp works only if one group exists.
Alex Ouzounis resolved JENKINS-23922 as Wont Fix Regexp works only if one group exists. No need to fix anything, just make sure you define your other groups as uncaptured by appending ?: Change By: Alex Ouzounis (22/Jul/14 2:07 PM) Status: Open Resolved Resolution: WontFix 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] [mantis] (JENKINS-23922) Regexp works only if one group exists.
Alex Ouzounis commented on JENKINS-23922 Regexp works only if one group exists. I can get around the issue by defined uncaptured groups like so: iIssues?:?(?:\s*(?:,|and)?\s*(\d+))+ As you can see the only matching group is (\d+) which gets correctly captured. 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] [mantis] (JENKINS-23922) Regexp works only if one group exists.
Alex Ouzounis assigned JENKINS-23922 to Alex Ouzounis Regexp works only if one group exists. Change By: Alex Ouzounis (22/Jul/14 2:06 PM) Assignee: sogabe AlexOuzounis 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis edited a comment on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Martin, Thanks for your reply. To reproduce the reported issue, all you need is: 1. Install the Role Strategy Plugin 2. Install the Inheritance Plugin 3. Create Abstract inheritance project, lets call it projA, with parameter paramA, over-writable. 4. Create Inheritance project, lets call it project_final, that extends projA and overwrite inheritance parameter reference paramA. 5. Make sure user TEST_USER has no build privileges in Manage Roles, then create a Project Role with pattern project_.* and enable the job build permissions. 6. assign that role to TEST_USER via the assign roles page. 7. sign in as TEST_USER and you will see the build with parameters button in p which when you click you get user TEST_USER has no job/build permissions. Even when I set the pattern in step 5 to .* ie everything, I still get the same error, as initially I thought that someone building project_final would require build rights for projA (sounded more like a bug rather than anything else but still) I will try and have a look in the code to see what is happening. Alex 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Martin, Thanks for your reply. To reproduce the reported issue, all you need is: 1. Install the Role Strategy Plugin 2. Install the Inheritance Plugin 3. Create Abstract inheritance project, lets call it projA, with patameter paramA, overwritable. 4. Create Inheritance project, lets call it project_final, that extends projA and overwrite inheritance parameter reference paramA. 5. Make sure user TEST_USER hasno build privileges in Manage Roles, then create a Project Role with pattern project_.* and enable the job build permissions. 6. assign that role to TEST_USER via the assign roles page. 7. sign in as TEST_USER and you will see the build with parameters button in p which when you click you get user TEST_USER has no job/build permissions. Even when I set the pattern in step 5 to .* ie everything, I still get the same error, as initially I thought that someone building project_final would require build rights for projA (sounded more like a bug rather than anything else but still) I will try and have a look in the code to see what is happening. Alex 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration I also forgot to mention that I am using afitz/jenkins-inheritance-plugin which contains bugfixes I really need related to scm polling etc. The issue reported is also present in the master i-m-c/jenkins-inheritance-plugin so no difference here, I just thought to mention it. 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Martin, I am seeing the exact same issue when using the Jenkins core "Project-based Matrix Authorization Strategy". So we can clearly rule out this being an issue of the Role-Based Strategy Plugin. Alex 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi Oleg, So what do you propose in doing ? All the code does is call the Jenkins.getItem method which in turn check for read permissions. That looks sensible to me. What do you think ? Alex 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] [ownership] (JENKINS-21390) [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Alex Ouzounis commented on JENKINS-21390 [Inheritance Plugin] - Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Hi all, Is anyone working on this? I would be interested in having a look as long someone throws me some pointers. Many thanks, Alex 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] [email-ext] (JENKINS-23619) Email Template Testing should support managed files as well
Alex Ouzounis created JENKINS-23619 Email Template Testing should support managed files as well Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 30/Jun/14 10:16 AM Description: When adding an Email-Ext post-build action, managed file templates can be used by pre-pending "managed:" when calling the script. Unfortunately the same is not true when using the Template Testing page. Environment: Jenkins 1.565 Email-Ext 2.38.1 Project: Jenkins Priority: Minor Reporter: Alex Ouzounis 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] [email-ext] (JENKINS-23619) Email Template Testing should support managed files as well
Alex Ouzounis updated JENKINS-23619 Email Template Testing should support managed files as well Change By: Alex Ouzounis (30/Jun/14 10:19 AM) Description: WhenaddinganEmail-Extpost-buildaction,managedfiletemplatescanbeusedbypre-pendingmanaged:whencallingthescript.UnfortunatelythesameisnottruewhenusingtheTemplateTestingpage. Whentryingtotestamanagedtemplatethefollowingexceptionisseen:preCausedby:java.lang.UnsupportedOperationException atjava.util.AbstractList.add(AbstractList.java:148) atjava.util.AbstractList.add(AbstractList.java:108) athudson.plugins.emailext.EmailExtTemplateAction.getTemplateConfigProviders(EmailExtTemplateAction.java:94) athudson.plugins.emailext.EmailExtTemplateAction.checkForManagedFile(EmailExtTemplateAction.java:75) athudson.plugins.emailext.EmailExtTemplateAction.doTemplateFileCheck(EmailExtTemplateAction.java:59) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:606) atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) atorg.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) atorg.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) atorg.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) ...70more/pre 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] [email-ext] (JENKINS-23619) Email Template Testing should support managed files as well
Alex Ouzounis commented on JENKINS-23619 Email Template Testing should support managed files as well The problem seems to be line 90 where the list is defined as: CollectionConfigProvider providers = Collections.emptyList(); which is immutable as noted by its associated Javadoc. Replacing this with a new list should do the trick. Alex 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] [email-ext] (JENKINS-23619) Email Template Testing should support managed files as well
Alex Ouzounis commented on JENKINS-23619 Email Template Testing should support managed files as well created pull request: https://github.com/jenkinsci/email-ext-plugin/pull/92 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-15063) support for multiple security realms with failover
Alex Ouzounis commented on JENKINS-15063 support for multiple security realms with failover I would also be interested in this. Any activity ? 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] [cloudbees-folder] (JENKINS-23307) Inheritance Project cannot reference another inheritance project which lies in a folder
Alex Ouzounis created JENKINS-23307 Inheritance Project cannot reference another inheritance project which lies in a folder Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Components: cloudbees-folder, project-inheritance Created: 04/Jun/14 9:29 AM Description: When creating a new inheritance project which is then configured to inherit the configuration of another project living within a folder, I see: WARNING: Found unresolvable reference to: XXX It seems that any configuration from those inherited projects living in a folder is not read any-more Project: Jenkins Priority: Major Reporter: Alex Ouzounis 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] [credentials] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Alex Ouzounis commented on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. seeing the same issue here as well 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] [project-inheritance] (JENKINS-23307) Inheritance Project cannot reference another inheritance project which lies in a folder
Alex Ouzounis commented on JENKINS-23307 Inheritance Project cannot reference another inheritance project which lies in a folder current workaround: move the "abstract/base" projects to Jenkins root. 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] [email-ext] (JENKINS-21362) Multiple (User Defined) Global Templates
Alex Ouzounis commented on JENKINS-21362 Multiple (User Defined) Global Templates This is a really exciting proposition, I will try and have a look at the plugin and give you some feedback at some point. 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] [sidebar-link] (JENKINS-18887) Alllow links to open in new window/tab
Alex Ouzounis commented on JENKINS-18887 Alllow links to open in new window/tab I was looking for exactly that and I suppose a bit of _javascript_ could do the trick. 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] [parameterized-trigger] (JENKINS-22125) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23
Alex Ouzounis commented on JENKINS-22125 FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23 I agree. This new feature should be optional and the default behaviour shall remain the same. Alex 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-21780) DirectoryBrowserSupport.buildChildPaths does quadratic number of calls to check whether entries are directories
Alex Ouzounis commented on JENKINS-21780 DirectoryBrowserSupport.buildChildPaths does quadratic number of calls to check whether entries are directories Is this fix present in the latest version ? We are also getting hit by it. 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/groups/opt_out.
[JIRA] [core] (JENKINS-21780) DirectoryBrowserSupport.buildChildPaths does quadratic number of calls to check whether entries are directories
Alex Ouzounis commented on JENKINS-21780 DirectoryBrowserSupport.buildChildPaths does quadratic number of calls to check whether entries are directories Aha! Yes, indeed. Its part of 1.554 Thanks for the quick reply Alex 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/groups/opt_out.
[JIRA] [core] (JENKINS-17265) Builds disappearing from history
Alex Ouzounis commented on JENKINS-17265 Builds disappearing from history Hi all, I am seeing the same problem occasionally and either restarting or reloading from disk fixes the problem. I have a feeling that its related with: "WARNING: Multiple builds have the same number: " because every time I delete conflicting builds it goes away. 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/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
Alex Ouzounis commented on JENKINS-20935 Provide separate monitoring pages for each slave node Just updated to the Monitoring plugin version 1.49 and all links in the node/monitoring page instead of starting with my defined Jenkins URL (host/jenkins) start with just the host making the links and images broken. Is anyone else 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 -- 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/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
Alex Ouzounis
commented on JENKINS-20935
Provide separate monitoring pages for each slave node
thanks!
the problem though is also affecting the links (not only the icons) and the patch provided does not seem to include any fix for the actual links i.e. ${it.monitoringUrl} seems not to include the full Jenkins URL, although I could be easily wrong
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/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Alex Ouzounis commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Hi, Just to add my observations here. Following the instructions from dev #comment-189758 the issue is gone for my Jenkins 1.539 installation. The only thing to add is make are that the JENKINS_HOME var is defined before the JAVA_ARGS var. Alex 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/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Alex Ouzounis edited a comment on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Hi, Just to add my observations here. Following the instructions from dev #comment-189758 the issue is gone for my Jenkins 1.539 installation. The only thing to add is make sure that the JENKINS_HOME var is defined before the JAVA_ARGS var. Alex 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/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis commented on JENKINS-17831 Update to latest xTrigger 0.28 seems to do the trick. Happy days 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/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis commented on JENKINS-17831 Update to latest xTrigger again I am seeing this: May 17, 2013 10:37:03 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job XXX hudson.util.IOException2: Unable to read /var/lib/jenkins/jobs/XXX/config.xml at hudson.XmlFile.read(XmlFile.java:147) at hudson.model.Items.load(Items.java:220) at jenkins.model.Jenkins$17.run(Jenkins.java:2554) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:888) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Caused by: com.thoughtworks.xstream.converters.ConversionException: Invalid reference Debugging information reference : ../../filePathFactory class : org.jenkinsci.plugins.ivytrigger.util.PropertiesFileContentExtractor required-type : org.jenkinsci.plugins.ivytrigger.util.PropertiesFileContentExtractor converter-type : hudson.util.RobustReflectionConverter path: /project/triggers/org.jenkinsci.plugins.ivytrigger.IvyTrigger/propertiesFileContentExtractor/filePathFactory line number : 71 class1: org.jenkinsci.plugins.ivytrigger.IvyTrigger class2: java.util.Vector converter-type1 : hudson.util.RobustCollectionConverter class3: hudson.model.FreeStyleProject version : null --- at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:57) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:61) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis commented on JENKINS-17831 Update to latest xTrigger looking in the config.xml of that job is see: org.jenkinsci.plugins.ivytrigger.IvyTrigger plugin="ivytrigger@0.24" spec# every 10 minutes H/10 * * * */spec ivyPathivy.xml/ivyPath ivySettingsPath$SOFCOMMON/conf/ivysettings.xml/ivySettingsPath propertiesFilePath$SOFCOMMON/conf/ivysettings.properties/propertiesFilePath debugfalse/debug filePathFactory/ propertiesFileContentExtractor filePathFactory reference="../../filePathFactory"/ /propertiesFileContentExtractor /org.jenkinsci.plugins.ivytrigger.IvyTrigger 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/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis edited a comment on JENKINS-17831 Update to latest xTrigger great! that would do it Let me know when a new release of IvyTrigger is available to test 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/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis commented on JENKINS-17831 Update to latest xTrigger great! that would do it 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/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis commented on JENKINS-17831 Update to latest xTrigger same with 0.25 SEVERE: Failed Loading job XXX hudson.util.IOException2: Unable to read /var/lib/jenkins/jobs/XXX/config.xml at hudson.XmlFile.read(XmlFile.java:147) at hudson.model.Items.load(Items.java:220) at jenkins.model.Jenkins$17.run(Jenkins.java:2554) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:888) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Caused by: com.thoughtworks.xstream.converters.ConversionException: Invalid reference Debugging information reference : ../../filePathFactory class : org.jenkinsci.plugins.ivytrigger.util.PropertiesFileContentExtractor required-type : org.jenkinsci.plugins.ivytrigger.util.PropertiesFileContentExtractor converter-type : hudson.util.RobustReflectionConverter path: /project/triggers/org.jenkinsci.plugins.ivytrigger.IvyTrigger/propertiesFileContentExtractor/filePathFactory line number : 71 class1: org.jenkinsci.plugins.ivytrigger.IvyTrigger class2: java.util.Vector converter-type1 : hudson.util.RobustCollectionConverter class3: hudson.model.FreeStyleProject version : null --- at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:57) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:61) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis commented on JENKINS-17831 Update to latest xTrigger I will try and test later when no builds are occurring 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/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis commented on JENKINS-17831 Update to latest xTrigger all jobs dependant of ivy trigger are now failling to load when using 0.26 Debugging information reference : ../../filePathFactory class : org.jenkinsci.plugins.ivytrigger.util.PropertiesFileContentExtractor required-type : org.jenkinsci.plugins.ivytrigger.util.PropertiesFileContentExtractor converter-type : hudson.util.RobustReflectionConverter path: /project/triggers/org.jenkinsci.plugins.ivytrigger.IvyTrigger/propertiesFileContentExtractor/filePathFactory line number : 68 class1: org.jenkinsci.plugins.ivytrigger.IvyTrigger class2: java.util.Vector converter-type1 : hudson.util.RobustCollectionConverter class3: hudson.model.FreeStyleProject version : null --- at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:57) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:61) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061) at hudson.util.XStream2.unmarshal(XStream2.java:109) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:925) at hudson.XmlFile.read(XmlFile.java:143) ... 10 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis created JENKINS-17831 Update to latest xTrigger Issue Type: Improvement Assignee: Unassigned Components: ivytrigger Created: 02/May/13 9:44 AM Description: The current ivytrigger version does not allow polling node restrictions. Please update to latest xtrigger to integrate that functionality Project: Jenkins Priority: Major Reporter: Alex Ouzounis 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/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis commented on JENKINS-17831 Update to latest xTrigger Release 0.28 and later of xtrigger allows the restriction of the polling node. Would it be possible to update ivy trigger such that this functionality is present ? 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/groups/opt_out.
[JIRA] [core] (JENKINS-8423) Slave priority
Alex Ouzounis commented on JENKINS-8423 Slave priority +1 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/groups/opt_out.
[JIRA] [core] (JENKINS-16845) NullPointer in getPreviousBuild
Alex Ouzounis commented on JENKINS-16845 NullPointer in getPreviousBuild Since 1.511 and clearing/deleting the bad builds problem is officially 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/groups/opt_out.
[JIRA] [core] (JENKINS-16845) NullPointer in getPreviousBuild
Alex Ouzounis commented on JENKINS-16845 NullPointer in getPreviousBuild Its back... I restarted jenkins and now I see this in the logs: Apr 17, 2013 3:21:18 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.finishedBuilds in /jenkins/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ... at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) ... at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.NullPointerException at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:346) at hudson.model.Run.onLoad(Run.java:319) at hudson.model.RunMap.retrieve(RunMap.java:226) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650) at jenkins.model.lazy.AbstractLazyLoadRunMap.all(AbstractLazyLoadRunMap.java:602) at jenkins.model.lazy.AbstractLazyLoadRunMap.entrySet(AbstractLazyLoadRunMap.java:264) at java.util.AbstractMap$2$1.init(AbstractMap.java:378) at java.util.AbstractMap$2.iterator(AbstractMap.java:377) at hudson.util.RunList.iterator(RunList.java:103) at hudson.util.RunList.size(RunList.java:114) at java.util.AbstractCollection.toArray(AbstractCollection.java:136) at java.util.ArrayList.addAll(ArrayList.java:530) at hudson.plugins.view.dashboard.builds.LatestBuilds.getFinishedBuilds(LatestBuilds.java:53) ... 149 more 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/groups/opt_out.
[JIRA] [core] (JENKINS-16845) NullPointer in getPreviousBuild
Alex Ouzounis edited a comment on JENKINS-16845 NullPointer in getPreviousBuild Its back... I restarted jenkins and now I see this in the logs: Apr 17, 2013 3:21:18 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.finishedBuilds in /jenkins/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ... at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) ... at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.NullPointerException at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:346) at hudson.model.Run.onLoad(Run.java:319) at hudson.model.RunMap.retrieve(RunMap.java:226) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650) at jenkins.model.lazy.AbstractLazyLoadRunMap.all(AbstractLazyLoadRunMap.java:602) at jenkins.model.lazy.AbstractLazyLoadRunMap.entrySet(AbstractLazyLoadRunMap.java:264) at java.util.AbstractMap$2$1.init(AbstractMap.java:378) at java.util.AbstractMap$2.iterator(AbstractMap.java:377) at hudson.util.RunList.iterator(RunList.java:103) at hudson.util.RunList.size(RunList.java:114) at java.util.AbstractCollection.toArray(AbstractCollection.java:136) at java.util.ArrayList.addAll(ArrayList.java:530) at hudson.plugins.view.dashboard.builds.LatestBuilds.getFinishedBuilds(LatestBuilds.java:53) ... 149 more 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/groups/opt_out.
[JIRA] [core] (JENKINS-16845) NullPointer in getPreviousBuild
Alex Ouzounis commented on JENKINS-16845 NullPointer in getPreviousBuild @jess_glick thanks for the reply Hopefully we will get a permeant fix in due time 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/groups/opt_out.
[JIRA] [core] (JENKINS-16845) NullPointer in getPreviousBuild
Alex Ouzounis commented on JENKINS-16845 NullPointer in getPreviousBuild updated your Jenkins to 1.511 and problem is gone! Obviously the log now contains a dozen of these: Apr 15, 2013 10:22:09 AM hudson.tasks.Fingerprinter$FingerprintAction onLoad WARNING: JENKINS-16845: broken FingerprintAction record Would it be more helpful to have the warning updated such that it displays the build name and number that contains the broken FingerprintAction record ? 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/groups/opt_out.
[JIRA] [core] (JENKINS-16845) NullPointer in getPreviousBuild
Alex Ouzounis edited a comment on JENKINS-16845 NullPointer in getPreviousBuild updated our Jenkins to 1.511 and problem is gone! Obviously the log now contains a dozen of these: Apr 15, 2013 10:22:09 AM hudson.tasks.Fingerprinter$FingerprintAction onLoad WARNING: JENKINS-16845: broken FingerprintAction record Would it be more helpful to have the warning updated such that it displays the build name and number that contains the broken FingerprintAction record ? 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/groups/opt_out.
[JIRA] [core] (JENKINS-16845) NullPointer in getPreviousBuild
Alex Ouzounis commented on JENKINS-16845 NullPointer in getPreviousBuild we are also affected by the broken serial form of FingerprintAction. What happens in our case is that in some cases the dashboard view cannot display the unstable and latest builds. After a couple of refreshes the view gets populated correctly so my assumption is that the lazy loaded "map" of builds loses its integrity and refreshing the dashboard view "forces" it to reload a bit every time until all builds are loaded correctly. We experience this after a jenkins restart or after periods of inactivity. Not sure why it happens in the second case; is the map of builds "cleared" after some time and needs to be re-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 -- 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/groups/opt_out.
[JIRA] [svnmerge] (JENKINS-15830) Error: Unable to infer the new branch name from XXX
Alex Ouzounis commented on JENKINS-15830 Error: Unable to infer the new branch name from XXX any help would be greatly appreciated 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/groups/opt_out.
[JIRA] (JENKINS-15830) Error: Unable to infer the new branch name from XXX
Alex Ouzounis created JENKINS-15830 Error: Unable to infer the new branch name from XXX Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: svnmerge Created: 14/Nov/12 9:16 PM Description: The problem lies in the fact that the plugin tries to deduce the branch to be create absolute path from the current trunk path. The assumption is that the svn repository is using the following convention: http://svnserver.com/projectName and within that you have a a trunk and a branches folder. Our setup uses a completely different structure where the "trunk" folder is at the root and has a different name other than trunk. Within that "trunk" folder you have another 2 layers at least till you reach the project that has been checked out. trunk example: http://svnserver.com/FolderTrunk/Folder2/Folder3/Folder4/ProjectName branch example: http://svnserver.com/FolderBranches/Folder2/..At_Least_3_Folders../FeatureBranch The "culprit" seems to be: svnmerge-plugin / src / main / java / jenkins / plugins / svnmerge / IntegratableProjectAction.java A possible fix would be to also allow the user to define the full feature branch path from the root of the svn as an additional feature. That would allow us to create a feature branch anywhere within our svn structure since features branches can go in more than one "branch locations" (ie you have no way to automatically deduce the full branch path) Its not critical but currently we cannot use this plugin due to this problem. I have never developed for Jenkins but I am a Java Developer so I could give it a go myself as long as I am pointed in the right direction. Environment: Jenkins Master on Ubuntu 12.04 Project: Jenkins Labels: plugin svnmerge error, Priority: Minor Reporter: Alex Ouzounis 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-15830) Error: Unable to infer the new branch name from XXX
Alex Ouzounis updated JENKINS-15830 Error: Unable to infer the new branch name from XXX Change By: Alex Ouzounis (14/Nov/12 9:17 PM) Description: Theproblemliesinthefactthattheplugintriestodeducethebranchtobe create created absolutepathfromthecurrenttrunkpath.Theassumptionisthatthesvnrepositoryisusingthefollowingconvention:http://svnserver.com/projectNameandwithinthatyouhaveaatrunkandabranchesfolder.Oursetupusesacompletelydifferentstructurewherethetrunkfolderisattherootandhasadifferentnameotherthantrunk.Withinthattrunkfolderyouhaveanother2layersatleasttillyoureachtheprojectthathasbeencheckedout.trunkexample:http://svnserver.com/FolderTrunk/Folder2/Folder3/Folder4/ProjectNamebranchexample:http://svnserver.com/FolderBranches/Folder2/..At_Least_3_Folders../FeatureBranchTheculpritseemstobe:svnmerge-plugin/src/main/java/jenkins/plugins/svnmerge/IntegratableProjectAction.javaApossiblefixwouldbetoalsoallowtheusertodefinethefullfeaturebranchpathfromtherootofthesvnasanadditionalfeature.Thatwouldallowustocreateafeaturebranchanywherewithinoursvnstructuresincefeaturesbranchescangoinmorethanonebranchlocations(ieyouhavenowaytoautomaticallydeducethefullbranchpath)Itsnotcriticalbutcurrentlywecannotusethispluginduetothisproblem.IhaveneverdevelopedforJenkinsbutIamaJavaDevelopersoIcouldgiveitagomyselfaslongasIampointedintherightdirection. 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
