[JIRA] (JENKINS-38225) TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD)
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-38225 TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD) Change By: GMC Software Development B Corporate I have tested the tokengroups group-lookup strategy of the (newest) Active Directory Plugin in our AD-environment. Out Our AD is setup as forest, were some users are located in the root-domain (e.g., root.local), but most user-accounts, security-groups and computers are located in the second resource -domain (e.g., subx.local).Therefore, the plugin is currently configured with* Domain Name = "subx.local,root.local",* Domain controller = "dc1.subx.local:3268,dc2.subx.local:3268"* Group Membership Lookup Strategy = "RECURSIVE"With this configuration, login "against" a local group of subx.local and by using an account of root.local (which is member of the local group) was is permitted.If I change the the group-lookup strategy to "TOKENGROUPS", the login fails .. and after some tests (with logging 'FINE'), I've determined (or assume), that:* Searching for the user-object and login (with credentials) is successful,* also getting the tokengroups-list (SIDs) will contain local, universal groups of the subx.local (which DC was asked),* But the the name-translation of the tokengroups-SIDs afterwards, is limited to the domain (by Bind-DN) of the user-object. Therefore, the security-groups of our resource-domain (subx.local) were not found!Assuming, that my findings/assumptions are correct: It is possible to change the implementation, that groups of "different" (but also configured/permitted domain), are permitted?Best regards from Salzburg,Markus Add Comment
[JIRA] (JENKINS-38225) TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD)
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-38225 TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD) Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2016/Sep/15 5:55 AM Environment: Windows Server 2008 R2 (x64), Active Directory plugin 1.48 Priority: Minor Reporter: GMC Software Development B Corporate I have tested the tokengroups group-lookup strategy of (newest) Active Directory Plugin in our AD-environment. Out AD is setup as forest, were some users are located in the root-domain (e.g., root.local), but most user-accounts, security-groups and computers are located in the second-domain (e.g., subx.local). Therefore, the plugin is currently configured with Domain Name = "subx.local,root.local", Domain controller = "dc1.subx.local:3268,dc2.subx.local:3268" Group Membership Lookup Strategy = "RECURSIVE" With this configuration, login "against" a local group of subx.local and using an account of root.local (which is member of the local group) was permitted. If I change the the group-lookup strategy to "TOKENGROUPS", the login fails ... ... and after some tests (with logging 'FINE'), I've determined (or assume), that: Searching for the user-object and login (with credentials) is successful,
[JIRA] (JENKINS-35476) Pipeline projects are not listed in widget
Title: Message Title Ignacio Albors assigned an issue to Ignacio Albors Jenkins / JENKINS-35476 Pipeline projects are not listed in widget Change By: Ignacio Albors Assignee: Ignacio Albors 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-38198) Jenkins and Maven SOA BPEL project deployment issue
Title: Message Title Atul Gupta updated an issue Jenkins / JENKINS-38198 Jenkins and Maven SOA BPEL project deployment issue Change By: Atul Gupta Labels: api configuration jenkins maven- plugin plugin pom 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-38198) Jenkins and Maven SOA BPEL project deployment issue
Title: Message Title Atul Gupta updated an issue Jenkins / JENKINS-38198 Jenkins and Maven SOA BPEL project deployment issue Change By: Atul Gupta Labels: api configuration jenkins plugin pom 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-26907) HockeyApp Configuration Lost after Jenkins Restart
Title: Message Title Darragh Sherwin commented on JENKINS-26907 Re: HockeyApp Configuration Lost after Jenkins Restart Thanks to some of the cloudbees folks at Jenkins World, we found a fix for this issue. See https://github.com/ohoeltke/hockeyapp-plugin/commit/84a31cef8fce00afcad94249e35783a6c0b6160c A pull request has been submitted 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-38224) The html select element added by the dropdownlist.jelly form control needs to have an id attribute
Title: Message Title Sridevi Sangaiah updated an issue Jenkins / JENKINS-38224 The html select element added by the dropdownlist.jelly form control needs to have an id attribute Change By: Sridevi Sangaiah The html select element added by the dropdownlist.jelly form control need needs to have an id attribute. In the validation flow, unlike save, the data submitted is not formatted. So, without the id attribute it is not possible to get the current selection in the validation flow 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-38224) The html select element added by the dropdownlist.jelly form control needs to have an id attribute
Title: Message Title Sridevi Sangaiah created an issue Jenkins / JENKINS-38224 The html select element added by the dropdownlist.jelly form control needs to have an id attribute Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Sep/15 4:36 AM Priority: Minor Reporter: Sridevi Sangaiah The html select element added by the dropdownlist.jelly form control need to have an id attribute. In the validation flow, unlike save, the data submitted is not formatted. So, without the id attribute it is not possible to get the current selection in the validation flow Add Comment
[JIRA] (JENKINS-38152) Jenkinsfile schema Java API as WorkflowRun action
Title: Message Title Sam Van Oort commented on JENKINS-38152 Re: Jenkinsfile schema Java API as WorkflowRun action Okay so that kind of helps make the use case clear, and makes sense 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-26907) HockeyApp Configuration Lost after Jenkins Restart
Title: Message Title Darragh Sherwin assigned an issue to Darragh Sherwin Jenkins / JENKINS-26907 HockeyApp Configuration Lost after Jenkins Restart Change By: Darragh Sherwin Assignee: Darragh Sherwin 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-31155) Workflow shared library improvements
Title: Message Title Mike Key commented on JENKINS-31155 Re: Workflow shared library improvements +1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34679) com.microsoft.tfs.core.exceptions.HTTPProxyUnauthorizedException: Access denied connecting to HTTP proxy XXX:3128 (no credentials were supplied)
Title: Message Title Olivier Dagenais resolved as Not A Defect The TFS plugin provides the Team Foundation Version Control (TFVC) SCM, which is not intended for accessing Git repositories. I've attempted to make this clearer with the labels in recent versions, so if you have any suggestions for improvements, they would be appreciated. As for proxy servers, they should also be much better supported in recent versions, including proxy servers that require authentication. Please open an issue if you find that's not the case. Jenkins / JENKINS-34679 com.microsoft.tfs.core.exceptions.HTTPProxyUnauthorizedException: Access denied connecting to HTTP proxy XXX:3128 (no credentials were supplied) Change By: Olivier Dagenais Status: Open Resolved Assignee: redsolo florent laville Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37710) Can't connect to TFS with TFS-PLUGIN
Title: Message Title Olivier Dagenais resolved as Fixed The fix for the [Test connection] button was included in release 5.2.0 Jenkins / JENKINS-37710 Can't connect to TFS with TFS-PLUGIN Change By: Olivier Dagenais Status: Open Resolved Assignee: redsolo Laura Molero Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Daniel Beck commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Then install it. MSBuild will veto all mspdbsrv killing. 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-32580) Plugin enable/disable information and dependencies are broken
Title: Message Title Daniel Beck commented on JENKINS-32580 Re: Plugin enable/disable information and dependencies are broken For example the Windows Slaves Plugin cannot be disabled, it claims that the jQuery plugin and other plugins depend on it. Not a bug, just a side effect of outdated core dependencies predating the release when Windows Slaves was detached from core and made into a plugin. Jenkins needs to assume an implied dependency exists. 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-26580) For JNLP slaves the master-slave communication should be encrypted
Title: Message Title Aaron Curley commented on JENKINS-26580 Re: For JNLP slaves the master-slave communication should be encrypted Great! Good to know. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey commented on JENKINS-38079 Re: Investigate performance degradation report Thanks Darragh Sherwin. This looks like search API performance issue as noted above, I will dig in to HAR file and get back. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Darragh Sherwin commented on JENKINS-38079 Re: Investigate performance degradation report As discussed at Jenkins World, HAR attached. Slownews when clicking on "Show More" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Darragh Sherwin updated an issue Jenkins / JENKINS-38079 Investigate performance degradation report Change By: Darragh Sherwin Attachment: blue-ocean-slow.har 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-33103) AccuRev Stream color is reset without a clear purpose
Title: Message Title Arno Moonen commented on JENKINS-33103 Re: AccuRev Stream color is reset without a clear purpose I think the answer is both. So on a global level you probably want to set the default and on a job level you'd probably want to override it. But still, resetting the color does not make sense to me, if you do not provide a way to set the color based on the result of the build for example. The client I'm currently working for that uses AccuRev has its own coloring scheme to indicate how a stream should be used (what its purpose is). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Vivek Pandey commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Michael Neale I could easily reproduce b1 state returned RUNNING by API instead of FINISHED/SUCCESS. It turns out underlying workflow-api is telling b1 is still running and so API ends up returning RUNNING state. I opened https://issues.jenkins-ci.org/browse/JENKINS-38223. There is workaround I can think of but I will wait for evaluation of JENKINS-38223. 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-38223) Incorrect state of completed parallel branch
Title: Message Title
Vivek Pandey created an issue
Jenkins / JENKINS-38223
Incorrect state of completed parallel branch
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-api-plugin
Created:
2016/Sep/15 1:45 AM
Priority:
Major
Reporter:
Vivek Pandey
Give following pipeline script, b1 branch finishes immediately and b2 is not completed yet (waiting for input). I determine branch's completion from a branch's end FlowNode and calling FlowNode.isRunning() returns true instead false as its already completed. This makes BlueOcean API returns b1 as running whereas its already been completed.
node {
stage("hey") {
echo "hello from hey"
}
stage("par") {
parallel (
"b1" : {
echo 'hello from b1'
},
"b2" : {
def branchInput = input message: 'Please input branch to test against', parameters: [[$class: 'StringParameterDefinition', defaultValue: 'master', description: '', name: 'branch']]
echo "BRANCH NAME: ${branchInput}"
}
)
}
stage("ho") {
echo "hello from ho"
}
}
[JIRA] (JENKINS-38205) Failed to deploy war on Weblogic: task completed abnormally (exit code = 1)
Title: Message Title Guillermo Figueroa edited a comment on JENKINS-38205 Re: Failed to deploy war on Weblogic: task completed abnormally (exit code = 1) Raphael, thanks for the quick response.weblogic.deploy.api.spi.DeploymentOptions isn't under the wlfullclient.jar.I tried with wlthint3client.jar (see weblogic-deployment-plugin-conf-3.png) but i I got this error in WebLogic Deployment Log: TASK EXECUTION Error: Could not find or load main class weblogic.DeployerI tried too with weblogic.jar (see weblogic-deployment-plugin-conf-4.png) but i I got the same error in WebLogic Deployment Log: TASK EXECUTION Error: Could not find or load main class weblogic.DeployerI put weblogic.jar, wlthint3client.jar, wlfullclient.jar in Jenkins home directory (you can see on images weblogic-deployment-plugin-conf-1.png, weblogic-deployment-plugin-conf-3.png, weblogic-deployment-plugin-conf-4.png) and my WebLogic is in another Machine, I don't have WebLogic on Jenkins Machine, could that be the problem?I ask because the "Additional classpath" field in Jenkins/Manage Jenkins/System Configuration/WebLogic Deployment Plugin says "The path pointing to the weblogic.jar library used to the plugin. If empty, the plugin will try to find out a WebLogic installation on the machine.". In "Additional class path" field, can I reference the files weblogic.jar or wlthint3client.jar from Weblogic Machine directory (not from Jenkins Machine directory)?, the fields validation don't let it, because the file must exist on Jenkins server, but I have this doubt. !weblogic-deployment-plugin-conf-3.png|thumbnail! !weblogic-deployment-plugin-conf-4.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38205) Failed to deploy war on Weblogic: task completed abnormally (exit code = 1)
Title: Message Title Guillermo Figueroa commented on JENKINS-38205 Re: Failed to deploy war on Weblogic: task completed abnormally (exit code = 1) Raphael, thanks for the quick response. weblogic.deploy.api.spi.DeploymentOptions isn't under the wlfullclient.jar. I tried with wlthint3client.jar (see weblogic-deployment-plugin-conf-3.png) but i got this error in WebLogic Deployment Log: TASK EXECUTION Error: Could not find or load main class weblogic.Deployer I tried too with weblogic.jar (see weblogic-deployment-plugin-conf-4.png) but i got the same error in WebLogic Deployment Log: TASK EXECUTION Error: Could not find or load main class weblogic.Deployer I put weblogic.jar, wlthint3client.jar, wlfullclient.jar in Jenkins home directory (you can see on images weblogic-deployment-plugin-conf-1.png, weblogic-deployment-plugin-conf-3.png, weblogic-deployment-plugin-conf-4.png) and my WebLogic is in another Machine, I don't have WebLogic on Jenkins Machine, could that be the problem? I ask because the "Additional classpath" field in Jenkins/Manage Jenkins/System Configuration/WebLogic Deployment Plugin says "The path pointing to the weblogic.jar library used to the plugin. If empty, the plugin will try to find out a WebLogic installation on the machine.". In "Additional class path" field, can I reference the files weblogic.jar or wlthint3client.jar from Weblogic Machine directory (not from Jenkins Machine directory)?, the fields validation don't let it, because the file must exist on Jenkins server, but I have this doubt. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38205) Failed to deploy war on Weblogic: task completed abnormally (exit code = 1)
Title: Message Title Guillermo Figueroa updated an issue Jenkins / JENKINS-38205 Failed to deploy war on Weblogic: task completed abnormally (exit code = 1) Change By: Guillermo Figueroa Attachment: weblogic-deployment-plugin-conf-3.png Attachment: weblogic-deployment-plugin-conf-4.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-38222) Cannot pass arguments to the "Parsing POMs" phase of a Maven build
Title: Message Title Joel Croteau created an issue Jenkins / JENKINS-38222 Cannot pass arguments to the "Parsing POMs" phase of a Maven build Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2016/Sep/15 1:12 AM Labels: maven Priority: Major Reporter: Joel Croteau I would very much like to be able to prevent the "Parsing POMs" phase of a Maven build from downloading snapshot updates of the POM's parents. I have modified POMs in a local repository that I want Jenkins to use, but if there are updates to the parent artifact it downloads this no matter what I do. I can prevent other artifacts from downloading by setting the `-nsu` flag in the goals, but this doesn't affect the initial "Parsing POMs" phase. Also, this makes the `hudson.maven.debug` flag meaningless here as there is no way to set this. Can we either add the ability to set Maven flags in this phase or create an option to prevent updating snapshot dependencies here? Add Comment
[JIRA] (JENKINS-38176) Steps not shown for incomplete parallel branch
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38176 Steps not shown for incomplete parallel branch Change By: Michael Neale Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Michael Neale commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Justin Rainwater I tried the instructions above but wasn't able to reproduce it with a build I had (maybe was fixed recently, but more likely I am not following along correctly). I was able to create a pipeline and freestyle job in a folder, link to its activity, or even its "results page" (ie the log) and have it follow along in a new browser tab. Perhaps if you could record a little video of it, and perhaps attach any logs from the browser console (it may be an error there that I don't see). I use a tool on OSX called "GIPHY CAPTURE" which does nice little screen gifs (small to upload) and often is easier to demonstrate things in action. 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-37843) REGRESSION direct link to a queued detail is not working anymore
Title: Message Title Michael Neale commented on JENKINS-37843 Re: REGRESSION direct link to a queued detail is not working anymore Justin Rainwater thanks lets track it there. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Michael Neale edited a comment on JENKINS-38079 Re: Investigate performance degradation report [~vivek] might be worth syncing up with [~tfennelly] so he is aware of these . (perhaps the SSE and js loading could be split off to him?) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38079 Investigate performance degradation report Change By: Michael Neale Priority: Critical Blocker 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-20718) Add Documentation and help for startup-trigger-plugin
Title: Message Title Emory Penney assigned an issue to Emory Penney Jenkins / JENKINS-20718 Add Documentation and help for startup-trigger-plugin Change By: Emory Penney Assignee: ashlux Emory Penney Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Michael Neale commented on JENKINS-38079 Re: Investigate performance degradation report Vivek Pandey might be worth syncing up with Tom FENNELLY so he is aware of these. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37770) Malformed JSON for /blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject
Title: Message Title Vivek Pandey commented on JENKINS-37770 Re: Malformed JSON for /blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject Hi emanuelez, Looks like a case of NPE coming from build-flow plugin during JSON serialization of FailureCauseBuildAction. As I mentioned in previous comment, I tried build-flow plugin but could not reproduce it. Can you describe whats your project setup is and build flow plugin configuration to help us reproduce 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-36189) Credentials from instance profile?
Title: Message Title Ben Walding commented on JENKINS-36189 Re: Credentials from instance profile? Trevor - I've just raised JENKINS-38220 which is likely the base requirement for the ECR plugin to leverage EC2 instance profiles. 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-38220) Support for EC2 instance profile credentials
Title: Message Title
Ben Walding created an issue
Jenkins / JENKINS-38220
Support for EC2 instance profile credentials
Issue Type:
Improvement
Assignee:
Nicolas De Loof
Components:
aws-credentials-plugin
Created:
2016/Sep/14 11:16 PM
Priority:
Minor
Reporter:
Ben Walding
In our AWS environment we avoid using static AWS credentials (i.e. AWS Access Key ID and AWS Secret Access Key) - instead we use ephemeral credentials that are supplied using the Amazon IAM/STS system. i.e. The use of static AWS credentials is not possible in our environment - we need to dynamically acquire credentials on the master / slave to. These credentials are then used to switch roles per our IAM configuration. Once the credentials are acquired, we use those credentials (Access Key ID, Secret Access Key, Session Token) to perform AWS actions as normal. An example As a brief example (from a pipeline script)
env.AWS_ACCESS_KEY_ID = ""
env.AWS_SECRET_ACCESS_KEY = ""
env.AWS_SESSION_TOKEN = ""
roleArn = "arn:aws:iam::<13 character AWS ID>:role/my-custom-role"
externalParam = "--external-id ABCDEFG" // security parameter - optional
json = sh(returnStdout: true,
script: "aws sts assume-role --duration-seconds 3600 --role-arn ${roleARN} --role-session-name rsn ${externalParam}"
def jsonSlurper = new groovy.json.JsonSlurperClassic()
def object = jsonSlurper.parseText(json)
return object.Credentials
Important points
external-id support required
credentials must be acquired on the correct instance
[JIRA] (JENKINS-38218) Additionnals classpath validation should support many dependencies
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-38218 Additionnals classpath validation should support many dependencies Change By: Raphael CHAUMIER Attachment: weblogic-deployment-plugin-conf-2.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-38221) Non informative error message when Marathon responds with HTTP 422
Title: Message Title Andrey Chernih created an issue Jenkins / JENKINS-38221 Non informative error message when Marathon responds with HTTP 422 Issue Type: Bug Assignee: Colin Components: marathon-plugin Created: 2016/Sep/14 11:16 PM Priority: Minor Reporter: Andrey Chernih When there's an error in JSON app definition, Marathon responds with HTTP 422 and appropriate error message. Jenkins Marathon plugin shows this error: java.lang.NullPointerException: reason at feign.Util.checkNotNull(Util.java:104) at feign.Response.(Response.java:49) at feign.Response.create(Response.java:60) at feign.Client$Default.convertResponse(Client.java:171) at feign.Client$Default.execute(Client.java:72) at feign.SynchronousMethodHandler.executeAndDecode(SynchronousMethodHandler.java:95) at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:74) at feign.ReflectiveFeign$FeignInvocationHandler.invoke(ReflectiveFeign.java:94) at com.sun.proxy.$Proxy108.updateApp(Unknown Source) at com.mesosphere.velocity.marathon.impl.MarathonBuilderImpl.update(MarathonBuilderImpl.java:71) at com.mesosphere.velocity.marathon.MarathonStep$MarathonStepExecution.run(MarathonStep.java:162) at com.mesosphere.velocity.marathon.MarathonStep$MarathonStepExecution.run(MarathonStep.java:143) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:40) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:184) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:126) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:120) at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151) at
[JIRA] (JENKINS-36215) Unable to deploy from a windows slave node
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-36215 Unable to deploy from a windows slave node Change By: Raphael CHAUMIER Labels: plugin weblogic-deployer-plugin-3.3 weblogic-deployer_plugin_4.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38218) Additionnals classpath validation should support many dependencies
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-38218 Additionnals classpath validation should support many dependencies Change By: Raphael CHAUMIER Labels: weblogic-deployer-plugin-3.6 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-38218) Additionnals classpath validation should support many dependencies
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-38218 Additionnals classpath validation should support many dependencies Change By: Raphael CHAUMIER Issue Type: Improvement Bug Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38205) Failed to deploy war on Weblogic: task completed abnormally (exit code = 1)
Title: Message Title Raphael CHAUMIER edited a comment on JENKINS-38205 Re: Failed to deploy war on Weblogic: task completed abnormally (exit code = 1) Hi [~guillermo_figueroa]You got a java.lang.ClassNotFoundException: weblogic.deploy.api.spi.DeploymentOptions. Can you check this class is under the wlfullclient.jar ? Can you try with wlthint3client.jar ? can you try with weblogic.jar ?wlfullclient.jar is deprecated in WLS 12 (see https://docs.oracle.com/middleware/1213/wls/SACLT/basics.htm#SACLT125)I added this information in wiki which was outdated. Don't append /path/to/wulfullclient.jar:/path/to/wlthint3client.jar. Regards 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-38217) Roadmap of authorize-project-plugin
Title: Message Title
ikedam updated an issue
Jenkins / JENKINS-38217
Roadmap of authorize-project-plugin
Change By:
ikedam
authorize-project-plugin have following issues for its design.* Authentications of the project during configuration and after configuration may change.** This makes it difficult for other plugins behave depending on authentications of projects.* The way to reject unauthenticated configurations is unstable.** authorize-project plugin should reject user A configure a project when the project is configured as user B.** The current implementation raises exception when saving unauthenticated configurfation.* Difficult to configure permissions of builds.** What users really want to do is to configure permissions of builds.*** This is why I named it "authorize-project".** {{QueueItemAuthenticator}} is designed to return {{Authentication}}, which can be considered a user.** And then, the current design of authorize-project is to configure builds run as a specific user.*** This might mean "authenticate-project" was more appropreate for the plugin name.** This causes following difficulties:*** There can be cases that administrators don't want to bind a project to an actual specific user. Alice and Bob belongs to DevOps group. They want run builds of a project as the permission of DevOps, but don't to run as Alice or Bob as they both want configure the project.*** There can be cases that administrators cannot define a new user for build authentications. E.g. Jenkins is configured to use an external user dictionary (e.g. Active Directory) and the administrator of Jenkins doesn't administer that directory.|| Issue || Resolution || JIRA ticket ||| Authentication may change when configuration | Split configuration page | JENKINS-35081 || Unstable way to reject unauthenticated configuration | Restrict CONFIGURE permission by plugins | JENKINS-38219 || Difficulties in configuring permissions | Introduce define additional build-in users | |
Add Comment
[JIRA] (JENKINS-38219) Restrict Job.CONFIGURE permissions by plugins
Title: Message Title ikedam created an issue Jenkins / JENKINS-38219 Restrict Job.CONFIGURE permissions by plugins Issue Type: New Feature Assignee: ikedam Components: authorize-project-plugin, core Created: 2016/Sep/14 11:11 PM Priority: Minor Reporter: ikedam authorize-project plugin can easily cause security issues like following situations: User A configured a project X run as user A. User B updates the configuration of project B. User B can do something with the authentication of user A. authorize-project avoids this problem by raising an exception when user B tries to configure project A. But this has following problem: Raising exception isn't the "proper" way to forbid configuration. It might not work in some cases or in the future version of Jenkins. Users have to configure the project again from the beginning if it is rejected by authorize-project plugin. It isn't user-friendly. There are several ways to configure projects. Web UI, REST WebAPI, CLI. Authorize-project have to cover all configuration methods. I believe the "proper" way to forbid a user to configure a project is to revoke Job.CONFIGURE permission for that project form that user. Then what I need is a mechanism
[JIRA] (JENKINS-38205) Failed to deploy war on Weblogic: task completed abnormally (exit code = 1)
Title: Message Title Raphael CHAUMIER edited a comment on JENKINS-38205 Re: Failed to deploy war on Weblogic: task completed abnormally (exit code = 1) Hi [~guillermo_figueroa]You got a java.lang.ClassNotFoundException: weblogic.deploy.api.spi.DeploymentOptions. Can you check this class is under the wlfullclient.jar ? Can you try with a wlthint3client.jar ? can you try with weblogic.jar ? wlfullclient.jar is deprecated in WLS 12 (see https://docs.oracle.com/middleware/1213/wls/SACLT/basics.htm#SACLT125) I added this information in wiki Regards 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-38218) Additionnals classpath validation should support many dependencies
Title: Message Title Raphael CHAUMIER created an issue Jenkins / JENKINS-38218 Additionnals classpath validation should support many dependencies Issue Type: Improvement Assignee: Raphael CHAUMIER Components: weblogic-deployer-plugin Created: 2016/Sep/14 11:00 PM Priority: Minor Reporter: Raphael CHAUMIER If we set multiple dependencies in additional classpath, the plugin configuration validation failed. It would be possible to support multiple dependency definitions (separated by a : or plateform dependent separator Add Comment
[JIRA] (JENKINS-38217) Roadmap of authorize-project-plugin
Title: Message Title ikedam created an issue Jenkins / JENKINS-38217 Roadmap of authorize-project-plugin Issue Type: Epic Assignee: ikedam Components: authorize-project-plugin Created: 2016/Sep/14 10:59 PM Priority: Minor Reporter: ikedam authorize-project-plugin have following issues for its design. Authentications of the project during configuration and after configuration may change. This makes it difficult for other plugins behave depending on authentications of projects. The way to reject unauthenticated configurations is unstable. authorize-project plugin should reject user A configure a project when the project is configured as user B. The current implementation raises exception when saving unauthenticated configurfation. Difficult to configure permissions of builds. What users really want to do is to configure permissions of builds. This is why I named it "authorize-project".
[JIRA] (JENKINS-38205) Failed to deploy war on Weblogic: task completed abnormally (exit code = 1)
Title: Message Title Raphael CHAUMIER edited a comment on JENKINS-38205 Re: Failed to deploy war on Weblogic: task completed abnormally (exit code = 1) Hi [~guillermo_figueroa]You got a java.lang.ClassNotFoundException: weblogic.deploy.api.spi.DeploymentOptions. Can you check this class is under the wlfullclient.jar ? Can you try with a weblogic.jar ? Regards 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-38205) Failed to deploy war on Weblogic: task completed abnormally (exit code = 1)
Title: Message Title Raphael CHAUMIER commented on JENKINS-38205 Re: Failed to deploy war on Weblogic: task completed abnormally (exit code = 1) Hi Guillermo Figueroa You got a java.lang.ClassNotFoundException: weblogic.deploy.api.spi.DeploymentOptions. Can you check this class is under the wlfullclient.jar ? Can you try with a weblogic.jar ? Regards 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-38216) cobertura-plugin page reports 1.9.8 as latest version, but no changelog entry
Title: Message Title Aaron Curley created an issue Jenkins / JENKINS-38216 cobertura-plugin page reports 1.9.8 as latest version, but no changelog entry Issue Type: Bug Assignee: Oliver Gondža Components: cobertura-plugin Created: 2016/Sep/14 9:38 PM Labels: documentation plugin Priority: Minor Reporter: Aaron Curley The cobertura-plugin page reports 1.9.8 as the latest version of this plugin, but no changelog entry for 1.9.8 is present. We probably should update the changelog (or otherwise abandon 1.9.8 if that's not the version people should use). Add Comment
[JIRA] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
Title: Message Title Oleg Nenashev commented on JENKINS-26580 Re: For JNLP slaves the master-slave communication should be encrypted Aaron Curley Remoting 3 is going to include JNLP4 based on TLS. It's already integrated, but we have not released it yet 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-26580) For JNLP slaves the master-slave communication should be encrypted
Title: Message Title Aaron Curley commented on JENKINS-26580 Re: For JNLP slaves the master-slave communication should be encrypted Hi all, Correct me if I'm mistaken (since I've only taken a cursory look at the JNLP3 implementation, and that look was a few months ago) but aren't we currently using a custom-built "secure" transport protocol? (i.e. we built our own protocol using cryptographic primitives?) If so, this seems like an incorrect approach. It is generally recognized in our industry that "rolling your own cryptographic protocol" is a clear path to subtle cryptographic vulnerabilities. Isn't this something that we could just use TLS for? Provided we use strong settings (TLSv1.2, good ciphers, etc) wouldn't that give us a much better guarantee of security (than something custom-built)? 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-7321) Ability to re-run a past job with the same or similar parameters
Title: Message Title Sebastien Vas edited a comment on JENKINS-7321 Re: Ability to re-run a past job with the same or similar parameters I think rebuild implies that you are rebuilding at the same revision, but this plugin does not do that. I wonder if there is another simple way to do that without having to change the job configuration. 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-7321) Ability to re-run a past job with the same or similar parameters
Title: Message Title Sebastien Vas commented on JENKINS-7321 Re: Ability to re-run a past job with the same or similar parameters I think rebuild implies that you are rebuilding at the same revision, but this plugin does not do that. I wonder if there is another way to that without having to change the job configuration. 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-38168) job-params being overwritten by template
Title: Message Title Brantone commented on JENKINS-38168 Re: job-params being overwritten by template Couple candidates for commit cause: https://github.com/jenkinsci/ez-templates-plugin/commit/2fdcdd10b1326b4c0367e7eb1e2136c8b437347b https://github.com/jenkinsci/ez-templates-plugin/commit/b0eee1933a3d36a960e734b3f6915d94c12e1626 (Good reason for some unit tests ) 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-38214) Windows EXE runner should handle token macros
Title: Message Title Michael Fowler commented on JENKINS-38214 Re: Windows EXE runner should handle token macros fixed in PR https://github.com/jenkinsci/windows-exe-runner-plugin/pull/1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38215) msbuild compiler warning not detected / extracted
Title: Message Title Dirk Thomas created an issue Jenkins / JENKINS-38215 msbuild compiler warning not detected / extracted Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2016/Sep/14 8:23 PM Environment: Jenkins 2.7.1, Warnings Plug-in 4.56, Master is an Ubuntu 14.04 system, Slave is a Windows 10 system Priority: Minor Reporter: Dirk Thomas The console out of the job http://ci.ros2.org/job/ci_windows/1651/consoleFull shows the following compiler warning: (ClCompile target) -> cl : Command line warning D9002: ignoring unknown option '-std=c++11' but the result says: "MSBuild Warnings: 0 warnings". I am happy to provide more information if necessary and/or try a from-source build to check if it makes any difference. Add Comment
[JIRA] (JENKINS-38214) Windows EXE runner should handle token macros
Title: Message Title Michael Fowler created an issue Jenkins / JENKINS-38214 Windows EXE runner should handle token macros Issue Type: Improvement Assignee: Michael Fowler Components: windows-exe-runner-plugin Created: 2016/Sep/14 8:14 PM Priority: Major Reporter: Michael Fowler Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to
[JIRA] (JENKINS-38213) PROMOTION_ENV return env vars for the promotion environment not from the source of the promotion
Title: Message Title
Michael Fowler updated an issue
Jenkins / JENKINS-38213
PROMOTION_ENV return env vars for the promotion environment not from the source of the promotion
Change By:
Michael Fowler
{code:java}${PROMOTION_ENV, var="BUILD_DISPLAY_NAME"}${ENV, var="BUILD_DISPLAY_NAME"}{code}Both return the Build nameset name set in the promotion process , not the build name of the job containing the promotion procecss
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-38213) PROMOTION_ENV return env vars for the promotion environment not from the source of the promotion
Title: Message Title
Michael Fowler updated an issue
Jenkins / JENKINS-38213
PROMOTION_ENV return env vars for the promotion environment not from the source of the promotion
Change By:
Michael Fowler
{code:java} ${PROMOTION_ENV, var="BUILD_DISPLAY_NAME"}${ENV, var="BUILD_DISPLAY_NAME"} {code} Both return the Build name of nameset in the promotion process not the build name of the job containing the promotion procecss
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-38213) PROMOTION_ENV return env vars for the promotion environment not from the source of the promotion
Title: Message Title
Michael Fowler created an issue
Jenkins / JENKINS-38213
PROMOTION_ENV return env vars for the promotion environment not from the source of the promotion
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
promoted-builds-plugin
Created:
2016/Sep/14 7:42 PM
Priority:
Major
Reporter:
Michael Fowler
$ {PROMOTION_ENV, var="BUILD_DISPLAY_NAME"} $ {ENV, var="BUILD_DISPLAY_NAME"} Both return the Build name of the promotion process not the build name of the job containing the promotion procecss
Add Comment
[JIRA] (JENKINS-37770) Malformed JSON for /blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject
Title: Message Title emanuelez commented on JENKINS-37770 Re: Malformed JSON for /blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject The error is still there and this is the stacktrace: java.io.IOException: Failed to write failureCauseDisplayData at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151) at org.kohsuke.stapler.export.Property.writeTo(Property.java:126) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Property.writeTo(Property.java:135) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:222) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Property.writeValue(Property.java:279) at org.kohsuke.stapler.export.Property.writeValue(Property.java:168) at org.kohsuke.stapler.export.Property.writeTo(Property.java:139) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223) at org.kohsuke.stapler.export.Model.writeTo(Model.java:198) at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:273) at hudson.model.Api.doJson(Api.java:211) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:63) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at org.kohsuke.stapler.Function.renderResponse(Function.java:119) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:102) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:249) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at
[JIRA] (JENKINS-37770) Malformed JSON for /blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject
Title: Message Title emanuelez reopened an issue Jenkins / JENKINS-37770 Malformed JSON for /blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject Change By: emanuelez Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28629) Fix Apache Maven 3.3 support
Title: Message Title Robert Patrick commented on JENKINS-28629 Re: Fix Apache Maven 3.3 support I submitted a pull request to fix the Maven shell scripts to properly handle finding the correct .mvn directory when passing the file argument. No one seems to be looking at it from the Maven side... See MNG-5889 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Christian Höltje commented on JENKINS-38111 Re: github organization should allow 'clean before checkout' behavior Alex Dean It isn't clear what added the web-ui options would do. It would probably do both the @script and the checkout scm. Which would be better than nothing, but not allow the per-repository control that people really need. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Christian Höltje commented on JENKINS-38111 Re: github organization should allow 'clean before checkout' behavior Mark Waite I tried your Jenkinsfile against our Git Hub Enterprise and it failed because it doesn't have the correct credentials. I could shoe-horn them in there someplace (not sure where, since this interface is confusing). Either way, having to write that massive amount of boiler plate when all the values are in the scm object right now is really bad UX design. 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-31791) Cannot load job pages due to HistoryWidget hanging
Title: Message Title DJ Lee commented on JENKINS-31791 Re: Cannot load job pages due to HistoryWidget hanging Oliver Gondža aha - thanks for explaining! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Alex Dean resolved as Won't Fix closing because i believe that allowing additional git operations via Github Organization configuration will not have the effect I want to achieve. i want to remove old artifacts from a workspace prior to a build, but i believe that running `git clean` & etc during the initial checkout would actually clean the `project@script` working copy instead. if a maintainer thinks i've summarized this incorrectly, please re-open. Jenkins / JENKINS-38111 github organization should allow 'clean before checkout' behavior Change By: Alex Dean Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Matt Hess commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. I just tried the work around above by Yury Zaytsev ( explained more in JENKINS-30744)... this works... Thank you!!! However, it would still be nice to have an actual fix and get this out of the jenkinFile. 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-38212) We should only get the Jenkinsfile from github, not the whole repository
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-38212 We should only get the Jenkinsfile from github, not the whole repository Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/Sep/14 6:59 PM Environment: Jenkins 2.7.3 github-api v1.77 GitHub API Plugin github-branch-source v1.9 GitHub Branch Source Plugin github-oauth v0.24 GitHub Authentication plugin github-organization-folder v1.5 GitHub Organization Folder Plugin github v1.21.1 GitHub plugin Priority: Major Reporter: Christian Höltje As a developer, my git repository may be large. The GitHub Org Folder plugin should only fetch the Jenkinsfile, not the whole git repository. Currently, a git clone is done for every branch of every repository. For teams with a large code base (e.g. a .git directory of 1.7GiB (real example)) this can be bad: It can take a very long time. It uses a lot of disk space on the Jenkins server. Instead, I propose we use the raw file download mechanism instead: https://raw.Jenkinsfile?token= We have all the parts needed for this. We can always fall back to git clone if the github server doesn't support the raw. interface.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Christian Höltje commented on JENKINS-38111 Re: github organization should allow 'clean before checkout' behavior I created JENKINS-38212 to address the "getting the Jenkinsfile" story. 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-38211) JenkinsFiles cannot run on Linux agent of Windows master
Title: Message Title Justen Britain commented on JENKINS-38211 Re: JenkinsFiles cannot run on Linux agent of Windows master Some additional information that I didn't feel was appropriate for the description as it is a bit speculative. Looking into the "bad interpreter: No such file or directory" output, it seems that most of the time this is related to windows style EOL characters in the script that is attempting to run. I verified that the JenkinsFile did not have the windows specific ^M line endings, to no avail. My hunch as to what is happening is that the command, "sh mvn test" is getting converted to a script, due to this line of output "sh: /opt/jenkins/workspace/ProjectName - TestMultiBranchPipeline/developer-branch-1@tmp/durable-6f9c6a38/script.sh:" and that script is either: 1. Getting created on the windows machine and copied to the node causing it to have windows style line endings 2. Getting created by the windows master as a bash script and copied to the node Again this is speculative but seemed worth adding to the comments. 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-37791) When running a pipeline from a favourite we should not move the card
Title: Message Title Cliff Meyers started work on JENKINS-37791 Change By: Cliff Meyers 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-37281) Remove "StopPropagation" from blueocean-dashboard module
Title: Message Title Cliff Meyers updated JENKINS-37281 Jenkins / JENKINS-37281 Remove "StopPropagation" from blueocean-dashboard module Change By: Cliff Meyers 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-37281) Remove "StopPropagation" from blueocean-dashboard module
Title: Message Title Cliff Meyers commented on JENKINS-37281 Re: Remove "StopPropagation" from blueocean-dashboard module PR: https://github.com/jenkinsci/blueocean-plugin/pull/498 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-38211) JenkinsFiles cannot run on Linux agent of Windows master
Title: Message Title
Justen Britain created an issue
Jenkins / JENKINS-38211
JenkinsFiles cannot run on Linux agent of Windows master
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
pipeline
Created:
2016/Sep/14 6:36 PM
Environment:
Operating System: (master)Windows Server 2012 R2 64-bit, (slave/agent)amazon-linux-ami 2016.03-release 64-bit JRE/JDK: (master) 1.8.0_20, (slave/agent) 1.8.0_45 Jenkins Verison: 2.17 Plugin Versions: pipeline 2.2 pipeline-build-step 2.2 pipeline-input-step 2.1 pipeline-rest-api 1.7 pipeline-stage-step 2.1 pipeline-stage-view 1.7 Running as Jenkins service, not in Tomcat Reverse Proxy: No Jenkins Install Method: Windows Installer Slave Deploy method: via SSH Browser Version: Chrome - Version 53.0.2785.113 (64-bit)
Labels:
pipeline windows linux
Priority:
Major
Reporter:
Justen Britain
In a multi-branch pipeline using a JenkinsFile in the SCM it does not appear to be possible to execute 'sh' commands on a Linux node/agent. As per the example below, when using the 'sh' command in the JenkinsFile it causes a 'bad interpreter' error. JenkinsFile Snippit:
node('linux-agent-1') {
String jdktool = tool name: "1.7", type: 'hudson.model.JDK'
withEnv(["PATH+MVN=${tool 'Maven 2'}/bin", "PATH+JDK=${jdktool}/bin", "JAVA_HOME=${jdktool}"]) {
stage 'Checkout'
checkout scm
stage 'Build'
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Matt Hess commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Please fix.. this defect renders Jenkins at my current location as "not the way forward". 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-38209) Multibranch pipeline workspace files for PRs seems to be in wrong location
Title: Message Title Pete Hale closed an issue as Not A Defect Jenkins / JENKINS-38209 Multibranch pipeline workspace files for PRs seems to be in wrong location Change By: Pete Hale 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 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-38209) Multibranch pipeline workspace files for PRs seems to be in wrong location
Title: Message Title Pete Hale commented on JENKINS-38209 Re: Multibranch pipeline workspace files for PRs seems to be in wrong location I missed the nuance of having the run the command "checkout scm" in order to clone the github repor into the designated workspace location. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Christian Höltje commented on JENKINS-38111 Re: github organization should allow 'clean before checkout' behavior Right. There are two issues, really... The @script checkout on the master should probably always use shallow to prevent huge checkout times. If there was another way to just get the correct Jenkinsfile (e.g. https://raw.Jenkinsfile?token=) that'd be even better. The checkout scm needs to be configurable so changes specific to a repository can be setup, such as setting "clean before checkout" or "shallow clone". Otherwise this cannot be setup due to the way the GitHub Org Folder works. The second item is what I'm concerned about here. I should file another issue on the first item. 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-35246) Kubernetes nodes not getting deleted when a pipeline job fails
Title: Message Title Sebastien Vas commented on JENKINS-35246 Re: Kubernetes nodes not getting deleted when a pipeline job fails Hi Carlos. Sorry for the late response I was out of the country. the slaves are actually gone from the kubernetes cluster, they are just listed as offline / suspended in Jenkins and since we keep creating them, they pile up. 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-38053) JellyTagException on Multijob project view with Jenkins 2.7.3 LTS
Title: Message Title Caleb Mayeux commented on JENKINS-38053 Re: JellyTagException on Multijob project view with Jenkins 2.7.3 LTS Also seeing the same here on Jenkins 1.642.3 and 1.642.18.3. Also don't see issue on 1.21. Tried making a fresh multijob, and the job screen appears with no issue. The stacktrace appears when I add a "Trigger/call builds on other projects" build step from the Parameterized Trigger Plugin to a Multijob. Take it out, and the job screen doesn't have a stacktrace. Hopefully that tidbit helps narrow down the 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-31155) Workflow shared library improvements
Title: Message Title Flávio Augusto Valones edited a comment on JENKINS-31155 Re: Workflow shared library improvements same problem here, can't configure legacy or modern and the options seem to be reversed inverted . 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-37288) option to continue processing dsl if an error occurs
Title: Message Title mcrooney commented on JENKINS-37288 Re: option to continue processing dsl if an error occurs I agree and think there is a simple solution. The idea (at least to me) is that it degrades as gracefully as possible. So, it can continue doing other DSLs, but it is absolutely fine (and in fact preferred for me) that if an error happens processing a job or view, and continue is enabled, that this implicitly skips any job disabling/deleting. The build is definitely still broken so it is fine that it didn't get to the disabling/deleting step, the idea is that it at least finishes the job creation step as best it can (processing all the scripts), so that a rogue error in one script doesn't stop updating all the other jobs. Again, it should still fail and anyone responsible should still fix it, but with this option large orgs aren't nearly as hugely impacted by one syntax error. Just fail the build and don't move on to the job/view disabling/deleting step. What do you think? 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-31155) Workflow shared library improvements
Title: Message Title Flávio Augusto Valones commented on JENKINS-31155 Re: Workflow shared library improvements same problem here, can't configure legacy or modern and the options seem to be reversed. 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-37281) Remove "StopPropagation" from blueocean-dashboard module
Title: Message Title Cliff Meyers started work on JENKINS-37281 Change By: Cliff Meyers 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-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Alex Dean commented on JENKINS-38111 Re: github organization should allow 'clean before checkout' behavior Mark: Thank you for the idea. While I think that would work for now, I'm concerned about needing to statically specify so much of what is already provided by the built-in `scm` global variable. (As Christian also raises in JENKINS-37817.) Christian: Thank you for that explanation. Makes sense. Based on your explanation, it sounds like being able to specify 'clean before checkout' in the org plugin wouldn't accomplish what I want anyway. (Since I think i'd be cleaning the `@script` working copy rather than the actual workspace where the build it going to happen? If I've got that right, then I think this issue is probably invalid. 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-37233) Switch to a responsive table component
Title: Message Title Cliff Meyers commented on JENKINS-37233 Re: Switch to a responsive table component The grid does handle horizontal scrolling pretty well, when the grid's width is larger than the viewport. 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-37233) Switch to a responsive table component
Title: Message Title Cliff Meyers commented on JENKINS-37233 Re: Switch to a responsive table component James Dumay the API looks pretty decent, in particular it's crucial that the grid allows custom JSX for each cell so that we can customize it with anything we dream up. I tested it on my Nexus 6P and it seems decent, although some oddities: Sorting did not work at all; would need to debug to find out why. Maybe it's not listening for the right gesture events. Since the grid is virtualized, you can only command-F against the visible data. This will be an issue with any virtualized grid of course. Filtering is not really "baked in"; they're just writing a bunch of custom logic and updating the data provider to the grid. This is the same amount of code you'd write for any filtered list. Need to see how the dimensions work. They want explicit pixel dimensions for the width and height of the grid. It doesn't seem to support percentages, strangely. That seems... very unresponsive to me. Although we could write a JSX component we use to wrap the grid and specify appropriate width or height based on browser's resize event. I'd say this might be worth spiking a POC on a single screen, perhaps pipelines or activity? Maybe we can touch base on it when you are back next week and I whip something together real quick. I suspect I could adapt one of our screens in a few hours. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37843) REGRESSION direct link to a queued detail is not working anymore
Title: Message Title Justin Rainwater commented on JENKINS-37843 Re: REGRESSION direct link to a queued detail is not working anymore Thanks for the reply. I did a bit more digging and it seems to only apply to jobs created inside of folders. I've created this issue here: https://issues.jenkins-ci.org/browse/JENKINS-38210 Since all of our existing jobs are inside a folder this is quite the blocker for us. 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-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater created an issue Jenkins / JENKINS-38210 Can't link to blue ocean jobs inside folders Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/14 5:34 PM Environment: OS X 10.11.4, MacBook Pro Chrome 52 Jenkins 2.7.3 BlueOcean beta 1.0.0-b05 Priority: Major Reporter: Justin Rainwater 1. In regular Jenkins view click New Item, enter Item Name, select Folder and click OK. 2. Click Save on folder config page then click link to create a new job inside the folder. 3. Add a name for the job, select Freestyle Project and click OK. 4. Click Save in config page then click TRY BLUE OCEAN UI at the top. 5. Click the path in the list that matches the folder/job you just created (jenkins/myFolder/myJob) 6. The url should now end with /activity. Click Refresh Result: Screen doesn't load. Same as if you try to go to this link directly. Add Comment
[JIRA] (JENKINS-38209) Multibranch pipeline workspace files for PRs seems to be in wrong location
Title: Message Title Matthew DeTullio assigned an issue to Jesse Glick Jenkins / JENKINS-38209 Multibranch pipeline workspace files for PRs seems to be in wrong location Change By: Matthew DeTullio Assignee: Matthew DeTullio Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38209) Multibranch pipeline workspace files for PRs seems to be in wrong location
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-38209 Multibranch pipeline workspace files for PRs seems to be in wrong location Change By: Matthew DeTullio Component/s: workflow-multibranch-plugin Component/s: multi-branch-project-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38209) Multibranch pipeline workspace files for PRs seems to be in wrong location
Title: Message Title Pete Hale created an issue Jenkins / JENKINS-38209 Multibranch pipeline workspace files for PRs seems to be in wrong location Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Sep/14 5:30 PM Environment: Mac OS X 10.11 Jenkins 2.7 Pipeline plugin 2.3 Priority: Minor Reporter: Pete Hale Not sure if this cockpit error or not. I have a multibranch pipeline project and when a job is created for a PR it seems that the github repo is being stored in a location other that what is expected. The workspace name calculated for a job is either based on PR number or origina branch. When visiting the Workspace link from Pipeline steps I can see my source artifacts. But when I try to examine the artifacts in the files system I noticed that the artifacts are not present. I scan for known files in my repo and I have located them in a directory that has the workspace name, but with a name suffixed with '@script' . For example, if the job is from a PR number 10, the workspace name shown in console log as '/PR-10'. I can find this dir on the files system, but it is empty. I also find a dir on file system of '/PR-10@script'. It is in this dir I find my repo artifacts.
[JIRA] (JENKINS-38208) Display parameters in pipeline-stage-view
Title: Message Title Sterling Heibeck updated an issue Jenkins / JENKINS-38208 Display parameters in pipeline-stage-view Change By: Sterling Heibeck It would be nice to have the pipeline-stage-view support Parameterized builds and display the any parameters when for each run of the job runs. 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-38208) Display parameters in pipeline-stage-view
Title: Message Title Sterling Heibeck created an issue Jenkins / JENKINS-38208 Display parameters in pipeline-stage-view Issue Type: Improvement Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2016/Sep/14 5:17 PM Labels: plugins Priority: Minor Reporter: Sterling Heibeck It would be nice to have the pipeline-stage-view support Parameterized builds and display the parameters when the job runs. Add Comment
[JIRA] (JENKINS-38207) Can't use parameters from Mask Passwords Plugin in ansible
Title: Message Title Dmitry Raidman updated an issue Jenkins / JENKINS-38207 Can't use parameters from Mask Passwords Plugin in ansible Change By: Dmitry Raidman Priority: Major 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-38207) Can't use parameters from Mask Passwords Plugin in ansible
Title: Message Title
Dmitry Raidman created an issue
Jenkins / JENKINS-38207
Can't use parameters from Mask Passwords Plugin in ansible
Issue Type:
Bug
Assignee:
Jean-Christophe Sirot
Components:
ansible-plugin
Created:
2016/Sep/14 5:06 PM
Environment:
Jenkins version 2.21
Labels:
plugin ansible-plugin
Priority:
Major
Reporter:
Dmitry Raidman
Ansible not resolving parameters that set globally by the Mask Passwords Plugin. When I set such parameters as extra param instead of resolving the parameter to value the parameter name is passed to the Ansible playbook. Steps to reproduce: As example I'm passing AWS_KEY And AWS_SECRET parameters that set globally by the Mask Passwords Plugin, when using this parameters in shell step before the Invoke Ansible Playbook step is running such as below everythong works file echo $ {AWS_KEY} > /tmp/test.txt echo ${AWS_SECRET} >> /tmp/test.txt The parameters been resolved properly, and I get the proper values in /tmp/test.txt Next I'm adding to the Ansible playbook the following debug print: - name: Print debug debug: msg="KEY - {{ AWS_KEY }} SECRET - {{ AWS_SECRET }}" Next I'm configuring 2 extra parameters in Invoke Ansible Playbook (build step) KEY: AWS_KEY VALUE: ${AWS_KEY} KEY: AWS_SECRET VALUE: $ {AWS_SECRET} Running the job, and the output you get from the execution is: TASK [Print debug] * ok: [qa3-exs] => { "msg": "KEY - ${AWS_KEY} SECRET - *${AWS_SECRET} *" }
[JIRA] (JENKINS-38085) Settings not appearing in the sidebar
Title: Message Title
Daniel Kirkdorffer edited a comment on JENKINS-38085
Re: Settings not appearing in the sidebar
I'm not sure I understand the issue here, and why TimestampAnnotatorFactory has to be renamed. Why can't you add a "?t=" to your _javascript_ reference instead to ensure it is recognized as changed, or something similar? Or, why can't the reference you had to annotator.js include ``` {{ req.getScheme() ``` }} so that HTTPS is used? Just throwing out ideas without understanding the problem completely.
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-38085) Settings not appearing in the sidebar
Title: Message Title Daniel Kirkdorffer commented on JENKINS-38085 Re: Settings not appearing in the sidebar I'm not sure I understand the issue here, and why TimestampAnnotatorFactory has to be renamed. Why can't you add a "?t=" to your _javascript_ reference instead to ensure it is recognized as changed, or something similar? Or, why can't the reference you had to annotator.js include ```req.getScheme()``` so that HTTPS is used? Just throwing out ideas without understanding the problem completely. 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.
