[JIRA] [perforce] (JENKINS-12101) Post-commit hook for Perforce plugin
Ignacio Llamas edited a comment on JENKINS-12101 Post-commit hook for Perforce plugin Assigning to one of the Perforce plugin maintainers to ask a question. Perforce already has a trigger mechanism, all that needs to be done is add support for that on Jenkins, similar to that in the Subversion and Git plugins: https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin Something like this I imagine would be executed in the perforce trigger script: /usr/bin/wget \ --header "Content-Type:text/plain;charset=UTF-8" \ --post-data "$CHANGELIST $P4_PATH`" \ -output-document "" \ --timeout=2 \ http://server/perforce/notifyCommit?rev=$REV Is there any other way of doing this already? (Polling the repository seems like a suboptimal solution. Can miss changelists, and has to be done quite frequently) 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-12101) Post-commit hook for Perforce plugin
Ignacio Llamas commented on JENKINS-12101 Post-commit hook for Perforce plugin Thanks. Do you mean something like what is described in the last post in http://stackoverflow.com/questions/16435315/jenkins-perforce-plugin-multiple-changelists-in-a-single-poll ? Or do you perhaps have an example polling script that does what you suggest? 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-12101) Post-commit hook for Perforce plugin
Rob Petti commented on JENKINS-12101 Post-commit hook for Perforce plugin Sorry, I meant to type trigger script, not polling script. They are two different things entirely. It depends on what you intend. That stack overflow question is specifically about running a build per change list, not necessarily about a post commit trigger as this ticket describes. In the case of this ticket, you would need to write a post commit trigger in perforce that analyzes each change, and kicks off the associated builds using the Jenkins REST api or CLI. As I mentioned, the script will need to do the heavy lifting, since there's no "notifyCommit" interface yet, which is what this ticket is for. 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-17863) -Xrs switch missing on Windows slaves
Markus KARG commented on JENKINS-17863 -Xrs switch missing on Windows slaves I can reproduce the failure as often as you like. Just tell me what you want me exactly to do. Here is what I tried today: Logged in to XP slave using RDP. Start build process (build type is "run ant") using Jenkins Console. The process builds on XP slave. Logged out from XP slave / closed RDP connection. Here is the result as seen on the build console view: ... Build step 'Ant aufrufen' marked build as failure Sending e-mails to: k...@quipsy.de CIFS: Current build result is FAILURE, not going to run. Finished: FAILURE ... As you can see, Ant is cancelled due to the logout. So I assume that the jenkins client is itself running with -Xrs but possibly starts another Java process to run Ant, but does not supply -Xrs THERE? Regards -Markus 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-multijob-plugin] (JENKINS-18746) MultiJob override Configure Global Security configuration
Rotem G created JENKINS-18746 MultiJob override Configure Global Security configuration Issue Type: Bug Assignee: Unassigned Components: jenkins-multijob-plugin Created: 14/Jul/13 7:41 AM Description: MultiJob override Configure Global Security configuration. For user without "JOB" "CANCEL" Permissions, user IS able to Aborted MultiJob. Environment: Jenkins ver. 1.509.1 Jenkins Multijob plugin 1.9 Project: Jenkins Priority: Major Reporter: Rotem G 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-18734) BuildStepCompatibilityLayer.perform throws UnsupportedOperation when invoked using classes that subclass Build
kutzi commented on JENKINS-18734 BuildStepCompatibilityLayer.perform throws UnsupportedOperation when invoked using classes that subclass Build I see. See pull request for additional remarks. 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] [subversion] (JENKINS-18747) Checkouts from Subversion 1.7 server fail
Quentin Hartman updated JENKINS-18747 Checkouts from Subversion 1.7 server fail Change By: Quentin Hartman (14/Jul/13 3:10 PM) Summary: CheckoutsfromSubversion1.7server fails fail 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] [subversion] (JENKINS-18747) Checkouts from Subversion 1.7 server fails
Quentin Hartman created JENKINS-18747 Checkouts from Subversion 1.7 server fails Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: svn_trace.txt Components: subversion Created: 14/Jul/13 3:10 PM Description: I recently started migrating my projects from a subversion 1.6 server to a 1.7.9 server. Both use dav_svn through Apache. Since then, about 1 out of every 3 builds will fail with a "connection timed out" stack trace from the SVN plugin. This is happening with multiple projects, usually when getting an external. The new server should be substantially more performant than the old one, and is on a much faster network. If I move all the SCM tasks into scripts and use a "real" SVN 1.7 client, everything works reliably. Additionally, all my users have no trouble using the new server. Only Jenkins is failing. Full trace attached. Project: Jenkins Priority: Major Reporter: Quentin Hartman 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] [build-flow] (JENKINS-14938) Unable to change SSH site value on free flow job
Daniel Beck commented on JENKINS-14938 Unable to change SSH site value on free flow job Could you clarify whether you mean 'Build Flow' or 'Freestyle'? 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] [build-flow] (JENKINS-15900) A build failure in a parallel section does not mark it as failed
Daniel Beck
resolved JENKINS-15900 as Fixed
A build failure in a parallel section does not mark it as failed
I set up the following minimal(ish) test flow on Jenkins 1.509.2 with Build Flow 0.9:
parallel (
{ build("test-b") },
{ build("test-c") }
)
build ("test-a")
test-b is set up to always fail. Result:
Started by user anonymous
Building in workspace /Users/danielbeck/Projects/Jenkins/Home-1.509.2/jobs/flow/workspace
parallel {
Trigger job test-c
Trigger job test-b
test-c #1 completed
test-b #1 completed : FAILURE
}
Finished: FAILURE
test-a was never triggered. Closing this as resolved, probably by the commit linked above.
Change By:
Daniel Beck
(14/Jul/13 3:33 PM)
Status:
Open
Resolved
Resolution:
Fixed
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] [build-flow] (JENKINS-15900) A build failure in a parallel section does not mark it as failed
Daniel Beck
edited a comment on JENKINS-15900
A build failure in a parallel section does not mark it as failed
I set up a test flow on Jenkins 1.509.2 with Build Flow 0.9 like in the issue description. test-b is set up to always fail. Result:
Started by user anonymous
Building in workspace /Users/danielbeck/Projects/Jenkins/Home-1.509.2/jobs/flow/workspace
guard {
Trigger job test-a
test-a #1 completed
parallel {
Trigger job test-b
Trigger job test-c
test-c #2 completed
test-b #2 completed : FAILURE
}
} rescue {
Trigger job test-f
test-f #1 completed
}
Finished: FAILURE
test-d/test-e were never triggered. Closing this as resolved, probably by the commit linked above.
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] [build-flow] (JENKINS-18179) Allow Build Hiding in Build History
Daniel Beck commented on JENKINS-18179 Allow Build Hiding in Build History This isn't actually related to the build flow plugin, is it? https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin 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] [build-flow] (JENKINS-13914) Fixed width font for DSL
Daniel Beck commented on JENKINS-13914 Fixed width font for DSL Firefox browser uses fixed width font for multiline text boxes by default, so this might hide the issue for many users. 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] [build-flow] (JENKINS-13914) Fixed width font for DSL
Daniel Beck edited a comment on JENKINS-13914 Fixed width font for DSL (removed) 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] [build-flow] (JENKINS-16980) build flow need sandboxing
Daniel Beck commented on JENKINS-16980 build flow need sandboxing Simple fix until a proper solution can be designed in https://github.com/jenkinsci/build-flow-plugin/pull/33 (Shameless ripoff of https://github.com/jenkinsci/envinject-plugin/commit/96a526963b53819828c3a58ad7ea25dd8bfba244) 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] [ownership] (JENKINS-18740) Add support of co-owners
Oleg Nenashev started work on JENKINS-18740 Add support of co-owners Change By: Oleg Nenashev (14/Jul/13 6:16 PM) Status: Open InProgress 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] [role-strategy] (JENKINS-18700) Add support of macro-roles and macro-slaves
Oleg Nenashev started work on JENKINS-18700 Add support of macro-roles and macro-slaves Change By: Oleg Nenashev (14/Jul/13 7:32 PM) Status: Open InProgress 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] [role-strategy] (JENKINS-18700) Add support of macro-roles and macro-users
Oleg Nenashev updated JENKINS-18700 Add support of macro-roles and macro-users Change By: Oleg Nenashev (14/Jul/13 7:32 PM) Summary: Addsupportofmacro-rolesandmacro- slaves users 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] [role-strategy] (JENKINS-18748) Add support of slave roles assigments
Oleg Nenashev created JENKINS-18748 Add support of slave roles assigments Issue Type: New Feature Assignee: Oleg Nenashev Components: role-strategy Created: 14/Jul/13 7:35 PM Description: Just add individual setup of slave's permissions (as it has be done for slave) See https://github.com/jenkinsci/role-strategy-plugin/pull/3 for more info Project: Jenkins Priority: Major Reporter: Oleg Nenashev 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] [ssh-slaves] (JENKINS-8856) StreamCorruptedException
Indra Gunawan commented on JENKINS-8856 StreamCorruptedException Is there a RedHat rpm available for this version? http://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/1.509.2.JENKINS-8856-diag/jenkins-war-1.509.2.JENKINS-8856-diag.war Thanks. -Indra 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-7593) Master Slave connection error
zhijing wu commented on JENKINS-7593 Master Slave connection error With Jenkins 1.455, still meet this problem. The master lost connection with the slave regularly, which makes a big problem. I think Jenkins need to do better in the master-slave connection. 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] [jobgenerator] (JENKINS-18663) Generator triggers the build step using conditional build step
Sylvain Benner resolved JENKINS-18663 as Fixed Generator triggers the build step using conditional build step Change By: Sylvain Benner (15/Jul/13 3:21 AM) Status: InProgress Resolved Resolution: Fixed 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] [jobgenerator] (JENKINS-18663) Generator triggers the build step using conditional build step
Sylvain Benner commented on JENKINS-18663 Generator triggers the build step using conditional build step I fixed the bug and I'm just about to release the 1.16. The fix is in 2 parts: correctly keep the build step in the generated job remove the trigger of freestyle jobs when they are part of a job generator hierarchy. If the job triggered in a conditional build step is a job generator then it will be correctly executed as expected. 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.
