[JIRA] [subversion] (JENKINS-21042) Allow exclusions from SVN polling for certain repository URLs
S Daigle commented on JENKINS-21042 Allow exclusions from SVN polling for certain repository URLs Ah, thank you. I've only been using Jenkins for 6 years or so. I would have found those options in another 5 :-\ Thanks again. Those should work fine. 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-21042) Allow exclusions from SVN polling for certain repository URLs
S Daigle created JENKINS-21042 Allow exclusions from SVN polling for certain repository URLs Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: subversion Created: 17/Dec/13 1:23 PM Description: Many jobs require multiple Subversion repositories. For jobs that poll SVN to start execution, it would be good to allow exemptions for certain repository URLs. For example if I have a "main codebase" URL and a "Tools" URL specified and would only like changes made in the "main codebase" to execute a build, this would be helpful. A simple checkbox to "enable" or "disable" polling. This would stop many jobs from running when they really don't have to and hopefully would also keep these commit operations out of the "SCM files changed" Environment: All Project: Jenkins Priority: Major Reporter: S Daigle 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-15499) HistoryWidget/entry.jelly throws NullPointerException
S Daigle commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Upgraded to latest Jenkins ver. 1.492 today and the "More" link to additional builds is fixed as well as the "buildHistory/all" API. 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
S Daigle commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Mine rolled back without any issues. I diffed the client slave.jar files between 1.484 and 1.489 and they were identical so all I had to do was install the 1.484 jenkins war on the server. Our server is on Ubuntu so all I did was shutdown jenkins, remove the old exploded war/cache, copy the 1.484 war in place and restarted jenkins. Everything came back fine and the "more" links were working again and my API build history scripts worked again. 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-15499) HistoryWidget/entry.jelly throws NullPointerException
S Daigle commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException The only way I could get this to work was to roll back to version 1.484 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-15499) HistoryWidget/entry.jelly throws NullPointerException
S Daigle edited a comment on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Is there any update on this? We also use the API and now all the jobs we have that try accessing the complete build history are failing: wget --no-check-certificate --auth-no-challenge https://jenkins/ci/job/MYBUILD/buildHistory/all -2012-11-08 07:24:07- https://jenkins/ci/job/MYBUILD/all Resolving jenkins... 127.0.1.1, 10.0.0.70 Connecting to jenkins|127.0.1.1|:443... connected. HTTP request sent, awaiting response... 500 Internal Server Error 2012-11-08 07:24:07 ERROR 500: Internal Server Error. If I do not specify the "/all" attribute, it returns successfully. We are running the latest 1.489 version 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
S Daigle commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Is there any update on this? 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-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
[ https://issues.jenkins-ci.org/browse/JENKINS-11024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160172#comment-160172 ] S Daigle commented on JENKINS-11024: Is this issue ever going to be resolved? In companies like mine where adding anonymous read access is not an option, and relying on many of the CLI commands, an issue like this limits the things we can do with Jenkins jobs outside the UI. If anyone has a workaround to this, that would be welcome. > Some commands don't work when using _jenkins-cli.jar with -i switch, get-job > and update-job for sure, not certain about others > -- > > Key: JENKINS-11024 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11024 > Project: Jenkins > Issue Type: Bug > Components: cli > Environment: CLI >Reporter: Timothy Meazell > > Add keys for authenticated login. Works fine with who-am-i, enable-job, > disable-job, delete-job, create-job, but get-job and update-job fail claiming > there is no job by that name. The very same command line with enable-job (as > well as the others) works fine. > Workaround is to see if enable-job fails (which it will if there is no job by > that name, which was the point of using get-job), then delete-job and > create-job instead of update-job if the job already exists. Note that this > workaround causes the loss of job history upon deletion. > Diagnostics: > % java -jar jenkins/_jenkins-cli.jar -s http://localhost:9090/ -i > jenkins/id_rsa get-job trunk-pacman.integration.vdev-regression > No such job 'trunk-pacman.integration.vdev-regression' > java -jar jenkins-cli.jar get-job args... > Dumps the job definition XML to stdout > JOB : Name of the job > --username VAL : User name to authenticate yourself to Jenkins > --password VAL : Password for authentication. Note that passing a >password in arguments is insecure. > --password-file VAL : File that contains the password > % java -jar jenkins/_jenkins-cli.jar -s http://localhost:9090/ -i > jenkins/id_rsa enable-job trunk-pacman.integration.vdev-regression > % echo $? > 0 -- 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
