[JIRA] (JENKINS-38494) User can see the input form on an input step (UI)
Title: Message Title Michael Neale commented on JENKINS-38494 Re: User can see the input form on an input step (UI) James Dumay Brody Maclean currently the user can enter the text for the proceed button (but not the cancel). It is really a "continue or not" function - however it is worded (not continuing does not mean failure necessarily) 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-40370) Run stage when branch name matches
Title: Message Title James Dumay commented on JENKINS-40370 Re: Run stage when branch name matches Andrew Bayer with your work around it comes back to the model that the editor can understand when is just as non-roundtripable as the contents of script. Throwing another idea out here: what if the conditions were a pluggable thing that you could even write implementations for in a library? branch and when could be declared and implemented that way..? 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-40380) AJAX callbacks generate 403s for expired sessions which can trigger an IPS
Title: Message Title Greg Harvey assigned an issue to Unassigned Jenkins / JENKINS-40380 AJAX callbacks generate 403s for expired sessions which can trigger an IPS Change By: Greg Harvey Component/s: dashboard-view-plugin Assignee: Evan Van Dyke 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-38494) User can see the input form on an input step (UI)
Title: Message Title James Dumay commented on JENKINS-38494 Re: User can see the input form on an input step (UI) Brody Maclean I don't think we should have an 'abort' button. The affirmative should be "Continue" instead of "Submit"? 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-40013) Unable to set and use global groovy functions
Title: Message Title aurelien leboulanger closed an issue as Fixed @NonCPS usage break the pipeline. Jenkins / JENKINS-40013 Unable to set and use global groovy functions Change By: aurelien leboulanger 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 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-38494) User can see the input form on an input step (UI)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38494 User can see the input form on an input step (UI) Change By: Michael Neale Attachment: Screen Shot 2016-12-13 at 4.51.12 pm.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-38494) User can see the input form on an input step (UI)
Title: Message Title
Michael Neale edited a comment on JENKINS-38494
Re: User can see the input form on an input step (UI)
I put some details on how to get at the real data in the description. The following is a pipeline that excercises all types of input we want to support at the moment - you can run this, and log at the console to get to a form that you can fill in to try it if you like: {noformat}node {stage("parallelStage"){echo "running"def branchInput = input id: 'CustomIdHere', message: 'this is a message to user', ok: 'Go ahead', parameters: [booleanParam(defaultValue: false, description: 'yes or no', name: 'thisIsBool'), choice(choices: 'c1\nc2', description: 'this is choice description', name: 'This is choice'), text(defaultValue: 'default', description: 'Long text goes here', name: 'This is a multi line string'), string(defaultValue: 'yeah', description: 'string parameter desc', name: 'this is a string parmeter'), password(defaultValue: 'secret', description: 'password param desc', name: 'password param')]echo "BRANCH NAME: ${branchInput}"}}{noformat}Note that it shows a choice as a drop down cc [~brody] [~jamesdumay] - (we wouldn't have both radio and drop down - which should it be - as there is only one "choice" type?) What this looks like in Jenkins today on the console screen: !Screen Shot 2016-12-13 at 4.51.12 pm.png|thumbnail!
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-40157) Subversion checkout it not working
Title: Message Title
Jon Sten commented on JENKINS-40157
Re: Subversion checkout it not working
The problem is that you are using single quotes in your remote url: '$ {Project_SVN} ' Variable references inside single quotes are not expanded in groovy, see http://stackoverflow.com/questions/6761498/whats-the-difference-of-strings-within-single-or-double-quotes-in-groovy
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-40157) Subversion checkout it not working
Title: Message Title
Jon Sten edited a comment on JENKINS-40157
Re: Subversion checkout it not working
The problem is that you are using single quotes in your remote url: '${Project_SVN}'Variable references inside single quotes are not expanded in groovy, see http://stackoverflow.com/questions/6761498/whats-the-difference-of-strings-within-single-or-double-quotes-in-groovy So, use double quotes and it should work fine
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-38494) User can see the input form on an input step (UI)
Title: Message Title
Michael Neale edited a comment on JENKINS-38494
Re: User can see the input form on an input step (UI)
I put some details on how to get at the real data in the description. The following is a pipeline that excercises all types of input we want to support at the moment - you can run this, and log at the console to get to a form that you can fill in to try it if you like: {noformat}node {stage("parallelStage"){echo "running" // def branchInput = input message: 'Please input branch to test against', parameters: [[$class: 'StringParameterDefinition', defaultValue: 'master', description: '', name: 'branch']]def branchInput = input id: 'CustomIdHere', message: 'this is a message to user', ok: 'Go ahead', parameters: [booleanParam(defaultValue: false, description: 'yes or no', name: 'thisIsBool'), choice(choices: 'c1\nc2', description: 'this is choice description', name: 'This is choice'), text(defaultValue: 'default', description: 'Long text goes here', name: 'This is a multi line string'), string(defaultValue: 'yeah', description: 'string parameter desc', name: 'this is a string parmeter'), password(defaultValue: 'secret', description: 'password param desc', name: 'password param')]echo "BRANCH NAME: ${branchInput}"}}{noformat}Note that it shows a choice as a drop down cc [~brody] [~jamesdumay] - (we wouldn't have both radio and drop down - which should it be - as there is only one "choice" type?)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
[JIRA] (JENKINS-38494) User can see the input form on an input step (UI)
Title: Message Title
Michael Neale edited a comment on JENKINS-38494
Re: User can see the input form on an input step (UI)
I put some details on how to get at the real data in the description. I will soon add some more samples of how to get The following is a pipeline that excercises all the other types of input fields. we want to support at the moment - you can run this, and log at the console to get to a form that you can fill in to try it if you like: {noformat}node {stage("parallelStage"){echo "running"//def branchInput = input message: 'Please input branch to test against', parameters: [[$class: 'StringParameterDefinition', defaultValue: 'master', description: '', name: 'branch']]def branchInput = input id: 'CustomIdHere', message: 'this is a message to user', ok: 'Go ahead', parameters: [booleanParam(defaultValue: false, description: 'yes or no', name: 'thisIsBool'), choice(choices: 'c1\nc2', description: 'this is choice description', name: 'This is choice'), text(defaultValue: 'default', description: 'Long text goes here', name: 'This is a multi line string'), string(defaultValue: 'yeah', description: 'string parameter desc', name: 'this is a string parmeter'), password(defaultValue: 'secret', description: 'password param desc', name: 'password param')]echo "BRANCH NAME: ${branchInput}"}}{noformat}Note that it shows a choice as a drop down cc [~brody] [~jamesdumay] - (we wouldn't have both radio and drop down - which should it be - as there is only one "choice" type?)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40071) Problème intégration JENKINS et ALM 12.21 (upload test result to ALM)
Title: Message Title Roy Lu commented on JENKINS-40071 Re: Problème intégration JENKINS et ALM 12.21 (upload test result to ALM) Hi LHoste Cedric, how do you configured your job? What's the step before the upload step? 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-39179) All builds hang, JNA load deadlock on Windows slave
Title: Message Title retronym commented on JENKINS-39179 Re: All builds hang, JNA load deadlock on Windows slave I see the configuration option now in the "Configure Slave" UI. It was hidden by default behind the "advanced" button. 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-40397) Support for run "list subversion tag" parameter type
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40397 Support for run "list subversion tag" parameter type Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Dec/13 6:34 AM Priority: Minor Reporter: James Dumay In scope Support for run "list subversion tag" parameter type Add Comment
[JIRA] (JENKINS-40398) Support the "credentials" input parameter type
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40398 Support the "credentials" input parameter type Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Dec/13 6:34 AM Priority: Minor Reporter: James Dumay In Scope Support the "credentials" input parameter type Add Comment
[JIRA] (JENKINS-40396) Support for run input parameter type
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40396 Support for run input parameter type Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Dec/13 6:33 AM Priority: Minor Reporter: James Dumay In Scope Support for run input parameter type Add Comment This message was
[JIRA] (JENKINS-40395) Support for file input parameter type
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40395 Support for file input parameter type Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Dec/13 6:32 AM Priority: Minor Reporter: James Dumay In Scope Support the "file" input parameter type Add Comment This message
[JIRA] (JENKINS-39179) All builds hang, JNA load deadlock on Windows slave
Title: Message Title
retronym edited a comment on JENKINS-39179
Re: All builds hang, JNA load deadlock on Windows slave
As another datapoint, we 're (the Scala team) are experiencing the same deadlock on Windows in our Jenkins instance.Version details:https://gist.github.com/retronym/ad96dc3595d51f1f1d210f8e4eadcbdfOur ticket about the issue:https://github.com/scala/scala-jenkins-infra/issues/203Thread dump:https://gist.github.com/retronym/a206e211da392a3e55c604c26543a80bWe are yet to try the workaround of using {{-Dhudson.remoting.RemoteClassLoader.force=com.sun.jna.Native}} as I wasn't sure where to configure this. [~gregcovertsmith] you mentioned in JENKINS-19445 that you couldn't try this because of your use of virtual slaves. We are using "launch slave agents on unix machines via SSH" option. Does anyone know if this can pick up JVM options from one of the configured environment variables?Having an option to disable use of JNA from either the cygpath plugin or the SwapSpaceMonitor would workaround the issue we're seeing. Doing a controlled initialization of JNA at Jenkins startup would be ideal, however.
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-39179) All builds hang, JNA load deadlock on Windows slave
Title: Message Title retronym commented on JENKINS-39179 Re: All builds hang, JNA load deadlock on Windows slave As another datapoint, we're experiencing the same deadlock on Windows in our Jenkins instance. Version details: https://gist.github.com/retronym/ad96dc3595d51f1f1d210f8e4eadcbdf Our ticket about the issue: https://github.com/scala/scala-jenkins-infra/issues/203 Thread dump: https://gist.github.com/retronym/a206e211da392a3e55c604c26543a80b We are yet to try the workaround of using -Dhudson.remoting.RemoteClassLoader.force=com.sun.jna.Native as I wasn't sure where to configure this. Greg Smith you mentioned in JENKINS-19445 that you couldn't try this because of your use of virtual slaves. We are using "launch slave agents on unix machines via SSH" option. Does anyone know if this can pick up JVM options from one of the configured environment variables? Having an option to disable use of JNA from either the cygpath plugin or the SwapSpaceMonitor would workaround the issue we're seeing. Doing a controlled initialization of JNA at Jenkins startup would be ideal, however. 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-39895) Jenkins permission denied error while building
Title: Message Title Eswari Ravinutala updated an issue Jenkins / JENKINS-39895 Jenkins permission denied error while building Change By: Eswari Ravinutala Hi,Our jenkins master is ubuntu and the slaves are windows. With 775 permission on the ClearCase VOB, the builds are failing with permission denied for write operations in the jenkins slave.with 777 (everyone all), the builds are working fine on jenkins slaves.We have given clearcase environment variables in the slaves and the jenkins service is configured with the maser build account who has all access to clearcase. I have also set up build runs thorugh the masterbuild account as an alternative. But whatever it may be, our jenkins clearcase buildes are failing with permission denied with 775 permission.WE have checked the group and owner. The both are at permissable level. I have also given all privileges to the master build account to the jenkins installation directory on the windows. The windows slaves are some Windows 2003 and some are Windows7. But whatever may be the Operating system, the builds are failing.This is critical to our system as 777 permission is open to the public. And we want to restrict with 775.I have seen https://issues.jenkins-ci.org/browse/JENKINS-36756, but not much of help.Note: I selected Jenkins test harness, as I did not see Jenkins distributed builds pluging. Regards, We are not using ClearCase plugin as all our projects are freestyle. Regards, Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38494) User can see the input form on an input step (UI)
Title: Message Title Michael Neale commented on JENKINS-38494 Re: User can see the input form on an input step (UI) I put some details on how to get at the real data in the description. I will soon add some more samples of how to get all the other types of input fields. 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-40394) Amount of UDP sockets growing
Title: Message Title Gerard Sunga created an issue Jenkins / JENKINS-40394 Amount of UDP sockets growing Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Dec/13 4:49 AM Environment: Jenkins 2.36 java version "1.7.0_121" OpenJDK Runtime Environment (IcedTea 2.6.8) (7u121-2.6.8-1ubuntu0.14.04.1) OpenJDK 64-Bit Server VM (build 24.121-b00, mixed mode) 3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2 15:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux - Ubuntu 14.04 LTS /usr/bin/java -Djava.awt.headless=true -Dhudson.DNSMultiCast.disabled=true -Dhudson.udp=-1 -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 Priority: Major Reporter: Gerard Sunga I'm running a few jobs every minute, and I'm seeing the amount of UDP sockets grow at the start of every minute, eventually resulting in jenkins crashing due to too many open file descriptors. Add Comment
[JIRA] (JENKINS-38494) User can see the input form on an input step (UI)
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38494
User can see the input form on an input step (UI)
Change By:
Michael Neale
In Scope* Step should show the "waiting for input" indicator.* Input form should be shown where the log is usually shown.* When the user clicks "Submit" the form disappears and the log for that step is shown (Note: progress via karaoke should resume at this point)* User cannot submit the form unless they have filled in all values.* We will need to show a form validation message if the user tries to submit the form with empty values.* See https://issues.jenkins-ci.org/browse/JENKINS-35899 for details on the visual design of this and screen shotsBefore vivek left he was able to merge the first tranche of support for input. This is described in this closed PR here: https://github.com/jenkinsci/blueocean-plugin/pull/645 (with a sample pipeline, that will return states waiting for input)Creating the following pipeline and calling it "paused"{noformat}node {stage("parallelStage"){ parallel left : {echo "running"def branchInput = input message: 'Please input branch to test against', parameters: [[$class: 'StringParameterDefinition', defaultValue: 'master', description: '', name: 'branch']]echo "BRANCH NAME: ${branchInput}"}, right : {sh 'sleep 10'}}}{noformat}Run it - and then go to the following URL: http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/paused/runs/1/steps/And you will see: {noformat}{"_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineStepImpl","_links": {},"actions": [],"displayName": "Wait for interactive input","durationInMillis": 124735,"id": "12","input": {"_class": "io.jenkins.blueocean.rest.impl.pipeline.InputStepImpl","_links": {"self": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/blue/rest/organizations/jenkins/pipelines/paused/runs/1/steps/12/input/"}},"id": "C51b52435b43a326d5d4f92c290a64d5","message": "Please input branch to test against","ok": "Proceed","parameters": [{"_class": "hudson.model.StringParameterDefinition","defaultParameterValue": {"_class": "hudson.model.StringParameterValue","name": "branch","value": "master"},"description": "","name": "branch","type": "StringParameterDefinition"}],"submitter": null},"result": "UNKNOWN","startTime": "2016-12-13T15:32:28.343+1100","state": "PAUSED"}{noformat}We can come up with more canonical examples of all input types once familiar with the api : GET /jenkins/blue/rest/organizations/jenkins/pipelines/pipeline1/runs/1/ should report state==PAUSED, result==UNKNOWNGET /jenkins/blue/rest/organizations/jenkins/pipelines/pipeline1/runs/1/nodes/ should report state==PAUSED, result==UNKNOWN for nodes parallelStage and right.GET /jenkins/blue/rest/organizations/jenkins/pipelines/pipeline1/runs/1/steps/ should report state==PAUSED, result==UNKNOWN for step id 12When you drill into a step for a paused node you can see the input required: eg:
[JIRA] (JENKINS-38494) User can see the input form on an input step (UI)
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38494
User can see the input form on an input step (UI)
Change By:
Michael Neale
In Scope* Step should show the "waiting for input" indicator.* Input form should be shown where the log is usually shown.* When the user clicks "Submit" the form disappears and the log for that step is shown (Note: progress via karaoke should resume at this point)* User cannot submit the form unless they have filled in all values.* We will need to show a form validation message if the user tries to submit the form with empty values.* See https://issues.jenkins-ci.org/browse/JENKINS-35899 for details on the visual design of this and screen shotsBefore vivek left he was able to merge the first tranche of support for input. This is described in this closed PR here: https://github.com/jenkinsci/blueocean-plugin/pull/645 (with a sample pipeline, that will return states waiting for input) Creating the following pipeline and calling it "paused"{noformat}node {stage("parallelStage"){ parallel left : {echo "running"def branchInput = input message: 'Please input branch to test against', parameters: [[$class: 'StringParameterDefinition', defaultValue: 'master', description: '', name: 'branch']]echo "BRANCH NAME: ${branchInput}"}, right : {sh 'sleep 10'}}}{noformat}Run it - and then go to the following URL: http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/paused/runs/1/steps/And you will see: {noformat}{"_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineStepImpl","_links": {},"actions": [],"displayName": "Wait for interactive input","durationInMillis": 124735,"id": "12","input": {"_class": "io.jenkins.blueocean.rest.impl.pipeline.InputStepImpl","_links": {"self": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/blue/rest/organizations/jenkins/pipelines/paused/runs/1/steps/12/input/"}},"id": "C51b52435b43a326d5d4f92c290a64d5","message": "Please input branch to test against","ok": "Proceed","parameters": [{"_class": "hudson.model.StringParameterDefinition","defaultParameterValue": {"_class": "hudson.model.StringParameterValue","name": "branch","value": "master"},"description": "","name": "branch","type": "StringParameterDefinition"}],"submitter": null},"result": "UNKNOWN","startTime": "2016-12-13T15:32:28.343+1100","state": "PAUSED"}{noformat}We can come up with more canonical examples of all input types once familiar with the api
[JIRA] (JENKINS-38494) User can see the input form on an input step (UI)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38494 User can see the input form on an input step (UI) Change By: Michael Neale In Scope* Step should show the "waiting for input" indicator.* Input form should be shown where the log is usually shown.* When the user clicks "Submit" the form disappears and the log for that step is shown (Note: progress via karaoke should resume at this point)* User cannot submit the form unless they have filled in all values.* We will need to show a form validation message if the user tries to submit the form with empty values.* See https://issues.jenkins-ci.org/browse/JENKINS-35899 for details on the visual design of this and screen shotsBefore vivek left he was able to merge the first tranche of support for input. This is described in this closed PR here: https://github.com/jenkinsci/blueocean-plugin/pull/645 (with a sample pipeline, that will return states waiting for input) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40236) Clang scan-build trend icon does not display
Title: Message Title Jarrod Connolly commented on JENKINS-40236 Re: Clang scan-build trend icon does not display Added a pull request for this issue. https://github.com/jenkinsci/clang-scanbuild-plugin/pull/12 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-40369) rerun button in rundetails sometimes redirects to the wrong url
Title: Message Title Michael Neale commented on JENKINS-40369 Re: rerun button in rundetails sometimes redirects to the wrong url I spent some time reproducing. I can confirm that the back end is sending back the wrong expectedBuildNumber, however it isn't clear when. I am lowering priority: This is a bug, but likely not with front end Seems related to some race condition when you run the ATH with really fast clicking Can't be seen in the wild (believe me, I tried, with many combinations including executor starvation) Doesn't seem to ever fail the ATH due to the built in retry 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-40369) rerun button in rundetails sometimes redirects to the wrong url
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40369 rerun button in rundetails sometimes redirects to the wrong url Change By: Michael Neale Sprint: tethys 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-40369) rerun button in rundetails sometimes redirects to the wrong url
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40369 rerun button in rundetails sometimes redirects to the wrong url Change By: Michael Neale Sprint: frank 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-39594) Frequent, intermittent "Failed to deploy artifacts: Could not transfer artifact" errors when uploading to Nexus 3
Title: Message Title Suresh Kumar resolved as Fixed Fixed and released in 2.9 version Jenkins / JENKINS-39594 Frequent, intermittent "Failed to deploy artifacts: Could not transfer artifact" errors when uploading to Nexus 3 Change By: Suresh Kumar Status: Open 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
[JIRA] (JENKINS-40372) Clicking re-run won't show up steps when there are no stages
Title: Message Title Michael Neale commented on JENKINS-40372 Re: Clicking re-run won't show up steps when there are no stages Actually is resolved by: https://github.com/jenkinsci/blueocean-plugin/pull/648 (I verified) 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-40369) rerun button in rundetails sometimes redirects to the wrong url
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40369 rerun button in rundetails sometimes redirects to the wrong url Change By: Michael Neale Priority: Major Minor 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-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title Val Orekhov updated an issue Jenkins / JENKINS-40294 Exec Failure: HTTP:404. Message:Not Found Change By: Val Orekhov Priority: Minor Critical 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-40359) Webhook registration fails for private Github repositories
Title: Message Title Justin Silver edited a comment on JENKINS-40359 Re: Webhook registration fails for private Github repositories Authentication error seems to be with Github even with proper Jenkins configuration. Some projects resolved the issue on their own, the remaining project was corrected by renaming on Github to an arbitrary value and then back to the original name. 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-40359) Webhook registration fails for private Github repositories
Title: Message Title Justin Silver resolved as Not A Defect Authentication error seems to be with Github even with proper Jenkins configuration. Some projects resolved the issue on their own, the remaining project was corrected by renaming to an arbitrary value and then back to the original name. Jenkins / JENKINS-40359 Webhook registration fails for private Github repositories Change By: Justin Silver Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-40359) Webhook registration fails for private Github repositories
Title: Message Title Justin Silver commented on JENKINS-40359 Re: Webhook registration fails for private Github repositories I renamed the repository in Github "project" to "project2" and then changed the URL in the job configuration, and when I saved the webhook was created on Github. I then deleted the webhook, renamed the project back to the original name, removed the 2 from the Jenkins config, and once it again it was able to create the webhooks when I saved. It seems that something was in fact messed up with my project on Github and renaming it seems to have fixed it 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-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title Val Orekhov commented on JENKINS-40294 Re: Exec Failure: HTTP:404. Message:Not Found I'm having an exact same issue on a K8N cluster configured on bare metal. Tried configuring a custom logger on org.apache.http to capture the calls but it's not showing any entries. Were you able to figure out a solution to this problem? Thanks! Val 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-40359) Webhook registration fails for private Github repositories
Title: Message Title Justin Silver commented on JENKINS-40359 Re: Webhook registration fails for private Github repositories I created a new private repository with only a README.md and copied the failing job only replacing the git URL with the new project name and it successfully created the webhooks. I also copied the failing job and just ran it without success. This seems to me to point to an error on Github's side, not Jenkins. 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-40359) Webhook registration fails for private Github repositories
Title: Message Title Justin Silver commented on JENKINS-40359 Re: Webhook registration fails for private Github repositories "doublesharp" is a user account. I'm still trying to debug on my end, and now I'm seeing strange behavior. I have 7 total jobs, with 4 public and 3 private. When I submitted this issue the 4 public repositories worked and all 3 private repositories were failing, however now only 1 private is failing and the others are successful. I manually deleted the webhook and verified that it was recreated by Jenkins when I saved the project configuration. I don't see any meaningful differences between the configurations, so I wonder if maybe the issue is actually with Github? 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-36783) Artifact download links rely on mime type to determine download vs. view
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-36783 Artifact download links rely on mime type to determine download vs. view Change By: James Dumay Sprint: kraken Assignee: Thorsten Scherler 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-40359) Webhook registration fails for private Github repositories
Title: Message Title Kanstantsin Shautsou commented on JENKINS-40359 Re: Webhook registration fails for private Github repositories Is it org or user? 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-40359) Webhook registration fails for private Github repositories
Title: Message Title Justin Silver commented on JENKINS-40359 Re: Webhook registration fails for private Github repositories I forgot to mentioned that I am replacing the real private repository name with "PRIVATE_REPOSITORY" in the error logs. 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-40359) Webhook registration fails for private Github repositories
Title: Message Title
Justin Silver commented on JENKINS-40359
Re: Webhook registration fails for private Github repositories
I don't have "private_repo" available as a scope, but per the UI the "repo" scope should allow full access to private repositories. Screenshot with selected scopes:Looking at the full system log the stracktrace that I posted earlier is preceded by this error:
Failed to obtain repository com.cloudbees.jenkins.GitHubRepositoryName$1@603ff301
java.io.FileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
at org.kohsuke.github.Requester.handleApiError(Requester.java:592)
at org.kohsuke.github.Requester._to(Requester.java:272)
at org.kohsuke.github.Requester.to(Requester.java:213)
at org.kohsuke.github.GitHub.getRepository(GitHub.java:369)
at com.cloudbees.jenkins.GitHubRepositoryName$1.applyNullSafe(GitHubRepositoryName.java:218)
at com.cloudbees.jenkins.GitHubRepositoryName$1.applyNullSafe(GitHubRepositoryName.java:214)
at org.jenkinsci.plugins.github.util.misc.NullSafeFunction.apply(NullSafeFunction.java:18)
at com.google.common.collect.Iterators$8.next(Iterators.java:812)
at com.google.common.collect.Iterators$7.computeNext(Iterators.java:648)
at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
at com.google.common.collect.Iterators$7.computeNext(Iterators.java:647)
at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
at com.google.common.collect.Iterators.tryFind(Iterators.java:757)
at com.google.common.collect.Iterables.tryFind(Iterables.java:671)
at org.jenkinsci.plugins.github.util.FluentIterableWrapper.firstMatch(FluentIterableWrapper.java:126)
at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:180)
at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:175)
at org.jenkinsci.plugins.github.util.misc.NullSafeFunction.apply(NullSafeFunction.java:18)
at com.google.common.collect.Iterators$8.next(Iterators.java:812)
at com.google.common.collect.Iterators$7.computeNext(Iterators.java:648)
at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
at com.google.common.collect.Iterators$7.computeNext(Iterators.java:647)
at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
at com.google.common.collect.Lists.newArrayList(Lists.java:138)
at com.google.common.collect.Lists.newArrayList(Lists.java:119)
at org.jenkinsci.plugins.github.util.FluentIterableWrapper.toList(FluentIterableWrapper.java:147)
at org.jenkinsci.plugins.github.webhook.WebhookManager$1.run(WebhookManager.java:127)
at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
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
[JIRA] (JENKINS-40359) Webhook registration fails for private Github repositories
Title: Message Title Justin Silver updated an issue Jenkins / JENKINS-40359 Webhook registration fails for private Github repositories Change By: Justin Silver Attachment: Screen Shot 2016-12-12 at 5.15.35 PM.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-40359) Webhook registration fails for private Github repositories
Title: Message Title Kanstantsin Shautsou commented on JENKINS-40359 Re: Webhook registration fails for private Github repositories What scopes do you have for this user token that used in global configuration? Does it have private_repo? Please provide screenshot. 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-40359) Webhook registration fails for private Github repositories
Title: Message Title Justin Silver edited a comment on JENKINS-40359 Re: Webhook registration fails for private Github repositories "doublesharp" is my Github username, and all of the repositories in my Jenkins install belong to that account. I am able to create the webhooks from Jenkins for the public repositories (like https://github.com/doublesharp/lru-cache-for-clusters-as-promised), however it does not create the webhooks for my private repositories. I am able to build the project private projects manually, or from manually created webhooks, so the "doublesharp" user is able to clone the private repository, which I assumed meant that it was configured correctly within the job. Does this user need to be configured elsewhere to access the 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-40359) Webhook registration fails for private Github repositories
Title: Message Title Justin Silver commented on JENKINS-40359 Re: Webhook registration fails for private Github repositories "doublesharp" is my Github username, and all of the repositories in my Jenkins install belong to that account. I am able to create the webhooks from Jenkins for the public repositories (like https://github.com/doublesharp/lru-cache-for-clusters-as-promised), however it does not create the webhooks for my private repositories. I am able to build the project manually, or from manually created webhooks, so the "doublesharp" user is able to clone the private repository, which I assumed meant that it was configured correctly within the job. Does this user need to be configured elsewhere to access the 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-40359) Webhook registration fails for private Github repositories
Title: Message Title Kanstantsin Shautsou assigned an issue to Kanstantsin Shautsou Jenkins / JENKINS-40359 Webhook registration fails for private Github repositories Change By: Kanstantsin Shautsou Assignee: Kirill Merkushev Kanstantsin Shautsou 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-40359) Webhook registration fails for private Github repositories
Title: Message Title Kanstantsin Shautsou commented on JENKINS-40359 Re: Webhook registration fails for private Github repositories java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=doublesharp,repository=PRIVATE_PROJECT] 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-40359) Webhook registration fails for private Github repositories
Title: Message Title Justin Silver commented on JENKINS-40359 Re: Webhook registration fails for private Github repositories Just one Github server - "https://api.github.com", using a Personal Access Token for my user. Which global user are you referring to? My configuration is only using my personal Github user. 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-40256) Enhancements to form controls
Title: Message Title Cliff Meyers commented on JENKINS-40256 Re: Enhancements to form controls PR is ready for review. Going to handle error states and some more "form layout" stuff in a subsequent PR, to keep the size of this manageable. 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-40256) Enhancements to form controls
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-40256 Enhancements to form controls Change By: Cliff Meyers Implement finalized style guide...* (/) States for Text Input, Text Area, Radio Button, Checkbox, Dropdown** Focus** Disabled* ( x / ) New button styles (primary and inverted)* ( x) Error states for Text Input, Text Area* ( /) Sizes for Text Area, Text Input* (/) Restyle dropdown 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-40373) Agent went offline during the build after configuring NIC teaming
Title: Message Title Rakesh Dama commented on JENKINS-40373 Re: Agent went offline during the build after configuring NIC teaming I am also facing the similar error, but happening only for one job. Remaining all jobs working fine. Do we have root cause. Thanks R Dama. 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-40393) Internationalize all the error messages in Declarative
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-40393 Internationalize all the error messages in Declarative Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Dec/13 12:14 AM Priority: Major Reporter: Andrew Bayer We should change all the error messages (and probably any other string we expose, but I'm fairly sure all exposed strings are error messages) to be internationalized. Add Comment This message was sent by
[JIRA] (JENKINS-40239) Add descriptions for build conditions and expose them in the editor metadata
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-40239 Add descriptions for build conditions and expose them in the editor metadata I already added an endpoint in the editor metadata service for agents, and one for build condition names. But! I'm reusing this ticket for adding descriptions for build conditions. Change By: Andrew Bayer Summary: Provide descriptors Add descriptions for specialized aspects of build conditions and expose them in the pipeline editor 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
[JIRA] (JENKINS-40337) Support custom checkout scm behaviors
Title: Message Title Andrew Bayer updated JENKINS-40337 Jenkins / JENKINS-40337 Support custom checkout scm behaviors 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-40337) Support custom checkout scm behaviors
Title: Message Title Andrew Bayer commented on JENKINS-40337 Re: Support custom checkout scm behaviors Initial PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/67 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-39845) GitHub project URL property should not trim off tree/branch
Title: Message Title Sam Gleske commented on JENKINS-39845 Re: GitHub project URL property should not trim off tree/branch What I mean is the UI linking to a specific branch. I don't think it would confuse people. If a user wants it to represent a repository/project then they can set it to that. In this case, it is my desire for the UI to link the user to the specific branch of the project. Branch per job is not expected behaviour. Why is this not expected behavior? Jenkins can be configured to build only a specific branch. Why would it not be expected or desirable that one would want to link to said branch in the project URL? It's not about providing an automatic hook. This issue is about linking a user to the appropriate section of a code base for a given configured Jenkins job. I don't see how this could be confusing for a user; especially if the release notes properly communicate the change. 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-35408) TECoreException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters
Title: Message Title Scott Brenner commented on JENKINS-35408 Re: TECoreException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters Any resolution for 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-38475) Identify path filename if path/file name too long
Title: Message Title Scott Brenner commented on JENKINS-38475 Re: Identify path filename if path/file name too long Any resolution for 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-39845) GitHub project URL property should not trim off tree/branch
Title: Message Title Kanstantsin Shautsou commented on JENKINS-39845 Re: GitHub project URL property should not trim off tree/branch Branch per job is not expected behaviour. Cool triggers providing links directly to branch . This property is expected to represent repository. If you change it then people will be confused. I would suggest you attach additional BranchAction from some Listener ExtensionPoint. 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-40337) Support custom checkout scm behaviors
Title: Message Title Michael Neale commented on JENKINS-40337 Re: Support custom checkout scm behaviors SGTM 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-38802) Use a more sensible default GC algorithm for jenkins
Title: Message Title Baptiste Mathus commented on JENKINS-38802 Re: Use a more sensible default GC algorithm for jenkins I guess that makes sense. G1 for Java >= 8 seems to me logical in any case. I really don't think anyone expects a Jenkins master UI to freeze many seconds, but who would prefer that to losing a wee bit of throughput . Also, Sam Van Oort I remember there was a PR about that, more than the gist above? Can you add the link here or so? 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-39845) GitHub project URL property should not trim off tree/branch
Title: Message Title Sam Gleske edited a comment on JENKINS-39845 Re: GitHub project URL property should not trim off tree/branch This is incorrect behavior. It shouldn't trim off the full project URL because it completely ignores projects which were configured with specific branches. It is unfriendly to a user to drop them into a project that has many branches when the Jenkins job was configured for a specific branch. This line of thinking should be re-evaluated as to what value the current behavior is providing.I suggest that the current behavior is unfriendly and should not have been designed in the current manner. I'm willing to propose a pull request with a fix if you're willing to accept it. 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-39845) GitHub project URL property should not trim off tree/branch
Title: Message Title Sam Gleske edited a comment on JENKINS-39845 Re: GitHub project URL property should not trim off tree/branch This is incorrect unhelpful behavior. It shouldn't trim off the full project URL because it completely ignores projects which were configured with specific branches. It is unfriendly to a user to drop them into a project that has many branches when the Jenkins job was configured for a specific branch. This line of thinking should be re-evaluated as to what value the current behavior is providing.I suggest that the current behavior is unfriendly and should not have been designed in the current manner.I'm willing to propose a pull request with a fix if you're willing to accept it. 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-39845) GitHub project URL property should not trim off tree/branch
Title: Message Title Sam Gleske updated JENKINS-39845 Jenkins / JENKINS-39845 GitHub project URL property should not trim off tree/branch Change By: Sam Gleske Status: Closed In 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-39845) GitHub project URL property should not trim off tree/branch
Title: Message Title Sam Gleske commented on JENKINS-39845 Re: GitHub project URL property should not trim off tree/branch This is incorrect behavior. It shouldn't trim off the full project URL because it completely ignores projects which were configured with specific branches. It is unfriendly to a user to drop them into a project that has many branches when the Jenkins job was configured for a specific branch. This line of thinking should be re-evaluated as to what value the current behavior is providing. I suggest that the current behavior is unfriendly and should not have been designed in the current manner. 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-40342) No way to specify in the UI the network/IP address to use for SSH
Title: Message Title Tim Soderstrom commented on JENKINS-40342 Re: No way to specify in the UI the network/IP address to use for SSH In my testing so far, it seems to be working as described. I tried it with both networks just to make sure it wasn't do anything funky. I think our actual jobs are doing something odd I need to look at (and/or I picked the wrong job to use as a test), but the plugin itself seems to work as advertised (I see in the logs it's trying to connect where I tell it when it matches and likewise the UI has the proper IP bolded). I need to test more, but so far, it looks like we're in business! 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-40209) Developer can see all pipelines for an organization grouped on the dashboard
Title: Message Title James Dumay assigned an issue to Cliff Meyers Jenkins / JENKINS-40209 Developer can see all pipelines for an organization grouped on the dashboard Change By: James Dumay Assignee: James Dumay Cliff Meyers 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-40337) Support custom checkout scm behaviors
Title: Message Title Andrew Bayer commented on JENKINS-40337 Re: Support custom checkout scm behaviors Great! I'm going to add a top-level options section and a skipCheckout flag inside that section, so that we don't end up with tons of future flags. =) 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-32556) Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin
Title: Message Title Jesse Glick resolved as Fixed Daniel Sobral wrong component for that issue. Jenkins / JENKINS-32556 Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin Change By: Jesse Glick Status: Open 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-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Denys Digtiar commented on JENKINS-38228 Re: Incorrect implementation of `loadUserByUsename`, Users are added on demand Ivan Fernandez Calvo are we talking about the same thing? This is not about Id that IdP returns. Changing UserName will not make any difference. The problem is that SamlUserDetailsService to reconstruct User uses API that creates Users on demand. No matter what username Authorization Strategy query from SamlSecurityRealm it says such user exists because it creates them on demand. The fix in PR is just changing the `User#get` method to the one that is not creating users by default. 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-40206) Make the Blue Ocean dev process not suck so much
Title: Message Title Michael Neale commented on JENKINS-40206 Re: Make the Blue Ocean dev process not suck so much cc Tom FENNELLY epic has been created 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-40392) Improving developer experience for blue ocean core developers and extenders
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-40392 Improving developer experience for blue ocean core developers and extenders Issue Type: Epic Assignee: Unassigned Components: blueocean-plugin Created: 2016/Dec/12 10:01 PM Priority: Minor Reporter: Michael Neale Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
[JIRA] (JENKINS-40337) Support custom checkout scm behaviors
Title: Message Title Logan Glickfield commented on JENKINS-40337 Re: Support custom checkout scm behaviors That sounds like a reasonable solution to me! 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-40337) Support custom checkout scm behaviors
Title: Message Title Andrew Bayer commented on JENKINS-40337 Re: Support custom checkout scm behaviors How would you feel about a top-level "skipCheckout" (or something like that) option? Then you could do a customized checkout yourself at the beginning of your first stage. I'm as of yet unable to come up with a smooth way to allow specifying the various custom SCM options with validation at the top-level, so I think for now, I'd definitely lean towards a skip option, since that's simpler and I think can be useful in some other ways. 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-40227) blueocean site cannot be reached
Title: Message Title James Dumay resolved as Cannot Reproduce Matt Westlake I don't have enough information to reproduce this one. If you are able to provide more information don't hesitate to open this ticket again. Jenkins / JENKINS-40227 blueocean site cannot be reached Change By: James Dumay Status: Open Resolved Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-40367) Investigate making use of categories in with SCM 2.0 API
Title: Message Title Stephen Connolly commented on JENKINS-40367 Re: Investigate making use of categories in with SCM 2.0 API They will always have the same name... there is getName() which returns a name for use in URLs. there is getDisplayName() which returns a localized name in the current locale (we can adapt the API to return the localizable directly if you need that access to all the translations). The collection you get from the API will always be in getName() sorted order under Locale.ENGLISH. If you add a second source then the display name / name may get modified... For example, one source has Pull Requests under the name pull-requests... another source has Change Requests under the name change-requests... these are both the same category, so when a multibranch project has multiple sources they will be combined into change-requests_pull-requests as the getName() and the getDisplayName() will be Change Requests / Pull Requests... To give you a more concrete example... If you have an Accurev source and a GitHub source in the same multibranch project (because say you are migrating from Accurev to GitHub) you could then have: An UnclassifiedSCMHeadCategory with a name of default and a display name of Branches / Streams A ChangeRequestSCMHeadCatgeory with a name of pull-requests and a display name of Pull Requests (because Accurev does not have change requests as a concept A (to be implemented) TagSCMHeadCategory with a name of snapshots_tags and a display name of Snapshots / Tags If all this was in an organization folder, then the organization folder will have an UnclassifiedSCMSourceCategory with a name of default and a display name of Depots / Repositories All because Accurev uses a different set of idiomatic names for the concepts. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title Andrew Bayer commented on JENKINS-40370 Re: Run stage when branch name matches So I don't like this idea, if for no other reason than it's likely to lead to a slippery slope of "let's add a section for $SPECIFIC_CONDITION too!" and that's non-optimal. I see the point of it - it does make things simpler. But I don't think it's really that hard for a user to do the script part themselves. Maybe we have the editor have a list of special case conditions or a free script field? So that if you are going through the editor, you choose when and then Branch is... or whatever, but if you're editing the Jenkinsfile directly, you just get a script box. 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-40265) Promotion badge icon not showing after jenkins latest update
Title: Message Title Oleg Nenashev resolved as Duplicate Closing as a duplicate of JENKINS-40281, the fix has been released in 2.36 Jenkins / JENKINS-40265 Promotion badge icon not showing after jenkins latest update Change By: Oleg Nenashev 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
[JIRA] (JENKINS-40265) Promotion badge icon not showing after jenkins latest update
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40265 Promotion badge icon not showing after jenkins latest update Change By: Oleg Nenashev Component/s: core 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-40265) Promotion badge icon not showing after jenkins latest update
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40265 Promotion badge icon not showing after jenkins latest update Change By: Oleg Nenashev Labels: plugin promoted-builds regression 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-40370) Run stage when branch name matches
Title: Message Title James Dumay commented on JENKINS-40370 Re: Run stage when branch name matches Patrick Wolf agreed having two ways of doing this isn't great. Skipping stages with a script within when makes this feature not accessible to our target audience. Any bright ideas Andrew Bayer? 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-40265) Promotion badge icon not showing after jenkins latest update
Title: Message Title Alex Mondshain commented on JENKINS-40265 Re: Promotion badge icon not showing after jenkins latest update 2.36 fixed this for me 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-40265) Promotion badge icon not showing after jenkins latest update
Title: Message Title Alex Mondshain edited a comment on JENKINS-40265 Re: Promotion badge icon not showing after jenkins latest update 2.36 fixed this for meI think related to Several badges were missing in builds flagged as KeepBuildForever. (issue 40281, regression in 2.34) 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-40013) Unable to set and use global groovy functions
Title: Message Title Andrew Bayer commented on JENKINS-40013 Re: Unable to set and use global groovy functions Still can't reproduce this - what error are you getting? 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-40337) Support custom checkout scm behaviors
Title: Message Title Andrew Bayer started work on JENKINS-40337 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-40337) Support custom checkout scm behaviors
Title: Message Title Andrew Bayer commented on JENKINS-40337 Re: Support custom checkout scm behaviors Good question - thinking about that now. 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-40256) Enhancements to form controls
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-40256 Enhancements to form controls Change By: Cliff Meyers Implement finalized style guide...* (/) States for Text Input, Text Area, Radio Button, Checkbox, Dropdown** Focus** Disabled* (x) New button styles (primary and inverted)* (x) Error states for Text Input, Text Area* (/) Sizes for Text Area, Text Input* ( x / ) Restyle dropdown 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-40281) No Badge shown, Exception build.badgeActions depending on KeepBuildForever
Title: Message Title Daniel Beck updated JENKINS-40281 Fixed in 2.36 Jenkins / JENKINS-40281 No Badge shown, Exception build.badgeActions depending on KeepBuildForever Change By: Daniel Beck 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-40314) Jenkins URL cannot be set via environment
Title: Message Title Daniel Beck resolved as Not A Defect Not a bug. The intended actual host and port will often be unknown to Jenkins due to reverse proxies etc. While handling a request, Jenkins can infer the root URL, but in general, it's just impossible. Changing the configured(!!) URL based on a preference that may well have no effect on the effective URL accessed by users seems like a very bad idea. Jenkins / JENKINS-40314 Jenkins URL cannot be set via environment Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40389) Gerrit support for Multibranch Pipeline
Title: Message Title Patrick Wolf commented on JENKINS-40389 Re: Gerrit support for Multibranch Pipeline rsandell FYI 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-40391) Wipe Out Current Workspace issue with non-URL encoded characters in My Views
Title: Message Title Nick Zechmann created an issue Jenkins / JENKINS-40391 Wipe Out Current Workspace issue with non-URL encoded characters in My Views Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Dec/12 8:07 PM Environment: Jenkins: 2.8 Ubuntu 14.04 java version "1.7.0_80" 64bit Safari 10.0.1 Chrome Version 54.0.2840.98 (64-bit) Priority: Minor Reporter: Nick Zechmann Issue starts from creating a new "My View" with an apostrophe in it. (i.e. "MyView's" ). When you navigate to a Job under that newly created view and try to " Wipe Out Current Workspace ", it will throw: URL: http://localhost:8080/view/MyView's/job/asdf/ws/ SyntaxError: Unexpected identifier 's'. Expected ')' to end an argument list. I also tested this with Jenkins 2.19.4 and the issue is still there. Add Comment
[JIRA] (JENKINS-40175) Masked Passwords are shown while rebuild.
Title: Message Title Ben Jamin commented on JENKINS-40175 Re: Masked Passwords are shown while rebuild. No update on this issue ? 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-40390) Publishing Fortify 360 FPR Data ERROR: Build step failed with exception java.lang.NumberFormatException: For input string: "0_72)"
Title: Message Title Jason Hammond created an issue Jenkins / JENKINS-40390 Publishing Fortify 360 FPR Data ERROR: Build step failed with exception java.lang.NumberFormatException: For input string: "0_72)" Issue Type: Bug Assignee: samngms Components: fortify360-plugin Created: 2016/Dec/12 7:57 PM Environment: Windows Server 2012 R2 Jenkins 1.651.3 Fortify 360 plugin v 3.81 Priority: Major Reporter: Jason Hammond Using Jenkins to publish Fortify results in Jenkins. This worked with Fortify v4.21 and then we just upgraded Fortify to V16.10. Now the FPR file is throwing errors when trying to Publishing Fortify 360 FPR Data in Jenkins. Any Ideas? Is this a known issue? Console: 14:40:34 Publishing Fortify 360 FPR Data 14:40:36 ERROR: Build step failed with exception 14:40:36 java.lang.NumberFormatException: For input string: "0_72)" Add Comment
[JIRA] (JENKINS-40389) Gerrit support for Multibranch Pipeline
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-40389 Gerrit support for Multibranch Pipeline Issue Type: New Feature Assignee: Unassigned Attachments: Branch source options for MB Pipeline.png Components: workflow-multibranch-plugin Created: 2016/Dec/12 7:34 PM Priority: Minor Reporter: Dan Tranter Allow Gerrit "Branch Source" for Pipeline Multi-branch plugin. (currently only Git/GitHub and bitbucket are supported) Add Comment
[JIRA] (JENKINS-40342) No way to specify in the UI the network/IP address to use for SSH
Title: Message Title Tim Soderstrom commented on JENKINS-40342 Re: No way to specify in the UI the network/IP address to use for SSH Installed, thanks! I'm validating things right now. Having an issue I think that is more with Jenkins than the plugin so I'm working on that. Mostly I just wanted to update the issue so you knew I was taking a look. 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-40388) Rename "jobProperties" to "properties"
Title: Message Title Andrew Bayer commented on JENKINS-40388 Re: Rename "jobProperties" to "properties" PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/66 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-40388) Rename "jobProperties" to "properties"
Title: Message Title Andrew Bayer updated JENKINS-40388 Jenkins / JENKINS-40388 Rename "jobProperties" to "properties" 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-36516) EC2 plugin: Plugin fails to automatically launch slaves to meet demand
Title: Message Title Dan Stark commented on JENKINS-36516 Re: EC2 plugin: Plugin fails to automatically launch slaves to meet demand I'm also experiencing this issue with 1.36. I'm using spot instances if that matters. Here's the exception I'm seeing: Dec 12, 2016 7:02:19 PM hudson.plugins.ec2.EC2Cloud provision WARNING: Exception during provisioning com.amazonaws.SdkClientException: Unable to unmarshall response (Read timed out). Response Code: 200, Response Text: OK at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleResponse(AmazonHttpClient.java:1468) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1151) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:964) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:676) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:650) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:633) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$300(AmazonHttpClient.java:601) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:583) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:447) at com.amazonaws.services.ec2.AmazonEC2Client.doInvoke(AmazonEC2Client.java:11396) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:11372) at com.amazonaws.services.ec2.AmazonEC2Client.describeInstances(AmazonEC2Client.java:5542) at com.amazonaws.services.ec2.AmazonEC2Client.describeInstances(AmazonEC2Client.java:5554) at hudson.plugins.ec2.EC2Cloud.countCurrentEC2Slaves(EC2Cloud.java:363) at hudson.plugins.ec2.EC2Cloud.getPossibleNewSlavesCount(EC2Cloud.java:499) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:518) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:547) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:701) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:307) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:60) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:798) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: com.ctc.wstx.exc.WstxIOException: Read timed out at com.ctc.wstx.sr.StreamScanner.throwFromIOE(StreamScanner.java:708) at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1086) at com.ctc.wstx.evt.WstxEventReader.peek(WstxEventReader.java:306) at
