[JIRA] (JENKINS-41163) Launch retry not effective most of the time
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41163 Re: Launch retry not effective most of the time Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/plugins/sshslaves/SSHLauncher.java http://jenkins-ci.org/commit/ssh-slaves-plugin/44d7e2f9b1c768c52002e06b3ebecf5399f81cdb Log: [FIXED JENKINS-26379][FIXED JENKINS-41163]JENKINS-34100 Do not swallow IOException in case it is not recoverable. 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-41163) Launch retry not effective most of the time
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41163 Re: Launch retry not effective most of the time Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/plugins/sshslaves/SSHLauncher.java http://jenkins-ci.org/commit/ssh-slaves-plugin/d833545d4ef19b4aa24808383e80290320f1bec9 Log: Merge pull request #41 from olivergondza/JENKINS-41163 Do not swallow IOException in case it is not recoverable Compare: https://github.com/jenkinsci/ssh-slaves-plugin/compare/1df53269a568...d833545d4ef1 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-26379) Jenkins - ssh connection exception
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26379 Re: Jenkins - ssh connection exception Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/plugins/sshslaves/SSHLauncher.java http://jenkins-ci.org/commit/ssh-slaves-plugin/44d7e2f9b1c768c52002e06b3ebecf5399f81cdb Log: [FIXED JENKINS-26379][FIXED JENKINS-41163]JENKINS-34100 Do not swallow IOException in case it is not recoverable. 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-34100) Launch of cloud slave fails with "No route to host"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34100 Re: Launch of cloud slave fails with "No route to host" Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/plugins/sshslaves/SSHLauncher.java http://jenkins-ci.org/commit/ssh-slaves-plugin/44d7e2f9b1c768c52002e06b3ebecf5399f81cdb Log: [FIXED JENKINS-26379][FIXED JENKINS-41163]JENKINS-34100 Do not swallow IOException in case it is not recoverable. 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-38058) Properly pass context in folder's page objects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38058 Re: Properly pass context in folder's page objects Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/test/acceptance/po/Folder.java http://jenkins-ci.org/commit/acceptance-test-harness/88be022841ce43fe79fe57f32a8169314384fd48 Log: Merge pull request #264 from mafraba/JENKINS-38058 JENKINS-38058 bring back lost constructor for 'Folder' Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/252150450053...88be022841ce 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-41529) Rebuilder support by copyartifact
Title: Message Title ikedam created an issue Jenkins / JENKINS-41529 Rebuilder support by copyartifact Issue Type: New Feature Assignee: Unassigned Components: copyartifact-plugin, rebuild-plugin Created: 2017/Jan/28 6:13 AM Priority: Minor Reporter: ikedam RebuildParameterProvider allows provide rebuilder supports by parameter definitions provided by plugins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39978) hidden build parameters with its value "xxxBuildSelector" causes rebuild to fail
Title: Message Title ikedam updated an issue Jenkins / JENKINS-39978 hidden build parameters with its value "xxxBuildSelector" causes rebuild to fail Looks caused for incomplete workaround for copyartifact. JENKINS-13644 b46fdf3 Change By: ikedam Summary: hidden build parameters with its value "xxxBuildSelector" causes rebuild to fail 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-39978) hidden build parameters causes rebuild to fail
Title: Message Title
ikedam updated an issue
Jenkins / JENKINS-39978
hidden build parameters causes rebuild to fail
It apparently don't relates to copyartifact as it reproduced even without copyartifact in my environment.
Change By:
ikedam
Summary:
Copy artifact plugin hidden build parameters causes rebuild to fail when using hidden build parameters
Component/s:
copyartifact-plugin
The Rebuild plugin in jenkins fails to rebuild a job when it contains a hidden string parameter that contains the character string "MultiJobBuildSelector" in the default value field. For a simple reproducible example do the following: * install the following plugins: - copy artifact - , rebuild, hidden parameter * create a new job with the following configuration: ** Add a parameter of type "hidden" with an arbitrary name and a defult value of "MultiJobBuildSelector" * save the job and run it once * select the build that just completed and click the "rebuild" linkThis produces the following error (see attached screenshot):{panel}javax.servlet.ServletException: java.lang.ClassCastException: com.wangyin.parameter.WHideParameterDefinition cannot be cast to hudson.model.SimpleParameterDefinition{panel}This is fragile for those rare cases when a hidden parameter actually does need to contain that exact string, but it is also problematic when one wants to have a hidden job parameter to control which build the copy artifact plugin should use.I would suggest two changes here: # modify the logic of the multijob build selector to look for an exact match for the XML configuration needed to correctly populate a build selector parameter (avoiding accidental matches ) # modify the rebuild logic so that when a hidden parameter contains this exact XML that it correctly instantiates the multijob build selector so copy artifacts will work correctly when rebuilt using a hidden string parameter
[JIRA] (JENKINS-40820) Build time out does not work, I use abort the build
Title: Message Title ikedam assigned an issue to Ankit Gupta Jenkins / JENKINS-40820 Build time out does not work, I use abort the build Change By: ikedam Assignee: ikedam Ankit Gupta 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-41274) "Run as Specific User" does not work with Pipeline Jobs
Title: Message Title ikedam commented on JENKINS-41274 Re: "Run as Specific User" does not work with Pipeline Jobs Cannot reproduce in my environment. It is difficult for us to know what authorization a pipeline is running as, as it doesn't display it in the log like freestyle projects. Steps I tested: Install Jenkins 2.32.1 with recommended plugins. Create user "admin" Install authorize-project-1.2.2 (current latest) Create following users: user1 user2 Manage Jenkins > Configure Global Security Access Control Authorization Matrix-based security Admin can do everything user1, user2 can do anything except Administer, ConfigureUpdateCenter, RunScripts, UploadPlugins. Access Control for Builds Per-project configurable Build Authorization Enable "Run as Specific User" Create a new Pipeline job: test Configure Build Authorization Authorize Strategy: Run as Specific User
[JIRA] (JENKINS-41504) Jenkins integration in CentOs problem
Title: Message Title
Mark Waite edited a comment on JENKINS-41504
Re: Jenkins integration in CentOs problem
Please use the jenkins-user mailing list for configuration help, rather than a bug report. Far more users read the jenkins user mailing list than read individual bug reports, so you're more likely to receive timely help. Though, based on the message, you likely have a system configuration error. The global settings for the git plugin include a location to define the git executable. On a CentOS machine (and almost every other case), it should have the value "git". It appears from your output that the value is empty.If it had not been empty, the error message would have been:bq. Error performing command: *git* ls-remote ...Instead, you have the error message:{quote}Error performing command: git ls-remote ...{quote}
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-41504) Jenkins integration in CentOs problem
Title: Message Title
Mark Waite edited a comment on JENKINS-41504
Re: Jenkins integration in CentOs problem
Please use the jenkins-user mailing list for configuration help, rather than a bug report. Far more users read the jenkins user mailing list than read individual bug reports, so you're more likely to receive timely help.Though, based on the message, you likely have a system configuration error. The global settings for the git plugin include a location to define the git executable. On a CentOS machine (and almost every other case), it should have the value "git". It appears from your output that the value is empty.If it had not been empty, the error message would have been:bq. Error performing command: *git* ls-remote ...Instead, you have the error message:{quote}Error performing command: git ls-remote ...{quote}
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-41504) Jenkins integration in CentOs problem
Title: Message Title Mark Waite closed an issue as Not A Defect Please use the jenkins-user mailing list for configuration help, rather than a bug report. Far more users read the jenkins user mailing list than read individual bug reports, so you're more likely to receive timely help. Jenkins / JENKINS-41504 Jenkins integration in CentOs problem Change By: Mark Waite Status: Open Closed 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 "Jenkins Issues" group. To unsubscribe
[JIRA] (JENKINS-41504) Jenkins integration in CentOs problem
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-41504 Jenkins integration in CentOs problem Change By: Mark Waite Assignee: Mark Waite 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-39647) Failed to write defaultParameterValue: IAE from ExtensibleChoiceParameterDefinition.createValueCommon
Title: Message Title James Dumay commented on JENKINS-39647 Re: Failed to write defaultParameterValue: IAE from ExtensibleChoiceParameterDefinition.createValueCommon Nice one! 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-39647) Failed to write defaultParameterValue: IAE from ExtensibleChoiceParameterDefinition.createValueCommon
Title: Message Title ikedam updated JENKINS-39647 Fixed in extensible-choice 1.3.4. It will be available in the update center in a day. Please try that. Jenkins / JENKINS-39647 Failed to write defaultParameterValue: IAE from ExtensibleChoiceParameterDefinition.createValueCommon Change By: ikedam Status: In Review Resolved Assignee: ikedam Sterling Heibeck Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39647) Failed to write defaultParameterValue: IAE from ExtensibleChoiceParameterDefinition.createValueCommon
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39647 Re: Failed to write defaultParameterValue: IAE from ExtensibleChoiceParameterDefinition.createValueCommon Code changed in jenkins User: ikedam Path: src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ExtensibleChoiceParameterDefinition.java src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ExtensibleChoiceParameterDefinitionJenkinsTest.java http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/535d9d79337948fbbbefabb9189aad2d67cdd53d Log: [FIXED JENKINS-39647] `getDefaultParameterValue` should not fail 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-41373) Github SCM "creation" returns unhandled 403 exception when user lacks "create job" permission
Title: Message Title Vivek Pandey updated JENKINS-41373 Jenkins / JENKINS-41373 Github SCM "creation" returns unhandled 403 exception when user lacks "create job" permission 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-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title
Vivek Pandey commented on JENKINS-41403
Re: Additions to Github APIs for Organizations and Repositories
Cliff Meyers >> So auto-discover is false if in model there are no branch filtering specified? that is branch filter is empty then its auto-discover? > What we call "auto discover" in the UI is the mode where there is no filtering of repositories. You said "branch filtering" but I think perhaps you mean "repository filtering" First of all there could be more than one jenkins org folder for a given GitHub organization. Second there is no definitive way to tell if it was auto-discover. This is UI concept so I can provide an element that can provide list of requested repos when jenkins org folder was created. If its empty you can compute its auto-discover. So my proposed json element in GitHub organization response could be:
{
...
"isJenkinsOrganizationPipeline":true,
"jenkinsOrganizationPipelines":[
{
"pipeline":"cloudbeers1",
"requestedRepos":["PR-7"],
"_links" : {
"self" : {
"_class" : "io.jenkins.blueocean.rest.hal.Link",
"href" : "/organizations/jenkins/pipelines/cloudbeers1/"
}
}
},
{
"pipeline":"cloudbeers2",
"requestedRepos":[], //will fetch all repos
"_links" : {
"self" : {
"_class" : "io.jenkins.blueocean.rest.hal.Link",
"href" : "/organizations/jenkins/pipelines/cloudbeers2/"
}
}
}
]
...
}
There could be more than one jenkins org folder for a given GitHub org, I am not sure how useful its going to be. I would avoid doing it unless there is UX defined to handle it. Lets chat about it Monday, will be good to have James Dumay and Michael Neale around to get clarification on expected UX.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey edited a comment on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories [~cliffmeyers]> I added #2 to this list, related to the HAL href to the Jenkins org folder. Let me know if you think that's doable. It I would avoid doing it as HAL that is not doable inside _links element . HAL links are HTTP reachable resources, org folder contains repositories and not other way round. This way when you fetch jenkins org folder (/jenkins/scm/github/organizations/cliffmeyers/) you should see HAL link to repositories. Besides if you are accessing /jenkins/scm/github/organizations/cliffmeyers/repositories/ then you already have org folder link that is /jenkins/scm/github/organizations/cliffmeyers/. I could expose it as separate element, but it should be a collection as there could be more than one jenkins org folder for a given GitHub organization. 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-41249) Job failed despite all stages being successful
Title: Message Title Ian Leitch commented on JENKINS-41249 Re: Job failed despite all stages being successful @jeffweiss I'll double check that, but I seems to remember that archiveArtifacts produces an error in the log if there aren't any artifcats - I'm not seeing that. 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-41266) java.lang.ArrayIndexOutOfBoundsException after AccuRev Plugin upgrade
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-41266 java.lang.ArrayIndexOutOfBoundsException after AccuRev Plugin upgrade Change By: Joseph Petersen 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Cliff Meyers > I added #2 to this list, related to the HAL href to the Jenkins org folder. Let me know if you think that's doable. It is not doable. HAL links are HTTP reachable resources, org folder contains repositories and not other way round. This way when you fetch jenkins org folder (/jenkins/scm/github/organizations/cliffmeyers/) you should see HAL link to repositories. Besides if you are accessing /jenkins/scm/github/organizations/cliffmeyers/repositories/ then you already have org folder link that is /jenkins/scm/github/organizations/cliffmeyers/. 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-24097) Allow configurable color for warning
Title: Message Title Guillaume DELORY commented on JENKINS-24097 Re: Allow configurable color for warning I just created a Pull Request for that. Hopefully someone will take a look at 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-24097) Allow configurable color for warning
Title: Message Title Guillaume DELORY updated JENKINS-24097 Jenkins / JENKINS-24097 Allow configurable color for warning Change By: Guillaume DELORY 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-24097) Allow configurable color for warning
Title: Message Title Guillaume DELORY started work on JENKINS-24097 Change By: Guillaume DELORY 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-24097) Allow configurable color for warning
Title: Message Title Guillaume DELORY assigned an issue to Guillaume DELORY Jenkins / JENKINS-24097 Allow configurable color for warning Change By: Guillaume DELORY Assignee: rgoren Guillaume DELORY 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-41236) SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"
Title: Message Title Gavin Mogan resolved as Fixed Liam Newman this should now be fixed in 1.160 https://github.com/saucelabs/jenkins-sauce-ondemand-plugin/blob/master/CHANGELOG.md#jenkins-1160---2017-01-27 I'll mark it as resolved, reopen if necessary Jenkins / JENKINS-41236 SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath" Change By: Gavin Mogan 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"
[JIRA] (JENKINS-37610) Sauce Labs Results Publisher throws Exception in Pipeline
Title: Message Title Gavin Mogan resolved as Fixed Liam Newman this should now be fixed in 1.160 https://github.com/saucelabs/jenkins-sauce-ondemand-plugin/blob/master/CHANGELOG.md#jenkins-1160---2017-01-27 I'll mark it as resolved, reopen if necessary Jenkins / JENKINS-37610 Sauce Labs Results Publisher throws Exception in Pipeline Change By: Gavin Mogan 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
[JIRA] (JENKINS-37610) Sauce Labs Results Publisher throws Exception in Pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37610 Re: Sauce Labs Results Publisher throws Exception in Pipeline Code changed in jenkins User: Gavin Mogan Path: pom.xml src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandTestPublisher.java src/main/resources/hudson/plugins/sauce_ondemand/SauceOnDemandTestPublisher/config.jelly src/main/resources/hudson/plugins/sauce_ondemand/SauceOnDemandTestPublisher/help.html http://jenkins-ci.org/commit/sauce-ondemand-plugin/cc61f90fe98e7dfc03c453155d9187befd2a6966 Log: Make parameters for publish sauce labs test results pipeline step optional - JENKINS-37610 Also make a helper symbol of saucePublisher() 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-41236) SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41236 Re: SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath" Code changed in jenkins User: Gavin Mogan Path: src/main/java/com/saucelabs/jenkins/pipeline/SauceConnectStep.java http://jenkins-ci.org/commit/sauce-ondemand-plugin/18608f6f3e3188fd0c4f3f0d5002291575c35fb1 Log: Make parameters for sauceconnect pipeline step optional - JENKINS-41236 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-34065) Pinned label in plugin list
Title: Message Title Jesse Glick updated JENKINS-34065 Jenkins / JENKINS-34065 Pinned label in plugin list 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-41488) Pipeline view automatically scrolls down
Title: Message Title James Dumay resolved as Duplicate Jenkins / JENKINS-41488 Pipeline view automatically scrolls down Change By: James Dumay Status: Reopened 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-41459) Loading never finishes on blue ocean dashboard when clicked show more button.
Title: Message Title James Dumay commented on JENKINS-41459 Re: Loading never finishes on blue ocean dashboard when clicked show more button. allen lee could you please provide the version of Blue Ocean you are using? Also please attach a HAR file for this request (You can learn about generating one here) 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-41488) Pipeline view automatically scrolls down
Title: Message Title James Dumay commented on JENKINS-41488 Re: Pipeline view automatically scrolls down Keith Zantow JENKINS-41088 is exactly the same as this feature request however there may be some details this ticket contributes that are not currently defined in 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-40951) Wall Display configuration broken and wrong visualisation of the wall
Title: Message Title Alex Earl commented on JENKINS-40951 Re: Wall Display configuration broken and wrong visualisation of the wall Jenkins logs would be useful. 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-41509) FavoriteCards which has no last run cannot be linked to detail view
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41509 FavoriteCards which has no last run cannot be linked to detail view Change By: James Dumay Sprint: post-release 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-41210) Cannot define custom email body
Title: Message Title
Alex Earl commented on JENKINS-41210
Re: Cannot define custom email body
You don't put the \${SCRIPT} token in the pre-send script. The pre-send script is for running operations that would allow you to modify the message before it is sent, or cancel sending the message. You put the content you want in the email in the "Default Content" or in the Content for a specific trigger. There are help buttons next to all the fields that will give you information on how to use them.
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-34065) Pinned label in plugin list
Title: Message Title Jesse Glick started work on JENKINS-34065 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-34065) Pinned label in plugin list
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-34065 Pinned label in plugin list Change By: Jesse Glick Assignee: 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-34065) Pinned label in plugin list
Title: Message Title Jesse Glick commented on JENKINS-34065 Re: Pinned label in plugin list Apparently plugins can still be pinned and unpinned According to whom? Not this 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-40442) Role assignments are case sensitive to login credentials
Title: Message Title Jeff Blaine resolved as Duplicate Jenkins / JENKINS-40442 Role assignments are case sensitive to login credentials Change By: Jeff Blaine 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-41488) Pipeline view automatically scrolls down
Title: Message Title Keith Zantow reopened an issue I still don't think this is the same. Someone may be interested in looking at ONE EXACT pipeline execution. Jenkins / JENKINS-41488 Pipeline view automatically scrolls down Change By: Keith Zantow Resolution: Duplicate Status: Resolved Reopened 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.
[JIRA] (JENKINS-41081) Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41081 Re: Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step Code changed in jenkins User: Swathi Gangisetty Path: .gitignore src/main/java/com/anchore/jenkins/plugins/anchore/AnchoreAction.java src/main/java/com/anchore/jenkins/plugins/anchore/AnchoreBuilder.java src/main/java/com/anchore/jenkins/plugins/anchore/AnchoreQuery.java src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreAction/index.jelly src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreAction/summary.jelly src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/config.jelly src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/global.jelly src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-bailOnFail.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-bailOnPluginFail.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-bailOnWarn.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-containerId.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-containerImageId.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-doCleanup.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-doQuery.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-localVol.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-modulesVol.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-name.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-policyName.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-query1.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-query2.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-query3.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-query4.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-useSudo.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreBuilder/help-userScripts.html src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreQuery/config.jelly src/main/resources/com/anchore/jenkins/plugins/anchore/AnchoreQuery/help-query.html src/main/webapp/help/help-queriesBlock.html http://jenkins-ci.org/commit/anchore-container-scanner-plugin/5a7e570a285dcc015e5be94252833fa8698db54c Log: Plugin upgrades and bug fixes... Display Jenkins and Anchore plugin versions in build console log. Use default Anchore policy if it's not provided to plugin - JENKINS-41081. Dynamic list of queries. Improve logging. Clean up workspaces after plugin execution regardless of the end result.
[JIRA] (JENKINS-33392) Following the 'Role Strategy Plugin' instructions gets me locked out of Jenkins
Title: Message Title Jeff Blaine resolved as Not A Defect Jenkins / JENKINS-33392 Following the 'Role Strategy Plugin' instructions gets me locked out of Jenkins Change By: Jeff Blaine 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 "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-41074) UX Issue with Polling in Multibranch Pipeline
Title: Message Title Jesse Glick commented on JENKINS-41074 Re: UX Issue with Polling in Multibranch Pipeline amend WorkflowJob.poll to ignore polling on any SCM which came from a branch project I think this is really the correct behavior, rather than disabling polling altogether. The poll method gets a log handle so it can print a message about why it is ignoring polling on this SCM. What I am not sure about is how to implement this. SCMVar just gets to pass back an SCM, of some plugin-provided type, and SCMStep does not have any particular way of knowing where it came from. You can easily find the SCMRevisionAction indicating that a branch source was active on this build, but the old API SCMListener.onCheckout just gets a SCMRevisionState, which is what is stored for future use from WorkflowJob.poll, and there is no API for correlating an SCMRevisionState with an SCMRevision: these capture essentially similar information but they are not interconvertible. Perhaps scm-api could be amended so that SCMRevision could check whether it was the same as a given SCMRevisionState. Unfortunately even with such an API, there is no way the git plugin will soon support this, until JENKINS-19022 is implemented so that it actually uses SCMRevisionState as the API mandates. 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
[JIRA] (JENKINS-41488) Pipeline view automatically scrolls down
Title: Message Title James Dumay resolved as Duplicate Apologies, I marked this as the wrong duplicate - its JENKINS-41088. We are going to build a great page for a Pipeline that shows you the latest visualization of your Pipeline which will be perfect for big screens! Jenkins / JENKINS-41488 Pipeline view automatically scrolls down Change By: James Dumay Status: Reopened 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
[JIRA] (JENKINS-41088) Show "latest" run results via fixed URL (dashboard like feature)
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41088 Show "latest" run results via fixed URL (dashboard like feature) Change By: James Dumay Sprint: post-release 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-41146) SCM Trigger configuration being overwritten by SYSTEM user in Pipeline
Title: Message Title Jesse Glick resolved as Not A Defect As designed. I will emphasize this behavior in the step documentation though. Jenkins / JENKINS-41146 SCM Trigger configuration being overwritten by SYSTEM user in Pipeline Change By: Jesse Glick 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 "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-41074) UX Issue with Polling in Multibranch Pipeline
Title: Message Title Jesse Glick commented on JENKINS-41074 Re: UX Issue with Polling in Multibranch Pipeline Note that TimerTrigger (cron symbol) is occasionally desirable and unproblematic. For example, someone wants their master branch built every night, even if there are no recorded commits. 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-41528) Use local git reference repo to speed up cloning when using large jenkins instances
Title: Message Title Victor Martinez created an issue Jenkins / JENKINS-41528 Use local git reference repo to speed up cloning when using large jenkins instances Issue Type: New Feature Assignee: Victor Martinez Components: jenkinslint-plugin Created: 2017/Jan/27 9:38 PM Priority: Minor Reporter: Victor Martinez Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this
[JIRA] (JENKINS-41449) Get lint issues via API call
Title: Message Title Victor Martinez started work on JENKINS-41449 Change By: Victor Martinez 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-38617) SystemExit check when running system groovy scripts
Title: Message Title Victor Martinez started work on JENKINS-38617 Change By: Victor Martinez 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-34562) Parameterized Build option not providing advanced button in build page
Title: Message Title Victor Martinez assigned an issue to Unassigned Jenkins / JENKINS-34562 Parameterized Build option not providing advanced button in build page Change By: Victor Martinez Assignee: Victor Martinez 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-41277) can't upload artifacts to artifactory
Title: Message Title Andrew Martin commented on JENKINS-41277 Re: can't upload artifacts to artifactory I also had this problem and upgrading the Maven Integration Plugin from 2.12.1 to 2.14 resolved 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-38871) Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Undefined parameter var in token ENV], action = [Fail the build]
Title: Message Title Alex Earl commented on JENKINS-38871 Re: Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Undefined parameter var in token ENV], action = "" the build] If you are willing to try the .hpi I attached, please let me know if you see issues with 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-38871) Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Undefined parameter var in token ENV], action = [Fail the build]
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-38871 Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Undefined parameter var in token ENV], action = "" the build] Change By: Alex Earl Attachment: token-macro.hpi 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-41249) Job failed despite all stages being successful
Title: Message Title Jeff Weiss commented on JENKINS-41249 Re: Job failed despite all stages being successful Ian Leitch I recently had a similar problem which I discovered (read: wasted a full day) to be the result of an archiveArtifacts step that did not find any artifacts to archive. 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-39402) Jenkins creates massive HTTP headers that blows up proxies
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39402 Jenkins creates massive HTTP headers that blows up proxies Change By: Jesse Glick Labels: http lts-candidate robustness 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-41266) java.lang.ArrayIndexOutOfBoundsException after AccuRev Plugin upgrade
Title: Message Title Mark Berchem commented on JENKINS-41266 Re: java.lang.ArrayIndexOutOfBoundsException after AccuRev Plugin upgrade I upgraded to the 0.7.9 version of the AccuRev Plugin and it seems to be OK. 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-39402) Jenkins creates massive HTTP headers that blows up proxies
Title: Message Title Jesse Glick updated JENKINS-39402 Jenkins / JENKINS-39402 Jenkins creates massive HTTP headers that blows up proxies 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-39230) Artifactory Maven build hides stdout in Pipeline
Title: Message Title Tyrel Haveman commented on JENKINS-39230 Re: Artifactory Maven build hides stdout in Pipeline Thanks Eyal Ben Moshe, it does seem to be 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-41322) Lack of documentation
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-41322 Lack of documentation Change By: R. Tyler Croy Component/s: core Component/s: workflow-cps-global-lib-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-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey started work on JENKINS-41403 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-41373) Github SCM "creation" returns unhandled 403 exception when user lacks "create job" permission
Title: Message Title Vivek Pandey started work on JENKINS-41373 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-41521) Intermittent basic auth failure when adding jobs
Title: Message Title Keith Baitsell commented on JENKINS-41521 Re: Intermittent basic auth failure when adding jobs I've also got a wireshark capture I could share, but it's kinda hard to read since the problem only manifests itself with the encrypted protocol. 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-39402) Jenkins creates massive HTTP headers that blows up proxies
Title: Message Title Jesse Glick started work on JENKINS-39402 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-39402) Jenkins creates massive HTTP headers that blows up proxies
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-39402 Jenkins creates massive HTTP headers that blows up proxies Change By: Jesse Glick Assignee: 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-39402) Jenkins creates massive HTTP headers that blows up proxies
Title: Message Title Jesse Glick commented on JENKINS-39402 Re: Jenkins creates massive HTTP headers that blows up proxies Some plugins have similar issues; JENKINS-38720 offhand. Query in case someone wants to do a proactive search. 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-38720) 500 Server Error when notifying master of new mercurial commit: "Response header too large"
Title: Message Title Jesse Glick commented on JENKINS-38720 Re: 500 Server Error when notifying master of new mercurial commit: "Response header too large" Similar code exists in git-plugin but strangely I can find no analogous 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-39230) Artifactory Maven build hides stdout in Pipeline
Title: Message Title Eyal Ben Moshe commented on JENKINS-39230 Re: Artifactory Maven build hides stdout in Pipeline This issue was fixed as part of version 2.9.0 of the Artifactory Plugin. Can you please try it out and let us know if the is resolved 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-38021) Accessing unset global variable cause master to hang
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38021 Accessing unset global variable cause master to hang Change By: Jesse Glick Labels: documentation 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-38021) Accessing unset global variable cause master to hang
Title: Message Title Jesse Glick updated JENKINS-38021 Jenkins / JENKINS-38021 Accessing unset global variable cause master to hang 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-41527) "console" CLI command does not work with Pipeline projects
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-41527 "console" CLI command does not work with Pipeline projects Issue Type: Bug Assignee: CloudBees Inc. Components: core, pipeline Created: 2017/Jan/27 8:32 PM Labels: pipeline Priority: Minor Reporter: R. Tyler Croy I have a simple Pipeline defined named pirateship. I am able to build with the CLI: ➜ ~ ssh -p 2 -l admin localhost build -s pirateship Started pirateship #12 Completed pirateship #12 : SUCCESS ➜ ~ Using the console command does not work however: ➜ ~ ssh -p 2 -l admin localhost console pirateship ERROR: No such job 'pirateship'; perhaps you meant 'build-all-software'? ➜ ~ Jesse Glick suggested that the fix may be similar to the fix for JENKINS-28071
[JIRA] (JENKINS-41496) Bad pubsub dependency issue
Title: Message Title Vivek Pandey updated JENKINS-41496 Jenkins / JENKINS-41496 Bad pubsub dependency issue Change By: Vivek Pandey 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-41397) API to validate Git credentials
Title: Message Title Vivek Pandey updated JENKINS-41397 Jenkins / JENKINS-41397 API to validate Git credentials 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-17406) More scalable log viewer control
Title: Message Title Jesse Glick commented on JENKINS-17406 Re: More scalable log viewer control Probably due to be superseded by Blue Ocean (though that does not currently offer a better or even comparably powerful log viewer). 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-14435) No incremental display of progress within a line
Title: Message Title Jesse Glick commented on JENKINS-14435 Re: No incremental display of progress within a line Probably will not fix. 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-41481) Can't see list of version from maven-central for Sonal plugin auto installation
Title: Message Title Esteban Angee assigned an issue to Frédéric Meyrou Hi Frederic, I think there has been a mistake in the assignment of this issue. I'm responsible for Sonargraph's Jenkins plugin but I'm not related to Sonarqube development, thus I'm assigning it back to you so that you can assign it to the proper person. Regards, Jenkins / JENKINS-41481 Can't see list of version from maven-central for Sonal plugin auto installation Change By: Esteban Angee Assignee: Esteban Angee Frédéric Meyrou 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.
[JIRA] (JENKINS-25808) Set SHA256 as a fingerprint algorithm
Title: Message Title Matt Wilson commented on JENKINS-25808 Re: Set SHA256 as a fingerprint algorithm SHA256 would be nice. Ideally it would be great if we could get 3 listed. Sort of how Artifactory does it. SHA-1 SHA-256 MD5 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-31484) Endless loop in DefaultInvoker.getProperty when accessing field via getter/setter without @
Title: Message Title Jesse Glick updated JENKINS-31484 Jenkins / JENKINS-31484 Endless loop in DefaultInvoker.getProperty when accessing field via getter/setter without @ 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-41138) Coverity - Job Failed
Title: Message Title Joel Briggs commented on JENKINS-41138 Re: Coverity - Job Failed For both issues mentioned here, it seems that the file system capture was not enabled or working. If you can provide the console output logs and configuration it will be easier to determine if this is an issue with the plugin or a misconfiguration. (I'm looking for "--fs-capture-search" argument on the cov-build command with the $WORKSPACE directory value). Additionally, you could contact Coverity support to help assist 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-40168) Make the override of ENTRYPOINT by image.inside optional
Title: Message Title Andrew Bayer resolved as Duplicate Jenkins / JENKINS-40168 Make the override of ENTRYPOINT by image.inside optional Change By: Andrew Bayer 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-41395) docker.build() should sanitize input for newlines
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-41395 docker.build() should sanitize input for newlines Change By: Andrew Bayer Assignee: 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-40374) stash Notifier not available on Jenkins Plugin-Manager
Title: Message Title Pavel Batanov commented on JENKINS-40374 Re: stash Notifier not available on Jenkins Plugin-Manager Yeah, I have no such idea too, so thank Arnaud Héritier again for this. Fortunately I have an HPI file automatically published on github, so people can workaround this manually. 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-40429) Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy"
Title: Message Title Yevhenii Kurtov commented on JENKINS-40429 Re: Copy artifacts from multi-branch pipeline project with project name as a build parameter fails with "Unable to find project for artifact copy" Getting same error in multibranch enviornment with `step([$class: 'CopyArtifact', fingerprintArtifacts: true, optional: true, projectName: projectName, selector: [$class: 'StatusBuildSelector', stable: false]])` where projectName is a multibranch job 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-41134) failures in the windows build are ignored
Title: Message Title Alex Earl resolved as Fixed Jenkins / JENKINS-41134 failures in the windows build are ignored Change By: Alex Earl 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-41134) failures in the windows build are ignored
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41134 Re: failures in the windows build are ignored Code changed in jenkins User: Alex Earl Path: src/test/java/hudson/tasks/junit/TestResultTest.java src/test/resources/hudson/tasks/junit/JENKINS-41134/TestSuite_first.xml src/test/resources/hudson/tasks/junit/JENKINS-41134/TestSuite_second.xml http://jenkins-ci.org/commit/junit-plugin/c0f470f994693d50d78491bde7deb938903ccd7e Log: Add test for JENKINS-41134 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-41134) failures in the windows build are ignored
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41134 Re: failures in the windows build are ignored Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/tasks/junit/TestResult.java src/test/java/hudson/tasks/junit/TestResultTest.java src/test/resources/hudson/tasks/junit/JENKINS-41134/TestSuite_first.xml src/test/resources/hudson/tasks/junit/JENKINS-41134/TestSuite_second.xml src/test/resources/hudson/tasks/junit/JENKINS-41134/TestSuite_second_dup_first.xml http://jenkins-ci.org/commit/junit-plugin/631c41350f6eb24520af19083a9f2fe27163f572 Log: Merge pull request #63 from slide/master Fix JENKINS-41134 Compare: https://github.com/jenkinsci/junit-plugin/compare/90e7ddbda961...631c41350f6e 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-38871) Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Undefined parameter var in token ENV], action = [Fail the build]
Title: Message Title Alex Earl commented on JENKINS-38871 Re: Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Undefined parameter var in token ENV], action = "" the build] I think I might know why this happens and why it is intermittent. I will try and write a test to replicate it now that I understand it better. 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-40374) stash Notifier not available on Jenkins Plugin-Manager
Title: Message Title mcrooney commented on JENKINS-40374 Re: stash Notifier not available on Jenkins Plugin-Manager Apologies for any troubles! I renamed the Wiki page so more people could find the plugin, as it didn't show up if you searched for Bitbucket and Stash doesn't really exist anymore. You just had to "know" that it used to be called Stash and that a Stash plugin exists. Pavel Batanov, thanks for your help! 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-40374) stash Notifier not available on Jenkins Plugin-Manager
Title: Message Title mcrooney edited a comment on JENKINS-40374 Re: stash Notifier not available on Jenkins Plugin-Manager Apologies for any troubles! I renamed the Wiki page so more people could find the plugin, as it didn't show up if you searched for Bitbucket and Stash doesn't really exist anymore. You just had to "know" that it used to be called Stash and that a Stash plugin exists. I had no idea this could unpublish the plugin. [~scaytrase], thanks for your help! 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-37845) GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with
Title: Message Title Laurent TOURREAU commented on JENKINS-37845 Re: GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with I confirm this strange behavior. I used a fresh Jenkins 2.32.1 installed today with all Git/Plugins updated to their latest version before writing a new pipeline. To make the hook registering to work, I must run the pipeline first time ensuring a first checkout is performed. Once it is done, i disable GitHub hook trigger for GITScm polling option, save the job , re-enable the option and save again the job. Registration is done (i can see the webhook on githib project settings) and now the pipeline can be triggered. If is the expected process to register the hook, it should be documented clearly 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-41330) Extra VMs left running in Resource Group
Title: Message Title Claudiu Guiman started work on JENKINS-41330 Change By: Claudiu Guiman 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-41526) "Filter for Poll SCM" detects changes on similarly named folders
Title: Message Title Timothy Williams created an issue Jenkins / JENKINS-41526 "Filter for Poll SCM" detects changes on similarly named folders Issue Type: Bug Assignee: Joseph Petersen Components: accurev-plugin Created: 2017/Jan/27 6:47 PM Environment: Jenkins Version 2.32.1 AccuRev Plugin Version 0.7.9 Labels: regression Priority: Major Reporter: Timothy Williams "Filter for Poll SCM" detects changes on similarly named folders. We have three folders in the root of the stream named "hi-lib", "hi-lib-dal", and "hi-lib-dal-mongo". The "Filter for Poll SCM" for each folder job is set as "hi-lib/", "hi-lib-dal/", and "hi-lib-dal-mongo/". This is because without the trailing forward-slash AccuRev Plugin Version 0.7.6 would detect changes in each job even if changes were only promoted to one folder - adding the forward-slash resolved that issue. With AccuRev Plugin Version 0.7.9, after promoting a change to "hi-lib-dal-mongo", all three builds started for detected changes in all three folders even though only "hi-lib-dal-mongo" contained a promoted change. It appears something changed in AccuRev Plugin Version 0.7.9 that broke the polling and filtering by folders by ignoring the forward-slash that denoted the end of the folder name. Is there another way I should qualify the "Filter for Poll SCM" value? Thanks.
[JIRA] (JENKINS-31484) Endless loop in DefaultInvoker.getProperty when accessing field via getter/setter without @
Title: Message Title Jesse Glick updated JENKINS-31484 Jenkins / JENKINS-31484 Endless loop in DefaultInvoker.getProperty when accessing field via getter/setter without @ Change By: Jesse Glick Status: In Review 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-41525) Predefined parameters incompatible with Maven Metadata Plugin for Jenkins CI server
Title: Message Title Chris Gamache created an issue Jenkins / JENKINS-41525 Predefined parameters incompatible with Maven Metadata Plugin for Jenkins CI server Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2017/Jan/27 6:45 PM Environment: Jenkins 2.42; Parameterized Trigger Plugin 2.32; Maven Metadata Plugin 1.5.0 Priority: Minor Reporter: Chris Gamache When specifying predefined parameters in an upstream project: *_GROUP_ID *_ARTIFACT_ID *_VERSION *_PACKAGING (where * is the configured value in the Maven Metadata Plugin) since version 2.23 these values do not propagate to the triggered downstream project, even though the parameter definitions are provided by the Maven Metadata Plugin in the downstream project. Add Comment
[JIRA] (JENKINS-41524) Languague level dropdown list "N/A" option and when build runs it's set as null
Title: Message Title Matt Gibbs closed an issue as Fixed This should be fixed in 2.0.9. https://github.com/jenkinsci/fortify-on-demand-uploader-plugin/issues/23 Jenkins / JENKINS-41524 Languague level dropdown list "N/A" option and when build runs it's set as null Change By: Matt Gibbs 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
[JIRA] (JENKINS-41524) Languague level dropdown list "N/A" option and when build runs it's set as null
Title: Message Title Matt Gibbs commented on JENKINS-41524 Re: Languague level dropdown list "N/A" option and when build runs it's set as null This is fixed in 2.0.9. Sorry I didn't see this JIRA ticket. 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-32099) Using StringBuilder in Workflow makes failing build without warning
Title: Message Title Yevhenii Kurtov edited a comment on JENKINS-32099 Re: Using StringBuilder in Workflow makes failing build without warning I possibly run into the same situation with 2.6 - multibranch job crashes on `StringBuilder content = new StringBuilder();` and there is no visible errors in the console, it just fails withorg.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.lang.StringBuilder 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.
