[JIRA] [template-project-plugin] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title uncletall commented on JENKINS-31712 Re: Use SCM from another project is removed after upgrading to 1.5.1 Brantone: I installed it together with the 1.642.4 LTS in April and upgraded all my plugins. So if the 1.5.2 was available at that point it must have been the one I used. 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] [template-project-plugin] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title uncletall commented on JENKINS-31712 Re: Use SCM from another project is removed after upgrading to 1.5.1 Confirmed that downgrading to 1.4.2 solves this 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] [template-project-plugin] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title uncletall created an issue Jenkins / JENKINS-31712 Use SCM from another project is removed after upgrading to 1.5.1 Issue Type: Bug Assignee: huybrechts Components: template-project-plugin Created: 24/Nov/15 12:45 AM Environment: Ubuntu 14.04 Jenkins 1.625.2 LTS Template Project plugin 1.5.1 Labels: configuration regression plugin Priority: Major Reporter: uncletall I upgraded Jenkins to the latest LTS and the template project plugin from 1.4.2 to 1.5.1. After this all my projects lost the "Use SCM another project". The "Use SCM from another project" option was also not available. However, using builders from another project was still present. Reverting the plugin back to the 1.4.2 version fixed this issue
[JIRA] [core] (JENKINS-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall closed JENKINS-25180 as Fixed Unable to authenticate using LDAP after upgrading to 1.576 or higher I have tested 1.592 and the issue is fixed Change By: uncletall (03/Dec/14 4:00 AM) Status: Open Closed 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/d/optout.
[JIRA] [core] (JENKINS-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall commented on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher I am not so sure how to do that. But I have just tested 1.589 and the problem is still present in this version. I can't find the tag in GitHub and the latest link still points to the 1.588 on the web site so I don't know if the 1.589 is officially released. But as JENKINS-25144 is marked as fixed I would have expected this issue to be fixed 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 -- 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-25144) Basic Authentication in combination with Session is broken
uncletall commented on JENKINS-25144 Basic Authentication in combination with Session is broken Actually, the Apache config I posted allows for something like a single sign-on. Apache authenticates the user and passes the credentials on to the other servers. This way I only need to log in once and have automatic access to Jenkins, Gerrit, MediaWiki and MantisBT. This way I do not need to log in for every single site and the users are manage centrally using LDAP. Very convenient. 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-25144) Basic Authentication in combination with Session is broken
uncletall commented on JENKINS-25144 Basic Authentication in combination with Session is broken There were 89K+ downloads for the LDAP plugin in Sep-2014. I guess indeed that this should be quite common. 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-25144) Basic Authentication in combination with Session is broken
uncletall commented on JENKINS-25144 Basic Authentication in combination with Session is broken Yes, you are right. Maybe this is not as common as I thought it was. Just that I accidentally upgraded Jenkins while upgrading Ubuntu using apt-get upgrade and ended up spending two days fixing my mistake. I would like other people to be spared the trouble. 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-25144) Basic Authentication in combination with Session is broken
uncletall
commented on JENKINS-25144
Basic Authentication in combination with Session is broken
This is my server config. Is there anything I can change to workaround this bug? I am not doing anything with a Session ID, at least not that I am aware of.
AuthBasicProvider ldap
AuthType Basic
AuthName "example.com"
AuthzLDAPAuthoritative off
AuthLDAPURL "ldap://example.com/ou=users,dc=example,dc=com?uid?one"
Require valid-user
RequestHeader set REMOTE_USER %{REMOTE_USER}s
AllowEncodedSlashes On
RewriteEngine On
Order deny,allow
Allow from all
Jenkins
ProxyPass http://192.168.1.2:8080/ci/
ProxyPassReverse /
Order deny,allow
Allow from all
Header edit Location ^http://example.com/ci/ https://example.com/ci/
Gerrit
ProxyPass /r/ http://192.168.1.1:8081/r/ nocanon
Wiki
ProxyPass /wiki/ https://192.168.1.3/wiki/
ProxyPassReverse /wiki/ https://192.168.1.3/wiki/
ProxyPass /w/ https://192.168.1.3/w/
ProxyPassReverse /w/ https://192.168.1.3/w/
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-25144) Basic Authentication in combination with Session is broken
uncletall commented on JENKINS-25144 Basic Authentication in combination with Session is broken Failing to fix this, there should be at least a WARNING on the main page telling people not to install the latest version if the are running behind a reverse proxy. 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-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall edited a comment on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher I don't think that's a good idea. We now have our development environment setup in such a way that 4 (Jenkins, Gerrit, wiki and bugtraker) sites share the same authentication mechanism. Changing that would result in a lot of broken URLs 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-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall commented on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher I did actually mention in the environment description that authentication is done by Apache and passed on to 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/d/optout.
[JIRA] [core] (JENKINS-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall commented on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher I don't think that's a good idea. We now have our development setup in such a way that 4 (Jenkins, Gerrit, wiki and bugtraker) sites share the same authentication mechanism. 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-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall commented on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher I think my definition of LDAP authentication is wrong. The authentication is actually done by the Apache front. LDAP is then used to retrieve the username, email and groups that are used for the authentication. I believe this might actually be basic authentication although in the Security config you need to specify it as LDAP authentication. 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-25144) Basic Authentication in combination with Session is broken
uncletall commented on JENKINS-25144 Basic Authentication in combination with Session is broken Related to: https://issues.jenkins-ci.org/browse/JENKINS-25180 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-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall commented on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher I found a fix here: https://github.com/jenkinsci/jenkins/pull/1427 So I guess this is related to: https://issues.jenkins-ci.org/browse/JENKINS-25144 I build the version from Christof Schoell and tested it on my server. After this the LDAP authentication works and I can get back into the Manage page after enabling security 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-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall
updated JENKINS-25180
Unable to authenticate using LDAP after upgrading to 1.576 or higher
Change By:
uncletall
(17/Oct/14 1:52 AM)
Description:
After upgrading to 1.576 or higher LDAP authentication fails. It is very repeatable and downgrading to 1.575 fixes the issue. I have tried 1.576 1.577 1.580 and 1.584 but am unable to log in.Basically, I disable security and then setup the same config again and am still unable to log in.I am using ldap 1.6 plugin but have also tried 1.11, both fail once I enable ldap authentication.This is my configuration from the config.xml trueldap://ldapfalseou=users,dc=xxx,dc=com,dc=sguid={0}ou=jenkins,ou=groups,dc=xxx,dc=com,dc=sgcn=admin,dc=xxx,dc=com,dc=sgxxxfalse Steps to reproduce:1. Fresh install of Jenkins 1.584 from Ubuntu apt-get install jenkins2. Enter settings as can be used up to 1.5753. Add the display name is the cn4. Authorization: Anyone can do anything (I used matrix before but for now I am happy to login)5. Save6. My name is shown as "Peter Bruin", proof that this was retrieved from ldap or else it would be peterbruin which is my user name7. Navigate back to Manage and I get prompted for password8. No log entries in /var/log/jenkins/jenkins.log9. Unable to access the system log (/log/all) as I am not able to access Jenkins10. Downgrade to 1.575 and I can log in againHow this affected my upgrade:1. Upgrade from 1.557 to 1.5842. Able to acess jenkins until I wanted to go Manage3. Prompted for password and unable to login4. Editted the config.xml and disable security5. Updated
LDAP
plugin from 1.6 to latest6. Spend hours messing around with ldap settings7. Need to restart server after every time, takes a few minutes8. Downgraded and was able to log in againOfcourse my bad for doing this on our production server but I didn't expect this kind of trouble. Cost me most of the last two days trying to get it working.Any help with trouble shooting would be welcome. How can I get more log info out of Jenkins, I don't see much in the /var/log/jenkins/jenkins.log file and the System Log is useless as I am unable to access it after I enable security
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-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall
updated JENKINS-25180
Unable to authenticate using LDAP after upgrading to 1.576 or higher
Change By:
uncletall
(17/Oct/14 1:50 AM)
Description:
After upgrading to 1.576 or higher LDAP authentication fails. It is very repeatable and downgrading to 1.575 fixes the issue. I have tried 1.576 1.577 1.580 and 1.584 but am unable to log in.Basically, I disable security and then setup the same config again and am still unable to log in.I am using ldap 1.6 plugin but have also tried 1.11, both fail once I enable ldap authentication.This is my configuration from the config.xml trueldap://ldapfalseou=users,dc=xxx,dc=com,dc=sguid={0}ou=jenkins,ou=groups,dc=xxx,dc=com,dc=sgcn=admin,dc=xxx,dc=com,dc=sgxxxfalse Steps to reproduce:1. Fresh install of Jenkins 1.584 from Ubuntu apt-get install jenkins2. Enter settings as can be used up to 1.5753. Add the display name is the cn4. Authorization: Anyone can do anything (I used matrix before but for now I am happy to login)5. Save6. My name is shown as "Peter Bruin", proof that this was retrieved from ldap or else it would be peterbruin which is my user name7. Navigate back to Manage and I get prompted for password8. No log entries in /var/log/jenkins/jenkins.log9. Unable to access the system log (/log/all) as I am not able to access Jenkins10. Downgrade to 1.575 and I can log in again
How this affected my upgrade:1. Upgrade from 1.557 to 1.5842. Able to acess jenkins until I wanted to go Manage3. Prompted for password and unable to login4. Editted the config.xml and disable security5. Updated plugin from 1.6 to latest6. Spend hours messing around with ldap settings7. Need to restart server after every time, takes a few minutes8. Downgraded and was able to log in againOfcourse my bad for doing this on our production server but I didn't expect this kind of trouble. Cost me most of the last two days trying to get it working.Any help with trouble shooting would be welcome. How can I get more log info out of Jenkins, I don't see much in the /var/log/jenkins/jenkins.log file and the System Log is useless as I am unable to access it after I enable security
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-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall
updated JENKINS-25180
Unable to authenticate using LDAP after upgrading to 1.576 or higher
Change By:
uncletall
(17/Oct/14 1:40 AM)
Environment:
ubuntu 12.04 and 14.04 openldap
, authentication is normally done by Apache and the user information should be retrieved by Jenkins from ldap.
Description:
After upgrading to 1.576 or higher LDAP authentication fails. It is very repeatable and downgrading to 1.575 fixes the issue. I have tried 1.576 1.577 1.580 and 1.584 but am unable to log in.Basically, I disable security and then setup the same config again and am still unable to log in.I am using ldap 1.6 plugin but have also tried 1.11, both fail once I enable ldap authentication.This is my configuration from the config.xml trueldap://ldapfalseou=users,dc=xxx,dc=com,dc=sguid={0}ou=jenkins,ou=groups,dc=xxx,dc=com,dc=sgcn=admin,dc=xxx,dc=com,dc=sgxxxfalse
Steps to reproduce:1. Fresh install of Jenkins 1.584 from Ubuntu apt-get install jenkins2. Enter settings as can be used up to 1.5753. Add the display name is the cn4. Authorization: Anyone can do anything (I used matrix before but for now I am happy to login)5. Save6. My name is shown as "Peter Bruin", proof that this was retrieved from ldap or else it would be peterbruin which is my user name7. Navigate back to Manage and I get prompted for password8. No log entries in /var/log/jenkins/jenkins.log9. Unable to access the system log (/log/all) as I am not able to access Jenkins10. Downgrade to 1.575 and I can log in 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
--
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-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall
created JENKINS-25180
Unable to authenticate using LDAP after upgrading to 1.576 or higher
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
16/Oct/14 9:40 AM
Description:
After upgrading to 1.576 or higher LDAP authentication fails. It is very repeatable and downgrading to 1.575 fixes the issue. I have tried 1.576 1.577 1.580 and 1.584 but am unable to log in.
Basically, I disable security and then setup the same config again and am still unable to log in.
I am using ldap 1.6 plugin but have also tried 1.11, both fail once I enable ldap authentication.
This is my configuration from the config.xml
true
ldap://ldap
false
ou=users,dc=xxx,dc=com,dc=sg
uid={0}
ou=jenkins,ou=groups,dc=xxx,dc=com,dc=sg
cn=admin,dc=xxx,dc=com,dc=sg
xxx
false
Environment:
ubuntu 12.04 and 14.04 openldap
Project:
Jenkins
Priority:
Blocker
Reporter:
uncletall
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.
