[JIRA] (JENKINS-38155) Expand shelf ${VAR} failed if VAR is 'change'
Title: Message Title
Bing Shiao updated an issue
Jenkins / JENKINS-38155
Expand shelf ${VAR} failed if VAR is 'change'
Change By:
Bing Shiao
Using {{ ${change} }} for Perforce Unshelve build step failed with the following error: {quote} FATAL: For input string: "change"java.lang.NumberFormatException: For input string: "change" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:580) at java.lang.Integer.parseInt(Integer.java:615) at org.jenkinsci.plugins.p4.unshelve.UnshelveBuilder.unshelve(UnshelveBuilder.java:91) at org.jenkinsci.plugins.p4.unshelve.UnshelveBuilder.perform(UnshelveBuilder.java:65) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) {quote} Using other variable name works fine; for example, {{ ${changelist} }} .
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38155) Expand shelf ${VAR} failed if VAR is 'change'
Title: Message Title
Bing Shiao created an issue
Jenkins / JENKINS-38155
Expand shelf ${VAR} failed if VAR is 'change'
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2016/Sep/13 5:57 AM
Priority:
Minor
Reporter:
Bing Shiao
Using $ {change} for Perforce Unshelve build step failed with the following error: FATAL: For input string: "change" java.lang.NumberFormatException: For input string: "change" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:580) at java.lang.Integer.parseInt(Integer.java:615) at org.jenkinsci.plugins.p4.unshelve.UnshelveBuilder.unshelve(UnshelveBuilder.java:91) at org.jenkinsci.plugins.p4.unshelve.UnshelveBuilder.perform(UnshelveBuilder.java:65) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Using other variable name works fine; for example, $ {changelist} .
[JIRA] (JENKINS-35367) EMail-Ext Extended Pipeline Support - Templates
Title: Message Title Ashudeep Budhiraja commented on JENKINS-35367 Re: EMail-Ext Extended Pipeline Support - Templates Hi Team, David, Though email-ext involves lot and may need time, is there any basic level of template support existing currently? Thanks. 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] (JENKINS-34019) ANSIColor plugin leaks format onto next line's timestamp
Title: Message Title Steven G Brown commented on JENKINS-34019 Re: ANSIColor plugin leaks format onto next line's timestamp Seems to work with IE and Edge. 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] (JENKINS-38152) Jenkinsfile schema Java API as WorkflowRun action
Title: Message Title Michael Neale commented on JENKINS-38152 Re: Jenkinsfile schema Java API as WorkflowRun action Vivek Pandey ok thanks, makes sense. 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] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title Michael Neale commented on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API Right, so there really is no way to launch a build (request) and get a number back immediately. Vivek Pandey so is there a way to take a queue item and "eventually" resolve it to a run number? (as per the question) 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] (JENKINS-38152) Jenkinsfile schema Java API as WorkflowRun action
Title: Message Title Vivek Pandey commented on JENKINS-38152 Re: Jenkinsfile schema Java API as WorkflowRun action How does editor get the JSON model? My understanding talking to James Dumay is that editor will get hold of the JSON using this API. 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] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Denys Digtiar commented on JENKINS-37289 Re: authentication issue instant is too old or in the future Coltrey Mather I can't answer the question about the release. I just added a link to make sure that maintainer is aware of the relation. The issue was in the order of the calls. Saml2Client initialization is costly, so it is triggered once lazily in certain methods. client.printClientMetadata() is one of those methods. Since it was called before setMaximumAuthenticationLifetime(), the new value of the Maximum Authentication Lifetime was disregarded in future calls to the client. The fix changes the order of the method calls to allow for the proper initialization of the client. 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] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Torsten Kleiber Attachment: build_history_with_more_builds_as_log_rotation.png 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] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Torsten Kleiber Attachment: log_rotation.png 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] (JENKINS-38154) cpu load since 2.22
Title: Message Title Ronny Borchert created an issue Jenkins / JENKINS-38154 cpu load since 2.22 Issue Type: Bug Assignee: Unassigned Attachments: jenkins_log.txt Components: core Created: 2016/Sep/13 5:02 AM Environment: Windows Server 2008 R2 Priority: Critical Reporter: Ronny Borchert Since today ( yesterday was update), I see that java.exe is running with 100% cpu load. Maybe is it related to Jenkins version 2.22. I was currently updating the JENKINSHOME with a trailing backslash in every job. On save comes probably this: Add Comment
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber commented on JENKINS-37515 Re: pipeline input blocks the executor This is a little bit confusing: the build history shows all the jobs running until you proceed or abort any job instande. Additional old "running" jobs are not deleted by log rotation. So how to batch delete old job instances or timeout these? 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] (JENKINS-30430) Test Result table columns misaligned
Title: Message Title Tu An Huynh Van commented on JENKINS-30430 Re: Test Result table columns misaligned Is there a way to get the view of 'Test Results' table with borders to separate columns of results on Win 7 Chrome ? 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] (JENKINS-38130) JENKINS_HOME is set different for manual build
Title: Message Title Ronny Borchert updated an issue Jenkins / JENKINS-38130 JENKINS_HOME is set different for manual build Change By: Ronny Borchert I have installed Jenkins 2.20 and found today when I build a job manual that JENKINS_HOME is different as when it triggered by tfs plugin version 3.2.0.On manual run is it:H:\JenkinsOn automatical run is it:H:\Jenkins\In case it is a TFS plugin bug and is already fixed, I wanna only now what is the right one. edit: Maybe I am wrong but maybe is it since Jenkins version 2.22 for all builds, and has nothing to do with manual triggering. 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] (JENKINS-38152) Jenkinsfile schema Java API as WorkflowRun action
Title: Message Title Michael Neale commented on JENKINS-38152 Re: Jenkinsfile schema Java API as WorkflowRun action I am not sure how this relates to the editor - wont it operate on the JSON model and be passing that around? What am I missing? 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] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Michael Neale commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Jesse Glick yes the oddness you see is the oddness this ticket aims to address - in terms of running execution. The other stuff, about breaking things down via step vs a more direct log view (with collapsible sections) is a broader topic (I'll find somewhere else we can talk about this). however, being able to see a full log for all stages, branches, or a single branch/stage could be nice as well (with the ability to smoothly go in and out of step view). 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] (JENKINS-27394) Render stages in logs as collapsible sections
Title: Message Title Michael Neale edited a comment on JENKINS-27394 Re: Render stages in logs as collapsible sections There have been other console annotator plugins that have done something similar (but generically based on regex) right? 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] (JENKINS-27394) Render stages in logs as collapsible sections
Title: Message Title Michael Neale commented on JENKINS-27394 Re: Render stages in logs as collapsible sections There have been console annotator plugins that have done something similar (but generically based on regex) right? 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] (JENKINS-12769) Cannot specify location of gradle wrapper
Title: Message Title SCM/JIRA link daemon commented on JENKINS-12769 Re: Cannot specify location of gradle wrapper Code changed in jenkins User: Justin Ryan Path: src/main/java/hudson/plugins/gradle/Gradle.java src/main/resources/hudson/plugins/gradle/Gradle/config.jelly src/main/resources/hudson/plugins/gradle/Gradle/help-wrapperScript.html http://jenkins-ci.org/commit/gradle-plugin/ffddd0b33e7c820b16d97b5e60a330fe81917556 Log: JENKINS-12769 Provide location of gradlew script, which required moving code into radioBlocks which dont have inline, so I had to move to a POJO to store them. Uses macro replacement on wrapper location. 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] (JENKINS-27394) Render stages in logs as collapsible sections
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-27394 Render stages in logs as collapsible sections Change By: Jesse Glick Priority: Minor Major 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] (JENKINS-27394) Render stages in logs as collapsible sections
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-27394 Render stages in logs as collapsible sections Change By: Jesse Glick Component/s: pipeline-stage-step-plugin 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] (JENKINS-36080) docker 1.12 breaks plugin because of HostConfig
Title: Message Title Andrey Moor commented on JENKINS-36080 Re: docker 1.12 breaks plugin because of HostConfig Is there any progress on this? 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] (JENKINS-27394) Render stages in logs as collapsible sections
Title: Message Title Jesse Glick started work on JENKINS-27394 Change By: Jesse Glick Status: Open In Progress 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] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather commented on JENKINS-37289 Re: authentication issue instant is too old or in the future The link looks like a fix for how logging works - does this mean that logging preempts the authentication and shows an error instead of actually acknowledging authentication? Both sides of that commit call client.setMaximumAuthenticationLifetime(this.maximumAuthenticationLifetime);, which seems to be the good stuff... Is there a release that includes this fix? Last official was 7/29, so wouldn't include that commit. Is there a release schedule for the plugin? 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] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Denys Digtiar commented on JENKINS-37289 Re: authentication issue instant is too old or in the future Appears to be fixed on master. See the link. 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] (JENKINS-33526) Support generation of the SAML metadata that can be consumed by IdPs
Title: Message Title Denys Digtiar commented on JENKINS-33526 Re: Support generation of the SAML metadata that can be consumed by IdPs Implemented in saml-0.6. The URL is http://JENKINS_HOST/securityRealm/metadata 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] (JENKINS-29086) User IDs are case sensitive in saml-plugin
Title: Message Title Denys Digtiar commented on JENKINS-29086 Re: User IDs are case sensitive in saml-plugin Looks like this has been released in saml-0.5 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] (JENKINS-27394) Render stages in logs as collapsible sections
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-27394 Render stages in logs as collapsible sections Change By: Jesse Glick Summary: Use console annotation for stage name Render stages in console log logs as collapsible sections 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] (JENKINS-28222) Thread labels in console output don't persist after a node block
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28222 Thread labels in console output don't persist after a node block Change By: Jesse Glick Priority: Minor Major 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] (JENKINS-28222) Thread labels in console output don't persist after a node block
Title: Message Title Jesse Glick updated JENKINS-28222 Jenkins / JENKINS-28222 Thread labels in console output don't persist after a node block Change By: Jesse Glick Status: In Progress Review 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] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Katherine Morgan commented on JENKINS-37515 Re: pipeline input blocks the executor Hi @tkleiber, Your screenshot shows the job in the build history for your 'PipelineTest' job, not the 'Build Executor Status' list which is on the main jenkins page, see my screenshot. When I made the change suggested by Jesse, the jobs do drop out of the executor list. 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] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Katherine Morgan updated an issue Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Katherine Morgan Attachment: jenkins-build-executor.PNG 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] (JENKINS-38153) Pre and post steps/stage handling
Title: Message Title Andrew Bayer commented on JENKINS-38153 Re: Pre and post steps/stage handling Work-in-progress on PR up - https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/13 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] (JENKINS-38153) Pre and post steps/stage handling
Title: Message Title Andrew Bayer started work on JENKINS-38153 Change By: Andrew Bayer Status: Open In Progress 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] (JENKINS-38153) Pre and post steps/stage handling
Title: Message Title Andrew Bayer updated JENKINS-38153 Jenkins / JENKINS-38153 Pre and post steps/stage handling Change By: Andrew Bayer Status: In Progress Review 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] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Christian Höltje commented on JENKINS-38111 Re: github organization should allow 'clean before checkout' behavior In addition, I would prefer if those Additional Behaviors (scm.extensions) were available to the Jenkinsfile since some are not useful for every repository in a GitHub Org. 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] (JENKINS-35899) Form to capture user input when pipeline is waiting for user input
Title: Message Title James Dumay commented on JENKINS-35899 Re: Form to capture user input when pipeline is waiting for user input Raphaël PINSON there's no way to visualise what you have there today but I'd be really happy to chat with you about your use case. Hit me on email jdu...@cloudbees.com 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] (JENKINS-31595) Improve metadata logs for parallel step
Title: Message Title Jesse Glick resolved as Duplicate Fix of JENKINS-28222 addresses this well enough too. Jenkins / JENKINS-31595 Improve metadata logs for parallel step Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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] (JENKINS-37817) Pipeline should be able to use hudson.plugins.git.GitSCM getBranches
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-37817 Pipeline should be able to use hudson.plugins.git.GitSCM getBranches Change By: Christian Höltje Environment: Jenkins 2.7. 2 3 Git-Plugin: 2 3 . 0.0GitHub Organization Folder Plugin: 1. 5 GitHub plugin: 1 . 3 21.1 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] (JENKINS-28222) Thread labels in console output don't persist after a node block
Title: Message Title Jesse Glick started work on JENKINS-28222 Change By: Jesse Glick Status: Open In Progress 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] (JENKINS-37817) Pipeline should be able to use hudson.plugins.git.GitSCM getBranches
Title: Message Title Christian Höltje commented on JENKINS-37817 Re: Pipeline should be able to use hudson.plugins.git.GitSCM getBranches What does that mean I put into a Jenkinsfile? I tried scm.extensions.add([$class: 'CloneOption', noTags: false, reference: '', shallow: true]) but that didn't do anything. scm itself seems to be a GitSCM object, not a GitSCMSource. And the pipeline syntax snippets generator doesn't have anything for checkout with scm, only manually specifying everything by hand, which defeats the purpose of using the Github Org Folders plugin (which provides scm for you). 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] (JENKINS-38136) Support POST requests to the /blue/rest/classes/?q= endpoint
Title: Message Title Vivek Pandey updated JENKINS-38136 Jenkins / JENKINS-38136 Support POST requests to the /blue/rest/classes/?q= endpoint Change By: Vivek Pandey Status: In Progress Review 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] (JENKINS-37817) Pipeline should be able to use hudson.plugins.git.GitSCM getBranches
Title: Message Title
Christian Höltje edited a comment on JENKINS-37817
Re: Pipeline should be able to use hudson.plugins.git.GitSCM getBranches
Okay, you can't access {{scm.extensions}}, {{scm.doGenerateSubmoduleConfigurations} } , nor {{scm.userRemoteConfigs}}. The same {{org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException}} error each time.What's the right way to modify the SCM options, then?
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] (JENKINS-38153) Pre and post steps/stage handling
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-38153 Pre and post steps/stage handling Issue Type: Task Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Sep/13 12:20 AM Priority: Major Reporter: Vivek Pandey As discussed with Andrew Bayer, Pre steps to be exposed as synthetic stages * Pre stage to have action to indicate they are pre stages postBuild stage to have action to indicate its postBuild stage Any Kyoto generated synthetic stage to have action to indicate it was generated by Kyoto This will enable BO to provide appropriate visualization of these stages. Add Comment
[JIRA] (JENKINS-37769) Too long stop docker container(default docker stop timeout=10s)
Title: Message Title Jesse Glick updated JENKINS-37769 Jenkins / JENKINS-37769 Too long stop docker container(default docker stop timeout=10s) Change By: Jesse Glick Status: In Progress Review 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] (JENKINS-37769) Too long stop docker container(default docker stop timeout=10s)
Title: Message Title Jesse Glick started work on JENKINS-37769 Change By: Jesse Glick Status: Open In Progress 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] (JENKINS-38151) Add support for AWS EB Deployment plugin
Title: Message Title Adam Trousdale updated an issue Jenkins / JENKINS-38151 Add support for AWS EB Deployment plugin Change By: Adam Trousdale Add support for the AWS EB Deployment pluginhttps://wiki.jenkins-ci.org/display/JENKINS/AWSEB+Deployment+Plugin PR: https://github.com/jenkinsci/job-dsl-plugin/pull/912 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] (JENKINS-38152) Jenkinsfile schema Java API as WorkflowRun action
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-38152 Jenkinsfile schema Java API as WorkflowRun action Issue Type: Task Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Sep/13 12:16 AM Priority: Minor Reporter: Vivek Pandey Kyoto has REST API to expose Jenkinsfile schema in JSON format. Pipeline editor in BO needs to call this API and this would needed to be exposed using pipeline API actions so that pipeline editor UI can call it by looking at 'actions' element in pipeline API response. As discussed with Andrew Bayer the schema parsing Java API can be exposed as action on WorkflowAction. Add Comment
[JIRA] (JENKINS-38151) Add support for AWS EB Deployment plugin
Title: Message Title Adam Trousdale created an issue Jenkins / JENKINS-38151 Add support for AWS EB Deployment plugin Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/Sep/13 12:15 AM Priority: Minor Reporter: Adam Trousdale Add support for the AWS EB Deployment plugin https://wiki.jenkins-ci.org/display/JENKINS/AWSEB+Deployment+Plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38150) Handle Kyoto preparatory steps and postBuild stage
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-38150 Handle Kyoto preparatory steps and postBuild stage Issue Type: Task Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Sep/13 12:00 AM Labels: API Priority: Major Reporter: Vivek Pandey In Kyoto there is preparatory steps that get executed and postBuild stapes get executed as finally block. Preparatory steps Prefix all steps from it over to next stage postBuild stage Append all postBuild steps to the last executed stage's steps
[JIRA] (JENKINS-37769) Too long stop docker container(default docker stop timeout=10s)
Title: Message Title Jesse Glick commented on JENKINS-37769 Re: Too long stop docker container(default docker stop timeout=10s) Stranger still: docker run --rm --name test ubuntu sleep infinity Now docker exec test ps fauxwww confirms that sleep is PID 1, yet docker exec test kill -9 1 does not do anything. docker stop test will pause for ten seconds. I suspect that somehow signal delivery is just getting blocked to PID 1. On the other hand, with docker run --rm --name test --stop-signal=KILL ubuntu sleep infinity you will see that docker stop test works promptly. Perhaps in this case the stop command is just being clever and knows that it makes no sense to wait after sending SIGKILL, so behaves like --time=0? Really not sure what is going on. Passing --time 0 does correct the symptom, without addressing the underlying problem. But it is less than clear that a clean TERM is being delivered to any spawned processes even in the current state—it seems that TERM is delivered to the entrypoint ((cat) but does nothing. I am (dimly) aware of zombie reaping issues but that does not seem to be relevant in this case. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34284) Web hook http://JENKINS_URL/project/PROJECT_NAME fails
Title: Message Title John McGehee closed an issue as Fixed The solution was remarkably simple. I mistakenly used the GitLab project name. It is the Jenkins project name, including any folders, that should be specified. I added this to the GitLab Plugin documentation and issued pull request #414. Jenkins / JENKINS-34284 Web hook http://JENKINS_URL/project/PROJECT_NAME fails Change By: John McGehee Status: Open Closed Resolution: Fixed 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
[JIRA] (JENKINS-37769) Too long stop docker container(default docker stop timeout=10s)
Title: Message Title Jesse Glick commented on JENKINS-37769 Re: Too long stop docker container(default docker stop timeout=10s) Not following what is going on. If you run bash -c 'trap "echo term" EXIT; sleep 120' and then kill this bash process from another terminal window, you see term Terminated immediately. But if you run docker run --rm --name test ubuntu bash -c 'trap "echo term" EXIT; sleep 120' and from another window docker stop test you will see term and then ten seconds will elapse before the container exits. Somehow the TERM signal is getting sent, but not properly handled. (sleep is still running during this time.) Add Comment This
[JIRA] (JENKINS-37769) Too long stop docker container(default docker stop timeout=10s)
Title: Message Title Jesse Glick commented on JENKINS-37769 Re: Too long stop docker container(default docker stop timeout=10s) At first I thought it was this problem with systemd, but --stop-signal=RTMIN+3 does not work. Anyway the overridden --entrypoint means that systemd is not in play. 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] (JENKINS-38136) Support POST requests to the /blue/rest/classes/?q= endpoint
Title: Message Title
Vivek Pandey updated an issue
Jenkins / JENKINS-38136
Support POST requests to the /blue/rest/classes/?q= endpoint
Change By:
Vivek Pandey
TL;DR: support method=POST for the {{/blue/rest/classes}} API so very long values for "classList" can be sent.The new capabilities code on the frontend (JENKINS-37519) may potentially call the {{/blue/rest/classes?q=classList}} API with a very long "classList" parameter (in some cases over 1700 chars long). Some browsers have problems with URL's over 2000 characters, although it's unclear whether that applies to fetch / XHR calls or just URLs pasted into the address bar UI. To be safe it would be good to support the POST method so we can send large "classList" values in the body and avoid any potential problems. Also fix these issues:* For pipeline-related things, I think it would be good to refactor the string values into static string constants in a single class (or possibly an enum( to ensure consistent values are used throughout and make it easier to see what capabilities are available.* Fix typo in BranchImpl.java ("io.jenkins.blueocean.rest.impl.pipeline.PullReuqest")
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38136) Support POST requests to the /blue/rest/classes/?q= endpoint
Title: Message Title Vivek Pandey started work on JENKINS-38136 Change By: Vivek Pandey Status: Open In Progress 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] (JENKINS-38143) Refactor of Capabilities on backend
Title: Message Title Vivek Pandey commented on JENKINS-38143 Re: Refactor of Capabilities on backend Cliff Meyers As discussed I am implementing #1 and #2 in JENKINS-38136. 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] (JENKINS-38136) Support POST requests to the /blue/rest/classes/?q= endpoint
Title: Message Title Vivek Pandey commented on JENKINS-38136 Re: Support POST requests to the /blue/rest/classes/?q= endpoint sounds good. 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] (JENKINS-38136) Support POST requests to the /blue/rest/classes/?q= endpoint
Title: Message Title Cliff Meyers commented on JENKINS-38136 Re: Support POST requests to the /blue/rest/classes/?q= endpoint That change should not break any code currently in master. I will update my in -progress PR as soon as the changes are made on your end and merge that branch into mine. 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] (JENKINS-36420) Allow to configure the client idle timeout.
Title: Message Title Arnaud Héritier resolved as Fixed yes it is good now Daniel Beck It is fixed in 2.22 Jenkins / JENKINS-36420 Allow to configure the client idle timeout. Change By: Arnaud Héritier Status: In Progress Resolved Resolution: Fixed 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
[JIRA] (JENKINS-36420) Allow to configure the client idle timeout.
Title: Message Title Daniel Beck commented on JENKINS-36420 Re: Allow to configure the client idle timeout. Arnaud Héritier Is this fixed? 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] (JENKINS-38136) Support POST requests to the /blue/rest/classes/?q= endpoint
Title: Message Title
Vivek Pandey commented on JENKINS-38136
Re: Support POST requests to the /blue/rest/classes/?q= endpoint
Cliff Meyers I was talking about the later, that is to replace
GET /blue/rest/classes/?q=classList
by
POST /blue/rest/classes/ with body {"q": ["",""]}
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] (JENKINS-38143) Refactor of Capabilities on backend
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-38143
Refactor of Capabilities on backend
Change By:
Cliff Meyers
Some suggestions on tweaks to capabilities:# For pipeline-related things, I think it would be good to refactor the string values into static string constants in a single class (or possibly an enum( to ensure consistent values are used throughout and make it easier to see what capabilities are available.# Fix typo in BranchImpl.java ("io.jenkins.blueocean.rest.impl.pipeline.PullReuqest") Items deferred for now but kept for later in case they're useful: # -I have some suggestions on how we might refine some of the metadata too. Right now I would say that most of our Capabilities are simply proxies for the underlying class name. I think instead that similar classes should share a capability when it makes sense. This simplifies the UI code so we are more often testing for a single capability rather than multiple capabilities that ultimately refer to the same kind of functionality.-## -I think that BluePipeline.java and BlueMultiBranchPipeline.java should share a capability to indicate they are both pipelines. Perhaps just add {{"io.jenkins.blueocean.rest.model.BluePipeline"}} to multi-branch, or come up with a new capability altogether.-## -I think that BranchImpl.java and BlueMultiBranchPipeline.java should share a capability to indicate they are both multibranch "components". It would be nice not to have to test for BlueBranch and BlueMultiBranchPipeline, rather something like BlueBranchAware, etc-## -Should PipelineRunImpl.java have a "WorkflowRun" capability name or should it be something more generic like "PipelineRun" ?-## -Is the "MultiBranchProject" capability on MultiBranchPipelineImpl necessary? It seems that there could be confusion whether to check for that capability or for BlueMultiBranchPipeline-There may be some other capabilities worthy of discussion too; scheduling a meeting to discuss and refine might be a good idea.
Add Comment
[JIRA] (JENKINS-38143) Refactor of Capabilities on backend
Title: Message Title Cliff Meyers commented on JENKINS-38143 Re: Refactor of Capabilities on backend Vivek Pandey I left the content in there in case we want to reference it later but added strikethroughs. 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] (JENKINS-38143) Refactor of Capabilities on backend
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-38143
Refactor of Capabilities on backend
Change By:
Cliff Meyers
Some suggestions on tweaks to capabilities:# For pipeline-related things, I think it would be good to refactor the string values into static string constants in a single class (or possibly an enum( to ensure consistent values are used throughout and make it easier to see what capabilities are available.# Fix typo in BranchImpl.java ("io.jenkins.blueocean.rest.impl.pipeline.PullReuqest")# - I have some suggestions on how we might refine some of the metadata too. Right now I would say that most of our Capabilities are simply proxies for the underlying class name. I think instead that similar classes should share a capability when it makes sense. This simplifies the UI code so we are more often testing for a single capability rather than multiple capabilities that ultimately refer to the same kind of functionality. - ## - I think that BluePipeline.java and BlueMultiBranchPipeline.java should share a capability to indicate they are both pipelines. Perhaps just add {{"io.jenkins.blueocean.rest.model.BluePipeline"}} to multi-branch, or come up with a new capability altogether. - ## - I think that BranchImpl.java and BlueMultiBranchPipeline.java should share a capability to indicate they are both multibranch "components". It would be nice not to have to test for BlueBranch and BlueMultiBranchPipeline, rather something like BlueBranchAware, etc - ## - Should PipelineRunImpl.java have a "WorkflowRun" capability name or should it be something more generic like "PipelineRun" ? - ## - Is the "MultiBranchProject" capability on MultiBranchPipelineImpl necessary? It seems that there could be confusion whether to check for that capability or for BlueMultiBranchPipeline - There may be some other capabilities worthy of discussion too; scheduling a meeting to discuss and refine might be a good idea.
Add Comment
[JIRA] (JENKINS-38136) Support POST requests to the /blue/rest/classes/?q= endpoint
Title: Message Title Cliff Meyers commented on JENKINS-38136 Re: Support POST requests to the /blue/rest/classes/?q= endpoint Vivek Pandey did a search on the current UI code and right now there is only one spot using the /classes API and it's using the /blue/rest/classes/:className/ form with method=GET. The only place using the /blue/rest/classes/?q=classList form is in new code that hasn't been merged yet to master, which I was going to update to method=POST first anyways. So let me know what how you'd like to proceed and I can make that compensating change in the same branch if needed. 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] (JENKINS-34284) Web hook http://JENKINS_URL/project/PROJECT_NAME fails
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-34284
Web hook http://JENKINS_URL/project/PROJECT_NAME fails
Change By:
John McGehee
I am trying to set up the Jenkins GitLab plugin. The [GitLab plugin installation instructions|https://github.com/jenkinsci/gitlab-plugin] say to use the web hook {{http://JENKINS_URL/project/PROJECT_NAME}}. Upon testing this hook in GitLab, Jenkins responds with the giant stack trace shown below.I tried the more standard web hook {{http://JENKINS-SERVER/git/notifyCommit?url=""> infra2 SERVER :GROUP/REPO.git}} in GitLab and it did work for ordinary pushes to the source repository. However, when this web hook gets used on merge requests, the Jenkins job is triggered but it fails, complaining:{code}Error fetching remote repo '${gitlabSourceRepoName}'{code}I suppose this is because {{http://JENKINS-SERVER/git/notifyCommit?url=""> infra2 SERVER :GROUP/REPO.git}} triggers Jenkins directly, circumventing the GitLab plugin, which would define variable {{gitlabSourceRepoName}}.[Toward the end of the installation instructions|https://github.com/jenkinsci/gitlab-plugin#help-needed], there are words that cast doubt on whether {{http://JENKINS_URL/project/PROJECT_NAME}} actually does work.-Here is the stack trace mentioned above:{code}Hook execution failed: Jenkins [Jenkins]var isRunAsTest=false; var rootURL=""; var resURL="/static/2ea7aded";crumb.init("", "");var Q=jQuery.noConflict()Skip to content log in createSearchBox("/search/");Jenkins Jenkins project Bug tracker Mailing Lists Twitter: @jenkinsci Oops!A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejavax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at
[JIRA] (JENKINS-36975) User should only see the administration link in the header if they are logged in
Title: Message Title Ivan Meredith updated JENKINS-36975 Jenkins / JENKINS-36975 User should only see the administration link in the header if they are logged in Change By: Ivan Meredith Status: In Review Resolved Resolution: Fixed 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] (JENKINS-38136) Support POST requests to the /blue/rest/classes/?q= endpoint
Title: Message Title Vivek Pandey commented on JENKINS-38136 Re: Support POST requests to the /blue/rest/classes/?q= endpoint Cliff Meyers In this case keeping GET call doesn't make sense. I would have it replaced with POST. Is it going to break UI code? 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] (JENKINS-37300) Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
Title: Message Title Jesse Luehrs commented on JENKINS-37300 Re: Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder Is there a timeline on the 1.23 release? I'd like to be able to upgrade for some of the other changes, but this is still blocking. 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] (JENKINS-37524) Add sort mode for branch parameter: most recently updated
Title: Message Title George Sakhnovsky commented on JENKINS-37524 Re: Add sort mode for branch parameter: most recently updated if git_version >= 2.7.0: git branch --sort=-committerdate else: git for-each-ref --sort=-committerdate refs/heads/ I got the above from the top answer to this StackOverflow question: http://stackoverflow.com/questions/5188320/how-can-i-get-a-list-of-git-branches-ordered-by-most-recent-commit 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] (JENKINS-38148) NullPointerException in AccuRev Launcher
Title: Message Title Mark Berchem updated an issue Jenkins / JENKINS-38148 NullPointerException in AccuRev Launcher Change By: Mark Berchem Priority: Minor Major 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] (JENKINS-37524) Add sort mode for branch parameter: most recently updated
Title: Message Title Boguslaw Klimas commented on JENKINS-37524 Re: Add sort mode for branch parameter: most recently updated HI George Sakhnovsky Could you add some more information about this feature. Add some example or git command. Regards Boguslaw 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] (JENKINS-35899) Form to capture user input when pipeline is waiting for user input
Title: Message Title Raphaël PINSON edited a comment on JENKINS-35899 Re: Form to capture user input when pipeline is waiting for user input [~jamesdumay] Definitely, that could be very useful. Also, I see there's steps inside parallel branches in your graph (in the QA part). This would normally be achived using steps stages , but steps stages are not displayed in parallel branches, are strongly advised against in parallel branches apparently. Is there another way to achieve this? 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] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey started work on JENKINS-38079 Change By: Vivek Pandey Status: Open In Progress 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] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey stopped work on JENKINS-38079 Change By: Vivek Pandey Status: In Progress Open 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] (JENKINS-37769) Too long stop docker container(default docker stop timeout=10s)
Title: Message Title Jesse Glick commented on JENKINS-37769 Re: Too long stop docker container(default docker stop timeout=10s) Oleksii Trekhov I can reproduce the pause. I am still trying to determine why it is pausing. From what I can tell so far, the container is killed right away (presumably after the SIGTERM), so I am wondering why it is then waiting for the timeout to expire, supposedly to send a SIGKILL. Perhaps this is a bug in Docker. Needs more investigation. Gabor Almer can we skip passing cat as command when running a container? The problem is determining which images that would apply to. Bart Vanbrabant your problem seems to be unrelated, far more serious, and specific to the fedora image (perhaps). I think it has something to do with different procfs handling. Please file it separately. 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] (JENKINS-38149) TAP Extended Test Results throws NullPointerException
Title: Message Title Olof Kindgren created an issue Jenkins / JENKINS-38149 TAP Extended Test Results throws NullPointerException Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap-plugin Created: 2016/Sep/12 8:15 PM Priority: Minor Reporter: Olof Kindgren Tests work fine and TAP file is correctly parsed. When I press the TAP Extended Test Results however, I get a NullPointerException Stack trace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at
[JIRA] (JENKINS-38008) unable to launch UFT from jenkins ,when launching from jenkins able to see the process UFT.exe *32 in task manager but tool not showing on VM but when launching from ALM UFT is
Title: Message Title krishna b assigned an issue to Amit Bezalel Jenkins / JENKINS-38008 unable to launch UFT from jenkins ,when launching from jenkins able to see the process UFT.exe *32 in task manager but tool not showing on VM but when launching from ALM UFT is able to open Change By: krishna b Assignee: Michael Fazio Amit Bezalel 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] (JENKINS-35899) Form to capture user input when pipeline is waiting for user input
Title: Message Title Raphaël PINSON commented on JENKINS-35899 Re: Form to capture user input when pipeline is waiting for user input James Dumay Definitely, that could be very useful. Also, I see there's steps inside parallel branches in your graph (in the QA part). This would normally be achived using steps, but steps are not displayed in parallel branches, are strongly advised against in parallel branches apparently. Is there another way to achieve this? 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] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Boguslaw Klimas updated JENKINS-34876 Release 0.7.0 Jenkins / JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Change By: Boguslaw Klimas Status: In Review Resolved Resolution: Fixed 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
[JIRA] (JENKINS-37370) Retrieving Git references do not work with variable in "Repository URL"
Title: Message Title Boguslaw Klimas updated JENKINS-37370 Release 0.7.0 Jenkins / JENKINS-37370 Retrieving Git references do not work with variable in "Repository URL" Change By: Boguslaw Klimas Status: In Review Resolved Resolution: Fixed 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
[JIRA] (JENKINS-37555) Better support for internationalization
Title: Message Title Boguslaw Klimas updated JENKINS-37555 Release 0.7.0 Jenkins / JENKINS-37555 Better support for internationalization Change By: Boguslaw Klimas Status: In Review Resolved Resolution: Fixed 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] (JENKINS-37595) Add support for polish localization
Title: Message Title Boguslaw Klimas updated JENKINS-37595 Release 0.7.0 Jenkins / JENKINS-37595 Add support for polish localization Change By: Boguslaw Klimas Status: In Review Resolved Resolution: Fixed 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] (JENKINS-37738) Update dependency in plugin and cleanup in pom
Title: Message Title Boguslaw Klimas updated JENKINS-37738 Release 0.7.0 Jenkins / JENKINS-37738 Update dependency in plugin and cleanup in pom Change By: Boguslaw Klimas Status: In Review Resolved Resolution: Fixed 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] (JENKINS-37953) Add support to ProxySCM
Title: Message Title Boguslaw Klimas commented on JENKINS-37953 Re: Add support to ProxySCM Release 0.7.0 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] (JENKINS-37953) Add support to ProxySCM
Title: Message Title Boguslaw Klimas updated JENKINS-37953 Release 0.7.0 Jenkins / JENKINS-37953 Add support to ProxySCM Change By: Boguslaw Klimas Status: In Review Resolved Resolution: Fixed 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] (JENKINS-38084) Add support to mark jobs as disabled on import
Title: Message Title Owen Wood resolved as Done Jenkins / JENKINS-38084 Add support to mark jobs as disabled on import Change By: Owen Wood Status: In Progress Resolved Resolution: Done 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] (JENKINS-38129) pipelines stopped working after update to 2.22 must specify $class with an implementation
Title: Message Title Bram Verhaegh updated an issue Jenkins / JENKINS-38129 pipelines stopped working after update to 2.22 must specify $class with an implementation Change By: Bram Verhaegh Summary: pipelines stopped working after update to 2.22 must specify $class with an implementation 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] (JENKINS-38129) pipelines stopped working after update to 2.22
Title: Message Title Bram Verhaegh updated an issue Jenkins / JENKINS-38129 pipelines stopped working after update to 2.22 Change By: Bram Verhaegh Environment: ubuntu 14.04 LTS, Jenkins 2.22, latest gitlab , pipelinescripts are at latest version 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] (JENKINS-38129) pipelines stopped working after update to 2.22
Title: Message Title Bram Verhaegh updated an issue Jenkins / JENKINS-38129 pipelines stopped working after update to 2.22 Change By: Bram Verhaegh Environment: ubuntu 14.04 LTS, Jenkins 2.22, latest gitlab pipelinescripts are at latest version 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] (JENKINS-38129) pipelines stopped working after update to 2.22
Title: Message Title Justin Rainwater commented on JENKINS-38129 Re: pipelines stopped working after update to 2.22 I found this bug by searching online for the error message. I was able to resolve it by using the pipeline syntax snippet generator, to change all of my properties away from the old $class style. However I see from Jenkinsfile that the gitlab parameter is the only property you have using $class and I dont see gitlab as an available parameter in the snippet generator so maybe that won't help in your case. Either way I think a more accurate description of this issue would be gitlab specific rather than just "pipelines stopped working" 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] (JENKINS-38129) pipelines stopped working after update to 2.22
Title: Message Title Justin Rainwater edited a comment on JENKINS-38129 Re: pipelines stopped working after update to 2.22 I found this bug by searching online for the error message. I was able to resolve it by using the pipeline syntax snippet generator, to change all of my properties away from the old $class style. However I see from your Jenkinsfile that the gitlab parameter is the only property you have using $class and I dont see gitlab as an available parameter in the snippet generator so maybe that won't help in your case.Either way I think a more accurate description of this issue would be gitlab specific rather than just "pipelines stopped working" 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] (JENKINS-38148) NullPointerException in AccuRev Launcher
Title: Message Title Mark Berchem created an issue Jenkins / JENKINS-38148 NullPointerException in AccuRev Launcher Issue Type: Bug Assignee: Joseph Petersen Components: accurev-plugin Created: 2016/Sep/12 6:08 PM Environment: Jenkins 2.21 running standalone (not in container) Accurev plugin 0.7.0 fails (0.6.35 does not fail) Windows 8.1 java.vendor Oracle Corporation java version: 1.8.0_20 Labels: plugin Priority: Minor Reporter: Mark Berchem With Accurev 0.6.35 plugin: 10:34:55 [workspace] $ "C:\Program Files (x86)\AccuRev\bin\accurev.exe" setproperty -H usmlvv1prodv01:5050 -s HDX-INTGCODE_ELRF -r style10:34:55 FATAL: You are not authorized to perform this operation. 10:34:55 Setting "text" property "style" on "stream" is an admin function: 10:34:55 server_admin_trig: You are not in the Depot Admin or User Admin group. 10:34:55 10:34:55 FATAL: Failed authentication. (failed with exit code 1 ) and the build continues. With Accurev 0.7.0 plugin: [workspace] $ "C:\Program Files (x86)\AccuRev\bin\accurev.exe" setproperty -H usmlvv1prodv01:5050 -s HDX-INTGCODE_ELRF -r style #FF 10:33:36 FATAL: You are not authorized to perform this operation. 10:33:36 Setting "text" property "style" on "stream" is an admin function: 10:33:36 server_admin_trig: You are not in the Depot Admin or User Admin group. 10:33:36 10:33:36 FATAL: Failed authentication. (failed with exit code 1 ) 10:33:36 FATAL: null 10:33:36 java.lang.NullPointerException 10:33:36 at #FF
[JIRA] (JENKINS-38138) Git plugin over HTTP with TFS 2015 causes authorization error
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-38138
Git plugin over HTTP with TFS 2015 causes authorization error
Change By:
James Dumay
Bug in that our build last worked on 30th August - I've noticed two updates to the plugin since on the 2nd and 10th of September. When I upgrade the plugin for compatibility with Blue Ocean project I started to get this issue.The server in question works OK from local machine with same credentials as are saved in Jenkins Credential Manager.I've looked at the similar issues which may be around HTTPs certificates - in this instance we're using plain HTTP for this server. Using pipeline plugin.{quote}Started by user anonymous[Pipeline] nodeRunning on master in /var/jenkins_home/workspace/API tests[Pipeline] {[Pipeline] git > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://project/myprojectA.git # timeout=10Fetching upstream changes from http://project/myprojectA.git > git --version # timeout=10using GIT_ASKPASS to set credentials SVCACC service account > git fetch --tags --progress http://project/myprojectA.git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from http://project/myprojectA.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1051) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1082) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress http://project/myprojectA.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: fatal: Authentication failed for 'http://project/myprojectA.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1752) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1495) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at
[JIRA] (JENKINS-38138) Git plugin over HTTP with TFS 2015 causes authorization error
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-38138
Git plugin over HTTP with TFS 2015 causes authorization error
Change By:
James Dumay
Bug in that our build last worked on 30th August - I've noticed two updates to the plugin since on the 2nd and 10th of September. When I upgrade the plugin for compatibility with Blue Ocean project I started to get this issue.The server in question works OK from local machine with same credentials as are saved in Jenkins Credential Manager.I've looked at the similar issues which may be around HTTPs certificates - in this instance we're using plain HTTP for this server. Using pipeline plugin. {quote} Started by user anonymous[Pipeline] nodeRunning on master in /var/jenkins_home/workspace/API tests[Pipeline] {[Pipeline] git > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://project/myprojectA.git # timeout=10Fetching upstream changes from http://project/myprojectA.git > git --version # timeout=10using GIT_ASKPASS to set credentials SVCACC service account > git fetch --tags --progress http://project/myprojectA.git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from http://project/myprojectA.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1051) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1082) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress http://project/myprojectA.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: fatal: Authentication failed for 'http://project/myprojectA.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1752) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1495) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at
[JIRA] (JENKINS-38138) Git plugin over HTTP with TFS 2015 causes authorization error
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-38138
Git plugin over HTTP with TFS 2015 causes authorization error
Change By:
James Dumay
Bug in that our build last worked on 30th August - I've noticed two updates to the plugin since on the 2nd and 10th of September. When I upgrade the plugin for compatibility with Blue Ocean project I started to get this issue.The server in question works OK from local machine with same credentials as are saved in Jenkins Credential Manager.I've looked at the similar issues which may be around HTTPs certificates - in this instance we're using plain HTTP for this server. Using pipeline plugin. { { quote} Started by user anonymous[Pipeline] nodeRunning on master in /var/jenkins_home/workspace/API tests[Pipeline] {[Pipeline] git > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://project/myprojectA.git # timeout=10Fetching upstream changes from http://project/myprojectA.git > git --version # timeout=10using GIT_ASKPASS to set credentials SVCACC service account > git fetch --tags --progress http://project/myprojectA.git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from http://project/myprojectA.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1051) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1082) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress http://project/myprojectA.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: fatal: Authentication failed for 'http://project/myprojectA.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1752) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1495) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at
[JIRA] (JENKINS-38147) Allow per-job Parameters for Multi-Branch
Title: Message Title Matthew DeTullio assigned an issue to Jesse Glick Jenkins / JENKINS-38147 Allow per-job Parameters for Multi-Branch Change By: Matthew DeTullio Assignee: Matthew DeTullio Jesse Glick 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] (JENKINS-38147) Allow per-job Parameters for Multi-Branch
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-38147 Allow per-job Parameters for Multi-Branch Change By: Matthew DeTullio Component/s: workflow-multibranch-plugin Component/s: multi-branch-project-plugin 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] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Jesse Glick commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly BTW from parallel-test-executor PR 20 if you install B.O. you can see various odd behaviors. 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.
