[JIRA] [bitbucket-oauth-plugin] (JENKINS-34792) Bitbucket plugin broken after Jenkins upgrade to 2.3
Title: Message Title Kristoffer Peterhänsel commented on JENKINS-34792 Re: Bitbucket plugin broken after Jenkins upgrade to 2.3 It has to be set as a system property at start (JVM -D option). Not sure if there is another way to do it 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] [amazon-ecr-plugin] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Kristoffer Peterhänsel edited a comment on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials So I can't quite manually provoke this error message using the AWS CLI tool and docker. But it does appear that the credentials issued are regional. So it seems this plugin may need a way to set the desired region. But so far I haven't found the place in the AmazonECRClient where you can actually specify region... Edit: And then of course I did find see it. 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] [amazon-ecr-plugin] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Kristoffer Peterhänsel commented on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials So I can't quite manually provoke this error message using the AWS CLI tool and docker. But it does appear that the credentials issued are regional. So it seems this plugin may need a way to set the desired region. But so far I haven't found the place in the AmazonECRClient where you can actually specify region... 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] [amazon-ecr-plugin] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Kristoffer Peterhänsel created an issue Jenkins / JENKINS-34958 Getting "Your Authorization Token has expired" when using ECR credentials Issue Type: Bug Assignee: Nicolas De Loof Components: amazon-ecr-plugin Created: 2016/May/19 2:14 PM Environment: Jenkins 2.4 Docker Build and Publish plugin 1.2.2 (+ PR #41) Priority: Blocker Reporter: Kristoffer Peterhänsel In an attempt to start moving away from our self-hosted Docker Registry. I came across this plugin to make it easier to push to Amazon ECR. And after a (fairly) quick fix of the Docker Build and Publish plugin. Time had come to make that happen. But instead I am getting the this error when it attempt to push. So something is wrong. The push refers to a repository [somerepo.dkr.ecr.eu-west-1.amazonaws.com/imagename] 1b29323a75d2: Preparing 5bf87793f977: Preparing 5ccb950f635d: Preparing 965c3fc60463: Preparing f354df03c5c3: Preparing 5f70bf18a086: Preparing 5f70bf18a086: Preparing 9523ecdf69b1: Preparing 5f70bf18a086: Preparing 5f70bf18a086: Preparing 5f70bf18a086: Preparing 5f70bf18a086: Preparing 6d7b4f405a28: Preparing 5f70bf18a086: Preparing 5f70bf18a086: Preparing 099efa904cb9: Preparing 8f83f19c7186: Preparing
[JIRA] [bitbucket-oauth-plugin] (JENKINS-34792) Bitbucket plugin broken after Jenkins upgrade to 2.3
Title: Message Title Kristoffer Peterhänsel commented on JENKINS-34792 Re: Bitbucket plugin broken after Jenkins upgrade to 2.3 Setting hudson.model.User.SECURITY_243_FULL_DEFENSE=false (as suggested on the mailing list seems to make it go too 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] [nodejs-plugin] (JENKINS-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"
Title: Message Title Kristoffer Peterhänsel commented on JENKINS-27170 Re: "Provide Node & npm bin/ folder to PATH" not working for "npm install" Well. As a matter of fact. I took it upon myself to fix it and submitted the PR#6 - which was then greatly improved by Marcin Stanisławski . So it awaits review now. 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] [nodejs-plugin] (JENKINS-28491) npm ERR! Linux 3.2.0-4-amd64 - Add version 0.12.4 in auto install
Title: Message Title Kristoffer Peterhänsel resolved as Fixed Seems 0.12.4 is there now. I'm guessing the list is being loaded from the NodeJS site somehow. As it also does not always load - resulting in no selector at all. The other described in the comment looks like JENKINS-27170 Jenkins / JENKINS-28491 npm ERR! Linux 3.2.0-4-amd64 - Add version 0.12.4 in auto install Change By: Kristoffer Peterhänsel Status: Open Resolved Resolution: Fixed 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] [nodejs-plugin] (JENKINS-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"
Title: Message Title Kristoffer Peterhänsel commented on JENKINS-27170 Re: "Provide Node & npm bin/ folder to PATH" not working for "npm install" Same sort of issue trying to install node-sass 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] [nodejs-plugin] (JENKINS-29077) No selector is shown for installing NodeJS from nodejs.org
Title: Message Title Kristoffer Peterhänsel commented on JENKINS-29077 Re: No selector is shown for installing NodeJS from nodejs.org This appears to have solved itself. So I am guessing it was an issue with loading the list from the NodeJS website?. I changed the issue to be a minor issue instead. It should likely be showing something more useful in a situation like this - to avoid confusions like the one I experienced. 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] [nodejs-plugin] (JENKINS-29077) No selector is shown for installing NodeJS from nodejs.org
Title: Message Title Kristoffer Peterhänsel updated an issue Jenkins / JENKINS-29077 No selector is shown for installing NodeJS from nodejs.org Change By: Kristoffer Peterhänsel Priority: Major Minor 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] [nodejs-plugin] (JENKINS-29077) No selector is shown for installing NodeJS from nodejs.org
Title: Message Title Kristoffer Peterhänsel created an issue Jenkins / JENKINS-29077 No selector is shown for installing NodeJS from nodejs.org Issue Type: Bug Assignee: Unassigned Attachments: Broken NodeJS plugin.PNG Components: nodejs-plugin Created: 25/Jun/15 9:01 AM Environment: Jenkins 1.609.1 NodeJS Plugin 0.2.1 Running in a Docker container on Ubuntu 14.10 Priority: Major Reporter: Kristoffer Peterhänsel It appears that the version selector for installing NodeJS is broken. As can be seen in the attached screenshot an input box is simply shown instead of the selector that is supposed to be there.
[JIRA] [docker-build-step-plugin] (JENKINS-27369) Image push fails with "FATAL: authConfig was not specified"
Kristoffer Peterhänsel commented on JENKINS-27369 Image push fails with "FATAL: authConfig was not specified" Creating an empty credentials entry makes it run for me. But that is just a workaround 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-13153) "Upgrade Automatically" does not seem to work on Windows
Kristoffer Peterhänsel commented on JENKINS-13153 "Upgrade Automatically" does not seem to work on Windows Not a clue. I no longer work at the place where we had that installation. And don't really have anywhere to replicate the setup either. 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] (JENKINS-15509) It should not be required to enter a group name
Kristoffer Peterhänsel created JENKINS-15509 It should not be required to enter a group name Issue Type: Bug Affects Versions: current Assignee: Thorsten Heit Components: crowd2 Created: 12/Oct/12 11:44 AM Description: I am not quite sure I understand why it is "cool" to be able to enter group names in Jenkins and restrict users that way. Since one of the points of Crowd is that you can set up a lot of stuff in that end and have all that centralized. Haven't seen the setup in JIRA or Confluence. But it sounds pretty strange that they do that as it just seems like a redundant step to me. But anyway. Since I'd rather set up the groups that have access in my Crowd instance. It would be nice if I didn't need to jump though the hoop of creating a group and entering it into Jenkins to get this plugin working. Also the group I grant access to Jenkins come from an Active Directory and contain spaces. So I couldn't actually enter that if I wanted. Project: Jenkins Priority: Major Reporter: Kristoffer Peterhänsel 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-13153) "Upgrade Automatically" does not seem to work on Windows
Kristoffer Peterhänsel created JENKINS-13153:
Summary: "Upgrade Automatically" does not seem to work on Windows
Key: JENKINS-13153
URL: https://issues.jenkins-ci.org/browse/JENKINS-13153
Project: Jenkins
Issue Type: Bug
Components: update-center
Environment: Windows 2003 R3
Java 1.6.0_26
Apache httpd 2.2 as frontend (apj13 proxy)
Reporter: Kristoffer Peterhänsel
After moving to a Jenkins installation that runs as a service. I noticed it now
had the option to download new versions of itself and upgrade. I tried that
with 1.452 and was a bit confused that it restarted but still showed 1.452 as
version number. But also gives me the option to downgrade to 1.452.
After a couple more tries I think I can conclude that what happens is that it
downloads the new version just fine (as jenkins.war.tmp) and copies the current
version fine as well (jenkins.war.bak). But it never actually gets around to
replacing the current running version with the new one.
This appears to be the relevant part of the jenkins.err.log:
{noformat}
INFO: Starting the installation of jenkins.war on behalf of kpe
Mar 19, 2012 9:17:19 AM hudson.model.UpdateCenter$UpdateCenterConfiguration
download
INFO: Downloading jenkins.war
Mar 19, 2012 9:17:19 AM hudson.model.UpdateCenter doSafeRestart
INFO: Scheduling Jenkins reboot
Mar 19, 2012 9:17:40 AM hudson.model.UpdateCenter$DownloadJob run
INFO: Installation successful: jenkins.war
{noformat}
But I am a bit confused on how this would ever actually work on Windows? Since
files are generally locked up pretty tight. So replacing or overwriting a file
that Java is actively using would be practically impossible. And instead it
would require some sort of utility running before starting Jenkins to replace
the war file with the newly downloaded one.
--
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
