[JIRA] (JENKINS-56896) Shutdown message 'INFOS: JVM is terminating. Shutting down Jetty' is shown randomly
Title: Message Title Andreas Sieferlinger edited a comment on JENKINS-56896 Re: Shutdown message 'INFOS: JVM is terminating. Shutting down Jetty' is shown randomly Seems to be there for quite a while already: [https://github.com/jenkinsci/docker/issues/321] Overall the shutdown within the docker container seems not to be clean.According to [https://github.com/jenkinsci/jenkins/blob/0c2d194f0d933fdba8f5a9a1fda8adc8826981c0/core/src/main/java/jenkins/model/Jenkins.java#L3313] there should be a message like "Stopping Jenkins" which does not appear at all (logger is configured to show INFO) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198567.1554450203000.9600.1566815880396%40Atlassian.JIRA.
[JIRA] (JENKINS-56896) Shutdown message 'INFOS: JVM is terminating. Shutting down Jetty' is shown randomly
Title: Message Title Andreas Sieferlinger commented on JENKINS-56896 Re: Shutdown message 'INFOS: JVM is terminating. Shutting down Jetty' is shown randomly Overall the shutdown within the docker container seems not to be clean. According to https://github.com/jenkinsci/jenkins/blob/0c2d194f0d933fdba8f5a9a1fda8adc8826981c0/core/src/main/java/jenkins/model/Jenkins.java#L3313 there should be a message like "Stopping Jenkins" which does not appear at all (logger is configured to show INFO) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198567.1554450203000.9595.1566815160273%40Atlassian.JIRA.
[JIRA] (JENKINS-56896) Shutdown message 'INFOS: JVM is terminating. Shutting down Jetty' is shown randomly
Title: Message Title Andreas Sieferlinger commented on JENKINS-56896 Re: Shutdown message 'INFOS: JVM is terminating. Shutting down Jetty' is shown randomly seeing this problem also from time to time Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198567.1554450203000.7963.1566481560098%40Atlassian.JIRA.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Andreas Sieferlinger commented on JENKINS-57351 Re: Support for making Jenkins a "GitHub App" Hope that PR will go through soon. Maybe Liam Newman could merge it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199127.1557217283000.951.1564066980342%40Atlassian.JIRA.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Andreas Sieferlinger commented on JENKINS-57351 Re: Support for making Jenkins a "GitHub App" The exact steps are described at https://developer.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app In terms of things that are needed for Jenkins: A new credential type (storing the private PEM key, App ID, ...) Authenticating as App and fetching Installation Tokens Checking the validity of the installation token and renew if required (they are only short lived) Using the installation token to Authorize (which is just setting the correct HTTP header for all calls to GitHub) (see https://developer.github.com/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation ) I'm not sure how exactly the authentication currently works in the context of this plugin. The change to use GitHub App tokens for other things i've worked on often wasn't too difficult. I could help with writing docs and testing of this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199127.1557217283000.23110.1557467040159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57351) Support authentication as GitHub App
Title: Message Title Andreas Sieferlinger created an issue Jenkins / JENKINS-57351 Support authentication as GitHub App Issue Type: New Feature Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-05-07 08:21 Priority: Minor Reporter: Andreas Sieferlinger To my understanding currently the github-branch-source plugins always requires GitHub user credentials / tokens to authenticate. I'd suggest to add authenticating Jenkins to GitHub as a GitHub App too. Why is this better than the current way: GitHub Apps can be granted very fine grained permissions GitHub Apps can be added either to a whole org, or just to selected repos The app uses a key pair to then get temporary credentials, so leaked creds to user are only valid for a short period of time Higher API limits! (probably the most important one for bigger orgs) This is specifically NOT about authenticating users against GitHub, but for Authenticating Jenkins itself against GitHub References: https://developer.github.com/apps/differences-between-apps/
[JIRA] (JENKINS-42643) Conditional application of triggers in Declarative
Title: Message Title Andreas Sieferlinger commented on JENKINS-42643 Re: Conditional application of triggers in Declarative Has there been any progress on this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-29198) Console logs get truncated without reason
Title: Message Title Andreas Sieferlinger edited a comment on JENKINS-29198 Re: Console logs get truncated without reason We are seeing this issue aswell. Its seems like this happens mostly with pipelines that have multiple parallel steps.Running on 2.150.3 We are using also the Timestamper plugin, just curious if anybody else facing the issue is using it aswell and if it might be related. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-29198) Console logs get truncated without reason
Title: Message Title Andreas Sieferlinger commented on JENKINS-29198 Re: Console logs get truncated without reason We are seeing this issue aswell. Its seems like this happens mostly with pipelines that have multiple parallel steps. Running on 2.150.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56011) UI fails to set ECS Task Creation Timeout
Title: Message Title Andreas Sieferlinger commented on JENKINS-56011 Re: UI fails to set ECS Task Creation Timeout this seems to be fixed in the current state of the github repo (altough not released) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56101) ECS plugin - can't overwrite inheritFrom
Title: Message Title Andreas Sieferlinger commented on JENKINS-56101 Re: ECS plugin - can't overwrite inheritFrom see https://github.com/jenkinsci/amazon-ecs-plugin/pull/82 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56231) Suppress automatic SCM triggering is deprecated
Title: Message Title Andreas Sieferlinger commented on JENKINS-56231 Re: Suppress automatic SCM triggering is deprecated We also experience this issue, and neither found a way to work around this? Anybody has a suitable workaround or some more information on why this was removed at all? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Andreas Sieferlinger commented on JENKINS-35988 Re: Equivalent to polling commit exclusions for branch indexing any update on this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-43842) Conditional build trigger on branch indexing
Title: Message Title Andreas Sieferlinger commented on JENKINS-43842 Re: Conditional build trigger on branch indexing has this ever been implemented? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Andreas Sieferlinger commented on JENKINS-35988 Re: Equivalent to polling commit exclusions for branch indexing any update on this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55761) Webhook not created for API created jobs
Title: Message Title Andreas Sieferlinger created an issue Jenkins / JENKINS-55761 Webhook not created for API created jobs Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-01-24 14:05 Environment: Jenkins 2.150.2 (Official Docker image) github-branch-source-plugin 2.4.2 Labels: plugin github-branch-source-plugin Priority: Minor Reporter: Andreas Sieferlinger Hey, adding a new MultiBranch Pipeline via the UI works fine, and also create a webhook in GitHub. Altough if the Job is created by API (with exact same job config.xml) the Webhook is not being created in Github. Even after a manual trigger of a build, the Hook is not beeing triggered. Nothing related can be found in the logs. Is there any way to force the trigger creation (eg via groovy script) in an automatic way, or this simply a bug that needs to be fixed?
[JIRA] (JENKINS-55078) No longer able to start ECS slaves
Title: Message Title Andreas Sieferlinger commented on JENKINS-55078 Re: No longer able to start ECS slaves Hey, I also have the issue and almost have it traced down with a working workaround but not yet a Fix. Hope i can provide a PR soon. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
Title: Message Title Andreas Sieferlinger assigned an issue to Jesse Glick Jenkins / JENKINS-48300 Pipeline shell step aborts prematurely with ERROR: script returned exit code -1 Change By: Andreas Sieferlinger Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
Title: Message Title Andreas Sieferlinger assigned an issue to Unassigned Jenkins / JENKINS-48300 Pipeline shell step aborts prematurely with ERROR: script returned exit code -1 Change By: Andreas Sieferlinger Assignee: Andreas Sieferlinger Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
Title: Message Title Andreas Sieferlinger assigned an issue to Andreas Sieferlinger Jenkins / JENKINS-48300 Pipeline shell step aborts prematurely with ERROR: script returned exit code -1 Change By: Andreas Sieferlinger Assignee: Jesse Glick Andreas Sieferlinger Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Andreas Sieferlinger commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 The issue still seems to be there in version 2.4 which was released on May 16th. 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.
