[JIRA] [core] (JENKINS-12983) Redundat syncs when using matrix jobs
Title: Message Title Andy Bigos commented on JENKINS-12983 Re: Redundat syncs when using matrix jobs As the matrix functionality has now moved from the core maybe this issue should be moved to the Matrix Project plugin, or maybe to the Perforce plugin as it seems the 'fix' is most likely to be optimizations to reduce syncing in the P4 plugins itself (if possible). 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] [configurationslicing] (JENKINS-23776) Matrix axes are sometimes treated as jobs
Andy Bigos created JENKINS-23776 Matrix axes are sometimes treated as jobs Issue Type: Bug Affects Versions: current Assignee: mdonohue Attachments: matrix-axes.PNG, matrix-jobs.PNG Components: configurationslicing Created: 14/Jul/14 2:05 PM Description: I'm seeing some odd behaviour for matrix jobs. In some cases I'm seeing each axis of the matrix being treated as a job. When I look at all my jobs in the 'Configuration by View-All' view I see a list of jobs, as expected. I have two views that contain jobs, each of these jobs is a matrix type. In one of the views I see the jobs I expect. In another view I see a list of all axes in the matrix job. I'm attaching 2 files to clarify. Matrix-Jobs.png shows a view containing a list of jobs - the expected behaviour. Matrix-Axes.ping shows a view that is displayed as a list of all the matrix configurations. As the matrix axes view consists of several hundred combinations it's impossible to use. Environment: Jenkins ver. 1.554.3 - stable. Project: Jenkins Priority: Major Reporter: Andy Bigos 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] [configurationslicing] (JENKINS-23777) Support clear/set for all the boolean selection
Andy Bigos created JENKINS-23777 Support clear/set for all the boolean selection Issue Type: New Feature Assignee: mdonohue Components: configurationslicing Created: 14/Jul/14 2:12 PM Description: First thanks for this excellent plugin - nice job. I have a minor suggestion that I think would work quite nicely for handling large numbers of jobs with boolean options. For booleans it would be nice to have a select/clear all items in a view. We have a large number of jobs and often need to disable a group at a time. For example when we go into a release phase we enable a bunch of jobs that don't typically run. Being able to enable/disable all of these jobs in one go would be very useful. Thanks Andy Project: Jenkins Priority: Minor Reporter: Andy Bigos 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] [fstrigger] (JENKINS-17873) FSTrigger does not accept Parameters
Andy Bigos commented on JENKINS-17873 FSTrigger does not accept Parameters Same situation here. Would be good to avoid repeating the value if such as mechanism was possible. 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-21698) Perforce plugin should support credentials
Andy Bigos commented on JENKINS-21698 Perforce plugin should support credentials +1 for this. Would be very useful to keep the P4 password out of the project configuration. I just had a report of a user with permissions to update a project config getting prompted by Firefox if the P4 password should be saved (which belongs to a build bot user). Once it was in the browser manager it would likely be possible to recover the plain-text password. Using credentials would hopefully avoid that issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep] (JENKINS-21491) Time restriction does not work if earliest = latest
Andy Bigos commented on JENKINS-21491 Time restriction does not work if earliest = latest Just hit the same issue. Would be great if the period could span midnight. 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] [xunit] (JENKINS-11191) Test Name Reported as (root)
Andy Bigos commented on JENKINS-11191 Test Name Reported as (root) With xUnit plugin, there is missing the package name, so there is the default 'root' package name. Is it possible to set the package name from the XML? E.g. if the attribute 'package' was present it would be used to set the name? 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] [xunit] (JENKINS-11217) Not all failure cases reported for UnitTest results
Andy Bigos commented on JENKINS-11217 Not all failure cases reported for UnitTest results OK. I'll concat the results before passing to Jenkins. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Andy Bigos commented on JENKINS-20630 Jenkins fails to start +1. Running Win6 x64 as a service and got the same errors. Reverting to 1.539 works. 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] [perforce] (JENKINS-7436) Add support for perforce shelve builds
Andy Bigos commented on JENKINS-7436 Add support for perforce shelve builds .. I can't justify using company time to implement it. Thanks for update Rob, we will look at implementing this via build steps in that case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [perforce] (JENKINS-7436) Add support for perforce shelve builds
Andy Bigos commented on JENKINS-7436 Add support for perforce shelve builds Just bumping this issue as wondering if there has been any progress. It sounds like the way to get something going (at the moment) is as a build step, however it does really seem to fall in the domain of the scm plugin. The complications seem to come from trying to be consistent when the workspace isn't cleaned, which is something I guess most people don't do as it's generally considered best practice to clean the workspace between builds. I would think this was especially true when dealing the pre-commit testing. With that in mind, I wonder if it's possible to do an initial implementation that relies on having a clean workspace? E.g. if a shelved CL is provided (via a parameter) this overrides the clean workspace setting so that it always starts from a known state? That would remove some of the complexity and I guess meet most peoples use cases. Just an idea. I'd be interesting to hear of any progress on the plugin side before we go ahead and implement this as a build step. Ta Andy 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-12393) Support Matrix Projects
[ https://issues.jenkins-ci.org/browse/JENKINS-12393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159754#comment-159754 ] Andy Bigos commented on JENKINS-12393: -- Closing as appears to work. Support Matrix Projects --- Key: JENKINS-12393 URL: https://issues.jenkins-ci.org/browse/JENKINS-12393 Project: Jenkins Issue Type: Improvement Components: log-parser Affects Versions: current Reporter: Andy Bigos Assignee: rgoren Hi, I'm using the plugin without problems on simple builds, but it doesn't appear to support/work for matrix builds. Can you confirm if it's expected to work currently? If not I'd like to request the addition of support for matrix type projects. Thanks Andy -- 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-10606) Support Matrix Builds
[ https://issues.jenkins-ci.org/browse/JENKINS-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159704#comment-159704 ] Andy Bigos commented on JENKINS-10606: -- Hi, Given the title of this issue - can I ask what is the general state of Matrix Job support at the moment? I ask as I have some jobs which have some matrix elements that don't sync. It's pretty random which elements don't get a synced. I have selected: * Let Jenkins Manage Workspace View - TRUE * Let Jenkins Create Workspace - TRUE * Clean Workspace Before Each Build - TRUE * Always Force Sync - TRUE * Poll Only on Master - TRUE Does this behaviour sounds like something you might expect given the current level of support for matrix builds, or should I create a new issue and add more details? Or am I simply missing something in the config? Thanks for help, Andy Support Matrix Builds - Key: JENKINS-10606 URL: https://issues.jenkins-ci.org/browse/JENKINS-10606 Project: Jenkins Issue Type: Improvement Components: perforce Reporter: Rob Petti Assignee: Rob Petti Currently the perforce plugin does not explicitly support matrix builds, which can lead to certain features not working correctly. For example, matrix builds will always use the same client workspace for all sub jobs, requiring a force sync for each one. In addition, each sub job will sync to the latest changeset, which could be different depending on when the jobs run. At the very least, the perforce plugin should sync to the same changeset for all sub jobs. -- 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-10606) Support Matrix Builds
[
https://issues.jenkins-ci.org/browse/JENKINS-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159707#comment-159707
]
Andy Bigos commented on JENKINS-10606:
--
Yes - that was it. Thanks!
I'd set all the other items that had an 'Import Note' about matrix builds - but
the workspace name didn't have one (though it has plenty of others!). At the
risk of adding even more text I'd suggest adding something about this - or even
better, when a matrix job is detected auto-populate the field with ${JOB_NAME}.
That will at least bring the issue to notice.
Anyway - thanks for sorting the issue out so quickly.
Andy
Support Matrix Builds
-
Key: JENKINS-10606
URL: https://issues.jenkins-ci.org/browse/JENKINS-10606
Project: Jenkins
Issue Type: Improvement
Components: perforce
Reporter: Rob Petti
Assignee: Rob Petti
Currently the perforce plugin does not explicitly support matrix builds,
which can lead to certain features not working correctly.
For example, matrix builds will always use the same client workspace for all
sub jobs, requiring a force sync for each one. In addition, each sub job will
sync to the latest changeset, which could be different depending on when the
jobs run. At the very least, the perforce plugin should sync to the same
changeset for all sub jobs.
--
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
