[JIRA] (JENKINS-50152) SCM does not capture Nodes
Title: Message Title C. Alex Reober commented on JENKINS-50152 Re: SCM does not capture Nodes What: Change the requirment to look for any version control system. Why: with if a team uses TFS or some other version control system. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50153) SCM requires Subversion plugin
Title: Message Title C. Alex Reober created an issue Jenkins / JENKINS-50153 SCM requires Subversion plugin Issue Type: Improvement Assignee: Craig Rodrigues Components: scm-sync-configuration-plugin, subversion-plugin Created: 2018-03-13 18:24 Environment: Jenkins ver. 2.111 SCM Sync Configuration = 0.0.10 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS" Priority: Major Reporter: C. Alex Reober What: doing a recovery of my system reinstalling the SCM configuration plugin required Subversion plugin. What: remove that requirement. Why: This is un-necessary for Git users and add a plugin that is not needed. Add Comment
[JIRA] (JENKINS-50152) SCM does not capture Nodes
Title: Message Title C. Alex Reober created an issue Jenkins / JENKINS-50152 SCM does not capture Nodes Issue Type: Bug Assignee: Craig Rodrigues Components: scm-sync-configuration-plugin Created: 2018-03-13 18:03 Environment: Jenkins ver. 2.111 SCM Sync Configuration = 0.0.10 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS" Priority: Critical Reporter: C. Alex Reober What: When doing a recovery the nodes are not being recovered. What: Add node configurations in the backup and restore process. Why: Better and faster recovery of the system. Add Comment
[JIRA] (JENKINS-26904) Add the ability to change interval between SCM polls
Title: Message Title C. Alex Reober updated an issue Jenkins / JENKINS-26904 Add the ability to change interval between SCM polls Change By: C. Alex Reober Request the ability to change how often the SCM sync config plugin runs and pushes configs to the repo. This would allow the Admin to determine what is an optimal backup plan for there enviromment their environment . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [scm-sync-configuration-plugin] (JENKINS-26904) Add the ability to change interval between SCM polls
C. Alex Reober created JENKINS-26904 Add the ability to change interval between SCM polls Issue Type: Improvement Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 11/Feb/15 4:25 PM Description: Request the ability to change how often the SCM sync config plugin runs and pushes configs to the repo. This would allow the Admin to determine what is an optimal backup plan for there enviromment. Environment: All Project: Jenkins Labels: enhancement plugin Priority: Minor Reporter: C. Alex Reober 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] [scm-sync-configuration-plugin] (JENKINS-25129) SCM Sync Shows Errors in the logs but GIT show no issues.
C. Alex Reober updated JENKINS-25129 SCM Sync Shows Errors in the logs but GIT show no issues. Change By: C. Alex Reober (09/Feb/15 8:27 PM) Priority: Minor Major 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] [scm-sync-configuration-plugin] (JENKINS-25129) SCM Sync Shows Errors in the logs but GIT show no issues.
C. Alex Reober commented on JENKINS-25129 SCM Sync Shows Errors in the logs but GIT show no issues. This is becoming a major issue: updated the system: Jenkins ver. 1.598 Now the message is: [DATE-TIME] Error while copying file hierarchy to SCM checkouted directory 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-plugin] (JENKINS-26767) When trying to change configuration of Jobs Jenkins hangs.
C. Alex Reober commented on JENKINS-26767 When trying to change configuration of Jobs Jenkins hangs. Thanks inheritance-plugin = 1.5.3 Trying to down grade this to 1.5.0 which was updated. 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-26767) When trying to change configuration of Jobs Jenkins hangs.
C. Alex Reober created JENKINS-26767 When trying to change configuration of Jobs Jenkins hangs. Issue Type: Bug Assignee: Unassigned Attachments: Jenkins-ver.1.598_Stack_Trace .txt, Jenkins_Screen_Shot_2015-02-03_at_1.14.01_PM.png Components: core Created: 03/Feb/15 9:59 PM Description: From the Job page click to "Configure" the job and get the attached error. Environment: OS =Amazon Linux AMI JAVA = 1.7.0_75 OpenJDK Runtime Environment (amzn-2.5.4.0.53.amzn1-x86_64 u75-b13) JENKINS = 1.598 Project: Jenkins Priority: Blocker Reporter: C. Alex Reober 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-26767) When trying to change configuration of Jobs Jenkins hangs.
C. Alex Reober commented on JENKINS-26767 When trying to change configuration of Jobs Jenkins hangs. This is happening on multiple jobs with different setup and plugin usage. 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-25129) SCM Sync Shows Errors in the logs but GIT show no issues.
C. Alex Reober created JENKINS-25129 SCM Sync Shows Errors in the logs but GIT show no issues. Issue Type: Bug Assignee: Frédéric Camblor Attachments: Error.txt Components: core, scm-sync-configuration Created: 13/Oct/14 4:58 PM Description: I have had to turn off the "Dsiplay SCM Sync Status" on my system, because I am getting the attached error twice every 20 minutes or so, and it is making the screen scroll to display all the errors. Checking the SCM process to fix I cd to /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration Run "git status", and get the this: On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean Still get the same error on the next run. Environment: AWS Instance = Amazon Linux AMI release 2014.09 Jenkins = ver. 1.582 SCM Sync Configuration Plugin = 0.0.8 Project: Jenkins Priority: Minor Reporter: C. Alex Reober 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-25129) SCM Sync Shows Errors in the logs but GIT show no issues.
C. Alex Reober commented on JENKINS-25129 SCM Sync Shows Errors in the logs but GIT show no issues. More info: git version git version 2.1.0 java -version java version "1.7.0_65" OpenJDK Runtime Environment (amzn-2.5.1.2.45.amzn1-x86_64 u65-b17) OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) 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-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. This was the current version of the time, as of more then a year ago I do not know. 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-21163) Git Plugin causes Jenkins to stop working
C. Alex Reober commented on JENKINS-21163 Git Plugin causes Jenkins to stop working Yes that was my initial solution. 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-21163) Git Plugin causes Jenkins to stop working
C. Alex Reober created JENKINS-21163 Git Plugin causes Jenkins to stop working Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: core, git, git-client, git-server Created: 27/Dec/13 6:53 PM Description: Adding the Git plugin cause the Jenkins server to fail on next restart. Jenkins shows the following error: hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:234) Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:908) at jenkins.model.Jenkins.init(Jenkins.java:807) at hudson.model.Hudson.init(Hudson.java:82) at hudson.model.Hudson.init(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:109) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:897) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) Caused by: java.lang.reflect.InvocationTargetException 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:622) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) ... 8 more Caused by: java.lang.NullPointerException at hudson.plugins.git.GitTool.onLoaded(GitTool.java:105) ... 13 more Environment: Ubuntu 12.04 in AWS Project: Jenkins Priority: Critical Reporter: C. Alex Reober 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-21163) Git Plugin causes Jenkins to stop working
C. Alex Reober commented on JENKINS-21163 Git Plugin causes Jenkins to stop working More Info: System that does NOT work: jenkins-1a java -version java version "1.6.0_27" OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1ubuntu0.12.04.4) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) git --version git version 1.7.9.5 Git Plugin 2.0 This plugin allows use of Git as a build SCM. a recent Git runtime is required (1.7 recommended). Base feature may work on earlier versions, but can't guarantee. System that does work: jenkins-1b java -version java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.14) (amazon-65.1.11.14.57.amzn1-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) git --version git version 1.8.3.1 Jenkins GIT plugin 2.0 This plugin integrates GIT with Jenkins. 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-17183) Exception: java.lang.NullPointerException
C. Alex Reober commented on JENKINS-17183 Exception: java.lang.NullPointerException Update: This is not working still in Jenkins ver. 1.522 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-17874) Git Plugin Does not allow Passwords to be entered.
C. Alex Reober created JENKINS-17874 Git Plugin Does not allow Passwords to be entered. Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: core, git, git-client Created: 06/May/13 4:33 PM Description: I have set up my git repo to use ssh and LDAP for authentication. CLI git works fine using the accounts in LDAP. When try to pull from the git via Jenkins git plugin or git-client plugin, the deploy fails because the plugins do not allow a password to entered for the LDAP system. Environment: AWS; Jenkins: AWS Linux AMI release 2013.03 Git: Ubuntu 12.04.2 LTS OpenLDAP: openldap-2.4.28 Project: Jenkins Priority: Major Reporter: C. Alex Reober 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-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Thank you, but mine is a RHEL/CentOS flavor, and it is referencing the same process that is failing for me just in the Ubuntu OS. 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-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober edited a comment on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Thank you, and reading the page this is a similar issue. But mine is a RHEL/CentOS flavor, and it is referencing the same process that is failing for me in the Ubuntu OS. and references a fix that I do not know if there is a authbind system in RHEL/CentOS? 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-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. I understand what you are saying about binding to the port it just like the Apache user for httpd and port 80, but this issue also manifest when I try to make this a headless system and change the port to -1 That is what lead me to this as an issue with the Jenkins system and not a port binding 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] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Per the docs and the notes this setting should be modifiable, and the system should use the non-privileged user that is set it the /etc/sysconfig/jenkins 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-17183) Exception: java.lang.NullPointerException
C. Alex Reober created JENKINS-17183 Exception: java.lang.NullPointerException Issue Type: Bug Affects Versions: current Assignee: jieryn Attachments: jenkins_job-import_issue.txt Components: core, job-import Created: 12/Mar/13 6:17 PM Description: Run the job importer Enter the "Remote Jenkins URL:" Hit Query! button Remote Jenkins Job Selection show the job with the check box Check the box Hit Import! GET the info in the attached file. Environment: Jenkins 1.504 and Job-Import Plugin 1.0 Project: Jenkins Priority: Major Reporter: C. Alex Reober 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-17183) Exception: java.lang.NullPointerException
C. Alex Reober commented on JENKINS-17183 Exception: java.lang.NullPointerException Could be the same as JENKINS-15040 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-17183) Exception: java.lang.NullPointerException
C. Alex Reober commented on JENKINS-17183 Exception: java.lang.NullPointerException Confirmed it is not the same issue removed security from the systems and am still getting the error. 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-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. I need at least some sort of work around, or some kind of temporary fix. 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-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober updated JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Change By: C. Alex Reober (04/Mar/13 4:57 PM) Component/s: core Component/s: multi-slave-config 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-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober created JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Issue Type: Bug Affects Versions: current Assignee: rsandell Components: multi-slave-config Created: 28/Feb/13 5:55 PM Description: Install Jenkins via RPM per instructions. (There is nothing else running on the system, i.e. httpd, etc.) Edit /etc/sysconfig/jenkins Change JENKINS_PORT from JENKINS_PORT="8080" to JENKINS_PORT="80" or any other setting (i.e. -1) Restart jenkins using service jenkins restart Get Starting Jenkins [ OK ] check status service jenkins status Get jenkins dead but pid file exists No information in logs of what, when, or why. Due Date: 08/Mar/13 12:00 AM Environment: AWS: AWS Linux 3.2.12-3.2.4.amzn1.x86_64 AMI: ami-f619c29f Zone: us-east-1d Project: Jenkins Labels: jenkins configuration Priority: Major Reporter: C. Alex Reober 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.
