[JIRA] [copy-to-slave] (JENKINS-18360) Incorrect use of project.getWorkspace()
Daniel Petisme commented on JENKINS-18360 Incorrect use of project.getWorkspace() I'll try to do it before end of week... 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] [copy-to-slave] (JENKINS-18360) Incorrect use of project.getWorkspace()
Daniel Petisme commented on JENKINS-18360 Incorrect use of project.getWorkspace() Hi Jeesse, I've inherited of all rseguy's plugins ownership. I was a huge SVN fan :/ Do you have any kind of procedure to move Jenkins plugin from SVN to Github. It'll ease my work too Do you have to raise requests for all the plugins to integrate them into the Jenkins CI organization? 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] [master-slave] (JENKINS-10771) hudson.util.IOException2: remote file operation failed
Daniel Petisme commented on JENKINS-10771 hudson.util.IOException2: remote file operation failed Same issue: Version: Jenkins 1.424.2 Master: Suse Enterprise Linux Enterprise 10 SP2 Slave: Windows XP SP2 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-16317) Cannot install Jenkins if setup fails to start the Jenkins service
Daniel Petisme assigned JENKINS-16317 to Unassigned Cannot install Jenkins if setup fails to start the Jenkins service I'm not the appropriate assignee. I do not use this feature of Jenkins and moreover I don't have any Win Server 2012. Change By: Daniel Petisme (11/Jan/13 9:20 PM) Assignee: Daniel Petisme 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-10552) Add ability to check roles on project
Daniel Petisme commented on JENKINS-10552 Add ability to check roles on project I've got similar use cases. About the users' passwords I'm agree with Romain. Regarding the last 2 points, I use groovy scripts to compute such information. I can share them without problem if needed. 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-15031) Use view tabs to assign roles to projects
Daniel Petisme commented on JENKINS-15031 Use view tabs to assign roles to projects In fact, I'm also looking for such behavior. In my organization, more or less my roles are mapped to views, and adding a new project means adding a new view + update a role. Nevertheless, the role and the view concepts are not equals. I'm wondering if I can tie them together... 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-14687) Password is exposed through browser option "view page source"
Daniel Petisme commented on JENKINS-14687 Password is exposed through browser option "view page source" The Mask password plugin aims to hide your passwords in the jobs console output... It can be an interesting/mandatory ER for the next release. I hope to have to time to spend on this improve. I keep you informed. 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-15373) obfuscate parameterized build values
Daniel Petisme commented on JENKINS-15373 obfuscate parameterized build values Normally, in the global Hudson/Jenkins config, you can chosse the parameters you want to mask by default. For instance, you can configure the plugin to obfuscate the Password Parameters & Non-Stored Password Parameters without more user/job specific config. _Caution: You should always check the "Mask Passwords" checkbox in you jobs configs" 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-15373) obfuscate parameterized build values
Daniel Petisme edited a comment on JENKINS-15373 obfuscate parameterized build values Normally, in the global Hudson/Jenkins config, you can chosse the parameters you want to mask by default. For instance, you can configure the plugin to obfuscate the Password Parameters & Non-Stored Password Parameters without more user/job specific config. Caution: You should always check the "Mask Passwords" checkbox in you jobs configs" 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-12904) WAS Builder exposes username and password when using "system information" for the Master or Slave
[
https://issues.jenkins-ci.org/browse/JENKINS-12904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162916#comment-162916
]
Daniel Petisme commented on JENKINS-12904:
--
Indeed, the issue is related to Jenkins itself and it's not the plugin's fault.
We also encountered the issue.
Have a look at the [{{Mask Paswords
Plugin}}|https://wiki.jenkins-ci.org/display/JENKINS/Mask+Passwords+Plugin].
It'll mask the values you want and can automatically mask parameters values
(such as Password Parameters or Non-Stored Password Parameters).
> WAS Builder exposes username and password when using "system information" for
> the Master or Slave
> -
>
> Key: JENKINS-12904
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12904
> Project: Jenkins
> Issue Type: Bug
> Components: was-builder
>Reporter: Walter Kacynski
>Assignee: Daniel Petisme
>Priority: Critical
> Labels: security
>
> I'm not sure if this is a problem with the plugin on Jenkins it self. The
> thread name of the was-builder task embeds the full command line which
> includes the username / password that was invoked. I see this as a security
> exposure when using the Jenkins ui.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12896) IndexOutOfBoundsException when renaming/deleting several jobs at the same time (RROD plugin)
[ https://issues.jenkins-ci.org/browse/JENKINS-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Petisme closed JENKINS-12896. Fix Version/s: current Resolution: Fixed > IndexOutOfBoundsException when renaming/deleting several jobs at the same > time (RROD plugin) > > > Key: JENKINS-12896 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12896 > Project: Jenkins > Issue Type: Bug > Components: rrod >Reporter: Daniel Petisme >Assignee: Daniel Petisme > Fix For: current > > > Select a set of tasks to do > Apply > Obtain: > java.lang.IndexOutOfBoundsException: Index: 70, Size: 70 > java.util.ArrayList.get(ArrayList.java:338) > com.michelin.cio.jenkins.plugin.rrod.RequestRenameOrDeletePlugin.doManageRequests(RequestRenameOrDeletePlugin.java:83) > Random issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8075) Assign role interface does not scale to large number of users and roles
[ https://issues.jenkins-ci.org/browse/JENKINS-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162450#comment-162450 ] Daniel Petisme commented on JENKINS-8075: - Sure, it's possible. [Export to CSV| https://github.com/danielpetisme/jenkins-scripts/blob/master/scriptler/export-role-strategy-permissions-to-csv.groovy] I've opened a pull request to add it into the official scriptler catalog. Tutorial: 1 - [Assign your roles|https://issues.jenkins-ci.org/secure/attachment/21791/roles-assignation.png] 2 - Go to Manage Jenkins > Script Console 3 - Copy'n'Paste the [export-role-strategy-permissions-to-csv.groovy| https://github.com/danielpetisme/jenkins-scripts/blob/master/scriptler/export-role-strategy-permissions-to-csv.groovy] script 4 - Execute it, the script will display the [CSV output|https://issues.jenkins-ci.org/secure/attachment/21792/roles-strategy-csv-export.png] 5 - You're done!! You just have to copy the output to use it in a _Excel-like_ tool To be franck, I don't know when I could work on the plugin to improve it :( > Assign role interface does not scale to large number of users and roles > --- > > Key: JENKINS-8075 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8075 > Project: Jenkins > Issue Type: Improvement > Components: role-strategy > Environment: Hudson 1.381, Role based strategy 1.0 >Reporter: Costin Caraivan >Assignee: Daniel Petisme >Priority: Minor > Attachments: JENKINS-8075.png, roleassignment-mockup.png, > roleassignment-original.png, roles-assignation.png, > roles-strategy-csv-export.png > > > Hello, > Our Hudson deployment has a lot of independent projects which need to have > several roles assigned inside the team, some team members having more rights > than others. The end result: lots of users, lots of projects x several roles > per project = a huge bunch of roles. > The number of users and roles will only increase - right now we are at about > 50% of the final capacity. > Trying to use the Role Based Strategy plugin, we noticed some scaling issues > with the "Assign roles" page. See roleassignment-original.png attachment for > the problems. > Notice the scroll bars when having lots of users and roles. Having lots of > users is ok, vertical scrolling is something common on webpages. However, > having both vertical scrolling and horizontal scrolling is confusing. The > Hudson row/column highlight is helpful, however the interface is still > cumbersome. > I would propose the following interface change for the assign roles page: > - add a text box to each table row; preferably with role autocompletion, if > possible > - add a label with the list or roles for each user > See the roleassignement-mockup.png attachment. > Thank you for your help. > I propose a different design for the page, to allow it to scale when having > lots of users and roles -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8075) Assign role interface does not scale to large number of users and roles
[ https://issues.jenkins-ci.org/browse/JENKINS-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Petisme updated JENKINS-8075: Attachment: roles-assignation.png roles-strategy-csv-export.png > Assign role interface does not scale to large number of users and roles > --- > > Key: JENKINS-8075 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8075 > Project: Jenkins > Issue Type: Improvement > Components: role-strategy > Environment: Hudson 1.381, Role based strategy 1.0 >Reporter: Costin Caraivan >Assignee: Daniel Petisme >Priority: Minor > Attachments: JENKINS-8075.png, roleassignment-mockup.png, > roleassignment-original.png, roles-assignation.png, > roles-strategy-csv-export.png > > > Hello, > Our Hudson deployment has a lot of independent projects which need to have > several roles assigned inside the team, some team members having more rights > than others. The end result: lots of users, lots of projects x several roles > per project = a huge bunch of roles. > The number of users and roles will only increase - right now we are at about > 50% of the final capacity. > Trying to use the Role Based Strategy plugin, we noticed some scaling issues > with the "Assign roles" page. See roleassignment-original.png attachment for > the problems. > Notice the scroll bars when having lots of users and roles. Having lots of > users is ok, vertical scrolling is something common on webpages. However, > having both vertical scrolling and horizontal scrolling is confusing. The > Hudson row/column highlight is helpful, however the interface is still > cumbersome. > I would propose the following interface change for the assign roles page: > - add a text box to each table row; preferably with role autocompletion, if > possible > - add a label with the list or roles for each user > See the roleassignement-mockup.png attachment. > Thank you for your help. > I propose a different design for the page, to allow it to scale when having > lots of users and roles -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8075) Assign role interface does not scale to large number of users and roles
[ https://issues.jenkins-ci.org/browse/JENKINS-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162261#comment-162261 ] Daniel Petisme commented on JENKINS-8075: - @Jamie, I'm in charge now of Romain's work. As you, I'm not confortable when I use this tool. But to be franck, I haven't much time to improve it now. I've a groovy script to export 2 CSVs (one for the roles definition and the other one for role assignation aka. the matrix). I can share with you these scripts if you want. But I haven't a CSV import feature. Of course any contribution will be welcomed ;) > Assign role interface does not scale to large number of users and roles > --- > > Key: JENKINS-8075 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8075 > Project: Jenkins > Issue Type: Improvement > Components: role-strategy > Environment: Hudson 1.381, Role based strategy 1.0 >Reporter: Costin Caraivan >Assignee: Daniel Petisme >Priority: Minor > Attachments: JENKINS-8075.png, roleassignment-mockup.png, > roleassignment-original.png > > > Hello, > Our Hudson deployment has a lot of independent projects which need to have > several roles assigned inside the team, some team members having more rights > than others. The end result: lots of users, lots of projects x several roles > per project = a huge bunch of roles. > The number of users and roles will only increase - right now we are at about > 50% of the final capacity. > Trying to use the Role Based Strategy plugin, we noticed some scaling issues > with the "Assign roles" page. See roleassignment-original.png attachment for > the problems. > Notice the scroll bars when having lots of users and roles. Having lots of > users is ok, vertical scrolling is something common on webpages. However, > having both vertical scrolling and horizontal scrolling is confusing. The > Hudson row/column highlight is helpful, however the interface is still > cumbersome. > I would propose the following interface change for the assign roles page: > - add a text box to each table row; preferably with role autocompletion, if > possible > - add a label with the list or roles for each user > See the roleassignement-mockup.png attachment. > Thank you for your help. > I propose a different design for the page, to allow it to scale when having > lots of users and roles -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13622) ..\runTestSet.vbs(555, 5) ADODB.Stream: Write to file failed.
[ https://issues.jenkins-ci.org/browse/JENKINS-13622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162152#comment-162152 ] Daniel Petisme commented on JENKINS-13622: -- Can you check if your issue is similar to this one please: [JENKINS-9539|https://issues.jenkins-ci.org/browse/JENKINS-9539] The last time I've tried, I saw both message in the same log. To know if is the same issue. > ..\runTestSet.vbs(555, 5) ADODB.Stream: Write to file failed. > - > > Key: JENKINS-13622 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13622 > Project: Jenkins > Issue Type: Bug > Components: qc >Affects Versions: current > Environment: - Microsoft Windows XP Professional SP 3 > - IE 8 & Chrome > - Jenkins ver. 1.451 > - qc plugin 1.2.1 >Reporter: COE CI >Assignee: Daniel Petisme > Labels: plugin > > +--+ > | Test Name| > Status| > +--+ > | [1]MercuryTours | > Passed| > +--+ > ..\runTestSet.vbs(555, 5) ADODB.Stream: Write to file failed. > FATAL: Tests report not generated > Build step 'HP Quality Center' marked build as failure > Sending e-mails to: > Finished: FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13622) ..\runTestSet.vbs(555, 5) ADODB.Stream: Write to file failed.
[ https://issues.jenkins-ci.org/browse/JENKINS-13622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162136#comment-162136 ] Daniel Petisme edited comment on JENKINS-13622 at 4/27/12 7:59 AM: --- Can you try with IE6 or IE7 please, I'm not sure if ADODB.Stream works with IE8. was (Author: danielpetisme): Can you try with IE6 or IE7 please, I'm not sure if ADODB.Stream works with IE8. e > ..\runTestSet.vbs(555, 5) ADODB.Stream: Write to file failed. > - > > Key: JENKINS-13622 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13622 > Project: Jenkins > Issue Type: Bug > Components: qc >Affects Versions: current > Environment: - Microsoft Windows XP Professional SP 3 > - IE 8 & Chrome > - Jenkins ver. 1.451 > - qc plugin 1.2.1 >Reporter: COE CI >Assignee: Daniel Petisme > Labels: plugin > > +--+ > | Test Name| > Status| > +--+ > | [1]MercuryTours | > Passed| > +--+ > ..\runTestSet.vbs(555, 5) ADODB.Stream: Write to file failed. > FATAL: Tests report not generated > Build step 'HP Quality Center' marked build as failure > Sending e-mails to: > Finished: FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13622) ..\runTestSet.vbs(555, 5) ADODB.Stream: Write to file failed.
[ https://issues.jenkins-ci.org/browse/JENKINS-13622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162136#comment-162136 ] Daniel Petisme commented on JENKINS-13622: -- Can you try with IE6 or IE7 please, I'm not sure if ADODB.Stream works with IE8. e > ..\runTestSet.vbs(555, 5) ADODB.Stream: Write to file failed. > - > > Key: JENKINS-13622 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13622 > Project: Jenkins > Issue Type: Bug > Components: qc >Affects Versions: current > Environment: - Microsoft Windows XP Professional SP 3 > - IE 8 & Chrome > - Jenkins ver. 1.451 > - qc plugin 1.2.1 >Reporter: COE CI >Assignee: Daniel Petisme > Labels: plugin > > +--+ > | Test Name| > Status| > +--+ > | [1]MercuryTours | > Passed| > +--+ > ..\runTestSet.vbs(555, 5) ADODB.Stream: Write to file failed. > FATAL: Tests report not generated > Build step 'HP Quality Center' marked build as failure > Sending e-mails to: > Finished: FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9343) Add LOADING overlay when triggering a build with parameters
[
https://issues.jenkins-ci.org/browse/JENKINS-9343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Petisme reopened JENKINS-9343:
-
Similar to the following issue
[Jenkins-8789|https://issues.jenkins-ci.org/browse/JENKINS-8789]
When you use the {{Validating string parameter}}, if you type an apostrophe in
the {{Regular expression field}} or {{Failed Validation Message}} then you try
to build your build but the overlay never goes away.
> Add LOADING overlay when triggering a build with parameters
> ---
>
> Key: JENKINS-9343
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9343
> Project: Jenkins
> Issue Type: Improvement
> Components: core
>Reporter: Romain Seguy
>Assignee: Romain Seguy
>Priority: Trivial
> Attachments: Regular_Expression_With_Apostrophe.PNG,
> Regular_Expression_With_Apostrophe_Overlay_Blocked.PNG,
> Validation_Message_With_Apostrophe.PNG,
> Validation_Message_With_Apostrophe_Overlay_Blocked.PNG
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9343) Add LOADING overlay when triggering a build with parameters
[ https://issues.jenkins-ci.org/browse/JENKINS-9343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Petisme updated JENKINS-9343: Attachment: Validation_Message_With_Apostrophe_Overlay_Blocked.PNG Regular_Expression_With_Apostrophe.PNG Regular_Expression_With_Apostrophe_Overlay_Blocked.PNG Validation_Message_With_Apostrophe.PNG > Add LOADING overlay when triggering a build with parameters > --- > > Key: JENKINS-9343 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9343 > Project: Jenkins > Issue Type: Improvement > Components: core >Reporter: Romain Seguy >Assignee: Romain Seguy >Priority: Trivial > Attachments: Regular_Expression_With_Apostrophe.PNG, > Regular_Expression_With_Apostrophe_Overlay_Blocked.PNG, > Validation_Message_With_Apostrophe.PNG, > Validation_Message_With_Apostrophe_Overlay_Blocked.PNG > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12928) Job name Enforcer
Daniel Petisme created JENKINS-12928: Summary: Job name Enforcer Key: JENKINS-12928 URL: https://issues.jenkins-ci.org/browse/JENKINS-12928 Project: Jenkins Issue Type: New Feature Components: core Reporter: Daniel Petisme Fix For: current The aim of this feature is to be able to add constraints on job's name. For instance a simple use case is to be sure the jobs created follow a naming convention. This feature comes from the following thread in the jenkins-developer ML. [https://groups.google.com/forum/?hl=fr#!topic/jenkinsci-dev/rsxUpaNAe18] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12897) RROD enhancements: Sort requests, link to config.xml, etc.
Daniel Petisme created JENKINS-12897: Summary: RROD enhancements: Sort requests, link to config.xml, etc. Key: JENKINS-12897 URL: https://issues.jenkins-ci.org/browse/JENKINS-12897 Project: Jenkins Issue Type: Improvement Components: rrod Reporter: Daniel Petisme # Sort the tasks by type. Deletion appears first and then the renaming ones. # add the context root in the URL (hudson/) # Manage if the job already exist (prevent java.lang.IllegalArgumentException: Job FOO already exists hudson.model.AbstractItem.renameTo(AbstractItem.java:177) # Add a link to the config.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12897) RROD enhancements: Sort requests, link to config.xml, etc.
[ https://issues.jenkins-ci.org/browse/JENKINS-12897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12897 started by Daniel Petisme. > RROD enhancements: Sort requests, link to config.xml, etc. > -- > > Key: JENKINS-12897 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12897 > Project: Jenkins > Issue Type: Improvement > Components: rrod >Reporter: Daniel Petisme >Assignee: Daniel Petisme > > # Sort the tasks by type. Deletion appears first and then the renaming ones. > # add the context root in the URL (hudson/) > # Manage if the job already exist (prevent > java.lang.IllegalArgumentException: Job FOO already exists > hudson.model.AbstractItem.renameTo(AbstractItem.java:177) > # Add a link to the config.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12897) RROD enhancements: Sort requests, link to config.xml, etc.
[ https://issues.jenkins-ci.org/browse/JENKINS-12897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Petisme reassigned JENKINS-12897: Assignee: Daniel Petisme > RROD enhancements: Sort requests, link to config.xml, etc. > -- > > Key: JENKINS-12897 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12897 > Project: Jenkins > Issue Type: Improvement > Components: rrod >Reporter: Daniel Petisme >Assignee: Daniel Petisme > > # Sort the tasks by type. Deletion appears first and then the renaming ones. > # add the context root in the URL (hudson/) > # Manage if the job already exist (prevent > java.lang.IllegalArgumentException: Job FOO already exists > hudson.model.AbstractItem.renameTo(AbstractItem.java:177) > # Add a link to the config.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12896) IndexOutOfBoundsException when renaming/deleting several jobs at the same time (RROD plugin)
[ https://issues.jenkins-ci.org/browse/JENKINS-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159555#comment-159555 ] Daniel Petisme commented on JENKINS-12896: -- The requests collection is ordered. If a requests is removed, the sequencing is broken. The requests processing becomes unordered (as it was random). > IndexOutOfBoundsException when renaming/deleting several jobs at the same > time (RROD plugin) > > > Key: JENKINS-12896 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12896 > Project: Jenkins > Issue Type: Bug > Components: rrod >Reporter: Daniel Petisme >Assignee: Daniel Petisme > > Select a set of tasks to do > Apply > Obtain: > java.lang.IndexOutOfBoundsException: Index: 70, Size: 70 > java.util.ArrayList.get(ArrayList.java:338) > com.michelin.cio.jenkins.plugin.rrod.RequestRenameOrDeletePlugin.doManageRequests(RequestRenameOrDeletePlugin.java:83) > Random issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12896) IndexOutOfBoundsException when renaming/deleting several jobs at the same time (RROD plugin)
Daniel Petisme created JENKINS-12896: Summary: IndexOutOfBoundsException when renaming/deleting several jobs at the same time (RROD plugin) Key: JENKINS-12896 URL: https://issues.jenkins-ci.org/browse/JENKINS-12896 Project: Jenkins Issue Type: Bug Components: rrod Reporter: Daniel Petisme Assignee: Daniel Petisme Select a set of tasks to do Apply Obtain: java.lang.IndexOutOfBoundsException: Index: 70, Size: 70 java.util.ArrayList.get(ArrayList.java:338) com.michelin.cio.jenkins.plugin.rrod.RequestRenameOrDeletePlugin.doManageRequests(RequestRenameOrDeletePlugin.java:83) Random issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12896) IndexOutOfBoundsException when renaming/deleting several jobs at the same time (RROD plugin)
[ https://issues.jenkins-ci.org/browse/JENKINS-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12896 started by Daniel Petisme. > IndexOutOfBoundsException when renaming/deleting several jobs at the same > time (RROD plugin) > > > Key: JENKINS-12896 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12896 > Project: Jenkins > Issue Type: Bug > Components: rrod >Reporter: Daniel Petisme >Assignee: Daniel Petisme > > Select a set of tasks to do > Apply > Obtain: > java.lang.IndexOutOfBoundsException: Index: 70, Size: 70 > java.util.ArrayList.get(ArrayList.java:338) > com.michelin.cio.jenkins.plugin.rrod.RequestRenameOrDeletePlugin.doManageRequests(RequestRenameOrDeletePlugin.java:83) > Random issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
